Adaptive placement of receiver local oscillator frequency for mitigation of flicker noise and signal distortion

Abstract

Methods, systems, and apparatus for wireless communication are described. The described techniques can adjust the local oscillator frequency of a receiving device by applying a frequency offset, enabling the receiving device to reduce flicker noise and signal distortion around resource block allocations. The receiving device can predict that a resource block allocation may fall within a threshold frequency distance from the local oscillator frequency based on a threshold duration prior to the allocation of one or more previous resource block allocations (or one or more previous control channel decodings). The receiving device can perform fast frequency hopping and apply a frequency offset such that the adjusted local oscillator frequency does not overlap with at least one resource block allocation. The receiving device can adjust the frequency of the received signal based on the applied frequency offset and can receive one or more downlink messages.

Description

Cross-reference to related applications

[0001] This patent application claims priority to Indian Patent Application No. 202341080999, filed on November 29, 2023, entitled “Adaptive Placement of Receiver Local Oscillator Frequency to Mitigate Flicker Noise and Signal Distortion”, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The following relates to wireless communication, including the adaptive placement of the receiver's local oscillator frequency to mitigate flicker noise and signal distortion. Background Technology

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

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting adaptive placement of receiver local oscillator frequencies 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 future resource block allocations and apply a frequency offset using fast frequency hopping to adjust the receiving device's local oscillator frequency, resulting in reduced flicker noise and signal distortion in the resource block allocations (e.g., flicker noise and signal distortion shift with the local oscillator frequency). For example, the receiving device may predict that a resource block allocation is likely to fall within a threshold frequency distance from the local oscillator frequency based on one or more previous resource blocks that occurred prior to the allocation. The receiving device may identify the frequency offset and apply it to the receiver's local oscillator frequency such that the adjusted local oscillator frequency does not overlap with at least one resource block allocation. The receiving device may adjust the frequency of a down-converted received signal based on the applied frequency offset and receive one or more downlink messages.

[0005] A method for wireless communication by a receiving device is described. The method may include: applying a frequency offset to adjust the local oscillator frequency of the receiving device based on 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 based on the application of the frequency offset does not overlap with the at least one resource block allocation; adjusting the frequency of a down-converted received signal based on the applied frequency offset; and receiving one or more downlink messages based on the applied frequency offset and the adjusted local oscillator frequency of the down-converted received signal.

[0006] A receiving device for wireless communication is described. The receiving device may include one or more processors; one or more memories coupled to the processors; and one or more processor-readable instructions stored in and executable by the processors to individually or jointly cause the receiving device to: apply a frequency offset to adjust the local oscillator frequency of the receiving device based on 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 based on the application of the frequency offset does not overlap with the at least one resource block allocation; adjust the frequency of a down-converted received signal based on the applied frequency offset; and receive one or more downlink messages based on the applied frequency offset and the adjusted local oscillator frequency of the down-converted received signal.

[0007] Another receiving device for wireless communication is described. The receiving device may include: means for applying a frequency offset to adjust the local oscillator frequency of the receiving device based on 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 based on the application of the frequency offset does not overlap with the at least one resource block allocation; means for adjusting the frequency of a down-converted received signal based on the applied frequency offset; and means for receiving one or more downlink messages based on the applied frequency offset and the adjusted local oscillator frequency of the down-converted received signal.

[0008] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: apply a frequency offset to adjust the local oscillator frequency of the receiving device based on 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 based on the application of the frequency offset does not overlap with the at least one resource block allocation; adjust the frequency of a down-converted received signal based on the applied frequency offset; and receive one or more downlink messages based on the applied frequency offset and the adjusted local oscillator frequency of the down-converted received signal.

[0009] In some examples of the methods, receiving devices, and nontransitory computer-readable media described herein, applying the frequency offset to adjust the local oscillator frequency of the receiving device may include operations, features, components, or instructions for predicting that 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 that occurred within a threshold duration prior to the allocation of the at least one resource block.

[0010] In some examples of the methods, receiving devices, and nontransitory computer-readable media described herein, the prediction of the allocation of at least one resource block 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 methods, receiving devices, and nontransitory computer-readable media described herein, applying the frequency offset to adjust the local oscillator frequency of the receiving device may include operations, features, components, or instructions for performing the following actions: based on the prediction of the allocation of the at least one resource block, performing fast frequency hopping and applying the frequency offset before one or more orthogonal frequency division multiplexing (OFDM) symbols allocated for the Physical Downlink Shared Channel (PDSCH). In some examples of the methods, receiving devices, and nontransitory computer-readable media described herein, the frequency offset may be applied during the cyclic prefix (CP) of the OFDM symbol preceding the one or more OFDM symbols.

[0012] In some examples of the methods, receiving devices, and nontransitory computer-readable media described herein, applying the frequency offset to adjust the local oscillator frequency of the receiving device may include operations, features, components, or instructions for performing the following actions: applying the frequency offset to the local oscillator frequency based on the probability that the probability of the at least one resource block allocation falling within the threshold frequency distance from the local oscillator frequency is greater than a threshold probability.

[0013] Some examples of the methods, receiving devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing an application that disables the frequency offset based on the probability that the allocation of the at least one resource block falls within the threshold frequency distance from the local oscillator frequency is less than a threshold probability. In some examples of the methods, receiving devices, and nontransitory computer-readable media described herein, the threshold frequency distance includes resource blocks at a threshold number from the local oscillator frequency.

[0014] Some examples of the methods, receiving devices, and non-transitory computer-readable media described herein may include further operations, features, components, or instructions for down-converting a received signal based on applying the frequency offset to the adjusted local oscillator frequency.

[0015] Some examples of the methods, receiving devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: selecting the magnitude of the frequency offset based on a noise distribution curve, the number of portions of the resource block allocation, or any combination thereof, the noise distribution curve being variable with respect to the frequency offset from the local oscillator frequency.

[0016] Some examples of the methods, receiving devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: adjusting at least one or more parameters associated with the baseband filter of the receiving device based on the magnitude of the frequency offset exceeding an offset threshold, adjusting the sampling frequency of the analog-to-digital converter (ADC) of the receiving device based on the magnitude of the frequency offset satisfying the offset threshold, or both.

[0017] In some examples of the methods, receiving devices, and nontransitory computer-readable media described herein, adjusting the frequency of the down-converted received signal may include operations, features, components, or instructions for eliminating one or more effects of the applied frequency offset via a digital rotator at the modem of the receiving device.

[0018] In some examples of the methods, receiving devices, and nontransitory computer-readable media described herein, the frequency offset includes a low intermediate frequency (LIF) offset. In some examples of the methods, receiving devices, and nontransitory computer-readable media described herein, the at least one resource block allocation includes a partial resource block allocation or a complete resource block allocation. Attached Figure Description

[0019] Figure 1 , Figure 2 and Figure 3 An example of a wireless communication system is shown that supports one or more aspects of this disclosure for adaptive placement of the receiver local oscillator frequency to mitigate flicker noise and signal distortion.

[0020] Figure 4 An example of a process flow for adaptive placement of the receiver local oscillator frequency to mitigate flicker noise and signal distortion, according to one or more aspects of this disclosure, is shown.

[0021] Figure 5 and Figure 6 A block diagram of an apparatus for adaptive placement of a receiver local oscillator frequency to mitigate flicker noise and signal distortion, according to one or more aspects of this disclosure, is shown.

[0022] Figure 7 A block diagram is shown of a communication manager that supports adaptive placement of the receiver local oscillator frequency to mitigate flicker noise and signal distortion, according to one or more aspects of this disclosure.

[0023] Figure 8 A diagram of a system including a device for adaptive placement of the receiver local oscillator frequency to mitigate flicker noise and signal distortion, according to one or more aspects of this disclosure, is shown.

[0024] Figures 9 to 11 A flowchart illustrating a method for adaptive placement of the receiver local oscillator frequency to mitigate flicker noise and signal distortion, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0025] Some wireless communication devices (such as network entities or other scheduling devices) located within a wireless communication system can provide resource block allocations to receiving devices (such as User Equipment (UE)), enabling the UE to know which resources to monitor for downlink communication. However, in some cases, the UE may receive resource block allocations that occur relatively close to the local oscillator frequency, which can lead to significant flicker noise and reduced receiver sensitivity. Specifically, when resource block allocations are relatively narrow (e.g., one or two resource blocks, partial resource block allocations) and centered on the local oscillator frequency, the receiving device may experience significant challenges such as noise, increased power spectral density leading to second-order signal distortion, and power leakage, which have a significant impact on the receiving device's voice call coverage and data rate performance.

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

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

[0028] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are further illustrated and described by way of process flow. The aspects of this disclosure are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to the adaptive placement of the receiver local oscillator frequency for mitigating flicker noise and signal distortion, and are described with reference to these diagrams.

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

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

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

[0032] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or 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, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be 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 UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

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

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

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

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

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

[0038] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support adaptive placement of receiver local oscillator frequencies, as described herein, for mitigating flicker noise and signal distortion. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

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

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

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

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

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

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

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

[0046] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured using multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

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

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

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

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

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

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

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

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

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

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

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

[0058] In some examples, UE 115 can use fast frequency hopping to receive downlink communication and send uplink communication. In one example, UE 115-a can achieve phase-locked loop (PLL) locking to a new frequency (e.g., the resulting local oscillator frequency after applying an offset) within a very short time period. The settling time specifies how quickly the PLL reaches the new frequency when a change or frequency hopping occurs. In some examples, UE 115 may include a voltage-controlled oscillator (VCO), a phase detector, a loop filter (e.g., a low-pass filter), a control unit, and a frequency divider (e.g., an integer N synthesizer or a fractional synthesizer).

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

[0060] In some implementations, network entity 105 may provide resource block allocations to receiving devices (such as UE 115), enabling UE 115 to know which resources to monitor for downlink communication. However, in some cases, UE 115 may receive resource block allocations that occur relatively close to its local oscillator frequency, which can lead to significant flicker noise and reduced sensitivity. Specifically, when resource block allocations are relatively narrow and centered around the local oscillator frequency, UE 115 may experience significant challenges such as noise, increased power spectral density leading to second-order signal distortion, and power leakage, which have a significant impact on UE 115's voice call coverage and data rate performance.

[0061] To reduce the impact of flicker noise from resource block allocations occurring relatively close to the local oscillator frequency, UE 115 can perform fast frequency hopping to apply a frequency offset (e.g., LIF offset) to the local oscillator frequency. The application of the frequency offset allows UE 115 to adjust the local oscillator frequency outside of resource block allocations. In some examples, UE 115 can predict partial resource block allocations based on previously received resource block allocations or based on the history of past control channel decoding. In some examples, UE 115 can perform frequency hopping (e.g., fast frequency hopping) at the receiver-side local oscillator frequency to apply the frequency offset and adjust the local oscillator frequency outside of the predicted resource block allocation. UE 115 can then undo the effects of the frequency hopping at the receiver, ensuring that the receiver's modem does not experience any effects from the frequency hopping, and receive one or more downlink messages from network entity 105 according to the applied frequency offset.

[0062] Figure 2 An example of a wireless communication system 200, according to one or more aspects of this disclosure, is shown that supports adaptive placement of the receiver local oscillator frequency for mitigating flicker noise and signal distortion. In some examples, the wireless communication system 200 may implement or be implemented by aspects of the wireless communication system 100. For example, the wireless communication system 200 may include 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 as described in reference... Figure 1 Examples of the corresponding devices described. In some examples, the receiving device (e.g., UE 115-a) may adaptively position the local oscillator frequency to mitigate flicker noise and signal distortion associated with one or more communications 202 of the transmitting device (e.g., network entity 105-a).

[0063] In some examples (e.g., in lower-technology nodes with high power density relative to higher-technology nodes), flicker noise can affect receiver sensitivity performance. For instance, the receiver's sensitivity may be reduced if it receives a resource block allocation located around a relatively low frequency offset from the receiver's local oscillator (e.g., overlapping with or within a threshold frequency distance of a DC subcarrier). In some examples, resource block allocation may include partial or full allocations. In some examples, resource block allocation may be as narrow as a single resource block (e.g., for voice calls in LTE-based Voice over LTE (VoLTE)).

[0064] However, in some cases, when the resource block allocation is narrow (e.g., one or two resource blocks, or partial resource block allocation) and is allocated around the low frequencies following the downconversion of the received signal (e.g., a low-frequency offset from the local oscillator frequency at RF), the sensitivity performance of the receiving device may be negatively affected. 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 where receiver sensitivity decreases. In some examples, sensitivity reduction may occur for a single resource block allocation when the total number of resource blocks is odd (e.g., LTE 5 MHz bandwidth), or for a two resource block allocation when the total number of resource blocks is even (e.g., LTE 20 MHz bandwidth).

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

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

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

[0068] In some examples, the 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 down-converted frequencies). In some examples, the magnitude of noise 215 may increase when resource blocks are allocated at lower frequencies closer to the local oscillator (e.g., 220-a, 220-b, and 220-c).

[0069] To reduce the impact of increased noise and signal distortion at some resource block allocations near the DC after downconversion, UE 115-a can apply frequency offset to the local oscillator using frequency hopping 225-a, 225-b, or 225-c at the receiver. For example, UE 115-a can perform fast frequency hopping, where UE 115-a can utilize multiple frequency hoppings of the receiver frequency to receive a symbol. Additionally or alternatively, fast frequency hopping can allow UE 115-a to utilize multiple carrier frequencies to receive a symbol with several hops. Compared to other frequency hopping techniques, fast frequency hopping can also occur on a relatively short time scale. For example, where other frequency hopping techniques may require more time to complete, fast frequency hopping may occur in less than tens of microseconds. Using a fast frequency hopping technique with the receiver's local oscillator frequency, UE 115-a can apply 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 resource block allocation 210, and resource block allocation 210 experiences noise that is reduced or eliminated relative to the noise experienced at the initial local oscillator frequency. In some examples, LIF offset 230 can be approximately several hundred kilohertz.

[0070] In some other cases, resource block allocation 210 may be dynamically changed (e.g., within each subframe or time slot) such that the predicted probability of resource block allocation 210 falling near the local oscillator frequency 220-a is less than a threshold probability, which may disable the application of LIF offset 230. In examples where resource block allocation 210 may be narrow (e.g., one or two resource blocks, partial resource block allocation) and around the local oscillator frequency 220, applying LIF offset 230 via frequency hopping 225 can prevent sensitivity degradation (e.g., a static LIF offset without frequency hopping may not prevent sensitivity degradation).

[0071] In some examples, UE 115-a may apply LIF offset 230 in different relative frequency directions. For example, UE 115-a may use frequency hopping 225-b to apply LIF offset 230-b, causing the local oscillator frequency 220-b to move in a first direction (e.g., positive) away from resource block allocation 210. Alternatively, UE 115-a may use frequency hopping 225-c to apply LIF offset 230-c, causing the local oscillator frequency 220-c to move in a second direction (e.g., negative) away from resource block allocation 210. In both cases, the amount of noise 215 experienced by the allocated resource block can 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, based on the predicted probability of resource block allocation 210 being less than a threshold probability, additional frequency hopping may be used to disable the application of LIF offset 230.

[0072] In some implementations, UE 115-a may adjust or select the value of LIF offset 230 after down-converting the received signal. For example, the value of LIF offset 230 may be based on the receiver's small signal noise figure (ssNF) distribution curve, which varies with the frequency offset. Additionally or alternatively, the value of LIF offset 230 may be based on a portion of the resource block allocation. For example, when transmission has a small number of resource block allocations (e.g., the number of transmitted resource blocks is less than or equal to the total number of transmitted resource blocks, where in some cases the total number of transmitted resource blocks is 1), the value may be based on the span of the second-order transmission distortion (IM2) product falling on the received signal. In some cases, the value of LIF offset 230 may exceed a threshold (e.g., the value may be large enough to degrade the sensitivity of edge resource blocks). In such cases, UE 115-a may adjust at least one or more parameters associated with the baseband filter of the receiving device. For example, UE 115-a can widen the baseband filter poles (e.g., to reduce the effects of signal drop and analog-to-digital conversion (ADC) noise). Additionally or alternatively, UE 115-a can adjust the sampling frequency of the receiver's ADC (e.g., UE 115-a can increase the ADC sampling rate to push ADC quantization noise further out of the signal bandwidth).

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

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

[0075] In some examples, downlink message 301 may include a number of OFDM symbols, each of which includes a cyclic prefix (CP) 303 to reduce inter-symbol interference, and each of these OFDM symbols is included in 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 for PDSCH 310-b, and CP 303-d for PDSCH 310-c). In some examples, PDCCH 305 may be in any of the symbols in this number of symbols. Additionally or alternatively, PDCCH 305 may span multiple symbols in this number of symbols. In some cases, the location and span of PDCCH 305 may be communicated by network entity 105-b based on System Information Block (SIB) or RRC configuration (or reconfiguration) signaling. In some cases, a certain number of PDCCH symbols may be communicated by network entity 105-b based on the Physical Control Format Indicator Channel (PCFICH) indicating the Control Format Indicator (CFI). For example, PCFICH may indicate CFI=1. Additionally, although PDSCH 310-a is exemplified as being adjacent to PDCCH 305, in some examples, PDSCH 310-a may not be adjacent to PDCCH 305 (e.g., the PDSCH symbols may be several symbols far from the PDCCH symbols in the same time slot).

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

[0077] In some examples, UE 115-b can be used over time t A 325-a (e.g., from reference point 315 to t) A Frequency hopping is completed at or before the duration of 325-a. In some cases, the duration t B 325-b (e.g., from reference point 315 to t) B The duration of 325-b can represent the duration of the DCI containing resource block allocations from PDSCH 310-a that can be decoded from PDCCH 305.

[0078] In some cases, the duration is t C 325-c (e.g., CP 303-d from reference point 315 to t) C The duration of 325-c can be represented as follows: where UE 115-b can be based on the duration t used for decoding PDCCH 305. B 325-b (e.g., the earliest duration at which frequency hopping can begin) is used to employ frequency hopping. In such cases, the duration t C 325-c can be longer than the duration t A 325-a. In these cases, UE 115-b can receive samples from PDSCH 310-a without adjusting the local oscillator frequency and enabling LIF offset mitigation before doing so. In other words, UE 115-b can implement techniques for performing frequency hopping on a shorter timescale than normal frequency hopping (e.g., UE 115-b can implement fast frequency hopping techniques for the receiver's local oscillator frequency) to receive downlink communications with less noise and higher accuracy.

[0079] Therefore, to more effectively reduce signal noise while adapting to the fast timescale used for data reception, the techniques described herein enable UE-b to accurately predict resource block allocations for PDSCH 310-a, allowing fast frequency hopping and local oscillator placement or adjustment to occur before UE 115-b receives PDSCH 310-a, ensuring no downlink data is lost due to ongoing decoding. In some examples, UE 115-b can use the history of past resource block allocations (e.g., the history of PDCCH decoding) to predict future or current resource block allocations, and this can be achieved over a time period t. AFrequency hopping is used during 325-a to apply LIF before receiving PDSCH 310-a. In some examples, UE 115-b can apply LIF during CP 303 of any symbol (assuming LIF is applied before receiving PDSCH 310-a). For example, UE 115-b can apply LIF during CP 303-b, CP 303-c, CP 303-d, or any combination thereof (e.g., the duration of CP 303 can be a buffer time zone during which UE 115-b can change receiver parameters without affecting decoding performance). In such examples, during duration t... A Performing frequency hopping during 325-a allows UE 115-b to significantly reduce the capture of one or more RF transients (e.g., via UE 115-b's modem). Reference Figure 4 The prediction of resource block allocation will be discussed in further detail.

[0080] Figure 4 An example of a process flow 400 supporting adaptive placement of the receiver local oscillator frequency to mitigate flicker noise and signal distortion, according to one or more aspects of this disclosure, is shown. In the following description of process flow 400, operations between UE 115-c and network entity 105-c may be transmitted in different orders as shown. In some specific implementations, UE 115-c may include a receiver. Some operations may also be omitted from process flow 400, and other operations may be added to process flow 400. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may occur simultaneously.

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

[0082] At 410, UE 115-c may predict that a resource block allocation will fall within (e.g., will occur) a threshold frequency distance from the local oscillator frequency based on the history of past PDCCH decoding (e.g., based on past resource block allocations). In some examples, the threshold frequency distance may include a threshold number of resource blocks from the local oscillator frequency. In some examples, UE 115-c may monitor one or more channels to receive downlink communication. 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 anywhere. In some examples, UE 115-c may predict that a resource block allocation will occur based on one or more previous resource block allocations. Additionally or alternatively, UE 115-c may predict that a 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, UE 115-c can predict that a resource block allocation will occur based on the probability that the allocation will occur within a threshold frequency distance from the local oscillator frequency is greater than a threshold probability. For example, UE 115-c can measure the probability that a 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 probability that the allocation will occur within a distance less than the threshold distance, UE 115-c can avoid applying LIF (e.g., disable LIF). In some other examples, the probability that a resource block allocation will occur within a certain distance may exceed the threshold distance around the local oscillator frequency. Then, based on the probability that the allocation will occur within a distance greater than the threshold distance, UE 115-c can apply LIF. In some examples, the rate of change of resource block allocation may exceed a resource block allocation threshold (e.g., resource block allocation may be relatively dynamic), causing the predicted probability that the allocation will fall near the local oscillator frequency to be less than the threshold probability, which can (automatically) disable the application of LIF offset.

[0084] At 415, UE 115-c may optionally select the magnitude of a frequency offset (e.g., LIF offset) to be applied to the local oscillator frequency. For example, UE 115-c may select the magnitude of the frequency offset based on a noise distribution profile associated with the receiving device (e.g., a noise distribution profile that varies with the frequency offset from the local oscillator frequency), the number of portions of the resource block allocation, or both. At 420, 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, UE 115-c may adjust at least one or more parameters of the baseband filter of the receiving device based on the frequency offset exceeding an offset threshold. Additionally or alternatively, UE 115-c may adjust the sampling frequency of the ADC of the receiving device based on the magnitude of the frequency offset satisfying an offset threshold.

[0085] At 425, UE 115-c can apply a frequency offset to the local oscillator frequency. In some examples, the local oscillator frequency of UE 115-c may partially overlap with a threshold frequency distance. In some examples, based on the application of the frequency offset, the local oscillator frequency may not overlap with resource block allocations. In some examples, UE 115-c may use one or more frequency hopping techniques to apply the frequency offset. For example, UE 115-c can implement a fast frequency hopping technique to apply multiple frequency hoppings to the receiver's local oscillator frequency to receive a symbol, and the fast frequency hopping can occur on a timescale smaller than other frequency hopping techniques (e.g., less than tens of microseconds).

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

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

[0088] Figure 5 A block diagram 500 illustrates a device 505, according to one or more aspects of this disclosure, for adaptive placement of a receiver local oscillator frequency to mitigate flicker noise and signal distortion. Device 505 may be an example of various aspects of a UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

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

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

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

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

[0095] The communication manager 520 may support wireless communication according to examples disclosed herein. For example, the communication manager 520 may be capable of, configured to, or operable to support components for applying a frequency offset to adjust the local oscillator frequency of the receiving device based on a prediction of at least one resource block allocation to the receiving device, wherein the at least one resource block allocation falls within a threshold frequency distance from the local oscillator frequency, and the adjusted local oscillator frequency based on the application of the frequency offset does not overlap with the at least one resource block allocation. The communication manager 520 may be capable of, configured to, or operable to support components for adjusting the frequency of a down-converted received signal based on the applied frequency offset. The communication manager 520 may be capable of, configured to, or operable to support components for receiving one or more downlink messages based on the applied frequency offset and the adjusted frequency of the received signal.

[0096] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., controlling receiver 510, transmitter 515, communication manager 520 or a combination thereof or at least one processor otherwise coupled to them) can support technologies for advantages such as reduced processing, lower power consumption, and more efficient use of communication resources.

[0097] Figure 6 A block diagram 600 illustrates a device 605, according to one or more aspects of this disclosure, for adaptive placement of a receiver local oscillator frequency to mitigate flicker noise and signal distortion. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0100] Device 605 or its various components may be examples of parts used to perform various aspects of adaptive placement of the receiver local oscillator frequency as described herein for mitigating flicker noise and signal distortion. For example, communication manager 620 may include frequency offset component 625, frequency adjustment component 630, downlink message receiving component 635, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0101] Communication manager 620 may support wireless communication according to examples disclosed herein. Frequency offset component 625 is capable of, configured to, or operable to support means for applying a frequency offset to adjust the local oscillator frequency of the receiving device based on a prediction of at least one resource block allocation to the receiving device, wherein the at least one resource block allocation falls within a threshold frequency distance from the local oscillator frequency, and wherein the adjusted local oscillator frequency based on the application of the frequency offset does not overlap with the at least one resource block allocation. Frequency adjustment component 630 is capable of, configured to, or operable to support means for adjusting the frequency of a downconverted received signal based on the applied frequency offset. Downlink message receiving component 635 is capable of, configured to, or operable to support means for receiving one or more downlink messages based on the applied frequency offset and the adjusted frequency of the received signal.

[0102] Figure 7 A block diagram 700 of a communication manager 720, according to one or more aspects of this disclosure, is shown to support adaptive placement of the receiver local oscillator frequency for mitigating flicker noise and signal distortion. The communication manager 720 may be an example of aspects of the communication manager 520, communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of parts for performing various aspects of adaptive placement of the receiver local oscillator frequency for mitigating flicker noise and signal distortion as described herein. For example, the communication manager 720 may include a frequency offset component 725, a frequency adjustment component 730, a downlink message transmission and reception component 735, an allocation prediction component 740, a frequency hopping component 745, an allocation probability component 750, a downconverter component 755, a frequency offset value component 760, a signal processing component 765, a digital rotator component 770, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0103] The communication manager 720 can support wireless communication according to examples disclosed herein. The frequency offset component 725 is capable of, configured to, or operable to support means for applying a frequency offset to adjust the local oscillator frequency of the receiving device based on a prediction of at least one resource block allocation to the receiving device, wherein the at least one resource block allocation falls within a threshold frequency distance from the local oscillator frequency, and wherein the adjusted local oscillator frequency based on the application of the frequency offset does not overlap with the at least one resource block allocation. The frequency adjustment component 730 is capable of, configured to, or operable to support means for adjusting the frequency of a downconverted received signal based on the applied frequency offset. The downlink message receiving component 735 is capable of, configured to, or operable to support means for receiving one or more downlink messages based on the applied frequency offset and the adjusted frequency of the received signal.

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

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

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

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

[0108] In some examples, to support the application of frequency offsets to adjust the local oscillator frequency of the receiving device, the allocation probability component 750 is capable of, can be configured to, or can operate to support components for applying frequency offsets to the local oscillator frequency based on a probability that the allocation of at least one resource block falls within a threshold frequency distance from the local oscillator frequency is greater than a threshold probability.

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

[0110] In some examples, the threshold frequency distance includes resource blocks of a threshold number of times the local oscillator frequency is located.

[0111] In some examples, the downconverter component 755 is capable of, configured to, or able to operate to support components for downconverting the adjusted received signal based on applying a frequency offset to the adjusted local oscillator frequency.

[0112] In some examples, the frequency offset magnitude component 760 is capable of, can be configured to, or can operate to support components for selecting the magnitude of the frequency offset based on a noise distribution curve, the number of portions of the resource block allocation, or any combination thereof, which varies with the frequency offset from the local oscillator frequency.

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

[0114] In some examples, in order to support adjusting the frequency of the downconverted received signal, the digital rotator assembly 770 is capable of, configured to, or operable to support components for eliminating one or more effects of the applied frequency offset via a digital rotator at the modem of the receiving device.

[0115] In some examples, the frequency offset includes a low-to-mid frequency offset.

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

[0117] Figure 8A diagram of a system 800 including device 805 supporting adaptive placement of the receiver local oscillator frequency for mitigating flicker noise and signal distortion, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication 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 communicate electronically via one or more buses (e.g., bus 845) or be otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically).

[0118] I / O controller 810 manages the input and output signals of device 805. I / O controller 810 can also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 810 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as 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, device 805 may include a single antenna 825. However, in other cases, device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 815 may communicate bidirectionally via one or more antennas 825, a wired link, or a wireless link as described herein. For example, transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. Transceiver 815, or transceiver 815 and one or more antennas 825, may be an example of transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof or components thereof as described herein.

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

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

[0122] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for applying a frequency offset to adjust the local oscillator frequency of the receiving device based on a prediction of at least one resource block allocation to the receiving device, wherein the at least one resource block allocation falls within a threshold frequency distance from the local oscillator frequency, and the adjusted local oscillator frequency based on the frequency offset application does not overlap with the at least one resource block allocation. The communication manager 820 may be capable of, configured to, or operable to support components for adjusting the frequency of a down-converted received signal based on the applied frequency offset. The communication manager 820 may be capable of, configured to, or operable to support components for receiving one or more downlink messages based on the applied frequency offset and the adjusted frequency of the received signal.

[0123] By including or configuring a communication manager 820 according to an example as described herein, device 805 can support technologies that provide advantages such as improved communication reliability, reduced latency, improved and reduced user experience related to processing, reduced power consumption, more efficient use of communication resources, improved coordination between devices, extended battery life, and improved utilization of processing power.

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

[0125] Figure 9 A flowchart illustrating a method 900 for adaptive placement of a receiver local oscillator frequency to mitigate flicker noise and signal distortion, according to various aspects of this disclosure, is shown. Operation of method 900 can be implemented by a UE or its components as described herein. For example, operation of method 900 can be performed by, as referenced... Figures 1 to 8 The UE 115 described herein performs the functions. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0126] At 905, the method may include: applying a frequency offset to adjust the local oscillator frequency of the receiving device based on a prediction of at least one resource block allocation to the receiving device, wherein the at least one resource block allocation falls within a threshold frequency distance from the local oscillator frequency, wherein the adjusted local oscillator frequency based on the application of the frequency offset does not overlap with the at least one resource block allocation. The operation of block 905 may be performed according to examples as disclosed herein, such as... Figure 4 Resource block allocation at 410, frequency offset value selection at 415, and device parameter adjustment at 420 or Figure 2 Various LIF applications. In some examples, aspects of the 905's operation can be derived from, as referenced... Figure 7 The frequency offset component 725 is described and used to perform this.

[0127] At 910, the method may include: adjusting the frequency of the down-converted received signal based on the applied frequency offset. The operation of block 910 may be performed according to examples disclosed herein, such as... Figure 4 The offset at 425 is applied. In some examples, aspects of the operation of 910 can be derived from, as referenced... Figure 7 The frequency adjustment component 730 described herein is used to perform this operation.

[0128] At 915, the method may include receiving one or more downlink messages based on an applied frequency offset and an adjusted frequency of the received signal. The operation of block 915 may be performed according to examples disclosed herein, such as... Figure 4 435 downlink message reception or Figure 2 and Figure 3 The illustrated downlink message reception. In some examples, aspects of the 915 operation can be derived from, as referenced... Figure 7 The downlink message receiving and sending component 735 described herein is used to perform this action.

[0129] Figure 10 A flowchart illustrating a method 1000 for adaptive placement of a receiver local oscillator frequency to mitigate flicker noise and signal distortion, according to various aspects of this disclosure, is shown. Operation of method 1000 can be implemented by a UE or its components as described herein. For example, operation of method 1000 can be performed by, as described in reference... Figures 1 to 8 The UE 115 described herein performs the functions. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0130] At 1005, the method may include: predicting that at least one resource block allocation falls within a threshold frequency distance from the local oscillator frequency based on one or more previous resource block allocations occurring within a threshold duration prior to at least one resource block allocation. The operation of box 1005 may be performed according to examples disclosed herein, such as those referenced. Figure 3 The resource block prediction described. In some examples, aspects of the 1005 operation can be derived from, as referenced... Figure 7 The described allocation prediction component 740 is used to perform this.

[0131] At 1010, the method may include: applying a frequency offset to adjust the local oscillator frequency of the receiving device based on a prediction of at least one resource block allocation to the receiving device, wherein the at least one resource block allocation falls within a threshold frequency distance from the local oscillator frequency, wherein the adjusted local oscillator frequency based on the application of the frequency offset does not overlap with the at least one resource block allocation. The operation of block 1010 may be performed according to examples disclosed herein, such as resource block allocation prediction at 410, selection of the frequency offset magnitude at 415, and / or Figure 2 Various LIF applications. In some examples, aspects of the operation of 1010 can be derived from, as referenced... Figure 7 The frequency offset component 725 is described and used to perform this.

[0132] At 1015, the method may include adjusting the frequency of the down-converted received signal based on the applied frequency offset. The operation of block 1015 may be performed according to examples disclosed herein, such as device parameter adjustment at 420 and offset application at 425. In some examples, aspects of the operation of 1015 may be as described in references... Figure 7 The frequency adjustment component 730 described herein is used to perform this operation.

[0133] At 1020, the method may include receiving one or more downlink messages based on an applied frequency offset and an adjusted frequency of the received signal. Operation of block 1020 may be performed according to examples disclosed herein, such as communication 202 from network entity 105-a to UE 115-a and / or downlink message 301 and / or downlink message 435. In some examples, aspects of the operation of 1020 may be derived from references... Figure 7 The downlink message receiving and sending component 735 described herein is used to perform this action.

[0134] Figure 11 A flowchart illustrating a method 1100 for adaptive placement of a receiver local oscillator frequency to mitigate flicker noise and signal distortion, according to various aspects of this disclosure, is shown. Operation of method 1100 can be implemented by a UE or its components as described herein. For example, operation of method 1100 can be performed by, as described in reference... Figures 1 to 8The UE 115 described herein performs the functions. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0135] At 1105, the method may include: applying a frequency offset to adjust the local oscillator frequency of the receiving device based on a prediction of at least one resource block allocation to the receiving device, wherein the at least one resource block allocation falls within a threshold frequency distance from the local oscillator frequency, wherein the adjusted local oscillator frequency based on the application of the frequency offset does not overlap with the at least one resource block allocation. The operation of block 1105 may be performed according to examples disclosed herein, such as resource block allocation prediction at 410, selection of the frequency offset magnitude at 415, and / or Figure 2 Various LIF applications. In some examples, aspects of the operation of 1105 can be derived from, as referenced... Figure 7 The frequency offset component 725 is described and used to perform this.

[0136] At 1110, the method may include: performing fast frequency hopping and applying a frequency offset before one or more OFDM symbols allocated for a physical downlink shared channel, based on a prediction of allocation for at least one resource block. The operation of block 1110 may be performed according to the examples disclosed herein, such as those referenced. Figure 2 The described fast frequency hopping 225-a, fast frequency hopping 225-b, or fast frequency hopping 225-c and / or the offset at 425 are applied. In some examples, aspects of the operation of 1110 can be derived from, as referenced... Figure 7 The frequency hopping component 745 described herein is used to perform this action.

[0137] At 1115, the method may include: adjusting the frequency of the down-converted received signal based on the applied frequency offset. The operation of block 1115 may be performed according to examples disclosed herein, such as device parameter adjustment at 420 and offset application at 425. In some examples, aspects of the operation of 1115 may be as described in references... Figure 7 The frequency adjustment component 730 described herein is used to perform this operation.

[0138] At 1120, the method may include receiving one or more downlink messages based on an applied frequency offset and the adjusted frequency of the down-converted received signal. Operation of block 1120 may be performed according to examples disclosed herein, such as communication 202 from network entity 105-a to UE 115-a and / or downlink message 301 and / or downlink message 435. In some examples, aspects of the operation of 1120 may be derived from references... Figure 7 The downlink message receiving and sending component 735 described herein is used to perform this action.

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

[0140] Aspect 1: A method for wireless communication at a receiving device, the method comprising: applying a frequency offset to adjust a local oscillator frequency of the receiving device based on 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 does not overlap with the at least one resource block allocation based at least in part on the application of the frequency offset; adjusting the frequency of a down-converted received signal based at least in part on the applied frequency offset; and receiving one or more downlink messages based on the applied frequency offset and the adjusted local oscillator frequency of the down-converted received signal.

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

[0142] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the prediction of the allocation of the at least one resource block 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 according to any one of Aspects 1 to 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 prior to one or more OFDM symbols allocated for the PDSCH, based at least in part on the prediction of the allocation of the at least one resource block.

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

[0145] Aspect 6: The method according to any one of Aspects 1 to 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 that the probability of the at least one resource block allocation falling within the threshold frequency distance from the local oscillator frequency is greater than a threshold probability.

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

[0147] Aspect 9: The method according to any one of Aspects 1 to 7, wherein the threshold frequency distance includes resource blocks of a threshold number from the local oscillator frequency.

[0148] Aspect 10: The method according to any one of Aspects 1 to 11 and Aspect 12, wherein in order to adjust the frequency of the down-converted received signal, the method further comprises: down-converting the received signal at least in part based on applying the frequency offset to the adjusted local oscillator frequency.

[0149] Aspect 13: The method according to any one of Aspects 1 to 14, Aspect 15 and Aspect 10, the method further comprising: selecting the magnitude of the frequency offset based at least in part on a noise distribution curve, the number of resource blocks allocated, or any combination thereof, the noise distribution curve varying with the frequency offset from the local oscillator frequency.

[0150] Aspect 16: The method according to any one of aspects 1 to 17 and aspects 18 to 13, the method further comprising: adjusting at least one or more parameters associated with the baseband filter of the receiving device based at least in part on the magnitude of the frequency offset exceeding an offset threshold, adjusting the sampling frequency of the ADC of 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 according to any one of Aspects 1 to 20 and Aspects 21 to 16, wherein adjusting the frequency of the down-converted received signal comprises: eliminating one or more effects of the applied frequency offset via a digital rotator at the modem of the receiving device.

[0152] Aspect 22: The method according to any one of aspects 1 to 19, wherein the frequency offset includes a LIF offset.

[0153] Aspect 23: The method according to any one of aspects 1 to 22, wherein the at least one resource block allocation includes partial resource block allocation or complete resource block allocation.

[0154] Aspect 24: A receiving device for wireless communication, the receiving device comprising: one or more processors; one or more memories coupled to 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 jointly cause the receiving device to perform the method according to any one of aspects 1 to 23.

[0155] Aspect 25: A receiving device for wireless communication, the receiving device comprising at least one component for performing the method according to any one of aspects 1 to 23.

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. An apparatus for wireless communication at a receiving device, the apparatus comprising: One or more processors; One or more memories, said one or more memories being coupled to said one or more processors; and One or more processor-readable instructions, stored in the one or more memories and executable individually or jointly by the one or more processors, to cause the device to: A frequency offset is applied to adjust the local oscillator frequency of the receiving device based on 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 does not overlap with the at least one resource block allocation, at least in part based on the application of the frequency offset. The frequency of the down-converted received signal is adjusted at least in part based on the applied frequency offset; as well as One or more downlink messages are received based on the applied frequency offset and the adjusted local oscillator frequency of the downconverted received signal.

2. The apparatus of claim 1, wherein, in order to apply the frequency offset to adjust the local oscillator frequency of the receiving device, the one or more processors are capable of operating individually or jointly to cause the apparatus to: The at least one resource block allocation is predicted to fall within the threshold frequency distance of the local oscillator frequency, based at least in part on one or more previous resource block allocations that occurred within a threshold duration prior to the allocation of the at least one resource block.

3. The apparatus of claim 1, wherein the prediction of the allocation of the at least one resource block 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.

4. The apparatus of claim 1, wherein, in order to apply the frequency offset to adjust the local oscillator frequency of the receiving device, the one or more processors are capable of operating individually or jointly to cause the apparatus to: Based at least in part on the prediction of the allocation of the at least one resource block, fast frequency hopping is performed and the frequency offset is applied before one or more orthogonal frequency division multiplexing (OFDM) symbols allocated for the physical downlink shared channel.

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, in order to apply the frequency offset to adjust the local oscillator frequency of the receiving device, the one or more processors are capable of operating individually or jointly to cause the apparatus to: The frequency offset is applied to the local oscillator frequency based at least in part on the probability that the allocation of the at least one resource block falls within the threshold frequency distance from the local oscillator frequency is greater than a threshold probability.

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

8. The apparatus of claim 1, wherein the threshold frequency distance comprises a resource block of a threshold number of distances from the local oscillator frequency.

9. The apparatus of claim 1, wherein, in order to adjust the frequency of the down-converted received signal, the one or more processors are individually or jointly capable of further operating the apparatus to: The received signal is down-converted at least in part based on applying the frequency offset to the adjusted local oscillator frequency.

10. The apparatus of claim 1, wherein the one or more processors are individually or jointly further operable to cause the apparatus to: The magnitude of the frequency offset is selected at least in part based on a noise distribution curve, the number of resource blocks allocated, or any combination thereof, the noise distribution curve varying with the frequency offset from the local oscillator frequency.

11. The apparatus of claim 1, wherein the one or more processors are individually or jointly further operable to cause the apparatus to: The sampling frequency of the analog-to-digital converter of the receiving device is adjusted at least in part based on the magnitude of the frequency offset exceeding an offset threshold, or both, based at least in part on the magnitude of the frequency offset satisfying the offset threshold.

12. The apparatus of claim 1, wherein, in order to adjust the frequency of the down-converted received signal, the one or more processors are capable of operating individually or jointly to cause the apparatus to: One or more effects of the applied frequency offset are eliminated via a digital rotator at the modem of the receiving device.

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

14. The apparatus of claim 1, wherein the at least one resource block allocation includes partial resource block allocation or complete resource block allocation.

15. A method for wireless communication at a receiving device, the method comprising: A frequency offset is applied to adjust the local oscillator frequency of the receiving device based on 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 does not overlap with the at least one resource block allocation, at least in part based on the application of the frequency offset. The frequency of the down-converted received signal is adjusted at least in part based on the applied frequency offset; as well as One or more downlink messages are received based on 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: The at least one resource block allocation is predicted to fall within the threshold frequency distance of the local oscillator frequency, based at least in part on one or more previous resource block allocations that occurred within a threshold duration prior to the allocation of the at least one resource block.

17. The method of claim 15, wherein the prediction of the allocation of the at least one resource block 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: Based at least in part on the prediction of the allocation of the at least one resource block, fast frequency hopping is performed and the frequency offset is applied before one or more orthogonal frequency division multiplexing (OFDM) symbols allocated for the physical downlink shared channel.

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: The frequency offset is applied to the local oscillator frequency based at least in part on the probability that the allocation of the at least one resource block falls within the threshold frequency distance from the local oscillator frequency is greater than a threshold probability.

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

22. The method of claim 15, wherein the threshold frequency distance comprises a resource block of a threshold number of distances from the local oscillator frequency.

23. The method of claim 15, wherein, in order to adjust the frequency of the down-converted received signal, the method further comprises: The received signal is down-converted at least in part based on applying the frequency offset to the adjusted local oscillator frequency.

24. The method according to claim 15, further comprising: The magnitude of the frequency offset is selected at least in part based on a noise distribution curve, the number of resource blocks allocated, or any combination thereof, the noise distribution curve varying with the frequency offset from the local oscillator frequency.

25. The method according to claim 15, further comprising: The sampling frequency of the analog-to-digital converter of the receiving device is adjusted at least in part based on the magnitude of the frequency offset exceeding an offset threshold, or both, based at least in part on the magnitude of the frequency offset satisfying the offset threshold.

26. The method of claim 15, wherein adjusting the frequency of the down-converted received signal comprises: One or more effects of the applied frequency offset are eliminated via a digital rotator at the modem of the receiving device.

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

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

Images