Techniques for reporting frequency correction
By requesting frequency correction reports in the wireless communication system, the problem that network entities find it difficult to accurately estimate the channel in a flat channel is solved, and more efficient channel resource utilization and improved user experience are achieved.
Patent Information
- Application Number
- CN202380067411.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-09-30
- Filing Date
- 2023-09-14
- Publication Date
- 2025-04-29
AI Technical Summary
In wireless communication systems, it is difficult for network entities to perform channel estimation accurately, especially in channels experiencing flat fading, resulting in a degradation in channel quality, increased latency and poor user experience.
By requesting a frequency correction report in a user equipment (UE), the UE monitors the reference signal in downlink signaling and sends a frequency correction report to the network entity based on the report parameters, which performs channel estimation based on the report.
Improve the accuracy of channel estimation, reduce delay, and improve channel quality and user experience.
Smart Images

Figure CN119908150A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority to U.S. patent application No. 17 / 957,216, entitled “TECHNIQUES FOR REPORTING FREQUENCY CORRECTIONS,” filed by LANDIS et al. on September 30, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field
[0003] The following relates to wireless communications, including techniques for reporting frequency corrections. Background Art
[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM).
[0005] A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication for communication devices, which may be referred to as user equipment (UE). In some wireless communication systems, a network entity (such as one or more components of a base station) may perform channel estimation on a channel. Summary of the invention
[0006] The described technology relates to improved methods, systems, devices and apparatuses that support technology for reporting frequency corrections. For example, the described technology may enable a network entity to perform channel estimation on a channel. For example, a network entity may use the technology described herein to perform channel estimation on a communication channel that undergoes flat fading, thereby improving the performance of the flat channel, improving the quality of communication and reducing latency. For example, the network entity may send a request to a user equipment (UE) to cause the UE to report one or more frequency corrections. The UE may monitor a set of one or more reference signals associated with performing the one or more frequency corrections at the UE. The UE may send the report indicating the one or more frequency corrections to the network entity according to one or more reporting parameters. In some examples, the network entity may receive the report via a channel that undergoes flat fading. In such examples, the network entity may perform channel estimation on the flat channel based on the reported frequency correction, thereby enabling the network entity to improve the accuracy of channel estimation in a channel that undergoes flat fading.
[0007] A method for wireless communication at a UE is described. The method may include: receiving a request to report one or more frequency corrections from a network entity, the request including an indication of one or more reporting parameters for the one or more frequency corrections; monitoring a set of one or more reference signals associated with performing the one or more frequency corrections at the UE; and sending a report indicating the one or more frequency corrections to the network entity according to the one or more reporting parameters.
[0008] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receive a request to report one or more frequency corrections from a network entity, the request including an indication of one or more reporting parameters for the one or more frequency corrections; monitor a set of one or more reference signals associated with performing the one or more frequency corrections at the UE; and send a report indicating the one or more frequency corrections to the network entity based on the one or more reporting parameters.
[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving a request to report one or more frequency corrections from a network entity, the request including an indication of one or more reporting parameters for the one or more frequency corrections; means for monitoring a set of one or more reference signals associated with performing the one or more frequency corrections at the UE; and means for sending a report indicating the one or more frequency corrections to the network entity based on the one or more reporting parameters.
[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive a request to report one or more frequency corrections from a network entity, the request including an indication of one or more reporting parameters for the one or more frequency corrections; monitor a set of one or more reference signals associated with performing the one or more frequency corrections at the UE; and send a report indicating the one or more frequency corrections to the network entity according to the one or more reporting parameters.
[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication of the UE capability to report the one or more frequency corrections to the network entity, wherein receiving the request to report the one or more frequency corrections may be based on the indication of the UE capability.
[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: monitoring a second set of one or more reference signals after monitoring the set of one or more reference signals; and sending a second report indicating a second set of frequency error corrections to the network entity based on the one or more reporting parameters and the second set of one or more reference signals.
[0013] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, the report and the second report can be periodic reports. In some examples of methods, apparatus, and non-transitory computer-readable media described herein, the one or more reporting parameters indicate a periodicity for sending the report indicating the one or more frequency corrections.
[0014] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, the report and the second report can be non-periodic reports. In some examples of methods, apparatus, and non-transitory computer-readable media described herein, the one or more reporting parameters indicate a trigger for sending the report indicating the one or more frequency corrections.
[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the trigger comprises receiving the set of one or more reference signals at the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the set of one or more reference signals comprises at least one of a demodulation reference signal (DMRS), a tracking reference signal (TRS), or a combination thereof.
[0016] A method for wireless communication at a network entity is described. The method may include: sending a request to a UE to report one or more frequency corrections, the request including an indication of one or more reporting parameters for the one or more frequency corrections; sending a set of one or more reference signals associated with performing the one or more frequency corrections at the UE; and receiving a report from the UE indicating the one or more frequency corrections according to the one or more reporting parameters.
[0017] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: send a request to report one or more frequency corrections to a UE, the request including an indication of one or more reporting parameters for the one or more frequency corrections; send a set of one or more reference signals associated with performing the one or more frequency corrections at the UE; and receive a report from the UE indicating the one or more frequency corrections according to the one or more reporting parameters.
[0018] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending a request to a UE to report one or more frequency corrections, the request including an indication of one or more reporting parameters for the one or more frequency corrections; means for sending a set of one or more reference signals associated with performing the one or more frequency corrections at the UE; and means for receiving a report from the UE indicating the one or more frequency corrections based on the one or more reporting parameters.
[0019] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to perform the following operations: sending a request to report one or more frequency corrections to a UE, the request including an indication of one or more reporting parameters for the one or more frequency corrections; sending a set of one or more reference signals associated with performing the one or more frequency corrections at the UE; and receiving a report from the UE indicating the one or more frequency corrections according to the one or more reporting parameters.
[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, from the UE, an indication of UE capability to report the one or more frequency corrections, wherein sending the request to report the one or more frequency corrections may be based on the indication of the UE capability.
[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending a second set of one or more reference signals after sending the set of one or more reference signals; and receiving a second report indicating the second set of frequency error corrections from the UE based on the one or more reporting parameters and the second set of one or more reference signals.
[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing channel estimation for the UE based on the report indicating the one or more frequency corrections and the second report indicating the second set of frequency error corrections.
[0023] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, the report and the second report can be periodic reports. In some examples of methods, apparatus, and non-transitory computer-readable media described herein, the one or more reporting parameters indicate a periodicity for sending the report indicating the one or more frequency corrections.
[0024] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, the report and the second report can be non-periodic reports. In some examples of methods, apparatus, and non-transitory computer-readable media described herein, the one or more reporting parameters indicate a trigger for sending the report indicating the one or more frequency corrections.
[0025] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the triggering includes receiving the set of one or more reference signals at the UE. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the set of one or more reference signals includes at least one of a DMRS, a TRS, or a combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] Figure 1 An example of a wireless communication system supporting techniques for reporting frequency corrections in accordance with one or more aspects of the present disclosure is illustrated.
[0027] Figure 2 An example of a wireless communication system supporting techniques for reporting frequency corrections in accordance with one or more aspects of the present disclosure is illustrated.
[0028] Figure 3 An example of a process flow supporting techniques for reporting frequency correction in accordance with one or more aspects of the present disclosure is illustrated.
[0029] Figure 4 and Figure 5A block diagram of a device supporting techniques for reporting frequency corrections according to one or more aspects of the present disclosure is illustrated.
[0030] Figure 6 A block diagram of a communications manager supporting techniques for reporting frequency corrections in accordance with one or more aspects of the present disclosure is illustrated.
[0031] Figure 7 A diagram of a system including a device supporting techniques for reporting frequency correction in accordance with one or more aspects of the present disclosure is illustrated.
[0032] Figure 8 and Fig. 9 A block diagram of a device supporting techniques for reporting frequency corrections according to one or more aspects of the present disclosure is illustrated.
[0033] Fig.10 A block diagram of a communications manager supporting techniques for reporting frequency corrections in accordance with one or more aspects of the present disclosure is illustrated.
[0034] Fig.11 A diagram of a system including a device supporting techniques for reporting frequency correction is illustrated in accordance with one or more aspects of the present disclosure.
[0035] Figures 12 to 15 A flow chart illustrating a method of supporting techniques for reporting frequency correction in accordance with one or more aspects of the present disclosure is illustrated. DETAILED DESCRIPTION
[0036] In some wireless communication systems, a network entity may communicate with a user equipment (UE) via one or more channels. In such systems, the network entity may perform channel estimation based on uplink signaling received from the UE, and the UE may perform channel estimation based on downlink signaling received from the network entity. In some cases, the network entity may receive uplink signaling from the UE in a channel that undergoes flat fading. Since the frequency allocation for the channel is less than the coherence bandwidth of the channel (e.g., a measurement of the frequency range within which the channel is constant or flat), the channel may experience flat fading. In such cases, each frequency component (e.g., of a signal) sent in the channel may experience the same amplitude and phase fading. Additionally, the channel may experience flat fading in line-of-sight (LOS) communications (e.g., where the coherence bandwidth may be infinite, making the frequency allocation less than the coherence bandwidth).
[0037] In the case of flat fading, the network entity may not be able to accurately perform channel estimation on the received uplink signaling. For example, the network entity may receive uplink signaling including multiple demodulation reference signals (DMRS). As part of the channel estimation, the network entity may determine whether the frequency component of the channel is experiencing Doppler spread or Doppler shift based on measuring the correlation of two or more DMRS received in different symbols in the uplink signaling. However, if the network entity receives uplink signaling via a flat channel (e.g., a channel experiencing flat fading), the network entity may not be able to determine whether the flat channel is experiencing Doppler shift or Doppler spread, thereby increasing the error when performing channel estimation. The increased error in channel estimation may result in increased latency, poor channel quality, and reduced user experience.
[0038] The techniques described herein may enable a network entity to improve the accuracy with which channel estimation is performed. For example, a UE may receive a request from a network entity to report a frequency correction (e.g., frequency error correction) performed during channel estimation. The UE may monitor one or more reference signals (e.g., DMRS, tracking reference signal (TRS) or both) in downlink signaling from the network entity. In order to receive one or more reference signals from the network entity, the UE may perform a frequency correction (e.g., adjust one or more timing parameters or frequency parameters at the UE). Based on the time and frequency correction for receiving the reference signal, the UE may adjust one or more frequency or time parameters for sending uplink signaling. In addition to sending uplink signaling, the UE may also send a report indicating the frequency correction to the network entity. In some cases, the network entity may receive uplink signaling via a flat channel. In such cases, the network entity may use the received frequency correction to perform channel estimation. Therefore, based on the received frequency correction, the network entity may estimate a flat channel, thereby reducing channel estimation errors, reducing latency, and improving channel quality.
[0039] Aspects of the disclosure are first described in the context of a wireless communication system. Aspects of the disclosure are illustrated in the context of a process flow. Aspects of the disclosure are further illustrated by apparatus diagrams, system diagrams, and flow diagrams relating to techniques for reporting frequency corrections, and are described with reference to these diagrams.
[0040] Figure 1An example of a wireless communication system 100 supporting techniques for reporting frequency corrections according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
[0041] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).
[0042] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1 . The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 105 or other UEs 115 or network entities 105) as shown.
[0043] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.
[0044] In some examples, the network entities 105 may communicate with the core network 130, or with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication links 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication links 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, the midhaul communication links 162, or the fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .
[0045] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).
[0046] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).
[0047] The functional split between CU 160, DU 165, and 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 combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165, such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.
[0048] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.
[0049] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the techniques for reporting frequency correction as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).
[0050] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.
[0051] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 shown.
[0052] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may consist of a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any part (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send", "receive", or "communicate" when referring to the network entity 105 may refer to any part of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).
[0053] The signal waveform transmitted via the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), so that a relatively higher amount of resource elements (e.g., in the transmission duration) and a relatively higher order of the modulation scheme may correspond to a relatively higher communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.
[0054] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. Time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).
[0055] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slots may be further divided into mini-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.
[0056] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the amount of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).
[0057] Carriers may be used to multiplex physical channels for communication according to various techniques. Physical control channels and physical data channels may be multiplexed via downlink carriers for signaling, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .
[0058] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for respective coverage areas 110 using the same or different radio access technologies.
[0059] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
[0060] In some examples, a UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured by the network entity 105 (e.g., scheduled by the network entity). In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.
[0061] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered via a user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.
[0062] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from about one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.
[0063] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands (such as the 5 GHz industrial, scientific, and medical (ISM) band). When operating using unlicensed RF spectrum bands, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations using unlicensed bands may be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.
[0064] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a set of antenna ports of multiple rows and columns that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.
[0065] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).
[0066] In some examples of the wireless communication system 100, the network entity 105 may communicate with the UE 115 via one or more channels. In such cases, the network entity 105 may communicate with the UE 115 via a channel that may experience flat fading (e.g., a flat channel or a nearly flat channel), such that signals sent via the flat channel may experience the same amplitude and phase fading. A flat channel may occur due to a frequency allocation of the channel being less than the coherence bandwidth of the channel. Additionally, a flat channel may be due to LOS communication (where the coherence bandwidth is infinite, such that the frequency allocation is less than the coherence bandwidth).
[0067] In some cases, the network entity 105 may estimate channel statistics, such as delay spread, Doppler spread, and signal-to-noise ratio (SNR), based on one or more signals (e.g., DMRS or TRS) sent from the UE 115. For example, the network entity 105 may estimate the Doppler spread of the channel based on a measured empirical correlation between two or more DMRSs in different orthogonal frequency division multiplexing (OFDM) symbols of an uplink channel (e.g., a physical uplink shared channel (PUSCH)). However, if the network entity 105 receives the DMRS via a flat channel, the network entity 105 (e.g., due to lack of statistics between the DMRSs) may not be able to correctly estimate the Doppler spread. For example, if the amplitude and phase of the frequency component vary in the channel (e.g., a non-flat channel), the network entity 105 may be able to estimate the Doppler spread due to the difference in the DMRS received in each OFDM symbol. However, in the case of a flat channel, the network entity 105 may not be able to estimate the Doppler spread due to similar amplitude and phase fading on the channel. In addition, in some cases of a flat channel, the phase of the DMRS may vary between OFDM symbols. In such cases, the network entity 105 or UE 115 may not be able to distinguish whether the phase difference between the DMRS is due to the flat fading of the channel or due to the Doppler shift of the LOS channel. Therefore, when communicating on a flat channel, the network entity 105 may not be able to determine whether a Doppler shift or Doppler spread has occurred in the channel, thereby introducing errors in channel estimation, increasing latency, and reducing user experience.
[0068] In order for the network entity 105 to determine the cause of the flat channel and improve the accuracy of the channel estimation, the network entity 105 may request a frequency correction report from the UE 115 to assist in the channel estimation of the flat channel. For example, the UE 115 may receive a request from the network entity 105 to report the frequency correction implemented at the UE 115. For example, the UE 115 may monitor one or more DMRS, TRS, or both. In order to receive the DMRS or TRS, the UE 115 may perform a frequency correction (e.g., adjust one or more timing parameters and frequency parameters at the UE 115). The UE 115 may perform the frequency correction before sending the uplink signaling to the network entity 105. In some examples, the uplink signaling may be based on the frequency correction performed to receive the DMRS or TRS. Additionally, the UE 115 may send a report indicating the frequency correction to the network entity 105. In some examples, the network entity 105 may receive the uplink signaling via a flat channel. In such cases, the network entity 105 may use the received frequency correction to perform channel estimation for a flat channel, thereby improving performance when a flat channel is encountered (e.g., when the frequency allocation of the channel is less than the coherence bandwidth of the channel), improving channel estimation accuracy, and improving user experience.
[0069] Figure 2 An example of a wireless communication system 200 that supports techniques for reporting frequency correction according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may be implemented as shown in FIG. Figure 1 Various aspects of the wireless communication system 100 described herein may be implemented by various aspects of the wireless communication system. For example, the wireless communication system 200 may include a UE 115-a and a network entity 105-a, which may be as described herein with reference to Figure 1 Depicted are examples of UE 115 and network entity 105 . UE 115 - a and network entity 105 - a may operate within a coverage area 110 - a , which may be an example of coverage area 110 .
[0070] In some cases, the UE 115-a may monitor a reference signal 215 from the network entity 105-a. The reference signal 215 may include a DMRS, a TRS, or a combination thereof. In such cases, in order to successfully decode the reference signal 215, the UE 115 may perform one or more frequency corrections (e.g., by adjusting a crystal or an internal clock of a receive chain at the UE 115-a). For example, the UE 115-a may continuously estimate a timing error and a frequency error of a channel between the UE 115-a and the network entity 105-a based on the reference signal 215 (e.g., based on decoding TRS and DMRS received in a physical downlink shared channel (PDSCH)). The frequency error of the channel may be caused by channel conditions, while the timing error may be caused by an error in an oscillator (XO) crystal (e.g., an internal clock) of the UE 115-a. In some cases, Doppler spread or Doppler shift may result in frequency changes caused by channel conditions. A Doppler shift may be a frequency change of a channel from a single source (e.g., a single reflector), which results in a slow change in the frequency trend of the channel. A Doppler spread may be a combination of frequency changes of a channel due to one or more Doppler shifts with multiple reflectors (e.g., objects located on the communication path between the network entity 105-a and the UE 115-a) having different speeds. In the case of a Doppler spread, the frequency may change relatively quickly in time even if the physical speed of the UE 115-a remains unchanged. For example, the number of increased reflectors in the communication channel between the UE 115-a and the network entity 105-a may result in multiple Doppler shifts in the channel (e.g., all of which have different speeds). Therefore, a Doppler spread of a channel may refer to one or more Doppler shifts occurring in a channel, all of which have different rates of change.
[0071] In some cases, the network entity 105-a and the UE 115-a may communicate via a flat channel. For example, the UE 115-a may send one or more uplink signals via a channel, where the frequency allocation for the channel is less than the coherence bandwidth of the channel. In such examples, the network entity 105-a may receive the one or more uplink signals via the flat channel (e.g., the network entity encounters a flat channel). The network entity 105-a may attempt to empirically estimate the time correlation (e.g., Doppler spread) of the channel over two or more DMRSs of a channel (e.g., a physical uplink shared channel) using Formula 1:
[0072]
[0073] Where k represents the time index offset between DMRSs, p i represents the sample from the first DMRS in resource element i, and p i+k represents the samples from the second DMRS at resource element i.
[0074] However, in the case of flat fading (e.g., when the network entity 105-a encounters a flat channel), there may be no statistics due to the variation of the DMRS in the flat channel, and thus the network entity 105-a may not be able to accurately estimate the time correlation. For example, in a flat channel, the amplitude and phase fading of the signal across different frequency components may be similar. Subsequently, the time correlation between DMRS across multiple symbols may be similar. Therefore, in the case of a flat channel, the estimation using Formula 1 may result in a value of "1", which may not represent the actual Doppler spread of the channel. Without accurate time correlation estimation, the network entity 105-a may not be able to accurately perform channel estimation, resulting in reduced channel quality, increased latency, and a poor user experience.
[0075] In some specific implementations of the wireless communication system 200, in order to improve the accuracy of channel estimation for a flat channel, the network entity 105-a may request a report of frequency correction from the UE 115-a. For example, the UE 115-a may send a UE capability message 205, which indicates that the UE 115-a is capable of sending an indication of frequency correction to the network entity 105-a. The UE capability message 205 may be included in uplink control information (UCI), a MAC control element (MAC-CE), an RRC message, or a combination thereof. Based on receiving the UE capability message 205, the network entity 105-a may send a request message 210, which requests the transmission of a frequency correction report 220. The request message 210 may be included in downlink control information (DCI), an RRC message, or a combination thereof. In some examples, the request message 210 may include one or more reporting parameters associated with reporting frequency correction.
[0076] For example, the one or more reporting parameters may include a periodicity with which the UE 115-a will report a frequency correction (e.g., send a frequency correction report 220), a trigger for sending a frequency correction report 220 (e.g., a non-periodic frequency correction report), or both. In some implementations, the reporting parameters may include a threshold configured by the network entity 105-a, and if the frequency correction satisfies the threshold, the UE 115-a may send the frequency correction report 220. Additionally, the network entity 105-a may indicate to the UE 115-a which DMRS or TRS to use when reporting the frequency correction (e.g., the last TRS or DMRS). For example, the network entity 105-a may indicate that the UE 115-a is to report a frequency correction associated with decoding the last (most recent) DMRS or TRS.
[0077] The network entity 105-a may send a reference signal 215-a to the UE 115-a via a downlink channel (e.g., a PDSCH), which may include one or more DMRSs, one or more TRSs, or both. The UE 115-a may monitor the reference signal 215-a and decode the reference signal 215-a using one or more frequency corrections. In response to the request message 210, the UE 115-a may send uplink signaling to the network entity 105-a based on the one or more frequency corrections (e.g., by applying the same or similar frequency correction to decode the DMRS for transmission at the UE 115-a). In addition to sending the uplink signaling, the UE 115-a may send a frequency correction report 220-a to the network entity 105-a via the PUSCH, which indicates one or more frequency corrections. The frequency correction report 220 may be included in a UCI, a MAC-CE, an RRC message (as a payload of the PUSCH), or a combination thereof. The network entity 105 - a may use the frequency correction received in the frequency correction report 220 - a to perform channel estimation.
[0078] In some examples, the network entity 105-a may compare the frequency correction received in the frequency correction report 220-a with the frequency correction performed by the network entity 105-a. If the correlation between the frequency correction of the UE 115-a and the frequency correction of the network entity 105-a is low, the network entity 105-a may determine that the channel is experiencing flat fading due to Doppler spread (e.g., the frequency of the channel changes faster at the UE 115-a), and may assume that the time correlation between the time at the UE 115-a and the time at the network entity 105-a is low, thereby performing channel estimation. Alternatively, if the correlation between the frequency correction of the UE 115-a and the frequency correction of the network entity 105-a is high, the network entity 105-a may determine that the channel is experiencing flat fading due to Doppler shift (e.g., the frequency of the channel changes slower at the UE 115-a), and may assume that the time correlation between the UE 115-a and the network entity 105-a is high, thereby performing channel estimation.
[0079] In addition, UE 115-a may send frequency correction report 220-b based on one or more operating parameters (e.g., operating parameters indicated by network entity 105-a). For example, UE 115-a may receive reference signal 215-b and decode reference signal 215-b using one or more frequency corrections. In such examples, UE 115-a may send frequency correction report 220-b to network entity 105-a. In some examples, one or more operating parameters may indicate the periodicity with which UE 115-a will send frequency correction report 220-b. In some examples, one or more operating parameters may indicate a trigger for UE 115-a to send frequency correction report. In such examples, the trigger may be based on UE 115-a receiving reference signal 215-b or one of reference signals 215-b. For example, based on receiving reference signal 215-b, UE 115-a may decode reference signal 215-b using frequency corrections and send frequency correction report 220-b to network entity 105-a. In some examples, UE 115-a may receive reference signal 215-b and use frequency correction to decode reference signal 215-b. In such examples, UE 115-a may determine that the frequency correction used to decode reference signal 215-b satisfies an indicated frequency threshold. UE 115-b may send a frequency correction report 220-b based on the frequency correction satisfying the frequency threshold. Network entity 105-a may receive frequency correction report 220-b via a PUSCH experiencing flat fading. Network entity 105-a may use the indicated frequency correction to perform channel estimation, thereby improving communication quality in a channel experiencing flat fading.
[0080] Figure 3An example of a process flow 300 supporting techniques for reporting frequency correction according to one or more aspects of the present disclosure is illustrated. The process flow 300 may implement reference Figure 1 and Figure 2 Aspects of the wireless communication system 100 and the wireless communication system 200 described herein may be implemented thereby. For example, the process flow 300 may include the UE 115-b and the network entity 105-b, which may be as described herein with reference to Figure 1 and Figure 2 Examples of corresponding devices described. In the following description of the process flow 300, the operations may be performed in an order different from the order shown. Certain operations may also be excluded from the process flow 300, or other operations may be added to the process flow 300. In addition, although some operations or signaling are shown as occurring at different times for discussion purposes, these operations may actually occur simultaneously.
[0081] At 305, UE 115-b may optionally send an indication of UE capability to report one or more frequency corrections to network entity 105-b. This indication of UE capability may be as described herein with reference to Figure 2 An example of a UE capabilities message 205 is described.
[0082] At 310, UE 115-b may receive, and network entity 105-b may send, a request to report the one or more frequency corrections. The request may include an indication of one or more reporting parameters for the one or more frequency corrections. The one or more reporting parameters may indicate a periodicity for sending the report of the one or more frequency corrections. Additionally, the one or more reporting parameters may indicate a trigger for sending the report, wherein the trigger includes receiving one or more reference signals at UE 115-b. In some examples, the one or more reporting parameters may include a threshold value such that if the frequency correction at UE 115-b is greater than the indicated threshold value, UE 115-b may send a report of the one or more frequency corrections.
[0083] At 315, the network entity 105-b may send a set of one or more reference signals associated with performing the one or more frequency corrections. The set of one or more reference signals may include at least one of a DMRS, a TRS, or a combination thereof. At 320, the UE 115-b may monitor the set of one or more reference signals. For example, in order to monitor and decode the set of one or more reference signals, the UE 115-b may perform the one or more frequency corrections.
[0084] At 325, UE 115-b may send the report indicating the one or more frequency corrections to network entity 105-b based on the one or more reporting parameters. For example, UE 115-b may send the report based on the periodicity indicated in the reporting parameters (e.g., a periodic report). In some examples, UE 115-b may send the report based on receiving the one or more reference signals based on the trigger indicated in the one or more reporting parameters (e.g., a non-periodic report). In some examples, UE 115-b may determine that the one or more frequency corrections satisfy an indicated threshold, wherein the report is sent based on the one or more frequency corrections satisfying the indicated threshold.
[0085] At 330, the network entity 105-b may optionally perform channel estimation based on the report indicating the one or more frequency corrections. For example, the network entity 105-b may receive the report in a channel that experiences flat fading. In such an example, the network entity 105-b may determine whether Doppler shift or Doppler spread is affecting the channel and estimate the channel based on the one or more frequency corrections.
[0086] At 335, the network entity 105-b may optionally send a second set of one or more reference signals after sending the set of one or more reference signals. At 340, the UE 115-b may optionally monitor the second set of one or more reference signals and decode the second set of one or more reference signals using the second set of frequency error corrections.
[0087] At 345, the UE 115-b may optionally send a second report indicating the second set of frequency error corrections based on the one or more reporting parameters and the second set of one or more reference signals. At 350, the network entity 105-b may optionally perform channel estimation based on the report indicating the one or more frequency corrections and the second report indicating the second set of frequency error corrections.
[0088] Figure 4 A block diagram 400 of a device 405 supporting techniques for reporting frequency corrections according to one or more aspects of the present disclosure is illustrated. The device 405 may be an example of aspects of a UE 115 as described herein. The device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. The device 405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0089] Receiver 410 may provide 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 techniques for reporting frequency corrections). The information may be communicated to other components of device 405. Receiver 410 may utilize a single antenna or a set of multiple antennas.
[0090] Transmitter 415 may provide means for transmitting signals generated by other components of device 405. For example, transmitter 415 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for reporting frequency corrections). In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a set of multiple antennas.
[0091] The communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the techniques for reporting frequency corrections as described herein. For example, the communication manager 420, the receiver 410, the transmitter 415, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.
[0092] In some examples, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).
[0093] Additionally or alternatively, in some examples, the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.
[0094] In some examples, communication manager 420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 410, transmitter 415, or both. For example, communication manager 420 may receive information from receiver 410, transmit information to transmitter 415, or be integrated in conjunction with receiver 410, transmitter 415, or both to obtain information, output information, or perform various other operations as described herein.
[0095] According to examples as disclosed herein, the communication manager 420 may support wireless communications at a UE. For example, the communication manager 420 may be configured to or otherwise support a component for receiving a request to report one or more frequency corrections from a network entity, the request including an indication of one or more reporting parameters for the one or more frequency corrections. The communication manager 420 may be configured to or otherwise support a component for monitoring a set of one or more reference signals associated with performing the one or more frequency corrections at the UE. The communication manager 420 may be configured to or otherwise support a component for sending a report indicating the one or more frequency corrections to the network entity based on the one or more reporting parameters.
[0096] By including or configuring a communication manager 420 according to the examples described herein, the device 405 (e.g., a processor controlling or otherwise coupled to the receiver 410, the transmitter 415, the communication manager 420, or a combination thereof) can support network entities in using frequency error correction techniques in channel estimation, thereby achieving more efficient communication resource utilization.
[0097] Figure 5A block diagram 500 of a device 505 supporting techniques for reporting frequency corrections according to one or more aspects of the present disclosure is illustrated. The device 505 may be an example of aspects of the device 405 or UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0098] Receiver 510 may provide 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 techniques for reporting frequency corrections). The information may be communicated to other components of device 505. Receiver 510 may utilize a single antenna or a set of multiple antennas.
[0099] The transmitter 515 may provide means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to techniques for reporting frequency corrections). In some examples, the transmitter 515 may be co-located with the receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a set of multiple antennas.
[0100] Device 505 or its various components may be examples of components for performing various aspects of the technology for reporting frequency correction as described herein. For example, communication manager 520 may include communication component 525, reference signal monitoring component 530, frequency correction component 535, or any combination thereof. Communication manager 520 may be an example of various aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise in conjunction with receiver 510, transmitter 515, or both. For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or integrate with receiver 510, transmitter 515, or both in combination to obtain information, output information, or perform various other operations as described herein.
[0101] According to examples as disclosed herein, the communication manager 520 may support wireless communications at a UE. The communication component 525 may be configured to or otherwise support components for receiving a request to report one or more frequency corrections from a network entity, the request including an indication of one or more reporting parameters for the one or more frequency corrections. The reference signal monitoring component 530 may be configured to or otherwise support components for monitoring a set of one or more reference signals associated with performing the one or more frequency corrections at the UE. The frequency correction component 535 may be configured to or otherwise support components for sending a report indicating the one or more frequency corrections to the network entity based on the one or more reporting parameters.
[0102] Figure 6 A block diagram 600 of a communication manager 620 supporting techniques for reporting frequency correction according to one or more aspects of the present disclosure is illustrated. The communication manager 620 may be an example of aspects of the communication manager 420, the communication manager 520, or both as described herein. The communication manager 620 or its various components may be examples of components for performing various aspects of the techniques for reporting frequency correction as described herein. For example, the communication manager 620 may include a communication component 625, a reference signal monitoring component 630, a frequency correction component 635, a UE capability component 640, a frequency correction component 645, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).
[0103] According to examples as disclosed herein, the communication manager 620 may support wireless communications at a UE. The communication component 625 may be configured to or otherwise support components for receiving a request to report one or more frequency corrections from a network entity, the request including an indication of one or more reporting parameters for the one or more frequency corrections. The reference signal monitoring component 630 may be configured to or otherwise support components for monitoring a set of one or more reference signals associated with performing the one or more frequency corrections at the UE. The frequency correction component 635 may be configured to or otherwise support components for sending a report indicating the one or more frequency corrections to the network entity based on the one or more reporting parameters.
[0104] In some examples, the UE capability component 640 may be configured as or otherwise support components for sending an indication of the UE capability to report the one or more frequency corrections to the network entity, wherein receiving the request to report the one or more frequency corrections is based on the indication of the UE capability.
[0105] In some examples, reference signal monitoring component 630 can be configured or otherwise support components for monitoring a second set of one or more reference signals after monitoring the set of one or more reference signals. In some examples, frequency correction component 645 can be configured or otherwise support components for sending a second report indicating a second set of frequency error corrections to the network entity based on the one or more reporting parameters and the second set of one or more reference signals.
[0106] In some examples, the report and the second report are periodic reports. In some examples, the one or more reporting parameters indicate a periodicity of sending the report indicating the one or more frequency corrections. In some examples, the report and the second report are aperiodic reports.
[0107] In some examples, the one or more reporting parameters indicate a trigger for sending the report indicating the one or more frequency corrections. In some examples, the trigger includes receiving the set of one or more reference signals at the UE. In some examples, the set of one or more reference signals includes at least one of a DMRS, a TRS, or a combination thereof.
[0108] Figure 7 A diagram of a system 700 including a device 705 supporting techniques for reporting frequency corrections according to one or more aspects of the present disclosure is illustrated. The device 705 may be an example of a device 405, a device 505, or a UE 115 as described herein or include components thereof. The device 705 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 705 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 720, an input / output (I / O) controller 710, a transceiver 715, an antenna 725, a memory 730, a code 735, and a processor 740. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 745).
[0109] I / O controller 710 can manage input and output signals for device 705. I / O controller 710 can also manage peripheral devices that are not integrated into device 705. In some cases, I / O controller 710 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 710 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 710 may be implemented as part of a processor (such as processor 740). In some cases, a user may interact with device 705 via I / O controller 710 or via hardware components controlled by I / O controller 710.
[0110] In some cases, the device 705 may include a single antenna 725. However, in some other cases, the device 705 may have more than one antenna 725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 715 may communicate bidirectionally via one or more antennas 725, a wired or wireless link, as described herein. For example, the transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. The transceiver 715 or the transceiver 715 and the one or more antennas 725 may be examples of transmitters 415, transmitters 515, receivers 410, receivers 510, or any combination thereof or components thereof as described herein.
[0111] The memory 730 may include random access memory (RAM) and read-only memory (ROM). The memory 730 may store computer-readable, computer-executable code 735 including instructions that, when executed by the processor 740, cause the device 705 to perform various functions described herein. The code 735 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 735 may not be directly executable by the processor 740, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 730 may also include a basic I / O system (BIOS), etc., which may control basic hardware or software operations (such as interaction with peripheral components or devices).
[0112] The processor 740 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 740 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 740. The processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 730) to cause the device 705 to perform various functions (e.g., various functions or tasks supporting techniques for reporting frequency correction). For example, the device 705 or a component of the device 705 may include a processor 740 and a memory 730 coupled to or to the processor 740, and the processor 740 and the memory 730 are configured to perform the various functions described herein.
[0113] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a UE. For example, the communication manager 720 may be configured to or otherwise support a component for receiving a request to report one or more frequency corrections from a network entity, the request including an indication of one or more reporting parameters for the one or more frequency corrections. The communication manager 720 may be configured to or otherwise support a component for monitoring a set of one or more reference signals associated with performing the one or more frequency corrections at the UE. The communication manager 720 may be configured to or otherwise support a component for sending a report indicating the one or more frequency corrections to the network entity based on the one or more reporting parameters.
[0114] By including or configuring a communication manager 720 according to examples as described herein, the device 705 can support techniques for network entities to use frequency error correction in channel estimation, thereby improving communication reliability, reducing latency, and improving user experience associated with reduced processing and reduced power consumption.
[0115] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 715, one or more antennas 725, or any combination thereof. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or performed by the processor 740, the memory 730, the code 735, or any combination thereof. For example, the code 735 may include instructions that are executable by the processor 740 to cause the device 705 to perform various aspects of the techniques for reporting frequency corrections as described herein, or the processor 740 and the memory 730 may be otherwise configured to perform or support such operations.
[0116] Figure 8 A block diagram 800 of a device 805 supporting techniques for reporting frequency corrections according to one or more aspects of the present disclosure is illustrated. The device 805 may be an example of aspects of the network entity 105 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0117] The receiver 810 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 805. In some examples, the receiver 810 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 810 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.
[0118] The transmitter 815 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 805. For example, the transmitter 815 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 815 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 815 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 815 and the receiver 810 may be co-located in a transceiver, which may include a modem or be coupled to a modem.
[0119] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the techniques for reporting frequency corrections as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.
[0120] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).
[0121] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.
[0122] In some examples, the communication manager 820 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 can receive information from the receiver 810, transmit information to the transmitter 815, or integrate with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.
[0123] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a network entity. For example, the communication manager 820 may be configured to or otherwise support a component for sending a request to report one or more frequency corrections to a UE, the request including an indication of one or more reporting parameters for the one or more frequency corrections. The communication manager 820 may be configured to or otherwise support a component for sending a set of one or more reference signals associated with performing the one or more frequency corrections at the UE. The communication manager 820 may be configured to or otherwise support a component for receiving a report indicating the one or more frequency corrections from the UE according to the one or more reporting parameters.
[0124] By including or configuring a communication manager 820 according to the examples described herein, the device 805 (e.g., a processor controlling or otherwise coupled to the receiver 810, the transmitter 815, the communication manager 820, or a combination thereof) can support network entities in using frequency error correction techniques in channel estimation, thereby achieving more efficient communication resource utilization.
[0125] Fig. 9 A block diagram 900 of a device 905 supporting techniques for reporting frequency corrections according to one or more aspects of the present disclosure is illustrated. The device 905 may be an example of aspects of the device 805 or the network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0126] The receiver 910 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.
[0127] The transmitter 915 may provide means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 905. For example, the transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 915 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 915 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include a modem or be coupled to a modem.
[0128] The device 905 or its various components may be examples of components for performing various aspects of the technology for reporting frequency correction as described herein. For example, the communication manager 920 may include a communication component 925, a reference signal component 930, a frequency correction component 935, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its various components may be configured to use or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or integrate with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.
[0129] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a network entity. The communication component 925 may be configured to or otherwise support a component for sending a request to report one or more frequency corrections to a UE, the request including an indication of one or more reporting parameters for the one or more frequency corrections. The reference signal component 930 may be configured to or otherwise support a component for sending a set of one or more reference signals associated with performing the one or more frequency corrections at the UE. The frequency correction component 935 may be configured to or otherwise support a component for receiving a report indicating the one or more frequency corrections from the UE according to the one or more reporting parameters.
[0130] Fig.10 A block diagram 1000 of a communication manager 1020 supporting techniques for reporting frequency correction according to one or more aspects of the present disclosure is illustrated. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of components for performing various aspects of the techniques for reporting frequency correction as described herein. For example, the communication manager 1020 may include a communication component 1025, a reference signal component 1030, a frequency correction component 1035, a UE capability component 1040, a channel estimation component 1045, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of 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.
[0131] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. The communication component 1025 may be configured to or otherwise support a component for sending a request to report one or more frequency corrections to a UE, the request including an indication of one or more reporting parameters for the one or more frequency corrections. The reference signal component 1030 may be configured to or otherwise support a component for sending a set of one or more reference signals associated with performing the one or more frequency corrections at the UE. The frequency correction component 1035 may be configured to or otherwise support a component for receiving a report indicating the one or more frequency corrections from the UE according to the one or more reporting parameters.
[0132] In some examples, UE capability component 1040 may be configured as or otherwise support components for receiving an indication of UE capability to report the one or more frequency corrections from the UE, wherein sending the request to report the one or more frequency corrections is based on the indication of the UE capability.
[0133] In some examples, reference signal component 1030 can be configured or otherwise support components for sending a second set of one or more reference signals after sending the set of one or more reference signals. In some examples, frequency correction component 1035 can be configured or otherwise support components for receiving a second report indicating the second set of frequency error corrections from the UE based on the one or more reporting parameters and the second set of one or more reference signals.
[0134] In some examples, channel estimation component 1045 may be configured or otherwise support components for performing channel estimation for the UE based on the report indicating the one or more frequency corrections and the second report indicating the second set of frequency error corrections.
[0135] In some examples, the report and the second report are periodic reports.
[0136] In some examples, the one or more reporting parameters indicate a periodicity for sending the report indicating the one or more frequency corrections. In some examples, the report and the second report are non-periodic reports. In some examples, the one or more reporting parameters indicate a trigger for sending the report indicating the one or more frequency corrections.
[0137] In some examples, the trigger includes receiving the set of one or more reference signals at the UE. In some examples, the set of one or more reference signals includes at least one of DMRS, TRS, or a combination thereof.
[0138] Fig.11A diagram of a system 1100 including a device 1105 supporting techniques for reporting frequency correction according to one or more aspects of the present disclosure is illustrated. The device 1105 may be an example of a device 805, a device 905, or a network entity 105 as described herein, or include components thereof. The device 1105 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1105 may include components that support output and acquisition of communications, such as a communication manager 1120, a transceiver 1110, an antenna 1115, a memory 1125, a code 1130, and a processor 1135. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1140).
[0139] The transceiver 1110 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1110 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1105 may include one or more antennas 1115, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1110 may also include a modem for modulating a signal, providing the modulated signal for transmission (e.g., via one or more antennas 1115, via a wired transmitter), receiving a modulated signal (e.g., from one or more antennas 1115, from a wired receiver), and demodulating the signal. In some implementations, the transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1115 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1115 configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1110 may include or be configured to be coupled to one or more processors or memory components that are operable to perform the following operations: perform or support operations based on received or obtained information or signals; or generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1110, or the transceiver 1110 and one or more antennas 1115, or the transceiver 1110 and one or more antennas 1115 and one or more processors or memory components (e.g., processor 1135, or memory 1125, or both) may be included in a chip or chip assembly installed in the device 1105. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).
[0140] The memory 1125 may include RAM and ROM. The memory 1125 may store computer-readable, computer-executable code 1130 including instructions that, when executed by the processor 1135, cause the device 1105 to perform various functions described herein. The code 1130 may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, the code 1130 may not be directly executable by the processor 1135, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1125 may also include a BIOS, etc., which may control basic hardware or software operations (such as interaction with peripheral components or devices).
[0141] The processor 1135 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1135. The processor 1135 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1125) to enable the device 1105 to perform various functions (e.g., various functions or tasks supporting the technology for reporting frequency correction). For example, the device 1105 or a component of the device 1105 may include a processor 1135 and a memory 1125 coupled to the processor 1135, and the processor 1135 and the memory 1125 are configured to perform various functions described herein. The processor 1135 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance), which may host functions for performing the functions of the device 1105 (e.g., by executing code 1130). The processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1105 (such as in the memory 1125). In some specific implementations, the processor 1135 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be delivered to, for example, other systems or components of the device 1105). For example, the processing system of the device 1105 may refer to a system including various other components or subcomponents of the device 1105, such as the processor 1135, or the transceiver 1110, or the communication manager 1120, or other components or combinations of components of the device 1105. The processing system of the device 1105 may interface with other components of the device 1105, and may process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or modem of the device 1105 may include a processing system and one or more interfaces for outputting information or for obtaining 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 the same interface configured to output information and obtain information, etc. In some implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 1105 can transmit information output from the chip or modem. Additionally or alternatively, in some implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, so that the device 1105 can obtain information or signal input, and the information can be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.
[0142] In some examples, bus 1140 may support communications of protocol layers (e.g., within protocol layers) of a protocol stack. In some examples, bus 1140 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1105, or communications performed between different components of device 1105 that may be co-located or may be located in different locations (e.g., where device 1105 may refer to a system in which one or more of communication manager 1120, transceiver 1110, memory 1125, code 1130, and processor 1135 may be located in one component of different components or divided between different components).
[0143] In some examples, the communication manager 1120 may manage aspects of communications with the core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communication manager 1120 may manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, the communication manager 1120 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with the UEs 115 in coordination with the other network entities 105. In some examples, the communication manager 1120 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.
[0144] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. For example, the communication manager 1120 may be configured to or otherwise support a component for sending a request to report one or more frequency corrections to a UE, the request including an indication of one or more reporting parameters for the one or more frequency corrections. The communication manager 1120 may be configured to or otherwise support a component for sending a set of one or more reference signals associated with performing the one or more frequency corrections at the UE. The communication manager 1120 may be configured to or otherwise support a component for receiving a report indicating the one or more frequency corrections from the UE according to the one or more reporting parameters.
[0145] By including or configuring the communication manager 1120 according to examples as described herein, the device 1105 may support techniques for network entities to improve channel estimation accuracy, thereby increasing communication reliability, reducing latency, and improving user experience.
[0146] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1110, one or more antennas 1115 (e.g., where applicable), or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the transceiver 1110, the processor 1135, the memory 1125, the code 1130, or any combination thereof. For example, the code 1130 may include instructions that are executable by the processor 1135 to cause the device 1105 to perform various aspects of the techniques for reporting frequency corrections as described herein, or the processor 1135 and the memory 1125 may be otherwise configured to perform or support such operations.
[0147] Fig.12 A flowchart illustrating a method 1200 for supporting techniques for reporting frequency correction according to one or more aspects of the present disclosure is illustrated. The operations of the method 1200 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 7 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.
[0148] At 1205, the method may include: receiving a request to report one or more frequency corrections from a network entity, the request including an indication of one or more reporting parameters for the one or more frequency corrections. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed as described in reference to Figure 6 The described communication component 625 is executed.
[0149] At 1210, the method may include monitoring a set of one or more reference signals associated with performing the one or more frequency corrections at the UE. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed by reference to Figure 6 The described reference signal monitoring component 630 is performed.
[0150] At 1215, the method may include: sending a report indicating the one or more frequency corrections to the network entity according to the one or more reporting parameters. The operations of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed as described in reference to Figure 6 The described frequency correction component 635 is performed.
[0151] Fig.13 A flowchart illustrating a method 1300 for supporting techniques for reporting frequency correction according to one or more aspects of the present disclosure is illustrated. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 7 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.
[0152] At 1305, the method may include sending an indication of the UE capability to report one or more frequency corrections to the network entity. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 6 The described UE capability component 640 is performed.
[0153] At 1310, the method may include: receiving a request from a network entity to report the one or more frequency corrections, the request including an indication of one or more reporting parameters for the one or more frequency corrections. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Figure 6 The described communication component 625 is executed.
[0154] At 1315, the method may include monitoring a set of one or more reference signals associated with performing the one or more frequency corrections at the UE. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed by reference to Figure 6 The described reference signal monitoring component 630 is performed.
[0155] At 1320, the method may include: sending a report indicating the one or more frequency corrections to the network entity according to the one or more reporting parameters. The operations of 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed as described in reference to Figure 6 The described frequency correction component 635 is performed.
[0156] Fig.14 A flowchart illustrating a method 1400 for supporting techniques for reporting frequency correction according to one or more aspects of the present disclosure is illustrated. The operations of the method 1400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 3 as well as Figures 8 to 11The described network entity performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.
[0157] At 1405, the method may include: sending a request to the UE to report one or more frequency corrections, the request including an indication of one or more reporting parameters for the one or more frequency corrections. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Fig.10 The described communication component 1025 is executed.
[0158] At 1410, the method may include sending a set of one or more reference signals associated with performing one or more frequency corrections at the UE. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by reference to Fig.10 The described reference signal component 1030 is performed.
[0159] At 1415, the method may include: receiving a report from the UE indicating the one or more frequency corrections according to the one or more reporting parameters. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Fig.10 The described frequency correction component 1035 is performed.
[0160] Fig.15 A flowchart illustrating a method 1500 for supporting techniques for reporting frequency correction according to one or more aspects of the present disclosure is illustrated. The operations of the method 1500 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 3 as well as Figures 8 to 11 The described network entity performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.
[0161] At 1505, the method may include: receiving from the UE an indication of the UE capability to report one or more frequency corrections. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig.10 The described UE capability component 1040 is performed.
[0162] At 1510, the method may include: sending a request to the UE to report one or more frequency corrections, the request including an indication of one or more reporting parameters for the one or more frequency corrections. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig.10 The described communication component 1025 is executed.
[0163] At 1515, the method may include: sending a set of one or more reference signals associated with performing the one or more frequency corrections at the UE. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig.10 The described reference signal component 1030 is performed.
[0164] At 1520, the method may include: receiving a report from the UE indicating the one or more frequency corrections according to the one or more reporting parameters. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Fig.10 The described frequency correction component 1035 is performed.
[0165] The following provides an overview of various aspects of the disclosure:
[0166] Aspect 1: A method for performing wireless communications at a UE, the method comprising: receiving a request to report one or more frequency corrections from a network entity, the request comprising an indication of one or more reporting parameters for the one or more frequency corrections; monitoring a set of one or more reference signals associated with performing the one or more frequency corrections at the UE; and sending a report indicating the one or more frequency corrections to the network entity based on the one or more reporting parameters.
[0167] Aspect 2: According to the method of Aspect 1, the method also includes: sending an indication of the UE capability of reporting the one or more frequency corrections to the network entity, wherein receiving the request to report the one or more frequency corrections is at least partially based on the indication of the UE capability.
[0168] Aspect 3: According to the method described in any one of Aspects 1 to 2, the method further includes: after monitoring the one group of one or more reference signals, monitoring a second group of one or more reference signals; and sending a second report indicating a second group of frequency error corrections to the network entity based on the one or more reporting parameters and the second group of one or more reference signals.
[0169] Aspect 4: The method according to aspect 3, wherein the report and the second report are periodic reports.
[0170] Aspect 5: The method according to aspect 4, wherein the one or more reporting parameters indicate a periodicity of sending the report indicating the one or more frequency corrections.
[0171] Aspect 6: The method according to any one of Aspects 3, wherein the report and the second report are non-periodic reports.
[0172] Aspect 7: The method according to any one of aspects 1 to 6, wherein the one or more reporting parameters indicate a trigger for sending the report indicating the one or more frequency corrections.
[0173] Aspect 8: The method according to aspect 7, wherein the triggering includes receiving the set of one or more reference signals at the UE.
[0174] Aspect 9: The method according to any one of aspects 1 to 8, wherein the set of one or more reference signals comprises at least one of a DMRS, a TRS, or a combination thereof.
[0175] Aspect 10: A method for performing wireless communications at a network entity, the method comprising: sending a request to a UE to report one or more frequency corrections, the request comprising an indication of one or more reporting parameters for the one or more frequency corrections; sending a set of one or more reference signals associated with performing the one or more frequency corrections at the UE; and receiving a report indicating the one or more frequency corrections from the UE based on the one or more reporting parameters.
[0176] Aspect 11: According to the method according to Aspect 10, the method also includes: receiving an indication of the UE capability to report the one or more frequency corrections from the UE, wherein the request to report the one or more frequency corrections is at least partially based on the indication of the UE capability.
[0177] Aspect 12: According to the method described in any one of Aspects 10 to 11, the method further includes: sending a second group of one or more reference signals after sending the group of one or more reference signals; receiving a second report indicating a second group of frequency error correction from the UE based on the one or more reporting parameters and the second group of one or more reference signals.
[0178] Aspect 13: The method according to aspect 12 also includes: performing channel estimation for the UE based at least in part on the report indicating the one or more frequency corrections and the second report indicating the second set of frequency error corrections.
[0179] Aspect 14: The method according to any one of aspects 12 to 13, wherein the report and the second report are periodic reports.
[0180] Aspect 15: The method according to aspect 14, wherein the one or more reporting parameters indicate a periodicity for sending the report indicating the one or more frequency corrections.
[0181] Aspect 16: The method according to any one of Aspects 12, wherein the report and the second report are non-periodic reports.
[0182] Aspect 17: The method according to any one of aspects 10 to 16, wherein the one or more reporting parameters indicate a trigger for sending the report indicating the one or more frequency corrections.
[0183] Aspect 18: The method according to aspect 17, wherein the triggering comprises receiving the set of one or more reference signals at the UE.
[0184] Aspect 19: The method according to any one of aspects 10 to 18, wherein the set of one or more reference signals comprises at least one of a DMRS, a TRS, or a combination thereof.
[0185] Aspect 20: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 9.
[0186] Aspect 21: An apparatus for wireless communication at a UE, the apparatus comprising: at least one component for performing the method according to any one of aspects 1 to 9.
[0187] Aspect 22: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 1 to 9.
[0188] Aspect 23: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 10 to 19.
[0189] Aspect 24: An apparatus for wireless communication at a network entity, the apparatus comprising: at least one component for performing the method according to any one of aspects 10 to 19.
[0190] Aspect 25: A non-transitory computer-readable medium storing a code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform a method according to any one of aspects 10 to 19.
[0191] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified and other implementations are possible. Furthermore, aspects from two or more methods may be combined.
[0192] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.
[0193] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.
[0194] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
[0195] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.
[0196] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that promotes computer program to be transmitted from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.
[0197] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Moreover, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."
[0198] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Also, "determining" may include parsing, retrieving, selecting, choosing, establishing, and other such similar actions.
[0199] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.
[0200] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.
[0201] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving, from a network entity, a request to report one or more frequency corrections, the request comprising an indication of one or more reporting parameters for the one or more frequency corrections; monitoring a set of one or more reference signals associated with performing the one or more frequency corrections at the UE; as well as A report indicating the one or more frequency corrections is sent to the network entity according to the one or more reporting parameters.
2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: An indication of UE capabilities to report the one or more frequency corrections is sent to the network entity, wherein receiving the request to report the one or more frequency corrections is based at least in part on the indication of the UE capabilities.
3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: After monitoring the set of one or more reference signals, monitoring a second set of one or more reference signals; and A second report indicating a second set of frequency error corrections is sent to the network entity based on the one or more reporting parameters and the second set of one or more reference signals.
4. The device according to claim 3, wherein: The report and the second report are periodic reports.
5. The apparatus of claim 4, wherein the one or more reporting parameters indicate a periodicity for sending the reports indicating the one or more frequency corrections.
6. The device according to claim 3, wherein: The report and the second report are aperiodic reports.
7. The apparatus of claim 1, wherein the one or more reporting parameters indicate a trigger for sending the report indicating the one or more frequency corrections.
8. The apparatus of claim 7, wherein the trigger comprises receiving the set of one or more reference signals at the UE.
9. The apparatus of claim 1, wherein the set of one or more reference signals comprises at least one of a demodulation reference signal, a tracking reference signal, or a combination thereof.
10. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending a request to a user equipment (UE) to report one or more frequency corrections, the request comprising an indication of one or more reporting parameters for the one or more frequency corrections; transmitting a set of one or more reference signals associated with performing the one or more frequency corrections at the UE; as well as A report indicating the one or more frequency corrections is received from the UE according to the one or more reporting parameters.
11. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of UE capabilities to report the one or more frequency corrections is received from the UE, wherein sending the request to report the one or more frequency corrections is based at least in part on the indication of the UE capabilities.
12. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: After sending the set of one or more reference signals, sending a second set of one or more reference signals; and A second report indicating a second set of frequency error corrections is received from the UE based on the one or more reporting parameters and the second set of one or more reference signals.
13. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: Channel estimation for the UE is performed based at least in part on the report indicating the one or more frequency corrections and the second report indicating the second set of frequency error corrections.
14. The device according to claim 12, wherein: The report and the second report are periodic reports.
15. The apparatus of claim 14, wherein the one or more reporting parameters indicate a periodicity for sending the reports indicating the one or more frequency corrections.
16. The apparatus of claim 12, wherein: The report and the second report are aperiodic reports.
17. The apparatus of claim 10, wherein the one or more reporting parameters indicate a trigger for sending the report indicating the one or more frequency corrections.
18. The apparatus of claim 17, wherein the trigger comprises receiving the set of one or more reference signals at the UE.
19. The apparatus of claim 10, wherein the set of one or more reference signals comprises at least one of a demodulation reference signal, a tracking reference signal, or a combination thereof.
20. A method for wireless communication at a user equipment (UE), the method comprising: receiving, from a network entity, a request to report one or more frequency corrections, the request comprising an indication of one or more reporting parameters for the one or more frequency corrections; monitoring a set of one or more reference signals associated with performing the one or more frequency corrections at the UE; as well as A report indicating the one or more frequency corrections is sent to the network entity according to the one or more reporting parameters.
21. The method according to claim 20, further comprising: An indication of UE capabilities to report the one or more frequency corrections is sent to the network entity, wherein receiving the request to report the one or more frequency corrections is based at least in part on the indication of the UE capabilities.
22. The method according to claim 20, further comprising: After monitoring the set of one or more reference signals, monitoring a second set of one or more reference signals; as well as A second report indicating a second set of frequency error corrections is sent to the network entity based on the one or more reporting parameters and the second set of one or more reference signals.
23. The method of claim 22, wherein the report and the second report are periodic reports.
24. The method of claim 23, wherein the one or more reporting parameters indicate a periodicity for sending the reports indicating the one or more frequency corrections.
25. The method of claim 22, wherein the report and the second report are aperiodic reports.
26. The method of claim 20, wherein the one or more reporting parameters indicate a trigger for sending the report indicating the one or more frequency corrections.
27. The method of claim 26, wherein the trigger comprises receiving the set of one or more reference signals at the UE.
28. The method of claim 20, wherein the set of one or more reference signals comprises at least one of a demodulation reference signal, a tracking reference signal, or a combination thereof.
29. A method for wireless communication at a network entity, the method comprising: sending a request to a user equipment (UE) to report one or more frequency corrections, the request comprising an indication of one or more reporting parameters for the one or more frequency corrections; transmitting a set of one or more reference signals associated with performing the one or more frequency corrections at the UE; as well as A report indicating the one or more frequency corrections is received from the UE according to the one or more reporting parameters.
30. The method according to claim 29, further comprising: An indication of UE capabilities to report the one or more frequency corrections is received from the UE, wherein sending the request to report the one or more frequency corrections is based at least in part on the indication of the UE capabilities.