Selective cellular interference mitigation for gnss
By introducing a resource block allocation probability engine into wireless communication devices, cellular interference is selectively mitigated based on location and time, thus solving the problem of harmonic signal interference to GNSS signals, improving the quality of received signals, and saving power consumption.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- APPLE INC
- Filing Date
- 2022-08-30
- Publication Date
- 2026-05-26
AI Technical Summary
Harmonic signals generated by the transmitted signals in wireless communication devices interfere with the received signals, resulting in a degraded quality of the received signals, especially interference with Global Navigation Satellite System (GNSS) signals.
By introducing a resource block allocation probability engine into wireless communication devices, interference can be selectively mitigated based on location, time, and historical allocation data. This includes reducing cellular transmitter power, deactivating GNSS receivers, or using machine learning filters based on resource block combinations to filter out interference signals.
It effectively reduces the impact of cellular interference on GNSS signals, improves the quality of received signals, saves power consumption, and enhances the intelligence and accuracy of interference management.
Smart Images

Figure CN115842563B_ABST
Abstract
Description
[0001] Cross-references to related applications
[0002] This application claims priority to U.S. Provisional Application No. 63 / 247,202, filed September 22, 2021, entitled “SELECTIVE CELLULAR INTERFERENCEMITIGATION FOR GNSS,” the entire disclosure of which is incorporated herein by reference for all purposes. Background Technology
[0003] This disclosure relates in general to wireless communications, and more specifically to radio frequency interference in wireless communication devices.
[0004] Wireless communication devices may include a transmitter and a receiver. The transmitter may send a transmitted signal at a transmit frequency, and the receiver may receive a received signal at a receive frequency. However, the transmitted signal may generate harmonic signals with harmonic frequencies close to or overlapping with the receive frequency. Therefore, the harmonic signals can interfere with the received signal, thereby weakening it. Summary of the Invention
[0005] The following outlines some of the embodiments disclosed herein. It should be understood that these aspects are presented merely to provide the reader with a concise overview of these particular embodiments, and are not intended to limit the scope of this disclosure. In fact, this disclosure may cover many aspects not set forth below.
[0006] In one embodiment, the user equipment includes a transceiver, a Global Navigation Satellite System (GNSS) receiver, and processing circuitry. The processing circuitry receives an instruction to transmit a signal using the transceiver, receives a location via the GNSS receiver, and receives the time of day. The processing circuitry also selectively mitigates interference caused by transmitting the signal using the transceiver based on the location and the time of day, and causes the transceiver to transmit the signal based on the selective mitigation of interference.
[0007] In another embodiment, a method includes receiving, at a processing circuit of a wireless communication device, an instruction to transmit a signal using a transmitter of the wireless communication device to execute a client process. The method further includes receiving, at the processing circuit, signal characteristics for transmitting the signal. The method also includes selectively mitigating interference generated by transmitting the signal using the transmitter to execute the client process based on the client process and the signal characteristics. The method further includes causing the transmitter to transmit the signal based on the selective mitigation of the interference by the processing circuit.
[0008] In another embodiment, one or more tangible, non-transitory computer-readable media store computer-readable instructions that cause one or more processors of a wireless communication device to: receive an instruction to transmit a signal using a transmitter of the wireless communication device, and to receive the location of the wireless communication device and the time of day. These computer-readable instructions also cause the one or more processors to: receive crowdsourced resource block allocation data corresponding to the location and time of day of the wireless communication device. These computer-readable instructions further cause the one or more processors to: receive resource block usage probabilities for transmitting the signal using the transmitter, based on the crowdsourced resource block allocation data. These computer-readable instructions also cause the one or more processors to: selectively mitigate interference caused by transmitting the signal using the transmitter, based on the resource block usage probabilities, and cause the transmitter to transmit the signal based on the selective mitigation of interference.
[0009] Various modifications to the above-described features may exist with respect to various aspects of the invention. Other features may also be incorporated into these aspects. These modifications and additional features may exist individually or in any combination. For example, various features discussed below relating to one or more illustrated embodiments may be incorporated individually or in any combination into any of the above aspects of the invention. The brief summary presented above is intended only to familiarize the reader with specific aspects and context of the embodiments disclosed herein and does not limit the claimed subject matter. Attached Figure Description
[0010] Various aspects of this disclosure can be better understood by reading the following detailed description and referring to the accompanying drawings, wherein similar figures refer to similar parts.
[0011] Figure 1 This is a block diagram of user equipment according to an embodiment of this disclosure;
[0012] Figure 2 It is based on the implementation scheme of this disclosure. Figure 1 Functional diagram of user equipment;
[0013] Figure 3 It is based on the implementation scheme of this disclosure. Figure 1 A schematic diagram of the transmitter of the user equipment;
[0014] Figure 4 It is based on the implementation scheme of this disclosure. Figure 1 A schematic diagram of the receiver for the user equipment;
[0015] Figure 5 It is based on the implementation scheme of this disclosure and has Figure 1A schematic diagram of the communication system of the user equipment, which is connected to a cellular network via a cellular base station and to a Global Navigation Satellite System (GNSS) network via GNSS satellite communication; and
[0016] Figure 6 This is a flowchart of a method for selectively mitigating cellular interference according to an embodiment of the present disclosure. Detailed Implementation
[0017] One or more specific implementations will be described below. To provide a brief description of these implementations, not all characteristics of the actual implementations are described in this specification. It should be understood that in the development of any such actual implementation, as in any engineering or design project, decisions must be made specific to many implementations to achieve the developer's specific objectives, such as compliance with system-related and business-related constraints that may vary from one implementation to another. Furthermore, it should be understood that such development work can be complex and time-consuming, but will still be routine work of design, fabrication, and manufacturing for those skilled in the art who benefit from this disclosure.
[0018] When describing elements of various embodiments of this disclosure, the articles “an” and “the” are intended to refer to one or more of the elements present. The terms “comprising,” “including,” and “having” are intended to be included and to indicate the presence of additional elements besides those listed. Additionally, it should be understood that reference to “an embodiment” or “an embodiment” of this disclosure is not intended to be construed as excluding the existence of additional embodiments also incorporating the cited features. Furthermore, specific features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. The use of the terms “generally,” “approximately,” “about,” “close to,” and / or “substantially” should be understood to mean including close to the target (e.g., design, value, quantity), such as within limits of any suitable or conceivable error (e.g., within 0.1% of the target, within 1% of the target, within 5% of the target, within 10% of the target, within 25% of the target, etc.). Furthermore, it should be understood that any exact values, figures, measurements, etc. provided herein may be envisioned as approximations of such exact values, figures, measurements, etc. (e.g., within limits of suitable or conceivable error).
[0019] This disclosure relates to selectively mitigating cellular interference to Global Navigation Satellite System (GNSS) signals. A transmitter of a wireless communication device can transmit a transmitted signal at a transmit frequency, and a receiver of the wireless communication device can receive a received signal at a receive frequency. However, the transmitted signal can generate harmonic signals with harmonic frequencies close to or overlapping with the receive frequency. That is, transmitting the transmitted signal can result in the generation of one or more harmonic signals with harmonic frequencies that are multiples of the transmitted frequency. Therefore, the harmonic signals can interfere with the received signal, thereby attenuating the received signal, which can lead to data loss at the receiver. For example, the transmitter may include a cellular transmitter that transmits the transmitted signal in a Long Term Evolution (LTE) band 13 (e.g., a 700 MHz band with an uplink frequency range of 777 MHz to 787 MHz) or an LTE band 14 (e.g., a 700 MHz band with an uplink frequency range of 788 MHz to 798 MHz). This transmitted signal can generate a harmonic signal at twice the frequency of LTE bands 13 or 14 (e.g., 1554MHz to 1596MHz), which can approach or overlap with GNSS signals in GNSS band L1 (e.g., centered at 1575.42MHz). Therefore, the transmitted signal will interfere with GNSS signals. It should be understood that references to LTE bands 13 and 14 and GNSS band L1 are exemplary, and the embodiments disclosed herein are applicable to any suitable band that interferes with other bands, or to any suitable band where transmissions in those bands result in harmonic signals interfering with other bands.
[0020] In some cases, such interference of cellular transmissions on GNSS reception can be mitigated when cellular transmissions are anticipated by reducing (e.g., on LTE bands 13 and / or 14) the power of cellular transmissions, or by stopping cellular transmissions and / or reducing the power to the GNSS receiver or deactivating the GNSS receiver (e.g., by reducing automatic gain control). In other or alternative cases, machine learning filters based on resource block combinations can be used to filter the transmitted signal from the received GNSS signal.
[0021] However, such filters consume excessive power (e.g., the filter may be active for extended periods or always active). Furthermore, these mitigation procedures may be implemented unnecessarily. Specifically, at a given time (e.g., every 1 millisecond (ms)), a network (e.g., a cellular network) may allocate multiple (e.g., 50) resource blocks. Each resource block may include a different frequency range. In some cases, the number of allocable resource blocks may change over time (e.g., decrease). For example, at 0 ms, the number of allocable resource blocks may be 50, and the network may allocate any number of the 50 allocable resource blocks to a wireless communication device (e.g., user equipment). At 1 ms, the number of allocable resource blocks may decrease by 1 (e.g., a total of 49), and the network may allocate any number of the 49 allocable resource blocks to the user equipment. However, at the end of this cycle, for example at 49 ms, only one allocable resource block may remain to be allocated to the user equipment. This allocation may be referred to as "1RB 49" because it is one resource block long and begins at the resource block indexed 49. (Resource blocks typically begin at index 0.) For LTE bands 13 and / or 14, this single resource block may include frequency ranges that could interfere with the GNSS L1 band in cases of harmonic generation. The other 49 resource blocks do not interfere with the GNSS L1 band because they include frequency ranges that do not interfere with the GNSS L1 band in cases of harmonic generation. Therefore, in this case, mitigation procedures are only required if an allocatable resource block exists.
[0022] Figure 1 This is a block diagram of a user equipment 10 (e.g., an electronic device) according to an embodiment of the present disclosure. Among other things, the user equipment 10 may include one or more processors 12 (collectively referred to herein as a single processor, which may be implemented in any suitable form of processing circuitry), memory 14, non-volatile storage device 16, display 18, input structure 22, input / output (I / O) interface 24, network interface 26, and power supply 29. Figure 1 The various functional blocks shown may include hardware elements (including circuitry), software elements (including machine-executable instructions), or combinations of hardware and software elements (which may be referred to as logic). Processor 12, memory 14, non-volatile storage device 16, display 18, input structure 22, input / output (I / O) interface 24, network interface 26, and / or power supply 29 may each be directly or indirectly communicatively coupled to each other (e.g., via another component, communication bus, network) to transmit and / or receive data between them. It should be noted that... Figure 1 This is merely an example of a specific implementation and is intended to illustrate the types of components that may exist in user equipment 10.
[0023] For example, user equipment 10 may include any suitable computing device, including desktop or laptop computers (e.g., those available from Apple Inc. in Cupertino, California). Pro, MacBook mini or Mac (in the form of) portable or handheld electronic devices such as wireless electronic devices or smartphones (e.g., those available from Apple Inc. in Cupertino, California). (in the form of a model), tablet computer (e.g., available from Apple Inc. in Cupertino, California). (in the form of a model), wearable electronic devices (e.g., those available from Apple Inc. in Cupertino, California). (in the form of) or other similar equipment. It should be noted that Figure 1 The processor 12 and other related items herein may be generally referred to as "data processing circuitry". This data processing circuitry may be embodied wholly or partially in software, hardware, or both. Furthermore, the processor 12 and... Figure 1 Other related items may be a single, independent processing module, or may be fully or partially integrated into any of the other elements within user equipment 10. Processor 12 may be implemented using a combination of a general-purpose microprocessor, microcontroller, digital signal processor (DSP), field-programmable gate array (FPGA), programmable logic device (PLD), controller, state machine, gated logic, discrete hardware components, dedicated hardware finite state machine, or any other suitable entity capable of performing computational or other manipulations of information. Processor 12 may include one or more application processors, one or more baseband processors, or both, and performs the various functions described herein.
[0024] exist Figure 1 In user equipment 10, processor 12 may be operatively coupled to memory 14 and non-volatile storage device 16 to execute various algorithms. Such programs or instructions executed by processor 12 may be stored in any suitable article of writing comprising one or more tangible computer-readable media. The tangible computer-readable media may include memory 14 and / or non-volatile storage device 16, individually or jointly, to store instructions or routines. Memory 14 and non-volatile storage device 16 may include any suitable article of writing for storing data and executable instructions, such as random access memory, read-only memory, rewritable flash memory, hard disk drive, and optical disk. Furthermore, programs (e.g., operating systems) encoded on such computer program products may also include instructions executable by processor 12 to enable user equipment 10 to provide various functions.
[0025] In some embodiments, display 18 may facilitate a user's viewing of images generated on user equipment 10. In some embodiments, display 18 may include a touchscreen that facilitates user interaction with the user interface of user equipment 10. Furthermore, it should be understood that in some embodiments, display 18 may include one or more liquid crystal displays (LCDs), light-emitting diode (LED) displays, organic light-emitting diode (OLED) displays, active-matrix organic light-emitting diode (AMOLED) displays, or some combination of these and / or other display technologies.
[0026] The input structure 22 of user equipment 10 allows a user to interact with user equipment 10 (e.g., press a button to increase or decrease the volume level). Like network interface 26, I / O interface 24 enables user equipment 10 to interact with a variety of other electronic devices. In some embodiments, I / O interface 24 may include I / O ports for hardwired connections for charging and / or content manipulation using standard connectors and protocols such as the Lightning connector supplied by Apple Inc. of Cupertino, California, Universal Serial Bus (USB), or other similar connectors and protocols. Network interface 26 may include one or more interfaces, for example, for personal area networks (PANs) such as Ultra Wideband (UWB) or... Network; Local Area Network (LAN) or Wireless Local Area Network (WLAN) such as a protocol using one of the IEEE 802.11x series protocols (e.g., Networks; and / or wide area networks (WANs) such as any standards related to the 3rd Generation Partnership Project (3GPP), including, for example, third-generation (3G) cellular networks, Universal Mobile Telecommunications System (UMTS), fourth-generation (4G) cellular networks, Long Term Evolution (LTE) networks. Cellular networks, Long Term Evolution License Assisted Access (LTE-LAA) cellular networks, fifth-generation (5G) cellular networks and / or new radio (NR) cellular networks, satellite networks, etc. Specifically, network interface 26 may include, for example, one or more interfaces for using the version 15 cellular communication standard of the 5G specification, which includes millimeter wave (mm wave) frequency ranges (e.g., 24.25 GHz - 300 GHz), and / or any other version of the cellular communication standard (e.g., version 16, version 17, any future version) that defines and / or implements frequency ranges for wireless communication. The network interface 26 of user equipment 10 may allow communication via the aforementioned networks (e.g., 5G, Wi-Fi, LTE-LAA, etc.).
[0027] Network interface 26 may also include one or more interfaces for, for example, a broadband fixed wireless access network (e.g., Mobile broadband wireless network (mobile) Asynchronous digital subscriber lines (e.g., ADSL, VDSL) and digital video terrestrial broadcasting Network and its extensions DVB handheld Networks, ultra-wideband (UWB) networks, AC power lines, etc.
[0028] As shown, network interface 26 may include transceiver 30. In some embodiments, all or part of transceiver 30 may be located within processor 12. Transceiver 30 may support the transmission and reception of various wireless signals via one or more antennas, and therefore may include both a transmitter and a receiver. The power supply 29 of user equipment 10 may include any suitable power source, such as a rechargeable lithium polymer (Li-poly) battery and / or an alternating current (AC) power converter.
[0029] Figure 2 It is based on the implementation scheme of this disclosure. Figure 1 The functional diagram of user equipment 10 is shown. As shown, processor 12, memory 14, transceiver 30, transmitter 52, receiver 54 and / or antenna 55 (shown as 55A-55N, collectively referred to as antenna 55) may be directly or indirectly communicatively coupled to each other (e.g., through or via another component, communication bus, network) to transmit and / or receive data between each other.
[0030] Specifically, the transceiver 30 may take the form of a cellular transceiver 30 having a cellular transmitter 52 and / or a cellular receiver 54, which respectively enable the transmission and reception of cellular signals between user equipment 10 and external devices via, for example, a cellular network (e.g., including base stations such as NodeB, eNB, or eNodeB (evolved NodeB or E-UTRAN (Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network) NodeB) or gNodeB (e.g., next-generation NodeB)). As shown, the cellular transmitter 52 and the cellular receiver 54 may be combined into the cellular transceiver 30.
[0031] Additionally, user equipment 10 may include a GNSS receiver 56, which enables user equipment 10 to receive GNSS signals from a GNSS network comprising one or more GNSS satellites or GNSS ground stations. GNSS signals may include observation data from GNSS satellites, broadcast orbit information from tracked GNSS satellites, and supporting data such as meteorological parameters collected from cooperative positioning devices of GNSS satellites. For example, GNSS signals may be received from networks such as the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Galileo Navigation Satellite System, and the Quasi-Zenith Satellite System (QZSS or Michibiki).
[0032] User equipment 10 may also have one or more antennas 55A-55N (collectively referred to as 55) electrically coupled to cellular transceiver 30, and one or more antennas 57A-57N (collectively referred to as 57) electrically coupled to GNSS receiver 56. Antennas 55 and 57 may be configured in omnidirectional or directional configurations, single-beam, dual-beam, or multi-beam arrangements. Each antenna 55 and 57 may be associated with one or more beams and various configurations. In some embodiments, multiple antennas in antennas 55 and 57 of an antenna group or module may be communicatively coupled to a corresponding transceiver 30 or GNSS receiver 56, and each emits radio frequency signals that can be combined constructively and / or destructively to form a beam. User equipment 10 may include multiple transmitters, multiple receivers, multiple transceivers, and / or multiple antennas suitable for various communication standards.
[0033] User equipment 10 may include a resource block (RB) allocation probability engine 58, which may be implemented as hardware (e.g., circuitry), software (e.g., instructions stored in memory 14 and / or storage device 16), or both (e.g., as logic). The resource block allocation probability engine 58 can determine the probability that a cellular network (e.g., a 3G cellular network, a 4G / LTE cellular network, a 5G / NR cellular network, etc.) may allocate a resource block to user equipment 10 at a frequency that is a harmonic signal that could interfere with the GNSS signal received by GNSS receiver 56 when the cellular transmitter 52 uses the resource block to transmit a signal. For example, the resource block may be in LTE band 13 or 14, and the GNSS signal may be in the GNSS L1 band. The resource block allocation probability engine 58 may receive multiple inputs and determine the probability based on these inputs. In some embodiments, these inputs may include the location of user equipment 10, the current date and / or time, historical allocations of resource blocks (which may be crowdsourced), the client type associated with the signal to be transmitted, the signal environment at user equipment 10, real-world conditions, etc. Therefore, the resource block allocation probability engine 58 can ultimately determine the probability that cellular transmissions made by the cellular transmitter 52 will interfere with GNSS signals, and determine whether to perform mitigation procedures based on that probability.
[0034] As shown in the figure, various components of user equipment 10 can be coupled together via bus system 59. Bus system 59 may include, for example, a data bus, as well as power buses, control signal buses, and status signal buses in addition to the data bus. Components of user equipment 10 can be coupled together or use some other mechanism to accept or provide input to each other.
[0035] Figure 3This is a schematic diagram of a cellular transmitter 52 (e.g., a transmitting circuit) according to an embodiment of the present disclosure. As shown, the cellular transmitter 52 can receive outgoing data 60 to be transmitted via one or more antennas 55 in the form of a digital signal. A digital-to-analog converter (DAC) 62 of the cellular transmitter 52 can convert the digital signal into an analog signal, and a modulator 64 can combine the converted analog signal with a carrier signal to generate radio waves. A power amplifier (PA) 66 receives the modulated signal from the modulator 64. The power amplifier 66 can amplify the modulated signal to a suitable level to drive the transmission of the signal via one or more antennas 55. A filter 68 (e.g., filter circuitry and / or software) of the cellular transmitter 52 can then remove unwanted noise from the amplified signal to generate transmitted data 70 to be transmitted via one or more antennas 55. The filter 68 may include one or more suitable filters, such as bandpass filters, bandstop filters, low-pass filters, high-pass filters, and / or decimation filters, for removing unwanted noise from the amplified signal. Additionally, the cellular transmitter 52 may include any suitable additional components not shown, or may exclude some of the components shown, such that the cellular transmitter 52 can transmit data 60 via one or more antennas 55. For example, the cellular transmitter 52 may include a mixer and / or a digital up-converter. Furthermore, if the power amplifier 66 outputs the amplified signal within or substantially within the desired frequency range (so that filtering of the amplified signal is unnecessary), the cellular transmitter 52 may not include a filter 68.
[0036] Figure 4 This is a schematic diagram of receivers 54, 56 (e.g., receiver circuitry) of user equipment 10 according to an embodiment of this disclosure. Specifically, receivers 54, 56 may include... Figure 2The cellular receiver 54 and / or GNSS receiver 56 are shown. As illustrated, receivers 54 and 56 can receive data 80 (e.g., cellular data or GNSS data) from one or more antennas 55 and 57 in the form of analog signals. A low-noise amplifier (LNA) 82 can amplify the received analog signal to a suitable level for processing by receivers 54 and 56. A filter 84 (e.g., filter circuitry and / or software) can remove unwanted noise, such as interchannel interference, from the received signal. Filter 84 can also remove additional signals received by one or more antennas 55 and 57 at frequencies different from the desired signal. Filter 84 may include one or more suitable filters, such as bandpass filters, bandstop filters, low-pass filters, high-pass filters, and / or decimation filters, for removing unwanted noise or signals from the received signal. For example, filter 84 may include one or more machine learning filters based on resource block combinations that filter out transmitted signals at specific frequencies (e.g., 1554MHz to 1596MHz of harmonic signals caused by cellular signals transmitted in LTE bands 13 or 14) from GNSS received signals (e.g., which may be in GNSS band L1 centered at 1575.42MHz).
[0037] Receivers 54 and 56 may also include a demodulator 86 that removes the radio frequency envelope from the filtered signal and / or extracts the demodulated signal from the filtered signal for processing. An analog-to-digital converter (ADC) 88 may receive the demodulated analog signal and convert it into a digital signal of the incoming data 90 for further processing by the user equipment 10. Additionally, receivers 54 and 56 may include any suitable additional components not shown, or may exclude some of the components shown, such that receivers 54 and 56 can receive the received data 80 via one or more antennas 55 and 57. For example, receivers 54 and 56 may include a mixer and / or a digital downconverter.
[0038] Figure 5This is a schematic diagram of a communication system 98 having user equipment 10 according to an embodiment of the present disclosure. The user equipment is communicatively coupled to a cellular network 100 (e.g., a 3G cellular network, a 4G / LTE cellular network, a 5G / NR cellular network, etc.) via a cellular base station 102 (e.g., a NodeB, eNodeB, gNodeB, etc.) and communicatively coupled to a GNSS network 104 via a GNSS satellite 106. The cellular network 100 may be implemented and / or supported by multiple such base stations 102, radio access networks, core networks, etc. Similarly, the GNSS network 104 may be implemented and / or supported by multiple such GNSS satellites 106, ground stations, etc. However, in some cases, the user equipment 10 may use a cellular transmitter 52 to transmit a signal that generates a harmonic signal having a harmonic frequency close to or overlapping with the reception frequency of the GNSS signal transmitted by the GNSS satellite 106 and received by the GNSS receiver 56 of the user equipment 10. This harmonic signal may interfere with the GNSS signal, as discussed above.
[0039] Cellular transmitter 52 may transmit cellular signals in LTE band 13 (e.g., the 700 MHz band, with an uplink frequency range of 777 MHz to 787 MHz) or LTE band 14 (e.g., the 700 MHz band, with an uplink frequency range of 788 MHz to 798 MHz). This cellular signal may generate harmonic signals at twice the frequency of LTE band 13 or 14 (e.g., 1554 MHz to 1596 MHz), which may approach or overlap with GNSS signals received by GNSS receiver 56 in GNSS band L1 (e.g., centered at 1575.42 MHz). Therefore, the cellular signal may interfere with the GNSS signal.
[0040] In some cases, such interference from cellular transmissions to GNSS reception can be mitigated when cellular transmissions are anticipated by reducing (e.g., at least in LTE bands 13 and / or 14) the power of the cellular transmitter 52 or stopping the cellular transmitter and / or reducing the power to the GNSS receiver 56 or deactivating the GNSS receiver (e.g., by reducing automatic gain control). In other or alternative cases, the filter (e.g., 84) of the GNSS receiver 56 may include a machine learning filter based on resource block combination that filters out transmitted signals at specific frequencies (e.g., 1554MHz to 1596MHz of harmonic signals caused by cellular signals transmitted in LTE bands 13 or 14) from the GNSS received signal (e.g., which may be in GNSS band L1 centered at 1575.42MHz).
[0041] However, such filters consume excessive power because they may not be applied selectively, but rather remain active for extended periods or are always active. Furthermore, these mitigation procedures may be implemented unnecessarily. Specifically, at a given periodicity (e.g., every 1 millisecond (ms)), a network (e.g., cellular network 100) may allocate time and frequency resources to user equipment 10 to enable user equipment 10 to transmit and / or receive radio frequency signals. Resources may be allocated as resource blocks. However, the number of allocable resource blocks may be finite (e.g., up to 50 resource blocks may be allocable), and the number of allocable resource blocks may change over time (e.g., decrease). For example, at 0 ms, the number of allocable resource blocks may be at most 50, and cellular network 100 may allocate any number of allocable resource blocks from the 50 available blocks to user equipment 10. At 1 ms, the number of allocable resource blocks may decrease by 1 (e.g., a total of 49), and cellular network 100 may allocate any number of allocable resource blocks from the 49 available blocks to user equipment 10. However, at the end of this cycle, for example at 49 ms, only one allocatable resource block may exist to be allocated to user equipment 10. For certain cellular bands (e.g., LTE bands 13 and / or 14), this single resource block may include a frequency range that would interfere with the GNSS band (e.g., GNSS L1 band) in cases where harmonics are generated when user equipment 10 transmits radio frequency signals using a single resource block. The other 49 resource blocks will not interfere with the GNSS L1 band because they may include frequency ranges that would not interfere with the GNSS L1 band in cases where harmonics are generated. Furthermore, the probability of interference increases when only a single resource block is allocatable because the probability of allocating a single interfering resource block increases (e.g., 100% probability) because no other allocatable resource blocks exist. Comparing this situation to the situation where multiple (e.g., 2 or more, 4 or more, 50) allocatable resource blocks exist results in a reduction of at least 50% in the probability of allocating a single interfering resource block. Therefore, in this case, mitigation procedures can only be performed when there is only one allocatable resource block (e.g., at 49 ms in the resource block allocation cycle).
[0042] The embodiments described herein provide various means and techniques for selectively mitigating cellular interference to (e.g., GNSS signals received by GNSS receiver 56) from (e.g., GNSS signals transmitted on cellular transmitter 52). Specifically, user equipment 10 can determine the probability that cellular network 100 may allocate a resource block to user equipment 10 at a frequency that is a harmonic signal that may interfere with the GNSS signal received by GNSS receiver 56 when cellular transmitter 52 transmits a radio frequency signal using the resource block. Using the previous example, the resource block may be within LTE band 13 or 14, and the GNSS signal may be within the GNSS L1 band. This probability may be based on multiple factors that can influence the allocation of the resource block, including the location of user equipment 10, the current date and / or time, the historical allocation of the resource block (which may be crowdsourced), the client type associated with the signal to be transmitted, the signal environment at user equipment 10, real-world conditions, etc.
[0043] Based on this probability, user equipment 10 may selectively perform mitigation procedures or transmit radio frequency signals without performing mitigation procedures. For example, if the probability is greater than or equal to a threshold, user equipment 10 may reduce the power of cellular transmitter 52 or prevent cellular transmitter 52 from transmitting signals, reduce the gain of GNSS receiver 56 or deactivate the GNSS receiver, activate one or more filters 84 to filter out at least a portion of the cellular transmitted signals from the GNSS signals received at GNSS receiver 56, and so on. If the probability is less than the threshold, cellular transmitter 52 may transmit cellular signals to base station 102 via LTE bands 13 and / or 14 without performing mitigation procedures.
[0044] Figure 6 This is a flowchart of a method 110 for selectively mitigating cellular interference according to an embodiment of the present disclosure. Method 110 can be executed by any suitable device (e.g., a controller) that controls components of user equipment 10 (such as processor 12 and / or resource block allocation probability engine 58). In some embodiments, method 110 can be implemented by using processor 12 to execute instructions stored in a tangible, non-transitory computer-readable medium such as memory 14 or storage device 16. For example, method 110 can be executed at least in part by one or more software components (such as the operating system of user equipment 10, one or more software applications of user equipment 10, resource block allocation probability engine 58, etc.). Although method 110 is described using a specific order of steps, it should be understood that the steps described herein are contemplated to be performed in a different order than shown, and that some described steps may be skipped or not performed at all.
[0045] In process block 111, processor 12 (e.g., from cellular network 100 via base station 102) receives an indication of the transmit signal and the transmit frequency range. Specifically, processor 12 may determine or receive an indication that a client of user equipment 10 will transmit radio frequency signals using cellular transmitter 52. That is, a client (e.g., a software application, first-party application, third-party application, daemon, thread, etc.) may execute a process on user equipment 10 (e.g., via the operating system of user equipment 10 and / or processor 12) that may request and cause cellular transmitter 52 to transmit cellular signals. Furthermore, base station 102 may schedule user equipment 10 for uplink and transmit to user equipment 10 a transmit frequency range (e.g., frequency band or channel) to be used for uplink. For example, base station 102 may transmit to user equipment 10 LTE frequency band 13 or 14 or a channel within LTE frequency band 13 or 14.
[0046] In process block 112, processor 12 receives or determines the location of user equipment 10. Specifically, GNSS receiver 56 of user equipment 10 may receive GNSS signals from GNSS network 104 via GNSS satellite 106 and determine the location of user equipment 10 based on the GNSS signals. In process block 114, processor 12 receives or determines the date and / or time. For example, user equipment 10 may receive or determine the current local date and / or time from an internal clock (e.g., a crystal, crystal oscillator, voltage-controlled crystal oscillator, etc.), cellular signals received from cellular network 100 via cellular base station 102 at cellular receiver 54, and / or GNSS signals received from GNSS network 104 via GNSS satellite 106 at GNSS receiver 56.
[0047] In process block 116, processor 12 receives or determines historical resource block allocation information based on the transmit frequency range received in process block 111, the location of user equipment 10 received in process block 112, the date received in process block 114, and / or the time received in process block 114. Specifically, processor 12 may generate a resource block allocation profile based on resource blocks allocated at different dates, times, and / or locations. That is, as user equipment 10 is communicatively coupled to cellular network 100 via cellular base station 102 over time, user equipment 10 stores information (e.g., in the form of a resource block allocation profile) related to resource blocks allocated by cellular network 100, the date of allocation, the time of allocation, and the location of user equipment 10. For example, user equipment 10 may be communicatively coupled to cellular network 100 via cellular base station 102 at noon on January 1, San Francisco, and receive one or more resource blocks allocated from cellular network 100. In addition, the resource block allocation profile can be further differentiated based on the day of the week (e.g., to identify different resource block allocation trends based on different days of the week, weekends and Sundays, etc.), special events of the year (e.g., holidays), and time of day corresponding to special events (e.g., parades, concerts, sporting events).
[0048] User equipment 10 may store this information in a resource block allocation configuration file. In some embodiments, processor 12 may store the resource block allocation configuration file and / or such information in the memory 14 and / or storage device 16 of user equipment 10. Each resource block allocation configuration file may be represented as a table, lookup table, formula, transfer function, heatmap, etc. In some embodiments, user equipment 10 may store the resource block allocation configuration file in a database indexed by resource blocks, date, time, location, geographic region, etc.
[0049] Additionally, this information can be received by User Equipment 10 from other User Equipment and stored as a resource block allocation profile. Specifically, User Equipment 10 can perform crowdsourcing techniques to receive or capture information related to resource blocks allocated by cellular network 100, the date of allocation, the time of allocation, and the locations of other User Equipment. In this way, User Equipment 10 can have more data points and a more accurate representation of which resource blocks were allocated and under what conditions (e.g., date, time, location, etc.).
[0050] To conserve memory and / or storage resources, in some cases, user equipment 10 may upload resource block allocation profiles to cloud storage, cellular network 100, etc. Therefore, user equipment 10 may download and / or store (e.g., in memory 14 and / or storage device 16) at least some resource block allocation profiles, such as those corresponding to the location of user equipment 10 and / or those corresponding to the current time (e.g., a threshold time range corresponding to the current time, such as a two-hour time range centered at the current time), date, and / or day of the week. User equipment 10 can then use, for example, the resource block allocation profiles corresponding to the location, time, and / or date of user equipment 10 to receive or determine historical resource block allocations performed by cellular network 100.
[0051] Additionally or alternatively, in process block 118, processor 12 receives or determines signal characteristics used for transmitting (e.g., received as indicated in process block 111) cellular signals. Signal characteristics may include any suitable indication of signal quality or strength, such as Resource Signal Strength Indicator (RSSI), Reference Received Power (RSRP), Reference Received Quality (RSRQ), Signal-to-Interference-plus-Noise Ratio (SINR), Signal-to-Noise-plus-Interference Ratio (SNIR), Signal-to-Noise Ratio (SNR), etc. For example, processor 12 may determine the RSSI of a transmit frequency range (e.g., LTE band 13 or 14 or a channel of LTE band 13 or 14) received in process block 111 while communicating with base station 102.
[0052] In process block 120, processor 12 receives or determines, based on signal characteristics, the likelihood of transmitting (e.g., receiving its indication in process block 111) a cellular signal at an increased or maximum transmit power (within the transmit frequency range received in process block 111). Increased transmit power may refer to transmit power greater than a threshold transmit power (e.g., greater than 50% or more, greater than 60% or more, greater than 70% or more, etc.), greater than the average transmit power, greater than the median transmit power, etc. Maximum transmit power may refer to the maximum transmit power that cellular transmitter 52 is enabled and / or permitted to transmit based on rules issued by a regulatory agency (e.g., the Federal Communications Commission (FCC), hardware capabilities, telecommunications specifications (e.g., 3GPP specifications), etc.).
[0053] In some implementations, user equipment 10 may generate and / or reference a relationship between signal characteristics (e.g., RSSI) and the transmit power of cellular transmitter 52 for transmitting cellular signals in a frequency band (e.g., LTE band 13 or 14) already allocated to it by cellular network 100. This relationship may be represented as a table, lookup table, formula, transfer function, heatmap, etc. For example, a higher RSSI results in better cellular coverage of user equipment 10, as provided by cellular network 100, and allows for lower transmit power usage, and a lower probability of retransmission by cellular transmitter 52 to transmit cellular signals in the band. Conversely, a lower RSSI results in poorer cellular coverage of user equipment 10, allows for higher transmit power usage, and a higher probability of retransmission by cellular transmitter 52 to transmit cellular signals in the band. In some cases, processor 12 may use artificial intelligence and / or machine learning techniques based on signal characteristics to determine the likelihood of transmitting cellular signals at increased or maximum transmit power, as explained in further detail below.
[0054] Additionally or alternatively, processor 12 receives or determines the type of client for which cellular signals are to be transmitted using cellular transmitter 52. As described above, a client may execute a process on user equipment 10 that requests and causes cellular transmitter 52 to transmit cellular signals. Each client, such as voice calls, video calls, video games, other sources of data requests, etc., may be associated with different duty cycles (e.g., the frequency and / or duration of data requests), which may affect resource block allocation or assignment.
[0055] In process block 124, processor 12 receives or determines the GNSS signal environment. For example, in a signal environment with fewer obstacles and / or more open sky (such as a rural environment), GNSS receiver 56 may receive a stronger GNSS signal. Therefore, since the stronger GNSS signal is less likely to be affected and / or weakened by harmonics of the cellular transmitted signal, the likelihood of needing to perform mitigation procedures is reduced. On the other hand, if the signal environment has more obstacles and / or less open sky, such as an urban environment or wooded area, GNSS receiver 56 may receive a weaker GNSS signal. Furthermore, urban environments may include more cellular base stations 102, which can further weaken the GNSS signal. Therefore, since the weaker GNSS signal is more likely to be affected and / or weakened by harmonics of the cellular transmitted signal, the likelihood of needing to perform mitigation procedures is increased.
[0056] In process block 124, processor 12 receives or determines real-world conditions that can affect resource block allocation. This may include factors such as time-based factors discussed above, such as holidays, parades, sporting events, etc., which can alter expected patterns of demand on cellular network 100, thereby affecting resource block allocation performed by cellular network 100. Similarly, natural disasters, epidemics, national and / or local emergencies can cause a sudden surge in demand on cellular network 100, thereby affecting resource block allocation performed by cellular network 100.
[0057] In process block 128, resource block allocation probability engine 58 determines the probability (e.g., resource block usage probability) that cellular network 100 may allocate a resource block with a certain frequency to user equipment 10, the frequency of which is a harmonic signal that may generate interference with the GNSS signal received by GNSS receiver 56 when cellular transmitter 52 uses the resource block to transmit a signal. Specifically, the resource block (e.g., a resource block designated 1RB 49) may be in LTE band 13 or 14, and the GNSS signal may be in GNSS L1 band.
[0058] As shown in the figure, the resource block allocation probability engine 58 may receive from the processor 12 historical resource block allocation information as determined in process block 116, the probability of transmitting a signal at increased or maximum transmit power as determined in process block 120, the client type for which a signal is to be transmitted as determined in process block 122, the GNSS signal environment as determined in process block 124, and / or real-world conditions as determined in process block 126. The resource block allocation probability engine 58 may then determine the probability that the cellular network 100 may allocate a resource block with a certain frequency to the user equipment 10 based on any combination of these factors that may affect resource block allocation, the frequency of which is a harmonic signal that may generate interference with the GNSS signal received by the GNSS receiver 56.
[0059] For example, the resource block allocation probability engine 58 can receive the transmission frequency range from process block 111, the location of user equipment 10 from process block 112, the current local time from process block 114, and historical resource block allocation information in the form of a set of crowdsourced resource block allocation profiles from process block 116. This set of crowdsourced resource block allocation profiles can be indexed by the transmission frequency range, location, and time. Therefore, the resource block allocation probability engine 58 can select a resource block allocation profile based on the transmission frequency range, location, and time, and determine the probability that user equipment 10 will be allocated a resource block that interferes with GNSS.
[0060] Additionally or alternatively, the resource block allocation probability engine 58 may receive the transmit frequency range from process block 111 and determine the signal characteristics (e.g., RSSI) from process block 118 for transmitting a signal using the transmit frequency range. The resource block allocation probability engine 58 may then determine the probability of transmitting the signal at increased or maximum transmit power. For example, if the RSSI is large (e.g., greater than a threshold), the cellular transmitter 52 may use a lower transmit power, and the probability of retransmission is lower, and the resource block allocation probability engine 58 may determine that the probability of transmitting the signal at increased or maximum transmit power is lower. On the other hand, if the RSSI is small (e.g., less than a threshold), the cellular transmitter 52 may use a higher transmit power, and the probability of retransmission is higher, and therefore, the resource block allocation probability engine 58 may determine that the probability of transmitting the signal at increased or maximum transmit power is higher. The resource block allocation probability engine 58 may then determine the probability that user equipment 10 will be allocated a resource block that interferes with GNSS.
[0061] Additionally or alternatively, the resource block allocation probability engine 58 may receive an indication of the type of client requesting or causing the cellular transmitter 52 to transmit cellular signals (e.g., on LTE bands 13 or 14) from process block 122, and determine the probability that user equipment 10 will be allocated a resource block that interferes with GNSS based on the client type. For example, the resource block allocation probability engine 58 may (e.g., based on the client type) determine the duty cycle associated with the client (e.g., the frequency and / or duration of data requests), and determine the probability that user equipment 10 will be allocated a resource block that interferes with GNSS based on the duty cycle. That is, the frequency and / or duration of data requests by certain client types can affect the allocation of resource blocks by the cellular network 100.
[0062] Additionally or alternatively, the resource block allocation probability engine 58 may receive the GNSS signal environment (e.g., fewer obstacles vs. more obstacles) from process block 124 and determine the probability that user equipment 10 will be allocated a resource block that interferes with GNSS based on the signal environment. Specifically, a more unobstructed signal path between user equipment 10 and GNSS satellite 106 may result in higher (e.g., above a threshold) GNSS received power, while a more obstructed signal path between user equipment 10 and GNSS satellite 106 may result in lower (e.g., below a threshold) GNSS received power. The resource block allocation probability engine 58 may then determine the probability that user equipment 10 will be allocated a resource block that interferes with GNSS based on the possible GNSS received power estimated according to the signal environment.
[0063] Additionally or alternatively, the resource block allocation probability engine 58 can receive real-world conditions in process box 126, such as whether there is an impending or current natural disaster, epidemic, etc., and determine the probability that user equipment 10 will be allocated a resource block that interferes with GNSS based on the real-world conditions.
[0064] In some implementations, the resource block allocation probability engine 58 may perform any suitable weighting technique on the factors described above to generate the probability that user equipment 10 will be allocated a resource block that interferes with GNSS. That is, the resource block allocation probability engine 58 may impose (e.g., multiply) a weight on each estimated factor and determine the probability by combining (e.g., summing) the weighted factors. In additional or alternative implementations, the resource block allocation probability engine 58 may use artificial intelligence and / or machine learning to determine the allocation probability and / or interference probability. Similarly, and as described above, the processor 12 may determine the likelihood of transmitting cellular signals at increased or maximum transmit power based on signal characteristics. As used herein, machine learning can refer to algorithms and statistical models used by a computer system (e.g., including user equipment 10) to perform a specific task with or without explicit instructions. For example, a machine learning process may generate a mathematical model based on a data sample (referred to as “training data”) to make predictions or decisions without being explicitly programmed to perform a task.
[0065] Based on the inferences to be made, the resource block allocation probability engine 58 and / or processor 12 can implement different forms of machine learning. For example, in some implementations (e.g., when there are specific known examples related to the future predictions or estimates that the machine learning engine might be delegated to produce), the machine learning engine can implement supervised machine learning. In supervised machine learning, a mathematical model of a set of data contains both inputs and desired outputs. This data is called “training data” and may include a set of training examples. Each training example may have one or more inputs and desired outputs, also called supervision signals. In the mathematical model, each training example is represented by an array or vector (sometimes called eigenvectors), and the training data is represented by a matrix. By iteratively optimizing an objective function, a supervised learning algorithm can learn a function that can be used to predict the output associated with new inputs. The optimal function allows the algorithm to correctly determine the output for inputs that are not part of the training data. An algorithm that improves its output or the accuracy of its predictions over time is said to have learned to perform the task.
[0066] Supervised learning algorithms can include classification and regression techniques. Classification algorithms are used when the output is limited to a finite set of values, while regression algorithms are used when the output has a range of values. Similarity learning is a closely related area of supervised machine learning to regression and classification, but its goal is to learn from examples using a similarity function that measures the degree of similarity or correlation between two objects. Similarity learning has applications in ranking, recommendation systems, visual identity tracking, facial verification, and speaker verification.
[0067] Additionally and / or alternatively, in some cases, leveraging unsupervised learning can be advantageous for machine learning engines (e.g., when a particular output type is unknown). Unsupervised learning algorithms take only a set of data containing the input and look for structures in the data, such as groupings or clusters of data points. Thus, the algorithm learns from test data that has not yet been labeled, classified, or categorized. Instead of responding to feedback, unsupervised learning algorithms identify commonalities in the data and react based on the presence or absence of such commonalities in each new piece of data.
[0068] That is, the machine learning engine can perform clustering analysis, which assigns a set of observations into subgroups (called clusters) such that observations within the same cluster are similar according to one or more predetermined criteria, while observations drawn from different clusters are dissimilar. Different clustering techniques make different assumptions about the data structure, which are typically defined by some similarity measure and evaluated, for example, by internal compactness (or similarity between members of the same cluster) and dissimilarity (difference between clusters). In additional or alternative implementations, the machine learning engine can implement other machine learning techniques, such as those based on estimated density and graph connectivity.
[0069] In any case, the resource block allocation probability engine 58 can determine the probability (e.g., allocation probability) that the cellular network 100 can allocate a resource block with a certain frequency to the user equipment 10, where the frequency is a harmonic signal that can interfere with the GNSS signal received by the GNSS receiver 56 when the cellular transmitter 52 uses the resource block to transmit signals. In some embodiments, the resource block allocation probability engine 58 can determine the interference probability that the cellular transmission made by the cellular transmitter 52 can interfere with the GNSS signal based on the allocation probability.
[0070] In decision box 130, resource block allocation probability engine 58 determines whether the probability indicates that interference will occur. For example, resource block allocation probability engine 58 may compare the probability to a threshold probability. The threshold probability can be any suitable value indicating that interference may occur between cellular transmissions and GNSS signals on the allocated resource block, such as 25% or greater, 30% or greater, 40% or greater, 50% or greater, 60% or greater, 70% or greater, 75% or greater, 80% or greater, 85% or greater, etc.
[0071] If the probability indication indicates no interference (e.g., if the probability is less than a threshold probability), then in process block 132, processor 12 causes cellular transmitter 52 to transmit (e.g., receive its indication in process block 111) a signal to base station 102 without performing mitigation procedures (e.g., via LTE bands 13 and / or 14). On the other hand, if the probability indication indicates interference (e.g., if the probability is greater than or equal to a threshold probability), then in process block 134, processor 12 performs one or more mitigation procedures, such as reducing the power to cellular transmitter 52 or preventing cellular transmitter 52 from transmitting signals (e.g., including by deactivating cellular transmitter 52), reducing the gain of GNSS receiver 56 or deactivating the GNSS receiver, and / or activating one or more filters 84 of GNSS receiver 56 (e.g., one or more machine learning filters based on resource block combination) to filter out at least a portion of the transmitted signal from the GNSS signal received at GNSS receiver 56. In this scenario, the processor 12 may transmit signals by, for example, reducing the power of the cellular transmitter 52, reducing the gain of the GNSS receiver 56, deactivating the GNSS receiver, and / or activating one or more filters 84 of the GNSS receiver 56 to filter out at least a portion of the signal from the GNSS signal received at the GNSS receiver 56. In other scenarios, the processor 12 may transmit signals by, for example, preventing or blocking the cellular transmitter 52 from transmitting signals, deactivating the cellular transmitter 52, etc.
[0072] In this manner, method 110 enables processor 12 to selectively enable cellular signal transmission based on the probability, as determined by resource block allocation probability engine 58, that cellular network 100 may allocate resource blocks with a certain frequency to user equipment 10, where the frequency is a harmonic signal that could interfere with GNSS signals received by GNSS receivers when cellular transmitter 52 transmits signals using resource blocks. Therefore, when mitigation procedures can be applied in other ways, the transmission function, performed based on the probability of interference occurring (e.g., as illustrated in process block 132), effectively cancels or otherwise prevents the implementation of mitigation procedures for a period of time.
[0073] Advantageously, the disclosed implementation allows user equipment 10 to save power by selectively activating one or more filters 84 of the GNSS receiver 56 for mitigation purposes, rather than continuously running one or more filters 84. In fact, overall, because the mitigation procedure in question is only executed when the resource block allocation probability engine 58 determines that the cellular network 100 has a high probability (e.g., above a threshold) of allocating a resource block to user equipment 10 with a frequency that could generate harmonic signals that interfere with the GNSS signals received by the GNSS receiver 56 when the cellular transmitter 52 transmits signals using the resource block, a performance gain can be achieved (e.g., compared to running the mitigation procedure every time a transmission is made on LTE bands 13 and / or 14).
[0074] Furthermore, because the mitigation process is not continuously running or at least has a reduced operating frequency and / or operating time, user equipment 10 can receive other signals. For example, the mitigation process filters out signals received by European Union Galileo GNSS. Implementing the disclosed embodiments to avoid continuously executing the mitigation process or at least reducing the operating frequency and / or operating time of the mitigation process can increase the likelihood of receiving Galileo signals or improved signal quality of Galileo signals. Additionally, because the resource block allocation probability engine 58 can be a software-based implementation at least in some embodiments, such embodiments can be selectively activated (e.g., in the case of world events or emergencies such as the E911 incident) to enable continuous operation of the mitigation process in an effort to ensure improved or maximum received GNSS signal quality.
[0075] It should be understood that in some cases, user equipment 10 may receive (e.g., in the next time period or milliseconds) the number of allocatable resource blocks from cellular network 100 or base station 102. However, user equipment 10 may spend time (e.g., approximately several seconds) performing the disclosed mitigation procedure, which may be longer than the time between receiving the indication of the number of allocatable resource blocks and allocating one or more of the allocatable resource blocks to user equipment 10 (e.g., approximately several milliseconds, such as 1 ms). Therefore, performing the mitigation procedure based on the indication of the number of allocatable resource blocks received from cellular network 100 or base station 102 may not be feasible. The disclosed implementation then avoids these infeasible scenarios or reduces their likelihood because, instead of always performing the mitigation procedure (e.g., when transmitting using LTE bands 13 and / or 14), the disclosed implementation makes it possible to selectively perform the mitigation procedure.
[0076] The specific embodiments described above have been illustrated by way of example, and it should be understood that various modifications and alternatives are permissible. It should also be understood that the claims are not intended to limit us to the specific forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the substance and scope of this disclosure.
[0077] The techniques described herein and protected by the claims are referenced and applied to specific examples of physical and practical nature, which significantly improve the technical field and are therefore not abstract, intangible, or purely theoretical. Furthermore, if any claim appended to the end of this specification contains one or more elements designated as "means for [performing] [function]..." or "steps for [performing] [function]...", those elements shall be interpreted in accordance with 35U.SC112(f). However, for any claim containing elements designated in any other manner, those elements shall not be interpreted in accordance with 35U.SC112(f).
[0078] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.
Claims
1. A user equipment comprising: transceiver; Global Navigation Satellite System (GNSS) receiver; and Processing circuit, the processing circuit being configured to: Receive an instruction to transmit a signal using the transceiver. The location is received via the GNSS receiver. Date of receipt and time of day, Based on the location, the date, and the time of day, selectively mitigate interference caused by the transmission of the signal using the transceiver to the signal received by the GNSS receiver, and The transceiver transmits the signal by selectively mitigating the interference.
2. The user equipment of claim 1, wherein the processing circuitry is configured to selectively mitigate the interference by determining the probability that the user equipment is allocated one or more resource blocks associated with a first frequency from the network, the first frequency overlapping with a second frequency used by the GNSS receiver, the probability being based on the location, the date, and the time of day.
3. The user equipment of claim 2, wherein the processing circuitry is configured to receive historical resource block allocations associated with the location, the date, and the time of day, and to selectively mitigate the interference based on the historical resource block allocations.
4. The user equipment of claim 3, wherein the allocation of the historical resource blocks is provided via multiple user equipments.
5. The user equipment of claim 2, wherein the processing circuitry is configured to selectively mitigate the interference by mitigating the interference based on the probability that the user equipment is allocated the one or more resource blocks being greater than or equal to a threshold probability.
6. The user equipment of claim 2, wherein the processing circuitry is configured to selectively mitigate the interference by not mitigating the interference based on the probability that the user equipment is allocated the one or more resource blocks being less than a threshold probability.
7. The user equipment of claim 1, wherein the processing circuitry is configured to cause the transceiver to transmit the signal based on selectively mitigating the interference: causing the transceiver to transmit the signal based on mitigating the interference, and preventing the transceiver from transmitting the signal based on not mitigating the interference.
8. The user equipment of claim 1, wherein the processing circuitry is configured to mitigate the interference by reducing the gain of the GNSS receiver.
9. The user equipment of claim 1, wherein the GNSS receiver is configured to receive a GNSS signal having a GNSS frequency, the GNSS frequency being a multiple of the transmission frequency of the signal.
10. The user equipment according to claim 9, wherein the GNSS frequency is within the GNSS L1 band.
11. The user equipment according to claim 9, wherein the transmission frequency is within Long Term Evolution (LTE) band 13 or Long Term Evolution (LTE) band 14.
12. The user equipment of claim 1, wherein the GNSS receiver includes one or more filters configured to filter out at least a portion of the signal from the GNSS signal, and the processing circuitry is configured to activate the one or more filters to mitigate the interference.
13. A method for transmitting a signal, the method comprising: The user equipment receives an instruction to transmit a signal using the transceiver of the user equipment via its processing circuitry. The location is received via the processing circuit through the GNSS receiver of the user equipment; The date and time of day are received via the processing circuit; The processing circuitry selectively mitigates interference caused by the signal transmitted using the transceiver to the signal received by the GNSS receiver based on the location, the date, and the time of day. as well as The transceiver transmits the signal by selectively mitigating the interference through the processing circuitry.
14. The method of claim 13, comprising: The processing circuitry determines, based on the location, the date, and the time of day, the probability that the user equipment will be allocated one or more resource blocks from the network associated with a first frequency, which overlaps with a second frequency used by the GNSS receiver. as well as The interference is selectively mitigated based on the probability via the processing circuit.
15. The method of claim 14, further comprising mitigating the interference via the processing circuit based on the probability being greater than or equal to a threshold probability.