The present invention generally relates to data communications over a power distribution system and more particularly, to a power line communications system for wirelessly communicating utility meter data and other data.
Well-established power distribution systems exist throughout most of the United States, and other countries, which provide power to customers via power lines. With some modification, the infrastructure of the existing power distribution systems can be used to provide data communication in addition to power delivery, thereby forming a power line communication system (PLCS). In other words, existing power lines that already have been run to many homes and offices, can be used to carry data signals to and from the homes and offices. These data signals are communicated on and off the power lines at various points in the power line communication system, such as, for example, near homes, offices; Internet service providers, and the like.
There are many challenges to overcome in order to use power lines for data communication. Power lines are not designed to provide high speed data communications and can be very susceptible to interference. Additionally, federal regulations limit the amount of radiated energy of a power line communication system, which therefore limits the strength of the data signal that can be injected onto power lines (especially overhead power lines). Consequently, due to the attenuation of power lines, communications signals typically will travel only a relatively short distance on power lines. In addition, the distance may vary from location to location.
In the past, utilities typically have sent personnel to manually read and record the meter data, which can be expensive. Automated meter reading has been investigated as a means for reducing the cost of reading meters. However, until now, there has been no economically feasible means of communicating the data to the utility. This fact, along with the cost of replacing old meters in a large geographical area, have hindered wide scale adoption of automated meter reading.
Thus, there is a need for a power line communications system and method that facilitates automated power meter reading and reliable communications of data signals that can be dynamically configured and reconfigured by a network management system. These and other advantages may be provided by various embodiments of the present invention.
The present invention provides an automated meter reading power line communications system and method of use. In one embodiment, the method may include measuring the utility usage of a first customer premises to provide first utility usage data, storing the first utility usage data in memory of a first device, wirelessly transmitting the first utility usage data from the first device, receiving the wirelessly transmitted first utility usage data at a second device coupled to a medium voltage power line, and transmitting the first utility usage data over the medium voltage power line.
The invention is further described in the detailed description that follows, by reference to the noted drawings by way of non-limiting illustrative embodiments of the invention, in which like reference numerals represent similar parts throughout the drawings. As should be understood, however, the invention is not limited to the precise arrangements and instrumentalities shown. In the drawings:
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular networks, communication systems, computers, terminals, devices, components, techniques, PLCS, data and network protocols, software products and systems, operating systems, development interfaces, hardware, etc. in order to provide a thorough understanding of the present invention.
However, it will be apparent to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. Detailed descriptions of well-known networks, communication systems, computers, PLCS, terminals, devices, components, techniques, data and network protocols, software products and systems, operating systems, development interfaces, and hardware are omitted so as not to obscure the description of the present invention.
As shown in
In addition to HV transmission lines, power distribution systems include MV power lines and LV power lines. As discussed, MV typically ranges from about 1000 V to about 100 kV and LV typically ranges from about 100 V to about 800 V. Transformers are used to convert between the respective voltage portions, e.g., between the HV section and the MV section and between the MV section and the LV section. Transformers have a primary side for connection to a first voltage (e.g., the MV section) and a secondary side for outputting another (usually lower) voltage (e.g., the LV section). Such transformers are often referred to as distribution transformers or a step down transformers, because they “step down” the voltage to some lower voltage. Transformers, therefore, provide voltage conversion for the power distribution system. Thus, power is carried from substation transformer to a distribution transformer over one or more MV power lines. Power is carried from the distribution transformer to the customer premises via one or more LV power lines.
In addition, a distribution transformer may function to distribute one, two, three, or more phase voltages to the customer premises, depending upon the demands of the user. In the United States, for example, these local distribution transformers typically feed anywhere from one to ten homes, depending upon the concentration of the customer premises in a particular area. Distribution transformers may be pole-top transformers located on a utility pole, pad-mounted transformers located on the ground, or transformers located under ground level.
One example of a portion of a conventional PLCS is shown in
In this example embodiment, the BD 100 provides communication services for the user devices, which may include security management, routing of Internet Protocol (IP) packets, filtering data, access control, service level monitoring, signal processing and modulation/demodulation of signals transmitted over the power lines.
This example portion of a PLCS also includes a backhaul point 10. The backhaul point 10 is an interface and gateway between a portion of a PLCS (e.g., an MV run) and a traditional non-power line telecommunications network. One or more backhaul points (BP) 10 may be communicatively coupled to an aggregation point (AP) 20 that in many embodiments may be at (e.g., co-located with), or connected to, the point of presence to the Internet. The BP 10 may be connected to the AP 20 using any available mechanism, including fiber optic conductors, T-carrier, Synchronous Optical Network (SONET), or wireless techniques well known to those skilled in the art. Thus, the BP 10 may include a transceiver suited for communicating through the communication medium that comprises the backhaul link.
The PLCS also may include a power line server (PLS) that is a computer system with memory for storing a database of information about the PLCS and includes a network element manager (NEM) that monitors and controls the PLCS. The PLS allows network operations personnel to provision users and network equipment, manage customer data, and monitor system status, performance and usage. The PLS may reside at a remote network operations center (NOC), and/or at a PLCS Point of Presence (POP), to oversee a group of communication devices via the Internet. The PLS may provide an Internet identity to the network devices by assigning the devices (e.g., user devices, BDs 100, (e.g., the LV modems and MV modems of BDs), BPs 10, and AP 20) IP addresses and storing the IP addresses and other device identifying information (e.g., the device's location, address, serial number, etc.) in its memory. In addition, the PLS may approve or deny user devices authorization requests, command status reports, statistics and measurements from the BDs, and BPs, and provide application software upgrades to the communication devices (e.g., BDs, BPs, and other devices). The PLS, by collecting electric power distribution information and interfacing with utilities' back-end computer systems may provide enhanced power distribution services such as automated meter reading, outage detection, restoration detection, load balancing, distribution automation, Volt/Volt-Amp Reactance (Volt/VAr) management, and other similar functions. The PLS also may be connected to one or more APs and/or core routers directly or through the Internet and therefore can communicate with any of the BDs, user devices, and BPs through the respective AP and/or core router.
The PLCS may further include indoor low voltage repeaters and outdoor low voltage repeaters. Indoor low voltage repeaters may be plugged into a wall socket inside the customer premises. Outdoor low voltage repeaters may be coupled to the external low voltage power line conductors extending from the transformer and therefore, be located between the customer premises and the BD 100. Both the indoor low voltage repeaters and outdoor low voltage repeaters repeat data on the low voltage power line to extend the communication range of the BD 100 and power line modem.
At the user end of the PLCS of this example system, data flow originates from a user device, which provides the data to a power line modem (PLM) 50, which is well-known in the art.
The user device connected to the PLM 50 may be any device capable of supplying data for transmission (or for receiving such data) including, but not limited to a computer, a telephone, a telephone answering machine, a fax, a digital cable box (e.g., for processing digital audio and video, which may then be supplied to a conventional television and for transmitting requests for video programming), a video game, a stereo, a videophone, a television (which may be a digital television), a video recording device (which may be a digital video recorder), a home network device, a utility meter, or other device. The PLM 50 transmits the data received from the user device through the LV power lines to a BD 100 and provides data received from the LV power line to the user device. The PLM 50 may also be integrated with the user device, which may be a computer. In addition, the functions of the PLM may be integrated into a smart utility meter such as a gas meter, electric meter, water meter, or other utility meter to thereby provide automated meter reading (AMR).
The BD 100 typically receives data from the user devices coupled to its LV power line subnet and then transmits the data to (and receives the data from) the backhaul point 10, which, in turn, transmits the data to (and receives the data from) the AP 20. The AP 20 then transmits the data to (and receives the data from) the appropriate destination (perhaps via a core router), which may be a network destination (such as an Internet address) in which case the packets are transmitted to, and pass through, numerous routers (herein routers are meant to include both network routers and switches) in order to arrive at the desired destination. A detailed description of an example PLCS, its components and features is provided in U.S. patent application Ser. No. 11/091,677 filed Mar. 28, 2005, entitled “Power Line Repeater System and Method”, which is hereby incorporated by reference in its entirety. A detailed description of another example PLCS, its components and features is provided in U.S. patent application Ser. No. 10/973,493 filed Oct. 26, 2004, entitled “Power Line Communications System and Method of Operating the Same,” which is hereby incorporated by reference in its entirety. The present invention may be used with networks as described in the above patent applications or others. Thus, the invention is not limited to a particular PLCS, PLCS architecture, or topology.
Referring to
Similarly, BD 100b is coupled to backhaul point 10 via the MV power line and also coupled to LV power line subnet 61b to provide communications to the user devices coupled thereto. In this example, LV power line subnet 61b includes the LV power lines coupled to distribution transformer 60b. One or more of the customer premises 119 receiving power via LV power line subnet 61b may include one or more PLMs 50 and the associated user devices connected thereto. Thus, as shown in
Thus, the prevent invention may provide an additional communication link to the customer premises (or the vicinity thereof) for communications with the utility meter(s) and/or user devices. For example, if the power line communication channel becomes inoperative, the wireless link may be used to provide communications.
The wireless modem 2022 may be communicatively coupled to the processor 2040. The processor 2040 may be in communication with memory 2045, which may include volatile and non-volatile random access memory (RAM) which may be used to store power usage data collected from the meter 300 and program code to be executed by the processor 2040. New program code, requests for data, and other commands may be received via the wireless modem 2022 from a network element such as a bypass device, of the PLCS. The new code, requests for data, and/or other commands may then be stored in flash memory for execution by the processor 2040.
The processor 2040 may also be in communication with the meter via a power meter interface 2042 in order to receive data from the meter itself and to perform other AMR processes. This example embodiment also includes a power line modem 2020 to communicate with the BD 100 or power line modems in the customer premises. Other embodiments may not need to have a power line modem 2020. The module 500 may also include a line conditioner and power supply 2055 coupled to the processor 2040, wireless modem 2022, power line modem 2020 and other components to provide power thereto.
The meter data may be transmitted by the CM 500 by wireless modem 2022 to a power line communications system network element, which may be, for example, a transformer bypass device 100. The network element may then transmit the meter data (e.g., via the MV power line) to an upstream device (e.g., a backhaul device 10), which further transmits the meter data upstream for eventual reception by utility provider. During operation, the module 500 may periodically transmit utility usage data and subsequently await an acknowledgment from the receiving device (e.g., a BD 100) that the data has been received. If no acknowledgement is received after a predetermined time period (e.g., fifteen seconds), the module may re-transmit the data. If after five attempts no acknowledgement is received the process may begin again after a second predetermined time period (e.g., fifteen minutes). After a predetermined number of processes have been completed (e.g., 5), the module may attempt to transmit an alert over the power lines (if a power line modem is included in the device).
Also, the module may receive user data, request for utility usage data, new software, configuration commands, or other data wirelessly or, if, the module 500 includes a power line modem 2020, via the LV power line modems. In one embodiment, data transmitted by the BD 100 and the CM 500 is differentially transmitted over the two LV power line energized conductors. In another embodiment, the data signals are inductively coupled onto one or both energized conductors. User data received (from the BD 100 or originating from user device in a customer premises) may be re-transmitted wirelessly or over the LV power lines (if a power line modem is included in the module 500). Thus, data may be received wirelessly from a BD 100, a user device, or another utility meter and be re-transmitted wirelessly or over the power lines and data may be received via the LV power lines from a BD 100, a user device, or another utility meter and be re-transmitted wirelessly or over the power lines.
Referring to
This embodiment of the BD 100 provides bi-directional communication of a first communications path from the LV power line to the MV power line and a second path from the MV power line to the LV power line. Thus, BD 100 can receive and transmit data to one or more user devices in one or more customer premises via the LVI 400, which may be connected to a plurality customer premises via a plurality of LV power lines. The BD 100 may also receive and transmit data with other elements, such as one or more BPs 10 and other BDs 100, via the MVI 300. In addition, the BD 100 may wirelessly receive and transmit data through antenna 33 via wireless modem 2044 with meters on the same LV subnet or with meters on a different nearby LV subnet.
LV Modem
The LV modem 450 receives and transmits data over the LV power line subnet and may include additional functional submodules such as an Analog-to-Digital Converter (ADC), Digital-to-Analog Converter (DAC), a memory, source encoder/decoder, error encoder/decoder, channel encoder/decoder, MAC (Media Access Control) controller, encryption module, and decryption module. These functional submodules may be omitted in some embodiments, may be integrated into a modem integrated circuit (chip or chip set), or may be peripheral to a modem chip. In the present example embodiment, the LV modem 450 is formed, at least in part, by part number INT51X1, which is an integrated power line transceiver circuit incorporating most of the above-identified submodules, and which is manufactured by Intellon, Inc. of Ocala, Fla.
The LV modem 450 may provide decryption, source decoding, error decoding, channel decoding, and media access control (MAC) all of which are known in the art and, therefore, not explained in detail here. With respect to MAC, however, the LV modem 450 may examine information in the packet to determine whether the packet should be ignored or passed to the router 310. For example, the modem 450 may compare the destination MAC address of the incoming packet with the MAC address of the LV modem 450 (which is stored in the memory of the LV modem 450). If there is a match, the LV modem 450 may remove the MAC header of the packet and pass the packet to the router 310. If there is not a match, the packet may be ignored.
Router
The router 310 may perform prioritization, filtering, packet routing, access control, and encryption. The router 310 of this example embodiment of the present invention uses a table (e.g., a routing table) and programmed routing rules stored in memory to determine the next destination of a data packet. The table is a collection of information and may include information relating to which interface (e.g., LVI 400 or MVI 200) leads to particular groups of addresses (such as the addresses of the user devices (including control devices) connected to the customer LV power lines and BDs 100), priorities for connections to be used, and rules for handling both routine and special cases of traffic (such as voice packets and/or control packets).
The router 310 will detect routing information, such as the destination address (e.g., the destination IP address) and/or other packet information (such as information identifying the packet as voice data), and match that routing information with rules (e.g., address rules) in the table. The rules may indicate that packets in a particular group of addresses should be transmitted in a specific direction such as through the LV power line (e.g., if the packet was received from the MV power line or receiver and the destination address corresponds to a user device (e.g., control device) connected to the LV power line), repeated on the MV line (e.g., if the BD 100 is acting as a repeater), or be ignored (e.g., if the address does not correspond to a user device connected to the LV power line or to the BD 100 itself).
As an example, the table may include information such as the IP addresses (and potentially the MAC addresses) of the user devices on the BD's 100 LV subnet, the utility meters with which it can communicate, the MAC addresses of the PLMs 50 on the BD's 100 LV subnet, the addresses of the control devices on the LV subnet, the MV subnet mask (which may include the MAC address and/or IP address of the BD's BP 10), the IP (and/or MAC) addresses of BDs 100 (e.g., for which the device may be repeating), and the IP address of the LV modem 450 and MV modem 280. Based on the-destination address of the packet (e.g., an IP address), the router may pass the packet to the MV modem 280 for transmission on the MV power line. Alternately, if the destination address of the packet matches the address of the BD 100, the BD 100 may process the packet as a command such as request for a pay-per-view programming.
The router 310 may also prioritize transmission of packets. For example, data packets determined to be voice packets may be given higher priority for transmission through the BD 100 than data packets so as to reduce delays and improve the voice connection experienced by the user. Routing and/or prioritization may be based on IP addresses, MAC addresses, subscription level, type of data (e.g., power usage data or other enhanced power distribution system data may be given lower priority than voice or computer data), or a combination thereof (e.g., the MAC address of the PLM or IP address of the user device). Additionally, data to or from the one or more utility meters may be given a lower priority than data from user devices (which may include web page data, IP television data, voice data, etc.)
MV Modem
The MV modem 280, which is coupled to the router 310, receives and transmits data over the MV power line. Similar to the LV modem 450, the MV modem 280 receives data from the router 310 and includes a modulator and demodulator. In addition, the MV modem 280 also may include one or more additional functional submodules such as an ADC, DAC, memory, source encoder/decoder, error encoder/decoder, channel encoder/decoder, MAC controller, encryption module, frequency conditioning module (to upband and/or downband signals) and decryption module. These functional submodules may be omitted in some embodiments, may be integrated into a modem integrated circuit (chip or chip set), or may be peripheral to a modem chip. In the present example embodiment, the MV modem 280 is formed, at least in part, by part number INT51X1, which is an integrated power line transceiver circuit incorporating most of the identified submodules and which is manufactured by Intellon, Inc. of Ocala, Fla.
The incoming data from the router 310 (or controller) is supplied to the MV modem 280, which provides MAC processing, for example, by adding a MAC header that includes the MAC address of the MV modem 280 as the source address and the MAC address of the BP 10 (and in particular, the MAC address of the MV modem of the BP) or BD 100 as the destination MAC address. In addition, the MV modem 280 also provides channel encoding, source encoding, error encoding, and encryption. The data is then modulated and provided to the DAC to convert the digital data to an analog signal.
The term “router” is sometimes used to refer to a device that routes data at the IP layer (e.g., using IP addresses). The term “switch” or “bridge” are sometimes used to refer to a device that routes at the MAC layer (e.g., using MAC addresses). Herein, however, the terms “router”, “routing”, “routing functions” and the like are meant to include both routing at the IP layer and MAC layer. Consequently, the router 310 of the present invention may use MAC addresses instead of, or in addition to, IP addresses to perform routing functions.
Signal Conditioners
The signal conditioners 420 and 260 may provide filtering (anti-alias, noise, and/or band pass filtering) and amplification. In addition, the signal conditioners may provide frequency translation.
MV Power Coupler Line
The coupling device 210 may be inductive, capacitive, conductive, a combination thereof, or any suitable device for communicating data signals to and/or from the MV power line.
Controller
As discussed, the controller 300 includes the hardware and software for managing communications and control of the BD 100. In this embodiment, the controller 300 includes an IDT 32334 RISC microprocessor for running the embedded application software and also includes flash memory for storing the boot code, device data and configuration information (serial number, MAC addresses, subnet mask, and other information), the application software, routing table, and the statistical and measured data. This memory includes the program code stored therein for operating the processor to perform the routing functions described herein.
This embodiment of the controller also includes random access memory (RAM) for running the application software and temporary storage of data and data packets. This embodiment of the controller 300 also includes an Analog-to-Digital Converter (ADC) for taking various measurements, which may include measuring the temperature inside the BD 100 (through a temperature sensor such as a varistor or thermistor), for taking power quality measurements, detecting power outages, measuring the outputs of feedback devices, and others. The embodiment also includes a “watchdog” timer for resetting the device should a hardware glitch or software problem prevent proper operation to continue.
This embodiment of the controller 300 also includes an Ethernet adapter, an optional on-board MAC and physical (PHY) layer Ethernet chipset that can be used for converting peripheral component interconnect (PCI) to Ethernet signals for communicating with the backhaul side of the BD 100. The RJ45 connector provides a port for the wireless modem 2044 (which may be a 802.11 compliant transceiver) for communicating wirelessly to the meter, BP 10 or BD 100, which, of course, would include a similar transceiver.
In addition to storing a real-time operating system, the memory of controller 300 of the BD 100 also includes various program code sections such as a receiver control software, software upgrade handler, software upgrade processing software, the PLS command processing software (which receives commands from the PLS, and processes the commands, and may return a status back to the PLS), the ADC control software, the power quality monitoring software, the error detection and alarm processing software, the data filtering software, the traffic monitoring software, the network element provisioning software, and a dynamic host configuration protocol (DHCP) Server for auto-provisioning user devices (e.g., user computers) and associated PLMs.
During operation, the BD 100 may periodically transmit a request for, or anticipate reception of, utility usage data and, upon reception transmit an acknowledgment to the CM 500. The request may be send over the LV power lines or wirelessly depending on the implementation. If no data is received from the communication module after a predetermined time period (e.g., one hour or one day) or in response to a transmitted request, the BD may re-transmit the request. If no data is received again, the BD may transmit an alert over the MV power line to the PLS, which may transmit a notification to the utility to dispatch a repair crew to replace the meter and/or communication module. The BD may provide communications to a plurality of utility meters (e.g., power, water, and/or gas) and user devices. Thus, the CM associated with each utility meter may have a different address and be separately addressable by the BD 100. Once the utility usage data is received, the BD may store the data and subsequently transmit the data over the MV power line to the power line server and/or a destination designated by the utility (which may require that the BD or BP add a destination address to the data packet carrying the utility usage data).
In alternate embodiment, the BD 100 does not include a LVI, but may connect to the LV power lines to receive power therefrom, but does not communicate over the LV power lines. Thus, the BD 100 may include an MVI 200 (including an MV modem) and a wireless modem 2044 for communicating with utility meters and/or user devices. For example, some bypass devices 100 may not have any subscribers on their LV subnet. Consequently, such an embodiment of the present invention may not include a low voltage port on the device 100 because the BD 100 can communicate meter data wirelessly. Additionally, bypass devices with the wireless modem may be configured to communicate with numerous meters including both meters connected to the BD's LV subnet and to meters that are connected to other LV subnets (and with which there is no conductive path for data communications). Likewise, some utility meters (e.g., gas or water) may include a battery powered communication module and not be connected to the power lines. For such meters there often is no conductive path for data over power lines. Finally, the proliferation of wireless local area networks and cordless telephones (which either may often use the 2.4 GHz or 5.8 GHz) in a given area may make one or more of the 900 MHz frequency sub-bands attractive for implementing the present invention. Additionally, the 900 MHz may provide better penetration to or into customer premises and also allow for economic production of the invention.
It is to be understood that the foregoing illustrative embodiments have been provided merely for the purpose of explanation and are in no way to be construed as limiting of the invention. Words used herein are words of description and illustration, rather than words of limitation. In addition, the advantages and objectives described herein may not be realized by each and every embodiment practicing the present invention. Further, although the invention has been described herein with reference to particular structure, materials and/or embodiments, the invention is not intended to be limited to the particulars disclosed herein. Rather, the invention extends to all functionally equivalent structures, methods and uses, such as are within the scope of the appended claims. Those skilled in the art, having the benefit of the teachings of this specification, may affect numerous modifications thereto and changes may be made without departing from the scope and spirit of the invention.
This application is a continuation-in-part of and claims priority to U.S. patent application Ser. No. 10/075,332, filed Feb. 14, 2002, which claims priority to U.S. Provisional Patent Application Ser. Nos. 60/268,519 and 60/268,578, (both filed Feb. 14, 2001); and this application is a continuation-in-part of and claims priority to U.S. patent application Ser. No. 11/134,377 filed May 23, 2005, which is a continuation of U.S. patent application Ser. No. 09/835,532, now U.S. Pat. No. 6,958,680, filed Apr. 16, 2001, which claims priority to U.S. Provisional Patent Application Ser. No. 60/197,615 filed Apr. 14, 2000, all of which are hereby incorporated herein by reference in their entirety for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
3445814 | Spalti | May 1969 | A |
3641536 | Prosprich | Feb 1972 | A |
3656112 | Paull | Apr 1972 | A |
3701057 | Hoer | Oct 1972 | A |
3702460 | Blose | Nov 1972 | A |
3810096 | Kabat et al. | May 1974 | A |
3900842 | Calabro et al. | Aug 1975 | A |
3942168 | Whyte | Mar 1976 | A |
3942170 | Whyte | Mar 1976 | A |
3944723 | Fong | Mar 1976 | A |
3967264 | Whyte et al. | Jun 1976 | A |
3973087 | Fong | Aug 1976 | A |
3973240 | Fong | Aug 1976 | A |
3980954 | Whyte | Sep 1976 | A |
4012733 | Whyte | Mar 1977 | A |
4057793 | Johnson et al. | Nov 1977 | A |
4060735 | Pascucci et al. | Nov 1977 | A |
4119948 | Ward | Oct 1978 | A |
4199761 | Whyte et al. | Apr 1980 | A |
4268818 | Davis et al. | May 1981 | A |
4433284 | Perkins | Feb 1984 | A |
4442492 | Karlsson et al. | Apr 1984 | A |
4473816 | Perkins | Sep 1984 | A |
4473817 | Perkins | Sep 1984 | A |
4569045 | Schieble et al. | Feb 1986 | A |
4642607 | Strom et al. | Feb 1987 | A |
4644321 | Kennon | Feb 1987 | A |
4652855 | Weikel | Mar 1987 | A |
4675648 | Roth et al. | Jun 1987 | A |
4686382 | Shuey | Aug 1987 | A |
4701945 | Pedigo | Oct 1987 | A |
4724381 | Crimmins | Feb 1988 | A |
4749992 | Fitzmeyer et al. | Jun 1988 | A |
4829298 | Fernandes | May 1989 | A |
5006846 | Granville et al. | Apr 1991 | A |
5056107 | Johnson et al. | Oct 1991 | A |
5272462 | Teyssandier et al. | Dec 1993 | A |
5341265 | Westrom et al. | Aug 1994 | A |
5369356 | Kinney et al. | Nov 1994 | A |
5426360 | Maraio et al. | Jun 1995 | A |
5448229 | Lee, Jr. | Sep 1995 | A |
5481249 | Sato | Jan 1996 | A |
5498956 | Kinney et al. | Mar 1996 | A |
5592482 | Abraham | Jan 1997 | A |
5748104 | Argyroudis et al. | May 1998 | A |
5777545 | Patel | Jul 1998 | A |
5801643 | Williams et al. | Sep 1998 | A |
5805458 | McNamara et al. | Sep 1998 | A |
5835005 | Furukawa et al. | Nov 1998 | A |
5856776 | Armstrong et al. | Jan 1999 | A |
5880677 | Lestician | Mar 1999 | A |
5892430 | Wiesman et al. | Apr 1999 | A |
5892758 | Argyroudis | Apr 1999 | A |
5994998 | Fisher et al. | Nov 1999 | A |
6072858 | Bellin | Jun 2000 | A |
6130896 | Lueker et al. | Oct 2000 | A |
6140911 | Fisher et al. | Oct 2000 | A |
6150955 | Tracy et al. | Nov 2000 | A |
6151330 | Liberman | Nov 2000 | A |
6157292 | Piercy et al. | Dec 2000 | A |
6175860 | Gaucher | Jan 2001 | B1 |
6239722 | Colton et al. | May 2001 | B1 |
6243413 | Beukema | Jun 2001 | B1 |
6243571 | Bullock et al. | Jun 2001 | B1 |
6255805 | Papalia et al. | Jul 2001 | B1 |
6262672 | Brooksby et al. | Jul 2001 | B1 |
6300881 | Yee et al. | Oct 2001 | B1 |
6304231 | Reed et al. | Oct 2001 | B1 |
6313623 | Kojovic et al. | Nov 2001 | B1 |
6346875 | Puckette et al. | Feb 2002 | B1 |
6373399 | Johnson et al. | Apr 2002 | B1 |
6441723 | Mansfield, Jr. et al. | Aug 2002 | B1 |
6459998 | Hoffman | Oct 2002 | B1 |
6480510 | Binder | Nov 2002 | B1 |
6504357 | Hemminger et al. | Jan 2003 | B1 |
6538577 | Ehrke et al. | Mar 2003 | B1 |
6611134 | Chung | Aug 2003 | B2 |
6624532 | Davidow | Sep 2003 | B1 |
6650249 | Meyer et al. | Nov 2003 | B2 |
6684245 | Shuey et al. | Jan 2004 | B1 |
6687574 | Pietrowicz et al. | Feb 2004 | B2 |
6710721 | Holowick | Mar 2004 | B1 |
6737984 | Welles et al. | May 2004 | B1 |
6778099 | Meyer et al. | Aug 2004 | B1 |
6778817 | Bullock et al. | Aug 2004 | B1 |
6842459 | Binder | Jan 2005 | B1 |
6885674 | Hunt et al. | Apr 2005 | B2 |
6933835 | Kline | Aug 2005 | B2 |
6950567 | Kline | Sep 2005 | B2 |
6954814 | Leach | Oct 2005 | B1 |
6958680 | Kline | Oct 2005 | B2 |
6965302 | Mollenkopf et al. | Nov 2005 | B2 |
6965303 | Mollenkopf | Nov 2005 | B2 |
6980090 | Mollenkopf | Dec 2005 | B2 |
6980091 | White et al. | Dec 2005 | B2 |
6985714 | Akiyama et al. | Jan 2006 | B2 |
6993317 | Belsak, Jr. | Jan 2006 | B2 |
6998962 | Cope et al. | Feb 2006 | B2 |
7042351 | Kline | May 2006 | B2 |
7046882 | Kline | May 2006 | B2 |
7061370 | Cern | Jun 2006 | B2 |
7075414 | Giannini et al. | Jul 2006 | B2 |
7113134 | Berkman | Sep 2006 | B1 |
7142094 | Davidow et al. | Nov 2006 | B1 |
20010010032 | Ehlers et al. | Jul 2001 | A1 |
20010038343 | Meyer et al. | Nov 2001 | A1 |
20010054953 | Kline | Dec 2001 | A1 |
20020002040 | Kline et al. | Jan 2002 | A1 |
20020053912 | Saha et al. | May 2002 | A1 |
20020064010 | Nelson et al. | May 2002 | A1 |
20020067171 | Lanan | Jun 2002 | A1 |
20020084914 | Jackson et al. | Jul 2002 | A1 |
20020097953 | Kline | Jul 2002 | A1 |
20020109585 | Sanderson | Aug 2002 | A1 |
20020110310 | Kline | Aug 2002 | A1 |
20020110311 | Kline | Aug 2002 | A1 |
20020118101 | Kline | Aug 2002 | A1 |
20020121963 | Kline | Sep 2002 | A1 |
20020130768 | Che et al. | Sep 2002 | A1 |
20020154000 | Kline | Oct 2002 | A1 |
20020162032 | Gundersen et al. | Oct 2002 | A1 |
20030039257 | Manis | Feb 2003 | A1 |
20030046377 | Daum et al. | Mar 2003 | A1 |
20030052770 | Mansfield, Jr. et al. | Mar 2003 | A1 |
20030103303 | Barnes et al. | Jun 2003 | A1 |
20030129978 | Akiyama et al. | Jul 2003 | A1 |
20030133420 | Haddad | Jul 2003 | A1 |
20030160595 | Provanzana et al. | Aug 2003 | A1 |
20030169155 | Mollenkopf et al. | Sep 2003 | A1 |
20030201873 | Cern | Oct 2003 | A1 |
20030224784 | Hunt et al. | Dec 2003 | A1 |
20040024483 | Holcombe | Feb 2004 | A1 |
20040027748 | Kojovie et al. | Feb 2004 | A1 |
20040036478 | Logvinov et al. | Feb 2004 | A1 |
20040047335 | Proctor et al. | Mar 2004 | A1 |
20040061616 | Fischer et al. | Apr 2004 | A1 |
20040064276 | Villicana | Apr 2004 | A1 |
20040083066 | Hayes et al. | Apr 2004 | A1 |
20040110483 | Mollenkopf | Jun 2004 | A1 |
20040113756 | Mollenkopf | Jun 2004 | A1 |
20040113757 | White, II et al. | Jun 2004 | A1 |
20040135676 | Berkman et al. | Jul 2004 | A1 |
20040153215 | Kearney et al. | Aug 2004 | A1 |
20040176026 | Gainey et al. | Sep 2004 | A1 |
20040189317 | Borchert et al. | Sep 2004 | A1 |
20040198453 | Cutrer et al. | Oct 2004 | A1 |
20040223470 | Smith | Nov 2004 | A1 |
20040223617 | Corcoran et al. | Nov 2004 | A1 |
20040227621 | Cope et al. | Nov 2004 | A1 |
20040227622 | Giannini et al. | Nov 2004 | A1 |
20040239522 | Gallagher | Dec 2004 | A1 |
20050040809 | Uber, III et al. | Feb 2005 | A1 |
20050046550 | Crenshaw et al. | Mar 2005 | A1 |
20050055729 | Atad et al. | Mar 2005 | A1 |
20050057227 | Rockwell | Mar 2005 | A1 |
20050063422 | Lazar et al. | Mar 2005 | A1 |
20050068915 | Atad et al. | Mar 2005 | A1 |
20050076149 | McKown et al. | Apr 2005 | A1 |
20050085259 | Conner et al. | Apr 2005 | A1 |
20050111533 | Berkman | May 2005 | A1 |
20050125104 | Wilson et al. | Jun 2005 | A1 |
20050128057 | Mansfield et al. | Jun 2005 | A1 |
20050164666 | Lang et al. | Jul 2005 | A1 |
20050168326 | White et al. | Aug 2005 | A1 |
20050194944 | Folts et al. | Sep 2005 | A1 |
20050207079 | Tiller et al. | Sep 2005 | A1 |
20050226200 | Askildsen et al. | Oct 2005 | A1 |
20050239400 | Narikawa | Oct 2005 | A1 |
20050249245 | Hazani et al. | Nov 2005 | A1 |
20050251401 | Shuey | Nov 2005 | A1 |
20050259668 | Kim | Nov 2005 | A1 |
20050285720 | Cope et al. | Dec 2005 | A1 |
20060007016 | Borkowski et al. | Jan 2006 | A1 |
20060031180 | Tamarkin et al. | Feb 2006 | A1 |
20060045105 | Dobosz et al. | Mar 2006 | A1 |
20060046766 | Hair et al. | Mar 2006 | A1 |
20060052906 | Kates | Mar 2006 | A1 |
20060060007 | Mekhanoshin et al. | Mar 2006 | A1 |
20060091877 | Robinson et al. | May 2006 | A1 |
20060106554 | Borkowski et al. | May 2006 | A1 |
20060119368 | Sela et al. | Jun 2006 | A1 |
20060125422 | Costa | Jun 2006 | A1 |
20060132299 | Robbins et al. | Jun 2006 | A1 |
20060145834 | Berkman et al. | Jul 2006 | A1 |
20060165054 | Iwamura | Jul 2006 | A1 |
20060171085 | Keating | Aug 2006 | A1 |
20060176631 | Cannon | Aug 2006 | A1 |
20060181284 | Fraedrich | Aug 2006 | A1 |
20060187074 | O'Sullivan et al. | Aug 2006 | A1 |
20060220833 | Berkman | Oct 2006 | A1 |
20060262881 | Cern | Nov 2006 | A1 |
20060286927 | Berkman | Dec 2006 | A1 |
20060291546 | Zitting | Dec 2006 | A1 |
20060291575 | Berkman et al. | Dec 2006 | A1 |
20070002771 | Berkman et al. | Jan 2007 | A1 |
20070002772 | Berkman et al. | Jan 2007 | A1 |
20070002876 | Berkman et al. | Jan 2007 | A1 |
Number | Date | Country |
---|---|---|
197 28 270 | Jan 1999 | DE |
100 61 584 | Jun 2002 | DE |
100 61 586 | Jun 2002 | DE |
0 581 351 | Feb 1994 | EP |
0 632 602 | Jan 1995 | EP |
1 253 699 | Oct 2002 | EP |
2 293 950 | Apr 1996 | GB |
1276933 | Nov 1989 | JP |
WO-9959261 | Nov 1999 | WO |
WO-0108321 | Feb 2001 | WO |
WO-03039022 | May 2003 | WO |
WO-2004008656 | Jan 2004 | WO |
Number | Date | Country | |
---|---|---|---|
20060145834 A1 | Jul 2006 | US |
Number | Date | Country | |
---|---|---|---|
60268519 | Feb 2001 | US | |
60268578 | Feb 2001 | US | |
60197615 | Apr 2000 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09835532 | Apr 2000 | US |
Child | 10075332 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11134377 | May 2005 | US |
Child | 11327341 | US | |
Parent | 10075332 | Feb 2002 | US |
Child | 11134377 | US |