The invention described herein generally relates to Software Defined Radios (SDR) and SDR systems. In particular, a system and method of providing automated availability and integrity verification for software defined radios is described.
Software Defined Radio methodology is rapidly gaining favor as a way to architect and design radio communication systems with greatly improved interoperability and ability to accommodate future waveform variants. SDR refers to wireless communication in which the transmitter modulation is generated or defined by a computer, and the receiver uses a computer to recover the signal intelligence. To select the desired modulation type, the proper programs are run by microcomputers that control the transmitter and receiver.
A typical voice SDR transmitter, such as may be used in mobile two-way radio or cellular telephone communication, include the following stages: Microphone; Audio amplifier; Analog-to-digital converter (ADC) that converts the voice audio to digital data; Modulator that impresses the digital intelligence onto a radio-frequency (RF) carrier; Series of amplifiers that boosts the RF carrier to the power level necessary for transmission; and Transmitting antenna. Typically, the ADC and Modulator functions are carried out by computer-controlled circuits whose parameters are determined by software, in an SDR.
A typical receiver designed to intercept the above-described voice SDR signal may employ the following stages, essentially reversing the transmitter's action: Receiving antenna; Superheterodyne system that boosts incoming RF signal strength and converts it to a lower frequency; Demodulator that separates the digital intelligence from the RF carrier; Digital-to-analog converter (DAC) that generates a voice waveform from the digital data; Audio amplifier; and Speaker, earphone, and/or headset. Typically, the demodulator and DAC functions are carried out by computer-controlled circuits whose parameters are determined by software, in an SDR.
The most significant asset of SDR is versatility. Wireless systems employ protocols that vary from one service to another. Even in the same type of service, for example, cellular telephones, the protocol often differs from country to country. A single SDR set with an all-inclusive software repertoire may be used in any mode, anywhere in the world. Changing the service type, the mode, and/or the modulation protocol involves simply selecting and executing the requisite computer program. The ultimate goal of SDR engineers is to provide a single radio transceiver capable of playing the roles of cordless telephone, cell phone, wireless fax, wireless e-mail system, pager, wireless videoconferencing unit, wireless Web browser, Global Positioning System (GPS) unit, and other functions to be later developed, operable from any location on the surface or proximate the surface of the earth, and perhaps in space as well.
The United States Department of Defense (DoD) Joint Tactical Radio System (JTRS) initiative has established an Open Standard Architecture for implementation of military communication waveforms that is specifically intended to meet a subset of these objectives. Such Joint Tactical Radio Systems are available from Rockwell Collins, Inc. of Cedar Rapids, Iowa.
There is growing interest in applying an Open Standard SDR Architecture to commercial applications such as avionics communication, navigation and surveillance (CNS). The characteristics of commercial CNS waveforms are quite different from the military JTRS communication waveforms, and, in general, are less complex to implement. A key difference between military communications and commercial avionics are the requirements associated with safety. The safety requirements associated with commercial CNS avionics typically involve gaining approval for use (generally referred to as “certification”) by the appropriate civil aviation authority, such as the Federal Aviation Administration (FAA) in the United States or the Joint Aviation Administration (JAA) in Europe. The safety requirements for the CNS functions typically address the integrity and availability, and for some functions, the continuity. Thus, it is desirable to provide an avionics commercial CNS system architecture that addresses the safety requirements while retaining compatibility with an appropriate SDR standard, preferably the Open Standard Architecture established by the DoD as part of the JTRS program.
In particular, there is a need for SDR technology that allows a single set of hardware to perform multiple functions by software reconfiguration. Further, there is a need for reconfigurable systems that automatically and autonomously verify the availability and integrity of a reconfigured SDR using available SDR resources. Further still, there is a need for such a reconfigurable system that satisfies certification requirements with a robust means to automatically and autonomously verify the availability and integrity of the reconfigured SDR using available SDR resources.
What is provided is a method of providing at least one of availability verification and integrity checking for receiving using a software defined radio (SDR). The method comprises reconfiguring at least one radio channel, the at least one radio channel each having at least one radio function associated therewith. The method also comprises sending a test signal using a second radio channel and receiving the test signal by the at least one radio channel. Further, the method comprises checking for a test characteristic of the test signal and making the at least one radio channel and at least one radio function available for use.
What is also provided is a method of providing at least one of availability verification and integrity checking for transmitting using a software defined radio. The method comprises reconfiguring at least one radio channel. The at least one radio channel each has at least one radio function associated therewith. The method also comprises sending a test signal using the at least one radio channel and receiving the test signal by a second radio channel. Further, the method comprises checking for a test characteristic of the test signal after being received by the at least one radio channel and making the at least one radio channel and at least one radio function available for use.
Further, what is provided is a software defined radio. The software defined radio comprises a modem bank at least partially defined by software running on a processor. The software defined radio also comprises an antenna group translator coupled to the modem bank. The software defined radio also comprises at least one antenna coupled to the antenna group translator. Further, the software defined radio comprises a program stored in a memory and running on the processor. The program is configured to generate a test signal to be leaked by a first of at least two channels and to be received by the second of the two channels. The program is configured to at least one of verify the availability of a function of one of the at least two channels and determine the integrity of the function of the one of the at least two channels.
Alternative exemplary embodiments relate to other features and combination of features and combination of features as may be generally recited in the claims.
A better understanding of the features and advantages of the present invention will be obtained by reference to the following detailed description that sets forth illustrative embodiments by way of example only, in which the principles of the invention are utilized, and the accompanying drawings, of which:
Before describing in detail the particular improved system and method, it should be observed that the invention includes, but is not limited to a novel structural combination of conventional data/signal processing components and communications circuits, and not in the particular detailed configurations thereof. Accordingly, the structure, methods, functions, control and arrangement of conventional components and circuits have, for the most part, been illustrated in the drawings by readily understandable block representations and schematic diagrams, in order not to obscure the disclosure with structural details which will be readily apparent to those skilled in the art, having the benefit of the description herein. Further, the invention is not limited to the particular embodiments depicted in the exemplary diagrams, but should be construed in accordance with the language in the claims.
A software defined radio (SDR) is characterized by software executing on microprocessors and configurations loaded into programmable hardware such as field programmable gate arrays (FPGAs). To facilitate software design, portability and interoperability, a Software Communications Architecture (SCA) may be used. The SCA specified for JTRS is one instantiation of an SCA that was specifically defined to provide an abstraction layer between SDR waveform application software and the underlying hardware platform. The elements of the JTRS SCA are a Portable Operating System Interface (POSIX), Common Object Request Broker Architecture (CORBA), and a set of services and utilities labeled Core Framework. Application of the SCA to radio communication systems insures interoperability and portability of these systems.
The platform abstraction provided by the SCA makes it possible to use a wide variety of microprocessors to host the SCA operating environment (OE). A basic requirement for the platform microprocessor is that it must provide sufficient computing performance to meet the real time requirements of the waveform being executed on the platform.
In accordance with an exemplary embodiment, the method and apparatus discussed may employ any kind of hardware to run the software embodying the invention, including but not limited to a personal computer, Rockwell Collins Advanced Architecture MicroProcessor (AAMP), ARM processor, XScale processor, Digital Signal Processor (DSP), Application Specific Integrated Circuit (ASIC) or programmable platform ASIC, FPGA, General Purpose Processor (GPP), microprocessor, mainframe or dedicated circuit with memory, so that in general any compatible piece of hardware or virtual machine can be configured to run the software disclosed.
Thus, an exemplary method and apparatus for constructing the invention is a computing platform running a software program, which may be written in any computer language (such as C, C++, Ada, Perl, Java or the like), preferably an Object Oriented programming (OOP) language, run by a computer system having an operating system. The computer system typically has one or more processors, primary and secondary memory cooperating with the processor(s), which executes instructions stored in the memory, I/O means, and any necessary specialized hardware or firmware. Depending on the language used to construct and implement the software tool, the source code, object code and/or executables of the tool may have any number of classes, functions, objects, variables, templates, lines of code, portions of code, components and constructs (collectively and generally, “a process step”, “step”, “block”, “functional module” or “software module”) to carry out the invention in successive stages as described and taught herein, and may be either a standalone software application, or employed inside of or called by another software application, or as firmware. The software process or software module may be constructed so that one portion of code in the application performs a plurality of functions, as for instance in Object Oriented programming (e.g., an overloaded process). The converse is also true, in that a plurality of portions of code could perform a plurality of functions, and still be functionally the same as a single portion of code. At any stage of the process of the invention, intermediate values, variables and data may be stored for later use by the program. In addition, the executable or source code data comprising the software of the invention may reside on computer readable storage medium (e.g., a magnetic disk, which may be portable, such as a hard drive, floppy drive; memory (e.g., flash RAM); or a DVD or CD-ROM disk).
In
In accordance with an exemplary embodiment, radio system 100 may be used in a communication, navigation, and surveillance (CNS) application for an aircraft. Radio system 100 comprises an SDR which allows a single set of hardware to perform multiple functions by software reconfiguration. Alternatively, radio 100 may be used in other applications which may benefit from the reconfigurability of the radio node with regard to waveforms and other functionality. In SDR 100 modems 160 may be software based modems which provide reconfigurable modulation and demodulation functions. In CNS applications SDR 100 may be used for a variety of applications and associated waveforms including, but not limited to VHF (Very High Frequency) Omni-directional Radio-range (VOR), High Frequency (HF), Localizer (LOC), Glide Slope (GS), Marker Beacon (MB), VHF Communications (VHF COM), Satellite Communications (SATCOM), etc.
Because of the number and variety of signals being received and transmitted in a CNS system and because not all functions need to be used simultaneously, it is therefore beneficial to utilize a reconfigurable radio such as SDR 100. However, the reconfigurability creates certification challenges because the functionality of the reconfiguration must be verified before being used for life-critical applications. Thus, SDR 100 may be configured with software functionality which uses available resources (at least one of the Interface Processor 170, Modems 160, Waveform Priority Arbitrator 150, RF front ends 130, Antenna Switch 120, and Antenna 110) to automatically and autonomously verify the new configuration of a target set of hardware and software. The resources that are used to verify the functionality of the SDR 100 configuration (or reconfiguration) are referred to herein as a “‘spare’ channel set”, and in the preferred embodiment consist of one Modem 160, one RF front end 140, and an appropriate portion of the software and hardware in Interface Processor 170, Waveform Priority Arbitrator 150, and Antenna Switch 120 which support generating the test signal.
In accordance with an exemplary embodiment, the verification method may depend on the configuration being tested. For example, a receiver may be tested by generating a real-world test signal with the ‘spare’ channel set. Similarly, a transmitter may be tested by operating the transmitter briefly and using the ‘spare’ channel set as a receiver. In an exemplary embodiment, coupling between operation and ‘spare’ channel sets may occur in antenna switch module 120, using an intentionally “leaky” RF path, or alternatively outside the aircraft using the existing antennas 110. Locally generated test signals may be configured to contain real-world modulation, be low power, and contain identifiable characteristics (to allow discrimination between test signals and operational signals and to prevent interference with off-aircraft systems). By providing coupling between test and operational resources that occurs at or near the antennas, the availability and integrity of the entire functional chain may be verified.
Referring now to
Referring now to
Referring now to
Referring now to
In accordance with an exemplary embodiment, the entire process is transparent to the pilot and happens autonomously during all configuration changes. According to alternative embodiments, the process may be manually initiated during a reconfiguration or at anytime, should a fault be suspected. Also, in accordance with an exemplary embodiment, a dedicated test or ‘spare’ channel may not be required; the verification process may be staggered to allow an operating channel to be used as a test channel during a configuration change.
In accordance with an exemplary embodiment, the controlled RF leakage in Antenna Group Translator 140 allows use of operational channels as test generators/receivers. A uniquely identifiable characteristic may be applied on test signals to protect onboard systems from self-interference—a test signal is well known and will not be displayed to the pilot; to verify operation/de-operation of test signal generators; and to prevent interference with off-airport systems by utilizing unique modulation or data patterns. In accordance with an exemplary embodiment, availability of operational channels is verified automatically as part of the configuration process. Verification may be customized per function (for example, always verify ILS, but never Automatic Direction Finder (ADF)) or by phase-of-flight (for example, verify VOR operation only in approach environment). In accordance with an exemplary embodiment, the autonomous nature of the availability verification is advantageous so that a flight crew member is not required to take any steps to carry out the verification. If the availability is not verified the function will not be offered for use. Further, it may be desirable to cause an alert or alarm in specified situations in which verification is not possible and yet the function is a flight critical function. Additional hardware is not required. As earlier discussed, it may be desirable to use operational hardware as a test generator or receiver during a phased transition. This ability provides cost savings for hardware in that a separate test channel is not required.
Providing the capability to automatically carry out availability and integrity verification for functions of a reconfigurable SDR, allows SDR's to be used effectively in aviation CNS systems, as well as other radio applications. In-flight (automatic, autonomous) verification of availability and integrity using test signals as described herein may make certification, of the SDR, by a certifying body, possible. The verification of availability and integrity checking functions may be further used for ground-based detailed fault isolation and diagnostic testing. In providing ground-based analysis and testing, it may be possible and desirable to utilize a more comprehensive test signal (complete frequency coverage, modulation, simulated Doppler, etc.), which may not otherwise be possible while in-flight. Also, since the system both generates the test waveform and measures the response, diagnostic testing down to board or component level may be possible.
While the detailed drawings, specific examples, and particular formulations given described exemplary embodiments, they serve the purpose of illustration only. It should be understood that various alternatives to the embodiments of the invention described maybe employed in practicing the invention. It is intended that the following claims define the scope of the invention and that structures within the scope of these claims and their equivalents be covered thereby. The hardware and software configurations shown and described may differ depending on the chosen performance characteristics and physical characteristics of the computing and analysis devices. For example, the type of computing device, communications bus, or processor used may differ. The systems shown and described are not limited to the precise details and conditions disclosed. Method steps provided may not be limited to the order in which they are listed but may be ordered any way as to carry out the inventive process without departing from the scope of the invention. Furthermore, other substitutions, modifications, changes and omissions may be made in the design, operating conditions and arrangements of the exemplary embodiments without departing from the scope of the invention as expressed in the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
5020135 | Kasparian et al. | May 1991 | A |
5197084 | Fuhrman | Mar 1993 | A |
5302947 | Fuller et al. | Apr 1994 | A |
5404392 | Miller et al. | Apr 1995 | A |
5448765 | Kovanen et al. | Sep 1995 | A |
5488356 | Martinovich et al. | Jan 1996 | A |
5668591 | Shintani | Sep 1997 | A |
5801690 | Ayoub et al. | Sep 1998 | A |
6034623 | Wandel | Mar 2000 | A |
6052600 | Fette et al. | Apr 2000 | A |
6181734 | Palermo | Jan 2001 | B1 |
6242919 | Zuk et al. | Jun 2001 | B1 |
6272457 | Ford et al. | Aug 2001 | B1 |
6279019 | Oh et al. | Aug 2001 | B1 |
6279153 | Bi et al. | Aug 2001 | B1 |
6331834 | Smith | Dec 2001 | B1 |
6342869 | Edvardsson et al. | Jan 2002 | B1 |
6353846 | Fleeson | Mar 2002 | B1 |
6452325 | Dupont | Sep 2002 | B1 |
6463089 | Chauncey et al. | Oct 2002 | B1 |
6516204 | Funk et al. | Feb 2003 | B1 |
6529736 | Kopetzky | Mar 2003 | B1 |
6549067 | Kenington | Apr 2003 | B1 |
6556099 | Kahn et al. | Apr 2003 | B2 |
6591084 | Chuprun et al. | Jul 2003 | B1 |
6609039 | Schoen | Aug 2003 | B1 |
6614307 | Zhao et al. | Sep 2003 | B1 |
6667708 | Schooler et al. | Dec 2003 | B2 |
6671509 | Tanaka et al. | Dec 2003 | B1 |
6681989 | Bodin | Jan 2004 | B2 |
6687901 | Imamatsu | Feb 2004 | B1 |
6708879 | Hunt | Mar 2004 | B2 |
6768435 | Xu | Jul 2004 | B2 |
6785255 | Sastri et al. | Aug 2004 | B2 |
6792273 | Tellinger et al. | Sep 2004 | B1 |
6795444 | Vo et al. | Sep 2004 | B1 |
6801788 | Csapo et al. | Oct 2004 | B1 |
6804520 | Johansson et al. | Oct 2004 | B1 |
6807165 | Belcea | Oct 2004 | B2 |
6823181 | Kohno et al. | Nov 2004 | B1 |
6825766 | Hewitt et al. | Nov 2004 | B2 |
6873839 | Stanforth | Mar 2005 | B2 |
6914950 | Luneau | Jul 2005 | B1 |
7620127 | Koenck et al. | Nov 2009 | B1 |
20010037259 | Sharma et al. | Nov 2001 | A1 |
20020009161 | Ratni et al. | Jan 2002 | A1 |
20020028655 | Rosener et al. | Mar 2002 | A1 |
20020041639 | Krupezevic et al. | Apr 2002 | A1 |
20020072326 | Qureshey | Jun 2002 | A1 |
20020082044 | Davenport | Jun 2002 | A1 |
20020098864 | Mukai et al. | Jul 2002 | A1 |
20020131480 | Sousa et al. | Sep 2002 | A1 |
20020137514 | Mitsugi et al. | Sep 2002 | A1 |
20020144134 | Watanabe et al. | Oct 2002 | A1 |
20020151298 | Muhonen | Oct 2002 | A1 |
20020160765 | Okajima | Oct 2002 | A1 |
20030023761 | Jeansonne et al. | Jan 2003 | A1 |
20030026200 | Fu et al. | Feb 2003 | A1 |
20030028787 | Fayed et al. | Feb 2003 | A1 |
20030039214 | Huffman | Feb 2003 | A1 |
20030040282 | Park | Feb 2003 | A1 |
20030048762 | Wu et al. | Mar 2003 | A1 |
20030050055 | Ting et al. | Mar 2003 | A1 |
20030050073 | Wasko | Mar 2003 | A1 |
20030067902 | Skeba | Apr 2003 | A1 |
20030079048 | Kim | Apr 2003 | A1 |
20030081580 | Vaidyanathan et al. | May 2003 | A1 |
20030083055 | Riordan et al. | May 2003 | A1 |
20030143988 | Jamadagni | Jul 2003 | A1 |
20030158954 | Williams | Aug 2003 | A1 |
20030163551 | Riordan | Aug 2003 | A1 |
20030174731 | Tafazolli et al. | Sep 2003 | A1 |
20030216927 | Sridhar et al. | Nov 2003 | A1 |
20040005910 | Tom | Jan 2004 | A1 |
20040022332 | Gupta et al. | Feb 2004 | A1 |
20040029545 | Anderson et al. | Feb 2004 | A1 |
20040048608 | Matsuo et al. | Mar 2004 | A1 |
20040052372 | Jakoubek | Mar 2004 | A1 |
20040063425 | Wakutsu et al. | Apr 2004 | A1 |
20040105533 | Iseli | Jun 2004 | A1 |
20040127202 | Shih et al. | Jul 2004 | A1 |
20040128133 | Sacks et al. | Jul 2004 | A1 |
20040128134 | Sacks et al. | Jul 2004 | A1 |
20040128200 | Sacks et al. | Jul 2004 | A1 |
20040132500 | Rogalski et al. | Jul 2004 | A1 |
20040136452 | Feldman et al. | Jul 2004 | A1 |
20040138781 | Sacks et al. | Jul 2004 | A1 |
20040143652 | Grannan et al. | Jul 2004 | A1 |
20040153957 | Feldman et al. | Aug 2004 | A1 |
20040161062 | Richey et al. | Aug 2004 | A1 |
20040185805 | Kim et al. | Sep 2004 | A1 |
20040203709 | Luneau | Oct 2004 | A1 |
20040203733 | Collum et al. | Oct 2004 | A1 |
20040203837 | Lawrence | Oct 2004 | A1 |
20040215753 | Chan et al. | Oct 2004 | A1 |
20040224647 | Ma et al. | Nov 2004 | A1 |
20040242236 | Inagaki | Dec 2004 | A1 |
20040242261 | Fette | Dec 2004 | A1 |
20050007988 | Ferris et al. | Jan 2005 | A1 |
20050008098 | Iancu et al. | Jan 2005 | A1 |
20050024927 | Dolwin | Feb 2005 | A1 |
20050025170 | Po et al. | Feb 2005 | A1 |
20050027789 | Luo et al. | Feb 2005 | A1 |
20050032480 | Lee et al. | Feb 2005 | A1 |
20050041746 | Rosen et al. | Feb 2005 | A1 |
20050057578 | Chen et al. | Mar 2005 | A1 |
20050059427 | Wallace | Mar 2005 | A1 |
20050079890 | Yu | Apr 2005 | A1 |
20050108382 | Murotake et al. | May 2005 | A1 |
20050124330 | Hong et al. | Jun 2005 | A1 |
20050143005 | Moore, III | Jun 2005 | A1 |
20050157677 | Dowling | Jul 2005 | A1 |
20050160124 | Bisiaux | Jul 2005 | A1 |
20070032250 | Feher | Feb 2007 | A1 |
Number | Date | Country |
---|---|---|
0510322 | Oct 1992 | EP |
0675661 | Oct 1995 | EP |
0684743 | Nov 1995 | EP |
0785694 | Jan 1997 | EP |
0943928 | Sep 1999 | EP |
1225775 | Jan 2001 | EP |
1283994 | May 2001 | EP |
1335289 | Feb 2002 | EP |
1401224 | Sep 2002 | EP |
1263249 | Dec 2002 | EP |
1437667 | Dec 2002 | EP |
1352788 | Mar 2003 | EP |
1302088 | Apr 2003 | EP |
1528723 | Oct 2003 | EP |
1557743 | Jan 2005 | EP |
6252916 | Sep 1994 | JP |
8079379 | Mar 1996 | JP |
9224271 | Aug 1997 | JP |
10075206 | Mar 1998 | JP |
11055178 | Feb 1999 | JP |
11088508 | Mar 1999 | JP |
11220422 | Aug 1999 | JP |
11275171 | Oct 1999 | JP |
11341539 | Dec 1999 | JP |
11346186 | Dec 1999 | JP |
2000032154 | Jan 2000 | JP |
2000236268 | Aug 2000 | JP |
2000308135 | Nov 2000 | JP |
2000324043 | Nov 2000 | JP |
2001016355 | Jan 2001 | JP |
2001044882 | Feb 2001 | JP |
2001045566 | Feb 2001 | JP |
2001045567 | Feb 2001 | JP |
2001061186 | Mar 2001 | JP |
2001075717 | Mar 2001 | JP |
2001094445 | Apr 2001 | JP |
2001101005 | Apr 2001 | JP |
2001189700 | Jul 2001 | JP |
2001256052 | Sep 2001 | JP |
2001285175 | Oct 2001 | JP |
2001285179 | Oct 2001 | JP |
2001308730 | Nov 2001 | JP |
2001356979 | Dec 2001 | JP |
2002064399 | Feb 2002 | JP |
2002064451 | Feb 2002 | JP |
2002076979 | Mar 2002 | JP |
2002132400 | May 2002 | JP |
2002135276 | May 2002 | JP |
2002141823 | May 2002 | JP |
2002204273 | Jul 2002 | JP |
2002261723 | Sep 2002 | JP |
2002269473 | Sep 2002 | JP |
2002300071 | Oct 2002 | JP |
2002300664 | Oct 2002 | JP |
2002368543 | Dec 2002 | JP |
2003044301 | Feb 2003 | JP |
2003078475 | Mar 2003 | JP |
2003101474 | Apr 2003 | JP |
2003116040 | Apr 2003 | JP |
2003174404 | Jun 2003 | JP |
2003198450 | Jul 2003 | JP |
2003218731 | Jul 2003 | JP |
2003219464 | Jul 2003 | JP |
2003304235 | Oct 2003 | JP |
2003318802 | Nov 2003 | JP |
2003333663 | Nov 2003 | JP |
2003338799 | Nov 2003 | JP |
2004023753 | Jan 2004 | JP |
2004120650 | Apr 2004 | JP |
2004135221 | Apr 2004 | JP |
2004153659 | May 2004 | JP |
2004153661 | May 2004 | JP |
2004153662 | May 2004 | JP |
2004153663 | May 2004 | JP |
2004201024 | Jul 2004 | JP |
2004213339 | Jul 2004 | JP |
2004240869 | Aug 2004 | JP |
2004253993 | Sep 2004 | JP |
2004260513 | Sep 2004 | JP |
2004272789 | Sep 2004 | JP |
2004274300 | Sep 2004 | JP |
2004297357 | Oct 2004 | JP |
2004326689 | Nov 2004 | JP |
2004334735 | Nov 2004 | JP |
2004334736 | Nov 2004 | JP |
2004343500 | Dec 2004 | JP |
2005039557 | Feb 2005 | JP |
WO 9317530 | Feb 1993 | WO |
WO 9708838 | Mar 1997 | WO |
WO 9715161 | Apr 1997 | WO |
WO 0041407 | Jan 2000 | WO |
WO 0045521 | Jan 2000 | WO |
WO 0072276 | Apr 2000 | WO |
WO 0074412 | May 2000 | WO |
WO 0110050 | Feb 2001 | WO |
WO 0117123 | Mar 2001 | WO |
WO 0172058 | Mar 2001 | WO |
WO 0201740 | Jan 2002 | WO |
WO 0215419 | Feb 2002 | WO |
WO 0230141 | Apr 2002 | WO |
WO 02059752 | Aug 2002 | WO |
WO 02091694 | Nov 2002 | WO |
WO 03017706 | Feb 2003 | WO |
WO 2004008719 | Jan 2004 | WO |
WO 2004064271 | Jul 2004 | WO |
WO 2004074975 | Sep 2004 | WO |
WO 2005004513 | Jan 2005 | WO |
WO 2005013540 | Feb 2005 | WO |
WO 2005011185 | Feb 2005 | WO |
WO 2005029808 | Mar 2005 | WO |
WO 2005032099 | Apr 2005 | WO |
WO 2005043930 | May 2005 | WO |
WO 2005065098 | Jul 2005 | WO |