US 7,606,335 B2Grant
Signal pulse detection scheme for use in real-time spectrum analysis
Issue Date:2009-10-20
•18 Claims
•22 Drawing Sheets
Abstract
A spectrum analysis engine (SAGE) that comprises a spectrum analyzer component, a signal detector component, a universal signal synchronizer component and a snapshot buffer component. The spectrum analyzer component generates data representing a real-time spectrogram of a bandwidth of radio frequency (RF) spectrum. The signal detector detects signal pulses in the frequency band and outputs pulse event information entries output, which include the start time, duration, power, center frequency and bandwidth of each detected pulse. The signal detector also provides pulse trigger outputs which may be used to enable/disable the collection of information by the spectrum analyzer and the snapshot buffer components. An alternative pulse detection module is provided that tracks signal pulses by comparing peak data from successive FFT cycles with existing signal pulse data that is derived from comparing peak data for prior FFT cycles. Peaks for new FFT cycles are matched to data associated with signal pulses determined to be occurring over many FFT intervals.
Metadata
Assignee
- Cisco Technology, Inc.
Inventors
- David S. Kloper
- Brian F. Kane
- Gary L. Sugar
Application Information
Application Number:US 11/830,390
Filing Date:2007-07-30
Priority Date:2002-04-22
Art Unit:2611
Classifications
IPC:
H03D1/00H04L27/06
Patent Drawings (22 sheets)
Description
Related Applications
[0001] This application is a continuation of U.S. application Ser. No. 10/909,450, filed Aug. 2, 2004, which in turn claims priority to U.S. Provisional Application No. 60/587,834, filed Jul. 14, 2004, and is a continuation-in-part of U.S. application Ser. No. 10/757,704, filed Jan. 4, 2004, now U.S. Pat. No. 7,224,752 B2, which is a continuation of U.S. application Ser. No. 10/246,365, filed Sep. 18, 2002, now U.S. Pat. No. 6,714,605, that in turn claims priority to U.S. Application No. 60/374,365, filed Apr. 22, 2002; U.S. Application No. 60/380,890, filed May 16, 2002; U.S. Application No. 60/319,435, filed Jul. 30, 2002; and U.S. Application No. 60/319,542, filed Sep. 11, 2002.
[0002] The entirety of each of the aforementioned applications and patent is incorporated herein by reference.
[0003] This application is related to each of the following commonly assigned U.S. Applications, filed on Sep. 18, 2002 (the entirety of each of which is incorporated herein by reference):
[0004] U.S. application Ser. No. 10/246,364, now U.S. Pat. No. 6,850,735, entitled “System and Method for Classification of Unknown Signals in a Frequency Band.”
[0005] U.S. application Ser. No. 10/246,363, corresponding to U.S. Application Publication No. 2003/0198200 A1, entitled “System and Method for Spectrum Management of a Shared Frequency Band.”
Background of the Invention
[0006] The present invention is directed to technology used in a radio communication device to derive information about the signals active in a radio frequency band where the radio communication device is operating, such as an unlicensed radio frequency band shared by many different devices.
[0007] In certain radio communication systems, it would be desirable to know whether and what types of other signals or devices are active. For example, an unlicensed radio frequency band is, by its nature, free to be used by any device that emits radiowave energy within certain power levels in that part of the allocated spectrum. It is possible that many devices would share the unlicensed frequency band at the same time, potentially causing interference with each other. Under these circumstances, what would be useful is to provide the capability of processing signals that represent activity in the frequency spectrum over a time interval to derive information about the basic characteristics of those signals in order to identify or classify them.
Summary of the Invention
[0008] A real-time spectrum analysis engine (SAGE) is provided that generates information about the signal activity in a frequency band. The SAGE has several components to produce generalized spectrum information as well as specific information concerning the type of signal pulses in the frequency band at any given time.
[0009] The SAGE is, for example, a hardware accelerator that resides in a communication device and comprises a spectrum analyzer component, a signal detector component, a universal signal synchronizer component and a snapshot buffer component. The spectrum analyzer component generates data representing a real-time spectrogram of a bandwidth of radio frequency (RF) spectrum. The signal detector detects signal pulses in the frequency band and outputs pulse event information entries which include the start time, duration, power, center frequency and bandwidth of each detected pulse. The signal detector also provides pulse trigger outputs which may be used to enable/disable the collection of information by the spectrum analyzer and the snapshot buffer components. The snapshot buffer collects a set of raw digital signal samples useful for signal classification and other purposes. The universal signal synchronizer synchronizes to periodic signal sources, useful for instituting schemes to avoid interference with those signals. Some or all of the functions of the SAGE may be implemented entirely in software executed by a processor.
[0010] An alternative pulse detection module is provided that tracks signal pulses by comparing peak data from successive FFT sampling cycles with existing signal pulse data that is derived from comparing peak data for prior FFT cycles. Peaks for new FFT sampling cycles are matched to data associated with signal pulses determined to be occurring over longer periods of time, e.g., several sampling cycles.
[0011] The spectrum analysis techniques described herein may be applied to an unlicensed frequency band, or another frequency band in which it is desired to monitor RF activity.
[0012] The above and other objects and advantages will become readily apparent when reference is made to the following description taken in conjunction with the accompanying drawings.
Brief Description of the Drawings
[0013] FIG. 1 is a block diagram showing the spectrum analysis engine (SAGE).
[0014] FIG. 2 is a block diagram of a radio transceiver interface that interfaces the SAGE to a radio transceiver or radio receiver.
[0015] FIG. 3 is a more detailed block diagram of the SAGE.
[0016] FIG. 4 is schematic diagram of the spectrum analyzer component of the spectrum analysis engine.
[0017] FIG. 5 is a graphical diagram showing a representation of the FFT data generated by the spectrum analyzer.
[0018] FIG. 6 is a more detailed block diagram of the peak detector and pulse detector components of the spectrum analysis engine.
[0019] FIG. 7 is a graphical plot showing a signal peak that is detected by the peak detector.
[0020] FIG. 8 is a schematic diagram of the components of the pulse detector.
[0021] FIG. 9 is a block diagram of another type of pulse detector shown in FIG. 3 .
[0022] FIG. 10 is a graphical diagram of exemplary FFT data to explain the operation of the pulse detector shown in FIG. 9 .
[0023] FIG. 11 is a graphical plot showing exemplary signal pulses and pulse event information generated by the signal detector for the exemplary signal pulses.
[0024] FIG. 12 is a schematic diagram of the statistics logic module of the spectrum analyzer component of the SAGE.
[0025] FIG. 13 is a diagram showing exemplary statistics that are accumulated by the statistics logic module.
[0026] FIG. 14 is a diagram showing the exemplary peak stats that are accumulated by the stats logic module.
[0027] FIG. 15 is a block diagram showing the dual port RAM (DPR) storage used to store data generated by the spectrum analysis engine, and from which a microprocessor control unit (MCU) may obtain output of the SAGE.
[0028] FIG. 16 is a diagram showing the addressing scheme for data stored in the DPR.
[0029] FIG. 17 is a diagram showing the circular list structure of the data stored in the DPR.
[0030] FIG. 18 is a diagram showing the position list format of the circular list for data stored in the DPR.
[0031] FIG. 19 is a block diagram of a universal clock module component of the universal signal synchronizer.
[0032] FIG. 20 is a timing diagram showing how a universal clock module is used to synchronize to an exemplary pulse detected in the frequency band.
[0033] FIG. 21 is a block diagram of a clock update process to update the frequency offset between the clock of a detected signal and a local clock.
[0034] FIG. 22 is a diagram showing how the SAGE may be operated.
[0035] FIG. 23 is a block diagram showing another environment in which the SAGE may be deployed.
Detailed Description of the Drawings
[0036] The spectrum analysis engine, hereinafter referred to as “SAGE” is a hardware accelerator useful to generate in real-time information about received RF energy in a frequency band. FIG. 1 is a block diagram showing the SAGE 10 together with other hardware components that SAGE interacts with during operation. The SAGE 10 and related components may be implemented in a variety of ways. One way is with field programmable gate arrays (FPGAs) on a single or multiple semiconductor chips configured to perform the functions described herein. Another way with digital logic gates implemented in a semiconductor integrated circuit. For example, the majority of the SAGE 10 can be implemented as part of or the entirety of an application specific integrated circuit (ASIC). It is also envisioned that for certain applications, some or all of the functions of the SAGE 10 are implemented with software instructions stored on a processor readable medium, and executed by a processor, such as the MCU, or another processor in another device coupled to receive as input the output an ADC that converts the downconverted signals to a digital signal.
[0037] The SAGE 10 comprises a spectrum analyzer (SA) 100, a signal detector (SD) 200, a snapshot buffer (SB) 300 and a universal signal synchronizer (USS) 400. The SA 100 generates data representing a real-time spectrogram of a bandwidth of radio frequency (RF) spectrum, such as, for example, up to 100 MHz. As such, the SA 100 may be used to monitor all activity in a frequency band, for example, the 2.4-2.483 GHz ISM band, or the 5.15-5.35 GHz and 5.725-5.825 GHz UNII bands. Power vs. frequency information generated by SAGE 10 is stored in a dual-port RAM (DPR) 500 and is also used by the signal detector 200. The bandwidth capabilities of the SA 100 depends on the frequency band of application.
[0038] The signal detector 200 detects signal pulses in the frequency band and outputs pulse event information entries, which include one or more of the start time, duration, power, center frequency and bandwidth of each detected pulse. The signal detector 200 also provides pulse trigger outputs which may be used to enable/disable the collection of information by the spectrum analyzer 100 and the snapshot buffer 300 components.
[0039] The snapshot buffer 300 collects a set of raw digital signal samples useful for signal classification and other purposes, such as time of arrival location or received signal strength (RSS) measurements. The snapshot buffer 300 can be triggered to begin sample collection from either the signal detector 200 or from an external trigger source using the snapshot trigger signal SB_TRIG.
[0040] The universal signal synchronizer 400 synchronizes to periodic signal sources, such as Bluetooth SCO headsets and cordless phones. The USS 400 interfaces with medium access control (MAC) logic 750 that manages scheduling of packet transmissions in the frequency band according to a MAC protocol, such as, for example, the IEEE WLAN 802.11 protocols. The MAC logic 750 may be implemented in DSP firmware, or in higher level software.
[0041] The SAGE 10 is useful in a radio communication device where a radio transceiver 600 (or a radio receiver) is used to process received RF signals and convert them to baseband signals. A microprocessor control unit (MCU) 700 interfaces with the SAGE 10 to receive spectrum information output by SAGE 10, and to control certain operational parameters of SAGE 10 for particular functions described in detail hereinafter. The MCU 700 may be any suitable microprocessor that resides either on the same semiconductor chip as the SAGE 10, or on another chip. The MCU interfaces with SAGE 10 through the DPR 500 and the control registers 560. The SAGE 10 interfaces with the MCU 700 through a memory interface (I/F) 550 that is coupled to the DPR 500.
[0042] The control registers 560 include registers to enable the MCU 700 to configure control and monitor the SAGE 10. There is a control/status register, an interrupt enable register, an interrupt flags register, spectrum analyzer control registers, signal detector control registers, snapshot buffer control registers and USS control registers. The control/status register includes a field to perform a reset of the SAGE components. The interrupt enable register is used to indicate one or more pending interrupt conditions to the MCU 700. The MCU 700 also uses the interrupt flags register to clear any processed interrupts.
[0043] Two clock signals are used to drive the SAGE 10. The main clock signal, CLK, runs at the sampling rate of the ADC 810 and controls most of the SAGE logic. The other clock, BUSCLK, is used to control the MCU side of DPR 500, interface to the control registers 560, the global timer interfaces (GFIs), and the lower medium access control (LMAC) interfaces. The DPR 500 is driven using a separate clock on each port: CLK on the SAGE side and BUSCLK on the MCU side. The control registers 560 may be double-buffered to avoid synchronization problems between SAGE and MCU control logic.
[0044] The SAGE 10 operates on digital signals derived from the baseband signals output by the radio transceiver 600. An RF interface 800 is provided that pre-processes the baseband signals for processing by the SAGE 10.
[0045] Turning to FIG. 2 , the RF interface 800 will be described. The RF interface 800 comprises an analog-to-digital converter (ADC) block 810, an automatic gain control (AGC) block 820, a direct current (DC) correction block 830 and an amplitude/phase correction block 840.
[0046] The radio transceiver 600 that generates the received (Rx) baseband signals may have an RF receiver in which the local oscillator (LO) for the quadrature downconverter is placed at the center of the band of interest. As such, DC, amplitude and phase offset compensation circuits are employed before the Fast Fourier Transform (FFT) to maximize LO and sideband suppression.
[0047] The Rx baseband signals are sampled at the CLK frequency using two ADCs, one for the in-phase signal (I), and another for the quadrature signal (Q). Only one ADC is shown in FIG. 2 for simplicity. An example of a CLK and ADC frequency is 120 MHz, which is sufficient to digitize the entire 2.4 GHz band, as an example. Consequently, the maximum FFT rate is 468.8 kHz (2.13 microseconds per FFT) at CLK=120 MHz, though faster or slower rates may be suitable for other applications.
[0048] The AGC block 820 dynamically adjusts the gain of the receiver to optimize the placement of the Rx signal within the dynamic range of the ADC 810. A slow, feedback-driven algorithm is useful, in which the Rx gain is adjusted to place the maximum signal level received in the last T seconds (nominally T=1 second) 6 dB below full-scale on the ADC 810. The use of a “slow” AGC algorithm is beneficial because it prevents the ADC 810 from saturating when sampling the entire frequency band of interest (wideband mode) whenever strong signals appear suddenly in the band, without requiring rapid adjustments in gain which can cause distortion and discontinuities in Rx signal pulses. The output of the AGC 820 is an AGCcomp signal, the use of which is described hereinafter.
[0049] The DC correction and amplitude/phase correction blocks 830 and 840, respectively, compensate for LO leakage and amplitude/phase imbalance in the quadrature mixer of the radio transceiver. DC correction is performed adaptively by estimating the DC offset at the ADC output and updating a correction DAC to remove large DC offsets. Any residual DC offset after course correction is removed after the ADC via digital subtraction. The MCU estimates the amplitude and phase imbalance and programs the correction values into the appropriate control registers.
[0050] The output of the RF interface 800 comprises a digital signal DataI representing The in-phase received signal and a digital signal DataQ representing the quadrature phase received signal. The signals DataI′ and DataQ′ represent the output of the summer 835, uncorrected for DC and amplitude/phase, and can be supplied as the raw data to the snapshot buffer 300.
[0051] The SAGE 10 can be used in a radio communication device that includes a RF receiver capable of operating in a wideband mode or narrowband mode. In a wideband mode, the RF receiver may downconvert an entire or a substantial portion of a frequency band in which the radio communication device operates. In the wideband mode, the RF interface 800 supplies digital signals representing activity in the entire frequency band for successive time intervals as input to the SAGE 10. In a narrowband mode, the RF receiver may downconvert only a single RF channel or other designated portion of the frequency band, in which case, the RF interface 800 would supply digital signals representing activity in that single RF channel or portion of the frequency band. An example of a radio receiver having a wideband mode as part of a radio transceiver is disclosed in commonly assigned U.S. Provisional Application No. 60/319,434 filed Jul. 30, 2002, the entirety of which is incorporated herein by reference.
[0052] Turning to FIG. 3 , the spectrum analyzer 100, signal detector 200 and snapshot buffer 300 will be described.
The Spectrum Analyzer
[0053] With reference to FIGS. 3 and 4 , the spectrum analyzer 100 performs real-time FFT-based spectrum analysis on the DataI and DataQ signals. As an example, the SA 100 is capable of providing real-time spectrum analysis information for up to 120 MHz of RF bandwidth, and as such can be used to monitor all activity in either the 2.4 GHz or 5.7 GHz ISM bands. Other applications for monitoring smaller or greater bandwidths are also possible using similar techniques.
[0054] The spectrum analyzer 100 comprises a windowing block 110, a Fast Fourier Transform (FFT) block 120, a power calculation block 130, a lowpass filter block 140, a linear-to-log converter (dB conversion) block 150, a history buffer 160, statistics (stats) logic block 170 and a spectrum analyzer memory controller 190.
[0055] As shown in FIG. 4 , the windowing block 110 performs pre-FFT windowing on the I and Q data using either a Hanning or rectangular window with a multiplier 112 and a ROM 114 that stores slope coefficients for the windowing process.
[0056] The output of the windowing block 110 is coupled to the input of the FFT block 120. The FFT block 120 is, for example, a 256 frequency bin FFT block that provides (I and Q) FFT data for each of 256 frequency bins that span the bandwidth of frequency band of interest. An example of the FFT data field is shown in FIG. 5 . For each FFT sampling time interval, the FFT block outputs M (such as 10) bits of data for each FFT frequency bin, for example, 256 bins. Thus, it can be seen that two-dimensional data structure can be defined for the FFT data fields across time intervals. This diagram is a useful paradigm to understand the further operations that are performed on the FFT data.
[0057] The output of the FFT block 120 is coupled to the power calculation block 130. The power calculation block 130 comprises two multipliers 132 and 134 and an adder 136. The multipliers 132 and 134 compute (FFTdataI)2 and (FFTdataQ)2, respectively, and the adder 136 adds them together, to output a power value.
[0058] The lowpass filter block 140 comprises a multiplier 142, multiplier 144, an adder 145, a flip-flop 146 and a history RAM 148. The lowpass filter block 140 performs a unity-gain, single-pole lowpass filtering operation on the power values of the signal at each FFT frequency bin. Using Pfft(k) to denote the power value at FFT frequency f(k), the lowpass filter output Plpf(k) is updated once per FFT interval (t) as follows: Plpf(k, t):=α1P(k, t)+(1−α1)Plpf(k, t−1), 1≦k≦256, where α1 and (1-α1) are parameters for the multipliers 142 and 144, respectively specifying the LPF bandwidth which is configured by the MCU 700. The history RAM 148 stores the FFT power data for the previous FFT interval that is used with multiplier 144 according to the mathematical relationship described above.
[0059] The dB conversion block 150 at the output of the lowpass filter block 140 computes the decibel value PDB(k)=10*log(|Plpf(k, t)|) for each FFT bin value Plpf(k, t) (in dBFS, i.e., dB from full-scale on the ADC). The ROM 152 stores a table used for the dB conversion computation and the adder 152 subtracts the gain compensation AGCcomp output by the AGC 820. The output of the dB conversion block is a PDB(k) data field (k=number of frequency bins) containing dB power data at each frequency bin and a PDBSTART signal that indicates the start of the following PDB(k) field. \
[0060] The sequence of the LPF 140 and the dB conversion block 150 shown in FIGS. 3 and 4 may be switched.
[0061] The stats logic block 170 will be described hereinafter in conjunction with FIG. 10 .
[0062] The spectrum analyzer 100 has two operating modes for writing data into the DPR 500. In a continuous mode, one power vs. frequency value is written to the DPR 500 every N FFT cycles (N=decimation factor). In a transitional mode, a power vs. frequency value is written whenever a pulse event is detected by the signal detector 200, in response to a spectrum analyzer trigger event signal SD_SAEVT, described hereinafter. The transitional mode generally improves DPR storage efficiency over the continuous mode since in the former case power vs. frequency information is written to the DPR only after pulse transitions.
[0063] Examples of control registers for the spectrum analyzer include a control field, a register for the lowpass filter parameter α, registers for the DPR address of the DPR buffers that store the spectrum analyzer stats, a register that counts the number of times the stats have been updated, a register that stores a value that determines the number of FFT intervals for a statistic update cycle, a register that stores the power threshold value for the duty cycle stats (described hereinafter), and a register for the structure for the power vs. frequency circular list.
[0064] The spectrum analyzer control register includes fields to, among other things, indicate received signal strength indicator (RSSI) mode, absolute or relative. The relative mode means that power measurements are in units of dB full scale; absolute mode means the measurements are in units of dBm. In addition, there is a field to indicate the operational mode of the spectrum analyzer, continuous mode or transitional mode.
The Signal Detector
[0065] With reference to FIG. 3 in conjunction with FIG. 6 , the signal detector 200 identifies signal pulses in the Rx data path, filters these signals based on their spectral and temporal properties, and passes characteristic information about certain detected pulses to the MCU 700 via the DPR 500. The signal detector 200 also provides pulse timing information to the universal signal synchronizer 400 to allow it to synchronize its clocks to transmissions to/from other devices operating in the frequency band, for example, to eliminate interference with QoS-sensitive devices such as cordless phones, Bluetooth™ headsets, video-over-802.11 devices, etc.
[0066] As shown in FIG. 3 , the signal detector 200 comprises a peak detector 210 and a one or more pulse detectors 220 and 220′. The peak detector 210 looks for spectral peaks in the FFT sequence at its input, and reports the bandwidth, center frequency and power for each detected peak. The output of the peak detector is one or more peaks and related information. The pulse detectors 220 and 220′ detect and characterize signal pulses based on input from the peak detector 210.
[0067] The peak detector 210 detects a peak as a set of FFT points in contiguous FFT frequency bins, each above a configured minimum power level. Once per FFT interval, the peak detector 210 outputs data describing those frequency bins that had a FFT value above a peak threshold and which frequency bin of a contiguous set of frequency bins has a maximum value for that set. In addition, the peak detector 210 passes the PDB(k) data field for each FFT interval. This can be represented by the pseudo code (where k is the frequency bin index):
[0068]
| PDBdiff(k)= PDB(k) − SD_PEAKTH ; | |
| If(PDBdiff(k) > or = 0 ) | |
| PDBpeak(k)= PDB(k) ; | |
| PEAKEN(k)= 1 ; | |
| Else | |
| PDBpeak(k)= 0 ; | |
| PEAKEN(k)= 0 ; | |
| end | |
[0069] The peak detector 210, as shown in FIG. 6 , comprises a comparator 212, a register file 214, a FIFO 216 and a FIFO 218. The comparator 212 compares the dB power value PDB(k) with the peak threshold (SD_PEAKTH). The FIFO 216 stores a data word that indicates which frequency bins k had a power value above the peak threshold, and which did not. For example, if the FFT outputs 256 FFT values, the FIFO 216 stores a 256 bit word, with 1's indicating FFT values that exceed the peak threshold and 0's indicating FFT values that do not exceed the peak threshold. The register file 214 stores the maximum peak power value in any set of contiguous FFT values that exceed the peak threshold. This maxpeak information is used in the pulse detector. The FIFO 218 stores the PDB(k) data field corresponding to the data stored in the register file 214 and FIFO 216.
[0070] FIG. 7 shows an example where a peak is detected at the frequency bin 130 by a contiguous set of points above a peak threshold shown in the dotted line. In this example, NFFT=256, fs=120 MHz, configured min power level=−80 dBm (not shown), k0=129, k1=127, kh=131, P(k0)=−50 dBm, BW_THRESH=15 dB, bandwidth=1.875 MHz, center frequency=0.4688 MHz. These latter parameters will be described hereinafter in conjunction with the pulse detector 220. The variable fs is the sampling rate of the ADC (FIG. 2 ), which will depend on the width of the frequency band to be processed. Narrowband and wideband operation of the radio transceiver is described above.
[0071] As an alternative, it is not necessary that the peak detector detect a peak as a set of FFT points in contiguous frequency bins. For example, it may be desirable to account for frequency selective fading channel conditions, in which case a peak may span a non-contiguous set of bins. Similarly, it may be desirable to employ a peak threshold that is not absolute, but rather is varies or is relative to the power level of a nearby frequency bin, such as an adjacent bin or bins, so as to allow for more precise recognition of one or more peaks that might otherwise be detected as a single peak.
[0072] The signal detector 200 has one or more pulse detectors 220 (such as 4), allowing several pulses to be detected and characterized simultaneously. As shown in FIG. 6 , each pulse detector 220 comprises a pulse identifier block 230, a pulse finder block 250, a pulse tracking block 270 and a detect buffer 290. These components, described further in conjunction with FIG. 8 , are operated with configurable parameters to execute a set of rules:
[0073] Pulse Shaping Rules: How should pulse information be extracted from raw peak information—performed by the pulse identifier 230.
[0074] Pulse Detection Rules: Under what conditions is the start of a pulse detected—performed by the pulse finder 250.
[0075] Pulse Termination Rules: Under what conditions should an individual pulse be considered complete—performed by the pulse tracker 270.
[0076] Pulse Shaping Rules.
[0077] For a detected FFT peak at frequency index k0, the bandwidth of the peak is defined as FPBW=Bandwidth (Hz)=(kh−k1+1)*fs/NFFT, where k1 and kh are the smallest and largest integers, respectively, satisfying (1) k1≦k0≦kh, and (2) P(k)≧P(k0)−BW_THRESH for any k1≦k≦kh, where fs is the ADC sampling rate in Hz, NFFT is the number of points/bins in the FFT, and P(k) denotes the power (in milliwatts) at FFT frequency bin k.
[0078] Similarly, the center frequency of the peak is FPCENTER=Center Frequency (Hz)=[(kh+k1)/2]*fs/NFFT. This definition of center frequency locates the signal in the Nyquist band only. The actual center frequency at RF is given by RF Center Frequency (Hz)=FPCenter−fs/2+fLO, where fLO is the RF LO frequency used to convert the FFT band to baseband, and a zero-IF receiver architecture is assumed (i.e., the LO is in the center of the RF band).
[0079] The peak detector 210 uses the following formula to estimate the power of a peak: Power (dBm)=ΣPDBpeak(k), from k=k1 to kh. This is only an estimate and its accuracy depends on the signal itself and the value of BW_THRESH. The pulse identifier 230 shown in FIG. 8 comprises components to perform the pulse shaping rules using the bandwidth threshold (BW_THRESH) parameter to identify those pulses that have a bandwidth that is greater than or exceeds the bandwidth threshold.
[0080] Pulse Detection Rules. The pulse detection rules specify the conditions under which the start of a pulse is to be detected and these rules are performed by the pulse finder 250. For example, a pulse is considered DETECTED if there is a peak from the pulse shaping rules that satisfies ALL of the following conditions:
[0081] 1) Estimated power is between the peak detector minimum power and the peak detector maximum power. The pulse power level DETECT_POWER which triggered the detection of this specific pulse is used by the pulse termination rules.
[0082] 2) Center frequency of the peak is between a center frequency minimum and a center frequency maximum. The detected center frequency DETECT_CFREQ is used in pulse termination rules.
[0083] 3) Bandwidth of the peak is within a bandwidth minimum and a bandwidth maximum.
[0084] Pulse Termination Rules. A pulse may be considered TERMINATED if, for example, the pulse duration exceeds a duration maximum, or NONE of the detected peaks from the peak detector satisfies ALL of the following conditions:
[0085] 1) Estimated power of the peak is within +/−a power hold value of the power of the pulse when it was originally detected.
[0086] 2) Center frequency of the peak is within +/−a frequency hold value of the center frequency of the peak when it was originally detected.
[0087] 3) Bandwidth of the peak is within a bandwidth hold value of the bandwidth of the peak when it was originally detected.
[0088] The pulse tracker 270 comprises components to detect the termination of a pulse according to these rules.
[0089] When a pulse terminates, the pulse detector 220 writes a pulse event entry into the pulse event list if the pulse duration exceeds a pulse duration threshold value. Otherwise, the pulse event entry is discarded. The conditions which terminate the pulse are stored in a bit field which is included in the pulse event structure for the pulse. The pulse event structure will be described hereinafter.
[0090] Each pulse detector has its own configuration register (as part of the signal detector control registers) that stores values for each of the pulse parameters (described above) within which a pulse detector will process peak information. The following are examples of these parameters.
[0091] PWRMIN: Minimum power threshold (1 dBm)
[0092] PWRMAX: Maximum power threshold (1 dBm)
[0093] BWTHRESH: Bandwidth threshold (1 dBm)
[0094] CFREQMIN: Min center frequency (fs/NFFT Hz)
[0095] CFREQMAX: Max center frequency (fs/NFFT Hz)
[0096] BWMIN: Min pulse bandwidth (fs/NFFT Hz)
[0097] BWMAX: Max pulse bandwidth (fs/NFFT Hz)
[0098] DURMAX: Max pulse duration (TMR_PULSE)
[0099] DURMIN: Min pulse duration (TMR_PULSE)
[0100] PWRHOLD: Power hold value (1 dB)
[0101] FRQHOLD: Frequency hold value (fs/NFFT Hz)
[0102] BWHOLD: Bandwidth hold value (fs/NFFT Hz)
[0103] FPCENTER: Current pulse center frequency (fs/NFFT Hz)
[0104] FPBW: Current pulse bandwidth (fs/NFFT Hz)
[0105] PWR: Current pulse power estimate (1 dBm)
[0106] The terms fs and TMR_PULSE are described above and/or referenced in FIGS. 1-3 .
[0107] Each pulse detector can be configured by the MCU 700. The MCU 700 writes appropriate values to the configuration register(s) of the signal detector to configure one or more pulse detectors to look for and characterize a certain type of pulse in the frequency band. The control register controls clearing and resetting of a pulse detector so that it can be reconfigured to look for a different type of pulse. The pulse detector control register includes a field that identifies which, if any, universal clock module of the universal signal synchronizer 400 is to be associated with the pulse detector. The universal clock module (UCM) is described hereinafter. When there is an association between the pulse detector and the universal clock module, the pulse detector stores the counter value of that universal clock module into the pulse event list whenever it detects a pulse. The counter values can be used by the MCU 700 to phase lock a universal clock module to a periodic interference source, as described hereinafter.
[0108] Each pulse detector outputs pulse event data for storage in the DPR 500. The following is an example of pulse event data.
-
- [0109] SDID: Pulse detector identifier.
- [0110] TERMCODE: Pulse termination codes:
- [0111] Bit 0 (LSB): Pulse power outside of hold range
- [0112] Bit 1: Center frequency outside of hold range
- [0113] Bit 2: Bandwidth outside of hold range
- [0114] Bit 3: Duration exceeds durMax
- [0115] FCENTER: Center frequency (at beginning of pulse)
- [0116] BW: Pulse bandwidth (at beginning of pulse)
- [0117] DUR: Pulse duration in TMR_PULSE cycles. The pulse duration value is given by toff−ton, where toff and ton denote the TMR_TSTMP values latched at the FFT_START pulse associated with the first and last FFT of a detected pulse, respectively.
- [0118] TIMEON: Timestamp for start of pulse event. TIMEON contains the TMR_TSTMP value latched at the FFT_START pulse associated with the first FFT that produces a pulse detection match.
- [0119] UCMCNT: Counter values from an associated universal clock module (UCM, described hereinafter) in the USS. The low-order 16 bits contain the UCM down counter value at the beginning of the pulse event. The least-significant 2 bits in the upper half-word contain the mod(N) counter value (also in the associated UCM) at the beginning of the pulse event. If there is no associated UCM with a pulse detector, this field is set to all zeros.
- [0120] PWR: Pulse power estimate (at beginning of pulse, 1 dBm)
[0121] The signal detector 200 outputs descriptions of detected pulses as pulse events, containing the data described in the table above may be, for example, into a circular list called the pulse event list in the DPR 500. A single list may be used for all of the pulse detectors. The source pulse detector of an individual pulse event in the list is indicated by the pulse event “SDID” field.
[0122] FIG. 3 illustrates another type of pulse detector, designated by reference numeral 220′, that also operates on data output by the peak detector 210. Pulse detector 220′ may be used in place of or in additional to the pulse detector(s) 220. FIG. 9 shows a block diagram of the pulse detector 220′ and associated configuration blocks. The configuration block 2010 that contains registers that control the behavior of the various modules of the pulse detector 220′. The modules include a peak calculation module 2020, an incoming data FIFO module 2030, a pulse comparison module 2040, and an (existing and updated) data structures module 2050 that stores existing and updated pulse data (and may be embodied by one or more SRAMs). It should be understood that a single memory may be used for both the FIFO 2030 and the existing and updated data structures 2050. The pulse comparison module 2040 and data structure module 2050 are coupled to the memory interface (I/F) 2060. The interface 2060 couples data to the SAGE memory controller/interface 550 (FIG. 3 ) in accordance with addresses assigned by a circular list (Clist) module 2070. The functions of each of these modules may be implemented by digital logic gates in an ASIC, or programmable gate array logic such as an FPGA, etc. Alternatively, these modules may also be implemented by software stored on a processor readable medium and executed by a processor.
[0123] A brief description of each block is provided, followed by a more detail discussion.
[0124] The peak calculation module 2020 takes the peak detector output (start pulse for each FFT cycle, timestamp of each FFT, power per FFT bin, power exceeding defined threshold, and maximum power of a group of contiguous bins above the threshold) and calculates a frequency location of the peak, such as the starting (lefthand) frequency. In addition, the peak calculation module 2020 computes the bandwidth and maximum power per peak for up to a maximum number of peaks, e.g., the first 24 peaks, per FFT cycle. The peak calculation module 2020 also filters out peaks that are above the peak detector threshold for less than a configurable number of FFT bins (minimum bandwidth-based filtering). The number of peaks that can be detected is a system design decision, and more or less may be appropriate.
[0125] As an optional alternative, the peak calculation module 2020 may compute the sum of each of the lefthand frequencies, righthand frequencies and power for each peak, in order to compute (or allow computation of) the average lefthand frequency, average righthand frequency and average power across peaks.
[0126] The incoming data FIFO 2030 stores the data from the peak calculation module for up to two FFTs, and thereby buffers out the incoming peaks to allow for processing latency as well as latency caused by waiting for access to the DPR 500 to store results.
[0127] The pulse comparison module 2040 compares data associated with pulses determined to occur from one or more previous FFT cycles stored in the existing data structure portion of the module 2050 with data associated with peaks in the current FFT cycle stored in the incoming data FIFO 2030, and writes the results to the updated data structure portion of the module 2050. The pulse comparison module 2040 may take one of several actions: add a new pulse, extend a previous pulse with a current peak, or terminate an existing pulse. After processing the peaks for an FFT interval, the pulse comparison module 2040 signals to the memory I/F 2060 to start its function.
[0128] The memory I/F 2060 transfers to the SAGE memory I/F 500 (FIG. 3 ) data from the existing data structure portion of module 2050 for any peaks that were terminated or that have exceeded a configurable maximum duration. The range of addresses to be used is defined by the associated Clist module 2070.
[0129] A more detailed description of the pulse detector 220′ will now be provided.
[0130] The configuration block 2010 has registers to store values for the following configuration. These values control the filtering functions of the pulse detector 220′ as performed by operations of the various modules described above.
[0131]
| Field Name | Description |
|---|---|
| BW_min | This is the minimum bandwidth, in FFT bins, |
| for an incoming peak to be created by the peak | |
| calculation module and output to the incoming | |
| data FIFO to be checked against the existing | |
| data structure. By setting this greater than 1, it | |
| would be possible to eliminate the degenerate | |
| case of 24 peaks, each lasting for 1 bin and | |
| separated by 1 bin. | |
| BW_thresh | This is used to determine the bandwidth of the |
| peak - the highest bin number (before the max | |
| power is reached) that crosses this threshold | |
| below the peak (in db) is the lefthand (min) | |
| frequency of the pulse and the smallest bin | |
| number (after the peak is reached) that crosses | |
| this threshold is the righthand (max) frequency | |
| of the pulse. | |
| BW_hold | The amount, in FFT bins, that a peak can vary |
| or deviate from the measured bandwidth of the | |
| first peak without terminating the pulse. This is | |
| used by the pulse comparison module. | |
| Left_freq_hold | The amount, in FFT bins, that a peak can vary |
| from the measured minimum frequency of the | |
| first peak without terminating the pulse. This | |
| may be used by the pulse comparison module. | |
| Pwr_hold | The amount, in dB, that a peak can vary from |
| the measured max_power of the first peak | |
| without terminating the pulse. This is used by | |
| the pulse comparison module. | |
| Max_duration | If a pulse exists for more than this number of |
| FFT cycles (~5.9 μs at 44 MHz), then its data | |
| structure will be transferred to the host | |
| processor and its duration will restart from the | |
| initial value (the minimum/initial value of | |
| duration is 1). | |
[0132] The signals used by the pulse detector 220′ are defined below.
[0133]
| Signal Name | Description | |
|---|---|---|
| Pdb_peak | Power, in db, of the current FFT frequency | |
| bin | ||
| Peak_en | Is the power of the current FFT frequency | |
| bin greater than the value in SD_PEAKTH | ||
| Maxpeak | The maximum power of the current (or | |
| next, if peak_en is currently 0) peak | ||
| Peakstart | Start indication for the input data block | |
| Tstmp_pk | Timestamp of the block of the pdb_peak | |
| data | ||
[0134] The peak calculation module 2020 calculates (left) frequency, power and bandwidth for the peaks derived from the data output by the peak detector and stores that data in the incoming data FIFO 2030 (except for those peaks that are less than the configured minimum bandwidth). A method is used to specify the comparison logic on the other side of the FIFO the boundaries of each FFT cycle. This method may involve passing an additional bit through the FIFO as a “start of FFT” or the write address of the last word of the incoming FFT data (which the other side can compare against the read address). The timestamp is stored for each incoming FFT so that it can be passed to the host as part of the pulse data structure.
[0135] The data structure module 2050 may be a two-port SRAM, 1 R and 1 W. The RAM is deep enough to contain the existing data structure (e.g., 24 words) and the updated data structure (e.g., 24 words) for a total depth of 48 words, for example. Each of the power, bandwidth and frequency sections are further divided into three bytes: maximum value, minimum value and initial value. The incoming peaks data are sorted by increasing frequency bin index. The data in the existing data structure is sorted by increasing frequency bin index.
[0136] An example of a configuration of the data structure is as follows:
[0137]
| Time | EOP | SOP | Duration | Power | Bandwidth | Frequency |
| Stamp | ||||||
[0138] Thus, for each item stored in the data structure module 2050 there is each of the data shown above.
[0139] The following definitions are provided for purposes of explaining the operation of the pulse comparison module.
[0140] fe is the frequency bin of the current (pulse) item in the existing data structure.
[0141] P(fe) is data content for the current (pulse) item in the existing data structure (module 2050).
[0142] (f+1)e is the frequency bin of the next (pulse) item in the existing data structure.
[0143] P((f+1)e) is data content for the next (pulse) item in the existing data structure (module 2050).
[0144] fnew is the frequency bin of the current (peak) item in the incoming data FIFO 2030.
[0145] P(fnew) is the peak data for the current (peak) item stored in the incoming data FIFO 2030.
[0146] (f+1)new is the frequency bin of the next (peak) item stored in the incoming data FIFO 2030.
[0147] P((f+1)new) is peak data for the next (peak) item stored in the incoming data FIFO 2030.
[0148] EOP means end of pulse and is a flag used for indicating the end of a pulse.
[0149] SOP means start of pulse and is a flag used for indicating the start of a pulse.
[0150] The usage of the EOP and SOP flags are explained in the table below.
[0151]
| End of | Start of | |
|---|---|---|
| Pulse | Pulse | |
| (EOP) | (SOP) | Explanation |
| 0 | 1 | The pulse is being transferred due to a timeout |
| condition (max_duration has been exceeded). This | ||
| is the first time this pulse has been transferred. | ||
| The timestamp is the timestamp of the FFT in which | ||
| the timeout was exceeded (timeout is duration > | ||
| max_duration, not ≧). Therefore the timestamp of | ||
| the first FFT cycle in which the pulse existed is: | ||
| T(n) = timestamp − (duration (fft cycles) × | ||
| FFT time (us/fft cycle)) | ||
| 0 | 0 | The pulse is being transferred due to a |
| timeout condition (max_duration has been | ||
| exceeded). The pulse has been transferred at | ||
| least one time previously. In other words, this | ||
| is a data structure associated with a middle | ||
| transfer for the pulse (there are ones before | ||
| it and there will be ones after it). The timestamp | ||
| is the timestamp of the FFT in which the timeout | ||
| was exceeded (timeout is duration > max_duration, | ||
| not ≧). Therefore the timestamp of the first | ||
| FFT cycle in which the pulse existed is: T(n) = | ||
| timestamp − (duration (fft cycles) × FFT | ||
| time (us/fft cycle)) | ||
| 1 | 0 | The pulse is being transferred because it has |
| been terminated due to failing a frequency, | ||
| bandwidth, or power hold calculation. It has | ||
| been transferred at least one time previously. | ||
| The timestamp is the timestamp of the FFT in | ||
| which the hold calculation failed. Therefore | ||
| the timestamp of the 1st FFT cycle | ||
| in which the pulse existed is: T(n) = | ||
| timestamp − (duration (fft cycles) × FFT | ||
| time (us/fft cycle)) | ||
| 1 | 1 | The pulse is being transferred because it has |
| been terminated due to failing a frequency, | ||
| bandwidth, or power hold calculation. This is | ||
| the first time this pulse has been transferred. | ||
| The timestamp is the timestamp of the FFT in | ||
| which the hold calculation failed. Therefore the | ||
| timestamp of the first FFT cycle in which the | ||
| pulse existed is: T(n) = timestamp − (duration | ||
| (fft cycles) × FFT time (us/fft cycle)) | ||
[0152] For each entry in the incoming FIFO module 2030 and in the existing data structure portion of the data structure module 2050, the pulse comparison module 2040 performs a pulse comparison algorithm summarized by the pseudo-code below.
[0153]
| If fe = fnew then | |
| Compare P(fe) and P(fnew) based on pwr_hold, bw_hold [and | |
| freq_hold] | |
| If pass, then check max_duration | |
| If pass, then update existing data structure, else mark P(fe) as ready | |
| to be transferred to memory (do not set EOP) and add P(fnew) as | |
| new pulse to data structure (its duration is set back to 1) | |
| Else mark P(fe) as terminated (set EOP) and add P(fnew) as new pulse | |
| to data structure | |
[0154] Read next item from both FIFO and existing data
[0155]
| Else if fe > fnew then | |
| If |(f+1)new − fe| < | fnew− fe| then | |
| Add P(fnew) as new item | |
| Read next item from incoming FIFO | |
| Else | |
| Compare P(fe) and P(fnew) based on pwr_hold, bw_hold, | |
| and freq_hold | |
| If pass, then check max_duration | |
| If pass, then update existing data structure, else mark P(fe) as | |
| ready to be transferred to memory (do not set EOP) and add | |
| P(fnew) as new pulse to data structure (its duration is set back to 1) | |
| Else mark P(fe) as terminated (set EOP) and add P(fnew) as new pulse | |
| to data structure | |
[0156] Read next item from both FIFO and existing data
[0157]
| Else // fe < fnew | |
| If |(f+1)e − fnew| < | fe− fnew| then | |
| Terminate P(fe) | |
| Read next item from existing data structure | |
| Else | |
| Compare P(fe) and P(fnew) based on pwr_hold, bw_hold, | |
| freq_hold and max_duration | |
| If pass, check max_duration | |
| If pass, then update existing data structure, else mark P(fe) as | |
| ready to be transferred to memory (do not set EOP) and add | |
| P(fnew) as new pulse to data structure (its duration is set back to 1) | |
| Else mark P(fe) as terminated and add P(fnew) as new pulse | |
| to data structure | |
[0158] Read next item from both FIFO and existing data
[0159] The pulse comparison logic described above in pseudo-code performs the follow functions. Two lists are involved in the comparison process: an incoming peak list stored in the incoming data FIFO 2030 and an existing pulse list stored in the existing data structure (in module 2050). Items in each list are sorted by increasing (lefthand, i.e., starting) frequency. The incoming peak list tracks the peaks that are currently detected by the peak detector module. The existing pulse list tracks pulses that are currently being monitored from previous peak measurements. An updated pulse list stored in the updated data structure (in module 2050) is generated from the existing pulse list by removing old pulses that do not continue, and inserting new pulses for peaks (in the incoming peak list) that did not previously exist, and the algorithm repeats until all pulses and peaks have been processed in both lists.
[0160] Since signal measurements may not always match up to the same FFT bin for successive FFT cycles, an exact match in frequency is not required. For example, there may be two pulses in the existing pulse list, both of which are a sufficiently close match to a peak in the incoming peak list. A goal is to find the closest match to a pulse in the existing pulse list for the peak in the incoming peak list, and likewise to find the closest match to a peak in the incoming peak list with the pulse in the existing pulse list.
[0161] A comparison is made between data associated with a peak in the incoming peak list with data associated with the next two pulse items in the existing pulse list. If there is a better match in frequency of the peak to the first of these two pulse items, the pulse comparison logic will test the hold criteria to determine if the match is accepted for extending a pulse (by a time period equal to one FFT cycle) to the updated pulse list. If there is a better match in frequency of the peak to the second of these two pulse items, the first pulse item is terminated as not matching, and the algorithm will repeat. Similarly, data associated with a pulse in the existing pulse list is compared to data associated with the next two peak items in the incoming peak list, and will be used to add new pulses to the updated pulse list.
[0162] Each comparison pass results in consuming the first item in either the incoming peak list or existing pulse list, or consuming the first item in both lists. This process generates the updated pulse list which becomes the existing pulse list for the next batch of incoming peak data, and entries in the existing pulse list for transfer to the memory I/F 2060.
[0163] For purposes of further explanation of the operation of the pulse detector 220′, reference is made to FIG. 10 . FIG. 10 shows exemplary input to the pulse detector 220′. In this case, the peak calculation sub-block 2020 would identify three distinct peaks (whose characteristic frequency, power and bandwidth are labeled in FIG. 10 ). As an example, it is assumed the configuration registers for the pulse detector 220′ have the following values:
frequency_hold=4, power_hold=6, bandwidth_hold=3
and that there are two pulses in the existing data structure with the following characteristics:
frequency_hold=4, power_hold=6, bandwidth_hold=3
and that there are two pulses in the existing data structure with the following characteristics:
-
- [0164] Pulse 1: frequency_init=46, frequency_min=43, frequency_max=50; power_init=−50, power_min=−50, power_max=−45; bandwidth_init=20, bandwidth_min=19, bandwidth_max=22
- [0165] Pulse 2: frequency_init=160, frequency_min=159, frequency_max=162; power_init=−43, power_min=−47, power_max=−42; bandwidth_init=15, bandwidth_min=14, bandwidth_max=15
In this case, Peak 1 is inserted as a new pulse to the updated data structure since it does not match with any of the existing pulses. Peak 2 is very similar to Pulse 2, but its bandwidth exceeds the bandwidth of Pulse 2 by more than the bandwidth_hold value so Pulse 2 will be terminated and marked for transfer to the host via the memory I/F 2060, while Peak 2 will be inserted as a new pulse. Finally, Peak 3 matches Pulse 3, within the configured limits (hold values), so the duration of Pulse 3 will be increased by one (FFT cycle) and it will continue until the next FFT cycle's peak data values are checked. Also, the bandwidth of Peak 3 is greater than the existing maximum bandwidth of Pulse 3, so the bandwidth_max value of Pulse 3 in the updated data structure will be changed to 16.
[0166] The pulse data produced by the pulse detector 220′ (transferred to memory from the existing data structure) is passed to a host processor via the memory I/F 2060 and SAgE DPR. A software FIFO is constructed by using a circular list (Clist) maintained by the Clist module 2070 to configure the address range in the DPR, and interrupts to the host to signify the status of the Clist (not empty, above a configured threshold and full).
[0167] The signal pulse data that is output for processing may comprise data for at least one of power, frequency, bandwidth and duration for each signal pulse. Alternatively, or in addition, the signal pulse data may comprise ranges for at least one of power, frequency, bandwidth and duration for each signal pulse. As still another alternative, the signal pulse data may comprise averages for at least one of power, frequency, bandwidth and duration for signal pulses detected over time.
[0168] Some software post processing on the pulse data produced by the pulse detector 220′ may be desirable to clean up the measurements and convert to a more useable format for subsequent processing. In one embodiment, the output data is captured into a software buffer during the course of a dwell time (measurement interval) comprising many FFT sampling cycles, and then processed as a group at the end of the dwell. The processing may include one or more of the following steps:
[0169] Joining pulses that had been fragmented by the SOP/EOP logic described above.
[0170] Joining pulses that may have been broken up by measurement with pulses that start soon after their termination time at a nearby frequency. This is useful in the event fading conditions or modulation variations cause a peak to temporarily drop below the peak threshold, and then subsequently appear with slightly different peak characteristics. It is desirable to be flexible to these variations because the subsequent peak may be part of the same pulse that may have otherwise not been recognized.
[0171] Dropping short pulses. This is useful to compensate for glitches in FFT performance.
[0172] Subsetting the data to coincide with the actual dwell times. Latency of the hardware may cause data to cross over from one dwell interval to another. It may be necessary to separate the data cleanly between their respective dwell intervals.
[0173] Converting to more global measurement units such as converting a weighted average of FFT bins to absolute frequency measurements (in kHz).
[0174] In doing so, a list of pulses (and their associated pulse event data-starting frequency, bandwidth, power and time duration) is produced for a certain time interval of received RF energy. This pulse event list may be used for generating pulse histograms, signal classification (recognizing a type of signal occurring, such as an interferer), for triggering pulse event based alerts and for triggering the timing and application of suitable interference mitigation algorithms when the pulse events are representative of interferer activity with respect to other desired signal or wireless network traffic. Pulse histograms may statistically track distributions of center frequency, bandwidth power and duration of signal pulses detected over time by the SAGE.
[0175] FIG. 11 illustrates exemplary signals and the corresponding pulse event data. There is IEEE 802.11b signal activity consisting of pulses 1-6. Pulses 1, 3 and 5 are the forward channel 802.11b transmissions and pulses 2, 4 and 6 are acknowledgement signals. There is also a frequency hopping signal, such as a Bluetooth™ SCO signal comprising pulses 7-14. The timing, strength and duration of the signals are not shown at precise scale.
[0176] Two pulse detectors are configured in a device where it is expected that an 802.11b signal and a frequency hopping signal would occur. A first pulse detector is configured to detect signals, such as the 802.11 signals, and would have the following parameters:
[0177]
It is possible that the first pulse detector could be configured to detect a pulse on any frequency, but through prior general knowledge that can be acquired by looking at the spectrum statistics, it is possible to determine that an 802.11 signal pulse is occurring at a particular frequency in the frequency band.
| Pulse Bandwidth: | 10 to 20 MHz |
| Center Frequency: | 36-38 MHz (To cover channel 6-2437 MHz) |
| Pulse Duration: | 70 microsec to 20 msec |
| Power: | −30 dBm to −80 dBm |
It is possible that the first pulse detector could be configured to detect a pulse on any frequency, but through prior general knowledge that can be acquired by looking at the spectrum statistics, it is possible to determine that an 802.11 signal pulse is occurring at a particular frequency in the frequency band.
[0178] A second pulse detector is configured to detect signals such as the frequency hopping signal and would have, for example, the following parameters:
[0179]
| Pulse Bandwidth: | less than 2 MHz |
| Center Frequency: | 0 to 83 MHz (i.e., anywhere in the 2.4 GHz band) |
| Pulse Duration: | Up to 1 msec |
| Power: | −50 dBm to −75 dBm |
[0180] Alternatively, the pulse detector 220′ may be configured to detect all of these types of signal pulses. In this case, an SSID associated with detected signal pulses is not necessary.
[0181] Exemplary pulse event data for these pulses are listed below. For simplicity, the time-on data associated with these pulses is omitted.
[0182] Pulse 1
[0183]
| SDID: | 1 (identifying pulse detector 1) | ||
| Pulse Bandwidth: | 11 | MHz | |
| Center Frequency: | 37 | MHz | |
| Pulse Duration: | 1.1 | msec | |
| Power: | −75 | dBm | |
[0184] Pulse 2
[0185]
| SDID: | 1 | ||
| Pulse Bandwidth: | 11 | MHz | |
| Center Frequency: | 37 | MHz | |
| Pulse Duration: | 200 | microsec | |
| Power: | −60 | dBm | |
[0186] Pulse 3
[0187]
| SDID: | 1 | ||
| Pulse Bandwidth: | 12 | MHz | |
| Center Frequency: | 37 | MHz | |
| Pulse Duration: | 1.1 | msec | |
| Power: | −75 | dBm | |
[0188] Pulse 4
[0189]
| SDID: | 1 | ||
| Pulse Bandwidth: | 11 | MHz | |
| Center Frequency: | 37 | MHz | |
| Pulse Duration: | 200 | microsec | |
| Power: | −60 | dBm | |
[0190] Pulse 5
[0191]
| SDID: | 1 | ||
| Pulse Bandwidth: | 13 | MHz | |
| Center Frequency: | 37 | MHz | |
| Pulse Duration: | 18 | msec | |
| Power: | −75 | dBm | |
[0192] Pulse 6
[0193]
| SDID: | 1 | ||
| Pulse Bandwidth: | 11 | MHz | |
| Center Frequency: | 37 | MHz | |
| Pulse Duration: | 200 | microsec | |
| Power: | −60 | dBm | |
[0194] The pulse event data for pulses 7-14 are very similar to each other, with the exception of the center frequency. For example, pulses 7-14 may have a pulse bandwidth of 1 MHz, a pulse duration of 350 microsec, whereas the center frequency will vary across nearly all of the 2400 MHz to 2483 MHz frequency band. The SDID for pulses 7-14 is 2, since pulse detector 2 is configured to detect these types of pulses.
[0195] There are other signal detector functions. One or more pulse detectors 220 or pulse detector 220′ in the signal detector 200 may be configured to monitor pulse activity and the signal detector 200 may send a snapshot buffer trigger signal (SD_SBEVT) to the snapshot buffer 300 when a pulse event occurs corresponding to a configured pulse detector. The signal detector will monitor all pulse detectors and if any one of them detects such an event, the snapshot trigger signal SD_SBEVT is generated, either on the rising edge or falling edge of the detected pulse. The snapshot buffer trigger signal SD_SBEVT will cause the snapshot buffer 300 to capture samples of the DataI and DataQ signals, as described hereinafter.
[0196] Similarly, the signal detector 200 may be configured to monitor activity on each pulse detector 220 or pulse detector 220′ and send a spectrum analyzer trigger signal (SD_SAEVT) to the spectrum analyzer 100 (presumed to be in the transitional mode) when a desired pulse event is detected by any one of the pulse detectors. Again, this spectrum analyzer trigger signal is generated either on the rising edge or falling edge of the detected pulse. The SD_SAEVT signal is coupled to the SA memory controller 190 which will output to the DPR 500 samples (snapshots) of the PDB(k) data fields.
[0197] Turning to FIGS. 12-14 , the stats logic block 170 has modules to accumulate statistics for power, duty cycle, maximum power and a peaks histogram. Statistics are accumulated in the DPR over successive FFT time intervals. After a certain number of FFT intervals, determined by a configurable value stored in the spectrum analyzer control registers, an interrupt is generated to the MCU so that the MCU reads out the stats from the DPR into its memory. For example, the stats are maintained in the DPR for 10,000 FFT intervals before the MCU reads out the values from the DPR.
[0198] FIG. 13 illustrates an example of stats that are accumulated by the stats logic module shown in FIG. 10 . The table on the left side of FIG. 13 illustrates dB power values for exemplary frequencies during time intervals t=0 through 5. The table on the right represents values updated in the DPR for the SumPwr, DutyCnt and MaxPwr statistics at those frequencies. In this example, the peak threshold is −50, and it is assumed that there are essentially three peaks: a first from frequency bin 0 to frequency bin 20; a second from frequency bin 125 to frequency bin 175; and a third from frequency bin 200 to frequency bin 255. All other frequency bins are assumed to be at −100 dB. Though not shown as such, the SumPwr statistic may be averaged by the MCU or another processor, and the DutyCnt may be converted to a percentage number.
[0199] To accumulate power stats, the PDB(k) data field is supplied to the stats logic block 170. It may be decimated by an optional decimator 172. The power at each frequency bin for a previous time interval is added by the adder 174 to the power at that frequency bin for the current time interval. The running power sum at each frequency bin is output to the DPR 500 as a SumPwr stat.
[0200] A duty count stat is generated by comparing the PDB at each frequency bin k with a power threshold (SA_PWRTHRESH) at the adder 176 and MSB block 178. Each time the power at a frequency bin exceeds the power threshold, the previous duty count statistic for that frequency bin is incremented by the increment block 180. The output of the increment block 180 is the duty count stat (DutyCnt), which again, is a running count of the number of times the power at a FFT frequency exceeds the power threshold.
[0201] A maximum power stat (MaxPwr) is tracked at each frequency bin. The current maximum power value at each frequency k is compared to the new power value at each frequency k by the adder 182 and MSB block 183. The multiplexer 184 selects for output either the current power maximum or the new PDB(k), depending on whether the new PDB(k) exceeds the current power maximum at the frequency.
[0202] The number of peaks that are detected by the peak detector during each FFT time interval is counted by the counter 185, buffered in the flip-flop (FF) 186 and stored in the histogram registers 187 for output to the DPR 500. The PEAKEN signal is the output of the peak detector that goes high when a peak is detected. The PKDETSTART signal restarts the counting process for a statistic update cycle.
[0203] FIG. 14 shows exemplary content of the histogram registers 187 including a running count of the number of time intervals (i.e., stats update cycles) that have 0 peaks, 1 peak, 2 peaks, . . . up to 9 peaks. This histogram is useful to estimate the number of different devices or networks operating simultaneously at different frequencies in the frequency band. As shown in FIG. 14 , up until stats update cycle 5, there are two with no peaks, one stats update cycle with one peak and three stats update cycles with three peaks.
The Snapshot Buffer
[0204] The snapshot buffer 300 is a flexible data storage and triggering mechanism used to collect a set of raw ADC samples (DataI and DataQ or DataI′ and DataQ′, FIG. 2 ) for post-processing by the MCU 700. When a snapshot trigger condition is detected, the snapshot buffer 300 buffers up a set of ADC samples and asserts an interrupt to the MCU 700. The MCU 700 may then perform background-level processing on the ADC samples for the purposes of identifying or locating another device operating in the frequency band, or these samples may be passed to a different processor for processing.
[0205] In a pre-store mode, the snapshot buffer 300 writes continuously to the DPR 500 and stops writing and interrupts the MCU when a snapshot trigger signal is detected. In a post-store mode, the DPR write operation begins only after a trigger is detected. A combination pre and post store scenario may be created (using the DELAYSTART and DELAYEND control registers) to capture samples of the receive data signals both before and after a snapshot trigger condition.
[0206] There are two types of snapshot trigger signals supported: SB_TRIG and SD_SBEVT. The snapshot trigger signal SD_SBEVT is sourced from the signal detector 200 as described above, and the SB_TRIG signal is sourced from a module external to the SAGE 10, such as a location measurement module. For example, the MCU 700 may be programmed to collect raw ADC samples when a particular signal pulse is detected for signal classification processes. The MCU 700 configures a pulse detector to generate the snapshot trigger signal SD_SBEVT upon detecting a pulse that meets a certain set of characteristics, as described above. The snapshot buffer 300 clears this bit when it has finished its processing (usually within one clock).
[0207] The snapshot buffer 300 samples may be stored in a variety of formats. One example of a format is one complex sample per 32-bit word. The high-order 16 bits contain the real part of the sample; the low-order 16-bits contain the imaginary part. The real and imaginary parts may be stored in a Q15 format, where 0 represents 0V on the ADC in the RF Interface 800, and 0x7FFF and 0x8000 represent positive and negative full-scale, respectively. A B-bit QN fractional number x takes on the values {n/2N, n=−2B-1, . . . , 2B-1−1}. The B-bit signed integer n=2N*x is used to represent x and is usually stored as a signed, two's complement integer.
[0208] Examples of the control registers (and what they do) for the snapshot buffer are described below.
-
- [0209] DELAYSTART: Number of samples to wait after the SB_TRIG signal before starting to write into DPR. Only valid if CNTRL.PRESTORE=0.
- [0210] DELAYEND: Number of samples to write into DPR before DPR writes are disabled and a “snapshot complete” interrupt is posted to the MCU. The count begins (1) when a trigger condition is asserted in prestore mode, or (2) DELAYSTART samples after a trigger condition in poststore mode.
- [0211] STARTADDR: Address in DPR of first word of snapshot buffer.
- [0212] ENDADDR: Address in DPR of last word of snapshot buffer.
- [0213] WADDR: Starting write address into snapshot buffer (STARTADDR<=WADDR<=ENDADDR). When writing to the snapshot buffer, WADDR is incremented and after a write to ENDADDR, WADDR wraps back to STARTADDR. After a snapshot operation is complete, MCU may use this register to determine the address of the most recent write into the DPR.
- [0214] TSTMP: Contains the TMR_TSTMP value latched immediately after the most recent snapshot trigger condition was asserted.
[0215] The control register includes the fields described below.
-
- [0216] PRESTORE: Trigger prestore mode select. 1=Prestore mode (samples are written continuously to DPR while SB looks for a trigger signal) 0=Poststore mode (samples written to DPR DELAY_START samples after trigger detected).
- [0217] REP: Repetition mode select. 1=Continuous mode—After a trigger signal is detected, immediately start looking for next trigger and continue writing to DPR if prestore mode enabled. STATUS always reads 1 in this mode. 0=One shot mode—Perform one snapshot buffering operation (during which STATUS will set to 1) and set STATUS to zero when done.
- [0218] GO: Begin snapshot buffering operation. When GO is set to 0, SB is idle and does not look for a trigger. When the MCU sets GO to 1, SB starts looking for a trigger signal and prestoring samples in DPR (only if PRESTORE set to 1).
- [0219] STATUS: Status field. 00=SB in idle state due to GO=0.01=Waiting for trigger. Always set to 1 in continuous mode. 10=SB_TRIG detected in one shot mode and snapshot buffering operation complete. 11=SD_SBEVT detected in one shot mode and snapshot buffering operation complete. The SDID field indicates which pulse detector (1-4) caused the trigger.
- [0220] SDID: Indicates which pulse detector caused the trigger condition.
The Dual Port RAM
[0221] The DPR 500 will be described with reference to FIGS. 15-18 .
[0222] Referring first to FIGS. 15 and 16 , the DPR 500 is partitioned into several buffers or storage areas to store information generated by the spectrum analyzer 100, signal detector 200 and snapshot buffer 300. A power vs. frequency circular buffer (PF Buf) 510 stores real-time power vs. frequency information output by the spectrum analyzer 100. The table on the left in FIG. 12 generally resembles the PF Buffer 510. A stats buffer 520 stores SumPwr, DutyCnt, MaxPwr and peaks statistics output by stats logic module. FIGS. 15 and 16 show represented data that is stored by the stats buffer 520. A pulse event circular buffer 530 stores pulse event data output by the pulse detectors in the signal detector 200. A snapshot circular buffer 540 stores raw ADC samples from the snapshot buffer 300. In addition, a buffer 542 stores pulse events output by the pulse detector 220′. Information is exchanged between elements of the SAGE 10 and the DPR 500 via the memory interface (I/F) 550.
[0223] The DPR 500 is, for example, a 32-bit wide, synchronous DPR. Different clocks are used to drive the logic at each port. The CLK signal is used on SAGE components side and the BUSCLK signal is used on the MCU side. The DPR 500 is word addressable from the SAGE side and byte addressable from the MCU side. An AHB bus interface maps an internal MCU byte address into the corresponding word addresses (MDADDR) and byte enable (MDBYTEN) signals attached to the MCU side of the DPR.
[0224] The data structures used to manage the DPR buffers 510-542 are stored in the control registers associated with DPR. The MCU 700 is responsible for configuring the addresses and relative sizes of each buffer using these control registers after reset.
[0225] Referring to FIGS. 17 and 18 , the SAGE 10 uses circular lists to manage some of the data stored in the DPR 500. As indicated above, buffers 510, 530, 540 and 542 use circular lists. A circular list (Clist) consists of a list of fixed sized entries (ClistEntries) and a management structure (ClistMgt). The ClistEntries portion of the list is stored in the DPR 500. Each Clist has an associated ClistMgt structure which resides within the peripheral address space. The DPR location of the ClistEntries is held within ClistMgt. The entry size (ClistMgt.sizeofEntry) of the list is configurable. The Clist is essentially a circular buffer, i.e., a first-in-first-out (FIFO) buffer.
[0226] When performing input/output with a circular list, read and write indices are maintained to indicate the next entry to be read or written. Whenever the end of the list is reached the index is wrapped back to the starting position (i.e., circular list). Whenever a read or write index is wrapped to the starting position, a corresponding read pass number or write pass number is incremented. This combination of index and pass number is called a “position” or ClistPosition. The ClistPosition is, for example, a 32-bit quantity consisting of a 16-bit “pass” and a 16-bit “index.” When the pass number is updated, the entire 32-bit ClistPosition is written out as a single “atomic” operation. Similarly, a read operation reads the entire 32-bit ClistPosition to ensure the pass number and index components are consistent when wrap occurs.
The Universal Signal Synchronizer
[0227] The universal signal synchronizer 400 is useful to lock to interfering periodic signal sources. The USS 400 consists of multiple programmable clock generators referred to as USS clock modules (UCMs) 410. The MCU 700 can detect interference from a periodic signal source such as a Bluetooth™ headset, a cordless phone, etc., by examining traffic statistics gathered by the host communication device. For example, the MAC logic 750 will accumulate traffic statistics indicating how successful the host communication device has been in transmitting to and receiving information from other devices according to a MAC protocol, such as IEEE 802.11x, employed by the device. Traffic statistics that may reveal the presence of an interferer are: (1) un-acknowledged messages; (2) repeated cyclic redundancy code (CRC) errors; (3) low received signal strength, etc. For example, the fact that several messages are sent from the device that are not acknowledged by the intended destination device is very revealing of interference in the frequency band.
[0228] When the MCU determines to look for the cause of the interference, it configures the appropriate frequency and phase parameters corresponding to the interference source into a UCM 410, and, using pulse timing information from the signal detector 200, phase/frequency locks the UCM timing to the transmit timing for the interference source. After phase/frequency lock has taken place, the UCM can be used as a timing reference to prevent data transmissions to/from the MAC logic 750 (FIG. 1 ) from overlapping and interfering with data exchanges with the interference source.
[0229] A block diagram of a UCM 410 is shown in FIG. 19 . A timing diagram for an exemplary interferer, such as a Bluetooth™ signal, is shown in FIG. 20 . Each UCM clock interval consists of two on/off segments (on=logic 1, off=logic 0), the duration of which is specified by the DurOn1, DurOff1, DurOn2, and DurOff2 registers 412, 414, 416 and 418, respectively. The two segment UCM clock scheme is used to accommodate interference sources such as Bluetooth SCO links that exchange bidirectional data using two unequally-spaced pulses, as shown in FIG. 19 . A multiplexer 420 selects input from one of the registers 412 through 418, where selection from register 418 is via an adder 422 coupled between the register 418 and an input to the multiplexer 420.
[0230] A down counter 424 is connected to the output of the multiplexer 420 and counts down from the duration of each duration segment. A mod(N) counter 426 is connected to the down counter 424 and is used to reload the down counter 424 with the duration of the next segment after the down counter 424 counts down to zero. For the case shown, the mod(N) counter 426 is a mod4 counter. An accumulator 428 is coupled to the mod4 counter 424 and has a carry output that is coupled back to the adder 422. The most significant bit (MSB) output of the mod4 counter 426 is used to drive the count input of the accumulator 428. The accumulator 428 is a Z bit accumulator used to offset the UCM clock frequency, advancing or delaying the UCM clock by one TMR_CLK cycle every 2Z/freqOffset UCM cycles, where the freqOffset parameter is configurable by the MCU via an adder 430 coupled to the accumulator 428. There is a phaseOffset register 425 and a freqOffset register 427 that the MCU writes to for the purposes explained hereinafter.
[0231] In general, the clock module comprises at least N registers, each of which stores a programmable duration value associated with one of two states of a pulse of the communication signal, where N is equal to 2 times the number of pulses in a cycle of the communication signal, and the mod(N) counter coupled to the down counter counts up to N−1 by one in response to the down counter reaching zero and when reaching N−1, causing content of the next of the N registers to be loaded into the down counter. The count input of the Z-bit accumulator 428 is coupled to an output of the mod(N) counter, and the adder 430 adds an output of the accumulator 428 with the frequency offset value and supplies the sum to an input of the accumulator, wherein a carry output of the accumulator is coupled to the Nth register to increment or decrement the value of the Nth register before it is loaded into the counter, thereby extending or contracting the length of a cycle of the clock signal used to drive the down counter by one clock pulse every 2Z/(frequency offset value) clock cycles.
[0232] A UCM TMR_CLK frequency of fTMR— CLK=2 MHz provides sub-microsecond timing granularity on the pulse duration intervals. An 18-bit register size for the duration registers 412-418 accommodates transmission frequencies as low as 10 Hz. A 16-bit (Z=16) accumulator is suitable for the accumulator 428 to provide less than 0.01 ppm frequency resolution for a UCM clock frequency of 1 kHz. The following additional characteristics may apply to the UCM 410 shown in FIG. 19 :
[0233] Output frequency=fCLK/[(M+freqOffset)/216]≈fCLK/M{1−(freqOffset/M216)}Hz, where M=DurOn1+DurOff1+DurOn2+DurOff2.
[0234] Frequency Resolution≈fCLK/(M2216) Hz=106/(M216)
[0235] Output clock frequency range: 1.9 Hz (DurOn1=DurOff1=DurOn2=DurOff2=218−1) to 500 kHz (DurOn1=DurOff1=DurOn2=DurOff2=1)
[0236] When the MCU 700 detects and classifies a periodic interference source, it takes the following steps to lock the UCM timing to the transmission timing associated with the interference source.
[0237] First, the MCU initializes and configures a UCM 410 to the appropriate (nominal) frequency using the DurOn and DurOff registers and it sets the content of the freqOffset register 425 to zero. The MCU writes values to the duration registers based on knowledge gained about the interferer from pulse events output by a pulse detector 220 (FIG. 3 ) and/or from snapshot buffer data supplied to the MCU that lead to the MCU determine that there is an interference event. The MCU also associates a pulse detector with the UCM 410 and configures the pulse detector to measure the phase offset between the interference source and the UCM 410. During the synchronization process, information about the timing of the interferer signal is obtained from pulse events generated by the assigned pulse detector, and the MCU compares them against the duration values written into the duration registers. The pulse events include the count values of the down counter and the mod(N) counter at the detection of a pulse, as described above in connection with the description of the signal detector.
[0238] The MCU examines the count values of the down counter and the mod(N) counter to measure a phase error between the clock signal that drives the down counter and the occurrence of the pulse of the communication signal. The MCU removes the initial phase offset/error between the UCM 410 and the interference source by loading a phase adjustment value into the PhaseOffset register 425. This causes the UCM 410 to retard the phase by the value specified in the PhaseOffset register 425 the next time the down counter 424 and mod4 counter 426 cycle to zero.
[0239] After removing the initial phase offset, the MCU periodically monitors the phase count values of the down counter and the mod(N) counter in the pulse event data to measure the phase error. The MCU generates a frequency offset between the interference source (from the pulse detector) and the UCM clock and updates the FreqOffset register 427 to compensate for frequency drift between the two signals. A block diagram of an update technique using a second order phase lock loop (PLL) is shown in FIG. 19 , which will be described hereinafter. The MCU writes a value into the FreqOffset register that causes the accumulator 428 to retard or advance (depending on the sign of the adder 422) the frequency a certain number of times per UCM clock cycles.
[0240] When the phase offset samples converge to zero, the UCM is said to be phase/frequency locked to the interference source. Once the loop is locked, the MCU may let the UCM clock “flywheel” for a period of time without monitoring the phase offset from the interference source. The MCU may continue to periodically monitor the phase offset and update the loop parameters since the clocks will eventually drift (primarily due to temperature changes in the near and far end reference oscillators). A good rule of thumb to use for estimating the drift rate in this case is ½ microsecond per second, assuming an oscillator with +/−20 ppm of variation over 70 degrees C. ( 4/7 ppm per degree C.), and 3 degrees F=1.7 degrees C. temperature variation over 5 minutes (due to air conditioner hysteresis, etc.).
[0241] Reference is now made to FIG. 21 , which shows a process 440 useful by the MCU to update for clock drifts. The process 440 updates the frequency offset between the clock of the interfering signal and the local clock operating the UCM. Step 442 represents the pulse detector 220, associated with the particular interfering signal, generating phase information by reading the states of down counter 424 and mod(N) counter 426, and step 444 represents retrieving of information from the pulse event circular list in the pulse event buffer 530 of the DPR 500. Multiple pulse events from the signal detector 200 may be buffered up in the DPR 500 before the MCU has time to retrieve them. Next, in step 446, the phase detection information is updated depending on the value of the down counter 424 relative to the value of the DurOn1 register 412. If the down counter value 424 is less than the value of DurOne1 divided by 2, then the phase detection information is set equal to the value of the down counter 424. Otherwise, the phase detector information is set equal to the value of the down counter 424 less the value of the DurOn1 register 412. In step 448, output of step 446 is averaged to reduce noise effects. Next, a filter or phase-lock-loop (PLL) process 449 is performed to lock to the phase and frequency of the interfering signal clock. Any suitable first-order or second-order filtering or PLL process can be used. FIG. 21 shows a second order PLL process comprising two scaling operations 450 and 452, an adder 454, a z−1 block 456 and an accumulator 458. The parameters k1 and k2 are PLL constants that depend on the UCM clock rate and a buffering factor of the pulse event circular list in the DPR. The output of the process 440 is a frequency offset value that is stored for later use in synchronizing to the near clock and the far-end clock (that of the particular interfering signal). Once the frequency offset value is computed, the interfering signal can be ignored for a period of time, and the UCM can more quickly lock to the interfering signal by loading the stored frequency offset (FreqOffset) into the FreqOffset register 427 of the UCM as shown in FIG. 19 .
[0242] Examples of the registers used to control and monitor a UCM 410 from the MCU are described below.
-
- [0243] DURON1: Duration in TMR_PULSE cycles of first “on” interval of a UCM clock cycle. The MCU may update this value anytime (regardless of whether the UCM is enabled).
- [0244] DUROFF1: Duration in TMR_PULSE cycles of first “off” interval of a UCM clock cycle. The MCU may update this value anytime (regardless of whether the UCM is enabled).
- [0245] DURON2: Duration in TMR_PULSE cycles of second “on” interval of a UCM clock cycle. The MCU may update this value anytime (regardless of whether the UCM is enabled).
- [0246] DUROFF2: Duration in TMR_PULSE cycles of second “off” interval of a UCM clock cycle. The MCU may update this value anytime (regardless of whether the UCM is enabled).
- [0247] FREQOFFSET: Creates a frequency offset of (FTMR
— PULSE*FREQOFFSET)/(M2*216) Hz relative to the nominal clock frequency (FTMR— PULSE/M) on the UCM clock. The CNTRL.FOFFSET bit specifies the sense of the offset. If CNTRL.FOFFSET=1, a positive frequency offset is applied, otherwise a negative frequency offset is applied (a positive frequency offset corresponds to a higher-than-nominal UCM clock frequency). The MCU may update this value anytime (regardless of whether the UCM is enabled). - [0248] PHASEOFFSET: Retards the phase of the UCM clock by
- [0249] PHASEOFFSET TMR_PULSE cycles by loading the value
- [0250] PHASEOFFSET into the Down Counter at the end of the next Dur1Off interval. The phase adjustment is made once each time the PHADJUST bit in the CNTRL register is set.
- [0251] MINGAP: If the time between two consecutive interference events on the UCM signals specified by USS_SELECT is less than MINGAP TMR_PULSEs, the USS will merge the two events and report on them as if they were one interference event spanning both interference pulse durations.
- [0252] DOWNCTR: Contents of UCM down counter register (updated once per TMR_PULSE)
[0253] The fields of the control register for a UCM are defined below.
-
- [0254] ENABLE: UCM enable. Setting the ENABLE bit for 1 TMR_PULSE cycle causes the clock to start counting in the Dur1Off state. Clearing ENABLE for 1 or more TMR_PULSEs causes the UCM clock to stop counting.
- [0255] PHADJUST: Writing a 1 to this bit causes the UCM to retard its clock phase by PHASEOFFSET TMR_PULSE cycles by loading the value
- [0256] PHASEOFFSET into the Down Counter at the end of the next Dur1Off clock segment. The UCM clears this bit after the phase change has taken place.
- [0257] FOFFSET: Specifies whether a positive or negative frequency offset is to be applied using the FREQOFFSET field. 1=Positive frequency offset applied. 0=negative frequency offset applied
- [0258] MOD4CT: Contents of Modulo 4 counter
[0259] The USS 400 passes UCM timing information to an external component, such as the MAC logic 750, using the NEXTINTFDUR and NEXTINTFTIME signals described hereinafter. The USS_SELECT signals, also described in the table above, allow for selection of which UCMs to include in next event calculation.
Other Interfaces to the SAGE
[0260] With reference to FIG. 1 , other interfaces to the SAGE 10 will be described. The global timer interfaces (GTI) are used by the spectrum analyzer 100 and signal detector 200 to timestamp transmission events in the sampled frequency band. The GTI comprises, for example, the timestamp signal (TMR_TSTMP) and a global timer clock signal (TMR_PULSE), where TMR_PULSE=1 on the positive edge of BUSCLK indicates a new value of TMR_TSTMP. The GTI logic runs at the BUSCLK clock frequency. The TMR_TSTMP field is updated periodically, such as at 2 MHz, during BUSCLKs in which TMR_CLK=1.
[0261] The SAGE 10 communicates timing information for periodic interference sources (such as Bluetooth headsets or cordless phones) to another hardware element (external to the SAGE 10), such as the MAC logic 750. There are primarily three MAC interface signals, USS_SELECT, NEXTINTFDUR and NEXTINTFTIME. NEXTINTFDUR is the duration in TMR_PULSEs of the next interference event among the selected UCM clocks via USS_SELECT. The interference condition is said to be active (due to an interferer's transmission) when any of the selected UCM clocks is high. When all of the selected interference sources are inactive (i.e., all UCM clocks are low), NEXTINTFDUR indicates the duration of the next interference event in TMR_PULSEs. When at least one of the interference sources is active, NEXTINTFDUR indicates the time in TMR_PULSEs until the end of the current interference transmission, and is updated once per TMR_PULSE.
[0262] NEXTINTFTIME is the time remaining in TMR_PULSEs until the next interference event among the selected UCM clocks via USS_SELECT. The interference condition is said to be active (due to an interferer's transmission) when any of the selected UCM clocks is high. When all of the selected interference sources are inactive, NEXTINTFTIME indicates the time until the next interference event and is updated once per TMR_PULSE. When at least one of the interference sources is active, NEXTINTFTIME reads zero.
[0263] USS_SELECT is a signal that selects which USS UCMs 410 to include in the next interference event calculations, as reported to the MAC logic 750 through the NEXTINTFXXX signals. USS_SELECT[i]=1 means include UCM(i) in the calculation.
[0264] Examples of MCU interface signals are described below. Some of these signals are identified in FIGS. 1 , 3 and 6.
-
- [0265] ADDR: Control register word address
- [0266] BUSCLK: Clock used to control the MCU side of the DPR, USS, Lower
- [0267] MAC and Global Timer interfaces:
- [0268] IRQ: Level-triggered interrupt request to MCU. Whenever an enabled interrupt condition becomes active, SAGE 10 asserts an interrupt to the
- [0269] MCU by setting IRQ to 0. The MCU clears the interrupt by clearing the appropriate bits in the IF register. SAGE automatically sets IRQ to 1 when all active interrupt conditions have been cleared in the IF register.
- [0270] MDADDR: DPR word address—MCU side
- [0271] MDBYTEEN: DPR byte enable—MCU side
- [0272] MDRD: DPR read strobe—MCU side
- [0273] MDRDATA: DPR read data—MCU side
- [0274] MDWR: DPR write strobe—MCU side
- [0275] MDWDATA: DPR write data—MCU side
- [0276] RD: Control register read strobe
- [0277] RDATA: Control register read data
- [0278] SDADDR: DPR word address—SAGE side
- [0279] SDRD: DPR read strobe—SAGE side
- [0280] SDRDATA: DPR read data—SAGE side
- [0281] SDWR: DPR write strobe—SAGE side
- [0282] SDWDATA: DPR write data—SAGE side
- [0283] WR: Control register write strobe
- [0284] WDATA: Control register write data
Operation and Uses of the SAGE
[0285] With reference to FIG. 22 , one example of how the SAGE 10 may be operated is described. The SAGE 10 may reside in a communication device that comprises the radio transceiver 600 and a MCU 700. In addition, for higher level processing, a host processor 900 may also be provided that is coupled to the MCU 700. The MCU 700 and host processor 900 may share responsibility for configuring the SAGE 10 and the radio transceiver 600. The host processor 900 may be responsible for more complex functions. However, it should be understood that the functions of the MCU 700 and the host processor 900 may be executed by a single processor of suitable processing capability and power consumption characteristics. The radio transceiver 600 is shared by the SAGE 10 and other communication device functions, such as receiving signals from or transmitting signals to another communication device.
[0286] There are many ways to employ the features and functions of the SAGE 10, some examples of which are explained. The MCU 700 or the host processor 900 may be programmed to configure the receiver portion of the radio transceiver 600 to operate in a wideband mode, thereby sampling activity in an entire frequency band for a time period, such as 100 msec or longer. In addition, the MCU 700 or host processor 900 may configure certain basic parameters of the SAGE 10, such as the decimator factor, the cycle count of the number of spectrum analyzer updates (i.e., FFT intervals) before forwarding the stats to the MCU 700, the minimum power threshold for duty counting, the lowpass filter parameter of the spectrum analyzer. The receiver portion of the radio transceiver 600 may also be configured to operate in a narrowband mode at a configurable center frequency and bandwidth.
[0287] While the radio transceiver 600 is operated in a wideband mode, the SAGE 10 is activated to “sniff” the spectrum with the spectrum analyzer component of the SAGE 10. The spectrum analyzer stats, such as those shown in FIGS. 12 and 13 , are accumulated in the DPR and read by the MCU 700 and further processed by the host processor 900. During this sniff mode, the pulse detectors of the signal detector component may be configured in a default mode to look for signal pulses of commonly expected signals in the frequency band. In the case of an unlicensed frequency band, such signals may include an IEEE 802.11 signal, a cordless phone signal, or a Bluetooth™ frequency hopping signal. Alternatively, during the sniff mode the output of the pulse detectors may be completed ignored and the spectrum analyzer stats processed to determine generally what is happening in the frequency band. Based on intelligence gathered by the spectrum analyzer stats generated from the sniff mode, the host processor 900 or MCU 700 may configure one or more pulse detectors of the SAGE 10 to look for certain types of signal pulses in the frequency band using the pulse detector configuration parameters described above.
[0288] Still another possibility is to iteratively change the configuration of one or more pulse detectors so as to cycle through pulse detector configurations over time. For example, the center frequency, bandwidth, pulse duration and/or time between pulses parameters can be changed to process incoming signal data. The incoming signals are processed during each cycle with the one or more pulse detectors. Eventually, by cycling through different pulse detector configurations, the goal is to eventually find a pulse detector configuration that fits the type of signal activity occurring in the frequency band. This is useful, for example, in a signal classification process.
[0289] Further operation of the SAGE to gather output from the signal detector may occur while the radio is in a wideband mode or a narrowband mode, depending on the demands of the radio for communication services and the type of signals suspected to be present in the frequency band. Whether configured based on information gathered from a sniff mode, or operated using predetermined configuration information, the pulse detectors will generate pulse event information that is output to the MCU 700, together with spectrum analyzer stats and any snapshot buffered data. In addition, the universal signal synchronizer component of the SAGE 10 may be operated by the MCU to synchronize to the clocks of potentially interfering communication signals in the frequency band. This synchronization information can be used in an interference mitigation or co-existence algorithm executed by the MCU 700 or the host processor 900 to schedule transmissions by the communication device so as to avoid collisions with other communication signals in the frequency band.
[0290] In addition, the output of the SAGE 10 can be used in a signal classification process to identify/classify signals in a frequency band, such as for example: a wireless headset operating with a frequency hopping communication protocol (e.g., Bluetooth™); wireless file/print services; radar systems; microwave ovens, an IEEE 802.11 wireless local area network; a HomeRF™ network; a FHSS cordless phone; an analog cordless phone; wireless infant/security monitors; devices operating using the IEEE 802.15.3 communication protocol. A signal classification process is disclosed in the aforementioned commonly assigned patent application.
[0291] FIG. 23 illustrates another example of a use of the SAGE 10. In this example, the SAGE 10 is deployed together with the DPR 500 and radio I/F 800. These components may be implemented in a field programmable gate array together with a cardbus interface 570. The cardbus interface 570 may interface with various card-slot types, such as Type II PC-Card slot. The SAGE 10 is used by a host device 1000 that has a host processor 900 as well as other components. A display monitor 1100 may be coupled to the host device 1000. The host device 1000 may be, for example, an access point for a wireless local area network, in which case it would have the requisite radio transceiver and baseband signal processing components. Alternatively, the host device 1000 may be a desktop or notebook personal computer or personal digital assistant. A memory 910 in the host device may store a software programs for controlling the use of the SAGE 10 and one or application programs for using the output of the SAGE 10. In addition, the memory may store driver software for the host device, such as drivers for operating systems such as Windows operating systems (Windows® XP, Windows® CE, etc.).
[0292] One or more radio receivers may be coupled to the radio I/F 800. For example, one radio receiver 610 may be dedicated to one frequency band (such as the 2.4 GHz unlicensed band) and another radio receiver 620 may be dedicated to another frequency band (such as the 5 GHz unlicensed bands). Each radio receiver 600 and 610 may have the capability of operating in a wideband mode for purposes of downconverting energy in the entire frequency band for a time interval. An example of a radio receiver is identified above. A switch 630 selects the baseband analog output from one of the radio receivers, and couples it to an ADC 640, which is in turn coupled to the radio I/F 800. The DAC 650 is used to couple control signals to the radio receivers to, for example, control the bandwidth of operation of the radio receiver for wideband or narrowband operation. The dotted block around the radio receivers 610 and 620, the ADC and DAC, the SAGE 10, the DPR, and the radio I/F in FIG. 23 is meant to indicate that these components may integrated in a PC card device, such as a PC-card that interfaces with the host device 1000. Thus, the card device essentially is a spectrum analyzer device and much more for a radio frequency band, that interfaces to a host device 1000. The two radios 610 and 620 may optionally be implemented by a single multi-band radio. The DAC 650 may also be unnecessary.
[0293] In this use of the SAGE 10, the host processor 900 performs the functions that are otherwise performed by the MCU 700 to control, and interface with, the SAGE 10, as well as other functions. One use of the SAGE 10 is to display the various outputs of the SAGE 10. For example, an application program residing in the memory 910 of the host device 1000 may generate a graphic user interface display of the SAGE output.
[0294] Moreover, the radio I/F 800, SAGE 10 and DPR 500 are shown in phantom to indicate that all of the functions of these components may be performed by a software program stored in the memory 910 and executed by the host-processor 900. In this configuration, the output of the ADC 640 is coupled through an interface, such as the cardbus interface 570 to the host processor 900, which executes processes that would otherwise be performed in hardware by the SAGE 10, as well as the other processes referred to above.
[0295] In sum, a method is provided for detecting signal pulses from received radio frequency (RF) energy, comprising steps of: storing peak data describing at least one of frequency, bandwidth and power for each of one or more peaks of RF energy; comparing the peak data for one or more peaks detected for a current sampling cycle with the peak data for one or more peaks detected during a previous sampling cycle; and based on the step of comparing, storing a list of signal pulses representing the occurrence of peaks having similar peak data over multiple sampling cycles. The step of comparing may comprise matching peaks (with respect to frequency, bandwidth and power) for the current sampling cycle with the data in the list of signal pulses. The list of signal pulses is updated with data for a peak that matches data for a signal pulse in the list to thereby (a) extend a duration the signal pulse for a period of time corresponding to the sampling cycle; (b) add new signal pulse data the list for a peak associated with the current sampling cycle; or (c) terminate a signal pulse in the list.
[0296] Similarly, a signal pulse detector is provided that detects signal pulses from received radio frequency (RF) energy, comprising a peak calculation module that computes peak data describing at least one of frequency, bandwidth and power for each of one or more peaks of RF energy that exceed a power threshold and a minimum bandwidth threshold during each of a plurality of sampling cycles; a first memory that stores an incoming peak list comprising peak data for one or more peaks detected for a current sampling cycle; and a pulse comparison module coupled to the first memory, and which compares the peak data in the incoming peak list with existing pulse data to determine whether to (i) extend an existing pulse; (2) terminate an existing pulse; or (3) add a new pulse to the existing pulse data. A second memory may be provided that stores the existing pulse data in an existing pulse list for signal pulses determined to occur based on peak data in the incoming peak list, and that stores an updated pulse list containing changes to the existing pulse list based on comparison of data in the incoming peak list for the current sampling cycle with the pulse data in the existing pulse list.
[0297] The signal pulse detector may be part of a spectrum analysis system that includes a Fast Fourier Transform (FFT) block that receives as input a digital signal representing received RF energy and computes FFT values for a plurality of frequency bins for a time interval; a power calculation block coupled to the FFT block that computes the power at each frequency bin at each time interval; a peak detector that receives as input an output of the power calculation block for successive time intervals, detects one or more peaks in the output of the power calculation block and outputs data describing peaks of RF energy for each time interval; and a statistics computation module coupled to the power calculation module that computes one or more of a running sum of the power at each frequency bin over time intervals; a duty count comprising a running sum at each time interval of the number of times the power at each frequency bin exceeds the power threshold; a maximum power for each frequency bin for the current and prior time intervals; and a running count of the number of time intervals in which a certain number of peaks have been detected.
[0298] A method is provided for use in a radio communication device that operates in a frequency band, the method for analyzing activity in the frequency band based on signals received by the communication device, comprising steps of: computing Fast Fourier Transform (FFT) values at a plurality of frequency bins from a digital signal representing activity in a frequency band during a time interval; computing the power at each frequency bin; adding the power at each frequency bin for a current time interval with the power at the corresponding frequency bin for a previous time interval to obtain a running sum of the power at each frequency bin; comparing the power at each frequency bin with a power threshold to obtain a duty count of the number of times that the power at each frequency bin exceeds the power threshold over time intervals; and comparing the power at each frequency bin for a current time interval with the power at the corresponding frequency bin for a previous time interval to track the maximum power in each frequency bin over time intervals. This process may also be implemented by instructions encoded on a processor readable medium that, when executed by a processor, cause the processor to perform these same steps.
[0299] Still further provided is a spectrum analysis device for use in a radio communication device that operates in a frequency band, comprising a Fast Fourier Transform (FFT) block that receives as input a digital signal representing activity in the frequency band for a time interval, wherein the FFT block computes FFT values for each of a plurality of frequency bins from the digital signal; a power calculation block that computes the power at each frequency bin and outputs a power data field comprising power values for the plurality of frequency bins; and a signal detector circuit. The signal detector circuit comprises a peak detector that receives as input the power data field for successive time intervals of activity in a frequency band, and detects one or more peaks in the spectral information, the peak detector outputting information identifying peaks for each time interval; and at least one pulse detector coupled to the peak detector that detects signal pulses that satisfy configurable characteristics based on the output of the peak detector.
[0300] Still further provided is a method for detecting radio signals in a frequency band comprising steps of operating a radio receiver in a wideband mode so as to generate a downconverted signal representing activity in the entire frequency band; performing spectral analysis on the downconverted signal to generate spectral information of the frequency band; and detecting signal pulses of signals expected to be present in the frequency band from the downconverted signal based on knowledge gained from the spectral information of the frequency band.
[0301] Yet further provided is a processor readable medium encoded with instructions that, when executed by a processor, cause the processor to perform steps of computing a Fast Fourier Transform (FFT) values for each of a plurality of frequency bins from a digital signal representing activity in a frequency band for a time interval; computing the power at each frequency bin from the FFT values; detecting one or more peaks from the FFT values; and detecting signal pulses that meet one or more characteristics from the detected one or more peaks.
[0302] The above description is intended by way of example only and is not intended to limit the present invention in any way.
Claims
What is claimed is:
1. A method comprising:
in a radio receiver device configured to receive radio frequency (RF) energy, storing peak data describing spectral characteristics comprising frequency location and bandwidth for each of one or more spectral peaks of RF energy detected by the radio receiver device over sampling cycles;
in the radio receiver device, comparing the peak data for one or more peaks detected for a current sampling cycle with the peak data for one or more peaks detected during a previous sampling cycle;
in the radio receiver device, based on said comparing, storing a list of signal pulse data describing one or more identified signal pulses, where a signal pulse of said one or more identified signal pulses comprises a sequence of spectral peaks having similar spectral characteristics over multiple time intervals; and
updating the list by extending a duration of an existing signal pulse in the list with data for a spectral peak that has spectral characteristics which match data an existing signal pulse in the list, adding data for a new signal pulse to the list, or modifying the list to indicate termination of an existing signal pulse in the list.
2. The method of claim 1, and further comprising in the radio receiver device, detecting peaks of RF energy as power values above a power threshold at a set of frequencies.
3. The method of claim 2, wherein detecting peaks comprises detecting peaks of RF energy as power values above the power threshold at a set of contiguous frequencies.
4. The method of claim 3, wherein detecting peaks comprises comparing power values at a plurality of frequencies with the power threshold, wherein the power threshold for the comparison at a particular frequency may vary with a power level at a frequency near the particular frequency.
5. The method of claim 1, wherein storing peak data comprises storing data describing one or more of a lefthand frequency, a center frequency and a righthand frequency, of each of the one or more peaks.
6. The method of claim 1, wherein comparing comprises comparing frequency location, bandwidth and power of peak data for one or more peaks associated with the current sampling cycle with frequency location, bandwidth and power of signal pulses in the list.
7. The method of claim 1, and further comprising joining signal pulse data in the list for similar pulses that may have been broken up due to signal fading and other conditions.
8. The method of claim 1, and further comprising in the radio receiver device storing digital signals representing samples of received RF energy when a signal pulse is detected.
9. A signal pulse detector that detects signal pulses from received radio frequency (RF) energy, comprising:
a peak computation circuit that computes peak data describing frequency location and bandwidth for each of one or more peaks of RF energy detected over a plurality of sampling cycles;
a first memory that stores the peak data for one or more peaks detected for a current sampling cycle; and
a comparator circuit coupled to the first memory, and which compares the peak data with existing pulse data to determine whether to (1) extend an existing pulse; (2) terminate an existing pulse; or (3) add a new pulse to the existing pulse data.
10. The signal pulse detector of claim 9, and further comprising a second memory that stores the existing pulse data in an existing pulse list for signal pulses determined to occur based on peak data stored in the first memory, and that stores an updated pulse list containing changes to the existing pulse list based on comparison of data in the first memory for the current sampling cycle with the existing pulse data in the existing pulse list.
11. The signal pulse detector of claim 9, wherein the peak computation circuit and the comparator circuit are implemented by digital logic gates.
12. The signal pulse detector of claim 9, wherein the peak computation circuit, the comparator circuit and the first memory are implemented in an integrated circuit.
13. The signal pulse detector of claim 9, and further comprising a memory that stores one or more of:
a. a running sum of the power at each frequency bin over time intervals;
b. a duty count comprising a running sum at each time interval of the number of times the power at each frequency bin exceeds the power threshold;
c. a maximum power for each frequency bin for the current and prior time intervals; and
d. a running count of the number of time intervals in which a certain number of peaks have been detected.
14. A system comprising the signal pulse detector of claim 9, and further comprising a memory controller coupled to the comparator circuit, wherein the signal pulse detector outputs a trigger signal in response to detecting a signal pulse thereby causing the memory controller to store digital samples of received RF energy for a time interval in a memory.
15. The system of claim 14, wherein the memory controller writes a timestamp identifying a time associated with an occurrence of the trigger signal.
16. The signal pulse detector of claim 9, and further comprising a memory interface circuit that outputs the existing pulse data to a memory.
17. A system comprising the signal pulse detector of claim 16, and further comprising a processor coupled to the memory that processes the existing pulse data stored in the memory.
18. The system of claim 17, wherein the processor joins pulse data for similar pulses that may have been broken up due to signal fading and other conditions.
Patent Citations (67)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3992666(A) | 1976-11-01 | Edwards et al. | Applicant |
| US4054785(A) | 1977-10-01 | Lehmann | Applicant |
| US4084245(A) | 1978-04-01 | Bunge | Applicant |
| US4166980(A) | 1979-09-01 | Apostolos et al. | Applicant |
| US4227255(A) | 1980-10-01 | Carrick et al. | Applicant |
| US4336541(A) | 1982-06-01 | Tsui et al. | Applicant |
| US4501020(A) | 1985-02-01 | Wakeman | Applicant |
| US4597107(A) | 1986-06-01 | Ready et al. | Applicant |
| US4818949(A) | 1989-04-01 | Cohen | Applicant |
| US4839582(A) | 1989-06-01 | Fukaya et al. | Applicant |
| US4947338(A) | 1990-08-01 | Vistica | Applicant |
| US4950999(A) | 1990-08-01 | Agnello et al. | Applicant |
| US4965759(A) | 1990-10-01 | Uchida et al. | Applicant |
| US5005210(A) | 1991-04-01 | Ferrell | Applicant |
| US5144642(A) | 1992-09-01 | Weinberg et al. | Applicant |
| US5210820(A) | 1993-05-01 | Kenyon | Applicant |
| US5230087(A) | 1993-07-01 | Meyer et al. | Applicant |
| US5271036(A) | 1993-12-01 | Lobert et al. | Applicant |
| US5303262(A) | 1994-04-01 | Johnson | Applicant |
| US5323337(A) | 1994-06-01 | Wilson et al. | Applicant |
| US5432862(A) | 1995-07-01 | Hirsch | Applicant |
| US5436556(A) | 1995-07-01 | Komninos | Applicant |
| US5565764(A) | 1996-10-01 | Priebe et al. | Applicant |
| US5574979(A) | 1996-11-01 | West | Applicant |
| US5697078(A) | 1997-12-01 | Peterson et al. | Applicant |
| US5706202(A) | 1998-01-01 | Itahara et al. | Applicant |
| US5745777(A) | 1998-04-01 | English et al. | Applicant |
| US5808463(A) | 1998-09-01 | Nagano | Applicant |
| US5905949(A) | 1999-05-01 | Hawkes et al. | Applicant |
| US5956638(A) | 1999-09-01 | Chang et al. | Applicant |
| US6084919(A) | 2000-07-01 | Kleider et al. | Applicant |
| US6130907(A) | 2000-10-01 | Chen | Applicant |
| US6198779(B1) | 2001-03-01 | Taubenheim et al. | Applicant |
| US6229997(B1) | 2001-05-01 | Addy | Applicant |
| US6229998(B1) | 2001-05-01 | Hamdy et al. | Applicant |
| US6233529(B1) | 2001-05-01 | Nonaka | Applicant |
| US6349198(B1) | 2002-02-01 | Carlson et al. | Applicant |
| US6374082(B1) | 2002-04-01 | Carlson | Applicant |
| US6385434(B1) | 2002-05-01 | Chuprun et al. | Applicant |
| US6408696(B1) | 2002-06-01 | Jong | Applicant |
| US6484111(B1) | 2002-11-01 | Nara | Applicant |
| US6509728(B1) | 2003-01-01 | Uchino et al. | Applicant |
| US6512788(B1) | 2003-01-01 | Kuhn et al. | Applicant |
| US6584419(B1) | 2003-06-01 | Alexander | Applicant |
| US6711134(B1) | 2004-03-01 | Wichelman et al. | Applicant |
| US6714605(B2) | 2004-03-01 | Sugar et al. | Applicant |
| US6850735(B2) | 2005-02-01 | Sugar et al. | Applicant |
| US7035593(B2) | 2006-04-01 | Miller et al. | Applicant |
| US7116943(B2) | 2006-10-01 | Sugar et al. | Applicant |
| US7224752(B2) | 2007-05-01 | Sugar et al. | Applicant |
| US7292656(B2) | 2007-11-01 | Kloper et al. | Examiner |
| US2001/0055952(A1) | 2001-12-01 | Ficarra | Applicant |
| US2002/0086641(A1) | 2002-07-01 | Howard | Applicant |
| US2002/0142744(A1) | 2002-10-01 | Okanoue et al. | Applicant |
| US2002/0154614(A1) | 2002-10-01 | Jagger et al. | Applicant |
| US2002/0155811(A1) | 2002-10-01 | Prismantas et al. | Applicant |
| US2002/0177446(A1) | 2002-11-01 | Bugeja et al. | Applicant |
| US2003/0050014(A1) | 2003-03-01 | Cain | Applicant |
| US2003/0067662(A1) | 2003-04-01 | Brewer et al. | Applicant |
| US2003/0123420(A1) | 2003-07-01 | Sherlock | Applicant |
| US2003/0198200(A1) | 2003-10-01 | Diener et al. | Applicant |
| US2003/0198304(A1) | 2003-10-01 | Sugar et al. | Applicant |
| US2003/0224741(A1) | 2003-12-01 | Sugar et al. | Applicant |
| US2004/0028123(A1) | 2004-02-01 | Sugar et al. | Applicant |
| US2004/0156440(A1) | 2004-08-01 | Sugar et al. | Applicant |
| CA2260336 | 2000-08-01 | Applicant | |
| CA2298316 | 2000-08-01 | Applicant |
Non-Patent Literature (29)
- Medav, Dr. Hans-Joachim Kolb, “Short Time Spectral Analysis of Audio Signals on a PC,” date unknown.Applicant
- Agilent Publication, “Agilent PSA Performance Analyzer Series Swept and FFT Analysis, Product Note,” 2000.Applicant
- Agilent Publication, “Agilent 89400 Series Vector Signal Analyzer Product Overview,” 2000.Applicant
- Agilent Publication, “Agilent Technologies: 2G & 3G Solutions-Accelerating Progress,” 2002.Applicant
- Agilent Publication, “Agilent Technologies: Powerful Solutions to complex Measurement Problems; Burst, Transient + Modulated Signal Analysis,” 2000.Applicant
- Agilent Publication, “Agilent PN 89400-8 Using Vector Modulation Analysis in the Integration, Troubleshooting and Design of Digital RF Communications systems,” 2000 (and earlier).Applicant
- Agilent Publication, “Agilent PN 89400-10 Time-Capture Capabilities of the Agilent 89400 Series Vector Signal Analyzers,” 2000 (and earlier).Applicant
- Agilent Publication, “Agilent 89440A-1 Frequency and Time-Selective Power Measurements with the Agilent 89410A and 89440A,” 2001 (and earlier).Applicant
- Canadian Communications Research Center, “Spectrum Explorer Project of Canadian Cmmunications Research Center,” 1998 (and later).Applicant
- Stanford Research Systems, “Stanford Research Systems SR785 Two Channel Dynamic Signal Analyzer,” 1998.Applicant
- Agilent Publication, “Agilent Technologies Vector Signal Analyzer: Open New Windows for Alcatel Space Satellite Communications Business: Case Study,” May 24, 2001.Applicant
- Medav, Dr. Hans-Joachim Kolb, “Signal Processing and Neural Networks in Surveillance and Radio Monitoring,” Excerpt from ETH Zurich, 1993.Applicant
- Agilent Publication, “Agilent Technologies: Select the Right Agilent Signal Analyzer for Your Needs,” 2003 (and earlier).Applicant
- Medav, “Medav Astrid Analysis System for Telecom Signals, Recognition, Interception and Demodulation of HF/VHF/UHF Radio Signals from 0 to 2 GHz,” 2000.Applicant
- Medav, “Medav OC-6040 PC-based 4-Channel Analyser and Demodulator for Narrowband COMINT Signals with Automatic Signal Recognition and Text Decoding Capability,” 2002.Applicant
- Medav, “Medav DSP-Kit Metlab TM- Toolbox for Real-Time Measurement Acquisition,” date unknown.Applicant
- Medav, “Meda Spektro-Kit; Online Spectrogram Analysis on a PC,” date unknown.Applicant
- Tektronix, “Net Tek® BTS Transmitter and Interference Analyzer Ybt250,” Sep. 2002.Applicant
- Boudreau, Daniel et al., “Monitoring of the Radio-Frequency Spectrum with a Digital Analysis System,” Jun. 27, 2000, Proceedings of the 15th International Wroclaw Symposium and Exhibition on Electromagnetic Compatibility.Applicant
- BBN Technologies, “Using Signal Processing to Analyze Wireless Data Traffic,” May 22, 2002, BBN Technical Memorandum No. 1321, prepared for DARPA.Applicant
- Carlemalm, Catharina, “Suppression of Multiple Narrowband Interferers in a Spread-Spectrum Communication System,” Aug. 2000, IEEE Journal on Selected Areas in Communications, Special Issue on Broadband Communications, vol. 18.Applicant
- Boudreau, Daniel et al., “A Fast Automatic Modulation Algorithm and its Implementation in a Spectrum Monitoring Radio Signals,” Oct. 2000, Milcom 2000.Applicant
- Lo, Victor Yeeman, “Enhanced Spectral Analysis Tool (SAT) for Radio Frequency Interference Analysis and Spectrum Management,” Milcom, 1998.Applicant
- Medav, “Astrid++ Analysis, Monitoring, Recording and Multi-Channel Direction FInding of Wideband Application,” 2000.Applicant
- Tektronix, “Real-Time Spectrum Analysis Tools Aid Transition to Third-Generation Wireless Technology,” 1999.Applicant
- Patenaude, Francois et al., “Spectrum Surveillance: System Architecture,” CRC-TN-97-001, Canadian Communications Research Centre, Apr. 15, 1997.Applicant
- Oscor, “Oscor 5000 Omni-Spectral Correlator,” publication date unknown.Applicant
- Anritsu, “MS2711A Handheld Spectrum Analyzer,” May, 2000.Applicant
- PCT Search Report from counterpart PCT Application No. PCT/US03/12376 filed Apr. 22, 2003.Applicant