The subject disclosure is related to a method and apparatus for signal interference processing.
In most communication environments involving short range or long range wireless communications, interference from unexpected wireless sources can impact the performance of a communication system leading to lower throughput, dropped calls, reduced bandwidth which can cause traffic congestion, or other adverse effects, which are undesirable.
Some service providers of wireless communication systems have addressed interference issues by adding more communication nodes, policing interferers, or utilizing antenna steering techniques to avoid interferers.
Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
The subject disclosure describes, among other things, illustrative embodiments for detecting and mitigating interference signals. Other embodiments are included in the subject disclosure.
One embodiment of the subject disclosure includes a method for determining, by a system comprising a processor, at least one threshold for detecting signal interference in a plurality of resource blocks occurring in a radio frequency spectrum of a wireless communication system, detecting, by the system, signal interference in a first resource block of the plurality of resource blocks according to the at least one threshold, detecting, by the system, that the first resource block includes voice traffic, performing, by the system, a first quality of service measure of the first resource block responsive to detecting the signal interference, comparing, by the system, the first quality of service measure to a desired quality of service measure for voice traffic, determining, by the system, from the comparison that the first resource block is not suitable for voice traffic, and redirecting, by the system, the voice traffic to a second resource block of the plurality of resource blocks responsive to determining that the first resource block is not suitable for voice traffic.
One embodiment of the subject disclosure includes a machine-readable storage medium, comprising instructions, which when executed by a processor, cause the processor to perform operations comprising detecting signal interference in a first segment of a plurality of segments occurring in a radio frequency spectrum of a wireless communication system, determining according to the signal interference a measure of quality of service of the first segment for transmitting voice traffic, comparing the measure of quality of service to a desired measure of quality of service measure for voice traffic, determining from the comparison that the first segment is not suitable for voice traffic, and assigning non-voice traffic to the first segment while the first segment is affected by the signal interference.
One embodiment of the subject disclosure includes a communication device, comprising a memory to store instructions, and a processor coupled to the memory, wherein execution of the instructions by the processor causes the processor to perform operations comprising detecting signal interference in a first segment of a plurality of segments of a radio frequency spectrum of a wireless communication system, determining according to the signal interference a measure of quality of service of the first segment for transmitting voice traffic, comparing the measure of quality of service to a desired measure of quality of service measure for voice traffic, determining from the comparison that the first segment is not suitable for voice traffic, and notifying a system that the first segment is not suitable for voice traffic.
Interference signals can be generated from various sources including bidirectional amplifiers, unintended radiation from communication equipment (e.g., faulty transmitters of the carrier or other carriers), wireless microphones, garage door openers and similar production equipment, cross-border cellular (reduced buffer zones), federal and military installations, television transmissions, intermodulation from other transmitters, intermodulation from own faulty components and connectors, and so forth.
The embodiments of the subject disclosure can be performed singly or in combination by a mobile communication device, a stationary communication device, base stations, a wireless hub used by a satellite communication system, and/or a system or systems in communication with the base stations, the wireless hub, and/or mobile communication devices.
As shown in
During operation, the mobile units 12, 13A, 13B, 13C, and 13D exchange voice, data or other information with one of the base stations 14, 16, each of which is connected to a conventional land line communication network. For example, information, such as voice information, transferred from the mobile unit 12 to one of the base stations 14, 16 is coupled from the base station to the communication network to thereby connect the mobile unit 12 with, for example, a land line telephone so that the land line telephone may receive the voice information. Conversely, information, such as voice information may be transferred from a land line communication network to one of the base stations 14, 16, which in turn transfers the information to the mobile unit 12.
The mobile units 12, 13A, 13B, 13C, and 13D and the base stations 14, 16 may exchange information in either narrow band or wide band format. For the purposes of this description, it is assumed that the mobile unit 12 is a narrowband unit and that the mobile units 13A, 13B, 13C, and 13D are wideband units. Additionally, it is assumed that the base station 14 is a narrowband base station that communicates with the mobile unit 12 and that the base station 16 is a wideband digital base station that communicates with the mobile units 13A, 13B, 13C, and 13D.
Narrow band format communication takes place using, for example, narrowband 200 kilohertz (KHz) channels. The Global system for mobile phone systems (GSM) is one example of a narrow band communication system in which the mobile unit 12 communicates with the base station 14 using narrowband channels. Alternatively, the mobile units 13A, 13B, 13C, and 13D communicate with the base stations 16 using a form of digital communications such as, for example, code-division multiple access (CDMA), Universal Mobile Telecommunications System (UMTS), 3GPP Long Term Evolution (LTE™), or other next generation wireless access technologies. CDMA digital communication, for instance, takes place using spread spectrum techniques that broadcast signals having wide bandwidths, such as, for example, 1.2288 megahertz (MHz) bandwidths.
The switching station 18 is generally responsible for coordinating the activities of the base stations 14, 16 to ensure that the mobile units 12, 13A, 13B, 13C, and 13D are constantly in communication with the base station 14, 16 or with some other base stations that are geographically dispersed. For example, the switching station 18 may coordinate communication handoffs of the mobile unit 12 between the base stations 14 and another base station as the mobile unit 12 roams between geographical areas that are covered by the two base stations.
One particular problem that may arise in the telecommunication system 10 is when the mobile unit 12 or the base station 14, each of which communicates using narrowband channels, interferes with the ability of the base station 16 to receive and process wideband digital signals from the digital mobile units 13A, 13B, 13C, and 13D. In such a situation, the narrowband signal transmitted from the mobile unit 12 or the base station 14 may interfere with the ability of the base station 16 to properly receive wideband communication signals.
As will be readily appreciated, the base station 16 may receive and process wideband digital signals from more than one of the digital mobile units 13A, 13B, 13C, and 13D. For example, the base station 16 may be adapted to receive and process four CDMA carriers 40A-40D that fall within a multi-carrier CDMA signal 40, as shown in
As disclosed in detail hereinafter, a system and/or a method for multiple channel adaptive filtering or interference suppression may be used in a communication system. In particular, such a system or method may be employed in a wideband communication system to protect against, or to report the presence of, narrowband interference, which has deleterious effects on the performance of the wideband communication system. Additionally, such a system and method may be operated to eliminate interference in CDMA carriers having other CDMA carriers adjacent thereto.
As shown in
It will be readily understood that the illustrations of
Referring back to
Each of the components 50-60 of the base station 16 shown in
During operation of the base station 16, the antenna 50 receives CDMA carrier signals that are broadcast from the mobile unit 13A, 13B, 13C and 13D and couples such signals to the LNA 52, which amplifies the received signals and couples the amplified signals to the splitter 54. The splitter 54 splits the amplified signal from the LNA 52 and essentially places copies of the amplified signal on each of its output lines. The adaptive front end module 56 receives the signal from the splitter 54 and, if necessary, filters the CDMA carrier signal to remove any undesired narrowband interference and couples the filtered CDMA carrier signal to the wideband receiver 60.
As noted previously,
However, as noted previously, it is possible that the CDMA carrier signal transmitted by the mobile units 13A-13D and received by the antenna 50 has a frequency spectrum as shown in
The filtered multi-carrier CDMA signal 43 has the narrowband interferer 46 removed, as shown by the notch 46A. The filtered multi-carrier CDMA signal 43 is then coupled from the adaptive front end module 56 to the wideband receiver 60, so that the filtered multi-carrier CDMA signal 43 may be demodulated. Although some of the multi-carrier CDMA signal 42 was removed during filtering by the adaptive front end module 56, sufficient multi-carrier CDMA signal 43 remains to enable the wideband receiver 60 to recover the information that was broadcast by mobile unit(s). Accordingly, in general terms, the adaptive front end module 56 selectively filters multi-carrier CDMA signals to remove narrowband interference therefrom. Further detail regarding the adaptive front end module 56 and its operation is provided below in conjunction with
As shown in
By providing tuning coefficient data to the filter stage 78, the adaptive front end controller 68 acts to pre-filter the received RF signal before the signal is sent to the RF tuner 72, which analyzes the filtered RF signal for integrity and/or for other applications such as cognitive radio applications. After filtering, the radio tuner 72 may then perform channel demodulation, data analysis, and local broadcasting functions. The RF tuner 72 may be considered the receiver side of an overall radio tuner, while RF tuner 72′ may be considered the transmitter side of the same radio tuner. Prior to sending the filtered RF signal, the sampler 76 may provide an indication of the filtered RF signal to the controller 80 in a feedback manner for further adjusting of the adaptive filter stage 78.
In some examples, the adaptive front-end controller 68 is synchronized with the RF tuner 72 by sharing a master clock signal communicated between the two. For example, cognitive radios operating on a 100 μs response time can be synchronized such that for every clock cycle the adaptive front end analyzes the input RF signal, determines an optimal configuration for the adaptive filter stage 78, filters that RF signal into the filtered RF signal and communicates the same to the radio tuner 72 for cognitive analysis at the radio. By way of example, cellular phones may be implemented with a 200 μs response time on filtering. By implementing the adaptive front end controller 68 using a field programmable gate array configuration for the filter stage, wireless devices may identify not only stationary interference, but also non-stationary interference, of arbitrary bandwidths on that moving interferer.
In some implementations, the adaptive front-end controller 68 may filter interference or noise from the received incoming RF signal and pass that filtered RF signal to the tuner 72. In other examples, such as cascaded configurations in which there are multiple adaptive filter stages, the adaptive front-end controller 68 may be configured to apply the filtered signal to an adaptive bandpass filter stage to create a passband portion of the filtered RF signal. For example, the radio tuner 72 may communicate information to the controller 68 to instruct the controller that the radio is only looking at a portion of an overall RF spectrum and thus cause the adaptive front-end controller 68 not to filter certain portions of the RF spectrum and thereby bandpass only those portions. The integration between the radio tuner 72 and the adaptive front-end controller 68 may be particularly useful in dual-band and tri-band applications in which the radio tuner 72 is able to communicate over different wireless standards, such as GSM or UMTS standards.
The algorithms that may be executed by the controller 80 are not limited to interference detection and filtering of interference signals. In some configurations the controller 80 may execute a spectral blind source separation algorithm that looks to isolate two sources from their convolved mixtures. The controller 80 may execute a signal to interference noise ratio (SINR) output estimator for all or portions of the RF signal. The controller 80 may perform bidirectional transceiver data link operations for collaborative retuning of the adaptive filter stage 78 in response to instructions from the radio tuner 72 or from data the transmitter stage 64. The controller 80 can determine filter tuning coefficient data for configuring the various adaptive filters of stage 78 to properly filter the RF signal. The controller 80 may also include a data interface communicating the tuning coefficient data to the radio tuner 72 to enable the radio tuner 72 to determine filtering characteristics of the adaptive filter 78.
In one embodiment the filtered RF signal may be converted from a digital signal to an analog signal within the adaptive front-end controller 68. This allows the controller 68 to integrate in a similar manner to conventional RF filters. In other examples, a digital interface may be used to connect the adaptive front-end controller 68 with the radio tuner 72, in which case the ADC 70 would not be necessary.
The above discussion is in the context of the receiver stage 62. Similar elements are shown in the transmitter stage 64, but bearing a prime. The elements in the transmitter stage 64 may be similar to those of the receiver 62, with the exception of the digital to analog converter (DAC) 70′ and other adaptations to the other components shown with a prime in the reference numbers. Furthermore, some or all of these components may in fact be executed by the same corresponding structure in the receiver stage 62. For example, the RF receiver tuner 72 and the transmitter tuner 72′ may be performed by a single tuner device. The same may be true for the other elements, such as the adaptive filter stages 78 and 78′, which may both be implemented in a single FPGA, with different filter elements in parallel for full duplex (simultaneous) receive and transmit operation.
A DSP 110 is coupled to the FPGA 108 and executes signal processing algorithms that may include a spectral blind source separation algorithm, a signal to interference noise ratio (SINR) output estimator, bidirectional transceiver data line operation for collaborative retuning of the adaptive filter stage in response to instructions from the tuner, and/or an optimal filter tuning coefficients algorithm.
FPGA 108 is also coupled to a PCI target 112 that interfaces the FPGA 108 and a PCI bus 114 for communicating data externally. A system clock 118 provides a clock input to the FPGA 108 and DSP 110, thereby synchronizing the components. The system clock 118 may be locally set on the adaptive front-end controller, while in other examples the system claim 118 may reflect an external master clock, such as that of a radio tuner. The FPGA 108, DSP 110, and PCI target 112, designated collectively as signal processing module 116, will be described in greater detail below. In the illustrated example, the adaptive front-end controller 100 includes a microcontroller 120 coupled to the PCI bus 114 and an operations, alarms and metrics (OA&M) processor 122. Although they are shown and described herein as separate devices that execute separate software instructions, those having ordinary skill in the art will readily appreciate that the functionality of the microcontroller 120 and the OA&M processor 122 may be merged into a single processing device. The microcontroller 120 and the OA&M processor 122 are coupled to external memories 124 and 126, respectively. The microcontroller 120 may include the ability to communicate with peripheral devices, and, as such, the microcontroller 120 may be coupled to a USB port, an Ethernet port, or an RS232 port, among others (though none shown). In operation, the microcontroller 120 may locally store lists of channels having interferers or a list of known typically available frequency spectrum bands, as well as various other parameters. Such a list may be transferred to a reporting and control facility or a base station, via the OA&M processor 122, and may be used for system diagnostic purposes.
The aforementioned diagnostic purposes may include, but are not limited to, controlling the adaptive front-end controller 100 to obtain particular information relating to an interferer and retasking the interferer. For example, the reporting and control facility may use the adaptive front-end controller 100 to determine the identity of an interferer, such as a mobile unit, by intercepting the electronic serial number (ESN) of the mobile unit, which is sent when the mobile unit transmits information on the narrowband channel. Knowing the identity of the interferer, the reporting and control facility may contact infrastructure that is communicating with the mobile unit (e.g., the base station) and may request the infrastructure to change the transmit frequency for the mobile unit (i.e., the frequency of the narrowband channel on which the mobile unit is transmitting) or may request the infrastructure to drop communications with the interfering mobile unit altogether.
Additionally, in a cellular configuration (e.g., a system based on a configuration like that of
The FPGA 108 can provide a digital output coupled to a digital to analog converter (DAC) 128 that converts the digital signal to an analog signal which may be provided to a filter 130 to generate a filtered RF output to be broadcast from the base station or mobile station. The digital output at the FPGA 108, as described, may be one of many possible outputs. For example, the FPGA 108 may be configured to output signals based on a predefined protocol such as a Gigabit Ethernet output, an open base station architecture initiative (OBSAI) protocol, or a common public radio interface (CPRI) protocol, among others.
It is further noted that the aforementioned diagnostic purposes may also include creating a database of known interferers, the time of occurrence of the interferers, the frequency of occurrence of the interferers, spectral information relating to the interferers, a severity analysis of the interferers, and so on. The identity of the interferers may be based solely on spectral profiles of each interferer that can be used for identification purposes. Although the aforementioned illustrations describe a mobile unit 12 as an interferer, other sources of interference are possible. Any electronic appliance that generates electromagnetic waves such as, for example, a computer, a set-top box, a child monitor, a wireless access point (e.g., WIFI™ BLUETOOTH™, ZIGBEE™, etc.) can be a source of interference. In one embodiment, a database of electronic appliances can be analyzed in a laboratory setting or other suitable testing environment to determine an interference profile for each appliance. The interference profiles can be stored in a database according to an appliance type, manufacturer, model number, and other parameters that may be useful in identifying an interferer. Spectral profiles provided by, for example, the OA&M processor 122 to a diagnostic system can be compared to a database of previously characterized interferers to determine the identity of the interference when a match is detected.
A diagnostic system, whether operating locally at the adaptive front end controller, or remotely at a base station, switching station, or server system, can determine the location of the interferer near the base station (or mobile unit) making the detection, or if a more precise location is required, the diagnostic system can instruct several base stations (or mobile units) to perform triangulation analysis to more precisely locate the source of the interference if the interference is frequent and measurable from several vantage points. With location data, interference identity, timing and frequency of occurrence, the diagnostic system can generate temporal and geographic reports showing interferers providing field personnel a means to assess the volume of interference, its impact on network performance, and it may provide sufficient information to mitigate interference by means other than filtering, such as, for example, interference avoidance by way of antenna steering at the base station, beam steering, retasking an interferer when possible, and so on.
The I and Q components from the digital down converter 152 are provided to the DSP 110 which implements a detection algorithm and in response provides the tunable IIR/FIR filter 154 with tuning coefficient data that tunes the IIR and/or FIR filters 154 to specific notch (or bandstop) and/or bandpass frequencies, respectively, and specific bandwidths. The tuning coefficient data, for example, may include a frequency and a bandwidth coefficient pair for each of the adaptive filters, which enables the filter to tune to a frequency for bandpass or bandstop operation and the bandwidth to be applied for that operation. The tuning coefficient data corresponding to a bandpass center frequency and bandwidth may be generated by the detection algorithm and passed to a tunable FIR filter within the IIR/FIR filter 154. The filter 154 may then pass all signals located within a passband of the given transmission frequency. Tuning coefficient data corresponding to a notch (or bandstop) filter may be generated by the detection algorithm and then applied to an IIR filter within the IIR/FIR filter 154 to remove any narrowband interference located within the passband of the bandpass filter. The tuning coefficient data generated by the detection algorithm are implemented by the tunable IIR/FIR filters 154 using mathematical techniques known in the art. In the case of a cognitive radio, upon implementation of the detection algorithm, the DSP 110 may determine and return coefficients corresponding to a specific frequency and bandwidth to be implemented by the tunable IIR/FIR filter 154 through a DSP/PCI interface 158. Similarly, the transfer function of a notch (or bandstop) filter may also be implemented by the tunable IIR/FIR filter 154. Of course other mathematical equations may be used to tune the IIR/FIR filters 154 to specific notch, bandstop, or bandpass frequencies and to a specific bandwidth.
After the I and Q components are filtered to the appropriate notch (or bandstop) or bandpass frequency at a given bandwidth, a digital upconverter 156, such as a polyphase interpolator, converts the signal back to the original data rate, and the output of the digital upconverter is provided to the DAC 128.
A wireless communication device capable to be operated as a dual- or tri-band device communicating over multiple standards, such as over GSM and UMTS may use the adaptive digital filter architecture embodiments as described above. For example, a dual-band device (using both UMTS and GSM) may be preprogrammed within the DSP 110 to transmit first on UMTS, if available, and on GSM only when outside of a UMTS network. In such a case, the IIR/FIR filter 154 may receive tuning coefficient data from the DSP 110 to pass all signals within a UMTS range. That is, the tuning coefficient data may correspond to a bandpass center frequency and bandwidth adapted to pass only signals within the UMTS range. The signals corresponding to a GSM signal may be filtered, and any interference caused by the GSM signal may be filtered using tuning coefficients, received from the DSP 110, corresponding to a notch (or band stop) frequency and bandwidth associated with the GSM interference signal.
Alternatively, in some cases it may be desirable to keep the GSM signal in case the UMTS signal fades quickly and the wireless communication device may need to switch communication standards rapidly. In such a case, the GSM signal may be separated from the UMTS signal, and both passed by the adaptive front-end controller. Using the adaptive digital filter, two outputs may be realized, one output corresponding to the UMTS signal and one output corresponding to a GSM signal. The DSP 110 may be programmed to again recognize the multiple standard service and may generate tuning coefficients corresponding to realize a filter, such as a notch (or bandstop) filter, to separate the UMTS signal from the GSM signal. In such examples, an FPGA may be programmed to have parallel adaptive filter stages, one for each communication band.
To implement the adaptive filter stages, in some examples, the signal processing module 116 is pre-programmed with general filter architecture code at the time of production, for example, with parameters defining various filter types and operation. The adaptive filter stages may then be programmed, through a user interface or other means, by the service providers, device manufactures, etc., to form the actual filter architecture (parallel filter stages, cascaded filter stages, etc.) for the particular device and for the particular network(s) under which the device is to be used. Dynamic flexibility can be achieved during runtime, where the filters may be programmed to different frequencies and bandwidths, each cycle, as discussed herein.
One method of detecting a wideband signal having narrowband interference is by exploiting the noise like characteristics of a signal. Due to such noise like characteristics of the signal, a particular measurement of a narrowband channel power gives no predictive power as to what the next measurement of the same measurement channel may be. In other words, consecutive observations of power in a given narrowband channel are un-correlated. As a result, if a given measurement of power in a narrowband channel provides predictive power over subsequent measurements of power in that particular channel, thus indicating a departure from statistics expected of a narrowband channel without interference, such a narrowband channel may be determined to contain interference.
Specifically, the PDFs 204 include probability distribution of power in a given channel, which is the likelihood p(x) of measuring a power x in a given channel, for a DSSS signal carrying one mobile unit (212), for a DSSS signal carrying ten mobile units (214), and for a DSSS signal carrying twenty mobile units (210). For example, for the PDF 212, representing a DSSS signal carrying one mobile unit, the distribution p(x) is observed to be asymmetric, with an abbreviated high power tail. In this case, any channel having power higher than the high power tail of the PDF 212 may be considered to have an interference signal.
The CCDFs 206 denote the likelihood that a power measurement in a channel will exceed a given mean power a, by some value α/σ, wherein σ is standard deviation of the power distribution. Specifically, the CCDFs 206 include an instance of CCDF for a DSSS signal carrying one mobile unit (220), an instance of CCDF for a DSSS signal carrying ten mobile units (222), and an instance of CCDF for a DSSS signal carrying twenty mobile units (224). Thus, for example, for a DSSS signal carrying one mobile unit, the likelihood of any narrowband channel having the ratio α/σ of 10 dB or more is 0.01%. Therefore, an optimal filter can be tuned to such a narrowband channel having excess power.
One method of detecting such a narrowband channel having interference is by exploiting the noise like characteristic of a DSSS signal. Due to such noise like characteristic of DSSS signal, a particular measurement of a narrowband channel power gives no predictive power as to what the next measurement of the same measurement channel may be. In other words, consecutive observations of power in a given narrowband channels are un-correlated. As a result, if a given measurement of power in a narrowband channel provides predictive power over subsequent measurements of power in that particular channel, thus indicating a departure from statistics expected of a narrowband channel without interference, such a narrowband channel may be determined to contain interference.
At block 304 the adaptive front end controller can determine the number of sequences m of a DSSS signal that may be required to be analyzed to determine narrowband channels having interference. A user may provide such a number m based on any pre-determined criteria. For example, a user may provide m to be equal to four, meaning that four consecutive DSSS signals need to be analyzed to determine if any of the narrowband channels within that DSSS signal spectrum includes an interference signal. As one of ordinary skill in the art would appreciate, the higher is the selected value of m, the more accurate will be the interference detection. However, the higher the number m is, the higher is the delay in determining whether a particular DSSS signal had an interference present in it, subsequently, resulting in a longer delay before a filter is applied to the DSSS signal to remove the interference signal.
Generally, detection of an interference signal may be performed on a rolling basis. That is, at any point in time, m previous DSSS signals may be used to analyze presence of an interference signal. The earliest of such m interference signals may be removed from the set of DSSS signals used to determine the presence of an interference signal on a first-in-first-out basis. However, in an alternate embodiment, an alternate sampling method for the set of DSSS signals may also be used.
At block 306 the adaptive front end controller can select x narrowband channels having the highest signal strength from each of the m most recent DSSS signals scanned at the block 302. The number x may be determined by a user. For example, if x is selected to be equal to three, the block 306 may select three highest channels from each of the m most recent DSSS signals. The methodology for selecting x narrowband channels having highest signal strength from a DSSS signal is described in further detail in
After having determined the x narrowband channels having the highest signal strengths in each of the m DSSS signals, at block 308 the adaptive front end controller can compare these x narrowband channels to determine if any of these highest strength narrowband channels appear more than once in the m DSSS signals. In case of the example above, the adaptive front end controller at block 308 may determine that the narrowband channels 15 and 27 are present among the highest strength narrowband channels for each of the last three DSSS signals, while channel 35 is present among the highest strength narrowband channels for at least two of the last three DSSS signals.
Such consistent appearance of narrowband channels having highest signal strength over subsequent DSSS signals indicate that narrowband channels 15 and 27, and probably the narrowband channel 35, may have an interference signal super-imposed on them. At block 310 the adaptive front end controller may use such information to determine which narrowband channels may have interference. For example, based on the number of times a given narrowband channel appears in the selected highest signal strength channels, the adaptive front end controller at block 310 may determine the confidence level that may be assigned to a conclusion that a given narrowband channel contains an interference signal.
Alternatively, at block 310 the adaptive front end controller may determine a correlation factor for each of the various narrowband channels appearing in the x selected highest signal strength channels and compare the calculated correlation factors with a threshold correlation factor to determine whether any of the x selected channels has correlated signal strengths. Calculating a correlation factor based on a series of observations is well known to those of ordinary skill in the art and therefore is not illustrated in further detail herein. The threshold correlation factor may be given by the user of the interference detection program 300.
Note that while in the above illustrated embodiment, the correlation factors of only the selected highest signal strength channels are calculated, in an alternate embodiment, correlation factors of all the narrowband channels within the DSSS signals may be calculated and compared to the threshold correlation factor.
Empirically, it may be shown that when m is selected to be equal to three, for a clean DSSS signal, the likelihood of having at least one match among the higher signal strength narrowband channels is 0.198, the likelihood of having at least two matches among the higher signal strength narrowband channels is 0.0106, and the likelihood of having at least three matches among the higher signal strength narrowband channels is 9.38×10−5. Thus, the higher the number of matches, the lesser is the likelihood of having a determination that one of the x channels contains an interference signal (i.e., a false positive interference detection). It may be shown that if the number of scans m is increased to, say four DSSS scans, the likelihood of having such matches in m consecutive scans is even smaller, thus providing higher confidence that if such matches are found to be present, they indicate presence of interference signal in those narrowband channels.
To identify the presence of interference signals with even higher level of confidence, at block 312 the adaptive front end controller may decide whether to compare the signal strengths of the narrowband channels determined to have an interference signal with a threshold. If at block 312 the adaptive front end controller decides to perform such a comparison, at block 314 the adaptive front end controller may compare the signal strength of each of the narrowband channels determined to have an interference with a threshold level. Such comparing of the narrowband channel signal strengths with a threshold may provide added confidence regarding the narrowband channel having an interference signal so that when a filter is configured according to the narrowband channel, the probability of removing a non-interfering signal is reduced. However, a user may determine that such added confidence level is not necessary and thus no such comparison to a threshold needs to be performed. In which case, at block 316 the adaptive front end controller stores the interference signals in a memory.
After storing the information about the narrowband channels having interference signals, at block 318 the adaptive front end controller selects the next DSSS signal from the signals scanned and stored at block 302. At block 318 the adaptive front end controller may cause the first of the m DSSS signals to be dropped and the newly added DSSS signal is added to the set of m DSSS signals that will be used to determine presence of an interference signal (first-in-first-out). Subsequently, at block 306 the process of determining narrowband channels having interference signals is repeated by the adaptive front end controller. Finally, at block 320 the adaptive front end controller may select and activate one or more filters that are located in the path of the DSSS signal to filter out any narrowband channel identified as having narrowband interference in it.
Now referring to
At block 352 the adaptive front end controller may sort signal strengths of each of the n channels within a given DSSS signal. For example, if a DSSS signal has 41 narrowband channels, at block 352 the adaptive front end controller may sort each of the 41 narrowband channels according to its signal strengths. Subsequently, at block 354 the adaptive front end controller may select the x highest strength channels from the sorted narrowband channels and store information identifying the selected x highest strength channels for further processing. An embodiment of the high strength channels detection program 350 may simply use the selected x highest strength channels from each scan of the DSSS signals to determine any presence of interference in the DSSS signals. However, in an alternate embodiment, additional selected criteria may be used.
Subsequently, at block 356 the adaptive front end controller can determine if it is necessary to compare the signal strengths of the x highest strength narrowband channels to any other signal strength value, such as a threshold signal strength, etc., where such a threshold may be determined using the average signal strength across the DSSS signal. For example, at block 356 the adaptive front end controller may use a criterion such as, for example: “when x is selected to be four, if at least three out of four of the selected narrowband channels have also appeared in previous DSSS signals, no further comparison in necessary.” Another criterion may be, for example: “if any of the selected narrowband channels is located at the fringe of the DSSS signal, the signal strengths of such narrowband channels should be compared to a threshold signal strength.” Other alternate criteria may also be provided.
If at block 356 the adaptive front end controller determines that no further comparison of the signal strengths of the selected x narrowband channels is necessary, at block 358 the adaptive front end controller stores information about the selected x narrowband channels in a memory for further processing. If at block 356 the adaptive front end controller determines that it is necessary to apply further selection criteria to the selected x narrowband channels, the adaptive front end controller returns to block 360. At block 360 the adaptive front end controller may determine a threshold value against which the signal strengths of each of the x narrowband channels are compared based on a predetermined methodology.
For example, in an embodiment, at block 360 the adaptive front end controller may determine the threshold based on the average signal strength of the DSSS signal. The threshold signal strength may be the average signal strength of the DSSS signal or a predetermined value may be added to such average DSSS signal to derive the threshold signal strength.
Subsequently, at block 362 the adaptive front end controller may compare the signal strengths of the selected x narrowband channels to the threshold value determined at block 360. Only the narrowband channels having signal strengths higher than the selected threshold are used in determining presence of interference in the DSSS signal. Finally, at block 364 the adaptive front end controller may store information about the selected x narrowband channels having signal strengths higher than the selected threshold in a memory. As discussed above, the interference detection program 300 may use such information about the selected narrowband channels to determine the presence of interference signal in the DSSS signal.
The interference detection program 300 and the high strength channel detection program 350 may be implemented by using software, hardware, firmware or any combination thereof. For example, such programs may be stored on a memory of a computer that is used to control activation and deactivation of one or more notch filters. Alternatively, such programs may be implemented using a digital signal processor (DSP) which determines the presence and location of interference channels in a dynamic fashion and activates/de-activates one or more filters.
The interference detection program 370 may start scanning various DSSS signals 372-374 starting from the first DSSS signal 372. As discussed above at block 304 the adaptive front end controller determines the number m of the DSSS signals 372-374 that are to be scanned. Because the interference signal 378 causes the signal strength of a particular narrowband channel to be consistently higher than the other channels for a number of consecutive scans of the DSSS signals 372-374 at block 210 the adaptive front end controller identifies a particular channel having an interference signal present. Subsequently, at block 320 the adaptive front end controller will select and activate a filter that applies the filter function as described above, to the narrowband channel having interference.
The graph 370 also illustrates the average signal strengths of each of the DSSS signals 372-374 by a line 376. As discussed above, at block 362 the adaptive front end controller may compare the signal strengths of each of the x selected narrowband channels from the DSSS signals 372-374 with the average signal strength, as denoted by line 376, in that particular DSSS signal.
Now referring to
The foregoing interference detection and mitigation embodiments can further be adapted for detecting and mitigating interference in long-term evolution (LTE™) communication systems.
LTE™ transmission consists of a combination of Resource Blocks (RB's) which have variable characteristics in frequency and time. A single RB can be assigned to a user equipment, specifically, a 180 KHz continuous spectrum utilized for 0.5-1 msec. An LTE™ band can be partitioned into a number of RBs which could be allocated to individual communication devices for specified periods of time for LTE™ transmission. Consequently, an LTE™ spectrum has an RF environment dynamically variable in frequency utilization over time.
LTE™ utilizes different media access methods for downlink (orthogonal frequency-division multiple access; generally, referred to as OFDMA) and uplink (single carrier frequency-division multiple access; generally, referred to as SC-FDMA). For downlink communications, each RB contains 12 sub-carriers with 15 KHz spacing. Each sub-carrier can be used to transmit individual bit information according to the OFDMA protocol. For uplink communications, LTE™ utilizes a similar RB structure with 12 sub-carriers, but in contrast to downlink, uplink data is pre-coded for spreading across 12 sub-carriers and is transmitted concurrently on all 12 sub-carriers.
The effect of data spreading across multiple sub-carriers yields a transmission with spectral characteristics similar to a CDMA/UMTS signal. Hence, similar principles of narrow band interference detection can be applied within an instance of SC-FDMA transmission from an individual communication device—described herein as user equipment (UE). However, since each transmission consists of unknown RB allocations with unknown durations, such a detection principle can only be applied separately for each individual RB within a frequency and specific time domain. If a particular RB is not used for LTE™ transmission at the time of detection, the RF spectrum will present a thermal noise which adheres to the characteristics of a spread spectrum signal, similar to a CDMA/UMTS signal.
Co-channel, as well as other forms of interference, can cause performance degradation to SC-FDMA and OFDMA signals when present.
Time averaging system (TAS) can be achieved with a boxcar (rolling) average, in which the TAS is obtained as a linear average of a Q of previous spectrum samples, with Q being a user-settable parameter. The Q value determines the “strength” of the averaging, with higher Q value resulting in a TAS that is more strongly smoothed in time and less dependent on short duration transient signals. Due to the frequency-hopped characteristic of SC-FDMA/OFDMA signals, which are composed of short duration transients, the TAS of such signals is approximately flat. It will be appreciated that TAS can also be accomplished by other methods such as a forgetting factor filter.
In one embodiment, an adaptive threshold can be determined by a method 500 as depicted in
The adaptive front end module 56 repeats these steps until the spectrum of interest has been fully scanned for Q cycles, thereby producing the following power level sample sets:
The adaptive front end module 56 in step 504, calculates averages for each of the power level sample sets as provided below:
In one embodiment, the adaptive front end module 56 can be configured to determine at step 506 the top “m” averages (e.g., the top 3 averages) and dismiss these averages from the calculations. The variable “m” can be user-supplied or can be empirically determined from field measurements collected by one or more base stations utilizing an adaptive front end module 56. This step can be used to avoid skewing a baseline average across all frequency increments from being too high, resulting in a threshold calculation that may be too conservative. If step 506 is invoked, a baseline average can be determined in step 508 according to the equation: Baseline Avg=(a1+a2+ . . . +az−averages that have been dismissed)/(x−m). If step 506 is skipped, the baseline average can be determined from the equation: Baseline Avg=(a1+a2+ . . . +az)/x. Once the baseline average is determined in step 508, the adaptive front end module 56 can proceed to step 510 where it calculates a threshold according to the equation: Threshold=ydB offset+Baseline Avg. The ydB offset can be user defined or empirically determined from field measurements collected by one or more base stations utilizing an adaptive front end module 56.
Once a cycle of steps 502 through 510 have been completed, the adaptive front end module 56 can monitor at step 512 interference per frequency increment of the spectrum being scanned based on any power levels measured above the threshold 602 calculated in step 510 as shown in
Method 500 can utilize any of the embodiments in the illustrated flowcharts described above to further enhance the interference determination process. For example, method 500 of
When one or more interferers are detected in step 512, the adaptive front end module 56 can mitigate the interference at step 514 by configuring one or more filters to suppress the one or more interferers as described above. When there are limited resources to suppress all interferers, the adaptive front end module 56 can use a prioritization scheme to address the most harmful interference as discussed above.
In one embodiment, the adaptive front end module 56 can submit a report to a diagnostic system that includes information relating to the interferers detected. The report can include among other things, a frequency of occurrence of the interferer, spectral data relating to the interferer, an identification of the base station from which the interferer was detected, a severity analysis of the interferer (e.g., bit error rate, packet loss rate, or other traffic information detected during the interferer), and so on. The diagnostic system can communicate with other base stations with other operable adaptive front end module 56 to perform macro analysis of interferers such as triangulation to locate interferers, identity analysis of interferers based on a comparison of spectral data and spectral profiles of known interferers, and so on.
In one embodiment, the reports provided by the adaptive front end module 56 can be used by the diagnostic system to in some instance perform avoidance mitigation. For example, if the interferer is known to be a communication device in the network, the diagnostic system can direct a base station in communication with the communication device to direct the communication device to another channel so as to remove the interference experienced by a neighboring base station. Alternatively, the diagnostic system can direct an affected base station to utilize beam steering and or mechanical steering of antennas to avoid an interferer. When avoidance is performed, the mitigation step 514 can be skipped or may be invoked less as a result of the avoidance steps taken by the diagnostic system.
Once mitigation and/or an interference report has been processed in steps 514 and 516, respectively, the adaptive front end module 56 can proceed to step 518. In this step, the adaptive front end module 56 can repeat steps 502 thru 510 to calculate a new baseline average and corresponding threshold based on Q cycles of the resource blocks. Each cycle creates a new adaptive threshold that is used for interference detection. It should be noted that when Q is high, changes to the baseline average are smaller, and consequently the adaptive threshold varies less over Q cycles. In contrast, when Q is low, changes to the baseline average are higher, which results in a more rapidly changing adaptive threshold.
Generally speaking, one can expect that there will be more noise-free resource blocks than resource blocks with substantive noise. Accordingly, if an interferer is present (constant or ad hoc), one can expect the aforementioned algorithm described by method 500 will produce an adaptive threshold (i.e., baseline average+offset) that will be lower than interferer's power level due to mostly noise-free resource blocks driving down baseline average. Although certain communication devices will have a high initial power level when initiating communications with a base station, it can be further assumed that over time the power levels will be lowered to a nominal operating condition. A reasonably high Q would likely also dampen disparities between RB's based on the above described embodiments.
It is further noted that the aforementioned algorithms can be modified while maintaining an objective of mitigating detected interference. For instance, instead of calculating a baseline average from a combination of averages a1(f1) through ax(fx) or subsets thereof, the adaptive front end controller 56 can be configured to calculate a base line average for each resource block according to a known average of adjacent resource blocks, an average calculated for the resource block itself, or other information that may be provided by, for example, to a resource block scheduler (e.g., a software application and/or hardware component of the base station) that may be helpful in calculating a desired baseline average for each resource block or groups of resource blocks. For instance, the resource block schedule can inform the adaptive front end module 56 as to which resource blocks are active and at what time periods. This information can be used by the adaptive front end module 56 determine individualized baseline averages for each of the resource blocks or groups thereof. Since baseline averages can be individualized, each resource block can also have its own threshold applied to the baseline average of the resource block. Accordingly, thresholds can vary between resource blocks for detecting interferers.
It is further noted that the aforementioned mitigation and detection algorithms can be implemented by any communication device including cellular phones, smartphones, tablets, small base stations, macro base stations, femto cells, WIFI™ access points, and so on. Small base stations (commonly referred to as small cells) can represent low-powered radio access nodes that can operate in licensed and/or unlicensed spectrum that have a range of 10 meters to 1 or 2 kilometers, compared to a macrocell (or macro base station) which might have a range of a few tens of kilometers. Small base stations can be used for mobile data offloading as a more efficient use of radio spectrum.
Referring back to step 702, the interference occurring in the first resource block(s) can be detected by a mobile communication device utilizing the adaptive thresholds described in the subject disclosure. The mobile communication device can inform the communication system (herein referred to as a base station) that it has detected interference. The interference can also be detected by the base station during communications with the mobile communication device. The base station can also collect interference information in a database for future reference. The base station can also transmit the interference information to a centralized system that monitors interference at multiple base stations. The interference information can be stored and organized by the centralized system in a system-wide database along with localized storage in the individual databases of each respective base station. The interference information can be stored and organized according to time stamps when the interference occurred, resource blocks affected by the interference, an identity of the base station collecting the interference information, an identity of the mobile communication device affected by the interference, frequency of occurrence of the interference, spectral information descriptive of the interference, an identity of the interferer if it can be synthesized from the spectral information, and so on.
At step 704, a quality of service measure can be performed on the first resource blocks. The quality of service measure can be performed by the mobile communication device and/or the base station. The quality of service measure can include a bit error rate measure, a packet error rate measure, a packet retransmission rate measure, a jitter rate measure, or any combination thereof. Other metrics that can be used to assess quality of service such as a desired signal to noise ratio can be applied to the subject disclosure. At steps 706 and 708, the quality of service measure can be compared to a desired quality of service measure for voice traffic and a desired quality of service measure for data traffic, respectively. The desired quality of service measure for voice traffic can be defined by a service provider of a wireless communication system according to desirable metrics such as a desired bit error rate, a desired packet retransmission rate, and/or a desired jitter rate. For example, a service provider may establish desired metrics to reduce background noise, improve voice quality, reduce the likelihood of a dropped call, or other suitable business objectives. Similarly, the service provider can establish metrics for a desired quality of service measure for data traffic that may differ or perhaps may be more lenient than the metrics used for voice traffic.
At step 710, a determination can be made as to the type of traffic (data or voice) that the mobile communication device desires to transmit in the first resource blocks. If it is voice, at step 712, a determination can be made from the comparison performed in step 706 whether the first resource blocks are suitable for voice traffic. If, for example, the quality of service measure satisfies all or most of the desired metrics established by the service provider collectively defined in the desired quality of service measure for voice traffic, then at step 720 the mobile communication device can be assigned to the first resource blocks by a resource block scheduler of the base station for initiating voice traffic.
If, on the other hand, the quality of service measure does not satisfy one or more of the desired metrics established by the service provider (e.g., bit error rate is too high, signal to noise ratio is too low, etc.), then a determination can be made in step 714 as to whether it would be feasible to mitigate this condition by filtering in whole or in part the signal interference detected in step 702 utilizing any combination of the embodiments of the subject disclosure for detecting and filtering signal interference. If filtering would make the first resource blocks suitable for voice traffic, then the mobile communication device can autonomously proceed or be directed by the base station to proceed to step 716 and filter interference according to the subject disclosure, and receive instructions from the resource block scheduler of the base station to utilize at step 720 the first resource blocks for initiating voice traffic.
If, on the other hand, a determination is made in step 714 that filtering is not feasible because it will not satisfy the desired quality of service measure for voice traffic, then at step 718 the resource block scheduler of the base station can locate new resource block(s) that can be used for traffic. The base station and mobile communication device can determine in step 712 if the new resource blocks determined in step 718 are suitable for voice traffic. This can be performed by measuring the quality of service of the new resource blocks at step 704, comparing the new quality of service measure to the desired quality of service measure for voice traffic at step 706, and determining at step 712 if the new resource blocks are suitable for voice traffic. If they are, then the resource block scheduler of the base station can direct the mobile communication device to utilize the new resource blocks for voice traffic at step 720. If the new resource blocks are not suitable for voice traffic, then at step 714 a determination can be made if filtering can mitigate signal interference which may be present in the new resource blocks. If filtering is possible, then steps 716 and 720 are invoked as described earlier. Otherwise, the resource block scheduler of the base station is directed to step 718 where it repeats the process described above until suitable resource blocks for transmitting voice traffic are found. If none are found, and if data traffic cannot be redirected to the affected resource blocks, then the base station can proceed to step 728 where it disables use of the affected resource blocks and asserts an alarm directed to service provider personnel.
In parallel to the above process for selecting resource blocks for voice traffic, a determination can be made at step 722 whether the first resource blocks experiencing signal interference can be used for data traffic. Step 722 can be performed based on the results of the comparison of step 708. If, for example, the quality of service measure satisfies all or most of the desired metrics established by the service provider collectively defined in the desired quality of service measure for data traffic, then at step 724 the mobile communication device can be assigned to the first resource blocks by the resource block scheduler of the base station for initiating data traffic.
If, on the other hand, the quality of service measure does not satisfy one or more of the desired metrics established by the service provider (e.g., bit or packet error rate is too high), then a determination can be made at step 726 whether it would be feasible to mitigate this condition by filtering in whole or in part the signal interference detected in step 702 utilizing any combination of the embodiments of the subject disclosure for detecting and filtering signal interference, and/or by changing a modulation coding scheme used for the data traffic. If filtering would make the first resource blocks suitable for data traffic, then the mobile communication device can proceed to step 730 and filter interference according to the subject disclosure, and receive instructions from the resource block scheduler of the base station to utilize at step 724 the first resource blocks for initiating data traffic.
Alternatively, or in combination, the mobile communication device can be instructed to utilize a modulation coding scheme that's more aggressive with error correction (e.g., transitioning from 64-QAM to 4-QPSK which effectively increases error correction bits and reduces data bits per packet). A more aggressive modulation coding scheme trades off throughput for a reduction in retransmissions caused by signal interference.
If filtering nor changing the modulation coding scheme makes the first resource blocks suitable for data transmission, then at step 728, the resource block scheduler of the base station can disable utilizing of the first resource blocks for data or voice traffic, and assert an alarm to direct service provider personnel to resolve the signal interference experienced by the first resource blocks.
It is contemplated that the steps of method 700 can be rearranged and/or individually modified without departing from the scope of the claims of the subject disclosure. For example, a mobile communication device can be allotted a number of resource blocks to choose from, and can autonomously perform the steps of method 700 to choose desirable resource blocks for voice and/or data traffic. The selection of the resource blocks can be communicated to the resource block scheduler of the base station to track resource blocks in use versus those available to other mobile communication devices. Additionally, the resource block scheduler can collect signal interference information from mobile communication devices, the location of the mobile communication devices when experiencing signal interference, frequency of occurrence of the signal interference, the time of occurrence of the signal interference, and so on, to identify resource block(s) that may have issues supporting voice communications at different times and according to the location of mobile communication devices. The resource block scheduler can preemptively use this information to direct mobile communication devices away from certain resource blocks known to have issues with voice traffic. Similar assessments can be made for data traffic.
An illustrative embodiment of a communication device 800 is shown in
To enable these features, communication device 800 can comprise a wireline and/or wireless transceiver 802 (herein transceiver 802), a user interface (UI) 804, a power supply 814, a location receiver 816, a motion sensor 818, an orientation sensor 820, and a controller 806 for managing operations thereof. The transceiver 802 can support short-range or long-range wireless access technologies such as BLUETOOTH™, ZIGBEE™, WIFI™, DECT™, or cellular communication technologies, just to mention a few. Cellular technologies can include, for example, CDMA-1X, UMTS/HSDPA, GSM™/GPRS, TDMA/EDGE, EV/DO, WiMAX, SDR, LTE™, as well as other next generation wireless communication technologies as they arise. The transceiver 802 can also be adapted to support circuit-switched wireline access technologies (such as PSTN), packet-switched wireline access technologies (such as TCP/IP, VoIP, etc.), and combinations thereof.
The UI 804 can include a depressible or touch-sensitive keypad 808 with a navigation mechanism such as a roller ball, a joystick, a mouse, or a navigation disk for manipulating operations of the communication device 800. The keypad 808 can be an integral part of a housing assembly of the communication device 800 or an independent device operably coupled thereto by a tethered wireline interface (such as a USB cable) or a wireless interface supporting for example BLUETOOTH™. The keypad 808 can represent a numeric keypad commonly used by phones, and/or a QWERTY keypad with alphanumeric keys. The UI 804 can further include a display 810 such as monochrome or color LCD (Liquid Crystal Display), OLED (Organic Light Emitting Diode) or other suitable display technology for conveying images to an end user of the communication device 800. In an embodiment where the display 810 is touch-sensitive, a portion or all of the keypad 808 can be presented by way of the display 810 with navigation features.
The display 810 can use touch screen technology to also serve as a user interface for detecting user input. As a touch screen display, the communication device 800 can be adapted to present a user interface with graphical user interface (GUI) elements that can be selected by a user with a touch of a finger. The touch screen display 810 can be equipped with capacitive, resistive or other forms of sensing technology to detect how much surface area of a user's finger has been placed on a portion of the touch screen display. This sensing information can be used to control the manipulation of the GUI elements or other functions of the user interface. The display 810 can be an integral part of the housing assembly of the communication device 800 or an independent device communicatively coupled thereto by a tethered wireline interface (such as a cable) or a wireless interface.
The UI 804 can also include an audio system 812 that utilizes audio technology for conveying low volume audio (such as audio heard in proximity of a human ear) and high volume audio (such as speakerphone for hands free operation). The audio system 812 can further include a microphone for receiving audible signals of an end user. The audio system 812 can also be used for voice recognition applications. The UI 804 can further include an image sensor 813 such as a charged coupled device (CCD) camera for capturing still or moving images.
The power supply 814 can utilize common power management technologies such as replaceable and rechargeable batteries, supply regulation technologies, and/or charging system technologies for supplying energy to the components of the communication device 800 to facilitate long-range or short-range portable applications. Alternatively, or in combination, the charging system can utilize external power sources such as DC power supplied over a physical interface such as a USB port or other suitable tethering technologies.
The location receiver 816 can utilize location technology such as a global positioning system (GPS) receiver capable of assisted GPS for identifying a location of the communication device 800 based on signals generated by a constellation of GPS satellites, which can be used for facilitating location services such as navigation. The motion sensor 818 can utilize motion sensing technology such as an accelerometer, a gyroscope, or other suitable motion sensing technology to detect motion of the communication device 800 in three-dimensional space. The orientation sensor 820 can utilize orientation sensing technology such as a magnetometer to detect the orientation of the communication device 800 (north, south, west, and east, as well as combined orientations in degrees, minutes, or other suitable orientation metrics).
The communication device 800 can use the transceiver 802 to also determine a proximity to a cellular, WIFI™, BLUETOOTH™, or other wireless access points by sensing techniques such as utilizing a received signal strength indicator (RSSI) and/or signal time of arrival (TOA) or time of flight (TOF) measurements. The controller 806 can utilize computing technologies such as a microprocessor, a digital signal processor (DSP), programmable gate arrays, application specific integrated circuits, and/or a video processor with associated storage memory such as Flash, ROM, RAM, SRAM, DRAM or other storage technologies for executing computer instructions, controlling, and processing data supplied by the aforementioned components of the communication device 400.
Other components not shown in
The communication device 800 as described herein can operate with more or less of the circuit components shown in
It should be understood that devices described in the exemplary embodiments can be in communication with each other via various wireless and/or wired methodologies. The methodologies can be links that are described as coupled, connected and so forth, which can include unidirectional and/or bidirectional communication over wireless paths and/or wired paths that utilize one or more of various protocols or methodologies, where the coupling and/or connection can be direct (e.g., no intervening processing device) and/or indirect (e.g., an intermediary processing device such as a router).
The machine may comprise a server computer, a client user computer, a personal computer (PC), a tablet PC, a smart phone, a laptop computer, a desktop computer, a control system, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. It will be understood that a communication device of the subject disclosure includes broadly any electronic device that provides voice, video or data communication. Further, while a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methods discussed herein.
The computer system 900 may include a processor (or controller) 902 (e.g., a central processing unit (CPU), a graphics processing unit (GPU, or both), a main memory 904 and a static memory 906, which communicate with each other via a bus 908. The computer system 900 may further include a display unit 910 (e.g., a liquid crystal display (LCD), a flat panel, or a solid state display. The computer system 900 may include an input device 912 (e.g., a keyboard), a cursor control device 914 (e.g., a mouse), a disk drive unit 916, a signal generation device 918 (e.g., a speaker or remote control) and a network interface device 920. In distributed environments, the embodiments described in the subject disclosure can be adapted to utilize multiple display units 910 controlled by two or more computer systems 900. In this configuration, presentations described by the subject disclosure may in part be shown in a first of the display units 910, while the remaining portion is presented in a second of the display units 910.
The disk drive unit 916 may include a tangible computer-readable storage medium 922 on which is stored one or more sets of instructions (e.g., software 924) embodying any one or more of the methods or functions described herein, including those methods illustrated above. The instructions 924 may also reside, completely or at least partially, within the main memory 904, the static memory 906, and/or within the processor 902 during execution thereof by the computer system 900. The main memory 904 and the processor 902 also may constitute tangible computer-readable storage media.
Dedicated hardware implementations including, but not limited to, application specific integrated circuits, programmable logic arrays and other hardware devices that can likewise be constructed to implement the methods described herein. Application specific integrated circuits and programmable logic array can use downloadable instructions for executing state machines and/or circuit configurations to implement embodiments of the subject disclosure. Applications that may include the apparatus and systems of various embodiments broadly include a variety of electronic and computer systems. Some embodiments implement functions in two or more specific interconnected hardware modules or devices with related control and data signals communicated between and through the modules, or as portions of an application-specific integrated circuit. Thus, the example system is applicable to software, firmware, and hardware implementations.
In accordance with various embodiments of the subject disclosure, the operations or methods described herein are intended for operation as software programs or instructions running on or executed by a computer processor or other computing device, and which may include other forms of instructions manifested as a state machine implemented with logic components in an application specific integrated circuit or field programmable gate array. Furthermore, software implementations (e.g., software programs, instructions, etc.) including, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein. It is further noted that a computing device such as a processor, a controller, a state machine or other suitable device for executing instructions to perform operations or methods may perform such operations directly or indirectly by way of one or more intermediate devices directed by the computing device.
While the tangible computer-readable storage medium 622 is shown in an example embodiment to be a single medium, the term “tangible computer-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “tangible computer-readable storage medium” shall also be taken to include any non-transitory medium that is capable of storing or encoding a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methods of the subject disclosure.
The term “tangible computer-readable storage medium” shall accordingly be taken to include, but not be limited to: solid-state memories such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other re-writable (volatile) memories, a magneto-optical or optical medium such as a disk or tape, or other tangible media which can be used to store information. Accordingly, the disclosure is considered to include any one or more of a tangible computer-readable storage medium, as listed herein and including art-recognized equivalents and successor media, in which the software implementations herein are stored.
Although the present specification describes components and functions implemented in the embodiments with reference to particular standards and protocols, the disclosure is not limited to such standards and protocols. Each of the standards for Internet and other packet switched network transmission (e.g., TCP/IP, UDP/IP, HTML, and HTTP) represent examples of the state of the art. Such standards are from time-to-time superseded by faster or more efficient equivalents having essentially the same functions. Wireless standards for device detection (e.g., RFID), short-range communications (e.g., BLUETOOTH™, WIFI™, ZIGBEE™), and long-range communications (e.g., WiMAX, GSM™, CDMA, LTE™) can be used by computer system 900.
The illustrations of embodiments described herein are intended to provide a general understanding of the structure of various embodiments, and they are not intended to serve as a complete description of all the elements and features of apparatus and systems that might make use of the structures described herein. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. The exemplary embodiments can include combinations of features and/or steps from multiple embodiments. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. Figures are also merely representational and may not be drawn to scale. Certain proportions thereof may be exaggerated, while others may be minimized. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
Although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, can be used in the subject disclosure.
The Abstract of the Disclosure is provided with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.
The present application claims priority to and is a continuation of U.S. patent application Ser. No. 15/061,373, filed Mar. 4, 2016, which is a continuation of U.S. patent application Ser. No. 13/956,690, filed Aug. 1, 2013, now U.S. Pat. No. 9,313,680, which claims the benefit of priority to U.S. Provisional Application No. 61/792,184 filed on Mar. 15, 2013, the disclosures of which are hereby incorporated by reference herein in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
3732500 | Dishal | May 1973 | A |
3781705 | Dishal | Dec 1973 | A |
3783397 | Dishal | Jan 1974 | A |
3887222 | Hammond | Jun 1975 | A |
3911366 | Baghdady | Oct 1975 | A |
4027264 | Gutleber | May 1977 | A |
4328591 | Baghdady | May 1982 | A |
4513249 | Baghdady | Apr 1985 | A |
4712235 | Jones | Dec 1987 | A |
4761829 | Lynk et al. | Aug 1988 | A |
4859958 | Myers | Aug 1989 | A |
4992747 | Myers | Feb 1991 | A |
5038115 | Myers | Aug 1991 | A |
5038145 | DeCesare et al. | Aug 1991 | A |
5048015 | Zilberfarb | Sep 1991 | A |
5168508 | Iwasaki | Dec 1992 | A |
5185762 | Schilling | Feb 1993 | A |
5226057 | Boren | Jul 1993 | A |
5263048 | Wade | Nov 1993 | A |
5282023 | Scarpa | Jan 1994 | A |
5301197 | Yamada et al. | Apr 1994 | A |
5303413 | Braegas | Apr 1994 | A |
5307517 | Rich | Apr 1994 | A |
5325204 | Scarpa | Jun 1994 | A |
5343496 | Honig | Aug 1994 | A |
5381150 | Hawkins et al. | Jan 1995 | A |
5475868 | Duque-Anton et al. | Dec 1995 | A |
5497505 | Koohgoli et al. | Mar 1996 | A |
5500872 | Kinney | Mar 1996 | A |
5541959 | Myers | Jul 1996 | A |
5570350 | Myer | Oct 1996 | A |
5596600 | Dimos | Jan 1997 | A |
5640146 | Campana | Jun 1997 | A |
5640385 | Long | Jun 1997 | A |
RE35650 | Partyka | Nov 1997 | E |
5703874 | Schilling | Dec 1997 | A |
5721733 | Wang et al. | Feb 1998 | A |
5758275 | Cox | May 1998 | A |
5822373 | Addy | Oct 1998 | A |
5838742 | Abu-Dayya | Nov 1998 | A |
5852630 | Langberg | Dec 1998 | A |
5857143 | Kataoka | Jan 1999 | A |
5926761 | Reed et al. | Jul 1999 | A |
5947505 | Martin | Sep 1999 | A |
5949368 | DeCesare | Sep 1999 | A |
5960329 | Ganesh et al. | Sep 1999 | A |
5966657 | Sporre | Oct 1999 | A |
5970105 | Dacus | Oct 1999 | A |
5974101 | Nago | Oct 1999 | A |
5978362 | Lee | Nov 1999 | A |
5991273 | Abu-Dayya et al. | Nov 1999 | A |
5999574 | Sun et al. | Dec 1999 | A |
6005899 | Khayrallah | Dec 1999 | A |
6009129 | Kenney et al. | Dec 1999 | A |
6020783 | Coppola | Feb 2000 | A |
6035213 | Tokuda | Mar 2000 | A |
6038250 | Shou et al. | Mar 2000 | A |
6047175 | Trompower | Apr 2000 | A |
6052158 | Nielsen | Apr 2000 | A |
6104934 | Patton | Aug 2000 | A |
6115409 | Upadhyay | Sep 2000 | A |
6115580 | Chuprun et al. | Sep 2000 | A |
6118805 | Bergstrom et al. | Sep 2000 | A |
6122309 | Bergstrom et al. | Sep 2000 | A |
6125139 | Hendrickson et al. | Sep 2000 | A |
6127962 | Martinson | Oct 2000 | A |
6130907 | Chen | Oct 2000 | A |
6133942 | Lee | Oct 2000 | A |
6167240 | Carlsson et al. | Dec 2000 | A |
6167244 | Tomoe | Dec 2000 | A |
6205334 | Dent | Mar 2001 | B1 |
6208629 | Jaszewski et al. | Mar 2001 | B1 |
6215812 | Young | Apr 2001 | B1 |
6289004 | Mesecher et al. | Sep 2001 | B1 |
6313620 | Richardson | Nov 2001 | B1 |
6327245 | Satyanarayana et al. | Dec 2001 | B1 |
6327312 | Jovanovich | Dec 2001 | B1 |
6360077 | Mizoguchi | Mar 2002 | B2 |
6377606 | Toskala et al. | Apr 2002 | B1 |
6393284 | Dent | May 2002 | B1 |
6405043 | Jensen et al. | Jun 2002 | B1 |
6421077 | Reed et al. | Jul 2002 | B1 |
6426983 | Rakib et al. | Jul 2002 | B1 |
6430164 | Jones | Aug 2002 | B1 |
6490460 | Soliman | Dec 2002 | B1 |
6577670 | Roberts | Jun 2003 | B1 |
6580899 | Dalgleish et al. | Jun 2003 | B1 |
6621454 | Reudink et al. | Sep 2003 | B1 |
6631264 | Tat et al. | Oct 2003 | B1 |
6631266 | Lee et al. | Oct 2003 | B1 |
6671338 | Gamal et al. | Dec 2003 | B1 |
6678520 | Wang et al. | Jan 2004 | B1 |
6704378 | Jagger | Mar 2004 | B2 |
6718166 | Cordone | Apr 2004 | B2 |
6791995 | Azenkot et al. | Sep 2004 | B1 |
6807405 | Jagger | Oct 2004 | B1 |
6843819 | Suzuki et al. | Jan 2005 | B2 |
6850764 | Patel | Feb 2005 | B1 |
6920424 | Padmanabhan | Jul 2005 | B2 |
6959170 | Vannatta | Oct 2005 | B2 |
6975673 | Rouquette et al. | Dec 2005 | B1 |
6976044 | Kilani | Dec 2005 | B1 |
7003310 | Youssefmir et al. | Feb 2006 | B1 |
7031266 | Patel et al. | Apr 2006 | B1 |
7054396 | Shan | May 2006 | B2 |
7089008 | Bäck et al. | Aug 2006 | B1 |
7103316 | Hall | Sep 2006 | B1 |
7317698 | Jagger | Jan 2008 | B2 |
7359691 | Adachi et al. | Apr 2008 | B2 |
7408907 | Diener et al. | Aug 2008 | B2 |
7424002 | Barratt et al. | Sep 2008 | B2 |
7424268 | Diener et al. | Sep 2008 | B2 |
7457382 | Jones | Nov 2008 | B1 |
7477915 | Leinonen et al. | Jan 2009 | B2 |
7525942 | Cordone | Apr 2009 | B2 |
7929953 | Jiang | Apr 2011 | B2 |
8055191 | Unger | Nov 2011 | B2 |
8219105 | Kronestedt et al. | Jul 2012 | B2 |
8229368 | Immendorf et al. | Jul 2012 | B1 |
8238954 | Liu et al. | Aug 2012 | B2 |
8412256 | Lee et al. | Apr 2013 | B2 |
8422469 | Guvenc | Apr 2013 | B2 |
8478342 | Vedantham et al. | Jul 2013 | B2 |
8503938 | Laroia et al. | Aug 2013 | B2 |
8583170 | Sundström et al. | Nov 2013 | B2 |
8605686 | Lundby et al. | Dec 2013 | B2 |
8718024 | Jagger et al. | May 2014 | B2 |
8781044 | Cordone et al. | Jul 2014 | B2 |
8811213 | Rai et al. | Aug 2014 | B1 |
8811552 | Bayesteh et al. | Aug 2014 | B2 |
8989235 | Myers et al. | Mar 2015 | B2 |
9008680 | Abdelmonem | Apr 2015 | B2 |
9042497 | Wong et al. | May 2015 | B2 |
9071343 | Abdelmonem | Jun 2015 | B2 |
9226303 | Kronestedt | Dec 2015 | B2 |
9369909 | Wong et al. | Jun 2016 | B2 |
9729301 | Galeev et al. | Aug 2017 | B2 |
9742547 | Wang et al. | Aug 2017 | B2 |
20010046867 | Mizoguchi | Nov 2001 | A1 |
20020057751 | Jagger | May 2002 | A1 |
20020110206 | Becker et al. | Aug 2002 | A1 |
20020155812 | Takada | Oct 2002 | A1 |
20030081277 | Corbeil et al. | May 2003 | A1 |
20030123530 | Maeda | Jul 2003 | A1 |
20030142759 | Anderson et al. | Jul 2003 | A1 |
20030193366 | Barksdale | Oct 2003 | A1 |
20030216122 | Cordone | Nov 2003 | A1 |
20040042561 | Ho et al. | Mar 2004 | A1 |
20040048574 | Walker et al. | Mar 2004 | A1 |
20040088637 | Wada | May 2004 | A1 |
20040162093 | Bevan | Aug 2004 | A1 |
20040223484 | Xia et al. | Nov 2004 | A1 |
20050078734 | Baker | Apr 2005 | A1 |
20050117676 | Liu | Jun 2005 | A1 |
20050201498 | Nakai | Sep 2005 | A1 |
20060025127 | Cromer et al. | Feb 2006 | A1 |
20060068849 | Bernhard et al. | Mar 2006 | A1 |
20060094372 | Ahn et al. | May 2006 | A1 |
20060105769 | Flondro et al. | May 2006 | A1 |
20060153283 | Scharf et al. | Jul 2006 | A1 |
20060246938 | Hulkkonen et al. | Nov 2006 | A1 |
20070014254 | Chung et al. | Jan 2007 | A1 |
20070025455 | Greenwood et al. | Feb 2007 | A1 |
20070047494 | Cordone | Mar 2007 | A1 |
20070091896 | Liu | Apr 2007 | A1 |
20070105520 | Van Houtum | May 2007 | A1 |
20070115878 | Ashish et al. | May 2007 | A1 |
20070129071 | Shapira et al. | Jun 2007 | A1 |
20070173252 | Jiang | Jul 2007 | A1 |
20070183483 | Narayan | Aug 2007 | A1 |
20070274279 | Wood | Nov 2007 | A1 |
20080043612 | Geile | Feb 2008 | A1 |
20080043657 | Ishii et al. | Feb 2008 | A1 |
20080081655 | Shin et al. | Apr 2008 | A1 |
20080089296 | Kazmi et al. | Apr 2008 | A1 |
20080166976 | Rao et al. | Jul 2008 | A1 |
20090086841 | Guo et al. | Apr 2009 | A1 |
20090131067 | Aaron et al. | May 2009 | A1 |
20090161614 | Grandblaise | Jun 2009 | A1 |
20090233544 | Oyman et al. | Sep 2009 | A1 |
20090233568 | Zhang | Sep 2009 | A1 |
20090247107 | Roy et al. | Oct 2009 | A1 |
20090325509 | Mattisson et al. | Dec 2009 | A1 |
20100002575 | Eichinger et al. | Jan 2010 | A1 |
20100029289 | Love et al. | Feb 2010 | A1 |
20100046374 | Ludwig et al. | Feb 2010 | A1 |
20100054373 | Reial et al. | Mar 2010 | A1 |
20100061244 | Meier et al. | Mar 2010 | A1 |
20100099415 | Li et al. | Apr 2010 | A1 |
20100118921 | Abdelmonem et al. | May 2010 | A1 |
20100157934 | Tanno et al. | Jun 2010 | A1 |
20100159858 | Dent et al. | Jun 2010 | A1 |
20100167778 | Raghothaman et al. | Jul 2010 | A1 |
20100202400 | Richardson | Aug 2010 | A1 |
20100220670 | Teo et al. | Sep 2010 | A1 |
20100227613 | Kim et al. | Sep 2010 | A1 |
20100246503 | Fox et al. | Sep 2010 | A1 |
20100248736 | Hulkkonen | Sep 2010 | A1 |
20100254292 | Kim et al. | Oct 2010 | A1 |
20100255868 | Lee et al. | Oct 2010 | A1 |
20100279724 | Li et al. | Nov 2010 | A1 |
20100309864 | Tamaki et al. | Dec 2010 | A1 |
20100310026 | Sikri et al. | Dec 2010 | A1 |
20100315970 | Ramamurthi et al. | Dec 2010 | A1 |
20100330919 | Gurney et al. | Dec 2010 | A1 |
20110014938 | Shekalim | Jan 2011 | A1 |
20110096703 | Nentwig | Apr 2011 | A1 |
20110117967 | Vedantham et al. | May 2011 | A1 |
20110136497 | Youtz et al. | Jun 2011 | A1 |
20110149764 | Wietfeldt et al. | Jun 2011 | A1 |
20110164659 | Kawamura et al. | Jul 2011 | A1 |
20110183679 | Moon et al. | Jul 2011 | A1 |
20110188544 | Ponnuswamy et al. | Aug 2011 | A1 |
20110200126 | Bontu et al. | Aug 2011 | A1 |
20110222591 | Furudate et al. | Sep 2011 | A1 |
20110258678 | Cowling et al. | Oct 2011 | A1 |
20110275399 | Englund et al. | Nov 2011 | A1 |
20110305306 | Hu et al. | Dec 2011 | A1 |
20110310747 | Seo et al. | Dec 2011 | A1 |
20120021753 | Damnjanovic et al. | Jan 2012 | A1 |
20120028663 | Nejatian | Feb 2012 | A1 |
20120032854 | Bull et al. | Feb 2012 | A1 |
20120051315 | Wang et al. | Mar 2012 | A1 |
20120069806 | Norlén et al. | Mar 2012 | A1 |
20120082050 | Lysejko | Apr 2012 | A1 |
20120134280 | Rotvold et al. | May 2012 | A1 |
20120163223 | Lo et al. | Jun 2012 | A1 |
20120164950 | Nentwig et al. | Jun 2012 | A1 |
20120182930 | Sawai et al. | Jul 2012 | A1 |
20120195216 | Wu et al. | Aug 2012 | A1 |
20120207038 | Choi et al. | Aug 2012 | A1 |
20120213116 | Koo et al. | Aug 2012 | A1 |
20120236731 | Beaudin | Sep 2012 | A1 |
20120276937 | Astely et al. | Nov 2012 | A1 |
20120282889 | Tanaka | Nov 2012 | A1 |
20120282943 | Hsiao | Nov 2012 | A1 |
20120307770 | Kubota | Dec 2012 | A1 |
20130012134 | Jin et al. | Jan 2013 | A1 |
20130029658 | Jagger et al. | Jan 2013 | A1 |
20130058300 | Perets et al. | Mar 2013 | A1 |
20130071112 | Melester et al. | Mar 2013 | A1 |
20130090125 | Clifton et al. | Apr 2013 | A1 |
20130107737 | Lee et al. | May 2013 | A1 |
20130115988 | Sun | May 2013 | A1 |
20130115999 | Sirotkin et al. | May 2013 | A1 |
20130142136 | Pi et al. | Jun 2013 | A1 |
20130143592 | Brisebois et al. | Jun 2013 | A1 |
20130150106 | Bucknell et al. | Jun 2013 | A1 |
20130163570 | Zhang et al. | Jun 2013 | A1 |
20130170829 | Khatana | Jul 2013 | A1 |
20130242791 | Lim et al. | Sep 2013 | A1 |
20130287077 | Fernando et al. | Oct 2013 | A1 |
20130316710 | Maaref et al. | Nov 2013 | A1 |
20140029524 | Dimou et al. | Jan 2014 | A1 |
20140086191 | Berntsen et al. | Mar 2014 | A1 |
20140105136 | Tellado et al. | Apr 2014 | A1 |
20140105262 | Alloin et al. | Apr 2014 | A1 |
20140160955 | Lum et al. | Jun 2014 | A1 |
20140169279 | Song et al. | Jun 2014 | A1 |
20140206339 | Lindoff et al. | Jul 2014 | A1 |
20140256322 | Zhou et al. | Sep 2014 | A1 |
20140269318 | Hasarchi et al. | Sep 2014 | A1 |
20140274100 | Galeev et al. | Sep 2014 | A1 |
20140315593 | Vrzic et al. | Oct 2014 | A1 |
20140378077 | Din | Dec 2014 | A1 |
20150092621 | Jalloul | Apr 2015 | A1 |
20150263844 | Kinnunen | Sep 2015 | A1 |
20150295695 | Davydov et al. | Oct 2015 | A1 |
20160135061 | Abdelmonem | May 2016 | A1 |
20160192362 | Galeev et al. | Jun 2016 | A1 |
20160198353 | Abdelmonem | Jul 2016 | A1 |
20160249364 | Siomina | Aug 2016 | A1 |
20160249367 | Abdelmonem | Aug 2016 | A1 |
20160254840 | Abdelmonem et al. | Sep 2016 | A1 |
20160323086 | Abdelmonem et al. | Nov 2016 | A1 |
20160353455 | Jagger | Dec 2016 | A1 |
20170207816 | Abdelmonem et al. | Jul 2017 | A1 |
20170230983 | Abdelmonem et al. | Aug 2017 | A1 |
20170280464 | Jagger | Sep 2017 | A1 |
20170302332 | Abdelmonem et al. | Oct 2017 | A1 |
20170310450 | Galeev | Oct 2017 | A1 |
20170317807 | Abdelmonem et al. | Nov 2017 | A1 |
20170374625 | Abdelmodem et al. | Dec 2017 | A1 |
20170374626 | Abdelmonem et al. | Dec 2017 | A1 |
20180069682 | Abdelmonem et al. | Mar 2018 | A1 |
20180167189 | Abdelmonem et al. | Jun 2018 | A9 |
20180206240 | Abdelmonem | Jul 2018 | A1 |
20180254878 | Abdelmonem et al. | Sep 2018 | A1 |
20180324710 | Abdelmonem et al. | Nov 2018 | A1 |
20180324812 | Abdelmonem et al. | Nov 2018 | A1 |
20180332593 | Galeev et al. | Nov 2018 | A1 |
20180332594 | Abdelmonem et al. | Nov 2018 | A1 |
20180375546 | Abdelmonem et al. | Dec 2018 | A1 |
20190053247 | Abdelmonem et al. | Feb 2019 | A1 |
Number | Date | Country |
---|---|---|
2260653 | Jan 2000 | CA |
2288633 | Apr 2000 | CA |
1173101 | Feb 1998 | CN |
0704986 | Apr 1996 | EP |
0812069 | Dec 1997 | EP |
2288061 | Feb 2011 | EP |
2800412 | Nov 2014 | EP |
2304000 | Mar 1997 | GB |
06-061876 | Mar 1994 | JP |
09-326713 | Dec 1997 | JP |
199810514 | Mar 1998 | WO |
2000046929 | Aug 2000 | WO |
200046929 | Aug 2000 | WO |
2007063514 | Jun 2007 | WO |
2008033369 | Mar 2008 | WO |
2009005420 | Jan 2009 | WO |
2009019074 | Feb 2009 | WO |
20120116755 | Sep 2012 | WO |
WO2012158046 | Nov 2012 | WO |
2012172476 | Dec 2012 | WO |
Entry |
---|
23.203 Policy and Charging Control Architecture. |
“Excel Average Formula/Function without including Zeros”, Ozgrid.com, Aug. 8, 2011, 3 pages. |
“International Search Report & Written Opinion”, PCT/US01/11351, dated Apr. 2002. |
“PCT/US16/26212 International Search Report dated Jun. 7, 2016.”, dated Jun. 7, 2016. |
“U.S. Appl. No. 13/956,690, filed Aug. 1, 2013, pp. 4-10”. |
Berlemann, et al., “Cognitive Radio and IVIanagement of Spectrtun and Radio Resources in Reconfigurable Networks”, Wireless World Research Forum, Working Group 6 White Paper, 2005. |
Kim, Kihong , “Interference Mitigation in Wireless Communications”, Aug. 23, 2005, 133 pages. |
Milstein, “Interference Rejection Techniques in Spread Spectrum Communications”, Proceedings of the IEEE, vol. 76, No. 6, Jun. 1988. |
Patent Cooperation Treaty, “International Search Report and Written Opinion dated Jun. 1, 2010, International Application No. PCT/US2009/064191”. |
Patent Cooperation Treaty, “International Search Report and Written Opinion dated Jun. 1, 2010, from International Application No. PCT/US2009/064191”. |
Poor, et al., “Narrowband Interference Suppression in Spread Spectrum COMA”, IEEE Personal Communications Magazine, Third Quarter, 1994, pp. 14-27. |
Salgado-Galicia, Hector et al., “A Narrowband Approach to Efficient PCS Spectrum Sharing Through Decentralized DCA Access Policies”, IEEE Personal Communications, Feb. 1997, 24-34. |
Zyren, Jim et al., “Overview of the 3GPP Long Term Evolution Physical Layer”, Freescale Semiconductor, Jul. 2007, 27 pages. |
Number | Date | Country | |
---|---|---|---|
20170188374 A1 | Jun 2017 | US |
Number | Date | Country | |
---|---|---|---|
61792184 | Mar 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15061373 | Mar 2016 | US |
Child | 15458514 | US | |
Parent | 13956690 | Aug 2013 | US |
Child | 15061373 | US |