Remote access to electronic meters using a TCP/IP protocol suite

Abstract
An electronic meter incorporates a TCP/IP protocol suite and an HTTP server to provide two-way access to the meter data. Alternatively, the TCP/IP protocol suite may be incorporated into a gateway serving multiple meters connected through a power line or wireless two-way network. The gateway may incorporate an HTTP server for accessing data from multiple meters and for transmission of data to individual meters. Other aspects of the disclosed system include the use of a common gateway interface for remote access to meter data and to set meter parameters using HTML forms in HTTP browsers; remote reading and setting of multiple meter parameters using a TCP/IP protocol suite; a TCP/IP protocol suite implemented in designated nodes in a CEBus LAN with remote access through TCP/IP to routers and brouters and to individual meters on the LAN; and an SLIP-PPP enabled gateway for remote TCP/IP access through a serial interface to a single or multiple meter parameters.
Description
FIELD OF THE INVENTION

The present invention relates generally to electronic meters and automatic meter reading, and more particularly to TCP/IP-enabled electronic meters for remote two-way access over local area networks and wide area networks.


BACKGROUND OF THE INVENTION

The present invention relates to automatic meter reading (AMR) systems for use in automatically reading electrical energy and other utility meters (e.g., water and gas meters). The invention is more particularly intended for, although not limited to, use in an electronic meter. Further background information on electronic meters can be found in U.S. Pat. No. 5,548,527, Aug. 20, 1996, titled “Programmable Electrical Energy Meter Utilizing a Non-Volatile Memory” (assigned to ABB Power T&D Company Inc.) Further background on automatic meter reading systems can be found in U.S. Pat. No. 5,553,094, Sep. 3, 1996, titled “Radio Communication Network for Remote Data Generating Stations.”


SUMMARY OF THE INVENTION

The present invention, as discussed in greater detail below, involves the use of a TCP/IP protocol suite and a hypertext transfer protocol (HTTP) server. The terms “HTTP” and “TCP/IP” are well known in the networking and telecommunications arts. For example, TCP/IP refers to a well known set of protocols for linking dissimilar devices across networks. The invention also involves the use of a “gateway”. A gateway is a node in a network that connects two otherwise incompatible networks. Gateways may perform code and protocol conversion processes. A “protocol” is a set of rules or procedures relating to the format and timing of data transmissions between two devices. Protocols typically break a file into equal-size blocks or packets. These are sent and the receiving device uses a mathematical procedure to determine whether the block or packet was received accurately.


An electronic metering system in accordance with the present invention comprises a wide area network (WAN) operating in accordance with a TCP/IP protocol; a local area network (LAN) comprising a plurality of meters each of which includes meter electronics for measuring a prescribed quantity supplied by a utility and memory for storing measured data and meter control parameters; a gateway operatively coupled to the LAN and the WAN; and an HTTP server operatively coupled to the LAN and the gateway, whereby the WAN is provided remote access to the measured data and control parameters of the meters.


Presently preferred embodiments of the invention further include a CGI (common gateway interface) application coupled to the HTTP server for use in accessing the measured data. Alternatively, the inventive system may include a virtual machine coupled to the HTTP server for use in accessing the data.


The prescribed quantity is preferably electricity, water or gas.


The HTTP server and CGI application may be embedded in each of the meters or, alternatively, embedded in the gateway.


Other features of the present invention are disclosed below.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 schematically depicts an AMR network comprising a wide area network 10, gateway 20, local area network 30 and meters 40, in accordance with the present invention.



FIG. 2 schematically depicts an embodiment of the present invention in which an HTTP server and a common gateway interface are located in the meter(s) 40.



FIG. 3 schematically depicts an embodiment of the present invention in which an HTTP server and a common gateway interface are located in the gateway 20.



FIG. 4 illustrates how the common gateway interface could be replaced by a Java virtual machine and a Java applet.



FIG. 5 portrays an embodiment of the invention in which one or more computers are given access to the meters by way of a PPP server or interface.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The present invention, in one embodiment, employs an electronic meter incorporating a TCP/IP protocol suite and an HTTP server for two-way access to the meter data. In another embodiment of the invention, the TCP/IP protocol suite is incorporated into a gateway serving multiple meters connected through a power line or wireless two-way network. The gateway employed in a second embodiment of the present invention incorporates an HTTP server for accessing data from multiple meters and for transmission of data to individual meters.


The basic architecture of the present invention is shown in FIG. 1. As mentioned, embedding an HTTP server and a TCP/IP protocol stack within a meter 40 or a gateway 20 to multiple meters through a local area network (LAN) 30 enables remote access to meter parameters on a continuous basis. As shown, a set of N meters 40 communicate through a non-TCP/IP type of LAN 30. The LAN 30 may be, e.g., a CEBus network employing power line or radio frequency communications (the Consumer Electronics Bus (CEBus) protocol has been adopted as an Electronics Industry Association standard (EIA IS-60), and defines a LAN that uses multiple media, including power line, radio, twisted pair, coaxial cable, and infrared signaling). Also connected to the LAN 30 is a gateway 20 that is also connected to a TCP/IP wide-area network (WAN) 10. Other applications (not shown) are also connected to the TCP/IP WAN 10 and may need to access the individual meters or groups of meters. These applications access individual meters by sending commands contained in packets with attached TCP/IP destination addresses that are unique to each meter.


In the first implementation of the invention (FIG. 2), the gateway 20 receives packets from other applications on the WAN 10. The gateway 20 includes a TCP/IP interface 22 and a LAN interface 28. The LAN interface 28 includes software for transforming the data packets into the format required for transmission on the LAN 30. The gateway 20 then transmits these reformatted packets over the LAN 30 to the meters 40. The steps involved in this transformation are:


1. The gateway examines the TCP/IP address of the packet and determines if it is the address of a meter or meters within the set attached to the gateway through its LAN. If not, the packet is ignored.


2. If the packet is intended for one of the meters on the gateway's LAN, the gateway examines the meter TCP/IP address attached to the packet and determines if it is an individual meter address or a broadcast address.


3. If the packet is addressed to an individual meter, then the gateway encapsulates the packet into a larger packet that is addressed to the meter using its unique LAN address (which is different from its TCP/IP address).


4. If the packet is meant for broadcast to all the meters, then the gateway encapsulates the packet into a larger packet addressed to the special broadcast address of the LAN (which is different from the TCP/IP broadcast address).


5. If the packet is larger than the maximum allowable packet size for the LAN, then the gateway segments the packet into smaller pieces. Each piece is labeled with the same LAN address as the original, larger packet.


6. Each piece of the segmented packet is transmitted onto the LAN for reception by one or more of the meters. The gateway is responsible for receiving acknowledgments of packet receptions from the meters, and for retransmitting packets if they are not received.


Each individual meter listens on the LAN for packets. A meter reconstitutes the original TCP/IP WAN packet from one or more LAN packets, and then executes the commands contained in the packet and sends the results back to the gateway. The steps involved in this process are:


1. The meter examines the LAN address of the packet to see if it is intended for this meter or is a broadcast address. If the address is neither of these, the meter ignores the packet.


2. If the packet is specifically addressed for the meter, an acknowledgment of reception is sent back to the gateway. If an error is found in the packet, a negative acknowledgment is sent back to the gateway. For broadcast transmissions, no acknowledgment is sent.


3. The received packet is appended to any previously received pieces of the larger segmented packet. When all of the pieces of the segmented packet are received, the entire original TCP/IP packet is extracted and sent to the TCP/IP interface software, in the meter.


4. The TCP/IP interface software examines the packet to see what service is being requested. In this case, assume the packet is intended for servicing by the HTTP server. (It is possible that there could be other servers running on the meter to which TCP/IP messages could be sent.)


5. The HTTP server examines the data packet to see what operation is being requested. In this case, assume that the packet contains a request that an application program be run on the meter to extract its current reading and send it back to the originator of the request. The HTTP server will initiate this application through the CGI.


6. The CGI application will query the meter application software to find the current reading. The meter application directly accesses the meter electronics to get the required information. The reading is passed back to the CGI application, which writes the reading into a message using HTML. The HTML message is sent back lo the HTTP server.


7. The HTTP server encodes the HTML message as a TCP/IP packet and sends it on to the meter's TCP/IP interface.


8. The meter's TCP/IP interface sends the packet to the gateway using the same set of steps that the gateway used to send the original request to the meter.


9. Once the gateway receives the TCP/IP packet from the meter, it retransmits the packet onto the WAN where the originating application for the command can receive it.


In the second embodiment of the invention (FIG. 3), the gateway assumes most of the tasks assigned to the meters in the first embodiment (FIG. 2). The HTTP server 24 and CGI application 26 are moved to the gateway 20, and the meters retain only their interface 42 to the non-TCP/IP LAN. The processing of packets received from the WAN 10 proceeds as follows:


1. The gateway examines the TCP/IP address of the packet and determines if it is the address of a meter or meters within the set attached to the gateway through its LAN. If not, the packet is ignored.


2. The TCP/IP interface software examines the packet to see what service is being requested. In this case, assume the packet is intended for servicing by the HTTP server now contained in the gateway. (It is possible that there could be other server applications running on the meter to which TCP/IP messages could be sent.)


3. The HTTP server examines the data packet to see what operation is being requested. In this case, assume that the packet contains a request that an application program be run to get the current reading of an individual meter and send it back to the originator of the request. The HTTP server will initiate this application through the CGI (26).


4. The CGI application 26 now runs within the gateway. It must determine the LAN address of the specified meter and send a command packet to it over the LAN.


5. The command is received by the meter and causes the meter application to query the electronics to find the current reading.


6. The meter reading is encapsulated into a LAN packet and sent back to the gateway.


7. The CGI application receives the LAN packet from the meter and extracts the meter reading. The reading is written into an HTML message and is sent back to the HTTP server.


8. The HTTP server encodes the HTML message as a TCP/IP packet and sends it on to the gateway's TCP/IP interface 22.


9. The gateway's TCP/IP interface 22 sends the packet onto the WAN 10 where the originating application for the command can receive it.


Both implementations of the present invention have been described as using CGI applications 46, 26 to handle the details of accessing the current reading for a meter. As shown in FIG. 4, the CGI application could be replaced by a Java virtual machine (VM) 26′ running a Java application 26″ that performs the same operations as the CGI application.


In addition, both implementations have been described using an example where the current reading of an individual meter is requested by an application connected to the WAN. An application on the WAN can also write data to a meter or meters using similar procedures. The data could modify parameters affecting the operations of the meter or meters. An example would be rate updates.


Either implementation, with their use of TCP/IP and HTTP servers, supports the reading of meters or setting their parameters using browsers such as a Netscape™ or Explorer™. Utilities and homeowners could perform remote on-demand meter reading via their browsers. An individual meter or group of meters could be accessed as if the meter(s) were a web site and their current readings or other data could be displayed on the browser. The meters could send forms to the browser that the user could fill in to change parameters in the meters. Both reading and updating the meters would be protected by encryption and passwords.


As shown in FIG. 5, a browser could gain access to the meters through a phone line to a Point-to-Point Protocol (PPP) server 60 attached to the WAN 10 or attached directly to a gateway 20. The PPP server interfaces with modems (not shown) to provide a TCP/IP link to a browser on the other end of the line. The PPP server sends the packets from the phone line onto the WAN where they are received by the appropriate gateway. In the case of a phone line connection directly to a gateway, the PPP software includes an interface 21 for directly connecting to the TCP/IP WAN interface 22 so that the packets received over the phone line are handled in the same way as packets received over the WAN 10.


The browser may be replaced by an intelligent application program that accesses the HTTP server for automated meter reading and parameter setting on a scheduled and repetitive basis. The application uses the meter readings to create or update records in a database. This application could be a Java application which can interact with the HTTP servers and databases that support the HTTP protocols.


In sum, the present invention includes the following novel aspects: (1) Embedded HTTP server in a meter for on-demand access to meter data and for remotely setting meter parameters; (2) Embedded HTTP server in a gateway to multiple meters to read and set parameters in individual meters on a LAN; (3) Using CGI for remote access to meter data and to set meter parameters using HTML forms in HTTP browsers; (4) Remote reading and setting of multiple meter parameters using TCP/IP protocol suite; (5) TCP/IP protocol suite implemented in designated nodes in a CEBus LAN including CEBus routers and brouters with remote access through TCP/IP to the router/brouter and, therefore, individual meters on a LAN; (6) SLIP-PPP enabled gateway for remote TCP/IP access through a serial interface (phone line, or ISDN, for example) to a single or multiple meter parameters (setting and reading).


The foregoing detailed description of preferred embodiments of the invention is not meant to limit the scope of protection of the following claims. Those skilled in the art of electronic metering will recognize that many modifications may be made to the presently preferred and specifically described embodiments without departing from the true spirit of the invention.

Claims
  • 1. An electronic metering system, comprising: (A) a wide area network (WAN) operating in accordance with a TCP/IP protocol;(B) a local area network (LAN) comprising a plurality of meters each of which includes meter electronics for measuring a prescribed commodity supplied by a utility and memory for storing measured data and meter control parameters;(C) a gateway operatively coupled to said LAN and said WAN; and(D) a server operatively coupled to said LAN and said gateway, whereby said WAN is provided remote access to said measured data and control parameters of said meters.
  • 2. A system as recited in claim 1, further comprising a common gateway interface (CGI) application coupled to said server for use in accessing said measured data.
  • 3. A system as recited in claim 2, wherein said server and said CGI application are embedded in each of said meters.
  • 4. A system as recited in claim 3, wherein each of said meters further comprises a TCP/IP interface.
  • 5. A system as recited in claim 2, wherein said server and said CGI application are embedded in said gateway.
  • 6. A system as recited in claim 1, further comprising a virtual machine coupled to said server for use in accessing said data.
  • 7. A system as recited in claim 1, wherein each of said meters further comprises a LAN interface.
  • 8. A system as recited in claim 1, wherein said gateway comprises a LAN interface.
  • 9. A system as recited in claim 1, wherein said gateway comprises a TCP/IP interface.
  • 10. A system as recited in claim 1, further comprising a common gateway interface (CGI) application coupled to said server for use in accessing said measured data; wherein said server and CGI application are embedded in each of said meters; wherein said gateway and each of said meters comprises a LAN interface and a TCP/IP interface; and wherein said prescribed commodity is a member of the group consisting of electricity, water and gas.
  • 11. A system as recited in claim 1, further comprising a common gateway interface (CGI) application coupled to said server for use in accessing said measured data; wherein said server and CGI application are embedded in said gateway; wherein each of said meters and said gateway comprises a LAN interface; wherein said gateway further comprises a TCP/IP interface; and wherein said prescribed commodity is a member of the group consisting of electricity, water and gas.
  • 12. An electronic meter, comprising: meter electronics for measuring a prescribed commodity supplied by a utility;a memory for storing measured data and meter control parameters; anda server operatively coupled to said meter electronics and memory;said electronic meter being configured for use in a system including a wide area network (WAN) operating in accordance with a TCP/IP protocol, a local area network (LAN), and a gateway operatively coupled to said LAN and said WAN,
  • 13. An electronic meter as recited in claim 12, further comprising a LAN interface and a TCP/IP interface operating in the meter.
  • 14. An electronic meter as recited in claim 12, further comprising a common gateway interface (CGI) application and a meter application operating in the meter.
  • 15. A gateway for use in a system comprising an electronic meter connected to a local area network (LAN), the gateway, and a wide area network (WAN) operating in accordance with a TCP/IP protocol, wherein the electronic meter is operatively coupled to the WAN through the gateway, the gateway comprising: a server embedded in the gateway and operatively coupled to said electronic meter, whereby said WAN is provided with remote access, via the gateway to measured data and control parameters of the electronic meter.
  • 16. A gateway is recited in claim 15, further comprising a LAN interface and a TCP/IP interface embedded in the gateway.
  • 17. A gateway as recited in claim 15, further comprising a common gateway interface (CGI) application operating in the gateway.
  • 18. A method for operating an electronic metering system, comprising: (A) providing a wide area network (WAN) operating in accordance with a TCP/IP protocol;(B) coupling the WAN to a local area network (LAN) comprising a plurality of meters each of which includes meter electronics for measuring a prescribed commodity supplied by a utility and memory for storing measured data and meter control parameters;(C) providing a server operatively coupled to said LAN; and(D) providing said WAN with remote access to said measured data and control parameters of said meters.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a CON of Ser. No. 09/975,582 filed Oct. 10, 2001 now U.S. Pat. No. 6,747,981 which is a CON of Ser. No. 09/022,718 filed Feb. 12, 1998 now U.S. Pat. No. 6,396,839.

US Referenced Citations (298)
Number Name Date Kind
3445815 Saltzberg et al. May 1969 A
3858212 Tompkins et al. Dec 1974 A
3878512 Kobayashi et al. Apr 1975 A
3973240 Fong Aug 1976 A
4031513 Simciak Jun 1977 A
4056107 Todd et al. Nov 1977 A
4066964 Costanza et al. Jan 1978 A
4132981 White Jan 1979 A
4190800 Kelly, Jr. et al. Feb 1980 A
4204195 Bogacki May 1980 A
4218737 Buscher et al. Aug 1980 A
4250489 Dudash et al. Feb 1981 A
4254472 Juengel et al. Mar 1981 A
4319358 Sepp Mar 1982 A
4321582 Banghart Mar 1982 A
4322842 Martinez Mar 1982 A
4328581 Harmon et al. May 1982 A
4361851 Asip et al. Nov 1982 A
4361890 Green, Jr. et al. Nov 1982 A
4396915 Farnsworth et al. Aug 1983 A
4405829 Rivest et al. Sep 1983 A
4415896 Allgood Nov 1983 A
4466001 Moore et al. Aug 1984 A
4504831 Jahr et al. Mar 1985 A
4506386 Ichikawa et al. Mar 1985 A
4513415 Martinez Apr 1985 A
4525861 Freeburg Jun 1985 A
4600923 Hicks et al. Jul 1986 A
4608699 Batlivala et al. Aug 1986 A
4611333 McCallister et al. Sep 1986 A
4614945 Brunius et al. Sep 1986 A
4617566 Diamond Oct 1986 A
4628313 Gombrich et al. Dec 1986 A
4631538 Carreno Dec 1986 A
4638298 Spiro Jan 1987 A
4644321 Kennon Feb 1987 A
4653076 Jerrim et al. Mar 1987 A
4672555 Hart et al. Jun 1987 A
4680704 Konicek et al. Jul 1987 A
4688038 Giammarese Aug 1987 A
4692761 Robinton Sep 1987 A
4707852 Jahr et al. Nov 1987 A
4713837 Gordon Dec 1987 A
4724435 Moses et al. Feb 1988 A
4728950 Hendrickson et al. Mar 1988 A
4734680 Gehman et al. Mar 1988 A
4749992 Fitzmeyer et al. Jun 1988 A
4757456 Benghiat Jul 1988 A
4769772 Dwyer Sep 1988 A
4783748 Swarztrauber et al. Nov 1988 A
4792946 Mayo Dec 1988 A
4799059 Grindahl et al. Jan 1989 A
4804938 Rouse et al. Feb 1989 A
4827514 Ziolko et al. May 1989 A
4839645 Lill Jun 1989 A
4841545 Endo et al. Jun 1989 A
4860379 Schoeneberger et al. Aug 1989 A
4862493 Venkataraman et al. Aug 1989 A
4868877 Fischer Sep 1989 A
4884021 Hammond et al. Nov 1989 A
4912722 Carlin Mar 1990 A
4922518 Gordon et al. May 1990 A
4939726 Flammer et al. Jul 1990 A
4940974 Sojka Jul 1990 A
4940976 Gastouniotis et al. Jul 1990 A
4958359 Kato Sep 1990 A
4964138 Nease et al. Oct 1990 A
4965533 Gilmore Oct 1990 A
4972507 Lusignan Nov 1990 A
5018165 Sohner et al. May 1991 A
5022046 Morrow, Jr. Jun 1991 A
5032833 Laporte Jul 1991 A
5053766 Ruiz-del-Portal et al. Oct 1991 A
5053774 Schuermann et al. Oct 1991 A
5056107 Johnson et al. Oct 1991 A
5067136 Arthur et al. Nov 1991 A
5079715 Venkataraman et al. Jan 1992 A
5086292 Johnson et al. Feb 1992 A
5086385 Launey Feb 1992 A
5090024 Vander Mey et al. Feb 1992 A
5111479 Akazawa May 1992 A
5115433 Baran et al. May 1992 A
5115448 Mori May 1992 A
5129096 Burns Jul 1992 A
5132985 Hashimoto et al. Jul 1992 A
5136614 Hiramatsu et al. Aug 1992 A
5142694 Jackson et al. Aug 1992 A
5151866 Glaser et al. Sep 1992 A
5155481 Brennan, Jr. et al. Oct 1992 A
5160926 Schweitzer, III Nov 1992 A
5166664 Fish Nov 1992 A
5177767 Kato Jan 1993 A
5179376 Pomatto Jan 1993 A
5189694 Garland Feb 1993 A
5194860 Jones et al. Mar 1993 A
5197095 Bonnet Mar 1993 A
5204877 Endo et al. Apr 1993 A
5214587 Green May 1993 A
5225994 Arinobu et al. Jul 1993 A
5228029 Kotzin Jul 1993 A
5229996 Bäckström et al. Jul 1993 A
5239575 White et al. Aug 1993 A
5239584 Hershey et al. Aug 1993 A
5243338 Brennan, Jr. et al. Sep 1993 A
5252967 Brennan et al. Oct 1993 A
5260943 Comroe et al. Nov 1993 A
5270704 Sosa Quintana et al. Dec 1993 A
5280498 Tymes et al. Jan 1994 A
5280499 Suzuki Jan 1994 A
5285469 Vanderpool Feb 1994 A
5287287 Chamberlain et al. Feb 1994 A
5289497 Jacobson et al. Feb 1994 A
5295154 Meier et al. Mar 1994 A
5307349 Shloss et al. Apr 1994 A
5311541 Sanderford, Jr. May 1994 A
5311542 Eder May 1994 A
5315531 Oravetz et al. May 1994 A
5319679 Bagby Jun 1994 A
5329547 Ling Jul 1994 A
5345225 Davis Sep 1994 A
5359625 Vander Mey et al. Oct 1994 A
5377222 Sanderford, Jr. Dec 1994 A
5381462 Larson et al. Jan 1995 A
5383134 Wrzesinski Jan 1995 A
5384712 Oravetz et al. Jan 1995 A
5387873 Muller et al. Feb 1995 A
5390360 Scop et al. Feb 1995 A
5406495 Hill Apr 1995 A
5416917 Adair et al. May 1995 A
5420799 Peterson et al. May 1995 A
5428636 Meier Jun 1995 A
5430759 Yokev et al. Jul 1995 A
5432507 Mussino et al. Jul 1995 A
5432815 Kang et al. Jul 1995 A
5438329 Gastouniotis et al. Aug 1995 A
5448230 Schanker et al. Sep 1995 A
5448570 Toda et al. Sep 1995 A
5450088 Meier et al. Sep 1995 A
5452465 Geller et al. Sep 1995 A
5455533 Köllner Oct 1995 A
5455544 Kechkaylo Oct 1995 A
5455569 Sherman et al. Oct 1995 A
5455822 Dixon et al. Oct 1995 A
5457713 Sanderford, Jr. et al. Oct 1995 A
5461558 Patsiokas et al. Oct 1995 A
5463657 Rice Oct 1995 A
5473322 Carney Dec 1995 A
5475742 Gilbert Dec 1995 A
5475867 Blum Dec 1995 A
5479442 Yamamoto Dec 1995 A
5481259 Bane Jan 1996 A
5488608 Flammer, III Jan 1996 A
5491473 Gilbert Feb 1996 A
5493287 Bane Feb 1996 A
5495239 Ouellette Feb 1996 A
5497424 Vanderpool Mar 1996 A
5499243 Hall Mar 1996 A
5500871 Kato et al. Mar 1996 A
5511188 Pascucci et al. Apr 1996 A
5519388 Adair, Jr. May 1996 A
5521910 Matthews May 1996 A
5522044 Pascucci et al. May 1996 A
5524280 Douthitt et al. Jun 1996 A
5525898 Lee, Jr. et al. Jun 1996 A
5526389 Buell et al. Jun 1996 A
5528507 McNamara et al. Jun 1996 A
5528597 Gerszberg et al. Jun 1996 A
5539775 Tuttle et al. Jul 1996 A
5541589 Delaney Jul 1996 A
5544036 Brown, Jr. et al. Aug 1996 A
5546424 Miyake Aug 1996 A
5548527 Hemminger et al. Aug 1996 A
5548633 Kujawa et al. Aug 1996 A
5553094 Johnson et al. Sep 1996 A
5555508 Munday et al. Sep 1996 A
5559870 Patton et al. Sep 1996 A
5566332 Adair et al. Oct 1996 A
5572438 Ehlers et al. Nov 1996 A
5590179 Shincovich et al. Dec 1996 A
5592470 Rudrapatna et al. Jan 1997 A
5594740 LaDue Jan 1997 A
5602744 Meek et al. Feb 1997 A
5617084 Sears Apr 1997 A
5619192 Ayala Apr 1997 A
5619685 Schiavone Apr 1997 A
5621629 Hemminer Apr 1997 A
5627759 Bearden et al. May 1997 A
5631636 Bane May 1997 A
5640679 Lundqvist et al. Jun 1997 A
5659300 Dresselhuys et al. Aug 1997 A
5668803 Tymes et al. Sep 1997 A
5668828 Sanderford, Jr. et al. Sep 1997 A
5673252 Johnson et al. Sep 1997 A
5684472 Bane Nov 1997 A
5684799 Bigham et al. Nov 1997 A
5691715 Ouellette Nov 1997 A
5692180 Lee Nov 1997 A
5696501 Ouellette et al. Dec 1997 A
5696765 Safadi Dec 1997 A
5699276 Roos Dec 1997 A
5714931 Petite et al. Feb 1998 A
5715390 Hoffman et al. Feb 1998 A
5717604 Wiggins Feb 1998 A
5719564 Sears Feb 1998 A
5744657 Tofte Apr 1998 A
5745901 Entner et al. Apr 1998 A
5748104 Argyroudis et al. May 1998 A
5748619 Meier May 1998 A
5751914 Coley et al. May 1998 A
5751961 Smyk May 1998 A
5754772 Leaf May 1998 A
5754830 Butts et al. May 1998 A
5757783 Eng et al. May 1998 A
5768148 Murphy et al. Jun 1998 A
5778368 Hogan et al. Jul 1998 A
5787437 Potterveld et al. Jul 1998 A
5790789 Suarez Aug 1998 A
5790809 Holmes Aug 1998 A
5801643 Williams et al. Sep 1998 A
5805712 Davis Sep 1998 A
5808558 Meek et al. Sep 1998 A
5809059 Souissi et al. Sep 1998 A
5822521 Gartner et al. Oct 1998 A
5850187 Carrender et al. Dec 1998 A
5862391 Salas et al. Jan 1999 A
5872774 Wheatley, III et al. Feb 1999 A
5874903 Shuey et al. Feb 1999 A
5875183 Nitadori Feb 1999 A
5875402 Yamawaki Feb 1999 A
5884184 Sheffer Mar 1999 A
5892758 Argyroudis Apr 1999 A
5896382 Davis et al. Apr 1999 A
5897607 Jenney et al. Apr 1999 A
5898387 Davis et al. Apr 1999 A
5907540 Hayashi May 1999 A
5910799 Carpenter et al. Jun 1999 A
5923269 Shuey et al. Jul 1999 A
5926103 Petite Jul 1999 A
5926531 Petite Jul 1999 A
5943375 Veintimilla Aug 1999 A
5944842 Propp et al. Aug 1999 A
5959550 Giles Sep 1999 A
5960074 Clark Sep 1999 A
5963146 Johnson et al. Oct 1999 A
5974236 Sherman Oct 1999 A
5986574 Colton Nov 1999 A
6000034 Lightbody et al. Dec 1999 A
6028522 Petite Feb 2000 A
6034988 VanderMey et al. Mar 2000 A
6035201 Whitehead Mar 2000 A
6041056 Bigham et al. Mar 2000 A
6061604 Russ et al. May 2000 A
6067029 Durston May 2000 A
6073169 Shuey et al. Jun 2000 A
6073174 Montgomerie et al. Jun 2000 A
6078251 Landt et al. Jun 2000 A
6078785 Bush Jun 2000 A
6078909 Knutson Jun 2000 A
6088659 Kelley et al. Jul 2000 A
6091758 Ciccone et al. Jul 2000 A
6100817 Mason, Jr. et al. Aug 2000 A
6112192 Capek Aug 2000 A
6128276 Agee Oct 2000 A
6137423 Glorioso et al. Oct 2000 A
6150955 Tracy et al. Nov 2000 A
6154487 Murai et al. Nov 2000 A
6160993 Wilson Dec 2000 A
6172616 Johnson et al. Jan 2001 B1
6199068 Carpenter Mar 2001 B1
6208266 Lyons et al. Mar 2001 B1
6218953 Petite Apr 2001 B1
6233327 Petite May 2001 B1
6246677 Nap et al. Jun 2001 B1
6249516 Brownrigg et al. Jun 2001 B1
6363057 Ardalan et al. Mar 2002 B1
6396839 Ardalan et al. May 2002 B1
6430268 Petite Aug 2002 B1
6437692 Petite et al. Aug 2002 B1
6446192 Narasimhan et al. Sep 2002 B1
6643278 Panasik et al. Nov 2003 B1
6684245 Shuey et al. Jan 2004 B1
6747981 Ardalan et al. Jun 2004 B1
6751563 Spanier et al. Jun 2004 B1
20010002210 Petite May 2001 A1
20010024163 Petite Sep 2001 A1
20020012323 Petite et al. Jan 2002 A1
20020013679 Petite Jan 2002 A1
20020019712 Petite et al. Feb 2002 A1
20020019725 Petite Feb 2002 A1
20020027504 Davis et al. Mar 2002 A1
20020031101 Petite et al. Mar 2002 A1
20020125998 Petite et al. Sep 2002 A1
20020145537 Mueller et al. Oct 2002 A1
20020169643 Petite et al. Nov 2002 A1
20030036810 Petite Feb 2003 A1
20030036822 Davis et al. Feb 2003 A1
20030202512 Kennedy Oct 2003 A1
20040113810 Mason, Jr. et al. Jun 2004 A1
Foreign Referenced Citations (13)
Number Date Country
0 446 979 Sep 1991 EP
0 629 098 Dec 1994 EP
2 118 340 Oct 1983 GB
2 157 448 Oct 1985 GB
2 186 404 Aug 1987 GB
2 237 910 May 1991 GB
02-67967 Mar 1990 JP
4290593 Oct 1992 JP
8194023 Jul 1996 JP
9302515 Feb 1993 WO
9304451 Mar 1993 WO
9532595 Nov 1995 WO
9610856 Apr 1996 WO
Related Publications (1)
Number Date Country
20040218616 A1 Nov 2004 US
Provisional Applications (1)
Number Date Country
60039716 Feb 1997 US
Continuations (2)
Number Date Country
Parent 09975582 Oct 2001 US
Child 10862723 US
Parent 09022718 Feb 1998 US
Child 09975582 US