Opportunistic use of low power mode synthesizer and jammer detection

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may opportunistically switch between power modes and may enable and disable a low power mode (LPM) synthesizer to enter a LPM and use the LPM synthesizer when power saving can be achieved without negatively impacting performance, and avoid using the LPM and the LPM synthesizer when doing so would result in performance degradation. The UE may generate a proposal to enter a power mode. The UE may perform one or more measurements and determine whether one or more performance metrics satisfy respective thresholds or conditions. If each of the performance metrics satisfy their respective conditions or thresholds, then the UE may enter the LPM and enable the LPM synthesizer. If any of the performance metrics fail to satisfy a respective threshold, the UE may refrain from entering the LPM mode and enabling the LPM synthesizer.

Description

OPPORTUNISTIC USE OF LOW POWER MODE SYNTHESIZER AND JAMMER DETECTIONCROSS REFERENCE

[0001] The present Application for Patent claims priority to India Provisional Patent Application No. 202441046449 by JIAN et al., entitled “OPPORTUNISTIC USE OF LOW POWER MODE SYNTHESIZER AND JAMMER DETECTION,” filed June 17, 2024, assigned to the assignee hereof, and expressly incorporated by reference in its entirety herein.FIELD OF TECHNOLOGY

[0002] The following relates to wireless communications, including opportunistic use of low power mode synthesizer and jammer detection.BACKGROUND

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

[0004] The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0005] A method for wireless communications by a user equipment (UE) is described. The method may include detecting that each of a first set of parameters corresponding to the downlink traffic satisfy respective thresholds, measuring a set of performance metrics based on each of the first set of parameters satisfying the respective thresholds, and entering a low power mode and enable a low power mode synthesizer based on each of the first set of parameters satisfying the respective thresholds and based on each performance metric of the set of performance metrics satisfying respective thresholds.

[0006] A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the UE to detect that each of a first set of parameters corresponding to the downlink traffic satisfy respective thresholds, measure a set of performance metrics based on each of the first set of parameters satisfying the respective thresholds, and enter a low power mode and enable a low power mode synthesizer based on each of the first set of parameters satisfying the respective thresholds and based on each performance metric of the set of performance metrics satisfying respective thresholds.

[0007] Another UE for wireless communications is described. The UE may include means for detecting that each of a first set of parameters corresponding to the downlink traffic satisfy respective thresholds, means for measuring a set of performance metrics based on each of the first set of parameters satisfying the respective thresholds, and means for entering a low power mode and enable a low power mode synthesizer based on each of the first set of parameters satisfying the respective thresholds and based on each performance metric of the set of performance metrics satisfying respective thresholds.

[0008] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to detect that each of a first set of parameters corresponding to the downlink traffic satisfy respective thresholds, measure a set of performance metrics based on each of the first set of parameters satisfying the respective thresholds, and enter a low power mode and enable a low power mode synthesizer based on each of the first set of parameters satisfying the respective thresholds and based on each performance metric of the set of performance metrics satisfying respective thresholds.

[0009] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, periodically detecting the first set of parameters during a moving time window, determining that the first set of parameters satisfy the respective thresholds based on the detecting, generating a proposal to switch from the first high power mode to a low power mode based on the determining, and confirming the proposal to switch from the first high power mode to the low power mode based on each performance metric of the set of performance metrics satisfying respective thresholds.

[0010] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving control signaling indicating a modulation and coding scheme for the downlink traffic, where one of the first set of parameters includes the modulation and coding scheme.

[0011] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, detecting the first set of parameters may include operations, features, means, or instructions for measuring a block error rate (BLER), measuring a signal to noise ratio (SNR), or referring to a current modulation and coding scheme.

[0012] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based on any of the set of performance metrics failing to satisfy a respective threshold.

[0013] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for switching, via a controller, between the first high power mode, a second high power mode, and the low power mode and disabling the second high power mode based on analog-to-digital-converter sampling rate reduction being unavailable according to one or more current conditions, where enabling a low power mode synthesizer and entering the low power mode may be based on the disabling.

[0014] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, measuring the set of performance metrics may include operations, features, means, or instructions for measuring a signal to noise ratio (SNR) degradation within a set of multiple time intervals of a time window, the set of performance metrics including a reception reciprocal mixing impact metric and setting a value of the reception reciprocal mixing impact metric to indicate an absence of reciprocal mixing impact based on the signal-to-noise ratio (SNR) degradation failing to satisfy a threshold SNR degradation threshold during a threshold quantity of time intervals of the set of multiple time intervals, where enabling the low power mode synthesizer and entering the low power mode may be based on the value indicating the absence of the reciprocal mixing impact.

[0015] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for measuring the SNR degradation within a second set of multiple time intervals of a second time window while operating in the low power mode, setting the value of the reception reciprocal mixing impact metric to indicate a reciprocal mixing impact based on the SNR degradation satisfying the threshold SNR degradation threshold in during the threshold quantity of time intervals of the second set of multiple time intervals, and switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based on setting the value to indicate the reciprocal mixing impact.

[0016] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for measuring the SNR degradation within a third set of multiple time intervals of a third time window while operating in the high power mode, settingthe value of the reception reciprocal mixing impact metric to indicate a reciprocal mixing impact based on the SNR degradation satisfying the threshold SNR degradation threshold in during the threshold quantity of time intervals of the third set of multiple time intervals, and refraining from switching to the low power mode based on setting the value to indicate the reciprocal mixing impact.

[0017] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, measuring the set of performance metrics may include operations, features, means, or instructions for monitoring a transmission power utilized in the high power mode during a transmission window, a reference signal receive power indicated during the transmission window, or both, where the set of performance metrics includes a transmission reciprocal mixing impact metric and setting a value of the transmission reciprocal mixing impact metric to indicate an absence of a reciprocal mixing impact corresponding to an SNR degradation based on the monitoring, where enabling the low power mode synthesizer and entering the low power mode may be based on the value indicating the absence of the reciprocal mixing impact.

[0018] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for monitoring the transmission power utilized in the low power mode during a second transmission window, the reference signal receive power indicated during the second transmission window, or both, setting a value of the transmission reciprocal mixing impact metric to indicate a reciprocal mixing impact corresponding to an SNR degradation based on the monitoring during the second transmission window, and switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based on setting the value to indicate the reciprocal mixing impact.

[0019] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for monitoring the transmission power utilized in the high power mode during a third transmission window, the reference signal receive power indicated during the third transmission window, or both, setting a value of the transmission reciprocal mixing impact metric to indicate a reciprocal mixing impact corresponding toan SNR degradation based on the monitoring during the third transmission window, and refraining from switching to the low power mode based on setting the value to indicate the reciprocal mixing impact.

[0020] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, measuring the set of performance metrics may include operations, features, means, or instructions for computing a first signal to noise ratio (SNR) corresponding to the first high power mode, where the set of performance metrics includes a jammer impact metric and setting a value of the jammer impact metric to indicate an absence of a jammer impact on the first SNR based on the first SNR, where enabling the low power mode synthesizer and entering the low power mode may be based on the value indicating the absence of the jammer impact.

[0021] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for measuring a second SNR corresponding to the low power mode, comparing the second SNR to a projected low power mode SNR based on the first SNR, setting a value of the jammer impact metric to indicate a jammer impact on the second SNR based on a difference between the second SNR and the projected low power mode SNR satisfying a threshold, and switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based on setting the value to indicate the jammer impact on the second SNR.

[0022] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for initiating a timer upon entering the low power mode, switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer upon expiration of the timer, updating the first SNR corresponding to the first high power mode based on the switching upon expiration of the timer, and switching to the low power mode and enabling the low power mode synthesizer based on updating the first SNR.

[0023] In some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein, , measuring the set of performance metricsmay include operations, features, means, or instructions for periodically measuring a first signal to noise ratio (SNR) for a control channel code rate, where the set of performance metrics includes a control channel SNR condition metric and setting a value of the control channel SNR condition metric to indicate that a control channel may be decodable based on a projected SNR for the low power mode that may be based on the first SNR satisfying a first threshold, or based on the first SNR satisfying a second threshold, or both, where enabling the low power mode synthesizer and entering the low power mode may be based on the value indicating that the control channel may be decodable.

[0024] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving one or more reference signals in the low power mode, the one or more reference signals corresponding to an SNR estimate, maintaining the value of the control channel SNR condition metric to indicate that the control channel may be decodable based on a second SNR satisfying the first threshold, and continuing to operate in the low power mode using the low power mode synthesizer.

[0025] Some examples of the method, user equipment (UEs), and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving one or more reference signals in the low power mode, the one or more reference signals corresponding to an SNR estimate, setting the value of the control channel SNR condition metric to indicate that the control channel may be not decodable based on a second SNR failing to satisfy the first threshold, and switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based on setting the value to indicate that the control channel may be not decodable.

[0026] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.BRIEF DESCRIPTION OF THE DRAWINGS

[0027] FIG. 1 shows an example of a wireless communications system that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure.

[0028] FIG. 2 shows an example of a wireless communications system that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure.

[0029] FIG. 3 shows an example of a power mode switching scheme that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure.

[0030] FIG. 4 shows an example of a flow diagram that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure.

[0031] FIG. 5 shows an example of a performance metric determination scheme that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure.

[0032] FIG. 6 shows an example of a process flow that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure.

[0033] FIGs. 7 and 8 show block diagrams of devices that support opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure.

[0034] FIG. 9 shows a block diagram of a communications manager that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure.

[0035] FIG. 10 shows a diagram of a system including a device that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure.

[0036] FIGs. 11 through 13 show flowcharts illustrating methods that support opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION

[0037] A user equipment (UE) may be equipped with multiple synthesizers (e.g., a high power mode (HPM) synthesizer and a low power mode (LPM) synthesizer. The UE may be able to conserve some power by switching between a first HPM (e.g., a mission mode (MM)), and a second power mode (e.g., a LPM using the HPM synthesizer). More power could be conserved when the UE switches to a further LPM using the LPM synthesizer. Further the LPM synthesizer may utilize less space, conserving more physical space for other technology (e.g., antenna panels, synthesizers or the like). However, operations in a LPM using the LPM synthesizer may have a negative impact on performance (e.g., signal to noise (SNR) degradation) in some scenarios. If the UE avoid the LPM using the LPM synthesizer to maintain performance, the UE may expend significant power unnecessarily, resulting in decreased battery life and decreased user experience. However, if the UE enters the LPM and enables the LPM synthesizer in some scenarios, the UE may experience performance degradation (e.g., SNR degradation) due to reciprocal mixing caused by one or more entities via other channels (e.g., wide and strong phase noise resulting from use of the LPM synthesizer may result in jammer power leaking into a downlink channel after down conversion by the LPM synthesizer).

[0038] To improve performance, while conserving power, the UE may opportunistically switch between power modes and may enable and disable the LPM synthesizer to enter the LPM and use the LPM synthesizer when power saving can be achieved without negatively impacting performance, and avoid using the LPM and the LPM synthesizer when doing so would result in performance degradation. The UE may generate a proposal (e.g., a power mode vote) to enter a power mode (e.g., to enter the LPM and enable the LPM synthesizer). The UE may perform one or more measurements and determine whether one or more performance metrics satisfy respective thresholds or conditions. For example, the UE may determine whether the respective thresholds or conditions are satisfied for each of a reception reciprocalmixing impact metric, a transmission reciprocal mixing impact metric, a jamming impact metric, and a control channel decodability metric. If each of the performance metrics satisfy their respective conditions or thresholds, then the UE may enter the LPM and enable the LPM synthesizer per the low power mode proposal. If any of the performance metrics fail to satisfy a respective condition or threshold, then the UE may refrain from entering the LPM mode and enabling the LPM synthesizer. If, while operating in the LPM and using the LPM synthesizer, any of the performance metrics are updated to indicate an SNR degradation (e.g., a respective condition or threshold is not satisfied), then the UE may exit the LPM and disable the LPM synthesizer (e.g., and revert to the MM).

[0039] Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to wireless communications systems, power mode switching schemes, flow diagrams, performance metric determination schemes, and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to opportunistic use of low power mode synthesizer and jammer detection.

[0040] FIG. 1 shows an example of a wireless communications system 100 that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105), one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE- Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

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

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

[0046] In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105), such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or avirtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network entity 105 may include one or more of a central unit (CU), such as a CU 160, a distributed unit (DU), such as a DU 165, a radio unit (RU), such as an RU 170, a RAN Intelligent Controller (RIC), such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

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

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

[0049] For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor), IAB node(s) 104, and one or more UEs 115. The IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130. The IAB donor may include one or more of a CU 160, a DU 165, and an RU 170, in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node(s) 104 may communicate via an Fl interface according to a protocol that defines signaling messages (e.g., an Fl AP protocol). Additionally, or alternatively, the CU 160 may communicate with the core network 130 via an interface, which may be an example of a portion of a backhaul link, and may communicate with other CUs (e.g., including a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of another portion of a backhaul link.

[0050] IAB node(s) 104 may refer to RAN nodes that provide IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities). A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node(s) 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with IAB node(s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through other IAB node(s) 104). Additionally, or alternatively, IAB node(s) 104 may also be referred to as parent nodes or child nodes to other IAB node(s) 104, depending on the relay chain or configuration of the AN. The IAB-MT entity of IAB node(s) 104 may provide a Uu interface for a child IAB node (e.g., the IAB node(s) 104) to receive signaling from a parent IAB node (e.g., the IAB node(s) 104), and a DU interface (e.g., a DU 165) may provide a Uu interface for a parent IAB node to signal to a child IAB node or UE 115.

[0051] For example, IAB node(s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both. An IAB donor may include a CU 160 with a wired or wireless connection (e.g., backhaul communication link(s) 120) to the core network 130 and may act as a parent node to IAB node(s) 104. For example, the DU 165 of an IAB donor may relay transmissions to UEs 115 through IAB node(s) 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of the IAB donor may signal communication link establishment via an Fl interface to IAB node(s) 104, and the IAB node(s) 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through one or more DUs (e.g., DUs 165). That is, data may be relayed to and from IAB node(s) 104 via signaling via an NR Uu interface to MT of IAB node(s) 104 (e.g., other IAB node(s)). Communications with IAB node(s) 104 may be scheduled by a DU 165 of the IAB donor or of IAB node(s) 104.

[0052] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support test as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180).

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

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

[0055] The UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link(s) 125 (e.g., one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link(s) 125. For example, a carrier used for the communication link(s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105).

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

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

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

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

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

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

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

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

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

[0065] A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)). In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smallerareas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.

[0066] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a network entity 105 operating with lower power (e.g., a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG), the UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells and may also support communications via the one or more cells using one or multiple component carriers.

[0067] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband loT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.

[0068] In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110. In some examples, coverage areas 110 (e.g., different coverage areas) associated with different technologies may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105). In some other examples, overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105). The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

[0069] The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network entities (e.g., different ones of the network entities 105) may be approximately aligned in time. For asynchronous operation, network entities 105 may have different frame timings, and transmissions from different network entities (e.g., different ones of network entities 105) may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

[0070] Some UEs 115, such as MTC or loT devices, may be relatively low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0071] Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs 115 may include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type that is associatedwith a defined portion or range (e.g., set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a carrier, or outside of a carrier.

[0072] The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC). The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

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

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

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

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

[0077] The wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170), and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate using antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.

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

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

[0080] The network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

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

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

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

[0084] In some examples, transmissions by a device (e.g., by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115). The UE 115 may reportfeedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI- RS)), which may be precoded or unprecoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170), a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device).

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

[0086] The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP -based. An RLC layer may perform packet segmentation and reassembly to communicate via logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.

[0087] The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link(s) 125, a D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal -to-noise conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

[0088] A UE 115 may opportunistically switch between power modes and may enable and disable the LPM synthesizer to enter the LPM and use the LPM synthesizer when power saving can be achieved without negatively impacting performance, and avoid using the LPM and the LPM synthesizer when doing so would result in performance degradation. The UE may generate a proposal (e.g., a power mode vote) to enter a power mode (e.g., to enter the LPM and enable the LPM synthesizer). The UE 115 may perform one or more measurements and determine whether one or more performance metrics satisfy respective thresholds or conditions. For example, the UE 115 may determine whether the respective thresholds or conditions are satisfied for eachof a reception reciprocal mixing impact metric, a transmission reciprocal mixing impact metric, a jamming impact metric, and a control channel decodability metric. If each of the performance metrics satisfy their respective conditions or thresholds, then the UE 115 may enter the LPM and enable the LPM synthesizer per the low power mode proposal. If any of the performance metrics fail to satisfy a respective condition or threshold, then the UE 115 may refrain from entering the LPM mode and enabling the LPM synthesizer. If, while operating in the LPM and using the LPM synthesizer, any of the performance metrics are updated to indicate an SNR degradation (e.g., a respective condition or threshold is not satisfied), then the UE may exit the LPM and disable the LPM synthesizer (e.g., and revert to the MM).

[0089] FIG. 2 shows an example of a wireless communications system 200 that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure. The wireless communications system 200 may implement, or be implemented by, the wireless communications system 200. For example, the wireless communications system 200 may include a UE 115-a, and a network entity 105-a, which may be examples of corresponding devices described with reference to FIG. 1.

[0090] The UE 115-a and the network entity 105-a may communicate with each other (e.g., via a bidirectional communication link 205). Wireless communications performed by the UE 115-a may expend power. Techniques to conserve power may result in extended battery life and improved user experience. Such techniques may include switching between one or more high power modes (HPMs), and one or more low power modes (LPMs). For example, HPM communications may result in improved performance of wireless communications, but may expend more power. LPM communications may result in improved power conservation, but may negatively impact performance of wireless communications in some (but not all) scenarios. Thus, if the UE 115-a can enter a LPM (e.g., using a LPM synthesizer 210) in the right scenarios, and switch back to the HPM in other scenarios, the UE 115-a may be able to effectively conserve power (e.g., when the HPM is not needed to maintain high performance), without negatively impacting performance. Techniques described herein refer to mechanisms by which such switching may be effectively and opportunistically employed.

[0091] The UE 115-a may support one or multiple synthesizers (e.g., frequency synthesizers. The UE 115-a may support a HPM synthesizer 215 (which may be referred to as a HPM synth) and a LPM synthesizer 210 (which may be referred to as a LPM synth). The LPM synth may include one or more ring oscillators 220 (e.g., the low frequency (LF) ring oscillator 220-a and the high frequency (HF) ring oscillator 220-b). The LP ring oscillators may consume a small amount of power (e.g., compared to another oscillator, such as a voltage control oscillator (VCO)). The LP synthesizer 210 may also utilize a reduced area with reference to the HP synthesizer 215. For example, the LP synthesizer 210 may utilize a small percentage of the physical area utilized by the HP synthesizer 215. Thus, the smaller size of the LP synthesizer may free up space on the UE 115-a for other uses (e.g., other synthesizers, chips, antenna panels, etc.), and may utilize a small amount of power resulting in reduced power expenditure.

[0092] In some examples, the ring oscillators 220 may utilize one or more inverters (e.g., one or more NOT gates) attached in a chain, such that the output of the last inverter in the chain is fed back into the first inverter in the chain. The odd number of inverters in a ring may oscillate an output between two voltage levels (e.g., representing true or false values). The stages of the ring oscillator may include differential stages, and thus may be more resistant to external disturbances. In some examples, the ring oscillators 220 may utilize a mix of inverting and non-inverting stages. A VCO for a phase-locked loop (PLL) may be built from one or more ring oscillators 220. In the case of the LPM synthesizer 210, a digital-to-time converter (DTC) based sampling PLL architecture may be implemented. The DTC may be a digitally-controlled delay stage that may cancel out an error of the PLL (e.g., a quantization error or phase error corresponding to a modulator and a range of the modulator). The DTC may output a reference frequency frand a divided frequency fv, which may be provided as inputs to a phase frequency detector (PFD). The reference frequency frand the divided frequency fvmay be provided via the DTC to a phase detector (e.g., a bang-bang phase detector or baseband phase detector). The PFD may generate one or more output signals (e.g., a pump op (PU) signal and a pump down (PD) signal) to a charge pump (CHP) (e.g., based on a difference between the frand the fv. The CHP may provide one or more output signals to the oscillators 220 (e.g., the LF oscillator 220-a and the LF oscillator 220-b). In some examples, the output signal may be provided via a variable capacitancemultiplier (VCP). The output signal may also be processed (e.g., one or more times, such as two times) by a VCO low dropout (LDP) regulator (e.g., the output of which may be input into the ring oscillators 220). One or more outputs from the ring oscillator 220-a may be multiplexed (e.g., with or according to a division output), and one or more outputs of the ring oscillator 220-a may be multiplexed via a PLL multiplexer with one or more outputs of the ring oscillator 220-b. The PLL multiplexer may multiplex an output of the DTC via a divider (an N-divider corresponding to the error cancelation at the DTC) with an output from the ring oscillator 220-a and the ring oscillator 220-b.

[0093] The ring oscillators 220 may perform rate oscillation. Phase noise bandwidth and magnitude of phase noise may be higher in the LP synthesizer 210 as compared to the HP synthesizer 215. The LP synthesizer may also support a wide phase noise bandwidth, which may result in reciprocal mixing (e.g., when an undesired signal is present (interference or jammer signals), signal quality may be reduced (e.g., signal to noise ratio (SNR) may be degraded)).

[0094] Power savings may be impacted by one or more parameters or mechanisms. For example, the UE 115-a may adjust an analog-to-digital converter (ADC) sampling rate, utilize a PLL, perform a low noise amplifier (LNA) gain state (GS) bypass, perform an frequency domain residual side band (FDRSB) order reduction, support or adjust baseband filter (BBF) linearity, or perform an ADC order reduction, to reduce power consumption. The UE 115-a may support various power modes.

[0095] For example, the UE 115-a may be capable of utilizing a PLL procedure using a HPM synthesizer 215 in some power modes (e.g., MM), but may be capable of using the LPM synthesizer 210 in other power modes. Power modes may be based on downlink traffic and SNR. The UE 115-a may enable the LPM synthesizer 210 when downlink traffic can be supported with a low SNR, or when receiving physical downlink control channel (PDCCH) signaling (e.g., but not data signaling or other signaling). The UE 115-a may reduce the ADC frequencies when downlink traffic can be supported with mid-level (e.g., reduced) SNR. However, if the UE 115-a switches to a LPM (e.g., using the LPM synthesizer 210) in a scenario in which SNR is or will subsequently be degraded by operation in a LPM or using the LPM synthesizer 210, the UE may conserve power at the expense of consistent performance. Alternatively, if the UE 115-a does not switch to a LPM or utilize the LPM synthesizer 210 in scenario inwhich LPM communications would not negatively impact SNR or performance, the UE 115-a may unnecessarily increase power expenditure and decrease battery life, resulting in decreased user experience and inefficient use of available power.

[0096] As described herein, the UE 115-a may opportunistically switch between power modes and use of the LPM synthesizer 210 and the HPM synthesizer 215 (e.g., resulting in increased power savings) based on one or more parameters and one or more metrics (e.g., in decrease or avoid any negative impact on communication performance). For example, the UE 115-a may generate one or more votes regarding whether to switch power modes (e.g., from a HPM utilizing the HPM synthesizer 215 to a LPM utilizing the LPM synthesizer) based on one or more parameters. For instance, the UE 115-a may detect a configured MCS, may monitor for downlink traffic and measure or otherwise detect a BLER, and may generate a vote (e.g., a proposal) for switching from the HPM to the LPM (e.g., whether to enable the LPM synthesizer 210). Additionally, or alternatively, the UE 115-a may generate a vote (e.g., a proposal) regarding whether the UE 115-a should switch power modes (e.g., from a HPM utilizing the HPM synthesizer 215 to a LPM utilizing the LPM synthesizer) based on measured or detected SNR. If the UE 115-a is operating in HPM, and one or more votes based on the parameters fails to recommend switching to the LPM and utilizing the LPM synthesizer 210, then the UE 115-a may refrain from switching power modes. If the one or more votes based on the parameters result in a proposal (e.g., vote) to switch to the LPM and utilize the LPM synthesizer 210, then the UE 115-a may verify (e.g., confirm) the proposal by checking (e.g., measuring or otherwise detecting) one or more performance metrics (e.g., to ensure that such a switch in power mode and / or enabling the LPM synthesizer 210 will not negatively impact performance, such as SNR). For example, the UE 115-a may determine whether reciprocal mixing impact at the LPM synthesizer is detected (e.g., may set an adjacent channel interference (ACI) reciprocal mixing impact detection metric to true or false (e.g., 1 or 0)), may determine whether a transmission reciprocal mixing impact at the LPM synthesizer is detected (e.g., may set a transmission reciprocal mixing impact detection result metric to true or false (e.g., 1 or 0)), may determine whether a jammer detection result impact at the LPM synthesizer 210 is detected (e.g., may set a jammer detection result metric to true or false (e.g., 1, or 0)), and may determine whether PDCCH signaling is decodeable by the UE 115-a whenusing the LPM synthesizer 210 (e.g., may set a PDCCH decodability result metric to true or false (e.g., 1 or 0).

[0097] The UE 115-a may support a controller (e.g., a 3-mode controller), as described with reference to FIG. 3. The controller may consider multiple power modes (e.g., 3 power modes) including a LPM using the LPM synthesizer 210. The UE 115-a may include (e.g., the controller may include) a jammer detector (e.g., for a baseband signal I such as a baseband signal (e.g., IBB1 or IBB2) or out of band (OOB) jammers), a detector of reciprocal mixing from ACS and jammers (e.g., such as the first baseband signal I (e.g., IBB1), a detector of reciprocal mixing from transmission signals, a checker (e.g., detector or verifier) of PDCCH decodability, or any combination thereof.

[0098] FIG. 3 shows an example of a power mode switching scheme 300 that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure. The power mode switching scheme 300 may implement, or be implemented by, aspects of the wireless communications system 100 and the wireless communications system 200. For example, a device (e.g., a UE 115 or a network entity 105), which may be an example of corresponding devices described with reference to FIG. 1, may include a controller 305, which may implement the power mode switching scheme 300.

[0099] The controller 305 may manage switching between power modes. For example, the device may support one or more power modes including one or more HPMs (e.g., MM 320) and one or more LPMs (e.g., LPM 310 and LPM 315. In some examples, the device may operate with an LPM synthesizer (e.g., such as the LPM synthesizer 210) enabled for some power modes (e.g., the set of power modes 325), and the device may operate with a HPM synthesizer (e.g., such as the HPM synthesizer 215) enabled for other power modes (e.g., the set of power modes 330). The LPM 310 may be an example of power mode utilizing the LPM synthesizer, and the LPM 315 may be an example of a power mode utilizing a reduced ADC sampling rate and the HPM synthesizer.

[0100] As described herein, the controller 305 may switch between power modes according to one or more inputs. The inputs may include one or more votes (e.g., a power mode vote), which may be based on SNR or downlink traffic (e.g., a configuredMCS, a BLER, etc.), or both. A power mode vote may refer to a recommendation or a proposal as to whether or not the controller is to shift from a current power mode to another power mode. The vote or proposal may refer to a parameter value, which may be set based on one or more measurements or conditions (e.g., as described in greater detail with reference to FIG. 4). For example, if a measured SNR or a configured MCS satisfy one or more threshold values, then the parameter value may be set to a value (e.g.,1) indicating a vote or proposal to switch from a current power mode (e.g., the MM 320) to another power mode (e.g., the LPM 310). Such a parameter value (e.g., vote) may be input into the controller 305. If the vote indicates that the controller 305 is to move switch from a current power mode to another power mode (e.g., from the MM 320 to the LPM 310), then the controller 305 may consider additional metric values, such as performance metrics (e.g., to verify or confirm the vote input). The additional performance metric values may include an ACI reciprocal mixing impact detection metric (e.g., which may be referred to as RCP mix), a jammer detection result (e.g., which may be referred to as Jam impact), a transmission reciprocal mixing impact detection result (e.g., which may be referred to as Tx Rcp mix), and a PDCCH decodability result (e.g., which may be referred to as PDCCH Decodable). In some examples, the performance metrics may be set at a particular value (e.g., 1 or 0 indicating true or false).

[0101] The values of the performance metrics may be set and input into the controller 305 (e.g., based on one or more measurements, predictions, detections, or the like). The performance metric Jam impact (e.g., if set to true, or 1) may indicate a detected SNR impact due to reciprocal mixing with IBB2 or OOB jammers, or due to a jammer around the ADC frequencies. If such jamming is detected, the controller 305 may refrain from switching from the MM 320 or the LPM 315 to the LPM 310, or may switch back from the LPM 310 to the MM 320 (e.g., even if the vote indicates a switch to the LPM 310 and all other performance metrics confirm the vote). The performance metric Rcp mix (e.g., if set to true, or 1) may indicate a detection of an SNR impact due to reciprocal mixing with ACI and IBB1 jammers. If such jamming is detected, the controller 305 may refrain from switching from the MM 320 or the LPM 315 to the LPM 310, or may switch back from the LPM 310 to the MM 320 (e.g., even if the vote indicates a switch to the LPM 310 and all other performance metrics confirm the vote).The performance metric Tx Rcp mix may apply to frequency division duplex bands, and may indicate a detection of SNR impacts by reciprocal mixing corresponding to a transmission signal in the FDD band. If such SNR impact is detected, the controller 305 may refrain from switching from the MM 320 or the LPM 315 to the LPM 310, or may switch back from the LPM 310 to the MM 320 (e.g., even if the vote indicates a switch to the LPM 310 and all other performance metrics confirm the vote). The performance metric PDCCH decodable (e.g., if set to true, or 1) may indicate that PDCCH can be decoded even after enabling the LPM synthesizer. If the performance metric PDCCH decodable is set to false, or 0, then the performance metric may indicate that PDCCH signaling is not (e.g., or will not be) decodable if the LPM synthesizer is enabled. If such is the case, the controller 305 may refrain from switching from the MM 320 or the LPM 315 to the LPM 310, or may switch back from the LPM 310 to the MM 320 (e.g., even if the vote indicates a switch to the LPM 310 and all other performance metrics confirm the vote).

[0102] For instance, if the device is operating in the MM 320 with the HPM synthesizer enabled, the controller 305 may determine that a vote input indicates a proposal (e.g., based on the MCS, BLER, SNR, or any combination thereof) to switch to the LPM 310 and enable the LPM synthesizer. The controller may also consider other performance metrics (e.g., inputs). If all additional performance metrics are acceptable and aligned with the vote, then the controller 305 may switch from the MM 320 to the LPM 310, disable the HPM synthesizer, and enable the LPM synthesizer. For example, if the Rcp mix, Jam impact, and Tx Rcp mix metrics are all set to 0 (e.g., indicating no detected jamming or interference or SNR degradation that satisfies a threshold or minimum amount of detected or predicted SNR), and the PDCCH decodable is set to 1 (e.g., indicating that PDCCH signaling will be decodable with the LPM synthesizer), then the controller 305 may switch from the MM 320 to the LPM 310, disable the HPM synthesizer, and enable the LPM synthesizer. If, while operating in the LPM 310 using the LPM synthesizer, any of the performance metrics fail (e.g., any one of the Rcp mix, Jam impact, and Tx Rcp mix metrics are set to 1, or the PDCCH decodable is set to 0), then the controller 305 may switch from the LPM 310 to the MM 320, disable the LPM synthesizer, and enable the HPM synthesizer.

[0103] The controller 305 may similarly switch between the MM 320 and the LPM 315 based on one or more parameters (e.g., a proposal or power mode vote) and one or more performance metrics. For example, the device may generate a power mode vote (e.g., a proposal) based on one or more parameter values (e.g., a proposal to switch from the MM 320 to the LPM 315), and may verify (e.g., confirm) the vote based on one or more performance metrics. In some examples, the performance metrics used to confirm a switch from the MM 320 to the LPM 315 may include one or more of the performance metrics used to confirm a switch from the MM 320 to the LPM 310 (e.g., but may not include all of the same performance metrics used to confirm a switch from the MM 320 to the LPM 310). For instance, based on generating a vote to switch from the MM 320 to the LPM 315, the device may check (e.g., input into the controller 305) one or more performance metrics (e.g., the Jam impact metric, the Rcp mix metric, and the Tx rcp mix metric). If the one or more performance metrics satisfy one or more thresholds (e.g., the Jam impact metric is set to 0 indicating no more than a threshold amount of detected jamming impact, the Rcp mix metric is set to 0 indicating no more than a threshold amount of detected SNR degradation due to reciprocal mixing, and the Tx rcp mix metric is set to 0 indicating no more than a threshold amount of detected SNR degradation due to transmission-based reciprocal mixing), then the controller 305 may switch from the LPM 315. The device may continue to check (e.g., measure or otherwise detect) the performance metrics. If any of the performance metrics fail to satisfy a threshold, the controller 305 may switch from the LPM 315 to the MM 320.

[0104] The device may generate a power vote (e.g., a proposal) to switch from a current LPM to the MM 320. For instance, if operating in the LPM 315, the device may generate (e.g., an input into the controller 305) a power mode vote to MM 320. If one or more performance metrics satisfy a threshold (e.g., the Jam impact metric is set to 1, the Rcp mix metric is set to 1, the Tx rcp mix metric is set to 1, or if any one of the performance metrics is set to 1), then the controller 305 may switch from the LPM 315 to the MM 320. Similarly, while operating in the LPM 310, the device may generate (e.g., may input into the controller 305) a power mode vote proposing to switch from the LPM 310 to the LPM 315. If one or more performance metrics confirms the power mode vote (e.g., the Rcp mix metric is set to 0, the Jam impact metric is set to 0, the PDCCH decodable metric is set to 1, the Tx Rcp mix is set to 0), then the controller305 may switch the LPM 310 to the LPM 315, and may disable the LPM synthesizer and enable the HPM synthesizer. In some examples, the controller 305 may switch the LPM 310 to the LPM 315 if all of (e.g., or a threshold quantity of) the performance metrics satisfies a threshold. In some examples, if any one of the performance metrics fails to satisfy a threshold, then the controller 305 may (e.g., by default or according to one or more rules or conditions) switch from the LPM 310 to the MM 320 (e.g., disabling the LPM synthesizer and enabling the HPM synthesizer).

[0105] In some examples, the device (e.g., while operating in the LPM 315 and using the HPM synthesizer) may generate a power mode vote proposing to switch from the LPM 315 to the LPM 310 (e.g., and disable the HPM synthesizer and enable the LPM synthesizer). In such examples, the controller 305 may verify one or more performance metric inputs to confirm (e.g., or deny) the proposal. In some examples, if all of a set of performance metrics satisfy a threshold (e.g., the Rcp mix metric is set to 0, the Jam impact metric is set to 0, the PDCCH decodable metric is set to 1, the Tx Rcp mix is set to 0), then the controller 305 may switch from the LPM 315 to the LPM 310. In some examples, if any one of the set of performance metrics fails to satisfy a threshold (e.g., if the Rcp mix metric is set to 1, the Jam impact metric is set to 1, the PDCCH decodable metric is set to 0, pr the Tx Rcp mix is set to 1), then the controller 305 may refrain from switching from the LPM 315 to the LPM 310 (e.g., may override the power mode vote). Similarly, while operating in the LPM 310 (e.g., based on a confirmed power mode vote switching form the LPM 315, or the MM 320), the controller 305 may periodically determine (e.g., calculate) the one or more parameter values corresponding to a recent or pending power mode vote, determine (e.g., calculate) the one or more performance metric values, or both. If the parameter values fail to satisfy one or more thresholds, the performance metrics fail to satisfy one or more thresholds, or both, then the controller 305 may switch out of the LPM 310 (e.g., to the MM 320, or back to the LPM 315).

[0106] In some examples, the device (e.g., while operating in the LPM 310 and using the LPM synthesizer) may generate a power mode vote proposing that the controller 305 switch from the LPM 310 to the MM 320 (e.g., based on one or more parameter values, such as BLER, MCS, SNR, etc.). The device may determine (e.g., measure or calculate) one or more performance metrics to confirm the vote. Forexample, if one or more performance metrics indicate jammers, interference, degradation of SNR, or that PDCCH signaling is not decodable (e.g., if any one of the Rcp mix metric is set to 1 indicating detected reciprocal mixing in the LPM 310, the Jam impact metric is set to 1 indicated detected jamming in the LPM 310, the PDCCH decodable metric is set to 0 indicating that PDCCH signaling is not decodable in the LPM 310, or the Tx_Rcp-mix metric is set to 1 indicating detected reciprocal mixing corresponding to transmission), then the controller 305 may switch from the LPM 310 to the MM 320 (e.g., and disable the LPM synthesizer and enable the HPM synthesizer). In some examples, the controller 305 may initiate the switch from the LPM 310 to the MM 320 if any of the performance metrics fail to satisfy a threshold (e.g., in combination with an MM vote, or regardless of a previous power mode vote).

[0107] In some examples, the controller 305 may switch from a 3 -mode controller to a 2-mode controller (e.g., a 2-power mode controller) if one or more conditions are satisfied. In such examples, the controller 305 may manage switching between a single HPM (e.g., MM 320 with the HPM synthesizer enabled) and a single LPM (e.g., the LPM 310 with the LPM synthesizer enabled). For example, the controller 305 may fall back to a default controller setting (e.g., 2-power mode controller) if reduced ADC frequencies do not provide a power advantage (e.g., if a bandwidth is less than or equal to a threshold, such as 10 MHz). In some examples, the controller 305 may switch to a 2-power mode controller if jammers around a reduced ADC frequency cannot be reliably detected (e.g., if a TRS is not configured, if a high-speed scenario is detected, such as a high-speed train (HST) deployment, in which case a HST detector value may be set to 1). In some examples, the controller 305 may switch to a 2-power mode controller if a reduced ADC frequency is not supported or allowed.

[0108] The power mode vote described herein may be based on downlink traffic. For example, the device may generate a power mode vote based on a configured MCS, based on a measured BLER, or the like. The device may evaluate the downlink traffic parameters (e.g., measure BLER or refer to a most recently configured MCS) periodically (e.g., every 10 ms). In some examples, the downlink traffic parameters may be computed during a moving average window. The UE may consider whether one or more conditions are satisfied for decoding downlink grants with the LPM synthesizer enabled (e.g., may generate a power mode vote based on measurements or detection ofthe one or more parameters). In some examples, threshold MCS, BLER, SNR, or the like, may be different for various power mode votes (e.g., may be different for a switch from the MM 320 to the LPM 315, than for a switch from the MM 320 to the LPM 310). In some examples, the device may detect MCS and BLER during the moving average window, and may determine whether (e.g., for a given power mode or power mode vote) a threshold MCS, a threshold BLER (e.g., BLER TH), or both, is satisfied. For instance, the device may generate a vote (e.g., proposal) to switch from the MM 320 to the LPM 310 if the MCS is less than a threshold (e.g., the LPM 310 MCS LOW) and if the BLER is less than a threshold (e.g., the LPM 310 BLER LOW). If the MCS or the BLER, or if both, fail to satisfy the relevant thresholds, then the controller 305 may refrain from generating a vote to switch from the MM 320 to the LPM 310 (e.g., from inputting the vote to the controller 305). If the MCS is higher than the LPM 315 MCS HIGH threshold, or if BLER is higher than the LPM 315_ BLER HIGH, then the device may input the power mode vote to change from the LPM 310 to MM 320 (e.g., the controller 305 may switch from the LPM 310 to the MM 320, or if operating in the MM 320 mode may refrain from switching form the MM 320 to the LPM 310). The current MCS and RI, BLER, or both, may be considered in any given scenario to determine whether to generate a power mode vote.

[0109] In some examples, the device may determine whether to generate a power mode vote to switch between the MM 320 and the LPM 315. For example, if the MCS is less than an MCS threshold (e.g., LPM 315 MCS LOW), or if the BLER is less than a LPM 315 BLER LOW, or both, then the controller 305 may generate a power mode vote to switch from the MM 320 to the LPM 315. If the MCS, the BLER, or both, are higher than the respective thresholds for the given MCS and RI, then the controller 305 may refrain from entering a power mode vote, or from switching from the MM 320 to the LPM 315. If the device is operating in the LPM 315, then a power mode vote may be generated if the MCS is greater than a threshold (e.g., LPM 315 MCS HIGH), or the BLER is greater than a threshold (e.g., LPM 315 BLER HIGH), or both. If the respective thresholds are not satisfied, then the device may refrain from entering a power mode vote to switch form the LPM 315 to the MM 320 (e.g., or may refrain from switching between the LPM 315 to the MM 320 regardless of any performance metrics).

[0110] In some examples, the device may determine whether to generate a power mode vote to switch between the LPM 315 and the LPM 310. For example, if the MCS satisfies a threshold (e.g., is less than an LPM 310 MCS LOW threshold), the BLER is less than a threshold (e.g., an LPM 310 BLER LOW threshold), or both, then a power mode vote to switch from the LPM 315 to the LPM 310 may be generated. If the thresholds are not satisfied, then no such power mode vote may be generated. Similarly, when the device is operating in the LPM 310, if the MCS is greater than a threshold (e.g., is greater than an LPM 310 MCS HIGH threshold), the BLER is greater than a threshold (e.g., greater than theLPM 310 BLER HIGH threshold), then a power mode vote to switch from the LPM 310 to the LPM 315 may be generated.[OHl] In some examples, the power mode vote may be based on a measured SNR. The SNR may be measured based on the time window (e.g., may be evaluated if no grant is received during the time window). If such is the case, then the device may measure the SNR, and determine whether an SNR satisfies a threshold. If the device is operating in the MM 320, then a power mode vote to switch from the MM 320 to the LPM 310 may be generated if the SNR is less than a threshold (e.g., less than the LPM 310 SNR LOW threshold). For instance, if the SNR is less than LPM 310 SNR LOW, then the power mode vote to switch from the MM 320 to the LPM 310 may be generated. If the SNR is greater than the threshold, then no such power mode vote may be generated (e.g., and the controller 305 may maintain operation in the MM 320). If the UE is operating in the LPM 310, and the SNR is greater than the LPM 315 SNR HIGH threshold , then the controller 305 may switch back from the LPM 310 to the MM 320 (e.g., in some examples, the device may generate a power mode vote to switch from the LPM 310 to the MM 320, in some examples the controller 305 may automatically switch back to the MM 320 if the SNR is greater than the threshold ).

[0112] The controller 305 may manage switching between the MM 320 and the LPM 315 based on the SNR (e.g., if no downlink grant is received during a time window). If the device is operating in the MM 320 and the SNR is less than the LPM 315 SNR LOW threshold, then the power mode vote to switch from the MM 320 to the LPM 315 may be generated (e.g., and if the threshold is not satisfied, then such a vote may not be generated). If the device is operating in the LPM 315 and the SNR is greater than the LPM 315 SNR HIGH threshold, then the controller 305 may switch from theLPM 315 to the MM 320 (e.g., automatically, or based on a generated power mode vote).

[0113] The controller 305 may manage switching between the LPM 315 and the LPM 310. If device is operating in the LPM 315 and the SNR is less than the LPM 310 SNR LOW, then the vote to enter the LPM 310 may be generated (e.g., or may not be generated if the SNR is higher than LPM 310 SNR LOW). If the device is operating in the LPM 310 and the SNR is greater than the LPM 310 SNR HIGH threshold, then the controller 305 may switch from the LPM 310 to the LPM 315 (e.g., automatically, or based on a generated power mode vote).

[0114] Generating power mode votes based on such parameters is further discussed with reference to FIG. 4.

[0115] FIG. 4 shows an example of a flow diagram 400 that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure. The flow diagram 400 may implement, or be implemented by, aspects of the wireless communications system 100 and the wireless communications system 200 and the power mode switching scheme 300. For example, a device (e.g., a UE 115 or a network entity 105), which may be an example of corresponding devices described with reference to FIGs. 1-3, may perform aspects of the flow diagram 400.

[0116] At 405, the device may receive one or more metrics. For example, a downlink grant may be received, which may indicate an MCS, a RI, etc. The device may perform one or more measurements, or receive an indication of, a BLER. At 410, the device may update one or more parameter values (e.g., may update an MCS, a measured SNR, a received grant, etc.

[0117] At 415, the device may determine if and when a grant (e.g., a downlink grant) has been received. For example, the device may determine whether a time window (e.g., an amount of time or a timer initiated upon receipt of a most recently received grant) has expired. If a downlink grant has been received during the time window, then a power mode vote may be cast (e.g., based on the MCS and the BLER, which may have been updated at 410). For example, if a downlink grant has been received within the time window, then the device may set a parameter value Igrant to 1(e.g. Igrant > 0)- Then at 435, the device may perform a 3-state MCS and BLER test, and may generate a power mode vote based thereon. For example, the device may determine whether the MCS and the BLER satisfies a first threshold (e.g., the MCS is lower than LPM 310 MCS LOW threshold and the BLER is lower than LPM310 BLER LOW threshold), in which case the device may enter a vote to switch to the LPM 310 and enable the LPM synthesizer. If the device determines that the MCS and BLER satisfy a second threshold (e.g., the MCS is higher than LPM 315 MCS HIGH threshold and the BLER is higher than LPM 315 BLER HIGH threshold), the device may enter a vote to switch to or remain in the MM 320. If the device is operating in the MM 320 and determines that MCS is lower than LPM 315 MCS LOW threshold or the BLER is lower than LPM 315 BLER LOW threshold, the device may enter a vote to switch to the LPM 315. If the device is operating in the LPM 310 and determines that MCS is higher than LPM 310 MCS HIGH threshold or the BLER is higher than LPM 310 BLER HIGH threshold, the device may enter a vote to switch to the LPM 315.

[0118] If, at 415, the device determines that Igrant is not greater than 0, then the device may determine whether an SNR value satisfies a threshold. For example, if no downlink grant has been received in the first time window but downlink grant has been received during a second longer window, then the device may set a parameter value to 1 (e.g., {activity > 0)at420. In such examples, the device may cast a power mode vote based on the SNR. For example, at 425, the device may perform a 3-state SNR test and determine whether the SNR satisfies a first threshold (e.g., is less than LPM310 SNR LOW threshold, in which case the device may cast a vote to switch to the LPM 310), whether the SNR satisfies a second threshold (e.g., is higher than LPM 315 SNR HIGH threshold, in which case the device may cast a vote to remain in or switch to the MM 320). If the device is operating in the MM 320 and determines that SNR is lower than LPM 315 SNR LOW threshold, the device may enter a vote to switch to the LPM 315. If the device is operating in the LPM 310 and determines that SNR is higher than LPM 310 SNR HIGH threshold, the device may enter a vote to switch to the LPM 315.

[0119] If, at 420, the device determines that no downlink grant has been received in the second (longer) time window (e.g., {activity is set to 0 and is not greater than 0), then the device may generate a default power mode vote, and may switch to a LPM at 430(e.g., switch to the LPM 310 and enable the LPM synthesizer), resulting in increased power savings.

[0120] Having cast a power mode vote, in some examples, the device may verify the vote (e.g., the proposed power mode switch) according to one or more performance metrics, such as a reciprocal mixing metric (e.g., Rcp mix) or a transmission-based reciprocal mixing metric (e.g., Tx-Rcp_mix) as described in greater detail with reference to FIG. 5.

[0121] FIG. 5 shows an example of a performance metric determination scheme 500 that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure. The performance metric determination scheme 500 may implement, or be implemented by, aspects of the wireless communications system 100, the wireless communications system 200, the power mode switching scheme 300, and the flow diagram 400. For example, a device (e.g., a UE 115 or a network entity 105), which may be an example of corresponding devices described with reference to FIGs. 1-4, may perform aspects of the performance metric determination scheme 500.

[0122] Power leakage onto a downlink channel (e.g., generated by or caused by interference or jammers) may occur in some transmission modes. For example, a small (e.g., minimal) amount of power leakage to DL channels is guaranteed when the HPM synthesizer is enabled (e.g., in the set of power modes 330). However, LPM synthesizer use may result in wide and strong phase noise, which may cause jammer power leakage into the downlink channel (e.g., after down conversion by the LPM synthesizer. The SNR impact may be neglected in some scenarios (e.g., some low jammer regimes). However, in other scenarios (e.g., a high jammer regime), SNR impact may be neglected if the difference between signal power and jammer power is sufficiently high. The device may detect whether a switch to a LPM (e.g., and use of the LPM synthesizer) will result in jamming that will have a negative SNR impact, or not, and may set one or more performance metric values (e.g., Rcp mix) to indicate whether such a negative SNR impact is detected or predicted.

[0123] The device may set the reciprocal mixing impact metric using the controller 505-a (e.g., or may input the reciprocal mixing impact metric into a controller 505-a).The device may determine that reciprocal impact is occurring or will occur (e.g., to a device that is or will operate in a LPM 310 with a LPM synthesizer enabled) if a reciprocal mixing condition is satisfied by a first quantity of time intervals, such as slots, within a time window or second quantity of time intervals. If the device anticipates a threshold amount of SNR degradation (e.g., 1 dB of SNR degradation) after enabling the LPM synthesizer, then an entering condition (e.g., ENTER CONDITION) is met. If an entering condition is met, then the reciprocal mixing metric (e.g., Rcp mix) is set to 1 (e.g., Rcp_mix=l). The reciprocal mixing impact is lifted (e.g., Rcp_mix=0) if all slots in the moving average window satisfy an exit condition. If less than IdB of SNR degradation is anticipated after enabling the LPM synthesizer, then the exit condition (e.g., EXIT CONDITION) is met.

[0124] In some examples, the LPM synthesizer may be disabled when a signal level is less than a reference (e.g. reference sensing (REFSENS) plus 14 dB). The detector for the reference sensing may be implemented via receive automatic gain control (RxAGC). Received signal strength indicator (RS SI) may be available to the RxAGC. Jammers may be observable in the RxAGC. In some examples, one or more parameters may be defined for detecting the enter or exit conditions (e.g., via over the air signaling or predefined). An ACI threshold may be defined as (ACI TH LOW), an RSSI ACI threshold may be defined as RSSI ACI TH, and an in band RSSI may be defined as inband RSSI. For example, the device may determine the reciprocal mixing impact detector according to X (e.g., a quantity of time intervals, such as slots, in a window of time) , Y (e.g., a quantity of slots within the window), Nl, N2, a threshold hysteresis (e.g., TH HYST), an RSSI offset, and an RSSI hysteresis.

[0125] The exit condition may be defined as EXIT CONDITION: ACI < ACI TH LOW - TH HYST, or ACI < inband RSSI - RSSI ACI TH - TH HYST)) and (total RSSI > REFSENS+RSSI OFFSET+RSSI HYST). The enter condition may be defined as ENTER CONDITION: ((ACI > ACI TH LOW) and (ACI > inband RSSI - RSSI ACI TH)) or (total RSSI < REFSENS +RSSI OFFSET). Thus, if any active receiver satisfied the enter condition for the Y time intervals within the N2-slot sliding window, then the device may set the reciprocal mixing metric (e.g., Rcp mix) to 1 (e.g., Rcp_mix=l). If all active receivers satisfy theexit condition for X slots in the Nl-slot sliding window , then the device may set the reciprocal mixing metric (e.g., Rcp mix) to 0 (e.g., Rcp_mix=0).

[0126] The device may set a transmission reciprocal mixing impact metric using the controller 505-b (e.g., or may input the transmission reciprocal mixing impact metric into a controller 505-b). Reciprocal mixing due to transmission signals may occur when the LPM synthesizer is enabled in FDD bands. For example, when the LPM synthesizer is enabled, the reciprocal mixing may occur due to transmission signals being looped back into the receive chain, which may leak into a downlink channel and cause SNR degradation. Even if there is a rejection by a duplexer, higher transmit power (e.g., 21 dBm to about 26 dBm) may cause high SNR impacts.

[0127] Transmission-based reciprocal mixing may be detected if more than 1 dB of SNR loss is expected (e.g., when using the LPM synthesizer). In a low transmission power scenario, the SNR degradation due to the transmissions may be negligible (e.g., below a threshold). In high transmission power scenarios, the SNR degradation may also be negligible if a difference between a transmit power and an RSRP is below a threshold. Thus (e.g., and similar to receiver reciprocal mixing detection), the device may monitor one or more metrics or parameters (e.g., transmit power and reference signal receive power (RSRP)) with a time hysteresis for transmission reciprocal mixing detection. Such monitoring may be performed according to one or more parameter values. For instance, a transmission power hysteresis may be defined asTX RM HYST, a first window length may be defined as WIN LEN l, a second window length may be defined as WIN_LEN_2, an threshold quantity of slots may be defined as RM EVENT TH, and a transmit power threshold may be defined as TX TH LOW), and an RSRP threshold may be defined as RSRP TX TH.

[0128] During a window of length WIN LEN l, if each observed transmit power (P_Tx) is less than a threshold (e.g., if PTx< TX_TH_L0W - TX_RM_HYST) or the difference between RSRP and the transmit power is greater than the second threshold (e.g., RSRP — Ptx) > RSRPTXTH+ TX_RM_HYST'), then the device may set the transmission based reciprocal mixing metric to 0 (e.g., TX_Rcp_mix=0), indicating that no SNR degradation (e.g., or negligible SNR degradation) is detected for switching to a LPM (e.g., and enabling the LPM synthesizer). During a window length WIN_LEN_2,if a transmit power is greater than a threshold (e.g., if an observed RM EVENT TH quantity of slots satisfy a threshold PTx> TX_TH_LOW and RSRP — PTx) < RSRP_TX_TH, then the device may set the transmission based reciprocal mixing metric to 1 (e.g., TX_Rcp_mix=l), indicating that SNR degradation (e.g., non-negligible SNR degradation) is detected for switching to a LPM (e.g., and enabling the LPM synthesizer) or remaining in the LPM (e.g., with the LPM synthesizer enabled).

[0129] In some examples, the device may detect SNR impact caused by other sources (e.g., other jammers). For example, SNR degradation may be caused by interference sources such as an OOB jammer or an IBB2 jammer. Power from such jammers may leak into the downlink channel. The device will monitor for and detect reciprocal mixing due to jammers when the LPM synthesizer is enabled. In some examples, interference sources (e.g., jammers) around frequencies in the reduced ADC sampling rate may also cause SNR degradation.

[0130] Jammer detection may detect SNR loss caused by such jammers. For example, when operating in a HPM (e.g., the MM 320 using the HPM synthesizer), the device may compute a first SNR (e.g., an MM SNR) as a reference SNR. Assuming the projected LPM SNR from reference SNR satisfies a threshold, then (e.g., upon receiving a vote to switch to the LPM and enable the LPM synthesizer), the controller may set the jammer detection metric (e.g., Jam impact) to indicate a lack of detected SNR degradation (e.g., Jam_Impact=0), and switch to the LPM.

[0131] Upon entering a LPM (e.g., the LPM enabling the LPM synthesizer), the device may compute a LPM SNR, and compare the LPM SNR with the projected LPM SNR from the reference SNR. If an SNR drop is detected (e.g., if the LPM SNR is less than the projected LPM SNR from the reference SNR, or if a difference between the projected LPM SNR from the reference SNR and the LPM SNR exceeds a threshold), then the device may switch from the HPM (e.g., MM 320), disable the LPM synthesizer, and enable the HPM synthesizer (e.g., based on setting the jammer impact metric to indicated detected jammer impact (e.g., Jam_Impact=l). In some examples, the device may switch back to the MM if a timer expires. For example, after a time duration expires, the controller may switch from the LPM to the MM (e.g., may disable the LPM synthesizer and enable the HPM synthesizer) to update the reference SNR.Upon updating the reference SNR (e.g., and in some examples, if the parameter values, the performance metrics, or both, still satisfy respective thresholds), the controller may switch back to the LPM and enable the LPM synthesizer. The device may continue to measure a LPM SNR, and compare it with the updated reference SNR.

[0132] If a jammer is detected (e.g., if the difference between the projected LPMSNR from the reference SNR and the LPM SNR exceeds the threshold), in some examples, the controller may maintain the device in a HPM (e.g., the MM 320) to avoid rapid or constant changes between the LPM and the MM. In some examples, the device may detect a high Doppler case, and may set the jammer impact metric to indicate detected jammer impact (e.g., Jam_Impact=l).

[0133] In some examples, the device may detect PDCCH SNR conditions, and may set a PDCCH decodable metric based thereon. For example, for each PDCCH code rate, a receiver SNR may be greater than a threshold to ensure (e.g., increase the likelihood of) a PDCCH BLER that satisfies a threshold (e.g., is less than 1%). Due to high integrated phase noise (IPN) of the LPM synthesizer, a threshold (e.g., maximum) achievable SNR of a LPM synthesizer may be lower than a threshold (e.g., maximum) achievable SNR of a HPM synthesizer.

[0134] The device may check (e.g., measure) one or more PDCCH SNR conditions periodically. When the HPM synthesizer is enabled (e.g., in the MM 320 or the LPM 315), the device may set the PDCCH decodability metric to indicate that PDCCH signaling is decodable (e.g., even if the LPM synthesizer is enabled) if one or more conditions are satisfied. For example, the device may set the PDCCH decodability metric to indicate that the PDCCH signaling is decodable (e.g., PDCCH_decodable=l) if a projected LPM synthesizer SNR (e.g., based on the HPM synthesizer SNR) is higher than an SNR threshold and an SNR hysteresis. In some examples, the device may set the PDCCH decodability metric to indicate that the PDCCH signaling is decodable (e.g., PDCCH_decodable=l) if the HPM synthesizer SNR is less than a SNR threshold which shows the same SNR value when LPM synthesizer is enabled. If a power mode vote indicates a switch to the LPM and enabling of the LPM synthesizer, and all of the performance metrics confirm the power mode vote (e.g., including PDCCH_decodable=l), then the controller may switch from the MM (e.g., or the LPM using the HPM synthesizer), to the LPM (e.g., with the LPM synthesizer enabled).

[0135] When operating in the LPM with the LPM synthesizer available, the device may set the PDCCH_decodable=l if one or more conditions are satisfied. For example, the device may set PDCCH_decodable=l if the LPM synthesizer SNR based on received synchronization signal block (SSB) (e.g., a LPM synthesizer SSB SNR) is higher than higher than an SNR threshold, or if the LPM synthesizer SNR is less than a threshold. If the PDCCH_decodable=0 when the device is operating in the MM, then the controller may refrain from switching to the LPM and enabling the LPM synthesizer. If the PDCCH_decodable=0 when the device is operating in the LPM with the LPM synthesizer enabled, then the controller may switch from the LPM with the LPM synthesizer enabled to a HPM (e.g., the MM 320) with the HPM synthesizer enabled (e.g., and the LPM synthesizer disabled). In some examples, the device may stay in the MM for a time period (e.g., 1 ms) if switching to the MM is due to PDCCH_decodable=0.

[0136] FIG. 6 shows an example of a process flow 600 that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure. The process flow 600 may implement, or be implemented by, aspects of the wireless communications system 100, the wireless communications system 200, the power mode switching scheme 300, and the flow diagram 400, or the performance metric determination scheme 500. For example, the process flow 600 may include a UE 115-b and a network entity 105-b, which may be examples of corresponding devices described with reference to FIGs. 1-5.

[0137] At 610, the UE 115-b may receive (e.g., from the network entity 105-b) downlink traffic. In some examples, the UE 115-b may receive a grant for downlink traffic. The grant may indicate an MCS for the downlink traffic. The UE may measure (e.g., or receive an indication of) a BLER corresponding to the traffic, may measure an SNR corresponding to the traffic, or the like.

[0138] At 615, the UE 115-b may generate a proposal to switch from one power mode to another power mode (e.g., a power mode vote). For example, the UE 115-b may generate a proposal to switch from a first HPM (e.g., the MM 320) to a LPM (e.g., the LPM 310) based at least in part on a first set of parameters corresponding to the downlink traffic satisfying respective thresholds.

[0139] In some examples, the UE 115-b may periodically detect the first set of parameters during a moving time window, and may determine that the first set of parameters satisfy the respective thresholds based at least in part on the detecting. For instance, as described in greater detail with reference to FIGs. 3-4, the UE 115-b may receive control signaling (e.g., a downlink grant) indicating an MCS for the downlink traffic. One of the parameters may be the MCS, and the UE 115-b may verify that the MCS (e.g., for a given band, BW, or group, etc., and a given RI) satisfies an MCS threshold. In some examples, measuring the first set of parameters may include measuring a BLER, measuring an SNR, or referring to the current MCS, or a combination thereof. For instance, if the grant has been received with in a window then the UE 115-b may generate the proposal based at least in part on the MCS satisfying an MCS threshold, and based on the BLER satisfying a threshold. If a grant has not been received within the window, then the UE 115-b may measure an SNR, and generate the power mode proposal if the SNR satisfies a threshold. If no grant has been received during an extended window, then the UE 115-b may generate a proposal to enter the LPM and enable the LPM synthesizer.

[0140] At 620, the UE 115-b may measure a set of performance metrics based at least in part on generating the proposal (e.g., to confirm or verify the proposed switch in power mode). The UE 115-b may only enter the LPM (e.g., switch from the MM and enable the LPM synthesizer) if each of the set of performance metrics confirms the proposal. At 625, the UE 115-b may enter the LPM (e.g., the LPM 310), and enable a LPM synthesizer based at least in part on each of the performance metrics of the set of performance metrics satisfying respective thresholds and according to the proposal.

[0141] For example, measuring the set of performance metrics may include measuring an SNR degradation within multiple time intervals of a time window (e.g., 60 slots), and the set of performance metrics may include a reception reciprocal mixing impact metric (e.g., the Rcp mix metric). The UE 115-b may set the value of the reception reciprocal mixing impact metric to indicate an absence of reciprocal mixing impact based at least in part on the SNR degradation failing to satisfy a threshold SNR degradation threshold during a threshold quantity of time intervals of the multiple of time intervals as described in greater detail with reference to FIG. 5. In such examples, the UE 115-b may set the Rcp mix metric to Rcp_mix=0. If any of the performancemetrics fails to satisfy a respective threshold while operating in the LPM using the LPM synthesizer, the UE 115-b may switch back to the first HPM (e.g., the MM). For example, the UE 115-b may measure the SNR degradation with the time window , and may set the value of the reception reciprocal mixing impact metric to indicate a reciprocal mixing impact (e.g., Rcp_mix=l) based on the measurements. In such examples, the UE 115-b may switch from the LPM, disable the LPM synthesizer, enable the HPM synthesizer, and enter the HPM (e.g., the MM).

[0142] If, while operating in the HPM using the HPM synthesizer, the SNR degradation is detected during the running window (e.g., during one or more slots of the 60 slots), the UE 115-b may set Rcp_mix=l, and may refrain from switching from the MM to the LPM and enabling the LPM synthesizer (e.g., despite the proposal at 615 indicating a switch).

[0143] In some examples, measuring the set of performance metrics may include monitoring a transmission power utilized in the HPM during a transmission window, a RSRP indicated or detected during the transmission window, or both. The set of performance metrics may include a transmission reciprocal mixing impact metric (e.g., the Tx Rcp mix metric). The UE 115-b may set the value of the Tx Rcp mix to indicate an absence of a reciprocal mixing impact corresponding to an SNR degradation (e.g., Tx_Rcp_mix=0) based at least in part on the monitoring, as described in greater detail with reference to FIG. 5. The UE 115-b may enable the LPM synthesizer and switch to the LPM based at least in part on setting the Tx_Rcp_mix=0 (e.g., and the other performance metrics). While operating in the LPM using the LPM synthesizer, the UE 115-b may monitoring the transmission power utilized in the LPM during a second transmission window, the RSRP indicated during the second transmission window, or both. The UE may set the value of the performance metric to indicate a reciprocal mixing impact corresponding to an SNR degradation (e.g., Tx_Rcp_mix=l) based at least in part on the monitoring during the second transmission window. The UE 115-b may switch to the first HPM, disable the LPM synthesizer, and enable the HPM synthesizer based at least in part on setting Tx_Rcp_mix=l.

[0144] If, while operating in the HPM using the HPM synthesizer, the SNR degradation is detected during a transmission window, the UE 115-b may setTx_Rcp_mix=l, and may refrain from switching from the MM to the LPM and enabling the LPM synthesizer (e.g., despite the proposal at 615 indicating a switch).

[0145] In some examples, measuring the set of performance metrics may include computing a fist NR corresponding to the HPM, the set of performance metrics including a jammer impact metric (e.g., the Jam impact metric). The UE 115-b may set the metric value to indicate an absence of jammer impact on the first SNR (e.g., Jam_Impact=0) based on the measuring of the first SNR. The UE 115-b may switch to the LPM and enable the LPM synthesizer based at least in part on setting the Jam_Impact=0. In the LPM using the LPM synthesizer, the UE 115-b may measure a second SNR corresponding to the LPM (e.g., a LPM SNR). The UE 115-b may compare the second SNR to a projected LPM SNR based on the first SNR (e.g., the reference SNR). The UE 115-b may set the value of Jam impact to indicate a jammer impact on the second SNR based on a difference between the reference SNR and the projected LPM SNR satisfying threshold (e.g., may set Jam_Impact=l). Based on setting Jam_Impact=l, the UE 115-b may switch to the first HPM, disable the LPM synthesizer, and enable the HPM synthesizer.

[0146] In some examples, the UE 115-b may initiate a timer upon entering the LPM and enabling the LPM synthesizer. In such examples, the UE 115-b may switch to the first HPM, disable the LPM synthesizer, and enable the HPM synthesizer upon expiration of the timer, and may update the first SNR (e.g., the reference SNR) in the first HPM based on the switching and the expiration of the timer. The UE 115-b may then switch back to the LPM and enable the LPM synthesizer, and may measure jammer impact by comparing and updated projected LPM SNR with a current LPM SNR.

[0147] If, while operating in the HPM using the HPM synthesizerjammer impact is is detected, the UE 115-b may set Jam-Impact=l, and may refrain from switching from the MM to the LPM and enabling the LPM synthesizer (e.g., despite the proposal at 615 indicating a switch).

[0148] In some examples, measuring the performance metrics may include periodically measuring a first SNR for a control channel code rate (e.g., for each PDCCH code rate), and the performance metric may include a control channel SNR metric (e.g., PDCCH decodable metric). The UE 115-b may set a value of the controlchannel SNR condition metric (e.g., PDCCH decodable) to indicate that the control channel is decodable (e.g., PDCCH_decodable=l) based at least in part on the first SNR satisfying a first threshold (e.g., a projected LPM synthesizer SNR based on or projected from the HPM synthesizer SNR is higher than an SNR threshold and an SNR hysteresis), or based on a second SNR threshold (e.g., the SNR satisfies LPM310 SNR HIGH), or both. Based on setting PDCCH_decodable=l, the UE 115-b may switch from the MM (e.g., or another HPM or LPM) to the LPM and may enable the LPM synthesizer. In the LPM using the LPM synthesizer, the UE 15-b may receive one or more reference signals at 605 (e.g., one or more SSBs). The UE 115-b may generate an SNR estimate based on the SSBs. The UE 115-b may maintain the value of the control channel SNR condition metric (e.g., PDCCH_decodable=l) to indicate that the PDCCH is decodable based on the SNR satisfying the first threshold, or may set the value of the PDCCH_decodable=0 to indicate that the PDCCH is not decodable based on the second SNR failing to satisfy the first threshold (e.g., the SSB SNR may satisfy a first threshold), or based at least in part on the first SNR failing to satisfy a second threshold (e.g., the SNR does not satisfy LPM 310 SNR HIGH), or both.

[0149] In some examples, the UE 115-b may generate the power mode proposal (e.g., the power mode vote) to switch to the LPM and enable the LPM synthesizer at 615. If all of the set of performance metrics do not satisfy the respective thresholds, then the UE 115-b may refrain from making the proposed switch. If each of the performance metrics satisfy the respective thresholds, then the UE 115-b may make the proposed switch, and may enable the LPM synthesizer. If, while operating in the LPM, any of the performance metrics fail to satisfy the respective threshold, then the UE 115-b may switch back to a HPM or another LPM (e.g., may enable the HPM synthesizer).

[0150] In some examples, the UE 115-b may switch, via a controller, between the first HPM (e.g., the MM), a second HPM (e.g. the LPM 315), and the LPM (e.g., the LPM 310). In such examples, the UE 115-b ,may disable the second HPM based at least in part on the ADC sampling rate reduction being unavailable according to one or more current conditions (e.g. and may switch between the MM using the HPM synthesizer and the LPM using the LPM synthesizer without reference to the other HPM).

[0151] FIG. 7 shows a block diagram 700 of a device 705 that supports opportunistic use of low power mode synthesizer and jammer detection in accordancewith one or more aspects of the present disclosure. The device 705 may be an example of aspects of a UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communications manager 720. The device 705, or one or more components of the device 705 (e.g., the receiver 710, the transmitter 715, the communications manager 720), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0152] The receiver 710 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to opportunistic use of low power mode synthesizer and jammer detection). Information may be passed on to other components of the device 705. The receiver 710 may utilize a single antenna or a set of multiple antennas.

[0153] The transmitter 715 may provide a means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to opportunistic use of low power mode synthesizer and jammer detection). In some examples, the transmitter 715 may be co-located with a receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a set of multiple antennas.

[0154] The communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be examples of means for performing various aspects of opportunistic use of low power mode synthesizer and jammer detection as described herein. For example, the communications manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

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

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

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

[0158] The communications manager 720 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 720 is capable of, configured to, or operable to support a means for receiving downlink traffic while operating in a first high power mode using a high power mode synthesizer. The communications manager 720 is capable of, configured to, or operableto support a means for generating a proposal to switch from the first high power mode to a low power mode based on each of a first set of parameters corresponding to the downlink traffic satisfying respective thresholds. The communications manager 720 is capable of, configured to, or operable to support a means for measuring a set of performance metrics based on generating the proposal. The communications manager 720 is capable of, configured to, or operable to support a means for entering the low power mode and enabling a low power mode synthesizer based on the proposal and based on each performance metric of the set of performance metrics satisfying respective thresholds.

[0159] By including or configuring the communications manager 720 in accordance with examples as described herein, the device 705 (e.g., at least one processor controlling or otherwise coupled with the receiver 710, the transmitter 715, the communications manager 720, or a combination thereof) may support techniques for power mode switching resulting in improved performance, reduced power consumption, and improved user experience.

[0160] FIG. 8 shows a block diagram 800 of a device 805 that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure. The device 805 may be an example of aspects of a device 705 or a UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. The device 805, or one of more components of the device 805 (e.g., the receiver 810, the transmitter 815, the communications manager 820), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0161] The receiver 810 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to opportunistic use of low power mode synthesizer and jammer detection). Information may be passed on to other components of the device 805. The receiver 810 may utilize a single antenna or a set of multiple antennas.

[0162] The transmitter 815 may provide a means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to opportunistic use of low power mode synthesizer and jammer detection). In some examples, the transmitter 815 may be co-located with a receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a set of multiple antennas.

[0163] The device 805, or various components thereof, may be an example of means for performing various aspects of opportunistic use of low power mode synthesizer and jammer detection as described herein. For example, the communications manager 820 may include an HPM manager 825, a power mode switching manager 830, a performance metric manager 835, an LPM manager 840, or any combination thereof. The communications manager 820 may be an example of aspects of a communications manager 720 as described herein. In some examples, the communications manager 820, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 810, the transmitter 815, or both. For example, the communications manager 820 may receive information from the receiver 810, send information to the transmitter 815, or be integrated in combination with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0164] The communications manager 820 may support wireless communications in accordance with examples as disclosed herein. The HPM manager 825 is capable of, configured to, or operable to support a means for receiving downlink traffic while operating in a first high power mode using a high power mode synthesizer. The power mode switching manager 830 is capable of, configured to, or operable to support a means for generating a proposal to switch from the first high power mode to a low power mode based on each of a first set of parameters corresponding to the downlink traffic satisfying respective thresholds. The performance metric manager 835 is capable of, configured to, or operable to support a means for measuring a set of performance metrics based on generating the proposal. The LPM manager 840 is capable of,configured to, or operable to support a means for entering the low power mode and enabling a low power mode synthesizer based on the proposal and based on each performance metric of the set of performance metrics satisfying respective thresholds.

[0165] FIG. 9 shows a block diagram 900 of a communications manager 920 that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure. The communications manager 920 may be an example of aspects of a communications manager 720, a communications manager 820, or both, as described herein. The communications manager 920, or various components thereof, may be an example of means for performing various aspects of opportunistic use of low power mode synthesizer and jammer detection as described herein. For example, the communications manager 920 may include an HPM manager 925, a power mode switching manager 930, a performance metric manager 935, an LPM manager 940, a parameter measurement manager 945, a power mode disabling manager 950, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0166] The communications manager 920 may support wireless communications in accordance with examples as disclosed herein. The HPM manager 925 is capable of, configured to, or operable to support a means for receiving downlink traffic while operating in a first high power mode using a high power mode synthesizer. The power mode switching manager 930 is capable of, configured to, or operable to support a means for generating a proposal to switch from the first high power mode to a low power mode based on each of a first set of parameters corresponding to the downlink traffic satisfying respective thresholds. The performance metric manager 935 is capable of, configured to, or operable to support a means for measuring a set of performance metrics based on generating the proposal. The LPM manager 940 is capable of, configured to, or operable to support a means for entering the low power mode and enabling a low power mode synthesizer based on the proposal and based on each performance metric of the set of performance metrics satisfying respective thresholds.

[0167] In some examples, the parameter measurement manager 945 is capable of, configured to, or operable to support a means for periodically detecting the first set ofparameters during a moving time window. In some examples, the parameter measurement manager 945 is capable of, configured to, or operable to support a means for determining that the first set of parameters satisfy the respective thresholds based on the detecting, where generating the proposal is based on the determining.

[0168] In some examples, the parameter measurement manager 945 is capable of, configured to, or operable to support a means for receiving control signaling indicating a modulation and coding scheme for the downlink traffic, where one of the first set of parameters includes the modulation and coding scheme.

[0169] In some examples, to support detecting the first set of parameters, the parameter measurement manager 945 is capable of, configured to, or operable to support a means for measuring a block error rate (BLER), measuring a signal to noise ratio (SNR), or referring to a current modulation and coding scheme.

[0170] In some examples, the HPM manager 925 is capable of, configured to, or operable to support a means for switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based on any of the set of performance metrics failing to satisfy a respective threshold.

[0171] In some examples, the power mode disabling manager 950 is capable of, configured to, or operable to support a means for switching, via a controller, between the first high power mode, a second high power mode, and the low power mode. In some examples, the power mode disabling manager 950 is capable of, configured to, or operable to support a means for disabling the second high power mode based on analog- to-digital-converter sampling rate reduction being unavailable according to one or more current conditions, where enabling a low power mode synthesizer and entering the low power mode is based on the disabling.

[0172] In some examples, to support measuring the set of performance metrics, the performance metric manager 935 is capable of, configured to, or operable to support a means for measuring a signal to noise ratio (SNR) degradation within a set of multiple time intervals of a time window, the set of performance metrics including a reception reciprocal mixing impact metric. In some examples, to support measuring the set of performance metrics, the performance metric manager 935 is capable of, configured to, or operable to support a means for setting a value of the reception reciprocal mixingimpact metric to indicate an absence of reciprocal mixing impact based on the SNR degradation failing to satisfy a threshold SNR degradation threshold during a threshold quantity of time intervals of the set of multiple time intervals, where enabling the low power mode synthesizer and entering the low power mode is based on the value indicating the absence of the reciprocal mixing impact.

[0173] In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for measuring the SNR degradation within a second set of multiple time intervals of a second time window while operating in the low power mode. In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for setting the value of the reception reciprocal mixing impact metric to indicate a reciprocal mixing impact based on the SNR degradation satisfying the threshold SNR degradation threshold in during the threshold quantity of time intervals of the second set of multiple time intervals. In some examples, the power mode switching manager 930 is capable of, configured to, or operable to support a means for switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based on setting the value to indicate the reciprocal mixing impact.

[0174] In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for measuring the SNR degradation within a third set of multiple time intervals of a third time window while operating in the high power mode. In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for setting the value of the reception reciprocal mixing impact metric to indicate a reciprocal mixing impact based on the SNR degradation satisfying the threshold SNR degradation threshold in during the threshold quantity of time intervals of the third set of multiple time intervals. In some examples, the power mode switching manager 930 is capable of, configured to, or operable to support a means for refraining from switching to the low power mode based on setting the value to indicate the reciprocal mixing impact.

[0175] In some examples, to support measuring the set of performance metrics, the performance metric manager 935 is capable of, configured to, or operable to support a means for monitoring a transmission power utilized in the high power mode during a transmission window, a reference signal receive power indicated during thetransmission window, or both, where the set of performance metrics includes a transmission reciprocal mixing impact metric. In some examples, to support measuring the set of performance metrics, the performance metric manager 935 is capable of, configured to, or operable to support a means for setting a value of the transmission reciprocal mixing impact metric to indicate an absence of a reciprocal mixing impact corresponding to an SNR degradation based on the monitoring, where enabling the low power mode synthesizer and entering the low power mode is based on the value indicating the absence of the reciprocal mixing impact.

[0176] In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for monitoring the transmission power utilized in the low power mode during a second transmission window, the reference signal receive power indicated during the second transmission window, or both. In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for setting a value of the transmission reciprocal mixing impact metric to indicate a reciprocal mixing impact corresponding to an SNR degradation based on the monitoring during the second transmission window. In some examples, the power mode switching manager 930 is capable of, configured to, or operable to support a means for switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based on setting the value to indicate the reciprocal mixing impact.

[0177] In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for monitoring the transmission power utilized in the high power mode during a third transmission window, the reference signal receive power indicated during the third transmission window, or both. In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for setting a value of the transmission reciprocal mixing impact metric to indicate a reciprocal mixing impact corresponding to an SNR degradation based on the monitoring during the third transmission window. In some examples, the power mode switching manager 930 is capable of, configured to, or operable to support a means for refraining from switching to the low power mode based on setting the value to indicate the reciprocal mixing impact.

[0178] In some examples, to support measuring the set of performance metrics, the performance metric manager 935 is capable of, configured to, or operable to support a means for computing a first signal to noise ratio (SNR) corresponding to the first high power mode, where the set of performance metrics includes a jammer impact metric. In some examples, to support measuring the set of performance metrics, the performance metric manager 935 is capable of, configured to, or operable to support a means for setting a value of the jammer impact metric to indicate an absence of a jammer impact on the first SNR based on the first SNR, where enabling the low power mode synthesizer and entering the low power mode is based on the value indicating the absence of the jammer impact.

[0179] In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for measuring a second SNR corresponding to the low power mode. In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for comparing the second SNR to a projected low power mode SNR based on the first SNR. In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for setting a value of the jammer impact metric to indicate a jammer impact on the second SNR based on a difference between the second SNR and the projected low power mode SNR satisfying a threshold. In some examples, the power mode switching manager 930 is capable of, configured to, or operable to support a means for switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based on setting the value to indicate the jammer impact on the second SNR.

[0180] In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for initiating a timer upon entering the low power mode. In some examples, the power mode switching manager 930 is capable of, configured to, or operable to support a means for switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer upon expiration of the timer. In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for updating the first SNR corresponding to the first high power mode based on the switching upon expiration of the timer. In some examples, the power mode switching manager 930 iscapable of, configured to, or operable to support a means for switching to the low power mode and enabling the low power mode synthesizer based on updating the first SNR.

[0181] In some examples, to support measuring the set of performance metrics, the performance metric manager 935 is capable of, configured to, or operable to support a means for periodically measuring a first signal to noise ratio (SNR) for a control channel code rate, where the set of performance metrics includes a control channel SNR condition metric. In some examples, to support measuring the set of performance metrics, the performance metric manager 935 is capable of, configured to, or operable to support a means for setting a value of the control channel SNR condition metric to indicate that a control channel is decodable based on a projected SNR for the low power mode that is based on the first SNR satisfying a first threshold, or based on the first SNR satisfying a second threshold, or both, where enabling the low power mode synthesizer and entering the low power mode is based on the value indicating that the control channel is decodable.

[0182] In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for receiving one or more reference signals in the low power mode, the one or more reference signals corresponding to an SNR estimate. In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for maintaining the value of the control channel SNR condition metric to indicate that the control channel is decodable based on a second SNR satisfying the first threshold. In some examples, the power mode switching manager 930 is capable of, configured to, or operable to support a means for continuing to operate in the low power mode using the low power mode synthesizer.

[0183] In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for receiving one or more reference signals in the low power mode, the one or more reference signals corresponding to an SNR estimate. In some examples, the performance metric manager 935 is capable of, configured to, or operable to support a means for setting the value of the control channel SNR condition metric to indicate that the control channel is not decodable based on a second SNR failing to satisfy the first threshold. In some examples, the power mode switching manager 930 is capable of, configured to, or operable to support a means for switching to the first high power mode, disabling the low power mode synthesizer, andenabling the high power mode synthesizer based on setting the value to indicate that the control channel is not decodable.

[0184] FIG. 10 shows a diagram of a system 1000 including a device 1005 that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of or include components of a device 705, a device 805, or a UE 115 as described herein. The device 1005 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof). The device 1005 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1020, an input / output (I / O) controller, such as an I / O controller 1010, a transceiver 1015, one or more antennas 1025, at least one memory 1030, code 1035, and at least one processor 1040. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1045).

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

[0186] In some cases, the device 1005 may include a single antenna. However, in some other cases, the device 1005 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1015 may communicate bi-directionally via the one or more antennas 1025 using wired or wireless links as described herein. For example, the transceiver 1015 may represent a wireless transceiver and may communicate bi-directionally withanother wireless transceiver. The transceiver 1015 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1025 for transmission, and to demodulate packets received from the one or more antennas 1025. The transceiver 1015, or the transceiver 1015 and one or more antennas 1025, may be an example of a transmitter 715, a transmitter 815, a receiver 710, a receiver 810, or any combination thereof or component thereof, as described herein.

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

[0188] The at least one processor 1040 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 1040. The at least one processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 1030) to cause the device 1005 to perform various functions (e.g., functions or tasks supporting opportunistic use of low power mode synthesizer and jammer detection). For example, the device 1005 or a component of the device 1005 mayinclude at least one processor 1040 and at least one memory 1030 coupled with or to the at least one processor 1040, the at least one processor 1040 and the at least one memory 1030 configured to perform various functions described herein.

[0189] In some examples, the at least one processor 1040 may include multiple processors and the at least one memory 1030 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 1040 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1040) and memory circuitry (which may include the at least one memory 1030)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1040 or a processing system including the at least one processor 1040 may be configured to, configurable to, or operable to cause the device 1005 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 1035 (e.g., processor-executable code) stored in the at least one memory 1030 or otherwise, to perform one or more of the functions described herein.

[0190] The communications manager 1020 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1020 is capable of, configured to, or operable to support a means for receiving downlink traffic while operating in a first high power mode using a high power mode synthesizer. The communications manager 1020 is capable of, configured to, or operable to support a means for generating a proposal to switch from the first high power mode to a low power mode based on each of a first set of parameters corresponding to the downlink traffic satisfying respective thresholds. The communications manager 1020 is capable of, configured to, or operable to support a means for measuring a set of performance metrics based on generating the proposal. The communications manager 1020 is capable of, configured to, or operable to supporta means for entering the low power mode and enabling a low power mode synthesizer based on the proposal and based on each performance metric of the set of performance metrics satisfying respective thresholds.

[0191] By including or configuring the communications manager 1020 in accordance with examples as described herein, the device 1005 may support techniques for power mode switching resulting in improved performance, improved throughput, increased reliability of wireless communications, increased power savings, more efficient use of available system resources, improved power savings, extended battery life, and improved user experience.

[0192] In some examples, the communications manager 1020 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1015, the one or more antennas 1025, or any combination thereof. Although the communications manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1020 may be supported by or performed by the at least one processor 1040, the at least one memory 1030, the code 1035, or any combination thereof. For example, the code 1035 may include instructions executable by the at least one processor 1040 to cause the device 1005 to perform various aspects of opportunistic use of low power mode synthesizer and jammer detection as described herein, or the at least one processor 1040 and the at least one memory 1030 may be otherwise configured to, individually or collectively, perform or support such operations.

[0193] FIG. 11 shows a flowchart illustrating a method 1100 that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure. The operations of the method 1100 may be implemented by a UE or its components as described herein. For example, the operations of the method 1100 may be performed by a UE 115 as described with reference to FIGs. 1 through 10. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0194] At 1105, the method may include receiving downlink traffic while operating in a first high power mode using a high power mode synthesizer. The operations of 1105 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1105 may be performed by an HPM manager 925 as described with reference to FIG. 9.

[0195] At 1110, the method may include generating a proposal to switch from the first high power mode to a low power mode based on each of a first set of parameters corresponding to the downlink traffic satisfying respective thresholds. The operations of 1110 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1110 may be performed by a power mode switching manager 930 as described with reference to FIG. 9.

[0196] At 1115, the method may include measuring a set of performance metrics based on generating the proposal. The operations of 1115 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1115 may be performed by a performance metric manager 935 as described with reference to FIG. 9.

[0197] At 1120, the method may include entering the low power mode and enabling a low power mode synthesizer based on the proposal and based on each performance metric of the set of performance metrics satisfying respective thresholds. The operations of 1120 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1120 may be performed by an LPM manager 940 as described with reference to FIG. 9.

[0198] FIG. 12 shows a flowchart illustrating a method 1200 that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure. The operations of the method 1200 may be implemented by a UE or its components as described herein. For example, the operations of the method 1200 may be performed by a UE 115 as described with reference to FIGs. 1 through 10. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0199] At 1205, the method may include receiving downlink traffic while operating in a first high power mode using a high power mode synthesizer. The operations of 1205 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed by an HPM manager 925 as described with reference to FIG. 9.

[0200] At 1210, the method may include generating a proposal to switch from the first high power mode to a low power mode based on each of a first set of parameters corresponding to the downlink traffic satisfying respective thresholds. The operations of 1210 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed by a power mode switching manager 930 as described with reference to FIG. 9.

[0201] At 1215, the method may include measuring a set of performance metrics based on generating the proposal. The operations of 1215 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed by a performance metric manager 935 as described with reference to FIG. 9.

[0202] At 1220, the method may include entering the low power mode and enabling a low power mode synthesizer based on the proposal and based on each performance metric of the set of performance metrics satisfying respective thresholds. The operations of 1220 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1220 may be performed by an LPM manager 940 as described with reference to FIG. 9.

[0203] At 1225, the method may include switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based on any of the set of performance metrics failing to satisfy a respective threshold. The operations of 1225 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1225 may be performed by an HPM manager 925 as described with reference to FIG. 9.

[0204] FIG. 13 shows a flowchart illustrating a method 1300 that supports opportunistic use of low power mode synthesizer and jammer detection in accordance with one or more aspects of the present disclosure. The operations of the method 1300may be implemented by a UE or its components as described herein. For example, the operations of the method 1300 may be performed by a UE 115 as described with reference to FIGs. 1 through 10. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0205] At 1305, the method may include receiving downlink traffic while operating in a first high power mode using a high power mode synthesizer. The operations of 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by an HPM manager 925 as described with reference to FIG. 9.

[0206] At 1310, the method may include generating a proposal to switch from the first high power mode to a low power mode based on each of a first set of parameters corresponding to the downlink traffic satisfying respective thresholds. The operations of 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by a power mode switching manager 930 as described with reference to FIG. 9.

[0207] At 1315, the method may include measuring a set of performance metrics based on generating the proposal. The operations of 1315 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed by a performance metric manager 935 as described with reference to FIG. 9.

[0208] At 1320, the method may include entering the low power mode and enabling a low power mode synthesizer based on the proposal and based on each performance metric of the set of performance metrics satisfying respective thresholds. The operations of 1320 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed by an LPM manager 940 as described with reference to FIG. 9.

[0209] At 1325, the method may include switching, via a controller, between the first high power mode, a second high power mode, and the low power mode. The operations of 1325 may be performed in accordance with examples as disclosed herein.In some examples, aspects of the operations of 1325 may be performed by a power mode disabling manager 950 as described with reference to FIG. 9.

[0210] At 1330, the method may include disabling the second high power mode based on analog-to-digital-converter sampling rate reduction being unavailable according to one or more current conditions, where enabling a low power mode synthesizer and entering the low power mode is based on the disabling. The operations of 1330 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1330 may be performed by a power mode disabling manager 950 as described with reference to FIG. 9.

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

[0212] Aspect 1 : A method for wireless communications at a UE, comprising: detecting that each of a first set of parameters corresponding to the downlink traffic satisfy respective thresholds; measuring a set of performance metrics based at least in part on each of the first set of parameters satisfying the respective thresholds; and entering a low power mode and enable a low power mode synthesizer based at least in part on each of the first set of parameters satisfying the respective thresholds and based at least in part on each performance metric of the set of performance metrics satisfying respective thresholds.

[0213] Aspect 2: The method of aspect 1, further comprising: periodically detecting the first set of parameters during a moving time window; determining that the first set of parameters satisfy the respective thresholds based at least in part on the detecting; generating a proposal to switch from the first high power mode to a low power mode based at least in part on the determining; and confirming the proposal to switch from the first high power mode to the low power mode based at least in part on each performance metric of the set of performance metrics satisfying respective thresholds.

[0214] Aspect 3 : The method of aspect 2, further comprising: receiving control signaling indicating a modulation and coding scheme for the downlink traffic, wherein one of the first set of parameters comprises the modulation and coding scheme.

[0215] Aspect 4: The method of any of aspects 2 through 3, wherein detecting the first set of parameters further comprises: measuring a block error rate (BLER),measuring a signal to noise ratio (SNR), or referring to a current modulation and coding scheme.

[0216] Aspect 5: The method of any of aspects 1 through 4, further comprising . switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based at least in part on any of the set of performance metrics failing to satisfy a respective threshold

[0217] Aspect 6: The method of any of aspects 1 through 5, further comprising: switching, via a controller, between the first high power mode, a second high power mode, and the low power mode; and disabling the second high power mode based at least in part on analog-to-digital-converter sampling rate reduction being unavailable according to one or more current conditions, wherein enabling a low power mode synthesizer and entering the low power mode is based at least in part on the disabling.

[0218] Aspect 7: The method of any of aspects 1 through 6, wherein measuring the set of performance metrics comprises: measuring a signal to noise ratio (SNR) degradation within a plurality of time intervals of a time window, the set of performance metrics comprising a reception reciprocal mixing impact metric; and setting a value of the reception reciprocal mixing impact metric to indicate an absence of reciprocal mixing impact based at least in part on the SNR degradation failing to satisfy a threshold SNR degradation threshold during a threshold quantity of time intervals of the plurality of time intervals, wherein enabling the low power mode synthesizer and entering the low power mode is based at least in part on the value indicating the absence of the reciprocal mixing impact.

[0219] Aspect 8: The method of aspect 7, further comprising: measuring the SNR degradation within a second plurality of time intervals of a second time window while operating in the low power mode; setting the value of the reception reciprocal mixing impact metric to indicate a reciprocal mixing impact based at least in part on the SNR degradation satisfying the threshold SNR degradation threshold in during the threshold quantity of time intervals of the second plurality of time intervals; and switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based at least in part on setting the value to indicate the reciprocal mixing impact.

[0220] Aspect 9: The method of aspect 8, further comprising: measuring the SNR degradation within a third plurality of time intervals of a third time window while operating in the high power mode; setting the value of the reception reciprocal mixing impact metric to indicate a reciprocal mixing impact based at least in part on the SNR degradation satisfying the threshold SNR degradation threshold in during the threshold quantity of time intervals of the third plurality of time intervals; and refraining from switching to the low power mode based at least in part on setting the value to indicate the reciprocal mixing impact.

[0221] Aspect 10: The method of any of aspects 1 through 9, wherein measuring the set of performance metrics further comprises: monitoring a transmission power utilized in the high power mode during a transmission window, a reference signal receive power indicated during the transmission window, or both, wherein the set of performance metrics comprises a transmission reciprocal mixing impact metric; and setting a value of the transmission reciprocal mixing impact metric to indicate an absence of a reciprocal mixing impact corresponding to an SNR degradation based at least in part on the monitoring, wherein enabling the low power mode synthesizer and entering the low power mode is based at least in part on the value indicating the absence of the reciprocal mixing impact.

[0222] Aspect 11 : The method of aspect 10, further comprising: monitoring the transmission power utilized in the low power mode during a second transmission window, the reference signal receive power indicated during the second transmission window, or both; setting a value of the transmission reciprocal mixing impact metric to indicate a reciprocal mixing impact corresponding to an SNR degradation based at least in part on the monitoring during the second transmission window; and switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based at least in part on setting the value to indicate the reciprocal mixing impact.

[0223] Aspect 12: The method of aspect 11, further comprising: monitoring the transmission power utilized in the high power mode during a third transmission window, the reference signal receive power indicated during the third transmission window, or both; setting a value of the transmission reciprocal mixing impact metric to indicate a reciprocal mixing impact corresponding to an SNR degradation based at leastin part on the monitoring during the third transmission window; and refraining from switching to the low power mode based at least in part on setting the value to indicate the reciprocal mixing impact.

[0224] Aspect 13: The method of any of aspects 1 through 12, wherein measuring the set of performance metrics further comprises: computing a first signal to noise ratio (SNR) corresponding to the first high power mode, wherein the set of performance metrics comprises a jammer impact metric; and setting a value of the jammer impact metric to indicate an absence of a jammer impact on the first SNR based at least in part on the first SNR, wherein enabling the low power mode synthesizer and entering the low power mode is based at least in part on the value indicating the absence of the jammer impact.

[0225] Aspect 14: The method of aspect 13, further comprising: measuring a second SNR corresponding to the low power mode; comparing the second SNR to a projected low power mode SNR based at least in part on the first SNR; setting a value of the jammer impact metric to indicate a jammer impact on the second SNR based at least in part on a difference between the second SNR and the projected low power mode SNR satisfying a threshold; and switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based at least in part on setting the value to indicate the jammer impact on the second SNR.

[0226] Aspect 15: The method of any of aspects 13 through 14, further comprising: initiating a timer upon entering the low power mode; switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer upon expiration of the timer; updating the first SNR corresponding to the first high power mode based at least in part on the switching upon expiration of the timer; and switching to the low power mode and enabling the low power mode synthesizer based at least in part on updating the first SNR.

[0227] Aspect 16: The method of any of aspects 1 through 15, wherein, measuring the set of performance metrics further comprises: periodically measuring a first signal to noise ratio (SNR) for a control channel code rate, wherein the set of performance metrics comprises a control channel SNR condition metric; and setting a value of the control channel SNR condition metric to indicate that a control channel is decodable based at least in part on a projected SNR for the low power mode that is based at least inpart on the first SNR satisfying a first threshold, or based at least in part on the first SNR satisfying a second threshold, or both, wherein enabling the low power mode synthesizer and entering the low power mode is based at least in part on the value indicating that the control channel is decodable.

[0228] Aspect 17: The method of aspect 16, further comprising: receiving one or more reference signals in the low power mode, the one or more reference signals corresponding to an SNR estimate; maintaining the value of the control channel SNR condition metric to indicate that the control channel is decodable based at least in part on a second SNR satisfying the first threshold; and continuing to operate in the low power mode using the low power mode synthesizer.

[0229] Aspect 18: The method of any of aspects 16 through 17, further comprising: receiving one or more reference signals in the low power mode, the one or more reference signals corresponding to an SNR estimate; setting the value of the control channel SNR condition metric to indicate that the control channel is not decodable based at least in part on a second SNR failing to satisfy the first threshold; and switching to the first high power mode, disabling the low power mode synthesizer, and enabling the high power mode synthesizer based at least in part on setting the value to indicate that the control channel is not decodable.

[0230] Aspect 19: A UE for wireless communications, comprising a processing system that includes processor circuitry and memory circuitry that stores code, the processing system configured to cause the UE to perform a method of any of aspects 1 through 18.

[0231] Aspect 20: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 18.

[0232] Aspect 21 : A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 18. It should be noted that the methods described herein describe possible implementations. The operations and the steps may be rearranged or otherwise modified and other implementations are possible. Further, aspects from two or more of the methods may be combined.

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

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

[0235] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a graphics processing unit (GPU), a neural processing unit (NPU), an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

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

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

[0238] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or Bor C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

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

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

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

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

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

Claims

CLAIMSWhat is claimed is:

1. A user equipment (UE), comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to: receive downlink traffic while operating in a first high power mode using a high power mode synthesizer; detect that each of a first set of parameters corresponding to the downlink traffic satisfy respective thresholds; measure a set of performance metrics based at least in part on each of the first set of parameters satisfying the respective thresholds; and enter a low power mode and enable a low power mode synthesizer based at least in part on each of the first set of parameters satisfying the respective thresholds and based at least in part on each performance metric of the set of performance metrics satisfying respective thresholds.

2. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: periodically detect the first set of parameters during a moving time window; determine that the first set of parameters satisfy the respective thresholds based at least in part on the detecting; generate a proposal to switch from the first high power mode to a low power mode based at least in part on the determining; and confirm the proposal to switch from the first high power mode to the low power mode based at least in part on each performance metric of the set of performance metrics satisfying respective thresholds.

3. The UE of claim 2, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:receive control signaling indicating a modulation and coding scheme for the downlink traffic, wherein one of the first set of parameters comprises the modulation and coding scheme.

4. The UE of claim 2, wherein, to detect the first set of parameters, the one or more processors are individually or collectively operable to execute the code to cause the UE to: measure a block error rate (BLER), measure a signal to noise ratio (SNR), or refer to a current modulation and coding scheme.

5. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: switch to the first high power mode, disable the low power mode synthesizer, and enable the high power mode synthesizer based at least in part on any of the set of performance metrics failing to satisfy a respective threshold.

6. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: switch, via a controller, between the first high power mode, a second high power mode, and the low power mode; and disable the second high power mode based at least in part on analog-to- digital-converter sampling rate reduction being unavailable according to one or more current conditions, wherein enabling a low power mode synthesizer and entering the low power mode is based at least in part on the disabling.

7. The UE of claim 1, wherein, to measure the set of performance metrics, the one or more processors are individually or collectively operable to execute the code to cause the UE to: measure a signal to noise ratio (SNR) degradation within a plurality of time intervals of a time window, the set of performance metrics comprising a reception reciprocal mixing impact metric; and set a value of the reception reciprocal mixing impact metric to indicate an absence of reciprocal mixing impact based at least in part on the SNR degradation failing to satisfy a threshold SNR degradation threshold during a threshold quantity oftime intervals of the plurality of time intervals, wherein enabling the low power mode synthesizer and entering the low power mode is based at least in part on the value indicating the absence of the reciprocal mixing impact.

8. The UE of claim 7, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: measure the SNR degradation within a second plurality of time intervals of a second time window while operating in the low power mode; set the value of the reception reciprocal mixing impact metric to indicate a reciprocal mixing impact based at least in part on the SNR degradation satisfying the threshold SNR degradation threshold in during the threshold quantity of time intervals of the second plurality of time intervals; and switch to the first high power mode, disable the low power mode synthesizer, and enable the high power mode synthesizer based at least in part on setting the value to indicate the reciprocal mixing impact.

9. The UE of claim 8, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: measure the SNR degradation within a third plurality of time intervals of a third time window while operating in the high power mode; set the value of the reception reciprocal mixing impact metric to indicate a reciprocal mixing impact based at least in part on the SNR degradation satisfying the threshold SNR degradation threshold in during the threshold quantity of time intervals of the third plurality of time intervals; and refrain from switching to the low power mode based at least in part on setting the value to indicate the reciprocal mixing impact.

10. The UE of claim 1, wherein, to measure the set of performance metrics, the one or more processors are individually or collectively operable to execute the code to cause the UE to: monitor a transmission power utilized in the high power mode during a transmission window, a reference signal receive power indicated during the transmission window, or both, wherein the set of performance metrics comprises a transmission reciprocal mixing impact metric; andset a value of the transmission reciprocal mixing impact metric to indicate an absence of a reciprocal mixing impact corresponding to an SNR degradation based at least in part on the monitoring, wherein enabling the low power mode synthesizer and entering the low power mode is based at least in part on the value indicating the absence of the reciprocal mixing impact.

11. The UE of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: monitor the transmission power utilized in the low power mode during a second transmission window, the reference signal receive power indicated during the second transmission window, or both; set a value of the transmission reciprocal mixing impact metric to indicate a reciprocal mixing impact corresponding to an SNR degradation based at least in part on the monitoring during the second transmission window; and switch to the first high power mode, disable the low power mode synthesizer, and enable the high power mode synthesizer based at least in part on setting the value to indicate the reciprocal mixing impact.

12. The UE of claim 11, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: monitor the transmission power utilized in the high power mode during a third transmission window, the reference signal receive power indicated during the third transmission window, or both; set a value of the transmission reciprocal mixing impact metric to indicate a reciprocal mixing impact corresponding to an SNR degradation based at least in part on the monitoring during the third transmission window; and refrain from switching to the low power mode based at least in part on setting the value to indicate the reciprocal mixing impact.

13. The UE of claim 1, wherein, to measure the set of performance metrics, the one or more processors are individually or collectively operable to execute the code to cause the UE to:compute a first signal to noise ratio (SNR) corresponding to the first high power mode, wherein the set of performance metrics comprises a jammer impact metric; and set a value of the jammer impact metric to indicate an absence of a jammer impact on the first SNR based at least in part on the first SNR, wherein enabling the low power mode synthesizer and entering the low power mode is based at least in part on the value indicating the absence of the jammer impact.

14. The UE of claim 13, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: measure a second SNR corresponding to the low power mode; compare the second SNR to a projected low power mode SNR based at least in part on the first SNR; set a value of the jammer impact metric to indicate a jammer impact on the second SNR based at least in part on a difference between the second SNR and the projected low power mode SNR satisfying a threshold; and switch to the first high power mode, disable the low power mode synthesizer, and enable the high power mode synthesizer based at least in part on setting the value to indicate the jammer impact on the second SNR.

15. The UE of claim 13, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: initiate a timer upon entering the low power mode; switch to the first high power mode, disable the low power mode synthesizer, and enable the high power mode synthesizer upon expiration of the timer; update the first SNR corresponding to the first high power mode based at least in part on the switching upon expiration of the timer; and switch to the low power mode and enable the low power mode synthesizer based at least in part on updating the first SNR.

16. The UE of claim 1, wherein, to measure the set of performance metrics, the one or more processors are individually or collectively operable to execute the code to cause the UE to:periodically measure a first signal to noise ratio (SNR) for a control channel code rate, wherein the set of performance metrics comprises a control channel SNR condition metric; and set a value of the control channel SNR condition metric to indicate that a control channel is decodable based at least in part on a projected SNR for the low power mode that is based at least in part on the first SNR satisfying a first threshold, or based at least in part on the first SNR satisfying a second threshold, or both, wherein enabling the low power mode synthesizer and entering the low power mode is based at least in part on the value indicating that the control channel is decodable.

17. The UE of claim 16, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: receive one or more reference signals in the low power mode, the one or more reference signals corresponding to an SNR estimate; maintain the value of the control channel SNR condition metric to indicate that the control channel is decodable based at least in part on a second SNR satisfying the first threshold; and continue to operate in the low power mode using the low power mode synthesizer.

18. The UE of claim 16, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to: receive one or more reference signals in the low power mode, the one or more reference signals corresponding to an SNR estimate; set the value of the control channel SNR condition metric to indicate that the control channel is not decodable based at least in part on a second SNR failing to satisfy the first threshold; and switch to the first high power mode, disable the low power mode synthesizer, and enable the high power mode synthesizer based at least in part on setting the value to indicate that the control channel is not decodable.

19. A method for wireless communications at a user equipment (UE), comprising:receiving downlink traffic while operating in a first high power mode using a high power mode synthesizer; detect that each of a first set of parameters corresponding to the downlink traffic satisfy respective thresholds; measuring a set of performance metrics based at least in part on each of the first set of parameters satisfying the respective thresholds; and entering a low power mode and enabling a low power mode synthesizer based at least in part on each of the first set of parameters satisfying the respective thresholds and based at least in part on each performance metric of the set of performance metrics satisfying respective thresholds.

20. A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to: receive downlink traffic while operating in a first high power mode using a high power mode synthesizer; detect that each of a first set of parameters corresponding to the downlink traffic satisfies respective thresholds; measure a set of performance metrics based at least in part on each of the first set of parameters satisfying the respective thresholds; and enter a low power mode and enabling a low power mode synthesizer based at least in part on each of the first set of parameters satisfying the respective thresholds and based at least in part on each performance metric of the set of performance metrics satisfying respective thresholds.

Images