Methods and apparatus for diagnosing equipment malfunctions

By generating test signals of GNSS signal characteristics and performing signal chain processing in the GNSS receiver, and using a diagnostic module to identify faults, the problem of difficulty in diagnosing GNSS receiver faults during normal operation in existing technologies is solved, achieving efficient fault identification and coverage improvement.

CN114660631BActive Publication Date: 2026-11-17U-BLOX
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202111571588.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-12-22
Filing Date
2021-12-21
Publication Date
2026-11-17
Estimated Expiration
2041-12-21

AI Technical Summary

Technical Problem

Existing technologies struggle to efficiently diagnose faults during normal operation of electronic equipment, especially in GNSS receivers, where it is difficult to simultaneously process real-time GNSS signals and test signals without affecting normal operation.

Method used

A test signal with GNSS signal characteristics is generated and injected. The output signal is processed and monitored through a signal chain. The diagnostic module is used to identify equipment faults, including carrier phase error, group delay drift, carrier tracking error, signal amplitude error, and receiver bandwidth error detection.

Benefits of technology

It enables efficient identification of equipment faults without affecting the normal operation of GNSS receivers, thereby improving diagnostic coverage and reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114660631B_ABST
    Figure CN114660631B_ABST
Patent Text Reader

Abstract

This disclosure relates to methods and apparatus for diagnosing equipment faults. A GNSS receiver with fault detection based on test signals includes: a signal generator configured to generate test signals having characteristics of GNSS signals; one or more amplifiers configured to amplify the test signals; a signal chain configured to receive and process the amplified test signals at input nodes of the signal chain; and a signal processor configured to monitor the test signals by: obtaining one or more output signals of the device at one or more output nodes; recovering the test signals from one or more output signals and determining whether one or more errors have occurred based on parameters of the recovered test signals; identifying an equipment fault based on the determined one or more errors; and generating a notification related to the equipment fault.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Apparatus and methods consistent with this disclosure generally relate to diagnosing faults in receiver equipment. Background Technology

[0002] Reliable operation of electronic devices is a critical aspect of wireless communications, especially when such devices provide essential functionalities such as safety features. For example, high reliability is crucial when a Global Navigation Satellite System (GNSS) receiver is relied upon for applications requiring safety considerations, such as autonomous vehicles, robotic lawnmowers, or autonomous drones. In these cases, it may be necessary to provide means to test or inspect the various hardware and / or software modules of the electronic device to diagnose potential faults or errors during operation. Examples of products where testing for potential faults is important might include electronic products that comply with relevant safety standards, such as IEC 61508 and / or ISO 26262 functional safety standards.

[0003] Typically, fault or error testing of electronic devices can be performed in two main modes. According to the first mode (called foreground testing), the electronic device is briefly taken offline to perform the test. However, in this testing mode, the electronic device is often unable to perform its normal operating functions, which can be problematic for applications requiring a high or near-constant level of availability. Alternatively, in the second mode, the electronic device can be tested in the background during normal operation by adding dedicated diagnostic hardware. The advantage of this testing mode is that it does not interrupt the normal operation of the device during testing. However, because the added hardware is not used during normal operation, the test results may not reflect the actual configuration of the electronic device during use, thus reducing diagnostic coverage.

[0004] Therefore, it is desirable to test electronic devices using the minimum amount of hardware added specifically for diagnostic testing during normal operation. Previous attempts have often encountered difficulties in meeting both normal operation and testing requirements using the same hardware configuration. For example, in a GNSS receiver, the receiver hardware may need to handle both real-time GNSS signals and test signals, which can be challenging to accomplish while maintaining the integrity of both normal and diagnostic operations. Summary of the Invention

[0005] According to this disclosure, a method for diagnosing equipment faults is provided, the method comprising the steps of: generating a test signal, the test signal including characteristics of a GNSS signal; amplifying the test signal; injecting the test signal into the equipment at an input node after amplification; processing the test signal by the signal chain of the equipment; monitoring the test signal by the following steps: obtaining one or more output signals of the equipment at one or more output nodes; recovering the test signal from the one or more output signals; determining whether one or more errors exist in the test signal based on parameters of the recovered test signal; identifying equipment faults based on the determined one or more errors; and generating an indication related to the equipment fault.

[0006] According to this disclosure, a GNSS receiver with fault detection based on a test signal is also provided, the GNSS receiver comprising: a signal generator configured to generate a test signal having characteristics of a GNSS signal; one or more amplifiers configured to amplify the test signal; a signal chain configured to receive and process the amplified test signal at an input node of the signal chain; and a processor configured to monitor the test signal by: obtaining one or more output signals of the device at one or more output nodes; recovering the test signal from the one or more output signals; determining whether one or more errors have occurred based on parameters of the recovered test signal; identifying a device fault based on the determined one or more errors; and generating a notification related to the device fault. Attached Figure Description

[0007] Figure 1 This is a schematic diagram illustrating an exemplary GNSS receiver device with integrated diagnostic testing consistent with this disclosure.

[0008] Figure 2 This is a schematic diagram illustrating a diagnostic module of an exemplary GNSS receiver device consistent with this disclosure.

[0009] Figure 3 A flowchart illustrating an exemplary diagnostic test operation for a GNSS receiver device consistent with this disclosure is provided. Detailed Implementation

[0010] Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the drawings, and unless otherwise stated, the same numerals in the different drawings denote the same or similar elements. The implementations set forth in the following disclosure are consistent with aspects of the invention as set forth in the appended claims.

[0011] According to some embodiments of this disclosure, a GNSS receiver with fault detection based on test signals is provided. The GNSS receiver can be an electronic device capable of receiving various types of radio frequency (RF) signals, including GNSS signals. Examples of GNSS signals may include, but are not limited to, RF signals from the Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), BeiDou Navigation Satellite System (BDS), Galileo system, or other such satellite-based navigation systems. Those skilled in the art will understand that a GNSS signal can be any electromagnetic signal suitable for use in a GNSS system in terms of power, frequency band, and other characteristics.

[0012] A GNSS receiver comprises a signal chain. A signal chain refers to one or more hardware or software modules of a GNSS receiver that receive, convert, mix, or otherwise process GNSS signals. For example, such as... Figure 1 As shown, device 100 is an example of a GNSS receiver. The signal chain of exemplary device 100 includes an analog module 101, an intermediate frequency preprocessing (IFPP) module 103, and a tracking engine 105. In some embodiments, the signal chain of device 100 may optionally include an antenna 102, an external low-noise amplifier (LNA) 104, and / or a surface acoustic wave (SAW) filter 106 coupled to the input of the analog module 101. In some embodiments, the signal chain of device 100 may also optionally include a memory 138 coupled to the tracking engine 105. In some embodiments, memory 138 stores output data of the tracking engine 105. In some embodiments, memory 138 may also store other data values. Those skilled in the art will understand that exemplary device 100 is merely illustrative, and components may be added, removed, modified, or rearranged to suit various design needs and objectives without departing from this disclosure.

[0013] In some embodiments, analog module 101 is part of device 100. Analog module 101 includes components considered "analog" and functions to receive, amplify, and down-convert GNSS signals from an RF carrier frequency to an intermediate frequency (IF). Analog module 101 includes an LNA 108, a mixer 110, a signal adder 112, a low-pass filter 114, and an RF programmable (or variable) gain amplifier (PGA) 116. The GNSS signal may be received by antenna 102, amplified by an external LNA 104, and filtered by a SAW filter 106 before being coupled to analog module 101. The GNSS signal received by antenna 102 is referred to hereinafter as a "real-time" GNSS signal. Real-time GNSS signals can be distinguished from test signals generated internally by device 100. Examples of real-time GNSS signals may include CDMA or OFDM signals. The real-time GNSS signal is amplified by LNA 108 and then mixed with a local oscillator signal in mixer 110. The local oscillator signal can be generated by the local oscillator ( Figure 1 (Not depicted in the text) is generated. The mixing operation down-converts the real-time GNSS signal from the RF carrier frequency to the intermediate frequency. In some embodiments, mixer 110 may be a quadrature (I / Q) mixer, and the down-converted real-time GNSS signal includes an in-phase component (I) and a quadrature phase component (Q). Figure 1 In this context, a signal represented by a double line indicates a signal with I / Q components.

[0014] At signal adder 112, a test signal is added to the real-time GNSS signal to create a mixed signal. The test signal may be amplified before being injected into the signal chain via signal adder 112. The mixed signal is then filtered by low-pass filter 114 and amplified by RF PGA 116. In some embodiments, RF PGA 116 may be controlled by commands or signals from RF gain control unit 124, which will be discussed in detail below. In some alternative embodiments, signal adder 112 may be located before mixer 110, thereby allowing the test signal to be added to the real-time GNSS signal before downconversion at mixer 110.

[0015] The analog module 101 also includes a test signal generator 128 and a test signal amplifier 130. The test signal generator 128 may be one or more electronic components that generate waveforms, patterns, functions, and / or other such electronic signals. The test signal generator 128 is configured to generate test signals. In some embodiments, the test signal is an electrical signal designed to produce a known result after being processed by components of device 100. For diagnostic purposes, the test signal may have one or more parameters and may be compared to some expected values, said one or more parameters having values ​​that can be monitored or measured. These parameters may include phase, timing, amplitude, or information contained therein, such as pseudo-random noise (PRN) codes. In some embodiments, the test signal may be designed to mimic or share some characteristics of typical GNSS signals, such as frequency, bandwidth, coding, modulation, and / or other characteristics relevant to diagnostic purposes. However, in order to distinguish the test signal from the real-time GNSS signal during operation, the test signal may be configured to differ from the real-time GNSS signal in one or more of the PRN code, bandwidth, amplitude, and / or center frequency. In some implementations, the test signal may also include an in-phase component (I) and a quadrature phase component (Q).

[0016] Test signal amplifier 130 is coupled to receive the test signal generated by test signal generator 128 and is configured to amplify the test signal. In some embodiments, test signal amplifier 130 may be a programmable / variable gain amplifier controlled to amplify the test signal to a desired amplitude. In some embodiments, test signal amplifier 130 is controlled to provide the amplitude of the test signal based on the amplitude of the real-time GNSS signal, such that the power spectral density of the test signal is 16 dB or lower than the power spectral density of noise at the injection node. For example, the amplitude of the test signal may be significantly smaller than the amplitude of the real-time GNSS signal. In some embodiments, test signal amplifier 130 may be controlled by commands or signals from test signal gain control unit 126, which will be discussed in more detail below. By adjusting the amplitude of the test signal based on the amplitude of the real-time GNSS signal, device 100 can thus prevent the test signal from interfering with the detection of the real-time GNSS signal when the signal reception is weak. Conversely, it may be necessary to increase the amplitude of the test signal, for example, when the signal strength of the received GNSS signal is high.

[0017] The IFPP module 103 includes hardware / software modules for demodulating a signal into readable data bits. In some embodiments, the IFPP module 103 includes an analog-to-digital converter (ADC) 118, a high-pass filter 120, and an intermediate frequency channel (IFCH) 122. The ADC 118 is coupled to receive a mixed signal from the RF PGA 116 and convert the received mixed signal from analog to digital form. The high-pass filter 120 is coupled to the output of the ADC 118 and filters the digitized mixed signal received by the IFCH 122. The IFCH 122 includes components configured to demodulate, decode, or otherwise process the mixed signal into data bits for further processing in different channels. For example, the IFCH 122 may include components such as a downconverter, a bandpass filter, automatic gain control (AGC), or parts thereof, and / or circuitry known to those skilled in the art for signal processing of the intermediate frequency channel.

[0018] The IFPP module 103 also includes an RF gain control unit 124 and a test signal gain control unit 126. The RF gain control unit 124 is coupled to receive the mixed signal from the ADC 118 and output commands / signals to the RF PGA 116 and the test signal gain control unit 126. In some embodiments, the RF gain control unit 124 may be programmed to compare the amplitude of the received mixed signal with a predetermined amplitude value and output commands / signals to increase or decrease the gain level of the RF PGA 116 such that the amplitude of the received mixed signal matches the predetermined amplitude value. The test signal gain control unit 126 is configured to receive commands / signals from the RF gain control unit 124 and determine the gain level of the test signal amplifier 130. For example, the test signal gain control unit 126 may be programmed to perform calculations based on the amplitude of the mixed signal from the RF gain control unit 124 and any increase or decrease in the gain level of the test signal amplifier 130. In some embodiments, the RF gain control unit 124 and / or the test signal gain control unit 126 may include programmable circuitry, such as a microprocessor, microcontroller, logic gate array, FPGA, and / or other programmable integrated circuits. In some embodiments, the RF gain control unit 124 and / or the test signal gain control unit 126 may be implemented as a module or software component of a processor, such as a digital signal processor or central processing unit.

[0019] Tracking engine 105 includes hardware / software modules that maintain a tracking loop using the received real-time GNSS signal. A tracking loop is a feedback loop used by device 100 to estimate parameters of the real-time GNSS signal in order to obtain an accurate value of the distance between device 100 and the satellite transmitting the real-time GNSS signal. Examples of tracking loop parameters include, but are not limited to, carrier phase shift, Doppler shift, and / or code delay. Tracking engine 105 includes a mixer 132, a correlation-and-dump unit 134, a test signal PRN code generator 136, and an oscillator 140.

[0020] In some embodiments, mixer 132 mixes the mixed signal received from IFCH 122 with an oscillator signal generated by oscillator 140. In some embodiments, oscillator 140 may include a carrier signal generator driven by a numerically controlled oscillator (NCO). Oscillator 140 generates an oscillator signal having phase and frequency, which is configured to correct the carrier phase shift of the real-time GNSS signal contained in the mixed signal at mixer 132. Oscillator 140 may generate the oscillator signal based on feedback control signals. For example, the carrier signal generator of oscillator 140 may be controlled by a feedback frequency control signal, and the NCO of oscillator 140 may be controlled by a feedback phase control signal. The feedback frequency and phase control signals may be generated by one or more diagnostic modules, details of which are referred to below. Figure 2 The following description is provided. In some implementations, the test signal PRN code generator 136 generates pseudo-random numbers (PRNs) for the test signal.

[0021] The correlation and dump unit 134 performs correlation between the mixed signal and the local copy signal and the test signal itself. The local copy signal is the same signal transmitted by the satellite (a real-time GNSS signal version that is not distorted by propagation or signal processing). In some embodiments, the correlation and dump unit 134 may be a multiple correlator (not depicted), and in t early t prompt and t late The timing of the mixing signal is correlated with the local copy signal. t prompt This refers to the time it takes for the local copy signal to align with the real-time GNSS signal, t. early It refers to t prompt The previous time, and t late It refers to t prompt The time that followed. Related to dump unit 134 is still t early t prompt and t late The timing is used to correlate the mixing signal with the test signal. The correlation and the output of the dump unit 134 can be stored in the memory 138 for later processing.

[0022] Figure 2 This is a schematic diagram illustrating a diagnostic module of an exemplary GNSS receiver device consistent with this disclosure. The correlation and dump unit 134 generates data related to t... early t prompt and t late The corresponding early correlation signal (early signal 401), instantaneous correlation signal (instantaneous signal 402), and late correlation signal (late signal 403) are also defined. In some implementations, early signal 401, instantaneous signal 402, and late signal 403 can be generated on a millisecond-level basis, for example, one sample per millisecond. Early signal 401, instantaneous signal 402, and late signal 403 comprise both of the following: 1) a correlation signal between a real-time GNSS signal and a local copy signal, and 2) a test signal and itself at a corresponding time delay t. early t prompt and t late Related signals.

[0023] Since the test signal does not undergo any changes, distortions, and / or delays due to propagation, any deviations from the test signal will be attributed to the signal processing of device 100. These deviations can be obtained through previous tests. For example, previous tests of device 100 can generate nominal values ​​of the autocorrelation of the test signal, and these nominal values ​​can be stored in a memory device (e.g., memory 138). For example, the nominal values ​​of the test signal may include those used for delay t. early t prompt and t late The nominal values ​​of the early signal 401, the instantaneous signal 402, and the late signal 403 of the test signal are specified. In some embodiments, the nominal value of the carrier phase of the test signal may also be stored in the memory 138 of the device 100.

[0024] According to some implementations, the diagnostic module includes a carrier phase error detector 201, a group delay drift detector 203, a carrier tracking error detector 205, a signal amplitude error detector 207, and a receiver bandwidth (BW) error detector 209. In some implementations, one or more of these diagnostic modules may be software modules (e.g., code, programs, functions, logic) executing in a microprocessor, microcontroller, logic gate array, FPGA, and / or other programmable integrated circuits.

[0025] In some embodiments, the output of the correlation and dump unit 134 is connected to the first integrator 202 and the second integrator 204. Alternatively, the output of the correlation and dump unit 134 may be stored in a memory 138, which in turn provides the stored output to the first integrator 202 and the second integrator 204. The first integrator 202 and the second integrator 204 are integration units referred to as "integration and dump" units, which are configured to accumulate and average the input over a time period, then output the accumulated value and reset the time period. In some embodiments, the first integrator 202 may be a coherent integrator with a period of 10 ms, and the second integrator 204 may be an incoherent integrator with a period of 100 ms. The first integrator 202 integrates the early signal 401, the immediate signal 402, and the late signal 403 over a period of 10 ms, and the second integrator 204 integrates the output of the first integrator 202 over a period of 100 ms. In some embodiments, the first integrator 202 and the second integrator 204 can be implemented as software modules executed by the processing unit. In other embodiments, the first integrator and the second integrator can be implemented as electronic circuits in hardware.

[0026] The carrier phase error detector 201 determines information about the carrier phase of the real-time GNSS signal and provides a correction value to keep the local copy signal as "matched" as possible to the real-time GNSS signal in the tracking loop. The carrier phase error detector 201 also determines whether the carrier phase of the test signal matches the nominal carrier phase value. The carrier phase error detector 201 includes a carrier phase discriminator 206, a comparator 208, and a phase-locked loop (PLL) 210. The carrier phase discriminator 206 is coupled to receive a 10 ms integral of the instantaneous signal 402 for both the real-time GNSS signal and the test signal and provides the carrier phase of the instantaneous signal 402 as an output. The PLL 210 uses the carrier phase of the real-time GNSS signal generated by the carrier phase discriminator 206 to calculate the feedback frequency and phase control signal to control the connection to... Figure 1 The mixer 132 has an oscillator 140. Comparator 208 uses the carrier phase of a test signal generated by carrier phase discriminator 206 to compare with the nominal carrier phase. The offset between the carrier phase of the test signal and the nominal carrier phase can produce a carrier phase error; if the carrier phase error exceeds a threshold, this can indicate a device malfunction.

[0027] Group delay drift detector 203 determines whether there is an offset in the group delay of the test signal caused by device 100. Group delay refers to the delay of the overall envelope of the signal, and the offset in the group delay may occur due to the nonlinear frequency response of different components to the frequency spectrum contained in the signal. The group delay module includes a drift calculator 212 and a comparator and error counter 214. The drift calculator 212 is connected to receive the 100ms integral values ​​of the early signal 401 and the late signal 403 from the second integrator 204 and calculates the drift value given by equation (1):

[0028]

[0029] In equation (1), E represents the 100ms integral value of the test signal component of the early signal 401, and L represents the 100ms integral value of the test signal component of the late signal 403. The drift value obtained by the comparator and error counter 214 is compared with the nominal drift value. Since the test signal is artificially generated within the device 100, its nominal drift value can be calculated based on the nominal value stored in the memory 138 of the device 100. In some embodiments, the comparator and error counter 214 can accumulate the difference between the calculated drift value and the nominal drift value over a time period (e.g., a multiple of 100ms) to generate a group delay error. In some embodiments, if the group delay error exceeds a threshold, the group delay module comparator and error counter 214 indicates a device failure. The threshold can be predetermined and stored in the memory 138 of the device 100.

[0030] The carrier tracking error detector 205 determines information about the code delay of the real-time GNSS signal and provides correction to the correlation and dump unit 134 to maintain the local copy signal in the tracking loop with the real-time GNSS signal. The carrier tracking error detector 205 includes a low dynamic delay locked loop (DLL) 216, which is coupled to receive 10ms integral values ​​of the early signal 401, the immediate signal 402, and the late signal 403, and determines the code delay information of the real-time GNSS signal based on these received values. The DLL 216 uses the code delay information to provide feedback control to the correlation and dump unit 134 to maintain the tracking loop with the real-time GNSS signal. The DLL 216 also determines the lock-in state of the test signal tracking loop based on the integral values ​​of the early signal 401, the immediate signal 402, and the late signal 403. For example, since the test signal is generated within device 100, it should not have any delay. Therefore, under normal operating conditions, the tracking loop of the test signal should always be locked (i.e., always tracked). If the lockout is lost for a threshold amount of time as determined by timer 218, carrier tracking error detector 205 may indicate an error in the test signal generator or some other non-specific error in a component of device 100.

[0031] Signal amplitude error detector 207 determines whether the amplitude of the autocorrelation test signal is within the design range. The signal amplitude error detector includes a comparator and error counter 220, which are connected to receive the test signal component of the instantaneous signal 402 after a 100 ms integral. The comparator and error counter 220 compares the amplitude of the test signal component of the instantaneous signal 402 with the nominal amplitude and outputs an amplitude error based on the difference. If the amplitude error exceeds a threshold, the signal amplitude error detector indicates a possible device failure in one or more amplifiers (e.g., RF PGA 116), or some other failure in the analog module 101.

[0032] The receiver bandwidth (BW) error detector 209 determines whether the bandwidth of the test signal is within the design range. In some embodiments, the receiver BW error detector 209 includes a ratio calculator 222, which is connected to receive the test signal components of the early signal 401, the instantaneous signal 402, and the late signal 403 as 100ms integrals. The ratio calculator 222 outputs the ratio of the instantaneous signal 402 to the sum of the early signal 401 and the late signal 403, as given by equation (2):

[0033]

[0034] In equation (2), E represents the test signal component of the 100ms integral value of the early signal 401, L represents the test signal component of the 100ms integral value of the late signal 403, and P represents the test signal component of the 100ms integral value of the instantaneous signal 402. A comparator and error counter 224 are connected to receive the ratio value calculated by the ratio calculator 222 and compare it with the nominal ratio value derived from the nominal values ​​of E, L, and P. The difference between the nominal ratio value and the calculated ratio value can be accumulated and averaged by the comparator and error counter 224, and a device malfunction can be indicated when the accumulated difference exceeds a threshold.

[0035] In some implementations, a false alarm refers to a situation where one or more of the diagnostic modules 201 to 209 indicate an error or anomaly even in the absence of a hardware failure. For example, a false alarm may occur under interference or adverse operating conditions that cause large fluctuations in the real-time GNSS signal, which can affect the autocorrelation results of the test signal at the dump unit 134. In some implementations, the frequency of false alarms (i.e., the false alarm rate) can be minimized to increase the maximum availability of device 100 for normal operation. For example, the thresholds described above with respect to diagnostic modules 201 to 209 can be selected based on a trade-off between the false alarm rate and sensitivity, within the Error Tolerance Time Interval (FTTI) requirement. For example, the thresholds can be determined based on theoretical simulations or actual tests of device 100 and real-time GNSS signals for different scenarios and operating conditions (e.g., driving a car in an aesthetically pleasing environment, a city center, a tunnel, interference, etc.).

[0036] Figure 3 A flowchart is depicted for a process 600 for diagnostic test operations of a GNSS receiver device such as device 100, consistent with the disclosed embodiments.

[0037] In step 602, the GNSS device receives real-time GNSS signals. (Return to reference) Figure 1 Device 100 receives real-time GNSS signals via antenna 102. The real-time GNSS signals are amplified by LNA 104 and filtered by SAW 106 before being connected to the input of analog module 101. In some embodiments, one or more of antenna 102, LNA 104b, and / or SAW 106 may optionally be detachable or separable external components of device 100. In some embodiments, step 602 may be optional. For example, even when no real-time GNSS signal is received, process 600 can still be performed in device 100 to monitor for faults in components of device 100. For example, even in the absence of a real-time GNSS signal, device 100 can still process test signals as described above.

[0038] In step 604, a test signal is generated in a GNSS device (such as device 100). For example, returning to the reference... Figure 1Test signal generator 128 can generate a test signal. In some embodiments, step 604 can occur simultaneously with step 602. The generated test signal can be a signal simulating a characteristic of a series of properties present in a real-time GNSS signal, so that various components of device 100 can be monitored by monitoring the test signal at the output of device 100. For example, the test signal can be a CDMA signal or an OFDM signal, depending on which type of real-time GNSS signal device 100 is designed to receive. In some embodiments, the test signal can be modulated by a rectangular pulse signal or a sinusoidal signal. In some embodiments, the PRN code attribute of the test signal can be controlled by a hardware or software module (e.g., test signal PRN code generator 136). To provide wide-range monitoring, the test signal can be a broadband signal or a single-band signal. Broadband, as used herein, refers to a frequency range that can cover multiple single-band frequencies. Single-band, as used herein, refers to a frequency range with a narrower bandwidth than broadband. For example, a real-time GNSS signal may occupy a single-signal frequency band, while different real-time GNSS signals may occupy different single-signal frequency bands. Therefore, the exemplary broadband test signal can be designed to cover all single-signal frequency bands of the real-time GNSS signal that the device 100 is designed to receive. In some alternative embodiments, the test signal may include a plurality of single-band signals, each of which covers a single frequency band of the real-time GNSS signal. In some embodiments, the real-time GNSS signal and the test signal differ in at least one of the following: PRN code, bandwidth, amplitude, or center frequency.

[0039] In step 606, one or more amplifiers amplify the test signal. (Return to reference) Figure 1 Test signal amplifier 130 amplifies the test signal generated by test signal generator 128. Test signal amplifier 130 may be a programmable / variable gain amplifier, with its gain value controlled by a hardware or software module. In some embodiments, the gain of test signal amplifier 130 is controlled by test signal gain control unit 126. Test signal gain control unit 126 determines the amplitude of the real-time GNSS signal based on the gain of RF PGA 116 and thus adjusts the gain of test signal amplifier 130 so that the amplitude of the test signal is less than the amplitude of the real-time GNSS signal. Therefore, the amplitude of the test signal is controlled to minimize interference with the real-time GNSS signal. For example, a lower amplitude and greater bandwidth for the test signal compared to the real-time GNSS signal will result in a lower power spectral density compared to any received real-time GNSS signal. In some embodiments, device 100 includes at least a first amplifier (e.g., RF PGA 116) for amplifying the real-time GNSS signal and / or the test signal and a second amplifier (e.g., test signal amplifier 130) for amplifying the test signal.

[0040] In step 608, an amplified test signal is injected into the GNSS device at the input node. For example, such as... Figure 1 As shown, the test signal is "injected" into the signal chain of device 100 at signal adder 112. Injection, as used here, refers to connecting a signal, such as a test signal, to a component of device 100. For example, when a real-time GNSS signal is present, signal adder 112 combines the real-time GNSS signal and the test signal to create a mixed signal. In some embodiments, signal adder 112, and thus the input node, is placed in a down-conversion stage. For example, as... Figure 1 As shown, down-conversion of the real-time GNSS signal occurs at mixer 110, and signal adder 112 is located after mixer 110 in the signal chain. In some alternative embodiments (not shown), signal adder 112 may be located before mixer 110 in the signal chain, such that the injection of the test signal occurs before down-conversion. In some embodiments, the test signal may be continuously added to the real-time GNSS signal. Alternatively, the test signal may be added to the real-time GNSS signal at predetermined time intervals.

[0041] In step 610, device 100 processes the test signal. Following the injection in step 608, the test signal is processed by device 100 along with the real-time GNSS signal, and the autocorrelation of the test signal is generated by correlation and dump unit 134. In some embodiments, device 100 processes the test signal in a manner similar to that of the real-time GNSS signal. In some embodiments, device 100 may process the test signal differently. For example, when processing a real-time GNSS signal, device 100 may first perform an acquisition step to introduce the real-time GNSS signal into a tracking loop with a local copy signal. However, device 100 may skip the acquisition step for the test signal and can immediately establish a tracking loop because device 100 always knows the characteristics of the test signal (e.g., frequency, phase, etc.).

[0042] Return to reference Figure 2Each of the early signal 401, instantaneous signal 402, and late signal 403 generated by the correlation and dump unit 134 may include a test signal component and a real-time GNSS signal component. The test signal components of the early signal 401, instantaneous signal 402, and / or late signal 403 are provided to multiple diagnostic modules, including a carrier phase error detector 201, a group delay drift detector 203, a carrier tracking error detector 205, a signal amplitude error detector 207, and a receiver BW error detector 209. In some embodiments, the test signal components of the early signal 401, instantaneous signal 402, and / or late signal 403 are processed by one or more integrators, such as a first integrator 202 and a second integrator 204. In some embodiments, the test signal components of the early signal 401, instantaneous signal 402, and / or late signal 403 generated by the correlation and dump unit 134 can be retrieved from memory 138.

[0043] In steps 612a to 612e, device 100 monitors the processed test signal. Device 100 can perform steps 612a to 612e simultaneously. As previously mentioned... Figure 2 As described, the nominal autocorrelation value of the test signal after processing by device 100 can be obtained from previous tests. Therefore, the output of the correlation and dump unit 134 for the test signal is monitored and compared with these nominal values ​​stored in the memory 138 of device 100 (e.g., memory 138). When the output of the correlation and dump unit 134 does not match these nominal values, some device malfunction can be assumed. Different parameters of the test signal can be monitored by multiple diagnostic modules including carrier phase error detector 201, group drift error detector 203, carrier tracking error detector 205, signal amplitude error detector 207, and receiver BW error detector 209.

[0044] In step 612a, the carrier phase is monitored. Figure 2 In the example depicted, the carrier phase error detector 201 includes a carrier phase discriminator 206, which is coupled to receive an instantaneous signal 402. After processing by device 100, the carrier phase discriminator 206 obtains the carrier phase of the test signal, and the comparator 208 compares this result with a nominal carrier phase value. A difference between the obtained carrier phase and the nominal carrier phase exceeding a threshold can indicate an anomaly. In some embodiments, an anomaly in the carrier phase of the test signal is indicated as "yes" in step 614. Figure 2 In the example, anomalies in the carrier phase may indicate drift or clock errors in the fast group delay.

[0045] In step 612b, the lock status is monitored. (By...) Figure 2In the example depicted, carrier tracking error detector 205 includes DLL 216, which is coupled to receive early signal 401, instantaneous signal 402, and late signal 403. DLL 216 determines whether a tracking loop for the test signal is maintained. In some embodiments, a predefined relationship exists between the amplitudes of the test signal components of early signal 401, instantaneous signal 402, and late signal 403. For example, in a locked tracking loop, the amplitude of the test signal component of early signal 401 should be close to the amplitude of the test signal component of late signal 403, and both amplitudes should be much smaller than the amplitude of the test signal component of instantaneous signal 402. If DLL 216 determines that the predefined relationship is not met, the tracking loop may be lost. Under normal operating conditions, the tracking loop for the test signal should always be locked (i.e., always tracked). Loss of lock can be an anomaly indicating an unspecified error in device 100 or test signal generator 128. In some embodiments, an anomaly in the locked state of the test signal tracking loop indicates "yes" in step 614.

[0046] In step 612c, group delay drift is monitored. Figure 2 In the example depicted, the group delay drift detector 203 includes a drift calculator 212 coupled to receive the early signal 401 and the late signal 403. The drift calculator 212 determines the drift value based on the above equation (1). A comparator and error counter 214 compares the calculated drift value with a nominal drift value calculated using the nominal values ​​of the early signal 401 and the late signal 403. The comparator and error counter 214 can also accumulate the difference between the calculated drift value and the nominal drift. In some embodiments, when the accumulated difference exceeds a threshold, the group delay drift detector 203 indicates an anomaly in the group delay of the test signal tracking loop and indicates "yes" in step 614.

[0047] In step 612d, the amplitude of the autocorrelation test signal is monitored. Figure 2 In the example depicted, the signal amplitude error detector 207 includes a comparator and error counter 220 coupled to receive the instantaneous signal 402. The comparator and error counter 220 compares the amplitude of the test signal component of the instantaneous signal 402 with a nominal amplitude. The comparator and error counter 220 can also accumulate the difference between the acquired amplitude value and the nominal amplitude. In some embodiments, when the accumulated difference exceeds a threshold, the signal amplitude error detector 207 indicates an anomaly in the amplitude of the autocorrelation test signal and can indicate "yes" in step 614.

[0048] In step 612e, the bandwidth of the test signal is monitored. Figure 2In the example depicted, the receiver BW error detector 209 includes a ratio calculator 222 coupled to receive the test signal components of the early signal 401, the instantaneous signal 402, and the late signal 403. The ratio calculator 222 determines a ratio value given by equation (2). The comparator and error counter 224 compares this calculated ratio value with a nominal ratio value calculated using the nominal values ​​of the early signal 401, the instantaneous signal 402, and the late signal 403. The comparator and error counter 224 may also sum the calculated ratio value and the nominal drift value. In some embodiments, when the summed difference exceeds a threshold, the receiver BW error detector 209 may indicate an anomaly in the bandwidth of the test signal and indicate "yes" in step 614.

[0049] In step 614, if the result is "yes", process 600 proceeds to step 616, which indicates a possible fault in device 100 corresponding to one or more specific diagnostic modules indicating an anomaly. If step 614 is "no", process 600 returns to step 610, and device 100 continues processing test signals.

[0050] In step 616, device 100 provides an error notification. This notification corresponds to an anomaly determined by one or more diagnostic modules. Figure 3 In the example, step 616 provides notification of device failures related to: fast group delay drift and / or clock, loss of lockout state for the test signal tracking loop, slow group delay drift, amplifier or I / Q stage failure, and / or bandwidth determined based on steps 612a through 612e. In some implementations, step 616 may also put device 100 into a safe mode. A safe mode is the default state of an electronic device when reliable operation cannot be guaranteed. For example, in a safe mode, device 100 may cease operation to avoid output errors. Alternatively, device 100 may continue operation in a safe mode to maintain availability required by different applications. For example, if the device is operating in an adverse environment prone to false alarms, device shutdown may be undesirable or unnecessary.

[0051] The memory disclosed herein can be a tangible device capable of storing instructions for use by an instruction execution device (such as the processor described above). For example, the memory can be, but is not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of memory includes the following: portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), portable optical disc read-only memory (CD-ROM), digital versatile disk (DVD), memory sticks, floppy disks, mechanical encoding devices (such as punch cards or raised structures in grooves on which instructions are recorded), and any suitable combination of the foregoing.

[0052] The computer-readable program instructions disclosed herein (e.g., any processor-executable software module or algorithm) may be assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​and conventional procedural programming languages. The computer-readable program instructions may execute entirely on a computing device as a standalone software package, or may execute partly on a first computing device and partly on a second computing device located remotely from the first computing device. In the latter case, the second remote computing device may be connected to the first computing device via any type of network, including local area networks (LANs) or wide area networks (WANs).

[0053] The flowcharts and block diagrams in the figures illustrate examples of the architecture, functionality, and operation of possible implementations of systems, methods, and apparatuses according to various embodiments. It should be noted that in some alternative embodiments, the functions marked in the blocks may not appear in the order indicated in the figures. For example, depending on the functions involved, two consecutively shown blocks may actually be executed substantially simultaneously, or sometimes these blocks may be executed in reverse order.

[0054] It should be understood that the described implementations are not mutually exclusive, and elements, components, materials, or steps described in conjunction with an example implementation may be combined with or removed from other implementations in a suitable manner to achieve desired design goals.

[0055] The terms "some implementations" or "some exemplary implementations" as used herein refer to specific features, structures, or characteristics described in connection with the implementation that may be included in at least one implementation. The phrases "one implementation," "some implementations," "another implementation," or "an alternative implementation" appearing throughout this disclosure do not necessarily all refer to the same implementation, nor are they necessarily single or alternative implementations that are mutually exclusive with other implementations.

[0056] It should be understood that the steps of the example methods described herein do not necessarily need to be performed in the order described, and the order of the steps in these methods should be understood as merely illustrative. For example, depending on the functionality involved, two consecutively shown boxes may actually be executed substantially simultaneously, or sometimes these boxes may be executed in reverse order. Similarly, in methods consistent with various implementations, additional steps may be included, and certain steps may be omitted or combined.

[0057] As used herein, the word “exemplary” is used to mean as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects or designs. Rather, the use of the word is intended to present the concept in a specific manner.

[0058] As used in this disclosure, unless otherwise specifically stated, the term "or" covers all possible combinations except those that are not feasible. For example, if a database is stated to include A or B, then unless otherwise expressly stated or not feasible, the database may include A, or B, or A and B. As a second example, if a database is stated to include A, B, or C, then unless otherwise expressly stated or not feasible, the database may include A, or B, or C, or A and B, or A and C, or B and C, or A and B and C.

[0059] Furthermore, unless otherwise stated or clearly indicated from the context, the articles “a” and “an” used in this disclosure and the appended claims should generally be interpreted as meaning “one or more”.

[0060] Unless otherwise explicitly stated, all numerical values ​​and ranges should be interpreted as approximations, just as the words “approximately” or “about” precede the value or range.

[0061] Although the elements (if any) in the appended method claims are set in a particular order, these elements are not necessarily intended to be limited to being implemented in that particular order unless the statement of the claims otherwise implies a particular order for implementing some or all of these elements.

[0062] It should be understood that, for clarity, certain features of this disclosure described in the context of individual embodiments may also be provided in combination in a single embodiment. Conversely, for brevity, various features of the specification described in the context of a single embodiment may also be provided individually or in any suitable sub-combination or appropriately in any other described embodiment of the specification. Certain features described in the context of various embodiments are not essential features of those embodiments, unless so stated.

[0063] It will be further understood that those skilled in the art can make various modifications, substitutions, and variations to the details, materials, and arrangements of the components described and shown for the purpose of explaining the nature of the described embodiments without departing from the scope. Therefore, the appended claims include all such substitutions, modifications, and variations that fall within the scope of the claims.

Claims

1. A method for diagnosing equipment faults, the method comprising the following steps: Generate a test signal, the test signal including the characteristics of a GNSS signal; Amplify the test signal; After amplification, the test signal is injected into the device at the input node; The test signal is processed by the signal chain of the device; The test signal is monitored using the following steps: One or more output signals of the device are obtained at one or more output nodes; Recover the test signal from one or more of the output signals; as well as The presence of one or more errors in the test signal is determined based on the parameters of the recovered test signal. Equipment faults are identified based on one or more determined errors; as well as Generate indications related to the equipment malfunction. The steps further include: The receiving unit of the device receives a real-time signal, which is a GNSS signal. The method further includes: A first amplifier, configured to amplify the amplitude of the GNSS signal; and A second amplifier is configured to amplify the amplitude of the test signal based on the amplitude of the GNSS signal.

2. The method according to claim 1, wherein the step further comprises: The GNSS signal is processed by the signal chain, wherein the one or more output signals include the GNSS signal and the test signal.

3. The method according to claim 1, wherein, The test signal is either a CDMA signal or an OFDM signal.

4. The method according to claim 1, wherein, The test signal is one of the following: Multiple single-band signals; and Wideband signals that span multiple signal frequency bands.

5. The method according to claim 1, wherein, The input node is located after the downconversion stage in the signal chain.

6. The method according to claim 1, wherein, The step of injecting the test signal includes continuously injecting the test signal.

7. The method according to claim 1, wherein, The step of injecting the test signal includes injecting the test signal at a predetermined test interval.

8. The method according to claim 1, wherein, The identified one or more errors include an anomaly in at least one of carrier lock state, code lock state, group delay drift, signal bandwidth, and amplitude.

9. The method according to claim 1, wherein, The parameters of the recovered test signal include at least one of phase, timing, amplitude, and information contained in the recovered test signal.

10. The method according to claim 2, wherein, The GNSS signal and the test signal differ in at least one of the following: PRN code, bandwidth, amplitude, and center frequency.

11. A GNSS receiver with fault detection based on test signals, the GNSS receiver comprising: A signal generator configured to generate a test signal having characteristics of a GNSS signal; One or more amplifiers, wherein the one or more amplifiers are configured to amplify the test signal; A signal chain configured to receive and process an amplified test signal at its input node; as well as Processor, the processor being configured to: The test signal is monitored using the following steps: One or more output signals of the device are obtained at one or more output nodes; Recover the test signal from one or more of the output signals; as well as The parameters of the recovered test signal are used to determine whether one or more errors have occurred; Equipment faults are identified based on one or more determined errors; as well as Generate a notification related to the device malfunction. The receiver further includes: RF front-end system, the RF front-end system being configured to receive GNSS signals, Wherein, the one or more amplifiers are RF programmable gain amplifiers, and the one or more amplifiers include: A first amplifier, configured to amplify the amplitude of a received GNSS signal; and A second amplifier is configured to amplify the amplitude of the test signal based on the amplitude of the received GNSS signal.

12. The receiver according to claim 11, wherein, The signal chain is also configured to process the received GNSS signals, and the one or more output signals include the received GNSS signals and the test signals.

13. The receiver according to claim 11, wherein, The test signal is either a CDMA signal or an OFDM signal.

14. The receiver according to claim 11, wherein, The test signal is one of the following: Multiple single-band signals; and Wideband signals that span multiple signal frequency bands.

15. The receiver according to claim 11, wherein, The input node is located after the downconversion stage in the signal chain.

16. The receiver according to claim 11, wherein, The signal chain is configured to continuously receive the test signal.

17. The receiver according to claim 11, wherein, The signal chain is configured to receive the test signal at predetermined test intervals.

18. The receiver according to claim 11, wherein, The identified one or more errors include an anomaly in at least one of carrier lock state, code lock state, group delay drift, signal bandwidth, and amplitude.

19. The receiver according to claim 12, wherein, The parameters of the test signal include at least one of phase, timing, amplitude, and information contained in the test signal.

20. The receiver according to claim 12, wherein, The GNSS signal and the test signal differ in at least one of the following: PRN code, bandwidth, amplitude, and center frequency.

Citation Information

Patent Citations

  • Built-in self-test for receiver

    US20150372773A1

  • Satellite positioning system receiver capable of detecting failure in RF receiver unit including receiving antenna

    US20180203127A1