This application further incorporates by this reference in their entirety for all purposes commonly assigned U.S. patent applications filed Jun. 3, 2002:
Furthermore, this application incorporates by reference for all purposes, commonly assigned U.S. patent applications filed Nov. 4, 2003:
Furthermore, this application incorporates by reference for all purposes, commonly assigned U.S. patent applications filed Feb. 6, 2004:
Furthermore, this application incorporates by reference for all purposes, commonly assigned U.S. patent application filed Oct. 19, 2005:
Furthermore, this application incorporates by reference for all purposes, commonly assigned U.S. patent application filed Jan. 13, 2006:
Furthermore, this application incorporates by reference for all purposes, commonly assigned U.S. patent application filed Mar. 17, 2006:
This disclosure relates to wireless network security systems and methods, and more particularly to systems and methods for using the distributed collaborative intelligence of wireless clients to monitor a wireless network.
Wireless networking has proliferated with the adoption of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards, the availability of license-free spectrum in the 2.4 GHz and 5 GHz bands, and the proliferation of cost-effective wireless networking equipment. The various 802.11 standards developed by the IEEE are available for download via URL: http://standards.ieee.org/getieee802/802.11.html; each of which is hereby incorporated by reference. The Federal Communications Commission (FCC) has designated the 900 MHz, 2.4 GHz, and 5 GHz bands as license-free for Industrial, Scientific, and Medical (ISM) purposes. Wireless networking manufacturers have introduced cost-effective wireless devices which operate over the ISM bands utilizing the 802.11 standards.
Wireless networks, also known as Wireless Local Area Networks (WLANs), offer a quick and effective extension of a wired network or a standard local area network (LAN). Wireless networks can include components such as wireless access points (APs) and wireless client devices. A wireless AP is a device that can connect wireless communications devices together to form a wireless network. The AP may connect to a wired networks, and can relay data between wireless devices and wired devices. Wireless client devices include laptop, desktop computers, and other computing devices equipped with a wireless capability.
It should be understood that wired networks, or LANs, can use cables to transfer information. Cables can be a controlled medium, protected by the buildings that enclose them. External traffic that enters a wired network can be policed by a firewall and established wired intrusion protection technologies. To gain access to a wired network, a hacker could bypass the physical security of the building or breach the firewall.
In contrast, wireless networks transfer information over the air. The air is an uncontrolled and shared medium—it lacks the equivalent physical security of its wired counterpart. This renders the entire network accessible from areas outside of the physical security of building. Radio signals from a single wireless AP can travel thousands of feet outside of the building. Additionally, wireless devices within the network can sniff all the traffic of all other wireless devices within the same basic service set.
Further, wireless devices are easy to deploy, are relatively inexpensive, and are mobile. Many laptops on the market today are wireless ready. Older laptops can get wireless access by adding a wireless network card and installing software. A stand-alone AP and a wireless card can cost under $100 each. Even well-intentioned employees, consultants, and contractors who install their own wireless stations and APs without regard to proper security configuration requirements can pose a threat to the enterprise. For example, many wireless ready laptops through default configuration permit ad-hoc wireless connections. These connections can readily be hacked at hotspots and other public access networks. Further, the devices connecting to WLANs are mobile and thereby introduce increased exposure to the internal network. For example, wireless devices can come and go in the enterprise, and can be located anywhere within a wireless footprint of the WLAN.
Wireless intrusion protection systems (WIPS) have been developed to monitor and secure wireless networks by identifying rogue wireless networks, detect intruders and impending threats, and enforce wireless network security policies. WIPS can include one or more servers connected through wired or wireless connections to multiple sensors (also known as sniffers) or APs. WIPS can use dedicated sensors or APs to detect attacks/events, performance degradation, and policy compliance. Sensors and APs therefore can be located throughout the wireless network infrastructure to attain coverage for the wireless network activity. Even with multiple sensors and APs, there still may be problems covering all the airwaves because sensors and APs often include single or dual-band radios which scan a single channel at a time. Further, wireless networks may operate in the 2.4 GHz and 5 GHz frequency bands, thereby incorporating 34 authorized channels.
Wireless networks can include multiple wireless clients (e.g., WLAN cards connected to a computer). There may be one to two orders of magnitude more wireless clients in a wireless network than sensors and APs. Wireless clients communicate to the wireless network when the computer has data to transmit or receive. The wireless device in a computer may be idle (e.g., not transmitting or receiving data) for a significant amount of time.
Some commercially available systems attempt to utilize processor idle time. Such systems include, for example, SETI@Home (University of California, Berkeley, Calif., available at http://setiathome.berkeley.edu/). SETI@Home is a computer program configured to operate when a processor is idle or in screen saver mode. The SETI@Home program is configured to connect to a server to receive Search for Extraterrestrial Intelligence (SETI) data, to analyze the data on the processor while the computer is idle, and to send the results back to a server when complete and there is a connection.
The present disclosure provides distributed monitoring of a wireless network using a plurality of wireless client devices in communication with the wireless network.
A method for distributed monitoring a wireless network with a plurality of wireless client devices in communication with the wireless network includes the steps of: directing one or more of a plurality of wireless client devices in communication with a wireless network to monitor the wireless network and collect data corresponding to wireless traffic on the wireless network at a predetermined range of frequencies, and to store the data for analysis; receiving collected data from the plurality of wireless client devices at one or more servers, the servers being configured to accumulate the collected data; storing the received data for analysis; and, analyzing the stored data received from the plurality of wireless client devices so as to identify traffic corresponding to anomalous wireless activity.
A processor based method for monitoring a wireless network using a client equipped with a wireless device includes the steps of: receiving wireless data from the wireless network at a wireless device responsive to an activation condition, the wireless data including wireless traffic transmitted to any receiver, wherein the wireless data is transmitted within a receiver range of the wireless device; analyzing the data to identify relevant data, events, and statistics, wherein the data, events, and statistics being relevant to a security profile associated with the wireless network; logging the relevant data, events, and statistics to a log file located on a local data store; and, sending the log file to a server responsive to the wireless device having an available connection to the server.
A computer system having an intrusion protection system agent includes: a wireless communication interface operable to receive and transmit data on a wireless network; a data store operable to store a log file associated with analysis of the wireless network; and a system processor including one or more processing elements, wherein the system processor is in communication with the system data store and the wireless communication interface and wherein the system processor is programmed or adapted to: access the wireless communication interface to collect wireless data responsive to an activation condition, the wireless data being collected without consideration for the intended recipient of the data; store the collected wireless data in the data store; perform an analysis of the collected wireless data to identify relevant data, events, and statistics, wherein the identified data, events, and statistics are relevant based upon a security profile associated with the wireless network; store a log file associated with the analysis of the collected wireless data; and, alert a centralized server via a network connection based upon the analysis of the information.
The wireless network 100 is monitored by a WIPS 101 which includes a wireless sensor 110 and an intrusion detection server 130. It should be understood that in various examples, the wireless sensor 110 can be a sniffer. In this example, the sensor 110 is located at a physical location covering the wireless coverage areas 140 of the three APs 115. The sensor 110 can include a wireless radio configured to transmit and receive wireless data. The sensor 110 can also connect to the LAN via the IP network 105. The sensor 110 can be configured to monitor the wireless network and to communicate to the intrusion detection server 130. The sensor 110 can monitor one to two wireless channels at a time, depending on the number of wireless radios included with the sensor 110. Additionally, APs 115 may also operate as sensors 110 and communicate to the intrusion detection server 130. In some wireless network deployments with a WIPS 101, multiple sensors 110 are located throughout the wireless network coverage areas.
The wireless network 100 can include multiple clients 120. The clients 120 can be configured with a wireless device for communication with the APs 115. Additionally, the wireless devices may be used for ad-hoc connections to other clients 120 (not shown). The clients 120 may include desktop computers, notebook computers, storage devices, printers, and any other system equipped with a wireless device. Client 120 wireless devices can include wireless radios configured to communicate over the wireless network 100. The wireless radios are used to transmit and receive data between the wireless network and the client 120. Clients 120 use the wireless radios while communicating over the wireless network. For example, the client 120 might not use its wireless radio when the client 120 is idle (e.g., in screen-saver mode or not transmitting/receiving data from the wireless network 100).
In
In
In
In
The processor 310 is a hardware device for executing software instructions. The processor 310 can be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the client 300, a semiconductor-based microprocessor (in the form of a microchip or chip set), or generally any device for executing software instructions. When the client 300 is in operation, the processor 310 is configured to execute software stored within the memory 320, to communicate data to and from the memory 320, and to generally control operations of the client 300 pursuant to the software instructions.
The I/O interfaces 330 may be used to receive user input from and/or for providing system output to one or more devices or components. User input may be provided via, for example, a keyboard and/or a mouse. System output may be provided via a display device and a printer (not shown). I/O interfaces 330 may include, for example, a serial port, a parallel port, a small computer system interface (SCSI), an infrared (IR) interface, a radio frequency (RF) interface, and/or a universal serial bus (USB) interface.
The WLAN card 340 may be used for communication with a Wireless Local Area Network (WLAN). Additionally, the WLAN card 340 may be configured in an ad-hoc mode whereby the WLAN card 340 is configured to connect to another client (not shown). The WLAN card 340 includes a wireless radio 360 which is configured to communicate wirelessly over a WLAN. The WLAN card 340 can be configured to communicate using one of the IEEE 802.11 protocols such as 802.11a/b/g. The WLAN card 340 may include address, control, and/or data connections to enable appropriate communications on the WLAN.
The memory 320 can include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.), and combinations thereof. Moreover, the memory 320 may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory 320 can have a distributed architecture, where various components are situated remotely from one another, but can be accessed by the processor 310.
The software in memory 320 may include one or more software programs, each of which includes an ordered listing of executable instructions for implementing logical functions. In the example of
The IPS agent 322 is a software program loaded in the memory 320 of the client 300 to enable monitoring of the wireless network. The IPS agent 322 is configured to run on the client 300 in the background, and to become active based upon predetermined or programmed conditions such as when the client 300 is idle. When active, the IPS agent 322 is configured to: 1) communicate with the WLAN card 340; 2) store received data in the memory 320; and 3) communicate with one or more intrusion detection servers. The intrusion detection server(s) may direct the IPS agent 322 to scan a particular wireless channel. Additionally, a user may preset the particular channel to monitor. The IPS agent 322 can be programmed in some examples to communicate with the WLAN card 340 when the WLAN card 340 or the client 300 is idle. The IPS agent 322 receives data from the WLAN and stores the data in the memory 320.
In some examples, the IPS agent 322 can include configurable parameters to allow a user to determine when it is active. For instance, the user may set the IPS agent 322 to operate when the client 300 is inactive for a predetermined time period. Alternatively, a system administrator may set the IPS agent 322 to operate whenever a client 120 is not communicating to the WLAN. The IPS agent 322 may be loaded on a client 300 via a CDROM, over a network connection, or preloaded when the operating system 321 is installed. The IPS agent 322 may be configured to operate on a variety of clients 300 including an Intel-compatible processor platforms, such as those using at least one Pentium III or Celeron (Intel Corp., Santa Clara, Calif.) class processor; processors such as UltraSPARC (Sun Microsystems, Palo Alto, Calif.) could be used in other embodiments.
The scenario 400 starts with the power-up and initialization of the client, as depicted in step 401. The IPS agent is loaded, as depicted in step 402. The IPS agent may be configured to load as the client initializes (e.g., on startup) or it may be loaded manually by a user. The IPS agent is loaded into memory as shown in
If the IPS agent is activated, then the IPS agent directs the client to receive wireless data from the WLAN card, as depicted in step 405. The IPS agent may be configured to scan a particular wireless channel based upon a preset configuration or based on direction from the intrusion detection server. Additionally, the IPS agent may be configured to receive all wireless data from a channel or particular frames only based a preset configuration or based on direction from the intrusion detection server. In some examples, the operational scenario 400 can determine whether a condition exists to deactivate by simultaneously performing step 403 and step 405.
The IPS agent analyzes the data, as depicted in step 406. The IPS agent uses the client processor to analyze the data, to collect statistics of the wireless network, and to process relevant frames. Upon analyzing the data, the IPS agent may store a copy of the results in memory. The IPS agent directs the client to check connectivity to the intrusion detection server, as depicted in step 407. If there is no connectivity, the IPS agent stores a copy of the results in memory, as depicted in step 408. The IPS agent periodically checks connectivity to determine whether the wireless data can be transmitted to an intrusion detection system. If connectivity exists, the IPS agent transmits the results to the intrusion detection system, as depicted in step 409. In steps 408 and 409, the operational scenario 400 returns to step 403 to determine whether to deactivate the IPS agent.
The intrusion detection server is initialized, as depicted in step 501. In the case of multiple servers, the servers can configured to communicate with the other servers or can be configured to be stand-alone entities. In step 502, the intrusion detection server establishes communication with clients operating the IPS agent software. The intrusion detection server tracks the clients and the channels that client is monitoring.
The intrusion detection server(s) can manage security policies, as depicted in step 503. Here, the intrusion detection server can determine what action to take, if any. These actions may include such actions as directing clients to monitor particular channels at particular times, directing clients to terminate a rogue device, providing notification of policy violations, attacks, events, and performance degradations, among many others.
The intrusion detection server can communicate with the clients, as depicted by step 504. The intrusion detection server can communicate the results from managing the security policies in step 503. This management of security policies can include providing updates on channel and time scan patterns. Additionally, the intrusion detection server can receive wireless data and statistics from clients in step 504. The data and statistics received from clients are stored in memory, as depicted in step 506. The memory may include local memory such as a system data store or other storage attached to the intrusion detection server. It should be understood that the memory can include network file storage.
The intrusion detection server correlates events and statistics, as depicted in step 505. The intrusion detection server can utilize several detection technologies such as anomalous behavior, stateful protocol analysis and signature matching. Additionally, the intrusion detection server can include a sophisticated correlation engine that is programmed to analyze data across different clients to minimize false positives. The intrusion detection server accesses and stores data in local or network file storage, as depicted in step 506. Based on the results of step 505, the intrusion detection server can manage security policies, as depicted in step 503.
The IPS agent 322 includes a wireless monitoring engine 602. The wireless monitoring engine 602 provides means to control communications of the WLAN card in the client including: setting the frequency (e.g., wireless channel) and time scan patterns on the WLAN card, setting ad-hoc channel monitoring on the WLAN card, and transmitting and receiving data between the WLAN card and the IPS agent 600. The wireless monitoring engine 602 is active according to the activation conditions in the configuration engine 601.
The IPS agent 600 includes an analysis engine 603. The analysis engine 603 receives and processes the data from the wireless monitoring engine 602. The analysis engine 603 operates on the client, and performs initial analysis of the received wireless data prior to forwarding it to the intrusion detection server. The analysis engine 603 compiles statistics regarding the wireless network and stores relevant frames. The relevant frames may include rogue devices or attack related frames and the analysis engine 603 is set to store these according to the parameters set in the configuration engine 601 and the communications from the intrusion detection server.
The IPS agent 600 includes a wireless termination engine 604. The wireless termination engine 604 is configured to provide proactive protection in the wireless network by using the client to thwart attacks on the network. The wireless termination engine 604 may be enabled through communications with the intrusion detection server where the intrusion detection server utilizes the client closest to an attacker (e.g., rogue wireless device or rogue AP) to thwart the attack through one of several air termination mechanisms existing in WIPS systems. The triggered active defense may include: transmitting a jamming signal, transmitting a signal to introduce errors, transmitting a signal to increase the difficulty associated with breaking the network encryption (e.g., typically by including in the signal packet appearing legitimate but containing randomized payloads), or setting up a honeypot trap on the client to lure an attacker. Systems and methods used to perform active defense methods are described in detail by U.S. patent application Ser. No. 10/161,443 entitled “METHOD AND SYSTEM FOR ACTIVELY DEFENDING A WIRELESS LAN AGAINST ATTACKS” filed Jun. 3, 2002, which has been incorporated by reference.
The IPS agent 600 includes a communications engine 605. The communications engine 604 provides means for the IPS agent 600 to communicate with the intrusion detection server. The communications engine 605 may communicate through the WLAN card or through another network connection (e.g., ethernet or dial-up). The communications engine 605 operates according to the parameters set in the configuration engine 601 including when to communicate with the intrusion detection server, retry communication attempts, and mode of communication. The communications engine 605 provides the intrusion detection server the data and statistics and receives updates from the intrusion detection server.
The IPS agent 600 includes a storage engine 606. The storage engine 606 provides local data storage for the IPS agent 600. The storage engine 606 may include the existing memory in the client such as a hard disk drive or resident RAM memory. The storage engine 606 communicates and stores data associated with the configuration engine 601, the wireless monitoring engine 602, the analysis engine 603, the wireless termination engine 604, and the communications engine 605.
Client based distributed sensing agents can provide better spatial, temporal and frequency level visibility because of sheer numbers in addition to improved location tracking and air termination capabilities. Moreover, distributed sensing agents installed on wireless clients can lower the cost of deploying a wireless intrusion protection system, for example, by reducing the number of sensors deployed, or enabling a wireless intrusion protection system to be deployed where no wireless infrastructure (e.g., no APs, sensor, or sniffer devices). Further, in some examples, the sensing agent can operate transparently to the user of a wireless client, because it can operate while the client is idle or inactive, thereby facilitating usage of an unused portion of radio and/or processing power.
As used in the description hereinabove and throughout the claims that follow, the meaning of “a,” “an,” and “the” includes plural reference unless the context clearly dictates otherwise. Also, as used in the description herein and throughout the claims that follow, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise. Finally, as used in the description herein and throughout the claims that follow, the meanings of “and” and “or” include both the conjunctive and disjunctive and may be used interchangeably unless the context clearly dictates otherwise; the phrase “exclusive or” may be used to indicate situation where only the disjunctive meaning may apply.
Throughout this application, various publications may have been referenced. The disclosures of these publications in their entireties are hereby incorporated by reference into this application in order to more fully describe the state of the art to which this invention pertains.
The embodiments described above are given as illustrative examples only. It will be readily appreciated by those skilled in the art that many deviations may be made from the specific examples disclosed in this specification without departing from the claims. Accordingly, the scope of this disclosure is to be determined by the claims below rather than being limited to the specifically described embodiments above.
Number | Name | Date | Kind |
---|---|---|---|
5077753 | Grau, Jr. et al. | Dec 1991 | A |
5231634 | Giles et al. | Jul 1993 | A |
5237614 | Weiss | Aug 1993 | A |
5339316 | Diepstraten | Aug 1994 | A |
5393965 | Bravman et al. | Feb 1995 | A |
5487069 | O'Sullivan et al. | Jan 1996 | A |
5577209 | Boyle et al. | Nov 1996 | A |
5646389 | Bravman et al. | Jul 1997 | A |
5666662 | Shibuya | Sep 1997 | A |
5737328 | Norman et al. | Apr 1998 | A |
5745479 | Burns et al. | Apr 1998 | A |
5745483 | Nakagawa et al. | Apr 1998 | A |
5768312 | Imamura | Jun 1998 | A |
5781857 | Hwang et al. | Jul 1998 | A |
5787077 | Kuehnel et al. | Jul 1998 | A |
5796942 | Esbensen | Aug 1998 | A |
5809060 | Cafarella et al. | Sep 1998 | A |
5825817 | Tanaka et al. | Oct 1998 | A |
5844900 | Hong et al. | Dec 1998 | A |
5866888 | Bravman et al. | Feb 1999 | A |
5870666 | Tanaka et al. | Feb 1999 | A |
5875179 | Tikalsky | Feb 1999 | A |
5896499 | McKelvey | Apr 1999 | A |
5903848 | Takahashi | May 1999 | A |
5913174 | Casarez et al. | Jun 1999 | A |
5919258 | Kayashima et al. | Jul 1999 | A |
5940591 | Boyle et al. | Aug 1999 | A |
5953652 | Amin et al. | Sep 1999 | A |
5987609 | Hasebe | Nov 1999 | A |
6006090 | Coleman et al. | Dec 1999 | A |
6058482 | Liu | May 2000 | A |
6067297 | Beach | May 2000 | A |
6070244 | Orchier et al. | May 2000 | A |
6104712 | Robert et al. | Aug 2000 | A |
6119230 | Carter | Sep 2000 | A |
6141778 | Kane et al. | Oct 2000 | A |
6145083 | Shaffer et al. | Nov 2000 | A |
6150961 | Alewine et al. | Nov 2000 | A |
6151357 | Jawahar et al. | Nov 2000 | A |
6158010 | Moriconi et al. | Dec 2000 | A |
6178512 | Fifield | Jan 2001 | B1 |
6185689 | Todd, Sr. et al. | Feb 2001 | B1 |
6188681 | Vesuna | Feb 2001 | B1 |
6202157 | Brownlie et al. | Mar 2001 | B1 |
6272129 | Dynarski et al. | Aug 2001 | B1 |
6272172 | Deshpande et al. | Aug 2001 | B1 |
6282546 | Gleichauf et al. | Aug 2001 | B1 |
6289214 | Backstrom | Sep 2001 | B1 |
6292508 | Hong et al. | Sep 2001 | B1 |
6301668 | Gleichauf et al. | Oct 2001 | B1 |
6301699 | Hollander et al. | Oct 2001 | B1 |
6304973 | Williams | Oct 2001 | B1 |
6317829 | Van Oorschot | Nov 2001 | B1 |
6320948 | Heilmann et al. | Nov 2001 | B1 |
6324647 | Bowman-Amuah | Nov 2001 | B1 |
6324656 | Gleichauf et al. | Nov 2001 | B1 |
6330244 | Swartz et al. | Dec 2001 | B1 |
6363477 | Fletcher et al. | Mar 2002 | B1 |
6400752 | Suzuki et al. | Jun 2002 | B1 |
6404772 | Beach et al. | Jun 2002 | B1 |
6411608 | Sharony | Jun 2002 | B2 |
6453159 | Lewis | Sep 2002 | B1 |
6453345 | Trcka et al. | Sep 2002 | B2 |
6466608 | Hong et al. | Oct 2002 | B1 |
6470384 | O'Brien et al. | Oct 2002 | B1 |
6473449 | Cafarella et al. | Oct 2002 | B1 |
6477198 | Gumm | Nov 2002 | B1 |
6484029 | Hughes et al. | Nov 2002 | B2 |
6487666 | Shanklin et al. | Nov 2002 | B1 |
6499107 | Gleichauf et al. | Dec 2002 | B1 |
6501951 | Moore | Dec 2002 | B2 |
6507864 | Klein et al. | Jan 2003 | B1 |
6522689 | Heinrich | Feb 2003 | B1 |
6539207 | del Castillo et al. | Mar 2003 | B1 |
6539428 | Davies | Mar 2003 | B2 |
6674403 | Gray et al. | Jan 2004 | B2 |
6697337 | Cafarelli et al. | Feb 2004 | B1 |
6738813 | Reichman | May 2004 | B1 |
6799047 | Bahl et al. | Sep 2004 | B1 |
6874089 | Dick et al. | Mar 2005 | B2 |
6910135 | Grainger | Jun 2005 | B1 |
6934298 | Bentley | Aug 2005 | B2 |
6988208 | Hrabik et al. | Jan 2006 | B2 |
7089303 | Sheymov et al. | Aug 2006 | B2 |
7366148 | Muaddi et al. | Apr 2008 | B2 |
7594267 | Gladstone et al. | Sep 2009 | B2 |
20010027107 | Shinozaki et al. | Oct 2001 | A1 |
20010030956 | Chillariga et al. | Oct 2001 | A1 |
20010038626 | Dynarski et al. | Nov 2001 | A1 |
20010039579 | Trcka et al. | Nov 2001 | A1 |
20020021745 | Negus | Feb 2002 | A1 |
20020029288 | Dobbins et al. | Mar 2002 | A1 |
20020032871 | Malan et al. | Mar 2002 | A1 |
20020035699 | Crosbie | Mar 2002 | A1 |
20020044533 | Bahl et al. | Apr 2002 | A1 |
20020059434 | Karaoguz et al. | May 2002 | A1 |
20020060994 | Kovacs et al. | May 2002 | A1 |
20020060995 | Cervello et al. | May 2002 | A1 |
20020061031 | Sugar et al. | May 2002 | A1 |
20020066034 | Schlossberg et al. | May 2002 | A1 |
20020072329 | Bandeira et al. | Jun 2002 | A1 |
20020083343 | Crosbie et al. | Jun 2002 | A1 |
20020087882 | Schneier et al. | Jul 2002 | A1 |
20020090089 | Branigan et al. | Jul 2002 | A1 |
20020090952 | Cantwell | Jul 2002 | A1 |
20020094777 | Cannon et al. | Jul 2002 | A1 |
20020101837 | Bender et al. | Aug 2002 | A1 |
20020112047 | Kushwaha et al. | Aug 2002 | A1 |
20020112185 | Hodges | Aug 2002 | A1 |
20020129138 | Carter | Sep 2002 | A1 |
20020138755 | Ko | Sep 2002 | A1 |
20020147920 | Mauro | Oct 2002 | A1 |
20020160769 | Gray | Oct 2002 | A1 |
20020161755 | Moriarty | Oct 2002 | A1 |
20020174364 | Nordman et al. | Nov 2002 | A1 |
20020176437 | Busch et al. | Nov 2002 | A1 |
20020178383 | Hrabik et al. | Nov 2002 | A1 |
20020181417 | Malhotra et al. | Dec 2002 | A1 |
20030009696 | Bunker et al. | Jan 2003 | A1 |
20030021254 | Fukuda | Jan 2003 | A1 |
20030026198 | Diepstraten et al. | Feb 2003 | A1 |
20030027550 | Rockwell | Feb 2003 | A1 |
20030036404 | Adachi et al. | Feb 2003 | A1 |
20030048770 | Proctor, Jr. | Mar 2003 | A1 |
20030060207 | Sugaya et al. | Mar 2003 | A1 |
20030061344 | Monroe | Mar 2003 | A1 |
20030061506 | Cooper et al. | Mar 2003 | A1 |
20030063592 | Seki et al. | Apr 2003 | A1 |
20030064720 | Valins et al. | Apr 2003 | A1 |
20030065934 | Angelo et al. | Apr 2003 | A1 |
20030070084 | Satomaa et al. | Apr 2003 | A1 |
20030084323 | Gales | May 2003 | A1 |
20030088789 | Fenton et al. | May 2003 | A1 |
20030095520 | Aalbers et al. | May 2003 | A1 |
20030096577 | Heinonen et al. | May 2003 | A1 |
20030096607 | Taylor | May 2003 | A1 |
20030100308 | Rusch | May 2003 | A1 |
20030105976 | Copeland, III | Jun 2003 | A1 |
20030108016 | Bonta | Jun 2003 | A1 |
20030110398 | Dacier et al. | Jun 2003 | A1 |
20030117966 | Chen | Jun 2003 | A1 |
20030117985 | Fujii et al. | Jun 2003 | A1 |
20030117986 | Thermond et al. | Jun 2003 | A1 |
20030119526 | Edge | Jun 2003 | A1 |
20030120821 | Thermond et al. | Jun 2003 | A1 |
20030123420 | Sherlock | Jul 2003 | A1 |
20030125035 | Khafizov et al. | Jul 2003 | A1 |
20030126258 | Conkright et al. | Jul 2003 | A1 |
20030135762 | Macaulay | Jul 2003 | A1 |
20030140246 | Kammer et al. | Jul 2003 | A1 |
20030149888 | Yadav | Aug 2003 | A1 |
20030161341 | Wu et al. | Aug 2003 | A1 |
20030174680 | Kuan et al. | Sep 2003 | A1 |
20030185244 | Wu et al. | Oct 2003 | A1 |
20030188189 | Desai et al. | Oct 2003 | A1 |
20030189908 | Kuan et al. | Oct 2003 | A1 |
20030192055 | Aoki et al. | Oct 2003 | A1 |
20030196115 | Karp | Oct 2003 | A1 |
20030200455 | Wu | Oct 2003 | A1 |
20030217289 | Ammon et al. | Nov 2003 | A1 |
20030221006 | Kuan et al. | Nov 2003 | A1 |
20030224797 | Kuan et al. | Dec 2003 | A1 |
20040003285 | Whelan et al. | Jan 2004 | A1 |
20040027988 | Billhartz | Feb 2004 | A1 |
20040068668 | Lor et al. | Apr 2004 | A1 |
20040078598 | Barber et al. | Apr 2004 | A1 |
20040102192 | Serceki | May 2004 | A1 |
20040103307 | Raphaeli et al. | May 2004 | A1 |
20040107219 | Rosenberger | Jun 2004 | A1 |
20040136318 | Bentley | Jul 2004 | A1 |
20040162995 | Muaddi et al. | Aug 2004 | A1 |
20050030929 | Swier et al. | Feb 2005 | A1 |
20050037733 | Coleman et al. | Feb 2005 | A1 |
20050202800 | Wang | Sep 2005 | A1 |
Number | Date | Country |
---|---|---|
WO 9859428 | Dec 1998 | WO |
WO 0143467 | Jun 2001 | WO |
WO 02058346 | Jul 2002 | WO |
WO 02058346 | Jul 2002 | WO |
WO 02097560 | Dec 2002 | WO |
WO 03021851 | Mar 2003 | WO |
WO 03079708 | Sep 2003 | WO |
WO 03084255 | Oct 2003 | WO |
WO 03085544 | Oct 2003 | WO |
WO 03088547 | Oct 2003 | WO |
WO 03088687 | Oct 2003 | WO |
Number | Date | Country | |
---|---|---|---|
20070217371 A1 | Sep 2007 | US |