[go: up one dir, main page]

WO2024187404A1 - Estimation de canal par tap pour un signal de référence d'onde continue modulé en fréquence - Google Patents

Estimation de canal par tap pour un signal de référence d'onde continue modulé en fréquence Download PDF

Info

Publication number
WO2024187404A1
WO2024187404A1 PCT/CN2023/081574 CN2023081574W WO2024187404A1 WO 2024187404 A1 WO2024187404 A1 WO 2024187404A1 CN 2023081574 W CN2023081574 W CN 2023081574W WO 2024187404 A1 WO2024187404 A1 WO 2024187404A1
Authority
WO
WIPO (PCT)
Prior art keywords
tap
fmcw
channel estimation
per
reference signal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/081574
Other languages
English (en)
Inventor
Kangqi LIU
Jing Jiang
Danlu Zhang
Weimin DUAN
Min Huang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Priority to PCT/CN2023/081574 priority Critical patent/WO2024187404A1/fr
Publication of WO2024187404A1 publication Critical patent/WO2024187404A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00—Baseband systems
    • H04L25/02—Details ; arrangements for supplying electrical power along data transmission lines
    • H04L25/0202—Channel estimation
    • H04L25/0224—Channel estimation using sounding signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00—Baseband systems
    • H04L25/02—Details ; arrangements for supplying electrical power along data transmission lines
    • H04L25/0202—Channel estimation
    • H04L25/0212—Channel estimation of impulse response

Definitions

  • the following relates to wireless communications, including per-tap channel estimation for a frequency modulated continuous wave reference signal.
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the 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-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems.
  • 4G systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems
  • 5G systems which may be referred to as New Radio (NR) systems.
  • a wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .
  • UE user equipment
  • the described techniques relate to improved methods, systems, devices, and apparatuses that support per-tap channel estimation for a continuous waveform in the time domain, such as a frequency modulated continuous wave (FMCW) reference signal.
  • a continuous waveform in the time domain such as a frequency modulated continuous wave (FMCW) reference signal.
  • FMCW frequency modulated continuous wave
  • Such a waveform may be used in a channel in which the waveform takes multiple paths, each associated with a unique channel delay, between a transmitter and a receiver.
  • different paths may be associated with different taps in the frequency domain of the channel response, and different taps may be associated with different amounts of error in the estimated channel response of the channel.
  • a network entity may transmit a first message to a user equipment (UE) indicating or otherwise identifying FMCW waveform parameters for an FMCW reference signal.
  • the network entity may transmit a second message to the UE indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal.
  • the UE may perform the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode and transmit a channel feedback message to the network entity indicating a result of the channel estimation procedure.
  • a method for wireless communications at a UE may include receiving a first message indicating one or more FMCW waveform parameters for a FMCW reference signal, receiving a second message indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal, performing the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode, and transmitting a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to receive a first message indicating one or more FMCW waveform parameters for a FMCW reference signal, receive a second message indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal, perform the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode, and transmit a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the apparatus may include means for receiving a first message indicating one or more FMCW waveform parameters for a FMCW reference signal, means for receiving a second message indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal, means for performing the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode, and means for transmitting a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • a non-transitory computer-readable medium storing code for wireless communications at a UE is described.
  • the code may include instructions executable by a processor to receive a first message indicating one or more FMCW waveform parameters for a FMCW reference signal, receive a second message indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal, perform the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode, and transmit a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • performing the channel estimation procedure according to the per-tap channel estimation mode may include operations, features, means, or instructions for compensating for a channel delay separately for each tap based on a channel delay estimation to obtain compensated taps, where the channel estimation procedure may be performed based on the compensated taps.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for performing an inverse fast-Fourier transform function on the FMCW reference signal to identify each tap in the set of taps from the FMCW reference signal and performing a fast Fourier transform function on a combination of the compensated taps to obtain a compensated FMCW reference signal.
  • compensating for the channel delay may include operations, features, means, or instructions for estimating the channel delay of each tap in the set of taps and compensating for the channel delay of each tap to obtain the compensated taps.
  • performing the channel estimation procedure according to the per-tap channel estimation mode may include operations, features, means, or instructions for identifying each port in a set of ports associated with the FMCW reference signal and performing, on a per-port basis for each port in the set of ports, channel delay estimation and compensation for each tap in the set of taps.
  • receiving the second message indicating the per-tap channel estimation mode may include operations, features, means, or instructions for receiving, via the second message, an indication that the UE may be to apply the per-tap channel estimation mode for channel estimation using the FMCW reference signal.
  • the method, apparatuses, and non-transitory computer-readable medium described herein may include further operations, features, means, or instructions for a radio resource control (RRC) message, a medium access control-control element (MAC-CE) , or a downlink control information (DCI) .
  • RRC radio resource control
  • MAC-CE medium access control-control element
  • DCI downlink control information
  • receiving the second message indicating the per-tap channel estimation mode may include operations, features, means, or instructions for receiving an indication of a channel delay threshold and transitioning to the per-tap channel estimation mode based on a channel delay associated with the FMCW reference signal satisfying the channel delay threshold.
  • an RRC message In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, an RRC message, a MAC-CE, or a DCI.
  • receiving the second message indicating the per-tap channel estimation mode may include operations, features, means, or instructions for receiving an indication of a port number threshold and transitioning to the per-tap channel estimation mode based on a port number associated with the FMCW reference signal satisfying the port number threshold.
  • an RRC message In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, an RRC message, a MAC-CE, or a DCI.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting a UE capability message indicating a first timing gap associated with performing channel estimation and reporting on a non-per-tap basis and a second timing gap associated with performing channel estimation and reporting on a per-tap basis according to the per-tap channel estimation mode, where the indication of the per-tap channel estimation mode may be based on the UE capability message.
  • a method for wireless communications at a network entity may include transmitting, to a UE, a first message indicating one or more FMCW waveform parameters for a FMCW reference signal, transmitting a second message indicating a per-tap channel estimation mode associated with the UE performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal, and receiving, from the UE, a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to transmit, to a UE, a first message indicating one or more FMCW waveform parameters for a FMCW reference signal, transmit a second message indicating a per-tap channel estimation mode associated with the UE performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal, and receive, from the UE, a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the apparatus may include means for transmitting, to a UE, a first message indicating one or more FMCW waveform parameters for a FMCW reference signal, means for transmitting a second message indicating a per-tap channel estimation mode associated with the UE performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal, and means for receiving, from the UE, a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • a non-transitory computer-readable medium storing code for wireless communications at a network entity is described.
  • the code may include instructions executable by a processor to transmit, to a UE, a first message indicating one or more FMCW waveform parameters for a FMCW reference signal, transmit a second message indicating a per-tap channel estimation mode associated with the UE performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal, and receive, from the UE, a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • transmitting the second message indicating the per-tap channel estimation mode may include operations, features, means, or instructions for transmitting, via the second message, an indication that the UE may be to apply the per-tap channel estimation mode for channel estimation using the FMCW reference signal.
  • the method, apparatuses, and non-transitory computer-readable medium described herein may include further operations, features, means, or instructions for an RRC message, a MAC-CE, or a DCI.
  • transmitting the second message indicating the per-tap channel estimation mode may include operations, features, means, or instructions for transmitting an indication of a channel delay threshold, where the UE transitions to the per-tap channel estimation mode based on a channel delay associated with the FMCW reference signal satisfying the channel delay threshold.
  • an RRC message In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, an RRC message, a MAC-CE, or a DCI.
  • transmitting the second message indicating the per-tap channel estimation mode may include operations, features, means, or instructions for transmitting an indication of a port number threshold, where the UE transitions to the per-tap channel estimation mode based on a port number associated with the FMCW reference signal satisfying the port number threshold.
  • an RRC message In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, an RRC message, a MAC-CE, or a DCI.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a UE capability message indicating a first timing gap associated with performing channel estimation and reporting on a non-per-tap basis and a second timing gap associated with performing channel estimation and reporting on a per-tap basis according to the per-tap channel estimation mode, where the indication of the per-tap channel estimation mode may be based on the UE capability message.
  • FIG. 1 illustrates an example of a wireless communications system that supports per-tap channel estimation for a frequency modulated continuous wave (FMCW) reference signal in accordance with one or more aspects of the present disclosure.
  • FMCW frequency modulated continuous wave
  • FIG. 2 illustrates an example of a receiver that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • FIG. 3 illustrates an example of a method that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • FIG. 4 illustrates an example of a method that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • FIG. 5 illustrates an example of a timing configuration that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • FIGs. 6 and 7 illustrate block diagrams of devices that support per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • FIG. 8 illustrates a block diagram of a communications manager that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • FIG. 9 illustrates a diagram of a system including a device that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • FIGs. 10 and 11 illustrate block diagrams of devices that support per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • FIG. 12 illustrates a block diagram of a communications manager that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • FIG. 13 illustrates a diagram of a system including a device that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • FIGs. 14 through 18 illustrate flowcharts showing methods that support per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • Some wireless networks may use a frequency modulated continuous wave (FMCW) waveform to convey information.
  • the FMCW waveform may support wideband channel estimation using a narrowband baseband.
  • the FMCW waveform may include the transmit frequency varying (e.g., increasing/decreasing) over the time domain according to a slope S during a symbol of a slot.
  • Some networks may generally use the FMCW waveform to estimate an orthogonal frequency division multiplexed (OFDM) channel. Such techniques reduce the sampling rate of legacy OFDM channel estimation techniques. However, these techniques generally do not address channel delay of the FMCW waveform.
  • OFDM orthogonal frequency division multiplexed
  • the FMCW waveform may be received by the receiver directly from the transmitting device (direct line-of-site) , but the FMCW waveform may take multiple paths (e.g., due to reflections, obstructions, or other physical conditions) between the transmitting device and the receiving device. Each path may be associated with a different frequency domain tap in the FMCW waveform, and different taps may be associated with different amounts of error in a channel estimate for the FMCW waveform.
  • Conventional techniques do not provide a mechanism to address the per-tap channel term error introduced by the channel delay during the channel estimation process.
  • the techniques described herein relate to improved methods, systems, devices, and apparatuses that support per-tap channel estimation for a FMCW reference signal.
  • the described techniques provide for per-tap channel error term (e.g., per-tap in the frequency domain) when using a FMCW waveform (e.g., a continuous wave in the time domain) to improve channel estimation.
  • a network entity may transmit a first message to a user equipment (UE) indicating or otherwise identifying FMCW waveform parameters for an FMCW reference signal.
  • the network entity may transmit a second message to the UE indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal.
  • the UE may perform the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode and transmit a channel feedback message to the network entity indicating a result of the channel estimation procedure.
  • aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to per-tap channel estimation for a FMCW reference signal.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • the wireless communications system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130.
  • the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-A Pro
  • NR New Radio
  • the network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities.
  • a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature.
  • network entities 105 and UEs 115 may wirelessly communicate via one or more communication links 125 (e.g., a radio frequency (RF) access link) .
  • a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish one or more communication links 125.
  • the coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .
  • RATs radio access technologies
  • the UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times.
  • the UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1.
  • the UEs 115 described herein may be capable of supporting communications with various types of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.
  • a node of the wireless communications system 100 which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein.
  • a node may be a UE 115.
  • a node may be a network entity 105.
  • a first node may be configured to communicate with a second node or a third node.
  • the first node may be a UE 115
  • the second node may be a network entity 105
  • the third node may be a UE 115.
  • the first node may be a UE 115
  • the second node may be a network entity 105
  • the third node may be a network entity 105.
  • the first, second, and third nodes may be different relative to these examples.
  • reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node.
  • disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
  • network entities 105 may communicate with the core network 130, or with one another, or both.
  • network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) .
  • network entities 105 may communicate with one another via a backhaul communication link 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via a core network 130) .
  • network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof.
  • the backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) , one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof.
  • a UE 115 may communicate with the core network 130 via a communication link 155.
  • One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) .
  • a base station 140 e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a giga-NodeB (either of which may be
  • a network entity 105 may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which 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 a base station 140) .
  • a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among 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) ) .
  • IAB integrated access backhaul
  • O-RAN open RAN
  • vRAN virtualized RAN
  • C-RAN cloud RAN
  • a network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) 180 system, or any combination thereof.
  • An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) .
  • one or more network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • the split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof
  • a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack.
  • the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
  • the CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access control (MAC) layer
  • a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack.
  • the DU 165 may support one or multiple different cells (e.g., via one or more RUs 170) .
  • a functional split between a CU 160 and a DU 165, or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) .
  • a CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • CU-CP CU control plane
  • CU-UP CU user plane
  • a CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) .
  • a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that are in communication via such communication links.
  • infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) .
  • IAB network one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other.
  • One or more IAB nodes 104 may be referred to as a donor entity or an IAB donor.
  • One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140) .
  • the one or more donor network entities 105 may be in communication with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120) .
  • IAB nodes 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs 165 of a coupled IAB donor.
  • IAB-MT IAB mobile termination
  • An IAB-MT may include an independent set of antennas for relay of communications with UEs 115, or may share the same antennas (e.g., of an RU 170) of an IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) .
  • the IAB nodes 104 may include DUs 165 that support communication links with additional entities (e.g., IAB nodes 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) .
  • one or more components of the disaggregated RAN architecture e.g., one or more IAB nodes 104 or components of IAB nodes 104) may be configured to operate according to the techniques described herein.
  • an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor) , IAB nodes 104, and one or more UEs 115.
  • the IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130) . That is, an IAB donor may refer to a RAN node with a wired or wireless connection to core network 130.
  • the IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170) , in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link) .
  • IAB donor and IAB nodes 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol) .
  • the CU 160 may communicate with the core network via an interface, which may be an example of a portion of backhaul link, and may communicate with other CUs 160 (e.g., a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of a portion of a backhaul link.
  • An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities) .
  • a DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through one or more other IAB nodes 104) .
  • an IAB node 104 may also be referred to as a parent node or a child node to other IAB nodes 104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of IAB nodes 104 may provide a Uu interface for a child IAB node 104 to receive signaling from a parent IAB node 104, and the DU interface (e.g., DUs 165) may provide a Uu interface for a parent IAB node 104 to signal to a child IAB node 104 or UE 115.
  • the DU interface e.g., DUs 165
  • IAB node 104 may be referred to as a parent node that supports communications for a child IAB node, or referred to as a child IAB node associated with an IAB donor, or both.
  • the IAB donor may include a CU 160 with a wired or wireless connection (e.g., a backhaul communication link 120) to the core network 130 and may act as parent node to IAB nodes 104.
  • the DU 165 of IAB donor may relay transmissions to UEs 115 through IAB nodes 104, or may directly signal transmissions to a UE 115, or both.
  • the CU 160 of IAB donor may signal communication link establishment via an F1 interface to IAB nodes 104, and the IAB nodes 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through the DUs 165. That is, data may be relayed to and from IAB nodes 104 via signaling via an NR Uu interface to MT of the IAB node 104. Communications with IAB node 104 may be scheduled by a DU 165 of IAB donor and communications with IAB node 104 may be scheduled by DU 165 of IAB node 104.
  • one or more components of the disaggregated RAN architecture may be configured to support per-tap channel estimation for a FMCW reference signal as described herein.
  • some operations described as being performed by a UE 115 or a network entity 105 may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180) .
  • a UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples.
  • a UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer.
  • PDA personal digital assistant
  • a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC machine type communications
  • the UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • devices such as other UEs 115 that may sometimes act as relays as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • the UEs 115 and the network entities 105 may wirelessly communicate with one another via one or more communication links 125 (e.g., an access link) using resources associated with one or more carriers.
  • the term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links 125.
  • a carrier used for a communication link 125 may include a portion of a RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR) .
  • BWP bandwidth part
  • Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling.
  • the wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation.
  • a UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration.
  • Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.
  • Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105.
  • the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105 may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105) .
  • a network entity 105 e.g., a base station 140, a CU 160, a DU 165, a RU 170
  • a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers.
  • a carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115.
  • E-UTRA evolved universal mobile telecommunication system terrestrial radio access
  • a carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different radio access technology) .
  • the communication links 125 shown in the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions.
  • Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
  • a carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100.
  • the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) .
  • Devices of the wireless communications system 100 e.g., the network entities 105, the UEs 115, or both
  • the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths.
  • each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
  • Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) .
  • MCM multi-carrier modulation
  • OFDM orthogonal frequency division multiplexing
  • DFT-S-OFDM discrete Fourier transform spread OFDM
  • a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related.
  • the quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication.
  • a wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
  • One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing ( ⁇ f) and a cyclic prefix.
  • a carrier may be divided into one or more BWPs having the same or different numerologies.
  • a UE 115 may be configured with multiple BWPs.
  • a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
  • Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) .
  • Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
  • SFN system frame number
  • Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration.
  • a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots.
  • each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing.
  • Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) .
  • a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f ) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
  • a subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) .
  • TTI duration e.g., a quantity of symbol periods in a TTI
  • the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
  • Physical channels may be multiplexed for communication using a carrier according to various techniques.
  • a physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • a control region e.g., a control resource set (CORESET)
  • CORESET control resource set
  • One or more control regions may be configured for a set of the UEs 115.
  • one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner.
  • An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size.
  • Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.
  • a network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof.
  • the term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) , or others) .
  • a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates.
  • Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105.
  • a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell.
  • a small cell may be associated with a lower-powered network entity 105 (e.g., a lower-powered base station 140) , as compared with a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells.
  • Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) .
  • a network entity 105 may support one or multiple cells and may also support communications via the one or more cells using one or multiple component carriers.
  • a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB) ) that may provide access for different types of devices.
  • protocol types e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB)
  • NB-IoT narrowband IoT
  • eMBB enhanced mobile broadband
  • a network entity 105 may be movable and therefore provide communication coverage for a moving coverage area 110.
  • 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.
  • the overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105.
  • the wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.
  • the wireless communications system 100 may support synchronous or asynchronous operation.
  • network entities 105 e.g., base stations 140
  • network entities 105 may have different frame timings, and transmissions from different network entities 105 may, in some examples, not be aligned in time.
  • the techniques described herein may be used for either synchronous or asynchronous operations.
  • Some UEs 115 may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) .
  • M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention.
  • M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program.
  • Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
  • Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently) .
  • half-duplex communications may be performed at a reduced peak rate.
  • Other power conservation techniques for the UEs 115 include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications) , or a combination of these techniques.
  • some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
  • the wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof.
  • the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) .
  • the UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions.
  • Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data.
  • Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications.
  • the terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
  • a UE 115 may be configured to support communicating directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) .
  • D2D device-to-device
  • P2P peer-to-peer
  • one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105.
  • one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105.
  • groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to each of the other UEs 115 in the group.
  • a network entity 105 may facilitate the scheduling of resources for D2D communications.
  • D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
  • a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115) .
  • vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these.
  • V2X vehicle-to-everything
  • V2V vehicle-to-vehicle
  • a vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system.
  • vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.
  • roadside infrastructure such as roadside units
  • network nodes e.g., network entities 105, base stations 140, RUs 170
  • V2N vehicle-to-network
  • the core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
  • the core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management function
  • S-GW serving gateway
  • PDN Packet Data Network gateway
  • UPF user plane function
  • the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130.
  • NAS non-access stratum
  • User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions.
  • the user plane entity may be connected to IP services 150 for one or more network operators.
  • the IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
  • IMS IP Multimedia Subsystem
  • the wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) .
  • the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from 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 the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
  • HF high frequency
  • VHF very high frequency
  • the wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band.
  • SHF super high frequency
  • EHF extremely high frequency
  • the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170) , and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas.
  • mmW millimeter wave
  • such techniques may facilitate using antenna arrays within a device.
  • EHF transmissions may be subject to even greater attenuation and shorter range than SHF or UHF transmissions.
  • the techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
  • the wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands.
  • the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) radio access technology, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • LAA License Assisted Access
  • LTE-U LTE-Unlicensed
  • NR NR technology
  • an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance.
  • operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) .
  • Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
  • a network entity 105 e.g., a base station 140, an RU 170
  • a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming.
  • the antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming.
  • one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower.
  • antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations.
  • a network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115.
  • a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations.
  • an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
  • the network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers.
  • Such techniques may be referred to as spatial multiplexing.
  • the multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas.
  • Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) .
  • Different spatial layers may be associated with different antenna ports used for channel measurement and reporting.
  • MIMO techniques include single-user MIMO (SU-MIMO) , for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , for which multiple spatial layers are transmitted to multiple devices.
  • SU-MIMO single-user MIMO
  • Beamforming which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device.
  • Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference.
  • the adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device.
  • the adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
  • a network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations.
  • a network entity 105 e.g., a base station 140, an RU 170
  • Some signals e.g., synchronization signals, reference signals, beam selection signals, or other control signals
  • the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission.
  • Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.
  • a transmitting device such as a network entity 105
  • a receiving device such as a UE 115
  • Some signals may be transmitted by transmitting device (e.g., a transmitting network entity 105, a transmitting UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as a receiving network entity 105 or a receiving UE 115) .
  • a single beam direction e.g., a direction associated with the receiving device, such as a receiving network entity 105 or a receiving UE 115
  • the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions.
  • a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.
  • transmissions by a device may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115) .
  • the UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands.
  • the network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS) ) , which may be precoded or unprecoded.
  • a reference signal e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS)
  • the UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook) .
  • PMI precoding matrix indicator
  • codebook-based feedback e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook
  • these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170)
  • a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device) .
  • a receiving device may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a receiving device (e.g., a network entity 105) , such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • a receiving device e.g., a network entity 105
  • signals such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions.
  • a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal) .
  • the single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions) .
  • receive configuration directions e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions
  • the wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack.
  • communications at the bearer or PDCP layer may be IP-based.
  • An RLC layer may perform packet segmentation and reassembly to communicate via logical channels.
  • a MAC layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency.
  • an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data.
  • a PHY layer may map transport channels to physical channels.
  • the UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully.
  • Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., a communication link 125, a D2D communication link 135) .
  • HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) .
  • FEC forward error correction
  • ARQ automatic repeat request
  • HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions) .
  • a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
  • At least some of the UEs 115 and network entities 105 may support communicating using FMCW waveforms, and may use a per-tap channel estimation mode with respect to FMCW reference signals.
  • a UE 115 may receive a first message from a network entity 105 indicating one or more FMCW waveform parameters for a FMCW reference signa.
  • the UE 115 may receive a second message from the network entity 105 indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the UE 115 may perform the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode.
  • the UE 115 may transmit a channel feedback message to the network entity 105 indicating a result of the channel estimation procedure using the FMCW reference signal.
  • a network entity 105 may transmit, to a UE 115, a first message indicating one or more FMCW waveform parameters for a FMCW reference signal.
  • the network entity 105 may transmit a second message indicating a per-tap channel estimation mode associated with the UE 115 performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the network entity 105 may receive, from the UE 115, a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • FIG. 2 illustrates an example of a receiver 200 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • Receiver 200 may implement aspects of wireless communications system 100.
  • Receiver 200 may include an antenna 205, a mixer 210, a VCO 215, a LPF 220, an ADC 225, a front-end 230, a iFFT 235, a port separator 240, a channel delay estimator 245, a filter/compensator 250, a combiner 255, and a FFT 260.
  • the receiver 200 may implement aspects of a UE, which may be an example of the corresponding device described herein.
  • Wireless networks employ various waveform and/or multiple-access designs to support a wide variety of use cases, such as mobile broadband, metaverse, massive IoT, sidelink, massive spectrum aggregation/duplexing, UE cooperation, and the like.
  • Examples of such waveform and/or multiple-access designs may include full duplex communications, radio frequency (RF) sensing, positioning, physical layer security, and more.
  • RF radio frequency
  • Such waveform and/or multiple-access designs may be adopted in existing frequency bands (e.g., frequency range one (FR1) ) as well as new frequency bands (e.g., frequency range two (FR2) , frequency range three (FR3) , and beyond) to support such RF techniques, duplexing, MIMO functions, and the like.
  • emerging waveform and/or multiple-access designs support massive connectivity (e.g., a large number of wireless devices) and improve cell capacity.
  • massive connectivity e.g., a large number of wireless devices
  • Such techniques provide efficient support mechanisms for channel access for an ever-growing number of users (e.g., UEs) .
  • Waveform designs generally apply a number of metrics and/or requirements.
  • Examples of waveform design metrics include, but are not limited to, spectrum efficiency, energy efficiency (e.g., both at the transmitter, such as power amplifier (PA) efficiency, and the receiver, such as processing power efficiency) , waveform processing complexity and latency, RF impairments (such as error vector magnitude (EVM) , spectrum confinement (in-band and out-of-band emissions) withing a practical PA model, support efficient multi-user/MIMO multiple-access, and more.
  • Such waveform designs may also include various requirements against various channel conditions and/or impairments, such as fading (e.g., time variation, inter-symbol interference (ISI) , and so forth) , phase noise, PA nonlinearity, and the like.
  • ISI inter-symbol interference
  • FMCW waveforms are one non-limiting example of such waveform designs adopted within a wireless communications system.
  • the FMCW waveform (or signal) has roots in radio detection and ranging (RADAR) applications where the waveform radiates at a continuous transmission power, but where the frequency of the waveform may change over time.
  • the FMCW waveform may include modulating the FMCW signal in the frequency domain to carry or otherwise convey information (e.g., data and/or control information) across a wireless medium.
  • FMCW techniques generally relate to channel performance estimation and reporting. Broadly, this enables the signal processing procedures for the channel estimation to be performed in the time domain when the frequency domain channel is being estimated.
  • FFT fast Fourier transform
  • the frequency domain channel can be estimated directly in the time domain using a low sampling rate (e.g., the sampling rate requirement is reduced) . In some examples, this may result in a sampling rate of 1.69%compared to traditional frequency domain channel estimation and reporting techniques of the OFDM channel.
  • the frequency domain OFDM channel can be estimated directly in the time domain signaling processing without FFT.
  • the FMCW transmitted signal of a symbol length can be represented as:
  • the FMCW signal may be generated using a voltage controlled oscillator (VCO) in the analog domain according to:
  • VCO voltage controlled oscillator
  • the FMCW signal received at the antenna 205 can be represented as:
  • the receiver may generate an FMCW signal using a VCO (such as the VCO 215) in the analog domain according to:
  • exponent (exp) function is associated with OFDM channel estimation.
  • the FMCW signal generated by the VCO 215 may be mixed with the received FMCW signal in the mixer 210 (e.g., to remove the center frequency) , which is then passed through the LPF 220.
  • the mixed signal after the LPF 220 may be represented as:
  • the output of the ADC 225 may generally be provided to the receiving device front-end circuitry (e.g., the front-end 230) for further processing and output.
  • the output of the front-end 230 according to these techniques may be considered a non-per-tap channel compensated estimation procedure.
  • Channel estimation according to this technique in a 50 MHz bandwidth having a four RB granularity may include the ADC sampling rate (e.g., applied by the ADC 225) being a fraction of the sampling rate applied during conventional OFDM channel estimation procedures (e.g., using as little as 1.69%of the sampling rate of the legacy techniques) . Accordingly, such non-per-tap compensated FMCW based channel estimation techniques using an FMCW based wideband channel estimation using narrowband baseband improves efficiency and has a low complexity when compared to legacy techniques.
  • multi-port FMCW based wideband channel estimation may be employed where the FMCW signal is associated with multiple ports (e.g., antenna (s) , antenna panel (s) or array (s) , transmit chain (s) , and the like) of the transmitting device.
  • multiple ports e.g., antenna (s) , antenna panel (s) or array (s) , transmit chain (s) , and the like
  • there is a per-tap, per-port channel error term during the channel estimation process which also increases with the channel delay spread.
  • the channel estimation of the multi-port FMCW signal may be based on As in the single port case, there will be additional per-tap channel error term (e.g., exp (j2 ⁇ S ⁇ i ⁇ p ) ) in the multi-port scheme.
  • aspects of the techniques described herein provide various mechanisms to mitigate or compensate for the per-tap channel error discussed above.
  • aspects of the techniques may be applied to improve the channel estimation accuracy when the channel delay spread is large, yet while maintaining the same ADC sampling rate discussed above.
  • aspects of these techniques are based on the diagram (e.g., receiver 200) of the per-tap compensation for FMCW based wideband (e.g., in the frequency domain) channel estimation scheme.
  • aspects of the techniques described herein enable switching between the per-tap channel estimation mode and a non-per-tap channel compensated estimation mode (e.g., based on the channel delay spread) .
  • Receiver 200 illustrates a non-limiting example of a diagram or configuration of the receiving device that implements the techniques described herein. Aspects of these techniques may be based on the receiving device (e.g., a UE) implementing receiver 200 being configured or otherwise signaled with FMCW parameter (s) for an FMCW reference signal.
  • the FMCW reference signal parameters may generally identify various configuration and/or resource parameters used by the transmitting device when transmitting the FMCW reference signal.
  • the FMCW reference signal parameters may define a frequency resource, time resource, spatial resource, and/or code resource being used to transmit the FMCW reference signal.
  • the FMCW reference signal parameters may define whether the FMCW transmission is transmitted from a single port or multiple ports of the transmitting device.
  • the FMCW reference signal parameters may be used by the UE to identify or otherwise determine when, where, and how to monitor for the FMCW reference signal to perform channel estimation.
  • the indication of the FMCW reference signal parameters may be received in a first message, which may be a system message (e.g., indicated as part of a system SSB) and/or in a UE-specific message, such as an RRC message, a medium access control-control element (MAC-CE) message, and/or a downlink control information (DCI) message.
  • a system message e.g., indicated as part of a system SSB
  • a UE-specific message such as an RRC message, a medium access control-control element (MAC-CE) message, and/or a downlink control information (DCI) message.
  • RRC resource control information
  • MAC-CE medium access control-control element
  • DCI downlink control information
  • the UE may also receive or otherwise be configured with a per-tap channel estimation mode from the network (e.g., received or otherwise obtained in a second message, which may be the same as the first message or in a separate message) .
  • the per-tap channel estimation mode may signal or otherwise indicate whether/that the UE, when performing channel estimation using the FMCW reference signal, is to turn on or otherwise begin application of the per-tap channel estimation techniques described herein. That is, the per-tap channel estimation mode may be associated with the UE performing channel estimation on a per-tap basis for each tap in the set of taps associated with the FMCW reference signal. Again, each tap in the set of taps may correspond to or otherwise be based on the unique channel delay associated with the FMCW reference signal.
  • the UE may perform the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode and then transmit a feedback signal (e.g., a CSI report) to the network indicating the results of the channel estimation procedure.
  • a feedback signal e.g., a CSI report
  • this may include the UE compensating for the channel delay separately for each tap based on an estimation of the channel delay to obtain compensated taps.
  • the feedback message may carry or otherwise convey an indication channel performance metrics (e.g., RSRP, SINR) derived based on the compensated taps.
  • This may include the output of the front-end 230 being provided to the iFFT 235. This may transition or switch the time domain signal into the frequency domain for the purposes of performing the per-tap channel estimation.
  • the UE may initiate or otherwise perform an iFFT function on the FMCW reference signal to identify or otherwise determine each tap in the set of taps.
  • the iFFT function may be based on:
  • the output of the iFFT 235 may optionally be provided to the port separator 240 to separate the different ports when the FMCW reference signal is a multi-port signal.
  • the output of the port separator 240, when applied, or the output of the iFFT 235 when the port separator 240 is not applied, may be provided to the channel delay estimator 245 for channel delay estimation. That is, the UE may calculate, estimate, or otherwise determine the channel delay of each tap in the set of taps.
  • the channel delay estimator 245 may be based on: for a multi-port FMCW signal to estimate the channel delay using for different ports i.
  • the output of the channel delay estimator 245 may be provided to the filter/compensator 250, which may apply a digital filter and then compensate for the channel delay estimation of each tap to obtain the compensated taps.
  • the digital filter and per-tap compensation may include each tap being filtered by the digital filter and compensated with is estimated by the channel delay estimator 245, and this term is a fixed phase shift term.
  • the output of the port separator 240 (e.g., the compensated taps) may be provided to the combiner 255 to be combined (e.g., to recreate the FMCW reference signal using the compensated taps) .
  • combining the per-tap channel for port i after compensation may be based on
  • the output of the combiner 255 may be provided to the FFT 260 to be converted again to the time domain, which is then output for further processing by the receiving device (e.g., to be reported in the feedback message) .
  • This may include the UE performing the FFT function on the combination of the compensated taps to identify or otherwise obtain the compensated FMCW signal, which is then provided for further processing and reporting by the UE.
  • the FFT function (e.g., the output of the FFT function) may be based on This approach may result in a tradeoff between complexity and channel estimation accuracy, which may be leveraged when the channel delay for the wireless channel over which the FMCW reference signal is transmitted increases (e.g., reaches or otherwise satisfies a channel delay threshold) .
  • the FMCW reference signal may be transmitted using multiple ports (e.g., in a set of ports a-through-n, with n being a positive integer) of the transmitting device.
  • the UE may identify and separate each port in the set of ports associated with the FMCW reference signal and perform, on a per-port basis for each of ports a-through-n, the per-tap channel delay estimation and compensation on a per-tap basis. This may include the port separator 240 identifying each port in the multi-port FMCW reference signal and outputting each port of the FMCW reference signal port into separate channel delay and compensation paths.
  • the channel delay estimator 245-a may estimate the channel delay for each tap associated with port a while the channel delay estimator 245-n may estimate the channel delay for port n.
  • the filter/compensator 250-a may apply the digital filter and per-tap compensation for each tap associated with port a while the filter/compensator 250-n may perform the same function for port n.
  • the combiner 255-a may combine the compensated taps for each tap associated with port a while the combiner 255-n may perform the same function for port n.
  • the FFT 260-a may implement the FFT function on the combined set of compensated taps associated with port a while the FFT 260-n may perform the same function for port n.
  • the number of ports included in the set of ports may be based on, and signaled to the UE in the FMCW parameters (e.g., in the first message) and/or in the indication of the per-tap channel estimation mode (e.g., in the second message) .
  • receiver 200 illustrates a non-limiting example of, when enabled or turned on, compensating for the channel delay associated with the FMCW reference signal during channel estimation on a per-tap basis.
  • the FMCW reference signal is a multi-port signal
  • the FMCW reference signal based channel estimation may be applied on a per-tap, per-port basis. This may improve the accuracy of the channel estimation by mitigating the channel delay associated with the wireless channel, with minimal processing by the UE.
  • FIG. 3 illustrates an example of a method 300 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • Method 300 may implement aspects of wireless communications system 100 and/or receiver 200. Aspects of the method 300 may be implemented at and/or implemented by a UE 305 and/or a network entity 310, which may be examples of the corresponding devices described herein. In some aspects, the UE 305 may be configured or otherwise support the features discussed with reference to receiver 200.
  • Method 300 illustrates a non-limiting example of switching between the per-tap channel estimation mode and a non-per-tap channel compensated estimation mode. That is, method 300 illustrates an example where the network entity 310 may indicate to the UE 305 that it is to compensate for the per-tap error term in its CSI report (e.g., in its channel feedback message) .
  • the UE 305 may transmit or otherwise provide (and the network entity 310 may receive or otherwise obtain) a UE capability report.
  • the UE capability report may be transmitted in a message carried or otherwise conveyed in DCI, MAC-CE and/or RRC signaling.
  • the UE capability report may be a dynamic indication and/or a semi-persistent indication.
  • the UE capability report may indicate, identify, or otherwise provide information associated with the capabilities of the UE 305, such as supported operating frequencies, timing information, power information, and more.
  • the UE capability report may be an FMCW capability report that indicates whether the UE 305 supports or is otherwise capable of performing channel estimation on a per-tap basis using the FMCW reference signal according to the per-tap channel estimation mode and/or according to a non-per-tap channel compensated estimation mode.
  • the UE capability report may be based on whether or not the UE 305 supports the features discussed with reference to receiver 200.
  • the FMCW capability report may carry or otherwise convey an indication timing information associated with such CSI reporting.
  • the UE capability report may indicate timing gap information associated with a period in the time domain that it takes the UE 305 to perform the channel estimation according to the per-tap channel estimation mode and report the results in the feedback message (e.g., in a CSI report) to the network entity 310.
  • the per-tap channel estimation mode may improve the channel estimation accuracy, but with a small increase in complexity. This increase may introduce additional processing time that it takes the UE 305 to perform the channel estimation procedure according to the per-tap channel estimation mode (e.g., as compared to the non-per-tap channel compensated estimation mode) , which may delay the CSI report.
  • the timing gap capability report may provide an indication of such timing gap for the UE 305 performing the per-tap and non-per-tap channel compensated estimation procedure (s) and reporting the results to the network entity 310.
  • the network entity 310 may transmit or otherwise provide (and the UE 305 may receive or otherwise obtain) a first message indicating FMCW waveform parameter (s) for the FMCW reference signal.
  • the parameter (s) may be transmitted in a first message that identifies, for the UE 305, the frequency resources, time resources, spatial resources, and the like, as well as various configuration information (such as transmit power) that will be used to transmit the FMCW reference signal.
  • the parameter (s) may identify, for the UE 305, whether the FMCW reference signal will be a single port FMCW reference signal or a multi-port FMCW reference signal.
  • the network entity 310 may transmit or otherwise provide (and the UE 305 may receive or otherwise obtain) an indication that the UE 305 is to apply the per-tap channel estimation mode (e.g., a FMCW channel compensation scheme) for the channel estimation using the FMCW reference signal.
  • the indication may be in a second message or in the first message (e.g., the message identifying the FMCW reference signal parameters) , such as in a DCI, MAC-CE, and/or RRC message.
  • the second message may optionally indicate a threshold for the channel delay spread for the non-per-tap channel compensated estimation mode and/or a threshold for the channel delay spread for the per-tap channel estimation mode. That is, in some examples the second message may carry or otherwise convey bit (s) , field (s) , and/or parameter (s) that serve (implicitly or explicitly) to indicate that the UE 305 is to begin compensating for the per-tap channel error term during channel estimations using the FMCW reference signal. One example of this may include the indication of the channel delay thresholds being indicated in the FMCW parameter (s) .
  • This may signal to the UE 305 that, when the channel delay spread reaches the threshold, that means that the network entity 310 is requesting the UE 305 to begin compensating for the per-tap error term in its CSI report.
  • This may enable the network to allow the UE 305 to perform and report FMCW reference signal based channel estimations using the non-per-tap channel compensated estimation mode when the channel delay is low (e.g., below the threshold) and to switch to the per-tap channel estimation mode when the channel delay increases (e.g., satisfies the threshold) . This may optimize efficiency in CSI reporting accuracy and the processing load of the UE 305.
  • the network entity 310 may transmit or otherwise provide (and the UE 305 may receive or otherwise obtain) the FMCW reference signal to the UE 305 according to the FMCW parameter (s) .
  • the network entity 310 may employ a VCO to generate the FMCW reference signal that is transmitted from the network entity 310 over the wireless channel.
  • the UE 305 may begin performing the channel estimation procedure using the FMCW reference signal and according to the per-tap channel estimation mode. For example, the UE 305 may monitor the resources indicated in the FMCW parameter (s) to detect the FMCW reference signal. The UE 305 may perform the channel estimation by removing the per-tap error term from the FMCW reference signal according to the per-tap channel estimation mode, such as is described with reference to receiver 200.
  • the network entity 310 may transmit or otherwise provide (and the UE 305 may receive or otherwise obtain) a message to trigger the UE 305 to transmit its CSI report (e.g., feedback message) indicating the results of the FMCW based channel estimation procedure using the per-tap channel estimation mode.
  • the trigger message may be transmitted in a DCI, MAC-CE, and/or RRC message to the UE 305.
  • the trigger message may carry or otherwise indicate resources to be used for providing the CSI report.
  • the resources to be used for providing the CSI report may be provided as part of the FMCW parameter (s) indicated in the first message and the trigger message may simply carry or convey a flag or bit that is set to a value that indicates the network entity 310 is requesting the CSI report from the UE 305.
  • the UE 305 may transmit or otherwise provide (and the network entity 310 may receive or otherwise obtain) the feedback message (e.g., the channel feedback message, such as a CSI report) based on the trigger message.
  • the channel feedback report (e.g., CSI report) may carry or otherwise convey an indication of the results (e.g., reference signal receive power (RSRP) , signal-to-interference-plus-noise (SINR) , and the like) for the FMCW reference signal based channel estimation according to the information indicated in the trigger message and/or in the first message carrying the FMCW parameter (s) .
  • RSRP reference signal receive power
  • SINR signal-to-interference-plus-noise
  • the UE 305 and the network entity 310 may perform subsequent communications (e.g., data transmissions) based at least in part on the CSI report.
  • the indication of the channel conditions carried in the CSI report may be used when making various scheduling and/or allocation determinations by the UE 305 and the network entity 310 to improve the reliability of the subsequent communications.
  • FIG. 4 illustrates an example of a method 400 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • Method 400 may implement aspects of wireless communications system 100 and/or receiver 200. Aspects of the method 400 may be implemented at and/or implemented by a UE 405 and/or a network entity 410, which may be examples of the corresponding devices described herein. In some aspects, the UE 405 may be configured or otherwise support the features discussed with reference to receiver 200.
  • Method 400 illustrates a non-limiting example of switching between the per-tap channel estimation mode and a non-per-tap channel compensated estimation mode. That is, method 400 illustrates an example where the network entity 310 may indicate to the UE 405 that it is to compensate for the per-tap error term in its CSI report (e.g., in its channel feedback message) . In some examples, method 400 illustrates a non-limiting example where the network entity 410 configures a first threshold (TH1) for the channel delay spread and a second threshold (TH2) for the port number, where the UE 405 autonomously determines whether to compensate for the per-tap channel error term in its CIS report.
  • TH1 first threshold
  • TH2 second threshold
  • the UE 405 may transmit or otherwise provide (and the network entity 410 may receive or otherwise obtain) a UE capability report.
  • the UE capability report may be transmitted in a message carried or otherwise conveyed in DCI, MAC-CE and/or RRC signaling.
  • the UE capability report may be a dynamic indication and/or a semi-persistent indication.
  • the UE capability report may indicate, identify, or otherwise provide information associated with the capabilities of the UE 405, such as supported operating frequencies, timing information, power information, and more.
  • the UE capability report may be an FMCW capability report that indicates whether the UE 405 supports or is otherwise capable of performing channel estimation on a per-tap basis using the FMCW reference signal according to the per-tap channel estimation mode and/or according to a non-per-tap channel compensated estimation mode.
  • the UE capability report may be based on whether or not the UE 405 supports the features discussed with reference to receiver 200.
  • the FMCW capability report may carry or otherwise convey an indication timing information associated with such CSI reporting.
  • the UE capability report may indicate timing gap information associated with a period in the time domain that it takes the UE 405 to perform the channel estimation according to the per-tap channel estimation mode and report the results in the feedback message (e.g., in a CSI report) to the network entity 410.
  • the per-tap channel estimation mode may improve the channel estimation accuracy, but with a small increase in complexity. This increase may introduce additional processing time that it takes the UE 405 to perform the channel estimation procedure according to the per-tap channel estimation mode (e.g., as compared to the non-per-tap channel compensated estimation mode) , which may delay the CSI report.
  • the timing gap capability report may provide an indication of such timing gap for the UE 405 performing the per-tap and non-per-tap channel compensated estimation procedure (s) and reporting the results to the network entity 410.
  • the network entity 410 may transmit or otherwise provide (and the UE 305 may receive or otherwise obtain) a first message indicating FMCW waveform parameter (s) for the FMCW reference signal.
  • the parameter (s) may be transmitted in a first message that identifies, for the UE 405, the frequency resources, time resources, spatial resources, and the like, as well as various configuration information (such as transmit power) that will be used to transmit the FMCW reference signal.
  • the parameter (s) may identify, for the UE 405, whether the FMCW reference signal will be a single port FMCW reference signal or a multi-port FMCW reference signal.
  • the network entity 310 may transmit or otherwise provide (and the UE 305 may receive or otherwise obtain) an indication that the UE 305 is to apply the per-tap channel estimation mode for the channel estimation using the FMCW reference signal.
  • the indication may be in a second message or in the first message (e.g., the message identifying the FMCW reference signal parameters) , such as in a DCI, MAC-CE, and/or RRC message.
  • the second message may indicate a threshold for the channel delay spread (e.g., TH1) for the non-per-tap channel compensated estimation mode and/or a threshold for the channel delay spread for the per-tap channel estimation mode. That is, in some examples the second message may carry or otherwise convey bit (s) , field (s) , and/or parameter (s) that serve (implicitly or explicitly) to indicate that the UE 405 is to begin compensating for the per-tap channel error term during channel estimations using the FMCW reference signal if the channel delay satisfies the channel delay threshold.
  • bit (s) e.g., TH1
  • the second message may carry or otherwise convey bit (s) , field (s) , and/or parameter (s) that serve (implicitly or explicitly) to indicate that the UE 405 is to begin compensating for the per-tap channel error term during channel estimations using the FMCW reference signal if the channel delay satisfies the channel delay threshold.
  • This may include the indication of the channel delay
  • This may signal to the UE 405 that, when the channel delay spread reaches the threshold, that means that the UE 405 to begin compensating for the per-tap error term in its CSI report.
  • This may enable the network to allow the UE 405 to perform and report FMCW reference signal based channel estimations using the non-per-tap channel compensated estimation mode when the channel delay is low (e.g., below the threshold) and to switch to the per-tap channel estimation mode when the channel delay increases (e.g., satisfies the threshold) . This may optimize efficiency in CSI reporting accuracy and the processing load of the UE 405.
  • the second message may indicate a threshold for the port number (e.g., TH2) for the non-per-tap channel compensated estimation mode and/or a threshold for the channel delay spread for the per-tap channel estimation mode. That is, in some examples the second message may carry or otherwise convey bit (s) , field (s) , and/or parameter (s) that serve (implicitly or explicitly) to indicate that the UE 405 is to begin compensating for the per-tap channel error term during channel estimations using the FMCW reference signal if the number of ports (e.g., how many ports are in the set of ports) satisfies the port threshold.
  • a threshold for the port number e.g., TH2
  • the second message may carry or otherwise convey bit (s) , field (s) , and/or parameter (s) that serve (implicitly or explicitly) to indicate that the UE 405 is to begin compensating for the per-tap channel error term during channel estimations using the FMCW reference signal if the number of ports (e
  • This may signal to the UE 405 that, when the number of ports associated with the FMCW reference signal reaches the port number threshold, that means that the UE 405 to begin compensating for the per-tap error term in its CSI report.
  • This may enable the network to allow the UE 405 to perform and report FMCW reference signal based channel estimations using the non-per-tap channel compensated estimation mode when the number of ports of the FMCW reference signal is low (e.g., below the threshold) and to switch to the per-tap channel estimation mode when the number of ports increases (e.g., satisfies the threshold) . This may again optimize efficiency in CSI reporting accuracy and the processing load of the UE 405.
  • certain ports (e.g., a first subset of ports in the set of ports) associated with the FMCW reference signal may be used for channel estimation according to the per-tap channel estimation mode while other ports (e.g., a second subset of ports in the set of ports) associated with the FMCW reference signal may be used for channel estimation according to the non-per-tap channel compensated estimation mode. This may reduce the processing load of the UE 405 while maintain CSI reporting accuracy.
  • the network entity 410 may transmit or otherwise provide (and the UE 405 may receive or otherwise obtain) the FMCW reference signal to the UE 405 according to the FMCW parameter (s) .
  • the network entity 410 may employ a VCO to generate the FMCW reference signal that is transmitted from the network entity 410 over the wireless channel.
  • the UE 405 may compare the FMCW reference signal to the threshold (s) (e.g., to TH1 and/or TH2) to determine whether to perform the FMCW reference signal based channel estimation procedure according to the per-tap channel estimation mode or the non-per-tap channel compensated estimation mode. For example, if the channel delay associated with the FMCW reference signal satisfies the channel delay threshold (TH1) , the UE 405 may switch or otherwise transition from the non-per-tap channel compensated estimation mode to the per-tap channel estimation mode.
  • the threshold e.g., to TH1 and/or TH2
  • the UE 405 may switch or otherwise transition from the non-per-tap channel compensated estimation mode to the per-tap channel estimation mode. In some examples, the UE 405 may switch to the per-tap channel estimation mode when either of TH1 or TH2 are satisfied and/or when both TH1 and TH2 are satisfied.
  • the UE 405 may begin performing the channel estimation procedure using the FMCW reference signal and according to the per-tap channel estimation mode. For example, the UE 405 may monitor the resources indicated in the FMCW parameter (s) to detect the FMCW reference signal. The UE 405 may perform the channel estimation by removing the per-tap error term from the FMCW reference signal according to the per-tap channel estimation mode, such as is described with reference to receiver 200.
  • the network entity 410 may transmit or otherwise provide (and the UE 405 may receive or otherwise obtain) a message to trigger the UE 405 to transmit its CSI report (e.g., feedback message) indicating the results of the FMCW based channel estimation procedure using the per-tap channel estimation mode.
  • the trigger message may be transmitted in a DCI, MAC-CE, and/or RRC message to the UE 405.
  • the trigger message may carry or otherwise indicate resources to be used for providing the CSI report.
  • the resources to be used for providing the CSI report may be provided as part of the FMCW parameter (s) indicated in the first message and the trigger message may simply carry or convey a flag or bit that is set to a value that indicates the network entity 410 is requesting the CSI report from the UE 405.
  • the UE 405 may transmit or otherwise provide (and the network entity 410 may receive or otherwise obtain) the feedback message (e.g., the channel feedback message, such as a CSI report) based on the trigger message.
  • the channel feedback report e.g., CSI report
  • the channel feedback report may carry or otherwise convey an indication of the results (e.g., RSRP, SINR, and the like) for the FMCW reference signal based channel estimation according to the information indicated in the trigger message and/or in the first message carrying the FMCW parameter (s) .
  • the UE 405 and the network entity 410 may perform subsequent communications (e.g., data transmissions) based at least in part on the CSI report.
  • the indication of the channel conditions carried in the CSI report may be used when making various scheduling and/or allocation determinations by the UE 405 and the network entity 410 to improve the reliability of the subsequent communications.
  • FIG. 5 illustrates an example of a timing configuration 500 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • Timing configuration 500 may implement aspects of wireless communications system 100, receiver 200, and/or aspects of method 300 and/or method 400. Aspects of timing configuration 500 may be implemented at or implemented by a UE and/or network entity, which may be examples of the corresponding devices described herein.
  • Timing configuration 500 illustrates a non-limiting example of timing gaps between an FMCW reference signal transmission and the corresponding CSI report using the non-per-tap channel compensated estimation mode and the per-tap channel estimation mode.
  • the UE may transmit a UE capability report to the network entity identifying or otherwise indicating support for performing the FMCW reference signal based channel estimation according to the per-tap channel estimation mode and/or the non-per-tap channel compensated estimation mode.
  • the network entity may transmit an indication of FMCW parameter (s) to the UE (e.g., in a first message) and an indication of the per-tap channel estimation mode (e.g., in a second message) .
  • the UE may perform the channel estimation procedure using the FMCW reference signal according to the FMCW parameter (s) and report the results of the procedure to the network entity in a CSI report (e.g., in a channel feedback message) .
  • Performing the channel estimation procedure may take a different amount of time (e.g., based on the associated processing by the UE) depending on whether the procedure uses the non-per-tap channel compensated estimation mode or the per-tap channel estimation mode.
  • Timing configuration 500 illustrates an example of such timing gaps reported by the UE in its UE capability report.
  • the UE may be indicated to report a minimum timing gap 1 (TG1) , which may be considered a first timing gap, that is used for the non-per-tap-compensation FMCW-based wideband (frequency domain) channel estimation between the FMCW reception and the associated CSI report (e.g., CSI report 510) .
  • the first timing gap TG1 may indicate to the network the timing gap associated with performing the channel estimation and reporting on a non-per-tap basis.
  • the UE may receive the FMCW reference signal 505, perform the channel estimation according to the non-per-tap channel compensated estimation mode, and report the results of the procedure in the CSI report 510.
  • the UE may be indicated to report a minimum timing gap 2 (TG2) , which may be considered a second timing gap, that is used for the per-tap-compensation FMCW-based wideband (frequency domain) channel estimation between the FMCW reception and the associated CSI report (e.g., CSI report 520) .
  • the second timing gap TG2 may indicate to the network the timing gap associated with performing the channel estimation and reporting on a per-tap basis.
  • the UE may receive the FMCW reference signal 515, perform the channel estimation according to the per-tap channel estimation mode, and report the results of the procedure in the CSI report 520.
  • TG2 may be greater than or equal to TG1.
  • FIG. 6 illustrates a block diagram 600 of a device 605 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • the device 605 may be an example of aspects of a UE 115 as described herein.
  • the device 605 may include a receiver 610, a transmitter 615, and a communications manager 620.
  • the device 605 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 610 may provide a means 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 related to per-tap channel estimation for a FMCW reference signal) . Information may be passed on to other components of the device 605.
  • the receiver 610 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 615 may provide a means for transmitting signals generated by other components of the device 605.
  • the transmitter 615 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 related to per-tap channel estimation for a FMCW reference signal) .
  • the transmitter 615 may be co-located with a receiver 610 in a transceiver module.
  • the transmitter 615 may utilize a single antenna or a set of multiple antennas.
  • the communications manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of per-tap channel estimation for a FMCW reference signal as described herein.
  • the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
  • the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • DSP digital signal processor
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory) .
  • the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure) .
  • code e.g., as communications management software or firmware
  • the communications manager 620 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both.
  • the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 620 may support wireless communications at a UE in accordance with examples as disclosed herein.
  • the communications manager 620 may be configured as or otherwise support a means for receiving a first message indicating one or more FMCW waveform parameters for a FMCW reference signal.
  • the communications manager 620 may be configured as or otherwise support a means for receiving a second message indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the communications manager 620 may be configured as or otherwise support a means for performing the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode.
  • the communications manager 620 may be configured as or otherwise support a means for transmitting a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the device 605 may support techniques for FMCW reference signal based channel estimation and reporting on a per-tap basis (and in some situations on a per-tap, per-port basis) to compensate for the per-tap error term associated with non-per-tap based channel compensated estimation and reporting using the FMCW reference signal.
  • FIG. 7 illustrates a block diagram 700 of a device 705 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • the device 705 may be an example of aspects of a device 605 or a UE 115 as described herein.
  • the device 705 may include a receiver 710, a transmitter 715, and a communications manager 720.
  • the device 705 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 710 may provide a means 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 related to per-tap channel estimation for a FMCW reference signal) . Information may be passed on to other components of the device 705.
  • the receiver 710 may utilize a single antenna or a set of multiple antennas.
  • the transmitter 715 may provide a means for transmitting signals generated by other components of the device 705.
  • the transmitter 715 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 related to per-tap channel estimation for a FMCW reference signal) .
  • the transmitter 715 may be co-located with a receiver 710 in a transceiver module.
  • the transmitter 715 may utilize a single antenna or a set of multiple antennas.
  • the device 705, or various components thereof may be an example of means for performing various aspects of per-tap channel estimation for a FMCW reference signal as described herein.
  • the communications manager 720 may include an FMCW parameter manager 725, a per-tap estimation manager 730, an estimation manager 735, a feedback manager 740, or any combination thereof.
  • the communications manager 720 may be an example of aspects of a communications manager 620 as described herein.
  • the communications manager 720, or various components thereof may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 710, the transmitter 715, or both.
  • the communications manager 720 may receive information from the receiver 710, send information to the transmitter 715, or be integrated in combination with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 720 may support wireless communications at a UE in accordance with examples as disclosed herein.
  • the FMCW parameter manager 725 may be configured as or otherwise support a means for receiving a first message indicating one or more FMCW waveform parameters for a FMCW reference signal.
  • the per-tap estimation manager 730 may be configured as or otherwise support a means for receiving a second message indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the estimation manager 735 may be configured as or otherwise support a means for performing the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode.
  • the feedback manager 740 may be configured as or otherwise support a means for transmitting a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • FIG. 8 illustrates a block diagram 800 of a communications manager 820 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • the communications manager 820 may be an example of aspects of a communications manager 620, a communications manager 720, or both, as described herein.
  • the communications manager 820, or various components thereof, may be an example of means for performing various aspects of per-tap channel estimation for a FMCW reference signal as described herein.
  • the communications manager 820 may include an FMCW parameter manager 825, a per-tap estimation manager 830, an estimation manager 835, a feedback manager 840, a compensation manager 845, a port manager 850, a per-tap estimation activation manager 855, a threshold manager 860, a capability manager 865, or any combination thereof.
  • Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the communications manager 820 may support wireless communications at a UE in accordance with examples as disclosed herein.
  • the FMCW parameter manager 825 may be configured as or otherwise support a means for receiving a first message indicating one or more FMCW waveform parameters for a FMCW reference signal.
  • the per-tap estimation manager 830 may be configured as or otherwise support a means for receiving a second message indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the estimation manager 835 may be configured as or otherwise support a means for performing the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode.
  • the feedback manager 840 may be configured as or otherwise support a means for transmitting a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the compensation manager 845 may be configured as or otherwise support a means for compensating for a channel delay separately for each tap based on a channel delay estimation to obtain compensated taps, where the channel estimation procedure is performed based on the compensated taps.
  • the compensation manager 845 may be configured as or otherwise support a means for performing an inverse fast-Fourier transform function on the FMCW reference signal to identify each tap in the set of taps from the FMCW reference signal. In some examples, the compensation manager 845 may be configured as or otherwise support a means for performing a fast Fourier transform function on a combination of the compensated taps to obtain a compensated FMCW reference signal.
  • the compensation manager 845 may be configured as or otherwise support a means for estimating the channel delay of each tap in the set of taps. In some examples, to support compensating for the channel delay, the compensation manager 845 may be configured as or otherwise support a means for compensating for the channel delay of each tap to obtain the compensated taps.
  • the port manager 850 may be configured as or otherwise support a means for identifying each port in a set of ports associated with the FMCW reference signal. In some examples, to support performing the channel estimation procedure according to the per-tap channel estimation mode, the port manager 850 may be configured as or otherwise support a means for performing, on a per-port basis for each port in the set of ports, channel delay estimation and compensation for each tap in the set of taps.
  • the per-tap estimation activation manager 855 may be configured as or otherwise support a means for receiving, via the second message, an indication that the UE is to apply the per-tap channel estimation mode for channel estimation using the FMCW reference signal.
  • the indication may be received in an RRC message, a MAC-CE, or a DCI.
  • the threshold manager 860 may be configured as or otherwise support a means for receiving an indication of a channel delay threshold. In some examples, to support receiving the second message indicating the per-tap channel estimation mode, the threshold manager 860 may be configured as or otherwise support a means for transitioning to the per-tap channel estimation mode based on a channel delay associated with the FMCW reference signal satisfying the channel delay threshold. In some examples, the indication may be received in an RRC message, a MAC-CE, or a DCI.
  • the threshold manager 860 may be configured as or otherwise support a means for receiving an indication of a port number threshold. In some examples, to support receiving the second message indicating the per-tap channel estimation mode, the threshold manager 860 may be configured as or otherwise support a means for transitioning to the per-tap channel estimation mode based on a port number associated with the FMCW reference signal satisfying the port number threshold. In some examples, the indication may be received in an RRC message, a MAC-CE, or a DCI.
  • the capability manager 865 may be configured as or otherwise support a means for transmitting a UE capability message indicating a first timing gap associated with performing channel estimation and reporting on a non-per-tap basis and a second timing gap associated with performing channel estimation and reporting on a per-tap basis according to the per-tap channel estimation mode, where the indication of the per-tap channel estimation mode is based on the UE capability message.
  • FIG. 9 illustrates a diagram of a system 900 including a device 905 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • the device 905 may be an example of or include the components of a device 605, a device 705, or a UE 115 as described herein.
  • the device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof.
  • the device 905 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 920, an input/output (I/O) controller 910, a transceiver 915, an antenna 925, a memory 930, code 935, and a processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 945) .
  • a bus 945 e.g., a bus 945
  • the I/O controller 910 may manage input and output signals for the device 905.
  • the I/O controller 910 may also manage peripherals not integrated into the device 905.
  • the I/O controller 910 may represent a physical connection or port to an external peripheral.
  • the I/O controller 910 may utilize an operating system such as or another known operating system.
  • the I/O controller 910 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 910 may be implemented as part of a processor, such as the processor 940.
  • a user may interact with the device 905 via the I/O controller 910 or via hardware components controlled by the I/O controller 910.
  • the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 915 may communicate bi-directionally, via the one or more antennas 925, wired, or wireless links as described herein.
  • the transceiver 915 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 915 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 925 for transmission, and to demodulate packets received from the one or more antennas 925.
  • the transceiver 915 may be an example of a transmitter 615, a transmitter 715, a receiver 610, a receiver 710, or any combination thereof or component thereof, as described herein.
  • the memory 930 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform various functions described herein.
  • the code 935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code 935 may not be directly executable by the processor 940 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 930 may contain, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 940 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 940.
  • the processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting per-tap channel estimation for a FMCW reference signal) .
  • the device 905 or a component of the device 905 may include a processor 940 and memory 930 coupled with or to the processor 940, the processor 940 and memory 930 configured to perform various functions described herein.
  • the communications manager 920 may support wireless communications at a UE in accordance with examples as disclosed herein.
  • the communications manager 920 may be configured as or otherwise support a means for receiving a first message indicating one or more FMCW waveform parameters for a FMCW reference signal.
  • the communications manager 920 may be configured as or otherwise support a means for receiving a second message indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the communications manager 920 may be configured as or otherwise support a means for performing the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode.
  • the communications manager 920 may be configured as or otherwise support a means for transmitting a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the device 905 may support techniques for FMCW reference signal based channel estimation and reporting on a per-tap basis (and in some situations on a per-tap, per-port basis) to compensate for the per-tap error term associated with non-per-tap based channel compensated estimation and reporting using the FMCW reference signal.
  • the communications manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 915, the one or more antennas 925, or any combination thereof.
  • the communications manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 920 may be supported by or performed by the processor 940, the memory 930, the code 935, or any combination thereof.
  • the code 935 may include instructions executable by the processor 940 to cause the device 905 to perform various aspects of per-tap channel estimation for a FMCW reference signal as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.
  • FIG. 10 illustrates a block diagram 1000 of a device 1005 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • the device 1005 may be an example of aspects of a network entity 105 as described herein.
  • the device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020.
  • the device 1005 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1010 may provide a means for obtaining (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) .
  • Information may be passed on to other components of the device 1005.
  • the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1015 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1005.
  • the transmitter 1015 may output 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 transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include or be coupled with a modem.
  • the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or various components thereof may be examples of means for performing various aspects of per-tap channel estimation for a FMCW reference signal as described herein.
  • the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
  • the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory) .
  • the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure) .
  • code e.g., as communications management software or firmware
  • the functions of the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a
  • the communications manager 1020 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both.
  • the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 1020 may support wireless communications at a network entity in accordance with examples as disclosed herein.
  • the communications manager 1020 may be configured as or otherwise support a means for transmitting, to a UE, a first message indicating one or more FMCW waveform parameters for a FMCW reference signal.
  • the communications manager 1020 may be configured as or otherwise support a means for transmitting a second message indicating a per-tap channel estimation mode associated with the UE performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the communications manager 1020 may be configured as or otherwise support a means for receiving, from the UE, a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the device 1005 may support techniques for FMCW reference signal based channel estimation and reporting on a per-tap basis (and in some situations on a per-tap, per-port basis) to compensate for the per-tap error term associated with non-per-tap based channel compensated estimation and reporting using the FMCW reference signal.
  • FIG. 11 illustrates a block diagram 1100 of a device 1105 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • the device 1105 may be an example of aspects of a device 1005 or a network entity 105 as described herein.
  • the device 1105 may include a receiver 1110, a transmitter 1115, and a communications manager 1120.
  • the device 1105 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 1110 may provide a means for obtaining (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) .
  • Information may be passed on to other components of the device 1105.
  • the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1115 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1105.
  • the transmitter 1115 may output 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 transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.
  • the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include or be coupled with a modem.
  • the device 1105 may be an example of means for performing various aspects of per-tap channel estimation for a FMCW reference signal as described herein.
  • the communications manager 1120 may include an FMCW parameter manager 1125, a per-tap estimation manager 1130, a feedback manager 1135, or any combination thereof.
  • the communications manager 1120 may be an example of aspects of a communications manager 1020 as described herein.
  • the communications manager 1120, or various components thereof may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1110, the transmitter 1115, or both.
  • the communications manager 1120 may receive information from the receiver 1110, send information to the transmitter 1115, or be integrated in combination with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.
  • the communications manager 1120 may support wireless communications at a network entity in accordance with examples as disclosed herein.
  • the FMCW parameter manager 1125 may be configured as or otherwise support a means for transmitting, to a UE, a first message indicating one or more FMCW waveform parameters for a FMCW reference signal.
  • the per-tap estimation manager 1130 may be configured as or otherwise support a means for transmitting a second message indicating a per-tap channel estimation mode associated with the UE performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the feedback manager 1135 may be configured as or otherwise support a means for receiving, from the UE, a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • FIG. 12 illustrates a block diagram 1200 of a communications manager 1220 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • the communications manager 1220 may be an example of aspects of a communications manager 1020, a communications manager 1120, or both, as described herein.
  • the communications manager 1220, or various components thereof, may be an example of means for performing various aspects of per-tap channel estimation for a FMCW reference signal as described herein.
  • the communications manager 1220 may include an FMCW parameter manager 1225, a per-tap estimation manager 1230, a feedback manager 1235, a per-tap estimation activation manager 1240, a threshold manager 1245, a port manager 1250, a capability manager 1255, or any combination thereof.
  • Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) which may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105) , or any combination thereof.
  • the communications manager 1220 may support wireless communications at a network entity in accordance with examples as disclosed herein.
  • the FMCW parameter manager 1225 may be configured as or otherwise support a means for transmitting, to a UE, a first message indicating one or more FMCW waveform parameters for a FMCW reference signal.
  • the per-tap estimation manager 1230 may be configured as or otherwise support a means for transmitting a second message indicating a per-tap channel estimation mode associated with the UE performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the feedback manager 1235 may be configured as or otherwise support a means for receiving, from the UE, a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the per-tap estimation activation manager 1240 may be configured as or otherwise support a means for transmitting, via the second message, an indication that the UE is to apply the per-tap channel estimation mode for channel estimation using the FMCW reference signal.
  • the indication may be transmitted in an RRC message, a MAC-CE, or a DCI.
  • the threshold manager 1245 may be configured as or otherwise support a means for transmitting an indication of a channel delay threshold, where the UE transitions to the per-tap channel estimation mode based on a channel delay associated with the FMCW reference signal satisfying the channel delay threshold.
  • the indication may be transmitted in an RRC message, a MAC-CE, or a DCI.
  • the port manager 1250 may be configured as or otherwise support a means for transmitting an indication of a port number threshold, where the UE transitions to the per-tap channel estimation mode based on a port number associated with the FMCW reference signal satisfying the port number threshold.
  • the indication may be transmitted in an RRC message, a MAC-CE, or a DCI.
  • the capability manager 1255 may be configured as or otherwise support a means for receiving a UE capability message indicating a first timing gap associated with performing channel estimation and reporting on a non-per-tap basis and a second timing gap associated with performing channel estimation and reporting on a per-tap basis according to the per-tap channel estimation mode, where the indication of the per-tap channel estimation mode is based on the UE capability message.
  • FIG. 13 illustrates a diagram of a system 1300 including a device 1305 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • the device 1305 may be an example of or include the components of a device 1005, a device 1105, or a network entity 105 as described herein.
  • the device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof.
  • the device 1305 may include components that support outputting and obtaining communications, such as a communications manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, code 1330, and a processor 1335. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1340) .
  • a communications manager 1320 e.g., operatively, communicatively, functionally, electronically, electrically
  • buses e.g., a bus 1340
  • the transceiver 1310 may support bi-directional communications via wired links, wireless links, or both as described herein.
  • the transceiver 1310 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the device 1305 may include one or more antennas 1315, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently) .
  • the transceiver 1310 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1315, by a wired transmitter) , to receive modulated signals (e.g., from one or more antennas 1315, from a wired receiver) , and to demodulate signals.
  • the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1315 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1315 that are configured to support various transmitting or outputting operations, or a combination thereof.
  • the transceiver 1310 may include or be configured for coupling with one or more processors or memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof.
  • the transceiver 1310, or the transceiver 1310 and the one or more antennas 1315, or the transceiver 1310 and the one or more antennas 1315 and one or more processors or memory components may be included in a chip or chip assembly that is installed in the device 1305.
  • the transceiver may be operable to support communications via one or more communications links (e.g., a communication link 125, a backhaul communication link 120, a midhaul communication link 162, a fronthaul communication link 168) .
  • one or more communications links e.g., a communication link 125, a backhaul communication link 120, a midhaul communication link 162, a fronthaul communication link 168 .
  • the memory 1325 may include RAM and ROM.
  • the memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by the processor 1335, cause the device 1305 to perform various functions described herein.
  • the code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code 1330 may not be directly executable by the processor 1335 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 1325 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • the processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, a discrete hardware component, or any combination thereof) .
  • the processor 1335 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1335.
  • the processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1325) to cause the device 1305 to perform various functions (e.g., functions or tasks supporting per-tap channel estimation for a FMCW reference signal) .
  • the device 1305 or a component of the device 1305 may include a processor 1335 and memory 1325 coupled with the processor 1335, the processor 1335 and memory 1325 configured to perform various functions described herein.
  • the processor 1335 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1330) to perform the functions of the device 1305.
  • the processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1305 (such as within the memory 1325) .
  • the processor 1335 may be a component of a processing system.
  • a processing system may generally refer to a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs (which may be passed to other systems or components of, for example, the device 1305) .
  • a processing system of the device 1305 may refer to a system including the various other components or subcomponents of the device 1305, such as the processor 1335, or the transceiver 1310, or the communications manager 1320, or other components or combinations of components of the device 1305.
  • the processing system of the device 1305 may interface with other components of the device 1305, and may process information received from other components (such as inputs or signals) or output information to other components.
  • a chip or modem of the device 1305 may include a processing system and one or more interfaces to output information, or to obtain information, or both.
  • the one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or a same interface configured to output information and to obtain information, among other implementations.
  • the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, such that the device 1305 may transmit information output from the chip or modem.
  • the one or more interfaces may refer to an interface between the processing system of the chip or modem and a receiver, such that the device 1305 may obtain information or signal inputs, and the information may be passed to the processing system.
  • a first interface also may obtain information or signal inputs
  • a second interface also may output information or signal outputs.
  • a bus 1340 may support communications of (e.g., within) a protocol layer of a protocol stack.
  • a bus 1340 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack) , which may include communications performed within a component of the device 1305, or between different components of the device 1305 that may be co-located or located in different locations (e.g., where the device 1305 may refer to a system in which one or more of the communications manager 1320, the transceiver 1310, the memory 1325, the code 1330, and the processor 1335 may be located in one of the different components or divided between different components) .
  • the communications manager 1320 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links) .
  • the communications manager 1320 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the communications manager 1320 may manage communications with other network entities 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other network entities 105.
  • the communications manager 1320 may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities 105.
  • the communications manager 1320 may support wireless communications at a network entity in accordance with examples as disclosed herein.
  • the communications manager 1320 may be configured as or otherwise support a means for transmitting, to a UE, a first message indicating one or more FMCW waveform parameters for a FMCW reference signal.
  • the communications manager 1320 may be configured as or otherwise support a means for transmitting a second message indicating a per-tap channel estimation mode associated with the UE performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the communications manager 1320 may be configured as or otherwise support a means for receiving, from the UE, a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the device 1305 may support techniques for FMCW reference signal based channel estimation and reporting on a per-tap basis (and in some situations on a per-tap, per-port basis) to compensate for the per-tap error term associated with non-per-tap based channel compensated estimation and reporting using the FMCW reference signal.
  • the communications manager 1320 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1310, the one or more antennas 1315 (e.g., where applicable) , or any combination thereof.
  • the communications manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1320 may be supported by or performed by the transceiver 1310, the processor 1335, the memory 1325, the code 1330, or any combination thereof.
  • the code 1330 may include instructions executable by the processor 1335 to cause the device 1305 to perform various aspects of per-tap channel estimation for a FMCW reference signal as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.
  • FIG. 14 illustrates a flowchart showing a method 1400 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1400 may be implemented by a UE or its components as described herein.
  • the operations of the method 1400 may be performed by a UE 115 as described with reference to FIGs. 1 through 9.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a first message indicating one or more FMCW waveform parameters for a FMCW reference signal.
  • the operations of 1405 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by an FMCW parameter manager 825 as described with reference to FIG. 8.
  • the method may include receiving a second message indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the operations of 1410 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by a per-tap estimation manager 830 as described with reference to FIG. 8.
  • the method may include performing the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode.
  • the operations of 1415 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by an estimation manager 835 as described with reference to FIG. 8.
  • the method may include transmitting a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the operations of 1420 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed by a feedback manager 840 as described with reference to FIG. 8.
  • FIG. 15 illustrates a flowchart showing a method 1500 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1500 may be implemented by a UE or its components as described herein.
  • the operations of the method 1500 may be performed by a UE 115 as described with reference to FIGs. 1 through 9.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a first message indicating one or more FMCW waveform parameters for a FMCW reference signal.
  • the operations of 1505 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by an FMCW parameter manager 825 as described with reference to FIG. 8.
  • the method may include receiving a second message indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the operations of 1510 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a per-tap estimation manager 830 as described with reference to FIG. 8.
  • the method may include performing the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode.
  • the operations of 1515 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed by an estimation manager 835 as described with reference to FIG. 8.
  • the method may include compensating for a channel delay separately for each tap based on a channel delay estimation to obtain compensated taps, where the channel estimation procedure is performed based on the compensated taps.
  • the operations of 1520 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed by a compensation manager 845 as described with reference to FIG. 8.
  • the method may include transmitting a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the operations of 1525 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1525 may be performed by a feedback manager 840 as described with reference to FIG. 8.
  • FIG. 16 illustrates a flowchart showing a method 1600 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1600 may be implemented by a UE or its components as described herein.
  • the operations of the method 1600 may be performed by a UE 115 as described with reference to FIGs. 1 through 9.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a first message indicating one or more FMCW waveform parameters for a FMCW reference signal.
  • the operations of 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by an FMCW parameter manager 825 as described with reference to FIG. 8.
  • the method may include receiving a second message indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the operations of 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by a per-tap estimation manager 830 as described with reference to FIG. 8.
  • the method may include performing the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode.
  • the operations of 1615 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed by an estimation manager 835 as described with reference to FIG. 8.
  • the method may include identifying each port in a set of ports associated with the FMCW reference signal.
  • the operations of 1620 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed by a port manager 850 as described with reference to FIG. 8.
  • the method may include performing, on a per-port basis for each port in the set of ports, channel delay estimation and compensation for each tap in the set of taps.
  • the operations of 1625 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1625 may be performed by a port manager 850 as described with reference to FIG. 8.
  • the method may include transmitting a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the operations of 1630 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1630 may be performed by a feedback manager 840 as described with reference to FIG. 8.
  • FIG. 17 illustrates a flowchart showing a method 1700 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1700 may be implemented by a network entity or its components as described herein.
  • the operations of the method 1700 may be performed by a network entity as described with reference to FIGs. 1 through 5 and 10 through 13.
  • a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting, to a UE, a first message indicating one or more FMCW waveform parameters for a FMCW reference signal.
  • the operations of 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by an FMCW parameter manager 1225 as described with reference to FIG. 12.
  • the method may include transmitting a second message indicating a per-tap channel estimation mode associated with the UE performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the operations of 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a per-tap estimation manager 1230 as described with reference to FIG. 12.
  • the method may include receiving, from the UE, a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the operations of 1715 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by a feedback manager 1235 as described with reference to FIG. 12.
  • FIG. 18 illustrates a flowchart showing a method 1800 that supports per-tap channel estimation for a FMCW reference signal in accordance with one or more aspects of the present disclosure.
  • the operations of the method 1800 may be implemented by a network entity or its components as described herein.
  • the operations of the method 1800 may be performed by a network entity as described with reference to FIGs. 1 through 5 and 10 through 13.
  • a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting, to a UE, a first message indicating one or more FMCW waveform parameters for a FMCW reference signal.
  • the operations of 1805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed by an FMCW parameter manager 1225 as described with reference to FIG. 12.
  • the method may include transmitting a second message indicating a per-tap channel estimation mode associated with the UE performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal.
  • the operations of 1810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by a per-tap estimation manager 1230 as described with reference to FIG. 12.
  • the method may include receiving, from the UE, a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • the operations of 1815 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed by a feedback manager 1235 as described with reference to FIG. 12.
  • the method may include receiving a UE capability message indicating a first timing gap associated with performing channel estimation and reporting on a non-per-tap basis and a second timing gap associated with performing channel estimation and reporting on a per-tap basis according to the per-tap channel estimation mode, where the indication of the per-tap channel estimation mode is based on the UE capability message.
  • the operations of 1820 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed by a capability manager 1255 as described with reference to FIG. 12.
  • a method for wireless communications at a UE comprising: receiving a first message indicating one or more FMCW waveform parameters for a FMCW reference signal; receiving a second message indicating a per-tap channel estimation mode associated with performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal; performing the channel estimation procedure using the FMCW reference signal according to the per-tap channel estimation mode; and transmitting a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • Aspect 2 The method of aspect 1, wherein performing the channel estimation procedure according to the per-tap channel estimation mode comprises: compensating for a channel delay separately for each tap based at least in part on a channel delay estimation to obtain compensated taps, wherein the channel estimation procedure is performed based at least in part on the compensated taps.
  • Aspect 3 The method of aspect 2, further comprising: performing an inverse fast-Fourier transform function on the FMCW reference signal to identify each tap in the set of taps from the FMCW reference signal; and performing a fast Fourier transform function on a combination of the compensated taps to obtain a compensated FMCW reference signal.
  • Aspect 4 The method of any of aspects 2 through 3, wherein compensating for the channel delay comprises: estimating the channel delay of each tap in the set of taps; and compensating for the channel delay of each tap to obtain the compensated taps.
  • Aspect 5 The method of any of aspects 1 through 4, wherein performing the channel estimation procedure according to the per-tap channel estimation mode comprises: identifying each port in a set of ports associated with the FMCW reference signal; and performing, on a per-port basis for each port in the set of ports, channel delay estimation and compensation for each tap in the set of taps.
  • Aspect 6 The method of any of aspects 1 through 5, wherein receiving the second message indicating the per-tap channel estimation mode comprises: receiving, via the second message, an indication that the UE is to apply the per-tap channel estimation mode for channel estimation using the FMCW reference signal.
  • Aspect 7 The method of aspect 6, wherein the second message comprises one or more of: an RRC message, a MAC-CE, or a DCI.
  • Aspect 8 The method of any of aspects 1 through 7, wherein receiving the second message indicating the per-tap channel estimation mode comprises: receiving an indication of a channel delay threshold; and transitioning to the per-tap channel estimation mode based at least in part on a channel delay associated with the FMCW reference signal satisfying the channel delay threshold.
  • Aspect 9 The method of aspect 8, wherein the indication of the channel delay threshold is received in one or more of an RRC message, a MAC-CE, or a DCI.
  • Aspect 10 The method of any of aspects 1 through 9, wherein receiving the second message indicating the per-tap channel estimation mode comprises: receiving an indication of a port number threshold; and transitioning to the per-tap channel estimation mode based at least in part on a port number associated with the FMCW reference signal satisfying the port number threshold.
  • Aspect 11 The method of aspect 10, wherein the indication of the port number threshold is received in one or more of an RRC message, a MAC-CE, or a DCI.
  • Aspect 12 The method of any of aspects 1 through 11, further comprising: transmitting a UE capability message indicating a first timing gap associated with performing channel estimation and reporting on a non-per-tap basis and a second timing gap associated with performing channel estimation and reporting on a per-tap basis according to the per-tap channel estimation mode, wherein the indication of the per-tap channel estimation mode is based at least in part on the UE capability message.
  • a method for wireless communications at a network entity comprising: transmitting, to a UE, a first message indicating one or more FMCW waveform parameters for a FMCW reference signal; transmitting a second message indicating a per-tap channel estimation mode associated with the UE performing a channel estimation procedure on a per-tap basis for each tap in a set of taps associated with the FMCW reference signal, each tap in the set of taps corresponding to a unique channel delay associated with the FMCW reference signal; and receiving, from the UE, a channel feedback message indicating a result of the channel estimation procedure using the FMCW reference signal.
  • Aspect 14 The method of aspect 13, wherein transmitting the second message indicating the per-tap channel estimation mode comprises: transmitting, via the second message, an indication that the UE is to apply the per-tap channel estimation mode for channel estimation using the FMCW reference signal.
  • Aspect 15 The method of aspect 14, wherein the second message comprises one or more of: an RRC message, a MAC-CE, or a DCI.
  • Aspect 16 The method of any of aspects 13 through 15, wherein transmitting the second message indicating the per-tap channel estimation mode comprises: transmitting an indication of a channel delay threshold, where the UE transitions to the per-tap channel estimation mode based at least in part on a channel delay associated with the FMCW reference signal satisfying the channel delay threshold.
  • Aspect 17 The method of aspect 16, wherein the indication of the channel delay threshold is transmitted in one or more of an RRC message, a MAC-CE, or a DCI.
  • Aspect 18 The method of any of aspects 13 through 17, wherein transmitting the second message indicating the per-tap channel estimation mode comprises: transmitting an indication of a port number threshold, wherein the UE transitions to the per-tap channel estimation mode based at least in part on a port number associated with the FMCW reference signal satisfying the port number threshold.
  • Aspect 19 The method of aspect 18, wherein the indication of the port number threshold is transmitted in one or more of an RRC message, a MAC-CE, or a DCI.
  • Aspect 20 The method of any of aspects 13 through 19, further comprising: receiving a UE capability message indicating a first timing gap associated with performing channel estimation and reporting on a non-per-tap basis and a second timing gap associated with performing channel estimation and reporting on a per-tap basis according to the per-tap channel estimation mode, wherein the indication of the per-tap channel estimation mode is based at least in part on the UE capability message.
  • Aspect 21 An apparatus for wireless communications at a UE, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 12.
  • Aspect 22 An apparatus for wireless communications at a UE, comprising at least one means for performing a method of any of aspects 1 through 12.
  • Aspect 23 A non-transitory computer-readable medium storing code for wireless communications at a UE, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 12.
  • Aspect 24 An apparatus for wireless communications at a network entity, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 13 through 20.
  • Aspect 25 An apparatus for wireless communications at a network entity, comprising at least one means for performing a method of any of aspects 13 through 20.
  • Aspect 26 A non-transitory computer-readable medium storing code for wireless communications at a network entity, the code comprising instructions executable by a processor to perform a method of any of aspects 13 through 20.
  • LTE, LTE-A, LTE-A Pro, or NR may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks.
  • the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
  • UMB Ultra Mobile Broadband
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Institute of Electrical and Electronics Engineers
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • a general-purpose processor may be a microprocessor but, in the alternative, the 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 in conjunction with a DSP core, or any other such configuration) .
  • the functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.
  • determining encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Power Engineering (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des procédés, des systèmes et des dispositifs destinés aux communications sans fil. Un équipement utilisateur (UE) peut recevoir un premier message indiquant un ou plusieurs paramètres de forme d'onde d'onde continue modulée en fréquence (FMCW) pour un signal de référence FMCW. L'UE peut recevoir un second message indiquant un mode d'estimation de canal par dérivation associé à la réalisation d'une procédure d'estimation de canal sur une base par dérivation pour chaque tap dans un ensemble de taps associés au signal de référence FMCW, chaque tap dans l'ensemble de taps correspondant à un retard de canal unique associé au signal de référence FMCW. L'UE peut effectuer la procédure d'estimation de canal à l'aide du signal de référence FMCW selon le mode d'estimation de canal par dérivation. L'UE peut transmettre un message de rétroaction de canal indiquant un résultat de la procédure d'estimation de canal à l'aide du signal de référence FMCW.
PCT/CN2023/081574 2023-03-15 2023-03-15 Estimation de canal par tap pour un signal de référence d'onde continue modulé en fréquence Pending WO2024187404A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/081574 WO2024187404A1 (fr) 2023-03-15 2023-03-15 Estimation de canal par tap pour un signal de référence d'onde continue modulé en fréquence

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/081574 WO2024187404A1 (fr) 2023-03-15 2023-03-15 Estimation de canal par tap pour un signal de référence d'onde continue modulé en fréquence

Publications (1)

Publication Number Publication Date
WO2024187404A1 true WO2024187404A1 (fr) 2024-09-19

Family

ID=92754076

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/081574 Pending WO2024187404A1 (fr) 2023-03-15 2023-03-15 Estimation de canal par tap pour un signal de référence d'onde continue modulé en fréquence

Country Status (1)

Country Link
WO (1) WO2024187404A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160047892A1 (en) * 2014-07-23 2016-02-18 Honeywell International Inc. Fmcw radar with phase encoded data channel
US20190265330A1 (en) * 2018-02-26 2019-08-29 Steradian Semiconductors Private Limited Method and Device for Calibrating a Radar Object Detection System
US20210320823A1 (en) * 2018-08-06 2021-10-14 Telefonaktiebolaget Lm Ericsson (Publ) Channel Estimation in a Wireless Communication System
WO2021258239A1 (fr) * 2020-06-22 2021-12-30 Qualcomm Incorporated Ajustement de paramètre de transmission basé sur une rétroaction pour une détection passive dans un système nr
US20220131723A1 (en) * 2020-10-27 2022-04-28 Huawei Technologies Co., Ltd. Sensing-assisted channel estimation
US20220345184A1 (en) * 2021-04-23 2022-10-27 Nxp B.V. Communication device and operating method

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160047892A1 (en) * 2014-07-23 2016-02-18 Honeywell International Inc. Fmcw radar with phase encoded data channel
US20190265330A1 (en) * 2018-02-26 2019-08-29 Steradian Semiconductors Private Limited Method and Device for Calibrating a Radar Object Detection System
US20210320823A1 (en) * 2018-08-06 2021-10-14 Telefonaktiebolaget Lm Ericsson (Publ) Channel Estimation in a Wireless Communication System
WO2021258239A1 (fr) * 2020-06-22 2021-12-30 Qualcomm Incorporated Ajustement de paramètre de transmission basé sur une rétroaction pour une détection passive dans un système nr
US20220131723A1 (en) * 2020-10-27 2022-04-28 Huawei Technologies Co., Ltd. Sensing-assisted channel estimation
US20220345184A1 (en) * 2021-04-23 2022-10-27 Nxp B.V. Communication device and operating method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Discussion of sidelink positioning", 3GPP DRAFT; R1-2004609, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. E-meeting; 20200525 - 20200605, 16 May 2020 (2020-05-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052345981 *

Similar Documents

Publication Publication Date Title
WO2023184062A1 (fr) Configurations de ressources d'informations d'état de canal pour prédiction de faisceau
US20240381352A1 (en) Wideband downlink precoding in subband full duplex symbols
US12500655B2 (en) Techniques for beam refinement and beam selection enhancement
US12244410B2 (en) Configuring a mixed-waveform modulation and coding scheme table
US20240089975A1 (en) Techniques for dynamic transmission parameter adaptation
US20240235917A9 (en) Frequency domain imbalance correction
US20240064540A1 (en) Inter-ue cross-link interference aware beam failure detection and radio link management
WO2023221033A1 (fr) Réalisation de mesures d'interférence de liaison croisée dans un mode de communication en duplex intégral
WO2024187404A1 (fr) Estimation de canal par tap pour un signal de référence d'onde continue modulé en fréquence
WO2024119293A1 (fr) Estimation de canaux de multiplexage par répartition orthogonale de la fréquence à l'aide de formes d'onde continues modulées en fréquence
WO2024216613A1 (fr) Granularité de canal pour estimation de canal à base de forme d'onde continue modulée en fréquence
WO2024229583A1 (fr) Chirp de forme d'onde continue modulée en fréquence basée sur un décalage cyclique en tant que signal de référence pour une estimation de canal à ports multiples
WO2024145801A1 (fr) Transmission de signal de référence à ports multiples pour forme d'onde d'onde continue modulée en fréquence
US12445326B2 (en) Asymmetric constellations for channel characterization
US20240214835A1 (en) Modem performance optimization under high frequency drift
US12395392B2 (en) Cyclic prefix guard interval for increased delay spread
WO2025152102A1 (fr) Signalisation de capacité agrégée pour une agrégation de porteuses et des modes de connectivité double
US20240098759A1 (en) Common time resources for multicasting
US20250233627A1 (en) Enhancement of user equipment (ue) selection for uplink aggregation
WO2024197782A1 (fr) États d'indicateur de configuration de transmission pour prédiction de faisceau spatial
US20250373390A1 (en) Tracking reference signals in full duplex operation
US20250047396A1 (en) Cross-link interference report with multiple hypotheses
US20250063409A1 (en) Phase noise reporting for constellation and waveform selection
WO2025054937A1 (fr) Mesure d'une couche sur la base d'un signal de référence de démodulation
US20240251309A1 (en) Reference cell configuration

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23926761

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE