Adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion

Abstract

Methods, systems, and devices for wireless communications are described. The described techniques may enable receiving devices to reduce flicker noise and signal distortions around a resource block allocation by applying a frequency offset to adjust a local oscillator frequency of the receiving device. The receiving device may predict that the resource block allocation may fall within a threshold frequency distance from the local oscillator frequency based on one or more previous resource block allocations (or one or more previous control channel decodes) falling within a threshold time duration prior to the resource block allocation. The receiving device may perform fast frequency hopping and apply the frequency offset such that the adjusted local oscillator frequency is non-overlapping with the at least one resource block allocation. The receiving device may adjust a frequency of a received signal based on the applied frequency offset, and may receive one or more downlink messages.

Description

ADAPTIVE PLACEMENT OF RECEIVER LOCAL OSCILLATOR FREQUENCY TO MITIGATE FLICKER NOISE AND SIGNAL DISTORTIONCROSS REFERENCE

[0001] The present Application for Patent claims priority to Indian Patent Application No. 202341080999 by NAGARAJAN et al., entitled ‘ADAPTIVE PLACEMENT OF RECEIVER LOCAL OSCILLATOR FREQUENCY TO MITIGATE FLICKER NOISE AND SIGNAL DISTORTION;’ filed November 29, 2023. which is assigned to the assignee hereof and expressly incorporated by reference herein.FIELD OF TECHNOLOGY

[0002] The following relates to wireless communications, including adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion.BACKGROUND

[0003] Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE).SUMMARY

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion. For example, the described techniques enable one or more receiving devices (e.g., user equipment (UE)) to predict a future resource block allocation and use fast frequency hopping to apply a frequency offset to adjust a local oscillator frequency of the receiving device such that the resource block allocation experiences reduced flicker noise and signal distortion (e.g., the flicker noise and signal distortion move with the local oscillator frequency). For example, a receiving device may predict that the resource block allocation may fall within a threshold frequency distance from the local oscillator frequency based on one or more previous resource blocks occurring prior to the resource block allocation. The receiving device may identify and apply a frequency offset to a receiver local oscillator frequency such that the adjusted local oscillator frequency is non-overlapping with the at least one resource block allocation. The receiving device may adjust a frequency of a downcon verted received signal based on the applied frequency offset and receive one or more downlink messages.

[0005] A method for wireless communications by a receiving device is described. The method may include applying a frequency offset to adjust a local oscillator frequency of the receiving device according to a prediction of at least one resource block allocation to the receiving device, the at least one resource block allocation falling within a threshold frequency distance from the local oscillator frequency, where the adjusted local oscillator frequency is non-overlapping with the at least one resource block allocation based on application of the frequency offset, adjusting a frequency of a do wncon verted received signal based on the applied frequency offset, and receiving one or more downlink messages in accordance with the applied frequency offset and the adjusted local oscillator frequency of the downconverted received signal.

[0006] A receiving device for wireless communications is described. The receiving device may include one or more processors and one or more memories coupled with the one or more processors, and one or more processor-readable instructions stored in the one or more memories and executable by the one or more processors to individually or collectively cause the receiving device to apply a frequency offset to adjust a localoscillator frequency of the receiving device according to a prediction of at least one resource block allocation to the receiving device, the at least one resource block allocation falling within a threshold frequency distance from the local oscillator frequency, where the adjusted local oscillator frequency is non-overlapping with the at least one resource block allocation based on application of the frequency offset, adjust a frequency of a down con verted received signal based on the applied frequency offset, and receive one or more downlink messages in accordance with the applied frequency offset and the adjusted local oscillator frequency of the downconverted received signal.

[0007] Another receiving device for wireless communications is described. The receiving device may include means for applying a frequency offset to adjust a local oscillator frequency of the receiving device according to a prediction of at least one resource block allocation to the receiving device, the at least one resource block allocation falling within a threshold frequency distance from the local oscillator frequency, where the adjusted local oscillator frequency is non-overlapping with the at least one resource block allocation based on application of the frequency offset, means for adjusting a frequency of a downconverted received signal based on the applied frequency offset, and means for receiving one or more downlink messages in accordance with the applied frequency offset and the adjusted local oscillator frequency of the downconverted received signal.

[0008] A non-transitoiy computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to apply a frequency offset to adjust a local oscillator frequency of the receiving device according to a prediction of at least one resource block allocation to the receiving device, the at least one resource block allocation falling within a threshold frequency distance from the local oscillator frequency, where the adjusted local oscillator frequency is non-overlapping with the at least one resource block allocation based on application of the frequency offset, adjust a frequency of a downconverted received signal based on the applied frequency offset, and receive one or more downlink messages in accordance with the applied frequency offset and the adjusted local oscillator frequency of the downconverted received signal.

[0009] In some examples of the method, receiving devices, and non- transitory computer-readable medium described herein, applying the frequency offset to adjust thelocal oscillator frequency of the receiving device may include operations, features, means, or instructions for predicting the at least one resource block allocation falls within the threshold frequency distance from the local oscillator frequency based on one or more previous resource block allocations occurring within a threshold duration prior to the at least one resource block allocation.

[0010] In some examples of the method, receiving devices, and non-transitory computer-readable medium described herein, the prediction of the at least one resource block allocation to the receiving device may be based on an artificial intelligence model, one or more machine learning algorithms, or any combination thereof.

[0011] In some examples of the method, receiving devices, and non-transitory computer-readable medium described herein, applying the frequency offset to adjust the local oscillator frequency of the receiving device may include operations, features, means, or instructions for performing fast frequency hopping and applying the frequency offset before one or more orthogonal frequency division multiplexing (OFDM) symbols allocated for a physical downlink shared channel (PDSCH) based on the prediction of the at least one resource block allocation. In some examples of the method, receiving devices, and non-transitory computer-readable medium described herein, the frequency offset may be applied during a cyclic prefix (CP) of an OFDM symbol preceding the one or more OFDM symbols.

[0012] In some examples of the method, receiving devices, and non-transitory computer-readable medium described herein, applying the frequency offset to adjust the local oscillator frequency of the receiving device may include operations, features, means, or instructions for applying the frequency offset to the local oscillator frequency based on a probability of the at least one resource block allocation falling within the threshold frequency distance from the local oscillator frequency being greater than a threshold probability.

[0013] Some examples of the method, receiving devices, and non-transitory' computer-readable medium described herein may further include operations, features, means, or instructions for performing additional fast frequency hopping to disable application of the frequency offset based on a probability of the at least one resource block allocation falling within the threshold frequency distance from the local oscillatorfrequency being less than a threshold probability. In some examples of the method, receiving devices, and non-transitory computer-readable medium described herein, the threshold frequency distance includes a threshold quantity of resource blocks from the local oscillator frequency.

[0014] In some examples of the method, receiving devices, and non-transitory computer-readable medium described herein, may include further operations, features, means, or instructions for downconverting a received signal based on application of the frequency offset to the adjusted local oscillator frequency.

[0015] Some examples of the method, receiving devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for selecting a magnitude of the frequency offset based on a noise profile which may be a function of the frequency offset from the local oscillator frequency, a partial quantity of resource block allocations, or any combination thereof.

[0016] Some examples of the method, receiving devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for adjusting at least one or more parameters associated with a baseband filter of the receiving device based on a magnitude of the frequency offset exceeding an offset threshold, adjusting a sampling frequency of an analog-to-digital converter (ADC) for the receiving device based on the magnitude of the frequency offset satisfying the offset threshold, or both.

[0017] In some examples of the method, receiving devices, and non-transitory computer-readable medium described herein, adjusting the frequency of the do wncon verted received signal may include operations, features, means, or instructions for cancelling one or more effects of the applied frequency offset via a digital rotator at a modem of the receiving device.

[0018] In some examples of the method, receiving devices, and non-transitory computer-readable medium described herein, the frequency offset includes a low intermediate frequency (LIF) offset. In some examples of the method, receiving devices, and non-transitory computer-readable medium described herein, the at least one resource block allocation includes a partial resource block allocation or a full resource block allocation.BRIEF DESCRIPTION OF THE DRAWINGS

[0019] FIGs. 1, 2, and 3 show examples of wireless communications systems that support adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with one or more aspects of the present disclosure.

[0020] FIG. 4 shows an example of a process flow that supports adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with one or more aspects of the present disclosure.

[0021] FIGs. 5 and 6 show block diagrams of devices that support adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with one or more aspects of the present disclosure.

[0022] FIG. 7 shows a block diagram of a communications manager that supports adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with one or more aspects of the present disclosure.

[0023] FIG. 8 shows a diagram of a system including a device that supports adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with one or more aspects of the present disclosure.

[0024] FIGs. 9 through 11 show flowcharts illustrating methods that support adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION

[0025] Some wireless communications devices such as network entities or other scheduling devices located within a wireless communications system may provide resource block allocations to a receiving device, such as a user equipment (UE), so that the UE may know which resources to monitor for downlink communications. In some cases, however, the UE may receive a resource block allocation that occurs relatively close to a local oscillator frequency, which may lead to a significant amount of flicker noise and degraded receiver sensitivity. Specifically, when the resource block allocation is relatively narrow (e.g., one or two resource blocks, a partial resource blockallocation) and centered around the local oscillator frequency, the receiving device may experience significant noise, increased power spectral density resulting in second order signal distortion, and power leakage, among other challenges, that have a notable impact on voice call coverage and data rate performance for the receiving device.

[0026] The receiving device may perform fast frequency hopping by applying a frequency offset (e.g., a low intermediate frequency (LIF) offset) to the receiver local oscillator frequency. For example, the receiving device may adjust the local oscillator frequency outside of the resource block allocation, which may significantly reduce noise and signal distortion of the received signal (e.g.. relative to noise and signal distortion with no frequency offset).

[0027] In some examples, the receiving device may predict a partial resource block allocation based on a history of receiving previous resource block allocations, or a history of control channel decodes. In some cases, the receiving device may predict the resource block allocation using the history of resource block allocations as input for a machine learning model or other artificial intelligence model. Upon predicting the resource block allocation, the receiving device may apply the frequency offset by performing frequency hopping (e.g., fast frequency hopping) of a local oscillator frequency. For example, the receiving device may perform frequency hopping in order to adjust the local oscillator frequency outside of the predicted resource block allocation. In such cases, the fast frequency hopping and application of the frequency offset may occur before reception of downlink data via the resource block allocation. The receiving device may undo the impact of the frequency hopping at the receiver, such that the modem of the receiver does not experience any impact from the frequency hopping, and may receive one or more downlink messages from the network entity in accordance with the applied frequency offset.

[0028] Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion.

[0029] FIG. 1 shows an example of a wireless communications system 100 that supports adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE- Advanced (LTE- A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

[0032] As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or morecomponents, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a 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 1 15, 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 yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

[0033] In some examples, network entities 105 may communicate with the core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g.. in accordance with an S I, N2. N3. or other interface protocol). In some examples, network entities 105 may communicate with one another via a backhaul communication link 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via a core network 130). In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol), or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link), one or more wireless links (e.g., a radio link, a wireless optical link), among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

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

[0035] In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities 105, such as an integrated access backhaul (I AB) 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, a network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT RIC). a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU). a virtual DU (VDU), a virtual RU (VRU)).

[0036] The split of functionality between a CU 160. a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency (RF) functions, and any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layersof the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 1 0 may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service data adaption protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (LI) (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 a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g.. via one or more RUs 170). In some cases, a functional split between a CU 160 and a DU 165, or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160. the DU 165, or the RU 170). A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e.g., Fl, Fl-c, Fl-u), and a DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that are in communication via such communication links.

[0037] In wireless communications systems (e.g., wireless communications system 100). infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130). 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 a donor entity or an IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled byone or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). The one or more donor network entities 105 (e.g., IAB donors) may be in communication with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). IAB nodes 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs 165 of a coupled IAB donor. An IAB-MT may include an independent set of antennas for relay of communications with UEs 115, or may share the same antennas (e g., of an RU 170) of an IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g.. referred to as virtual IAB-MT (vIAB-MT)). In some examples, the IAB nodes 104 may include DUs 165 that support communication links with additional entities (e.g., IAB nodes 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream). In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of IAB nodes 104) may be configured to operate according to the techniques described herein.

[0038] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion 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 disaggregated RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180).

[0039] A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the ‘‘device'’ may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (loT) device, an Internet of Everything (loE) device, or a machine type communications (MTC) device, among other examples, which may beimplemented in various objects such as appliances, or vehicles, meters, among other examples.

[0040] The UEs 115 described herein may be able to communicate with various ty pes of devices, such as other UEs 115 that may sometimes act as relays as well as the network entities 105 and the network equipment including macro eNBs or gNBs. small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.

[0041] The UEs 115 and the network entities 105 may wirelessly communicate with one another via one or more communication links 125 (e.g., an access link) using resources associated with one or more carriers. The term “carrier’ may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links 125. For example, a carrier used for a communication link 125 may include a portion of a RF spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more phy sical 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 that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g.. entity, subentity) of a network entity 105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0042] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absoluteRF channel number (EARFCN)) and may be identified according to a channel raster for discovery’ by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different radio access technology).

[0043] The communication links 125 shown in the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to cany’ downlink and uplink communications (e.g., in a TDD mode).

[0044] A carrier may be associated with a particular bandwidth of the RF spectrum, and, in some examples, the carrier bandwidth may be referred to as a '‘system bandwidth” of the carrier or the wireless communications system 100. For example, the carrier bandw idth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3. 5, 10, 15, 20. 40. or 80 megahertz (MHz)). Devices of the wireless communications system 100 (e.g., the network entities 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwddth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandw idth.

[0045] Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inverselyrelated. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam), and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.

[0046] One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (A / ) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.

[0047] The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts= l / ( fmax■seconds, for which fmaxmay represent a supported subcarrier spacing, and Nf may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

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

[0049] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g.. in bursts of shortened TTIs (sTTIs)).

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

[0051] The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low -latency communications (URLLC). The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliablecommunications may include private communication or group communication and may be supported by one or more sendees 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.

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

[0053] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility' (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility7, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g.. base stations 140) associated with the core network 130. User IP packets maybe transferred through the user plane entity, which may provide TP address allocation as well as other functions. The user plane entity may be connected to IP sendees 150 for one or more network operators. The IP services 150 may include access to the Internet. Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

[0054] The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g.. less than 100 kilometers) compared to communications using the smaller frequencies and longer weaves of the high frequency (HF) or very7high frequency (VHF) portion of the spectrum below7300 MHz.

[0055] The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology7, or NR technology7using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0056] A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity7105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

[0057] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

[0058] In some examples, a UE 115 may use fast frequency hopping techniques to receive downlink communications and to transmit uplink communications. In one example, the UE 115-a may achieve a phase lock loop (PLL) lock to a new frequency (e.g., the resulting local oscillator frequency after applying the offset) in a very short period of time. A settling time specifies how fast the PLL arrives at the new frequency when changing or hopping frequencies. In some examples, the UE 115 may include a voltage controlled oscillator (VCO). a phase detector, a loop filter (e.g., low pass filter),a control unit, and a frequency divider (e.g., integer-N synthesizer or fractional synthesizer).

[0059] In some examples, the fast frequency hopping implementation may be based on single point modulation to reduce settling time. For example, the UE 115 may adjust the frequency divider to achieve the frequency hopping. In other examples, the fast frequency hopping implementation may be based on a two-point modulation to reduce settling time. For example, the VCO of the UE may receive an input voltage from the loop filter and a frequency step (e.g., the frequency offset) scaled by the control unit. In some examples, the frequency divider may receive an output of the VCO based on the frequency step injected at the input of the VCO as well as an injection of the frequency step at an input port of the frequency divider.

[0060] In some implementations, the network entity 105 may provide resource block allocations to a receiving device, such as the UE 115, so that the UE 115 may know which resources to monitor for downlink communications. In some cases, however, the UE 115 may receive a resource block allocation that occurs relatively close to a local oscillator frequency, which may lead to a significant amount of flicker noise and degraded sensitivity7. Specifically, when the resource block allocation is relatively narrow and centered around the local oscillator frequency, the UE 115 may experience significant noise, increased power spectral density resulting in second order signal distortion, and power leakage, among other challenges, that have a notable impact on voice call coverage and data rate performance for the UE 115.

[0061] To reduce the impact of flicker noise for resource block allocations occurring relatively close to the local oscillator frequency, the UE 115 may perform fast frequency hopping to apply a frequency offset (e.g.. a LIF offset) to the local oscillator frequency. The application of the frequency offset may allow the UE 115 to adjust the local oscillator frequency outside of the resource block allocation. In some examples, the UE 115 may predict a partial resource block allocation based on receiving previous resource block allocations or based on a history of past control channel decodes. In some examples, the UE 115 may perform the frequency hopping (e.g., fast frequency hopping) of the receiver-side local oscillator frequency to apply the frequency offset and adjust the local oscillator frequency outside of the predicted resource block allocation. Then, the UE 115 may undo the impact of the frequency hopping at the receiver, suchthat the modem of the receiver does not experience any impact from the frequency hopping, and receive one or more downlink messages from the network entity 105 in accordance with the applied frequency offset.

[0062] FIG. 2 shows an example of a wireless communications system 200 that supports adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with one or more aspects of the present disclosure. In some examples, the wireless communications system 200 may implement or be implemented by aspects of the wireless communications system 100. For example, the wireless communications system 200 may include one or more network entities 105 (e.g., network entity 105-a) and one or more UEs 115 (e.g., UE 115-a), which may be examples of the corresponding devices as described with reference to FIG. 1. In some examples, a receiving device (e.g., the UE 115-a) may adaptively place a local oscillator frequency to mitigate flicker noise and signal distortion associated with one or more communications 202 with a transmitting device (e.g., the network entity 105-a).

[0063] In some examples (e.g., in lower technology nodes with high power densities relative to higher technology nodes), flicker noise may impact receiver sensitivity performance. For example, a sensitivity of the receiving device may be reduced in cases where the receiving device receives a resource block allocation that is located around a relatively low frequency offset from the receiving device’s local oscillator (e.g., overlapping with or within a threshold frequency distance of a direct current (DC) subcarrier). In some examples, the resource block allocation may include a partial resource block allocation or a full resource block allocation. In some examples, the resource block allocation may be as narrow as one resource block (e.g.. for a voice call in voice-over LTE (VoLTE)).

[0064] In some cases, however, the sensitivity’ performance of the receiving device may be negatively affected when the resource block allocation is narrow (e.g., one or two resource blocks, or a partial resource block allocation) and is allocated around low frequencies post downconversion of a received signal (e.g., a low frequency offset from the local oscillator frequency at RF). In some cases, the relatively low frequencies may be less than or equal to (but not limited to) 50 kHz from the local oscillator frequency, or any frequency in which receiver sensitivity is degraded. In some examples, sensitivity degradation may occur for one resource block allocation when the totalquantity of resource blocks is odd (e.g., LTE 5 MHz bandwidth), or for two resource block allocations when the total quantity of resource blocks is even (e.g., LTE 20 MHz bandwidth).

[0065] In some examples, such as in uplink single resource block or partial resource block allocations, increased power spectral density may cause signal distortion (e.g., second order distortion, IM2) because of transmission leakage appearing at the input of a low noise amplifier (LNA) (e.g., due to limited isolation of the duplexer). In such examples, the resulting second order distortion (e.g., IM2) may negatively affect the sensitivity of the receiver. In some cases, the second order distortion may also affect downlink resource blocks around low frequencies post downconversion. In some examples, the reduced sensitivity of the receiver for resource block allocation may adversely impact the performance of the receiver (e.g., coverage, voice call, and data rate performance, among other examples).

[0066] Accordingly, the techniques described herein may support adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion for a resource block allocation falling within a threshold distance from the local oscillator frequency. For example, the UE 115-a may predict a resource block allocation 210 (e.g., a future resource block allocation) from one or more communications 202 (e.g.. one or more previous resource block allocations or control channel decodes). In some cases, the resource block allocation 210 may be a partial resource block allocation. In some examples, the UE 115-a may predict the resource block allocation 210 based on a history of allocations (e.g., a history of control channel decodes) received from the network entity 105-a or another device located in wireless communications system 200.

[0067] In some cases, the resource block allocation 210 may be located at a frequency offset from a local oscillator frequency in the receiver of the UE 115-a (e.g., within a threshold frequency distance of the local oscillator frequency). For example, the resource block allocation 210 may overlap, or partially overlap, with the local oscillator frequency 220-a around a relatively low frequency offset (e.g., 50 kHz or less) from the local oscillator frequency 220-a (e.g., within the threshold frequency distance of the DC subcarrier) in a channel 205-a. Additionally, or alternatively, the resource block allocation 210 may fall on a lower side of the local oscillator frequency 220-b in achannel 205-b, fall on an upper side of the local oscillator frequency 220-c in a channel 205-c, or any combination thereof.

[0068] In some examples, a magnitude of noise 215 associated with the receiver (e.g., noise 215-a, noise 215-b, noise 215-c) may be associated with the placement of the local oscillator frequency 220. For example, the magnitude of noise 215 may follow the local oscillator such that the magnitude of noise 215 may increase for frequencies closer to DC (e.g., for frequencies post downconversion). In some examples, the magnitude of noise 215 may increase when the resource block allocation is near lower frequencies of the local oscillator (e.g., 220-a, 220-b, and 220-c).

[0069] To reduce the effect of increased noise and signal distortion at some resource block allocations that fall close to the DC post downconversion, the UE 1 15-a may use frequency hopping 225 -a, 225 -b, or 225 -c in the receiver to apply a frequency offset to the local oscillator. For example, the UE 115-a may perform fast frequency hopping where the UE 115 -a may utilize multiple frequency hops of the receiver frequency to receive one symbol. Additionally, or alternatively, the fast frequency hopping may allow the UE 115-a to utilize multiple carrier frequencies for receiving one symbol with several hops. The fast frequency hopping may also occur on a relatively shorter time scale than other frequency hopping techniques. For example, fast frequency’ hopping may occur in less than tens of microseconds, where other frequency hopping techniques may involve more time to complete. Using the fast frequency hopping techniques of the receiver local oscillator frequency, the UE 115-a may apply a LIF offset 230 (e.g., LIF offset 230-a, LIF offset 230-b, LIF offset 230-c) such that the local oscillator frequency 220 falls outside of the resource block allocation 210. and the resource block allocation 210 experiences noise that is either reduced or eliminated relative to the noise experienced at the initial local oscillator frequency. In some examples, the LIF offset 230 may be on the order of hundreds of kilohertz.

[0070] In some other cases, the resource block allocation 210 may change dynamically (e.g., in each sub-frame or slot), such that a predicted probability of the resource block allocation 210 falling close to the local oscillator frequency 220-a is less than a threshold probability, which may disable application of the LIF offset 230. Applying the LIF offset 230 via frequency hopping 225 may enable the prevention of sensitivity degradation in examples where the resource block allocation 210 may benarrow (e.g., one or two resource blocks, a partial resource block allocation) and surrounding the local oscillator frequency 220 (e.g., static LIF offset in cases without frequency hopping may not prevent sensitivity degradation).

[0071] In some examples, the UE 115-a may apply the LIF offset 230 in different relative frequency directions. For example, the UE 115-a may use frequency hopping 225-b to apply a LIF offset 230-b such that the local oscillator frequency 220-b moves in a first direction (e.g., positively) away from the resource block allocation 210. Alternatively, the UE 115-a may use frequency hopping 225-c to apply a LIF offset 230-c such that the local oscillator frequency 220-c moves in a second direction (e.g., negatively) away from the resource block allocation 210. In both cases, the magnitude of noise 215 experienced by the allocated resource blocks may be reduced (e.g., when the local oscillator frequency 220-b moves in the first direction or when the local oscillator frequency 220-c moves in the second direction). In some cases, additional frequency hopping may be used to disable the application of the LIF offset 230 based on the predicted probability of the resource block allocation 210 being less than the threshold probability'.

[0072] In some implementations, the UE 115-a may adjust, or select, the magnitude of the LIF offset 230 after downconverting the received signal. For example, the magnitude of the LIF offset 230 may be based on a small signal noise figure (ssNF) profile of the receiver as a function of frequency offset. Additionally, or alternatively, the magnitude of the LIF offset 230 may be based on a partial quantity of resource block allocations. For example, the magnitude may be based on the span of the transmission second order distortion (IM2) product falling on a receive signal when the transmission has a small quantity of resource block allocations (e.g., a quantity of transmission resource blocks is less than or equal to a quantity of total transmission resource blocks where, in some cases, the quantity of total transmission resource blocks is 1). In some cases, the magnitude of the LIF offset 230 may surpass a threshold (e.g., the magnitude may be large enough to cause edge resource block de-sense). In such cases, the UE 115-a may adjust at least one or more parameters associated with a baseband filter of the receiving device. For example, the UE 115-a may widen baseband filter poles (e.g., to reduce the signal droop and impact of analog to digital conversion (ADC) noise). Additionally, or alternatively, the UE 115-a may adjust a sampling frequency of anADC of the receiver (e.g., the UE 115-a may increase the sampling rate of the ADC to push the ADC quantization noise more outside the signal bandwidth).

[0073] In some examples, the UE 115-a may perform one or more adjustments to a frequency of a downconverted received signal based on applying the LIF offset 230 (or to compensate for the applied LIF offset) using frequency hopping 225. For example, the UE 115-a may cancel one or more effects of the frequency hopping 225 and the LIF offset 230 via a digital rotator at a modem of the receiving device (e.g., the UE 115-a may undo the impact of frequency hopping 225 at the digital rotator so that the modem may not experience the impact of the shift in the local oscillator frequency). In some examples, the received signal may be downconverted based on application of the frequency offset to the adjusted local oscillator frequency.

[0074] FIG. 3 shows an example of a wireless communications system 300 that supports adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with one or more aspects of the present disclosure. In some examples, the wireless communications system 300 may implement or be implemented by aspects of the wireless communications system 100 and 200. For example, the wireless communications system 300 may include one or more network entities 105 (e.g.. a network entity 105-b) and one or more UEs 115 (e.g.. a UE 115-b). which may be examples of the corresponding devices as described with reference to FIGs. 1 and 2. In some examples, a receiving device (e.g., the UE 115-b) may adaptively place a local oscillator frequency to mitigate flicker noise and signal distortion associated with one or more communications with a transmitting device (e.g., the network entity 105-a) according to receiving a downlink message 301.

[0075] In some examples, the downlink message 301 may include a quantity of OFDM symbols, each of which including a cyclic prefix (CP) 303 to reduce intersymbol interference, and each of the quantity of OFDM symbols being included in the message 301 (e.g., CP 303-a for physical downlink control channel (PDCCH) 305, CP 303-b for physical downlink shared channel (PDSCH) 310-a, CP 303-c PDSCH 310-b. CP 303-d PDSCH 310-c). In some examples, the PDCCH 305 may be in any of the quantity of symbols. Additionally, or alternatively, the PDCCH 305 may span multiple symbols of the quantity of symbols. In some cases, the location and span of the PDCCH 305 may be communicated by the network entity 105-b based on system informationblock (SIB) or RRC configuration (or reconfiguration) signaling. In some cases, the quantity7of PDCCH symbols may be communicated by the network entity 105-b based on a physical control format indicator channel (PCFICH) indicating a control format indicator (CFI). For example, the PCFICH may indicate CFI = 1. Additionally, while PDSCH 310-a is illustrated as adjacent to PDCCH 305, in some examples, PDSCH 310-a may not be adjacent to PDCCH 305 (e.g., the PDSCH symbols may be a few symbols away from the PDCCH symbols within a same slot).

[0076] In some cases, downlink resource block allocation information may be encoded in the PDCCH 305. In such cases, the resource block allocation information may precede one or more PDSCHs. In some implementations, the UE 115-b may the PDCCH 305 prior to decoding a PDSCH (e.g., PDSCH 310-a). In some examples, the resource block allocation associated with the PDSCH 310-a may not be decoded until the UE 115-b decodes the PDCCH 305. In some cases, a duration 320 to decode the PDCCH 305 may be longer than a duration of a CP 303 (e.g.. the duration from 315 to 325-a of CP 303-b). In some examples, the duration 320 to decode the PDCCH 305 may be based on one or more parameters of the UE 115-b, for example, based on the hardware of the UE 115-b, one or more properties of the firmware of the UE 115-b, a clock frequency of the UE 115-b, latencies (e.g., receiving latency, processing latency, transmission latency) associated with the UE 115-b, or any combination thereof.

[0077] In some examples, the UE 115-b may complete frequency hopping at or before a duration tA 325-a (e.g., a duration from reference point 315 to tA 325-a). In some cases, the duration tn 325-b (e.g., a duration from reference point 315 to tn 325-b) may represent a duration in which DCI containing resource block allocation from PDSCH 310-a may be decoded from PDCCH 305.

[0078] In some cases, a duration tc 325-c (e g., a duration from reference point 315 to tc 325-c of a CP 303-d) may represent a duration in which the UE 115-b may use frequency hopping based on the duration tB 325-b to decode the PDCCH 305 (e.g., the earliest duration when frequency hopping may start). In such cases, the duration tc 325-c may be longer than the duration tA 325-a. In these cases, the UE 115-b may not adjust a frequency of the local oscillator and enable LIF offset mitigation before receiving samples of the PDSCH 310-a based on PDCCH 305. In other words, the UE 115-b may implement techniques to perform frequency hopping on a shorter time scalerelative to normal frequency hopping (e.g., the UE 1 15-b may implement fast frequency hopping techniques of a receiver local oscillator frequency) to receive dow nlink communications with less noise and higher accuracy.

[0079] Accordingly, to reduce signal noise more effectively while also accommodating the fast time scales for receiving data, the techniques described herein may support a capability of the UE-b to accurately predict the resource block allocation of the PDSCH 310-a, such that fast frequency hopping and local oscillator placement or adjustment may occur before the UE 115-b receives the PDSCH 310-a, such that no downlink data is lost due to ongoing decoding. In some examples, the UE 115-b may predict a future or current resource block allocation using a history of past resource block allocations (e.g., a history of PDCCH decodes), and may use frequency hopping during the duration tA 325-a to apply the LIF before receiving the PDSCH 310-a. In some examples, the UE 115-b may apply the LIF during the CP 303 of any symbol (provided that the LIF is applied before receiving the PDSCH 310-a). For example, the UE 1 15-b may apply the LIF during CP 303-b, CP 303-c, CP 303-d, or any combination thereof (e.g., the duration of the CP 303 may be a buffer time zone during which the UE 115-b may make changes to the receiver parameters without affecting decode performance). In such examples, performing frequency hopping during the duration t 325-a may enable the UE 115-b to significantly reduce the capture of one or more RF transients (e.g., by a modem of the UE 115-b). The prediction of the resource block allocation is discussed in further detail with reference to FIG. 4.

[0080] FIG. 4 shows an example of a process flow 400 that supports adaptive placement of a receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with one or more aspects of the present disclosure. In the following description of the process flow 400, the operation betw een the UE 115-c and the network entity7105-c may be transmitted in a different order shown. In some implementations, the UE 115-c may include a receiver. Some operations may also be omitted from the process flow 400, and other operations may be added to the process flow 400. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may occur at the same time.

[0081] At 405, the UE 115-c may optionally receive one or more resource block allocations (e.g., an allocation of one or more resource blocks for the UE 115-c toreceive communications via a downlink channel). In some examples, the UE 1 15-c may identify the one or more previous resource block allocations occurring within a threshold time duration prior to the resource block allocation. In some cases, the resource block allocation may include a partial resource block allocation or a full resource block allocation.

[0082] At 410, the UE 115-c may predict that a resource block allocation falls (e.g., will occur) within a threshold frequency distance from the local oscillator frequency based on a history' of past PDCCH decodes (e.g., based on past resource block allocations). In some examples, the threshold frequency distance may include a threshold quantity of resource blocks from the local oscillator frequency. In some examples, the UE 115-c may monitor one or more channels to receive downlink communications. In some cases, each channel may include a DC subcarrier. In some examples (e.g.. in carrier aggregation scenarios), the local oscillator frequency may be a central subcarrier, or may be placed at any location. In some examples, the UE 115-c may predict that the resource block allocation will occur based on the one or more previous resource block allocations. Additionally, or alternatively, the UE 115-c may predict that the resource block allocation will occur based on an artificial intelligence model, one or more machine learning algorithms, or any combination thereof.

[0083] In some implementations, the UE 115-c may predict that the resource block allocation will occur based on a probability of the resource block allocation occurring within a threshold frequency distance from the local oscillator frequency being greater than a threshold probability'. For example, the UE 115-c may measure a probability that the resource block allocation will occur within a threshold distance (e.g., N RB distance, where N is an integer) around the local oscillator frequency. Then, based on the probability7of the resource block allocation occurring w ithin a distance being less than the threshold distance, the UE 115-c may refrain from applying the LIF (e.g., disable the LIF). In some other examples, the probability of the resource block allocation occurring w ithin a distance may exceed the threshold distance around the local oscillator frequency. Then, based on the probability of the resource block allocation occurring within a distance exceeding the threshold distance, the UE 115-c may apply the LIF. In some examples, the rate of change of the resource block allocation may exceed a resource block allocation threshold (e.g., the resource block allocation may be relativelydynamic), such that a predicted probability of the resource block allocation falling close to the local oscillator frequency is less than a threshold probability, which may (automatically) disable application of the LIF offset.

[0084] At 415, the UE 115-c may optionally select a magnitude of a frequency offset (e.g.. a LIF offset) to apply to the local oscillator frequency. For example, the UE 115-c may select the magnitude of the frequency offset based on a noise profile associated with the receiving device (e.g., based on a function of the frequency offset from the local oscillator frequency), a partial quantity of resource block allocations, or both. At 420. the UE 115-c may optionally adjust one or more parameters of the receiver based on the magnitude of the frequency offset exceeding an offset threshold. For example, the UE 115-c may adjust at least one or more parameters of a baseband filter of the receiving device based on the frequency offset exceeding the offset threshold. Additionally, or alternatively, the UE 115-c may adjust a sampling frequency of an ADC for the receiving device based on the magnitude of the frequency offset satisfying the offset threshold.

[0085] At 425, the UE 115-c may apply the frequency offset to the local oscillator frequency. In some examples, a local oscillator frequency of the UE 115-c may partially overlap with the threshold frequency distance. In some examples, the local oscillator frequency may be non-overlapping with the resource block allocation based on the application of the frequency offset. In some examples, the UE 115-c may apply the frequency offset using one or more frequency hopping techniques. For example, the UE 115-c may implement fast frequency hopping techniques to apply multiple frequency hops to the receiver local oscillator frequency for receiving one symbol, and the fast frequency hopping may occur on a time scale that is less than other frequency hopping techniques (e.g., less than tens of microseconds).

[0086] In some examples, the UE 115-c may apply the frequency offset before one or more symbols allocated for a PDSCH (e.g., the received PDSCH) based on the at least one resource allocation prediction. For example, the UE 115-c may apply the frequency offset during the cyclic prefix of an OFDM symbol preceding the one or more OFDM symbols allocated for the PDSCH . In some examples, the UE 115-c may apply the frequency offset based on the probability of the resource block allocation occurring within the threshold frequency distance being greater than the thresholdprobability. For example, the UE 1 15-c may apply the frequency offset in a first direction or a second direction (relative to the unadjusted local oscillator frequency) based on the probability being greater than the threshold probability. In some examples, the UE 115-c may disable the application of the frequency offset based on the probability of the resource block allocation occurring within the threshold frequency distance from the local oscillator frequency being less than a threshold probability. In some cases, the UE 115-c may perform additional frequency hopping to disable the application of the frequency offset. In some implementations, the UE 115-c may apply the frequency offset based on a rate of change of resource block allocations being less than a threshold (e.g., if the resource block allocation changes rapidly, the de-sense impact at the receiver may be low).

[0087] At 430, the UE 115-c may perform one or more adjustments to a frequency of a downconverted received signal based on the applied frequency offset. For example, the UE 115-c may cancel, via a digital rotator at a modem of the receiving device, one or more effects of the applied frequency offset. In some cases, the UE 115-c may cancel one or more effects of the fast frequency hopping to apply frequency offset. In some examples, the UE 115-c may adjust the frequency of the downconverted received signal based on downconverting the received signal based on application of the frequency offset to the adjusted local oscillator frequency. At 435, the UE 1 15-c may receive one or more downlink messages in accordance with the applied frequency offset and the one or more adjustments. For example, the UE 115-c may optionally receive a PDCCH. In some examples, the PDCCH may include an indication of a resource block allocation. In some examples, the PDCCH may be in any of the quantity of symbols. Additionally, or alternatively, the PDCCH may span multiple symbols of the quantity’ of symbols. In some cases, the location and span of the PDCCH may be communicated by the network entity 105-c based on SIB or RRC reconfiguration signaling. In some cases, the quantity of PDCCH symbols may be communicated by the network entity 105-c based on a CFI indicated by a PCFICH. In some other examples, the UE 1 15-c may receive a PDSCH after applying the applied frequency offset.

[0088] FIG. 5 shows a block diagram 500 of a device 505 that supports adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with one or more aspects of the present disclosure. The device505 may be an example of aspects of a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505, or one or more components of the device 505 (e.g., the receiver 510, the transmitter 515, and the communications manager 520). may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0089] The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion). Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.

[0090] The transmitter 515 may provide a 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 adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion). In some examples, the transmitter 515 may be co-located with a receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a set of multiple antennas.

[0091] The communications manager 520, the receiver 510, the transmitter 515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion as described herein. For example, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0092] In some examples, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented inhardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a digital signal processor (DSP), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g.. by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0093] Additionally, or alternatively, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0094] In some examples, the communications manager 520 may be configured to perform various operations (e.g.. receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510. the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0095] The communications manager 520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 520 is capable of, configured to, or operable to support a means for applying a frequency offset to adjust a local oscillator frequency of the receiving device according to a prediction of at least one resource block allocation to the receiving device, the atleast one resource block allocation falling within a threshold frequency distance from the local oscillator frequency, where the adjusted local oscillator frequency is nonoverlapping with the at least one resource block allocation based on application of the frequency offset. The communications manager 520 is capable of, configured to, or operable to support a means for adjusting a frequency of a downconverted received signal based on the applied frequency offset. The communications manager 520 is capable of, configured to, or operable to support a means for receiving one or more downlink messages in accordance with the applied frequency offset and the adjusted frequency of the received signal.

[0096] By including or configuring the communications manager 520 in accordance with examples as described herein, the device 505 (e.g., at least one processor controlling or otherwise coupled with the receiver 510, the transmitter 515, the communications manager 520. or a combination thereof) may support techniques for reduced processing, reduced power consumption, more efficient utilization of communication resources, among other advantages.

[0097] FIG. 6 shows a block diagram 600 of a device 605 that supports adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with one or more aspects of the present disclosure. The device 605 may be an example of aspects of a device 505 or a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605, or one or more components of the device 605 (e.g., the receiver 610, the transmitter 615, and the communications manager 620), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0098] The receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion). Information may be passed on to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.

[0099] The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion). In some examples, the transmitter 615 may be co-located with a receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.

[0100] The device 605, or various components thereof, may be an example of means for performing various aspects of adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion as described herein. For example, the communications manager 620 may include a frequency offset component 625, a frequency adjust component 630, a downlink messaging component 635, or any combination thereof. The communications manager 620 may be an example of aspects of a communications manager 520 as described herein. In some examples, the communications manager 620, or various components thereof, may be configured to perform various operations (e.g.. receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610. the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0101] The communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The frequency offset component 625 is capable of, configured to, or operable to support a means for applying a frequency offset to adjust a local oscillator frequency of the receiving device according to a prediction of at least one resource block allocation to the receiving device, the at least one resource block allocation falling within a threshold frequency distance from the local oscillator frequency, where the adjusted local oscillator frequency is non-overlapping with the at least one resource block allocation based on application of the frequency offset. The frequency adjust component 630 is capable of, configured to, or operable to support a means for adjusting a frequency of a downconverted received signal based on theapplied frequency offset. The downlink messaging component 635 is capable of, configured to, or operable to support a means for receiving one or more downlink messages in accordance with the applied frequency offset and the adjusted frequency of the received signal.

[0102] FIG. 7 shows a block diagram 700 of a communications manager 720 that supports adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with one or more aspects of the present disclosure. The communications manager 720 may be an example of aspects of a communications manager 520. a communications manager 620, or both, as described herein. The communications manager 720, or various components thereof, may be an example of means for performing various aspects of adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion as described herein. For example, the communications manager 720 may include a frequency offset component 725, a frequency adjust component 730. a downlink messaging component 735, an allocation prediction component 740, a frequency hopping component 745, an allocation probability component 750, a downconverter component 755, a frequency offset magnitude component 760, a signal processing component 765, a digital rotator component 770, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0103] The communications manager 720 may support wireless communications in accordance with examples as disclosed herein. The frequency offset component 725 is capable of, configured to, or operable to support a means for applying a frequency offset to adjust a local oscillator frequency of the receiving device according to a prediction of at least one resource block allocation to the receiving device, the at least one resource block allocation falling within a threshold frequency distance from the local oscillator frequency, where the adjusted local oscillator frequency is non-overlapping with the at least one resource block allocation based on application of the frequency offset. The frequency adjust component 730 is capable of, configured to, or operable to support a means for adjusting a frequency of a do wncon verted received signal based on the applied frequency offset. The downlink messaging component 735 is capable of, configured to, or operable to support a means for receiving one or more downlinkmessages in accordance with the applied frequency offset and the adjusted frequency of the received signal.

[0104] In some examples, to support applying the frequency offset to adjust the local oscillator frequency of the receiving device, the allocation prediction component 740 is capable of, configured to. or operable to support a means for predicting the at least one resource block allocation falls within the threshold frequency distance from the local oscillator frequency based on one or more previous resource block allocations occurring within a threshold duration prior to the at least one resource block allocation.

[0105] In some examples, the prediction of the at least one resource block allocation to the receiving device is based on an artificial intelligence model, one or more machine learning algorithms, or any combination thereof.

[0106] In some examples, to support applying the frequency offset to adjust the local oscillator frequency of the receiving device, the frequency hopping component 745 is capable of, configured to, or operable to support a means for performing fast frequency hopping and applying the frequency offset before one or more OFDM symbols allocated for a physical downlink shared channel based on the prediction of the at least one resource block allocation.

[0107] In some examples, the frequency offset is applied during a cyclic prefix of an OFDM symbol preceding the one or more OFDM symbols.

[0108] In some examples, to support applying the frequency offset to adjust the local oscillator frequency of the receiving device, the allocation probability component 750 is capable of, configured to, or operable to support a means for applying the frequency offset to the local oscillator frequency based on a probability of the at least one resource block allocation falling within the threshold frequency distance from the local oscillator frequency being greater than a threshold probability.

[0109] In some examples, the allocation probability component 750 is capable of, configured to, or operable to support a means for disabling fast frequency hopping and application of the frequency offset based on a probability of the at least one resource block allocation falling within the threshold frequency distance from the local oscillator frequency being less than a threshold probability.

[0110] In some examples, the threshold frequency distance includes a threshold quantity of resource blocks from the local oscillator frequency.[OHl] In some examples, the downconverter component 755 is capable of, configured to, or operable to support a means for downconverting the adjusted received signal based on application of the frequency offset to the adjusted local oscillator frequency.

[0112] In some examples, the frequency offset magnitude component 760 is capable of, configured to, or operable to support a means for selecting a magnitude of the frequency offset based on a noise profile which is a function of the frequency offset from the local oscillator frequency, a partial quantity of resource block allocations, or any combination thereof.

[0113] In some examples, the signal processing component 765 is capable of, configured to, or operable to support a means for adjusting at least one or more parameters associated with a baseband filter of the receiving device based on a magnitude of the frequency offset exceeding an offset threshold, adjusting a sampling frequency of an analog-to-digital converter for the receiving device based on the magnitude of the frequency offset satisfying the offset threshold, or both.

[0114] In some examples, to support adjusting the frequency of the downcon verted received signal, the digital rotator component 770 is capable of, configured to, or operable to support a means for cancelling one or more effects of the applied frequency offset via a digital rotator at a modem of the receiving device.

[0115] In some examples, the frequency offset includes a low intermediate frequency offset.

[0116] In some examples, the at least one resource block allocation includes a partial resource block allocation or a full resource block allocation.

[0117] FIG. 8 shows a diagram of a system 800 including a device 805 that supports adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with one or more aspects of the present disclosure. The device 805 may be an example of or include the components of a device 505, a device 605, or a UE 115 as described herein. The device 805 may communicate(e.g., wirelessly) with one or more network entities 105, one or more UEs 1 15, or any combination thereof. The device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).

[0118] The I / O controller 810 may manage input and output signals for the device 805. The I / O controller 810 may also manage peripherals not integrated into the device 805. In some cases, the I / O controller 810 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 810 may utilize an operating system such as iOS®, ANDROID®. MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®. LINUX®, or another known operating system. Additionally, or alternatively, the I / O controller 810 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as the at least one processor 840. In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

[0119] In some cases, the device 805 may include a single antenna 825. However, in some other cases, the device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bi-directionally, via the one or more antennas 825, wired, or wireless links as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 815 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 825 for transmission, and to demodulate packets received from the one or more antennas 825. The transceiver 815, or the transceiver 815 and one or more antennas 825, may be an example of a transmitter 515, a transmitter 615, a receiver 510, a receiver 610, or any combination thereof or component thereof, as described herein.

[0120] The at least one memory 830 may include random access memory (RAM) and read-only memory7(ROM). The at least one memory 830 may store computer- readable, computer-executable code 835 including instructions that, when executed by the at least one processor 840, cause the device 805 to perform various functions described herein. The code 835 may be stored in a non-transitory computer-readable medium such as system memory7or another type of memory7. In some cases, the code 835 may not be directly executable by the at least one processor 840 but may cause a computer (e.g.. when compiled and executed) to perform functions described herein. In some cases, the at least one memory 830 may contain, among other thrngs. a basic I / O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0121] The at least one processor 840 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 at least one processor 840 may be configured to operate a memory array using a memory7controller. In some other cases, a memory controller may be integrated into the at least one processor 840. The at least one processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion). For example, the device 805 or a component of the device 805 may include at least one processor 840 and at least one memory 830 coupled with or to the at least one processor 840, the at least one processor 840 and at least one memory 830 configured to perform various functions described herein. In some examples, the at least one processor 840 may include multiple processors and the at least one memory7830 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 840 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 840) and memory7circuitry (which may include the at least one memory 830)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. As such, the at least one processor 840 or a processing system including the at least one processor 840 may be configured to, configurable to, or operable to cause the device 805 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 830 or otherwise, to perform one or more of the functions described herein.

[0122] The communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of. configured to, or operable to support a means for applying a frequency offset to adjust a local oscillator frequency of the receiving device according to a prediction of at least one resource block allocation to the receiving device, the at least one resource block allocation falling within a threshold frequency distance from the local oscillator frequency, where the adjusted local oscillator frequency is nonoverlapping with the at least one resource block allocation based on application of the frequency offset. The communications manager 820 is capable of, configured to, or operable to support a means for adjusting a frequency of a downconverted received signal based on the applied frequency offset. The communications manager 820 is capable of, configured to, or operable to support a means for receiving one or more downlink messages in accordance with the applied frequency offset and the adjusted frequency of the received signal.

[0123] By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 may support techniques for improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing capability7, among other advantages.

[0124] In some examples, the communications manager 820 may be configured to perform various operations (e.g.. receiving, monitoring, transmitting) using or otherwisein cooperation with the transceiver 815, the one or more antennas 825, or any combination thereof. Although the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the at least one processor 840, the at least one memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the at least one processor 840 to cause the device 805 to perform various aspects of adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion as described herein, or the at least one processor 840 and the at least one memory 830 may be otherwise configured to, individually or collectively, perform or support such operations.

[0125] FIG. 9 shows a flowchart illustrating a method 900 that supports adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with aspects of the present disclosure. The operations of the method 900 may be implemented by a UE or its components as described herein. For example, the operations of the method 900 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0126] At 905, the method may include applying a frequency offset to adjust a local oscillator frequency of the receiving device according to a prediction of at least one resource block allocation to the receiving device, the at least one resource block allocation falling within a threshold frequency distance from the local oscillator frequency, where the adjusted local oscillator frequency is non-overlapping with the at least one resource block allocation based on application of the frequency offset. The operations of block 905 may be performed in accordance with examples as disclosed herein, such as the resource block allocation at 410, frequency offset magnitude selection at 415, and device parameter adjustment at 420 of FIG. 4, or the various LIF applications of FIG. 2. In some examples, aspects of the operations of 905 may be performed by a frequency offset component 725 as described with reference to FIG. 7.

[0127] At 910, the method may include adjusting a frequency of a downconverted received signal based on the applied frequency offset. The operations of block 910 may be performed in accordance with examples as disclosed herein, for example, such as the offset application at 425 of FIG. 4. In some examples, aspects of the operations of 910 may be performed by a frequency adjust component 730 as described with reference to FIG. 7.

[0128] At 915, the method may include receiving one or more downlink messages in accordance with the applied frequency offset and the adjusted frequency of the received signal. The operations of block 915 may be performed in accordance with examples as disclosed herein, such as the downlink message reception of 435 of FIG. 4, or the downlink message reception illustrated in FIGs. 2 and 3. In some examples, aspects of the operations of 915 may be performed by a dow nlink messaging component 735 as described with reference to FIG. 7.

[0129] FIG. 10 shows a flowchart illustrating a method 1000 that supports adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented by a UE or its components as described herein. For example, the operations of the method 1000 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0130] At 1005, the method may include predicting the at least one resource block allocation falls within the threshold frequency distance from the local oscillator frequency based on one or more previous resource block allocations occurring within a threshold duration prior to the at least one resource block allocation. The operations of block 1005 may be performed in accordance with examples as disclosed herein, such as the resource block prediction as described with reference to FIG. 3. In some examples, aspects of the operations of 1005 may be performed by an allocation prediction component 740 as described with reference to FIG. 7.

[0131] At 1010, the method may include applying a frequency offset to adjust a local oscillator frequency of the receiving device according to a prediction of at least one resource block allocation to the receiving device, the at least one resource block allocation falling within a threshold frequency distance from the local oscillator frequency, where the adjusted local oscillator frequency is non-overlapping with the at least one resource block allocation based on application of the frequency offset. The operations of block 1010 may be performed in accordance with examples as disclosed herein, such as the resource block allocation prediction at 410, frequency offset magnitude selection at 415, and / or the various LIF applications of FIG. 2. In some examples, aspects of the operations of 1010 may be performed by a frequency offset component 725 as described with reference to FIG. 7.

[0132] At 1015, the method may include adjusting a frequency of a downcon verted received signal based on the applied frequency offset. The operations of block 1015 may be performed in accordance with examples as disclosed herein such as the device parameter adjustment at 420 and the offset application at 425. In some examples, aspects of the operations of 1015 may be performed by a frequency adjust component 730 as described with reference to FIG. 7.

[0133] At 1020, the method may include receiving one or more downlink messages in accordance with the applied frequency offset and the adjusted frequency of the received signal. The operations of block 1020 may be performed in accordance with examples as disclosed herein such as the communications 202 from the network entity 105-a to the UE 115-a, and / or the downlink message 301, and / or the downlink messages 435. In some examples, aspects of the operations of 1020 may be performed by a downlink messaging component 735 as described with reference to FIG. 7.

[0134] FIG. 11 shows a flowchart illustrating a method 1 100 that supports adaptive placement of receiver local oscillator frequency to mitigate flicker noise and signal distortion in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a UE or its components as described herein. For example, the operations of the method 1100 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the describedfunctions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0135] At 1105, the method may include applying a frequency offset to adjust a local oscillator frequency of the receiving device according to a prediction of at least one resource block allocation to the receiving device, the at least one resource block allocation falling within a threshold frequency distance from the local oscillator frequency, where the adjusted local oscillator frequency is non-overlapping with the at least one resource block allocation based on application of the frequency offset. The operations of block 1105 may be performed in accordance with examples as disclosed herein such as the resource block allocation prediction at 410, frequency offset magnitude selection at 415, and / or the various LIF applications of FIG. 2. In some examples, aspects of the operations of 1105 may be performed by a frequency offset component 725 as described with reference to FIG. 7.

[0136] At 1110, the method may include performing fast frequency hopping and applying the frequency offset before one or more OFDM symbols allocated for a physical dow nlink shared channel based on the prediction of the at least one resource block allocation. The operations of block 1110 may be performed in accordance with examples as disclosed herein, such as the fast frequency hopping 225 -a, the fast frequency hopping 225-b, or the fast frequency hopping 225-c, as described with reference to FIG. 2, and / or the offset application at 425. In some examples, aspects of the operations of 1110 may be performed by a frequency hopping component 745 as described with reference to FIG. 7.

[0137] At 1115, the method may include adjusting a frequency of a downconverted received signal based on the applied frequency offset. The operations of block 1115 may be performed in accordance with examples as disclosed herein such as the device parameter adjustment at 420 and the offset application at 425. In some examples, aspects of the operations of 1115 may be performed by a frequency adjust component 730 as described with reference to FIG. 7.

[0138] At 1120, the method may include receiving one or more downlink messages in accordance with the applied frequency offset and the adjusted frequency of the downconverted received signal. The operations of block 1120 may be performed inaccordance with examples as disclosed herein such as the communications 202 from the network entity 105-ato the UE 115-a, and / or the downlink message 301, and / or the downlink messages 435. In some examples, aspects of the operations of 1120 may be performed by a downlink messaging component 735 as described with reference to FIG. 7.

[0139] The following provides an overview of aspects of the present disclosure:

[0140] Aspect 1 : A method for wireless communications at a receiving device, comprising: applying a frequency offset to adjust a local oscillator frequency of the receiving device according to a prediction of at least one resource block allocation to the receiving device, the at least one resource block allocation falling within a threshold frequency distance from the local oscillator frequency, wherein the adjusted local oscillator frequency is non-overlapping with the at least one resource block allocation based at least in part on application of the frequency offset; adjusting a frequency of a downconverted received signal based at least in part on the applied frequency offset; and receiving one or more downlink messages in accordance with the applied frequency offset and the adjusted local oscillator frequency of the downconverted received signal.

[0141] Aspect 2: The method of aspect 1, wherein applying the frequency offset to adjust the local oscillator frequency of the receiving device comprises: predicting the at least one resource block allocation falls within the threshold frequency distance from the local oscillator frequency based at least in part on one or more previous resource block allocations occurring within a threshold time duration prior to the at least one resource block allocation.

[0142] Aspect 3: The method of any of aspects 1 through 2, w herein the prediction of the at least one resource block allocation to the receiving device is based at least in part on an artificial intelligence model, one or more machine learning algorithms, or any combination thereof.

[0143] Aspect 4: The method of any of aspects 1 through 3, wherein applying the frequency offset to adjust the local oscillator frequency of the receiving device comprises: performing fast frequency hopping and applying the frequency offset before one or more OFDM symbols allocated for a PDSCH based at least in part on the prediction of the at least one resource block allocation.

[0144] Aspect 5: The method of aspect 4, wherein the frequency offset is applied during a CP of an OFDM symbol preceding the one or more OFDM symbols.

[0145] Aspect 6: The method of any of aspects 1 through 5, wherein applying the frequency offset to adjust the local oscillator frequency of the receiving device comprises: applying the frequency offset to the local oscillator frequency based at least in part on a probability of the at least one resource block allocation falling within the threshold frequency distance from the local oscillator frequency being greater than a threshold probability.

[0146] Aspect 7: The method of any of aspects 1 through 8. further comprising: performing additional fast frequency hopping to disable application of the frequency offset based at least in part on a probability of the at least one resource block allocation falling within the threshold frequency distance from the local oscillator frequency being less than a threshold probability.

[0147] Aspect 9: The method of any of aspects 1 through 7. wherein the threshold frequency distance comprises a threshold quantity of resource blocks from the local oscillator frequency.

[0148] Aspect 10: The method of any of aspects 1 through 11, and 12, wherein to adjust the frequency of the do wncon verted received signal, the method further comprises: downconverting a received signal based at least in part on application of the frequency offset to the adjusted local oscillator frequency.

[0149] Aspect 13: The method of any of aspects 1 through 14, 15, and 10, further comprising: selecting a magnitude of the frequency offset based at least in part on a noise profile which is a function of the frequency offset from the local oscillator frequency, a partial quantity of resource block allocations, or any combination thereof.

[0150] Aspect 16: The method of any of aspects 1 through 17, and 18 through 13, further comprising: adjusting at least one or more parameters associated with a baseband filter of the receiving device based at least in part on a magnitude of the frequency offset exceeding an offset threshold, adjusting a sampling frequency of an ADC for the receiving device based at least in part on the magnitude of the frequency offset satisfying the offset threshold, or both.

[0151] Aspect 19: The method of any of aspects 1 through 20, and 21 through 16, wherein adjusting the frequency of the downcon verted received signal comprises: cancelling one or more effects of the applied frequency offset via a digital rotator at a modem of the receiving device.

[0152] Aspect 22: The method of any of aspects 1 through 19, wherein the frequency offset comprises a LIF offset.

[0153] Aspect 23: The method of any of aspects 1 through 22, wherein the at least one resource block allocation comprises a partial resource block allocation or a full resource block allocation.

[0154] Aspect 24: A receiving device for wireless communications, comprising one or more processors, one or more memories coupled with the one or more processors. and one or more processor-readable instructions stored in the one or more memories and executable by the one or more processors to individually or collectively cause the receiving device to perform a method of any of aspects 1 through 23.

[0155] Aspect 25: A receiving device for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 23.

[0156] Aspect 26: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 23.

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

[0158] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology' may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers(IEEE) 802.1 1 (Wi-Fi), IEEE 802. 16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.

[0159] Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0160] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, an 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 the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

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

[0162] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.

[0163] As used herein, including in the claims, ‘"or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such 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). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

[0164] As used herein, including in the claims, the article “a” before a noun is open- ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a,” “at least one,” “one or more,” “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components.” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.”

[0165] The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory) and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0166] In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.

[0167] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term ‘‘example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0168] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary' skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMSWhat is claimed is:1 . An apparatus for wireless communication at a receiving device, comprising: one or more processors; one or more memories coupled with the one or more processors; and one or more processor-readable instructions stored in the one or more memories and executable by the one or more processors individually or collectively to cause the apparatus to: apply a frequency offset to adjust a local oscillator frequency of the receiving device according to a prediction of at least one resource block allocation to the receiving device, the at least one resource block allocation falling within a threshold frequency distance from the local oscillator frequency, wherein the adjusted local oscillator frequency is non-overlapping with the at least one resource block allocation based at least in part on application of the frequency offset; adjust a frequency of a downconverted received signal based at least in part on the applied frequency offset; and receive one or more downlink messages in accordance with the applied frequency offset and the adjusted local oscillator frequency of the downconverted received signal.

2. The apparatus of claim 1, wherein, to apply the frequency offset to adjust the local oscillator frequency of the receiving device, the one or more processors are individually or collectively operable to cause the apparatus to: predict the at least one resource block allocation falls within the threshold frequency distance from the local oscillator frequency based at least in part on one or more previous resource block allocations occurring within a threshold time duration prior to the at least one resource block allocation.

3. The apparatus of claim 1, w herein the prediction of the at least one resource block allocation to the receiving device is based at least in part on anartificial intelligence model, one or more machine learning algorithms, or any combination thereof.

4. The apparatus of claim 1. wherein, to apply the frequency offset to adjust the local oscillator frequency of the receiving device, the one or more processors are individually or collectively operable to cause the apparatus to: perform fast frequency hopping and applying the frequency offset before one or more orthogonal frequency division multiplexing (OFDM) symbols allocated for a physical downlink shared channel based at least in part on the prediction of the at least one resource block allocation.

5. The apparatus of claim 4, wherein the frequency offset is applied during a cyclic prefix of an OFDM symbol preceding the one or more OFDM symbols.

6. The apparatus of claim 1, wherein, to apply the frequency offset to adjust the local oscillator frequency of the receiving device, the one or more processors are individually or collectively operable to cause the apparatus to: apply the frequency offset to the local oscillator frequency based at least in part on a probability of the at least one resource block allocation falling within the threshold frequency distance from the local oscillator frequency being greater than a threshold probability.

7. The apparatus of claim 1, wherein the one or more processors are individually or collectively further operable to cause the apparatus to: perform additional fast frequency hopping to disable application of the frequency offset based at least in part on a probability of the at least one resource block allocation falling within the threshold frequency distance from the local oscillator frequency being less than a threshold probability'.

8. The apparatus of claim 1, wherein the threshold frequency distance comprises a threshold quantity of resource blocks from the local oscillator frequency.

9. The apparatus of claim 1 , wherein to adjust the frequency of the downcon verted received signal, the one or more processors are individually or collectively further operable to cause the apparatus to: downconvert a received signal based at least in part on application of the frequency offset to the adjusted local oscillator frequency.

10. The apparatus of claim 1 , wherein the one or more processors are individually or collectively further operable to cause the apparatus to: select a magnitude of the frequency offset based at least in part on a noise profile which is a function of the frequency offset from the local oscillator frequency, a partial quantity of resource block allocations, or any combination thereof.

11. The apparatus of claim 1. wherein the one or more processors are individually or collectively further operable to cause the apparatus to: adjust at least one or more parameters associated with a baseband filter of the receiving device based at least in part on a magnitude of the frequency offset exceeding an offset threshold, adjusting a sampling frequency of an analog-to-digital converter for the receiving device based at least in part on the magnitude of the frequency offset satisfying the offset threshold, or both.

12. The apparatus of claim 1. wherein, to adjust the frequency of the downconverted received signal, the one or more processors are individually or collectively operable to cause the apparatus to: cancel one or more effects of the applied frequency offset via a digital rotator at a modem of the receiving device.

13. The apparatus of claim 1, wherein the frequency offset comprises a low intermediate frequency offset.

14. The apparatus of claim 1, wherein the at least one resource block allocation comprises a partial resource block allocation or a full resource block allocation.

15. A method for wireless communications at a receiving device, comprising:applying a frequency offset to adjust a local oscillator frequency of the receiving device according to a prediction of at least one resource block allocation to the receiving device, the at least one resource block allocation falling within a threshold frequency distance from the local oscillator frequency, wherein the adjusted local oscillator frequency is non-overlapping with the at least one resource block allocation based at least in part on application of the frequency offset; adjusting a frequency of a downconverted received signal based at least in part on the applied frequency offset; and receiving one or more downlink messages in accordance with the applied frequency offset and the adjusted local oscillator frequency of the downconverted received signal.

16. The method of claim 15, wherein applying the frequency offset to adjust the local oscillator frequency of the receiving device comprises: predicting the at least one resource block allocation falls within the threshold frequency distance from the local oscillator frequency based at least in part on one or more previous resource block allocations occurring within a threshold time duration prior to the at least one resource block allocation.

17. The method of claim 15, wherein the prediction of the at least one resource block allocation to the receiving device is based at least in part on an artificial intelligence model, one or more machine learning algorithms, or any combination thereof.

18. The method of claim 15, wherein applying the frequency offset to adjust the local oscillator frequency of the receiving device comprises: performing fast frequency hopping and applying the frequency offset before one or more orthogonal frequency division multiplexing (OFDM) symbols allocated for a physical downlink shared channel based at least in part on the prediction of the at least one resource block allocation.

19. The method of claim 18, wherein the frequency offset is applied during a cyclic prefix of an OFDM symbol preceding the one or more OFDM symbols.

20. The method of claim 15, wherein applying the frequency offset to adjust the local oscillator frequency of the receiving device comprises: applying the frequency offset to the local oscillator frequency based at least in part on a probability of the at least one resource block allocation falling within the threshold frequency distance from the local oscillator frequency being greater than a threshold probability.

21. The method of claim 15, further comprising: performing additional fast frequency hopping to disable application of the frequency offset based at least in part on a probability of the at least one resource block allocation falling within the threshold frequency distance from the local oscillator frequency being less than a threshold probability.

22. The method of claim 15, wherein the threshold frequency distance comprises a threshold quantity7of resource blocks from the local oscillator frequency.

23. The method of claim 15, wherein to adjust the frequency of the downconverted received signal, the method further comprises: downconverting a received signal based at least in part on application of the frequency offset to the adjusted local oscillator frequency.

24. The method of claim 15, further comprising: selecting a magnitude of the frequency offset based at least in part on a noise profile which is a function of the frequency offset from the local oscillator frequency, a partial quantity of resource block allocations, or any combination thereof.

25. The method of claim 15, further comprising: adjusting at least one or more parameters associated with a baseband filter of the receiving device based at least in part on a magnitude of the frequency offset exceeding an offset threshold, adjusting a sampling frequency of an analog-to- digital converter for the receiving device based at least in part on the magnitude of the frequency offset satisfying the offset threshold, or both.

26. The method of claim 15, wherein adjusting the frequency of the downcon verted received signal comprises: cancelling one or more effects of the applied frequency offset via a digital rotator at a modem of the receiving device.

27. The method of claim 15, wherein the frequency offset comprises a low intermediate frequency offset.

28. The method of claim 15, wherein the at least one resource block allocation comprises a partial resource block allocation or a full resource block allocation.

Images