In-home display communicates with a fixed network meter reading system

Abstract
A display system that communicates with existing automated meter reading communications systems to provide information to a user. The display includes a radio that listens to communications between a utility meter and the reading system. When the display recognizes a particular utility meter identifier, it captures meter read information and stores it in memory. The information may then be presented to the user. Alternatively, a broadcast message may be communicated, that when received by the display, causes the display to extract information from the receiver. A manual override button may be provided to allow a user to manually request information from the meter. The display will extract information from the meter upon receipt of the manual request.
Description
FIELD OF THE INVENTION

The present invention relates to a display system, and more particularly, to a display and systems and methods for retrieving information from a fixed network meter reading system.


BACKGROUND OF THE INVENTION

An automated means for collecting meter data involves a fixed wireless network. Devices such as, for example, repeaters and gateways are permanently affixed on rooftops and pole-tops and strategically positioned to receive data from enhanced meters fitted with radio-transmitters. Typically, these transmitters operate in the 902-928 MHz range and employ Frequency Hopping Spread Spectrum (FHSS) technology to spread the transmitted energy over a large portion of the available bandwidth. Data is transmitted from the meters to the repeaters and gateways and ultimately communicated to a central location.


With the increased sophistication of meters and reading techniques has come the corresponding sophistication of billing techniques and amount of information stored within utility meters. For example, energy meters may be operated as either a “demand” meter or as a “time-of-use” (TOU) meter. TOU meters allow a power company to provide greater differentiation by which the energy is billed. Energy metered during peak hours will be billed differently than electrical energy billed during non-peak hours. Also, demand meters allow for a billing charge based on the maximum amount of power consumed in a given period of time (e.g., 15 minutes). As a result, energy meters contain a significant amount of information that is useful to consumers.


In-home display concepts for home automation systems have been available for quite some time. Communications from the utility meter to the display have been accomplished with a variety of different technologies, ranging from low speed power line carrier to broadband RF. The communication requirements are typically guided by the sophistication of the home automation system, which vary from basic functionalities to full consumer service offerings. Historically, the high cost of providing information to in-home displays has prevented nearly all system approaches from gaining significant installation quantities.


Therefore, there is a need to provide an in-home display that implements a low cost communications system that is compatible with existing technologies and which provides energy consumption information, etc. to the residential customer. The present invention provides such a system.


SUMMARY OF THE INVENTION

The invention provides a system and method for providing an in-home display that receives information from energy meters via a wide area network approach using, e.g., FHSS techniques. The display communicates with existing automated meter reading communications systems to provide information to a user. The display includes a radio that listens to communications between a utility meter and the reading system. When the display recognizes a particular utility meter identifier, it captures meter read information and stores it in memory. The information may then be presented to the user. Alternatively, a broadcast message may be communicated, that when received by the display, causes the display to extract information from the receiver. A manual override button may be provided to allow a user to manually request information from the meter. The display will extract information from the meter upon receipt of the manual request.


The display may also retrieve information using out of band techniques. Here the display would communicate with the meter using FHSS channels that are reserved for that purpose. Other channels would be used for normal communication between the meter and the reading system to reduce the likelihood of system degradation. Alternatively, an RF system may be used that is independent of the reading system RF communication system.


These and other novel features will be described in further detail below.





BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing summary, as well as the following detailed description of preferred embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings exemplary constructions of the invention; however, the invention is not limited to the specific methods and instrumentalities disclosed. In the drawings:



FIG. 1 is a diagram of a wireless system for collecting data from remote devices;



FIG. 2 expands upon the diagram of FIG. 1 and illustrates a system in which the present invention is embodied;



FIG. 3 illustrates an exemplary display device; and



FIG. 4 illustrates exemplary communication links to the in-home display and network elements.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Exemplary systems and methods for gathering meter data are described below with reference to FIGS. 1-2. It will be appreciated by those of ordinary skill in the art that the description given herein with respect to those figures is for exemplary purposes only and is not intended in any way to limit the scope of potential embodiments.


Generally, a plurality of meter devices, which operate to track usage of a service or commodity such as, for example, electricity, water and gas, may be operable to wirelessly communicate with each other and/or to communicate with one another via a wireline network. A collector may be operable to automatically identify and register meters for communication with the collector. When a meter is installed, the meter becomes registered with the collector that can provide a communication path to the meter. The collectors may receive and compile metering data from a plurality of meter devices via wireless communications. Also, a communications server communicates with the collectors to retrieve the compiled meter data.



FIG. 1 provides a diagram of an exemplary metering system 110. System 110 comprises a plurality of meters 114, which are operable to sense and record usage of a service or commodity such as, for example, electricity, water, or gas. Meters 114 may be located at customer premises such as, for example, a home or place of business. Meters 114 may comprise an antenna and may be operable to transmit data, including service usage data, wirelessly or via wired connections. Meters 114 may be further operable to receive data wirelessly as well. In an illustrative embodiment, meters 114 may be, for example, electrical meters manufactured by Elster Electricity, LLC.


System 110 may further comprise collectors 116. Collectors 116 also may be meters operable to detect and record usage of a service or commodity such as, for example, electricity, water, or gas. Collectors 116 may comprise an antenna and may be operable to send and receive data wirelessly. In particular, collectors 116 may be operable to send data to and receive data from meters 114. In an illustrative embodiment, meters 114 and/or collectors 116 may be, for example, an electrical meter manufactured by Elster Electricity, LLC.


A collector 116 and the meters 114 for which it is configured to receive meter data define a subnet/LAN 120 of system 110. In the context of networking, meters 114 and collectors 116 may be considered as nodes in the subnet 120. For each subnet/LAN 120, data may be collected at collector 116 and periodically transmitted to a data collection server 206. The data collection server 206 may store the data for analysis and preparation of bills, for example, among other uses. The data collection server 206 may be a specially programmed general purpose computing system and may communicate with collectors 116 wirelessly or via a wireline connection such as, for example, a dial-up telephone connection or fixed wire network.


Generally, collector 116 and meters 114 may communicate with and among one another using any one of several robust wireless techniques such as, for example, frequency hopping spread spectrum (FHSS) and direct sequence spread spectrum (DSSS). As illustrated, meters 114a may be referred to as “first level” meters that communicate with collector 116, and meters 114b may be referred to as “higher level” meters that communicate with other meters in the network and that forward information to the collector 116.


Referring now to FIG. 2, there is illustrated a system 200. The system 200 may include a network management server 202, a network management system (NMS) 204 and a data collection server 206 that together manage one or more subnets/LANs 120 and their constituent nodes. The NMS 204 may track changes in the network state, such as new nodes registering/unregistering with the system 200, node communication paths changing, etc. This information may be collected for each subnet/LAN 120 and may be detected and forwarded to the network management server 202 and data collection server 206.


Communication between nodes and the system 200 may be accomplished using a LAN identification, however customers also may query and communicate with nodes using their own identifier. To this end, a marriage file 208 may be used to correlate a customer serial number, a manufacturer serial number and LAN identification for each node (e.g., meters 114a and collectors 116) in the subnet/LAN 120. A device configuration database 210 may store configuration information regarding the nodes. For example, in the metering system 110, the device configuration database may include data regarding time of use (TOU) switchpoints, etc. for the meters 114a and collectors 116 communicating to the system 200. A data collection requirements database 212 may contain information regarding the data to be collected on a per node basis. For example, a user may specify that metering data such as load profile, demand, TOU, etc. is to be collected from particular meter(s) 114a. Reports 214 containing information on the network configuration may be automatically generated or in accordance with a user request.


A network management system (NMS) 204 maintains a database describing the current state of the global fixed network system (current network state 220) and a database describing the historical state of the system (historical network state 222). The current network state 220 may contain data regarding current meter to collector assignments, etc. for each subnet/LAN 120. The historical network state 222 may be a database from which the state of the network at a particular point in the past can be reconstructed. The NMS 204 may be responsible for, among other things, providing reports 214 about the state of the network. The NMS 204 may be accessed via an API 220 that is exposed to a user interface 216 and a Customer Information System (CIS) 218. Other external interfaces may be implemented as well. In addition, the data collection requirements stored in the database 212 may be set via the user interface 216 or CIS 218.


The data collection server 206 collects data from the nodes (e.g., collectors 116) and stores the data in a database 224. The data may include metering information, such as energy consumption and may be used for billing purposes, etc. by a utility provider.


The network management server 202, network management system 204 and data collection server 206 may communicate with the nodes in each subnet/LAN 120 via a communication system 226. The communication system 226 may be a Frequency Hopping Spread Spectrum radio network, a mesh network, a Wi-Fi (802.11) network, a Wi-Max (802.16) network, a land line (POTS) network, etc., or any combination of the above and enables the system 200 to communicate with the metering system 110.


Referring now to FIG. 3, an in-home display 250 includes a radio system 260 and antenna 264 to enable it to communicate with meters 114 and collectors 116 using the existing radio infrastructure. As described above, the meters 114 and collectors 116 communicate via, e.g., Frequency Hopping Spread Spectrum radio. By communicating with the existing radio and meter firmware, the in-home display 250 can provide information to a user without significantly impacting the operation and cost of the meter 114/collector 116. Additionally, the meters 114/collectors 116 that are presently installed in the field would be able to support display communications, thus eliminating the need for a costly change-out.


As would be understood by those of ordinary skill in the art, the in-home display 250 also includes a power supply/power management components 252, program firmware 255, memory 256, a microcontroller 258 and an input/output device 262 to enable the in-home display to communicate with other down stream devices (e.g., a hand-held reader, personal computer, etc.). A user interface 254 is also provided in an, e.g., LCD display, to allow an end user to interact with the display 250.


The amount of communications traffic within the system 110 is variable. For example, traffic can be heavy during some meter intervals and during network configuration periods. Other unscheduled events can occur that will also require considerable communication traffic. One-way devices, such as water and gas meters provide additional random traffic. The collector 116 typically controls communication traffic within a subnet/LAN 120 so that communication contention is reduced as much as possible.


To minimize contention with normal traffic, the collector 116 preferably controls the communications to the display 250. In general, if the collector 116 has control of the majority of display communications, the collector 116 can coordinate the meter reading and utility operational communications with the display communications. As an example, if meters are read every 4 hours and the total meter read time is 30 minutes, the collector 116 would preferably prevent display traffic during this meter read interval.


Normal Traffic Coordination


With reference to FIG. 4, for the in-home display 250 to gain a timely update that is correlated to the meter read interval, the display 250 may listen to the normal meter read traffic. When the associated meter 114 transmits its meter data, the display firmware 255 recognizes the meter's unique ID and updates the display memory with the current meter read information (communication link 268). The display 250 may maintain a duplicate copy of the meter's configuration so that information such as “time synch,” “tier pricing” or “TOU schedule” is known to the display 250.


However, there may be instances where interference or other operations prevent the display 250 from hearing the normal meter read communication. To account for these circumstances, when the meter read interval is complete, a broadcast message is sent throughout the system 110 that is directed to the in-home displays 250 (communication link 270). The display devices 250 are capable of receiving the broadcast command via the radios 260. After receipt of the broadcast, in-home display firmware 255 randomly or via a schedule extracts required information from it associated meter 114 (communication link 272). The individual displays 250 would be able to randomly select communication time windows in order to minimize contention traffic between displays or the collector could assign slot times. Using above noted solutions, the in-home display update would occur at approximately the same rate as the utility update rate.


The display firmware 255 accesses data from the meter 114 using table-based reads of selected information. Such table-based reads are performed by the collector 116 in its retrieval of information from the meter 114.


A manual override capability may be offered to the residential or commercial owner for the instances where more up-to-date metering data is desired. The display device 250 may optionally include a “read button” 266 that when activated, extracts the most recent meter data. The “read button” functionality may also provide a menuing system to allow the customer to extract more specific meter data than a standard update would provide using link 272. The display firmware 255 may include an override capability to prevent display traffic contention if the button is accidentally pushed multiple times in succession or fails in a mode that requests the update continuously.


In yet another alternative, the in-home display 250 may be placed as a node in the system 110. Here the meter read interval may not be correlated and the in-home display 250 contains the communications bound for the system 200. In this case, the collector 116 would update and read from the meter 114 and would additionally download information to the in-home display 250. This may be accomplished using link 272, where the link is a LAN communications link, such as those used between the collector 116 and the meters 114. Downloaded information could include the last meter read data, “time synch,” “tier pricing” or “TOU schedule” information. Additionally, information such as energy pricing could be downloaded to the in-home display 250 to provide an accurate representation of tier or total consumption.


The display firmware 255 may also have the capability to perform mathematical functions related to the metering data extracted from the meter 114. Examples of these functions include, but are not limited to, determining projected monthly usage, expected monthly bill, current rate of usage, comparison of today's or this month's usage to last year, etc. These types of calculations may be provided within the display firmware 255 without any impact on the existing meter firmware.


It is possible that the requirements of the display functionality will require that the collector 116 provide information to the display that is not part of the normal system traffic. This new information may be implemented in the existing communication infrastructure using new meter tables within the meter 114. Communications that write to tables in the in-home displays 250 would be handled by the meters 114 and meter repeaters to provide display devices necessary information related to energy pricing and other nonstandard metering data.


The in-home display 250 may perform the following non-limited functions:


Load Management: Curtailment, Notification, Automation


System Information: Control, Monitor, Outage (detect, record), Faults


Pricing Options: TOU, RTP, History, Tier Indication


Meter Reading: On site, Currency Conversion, Visual Presentations


Remote Disconnect: Status, Load Limiting, Prepay


Payment Notification: Bill, Prepay, Fund Transfer, Average Billing, On Demand


Alarms: Security, Tamper, Errors, Measurements


Load Research: Load Profile History, Payment History (monthly, yearly)


Messaging: Utility Info, Price Quotes, External Environment, Warnings


Metering: Sub-metering, Power Signature, Voltage Monitor


Advanced Functions: Harmonics, Power Factor, Other Energies, Gateway


Out of Band Traffic


There is a possibility that in some environments the communication requirements associated with the in-home display 250 will be quite high (e.g., as often as every minute). If the meter radio is required to spend a significant percentage of the time communicating with the in-home display 250, the result can be a degradation in the meter reading system performance. This degradation can occur because the meter in question will not respond to system reads while in-home communication is occurring. Compounding this problem, is that adjoining meters may not respond to system reads either due to in-band noise being generated by in-home communications. If large numbers of meters have in-home communications that are concurrent, the overall noise level may be excessive and meter reading system performance could suffer.


A typical communication consists of a 65-msec preamble followed by a 16-bit start frame delimiter and then a packet. The 65-msec preamble, SFD and packet are sent on one frequency out of the 25 channels used by the system. The 65-msec preamble allows sufficient time for an asynchronous receiver to scan all 25 possible channels with a redundant algorithm. FCC Part 15.247 focuses on an equitable distribution of energy across the spectrum in question. In the system 110, the spectrum is 902-915 MHz and equal distribution is managed by insuring each packet is sent on a different frequency. A frequency is not repeated until all 24 others have been utilized by a given transmitter. The total ISM band is 902-928 MHz, though, so there are another 30 channels in the total ISM band that can be utilized.


An approach for display communications in the ISM frequency spectrum that alleviates the above problem may be a system where the meter 114 sends display packets that use a selection of the 25 higher frequency channels. In an embodiment of this scheme, the display receiver 260 would begin by looking for channel 26. Similarly, the meter transmitter would begin with frequency 26 to send a display packet. Once the display receiver 260 detects channel 26 it decodes the data and determines the transmitter timing such that it can stay in lock step with the meter 114. This serves to minimize the amount of time spent on any given display packet relative to the 65-msec preamble time for the lower frequency channels. Further, if display communications is accomplished on the upper channels, the meter 114 and display 250 would have the same random list of channels to select from and would synchronously step through the channels to keep the energy in each higher channel equal.


Assuming the display receiver is able to change channels and lock in 0.5 msec, a 32-bit display packet should be able to be executed in less than 5 msec. With this limited amount of transmission time, display packets should have minimal impact on communications in the system 110. With changes to the meter firmware, the meter could be limited such that it will not send a display packet until a scan algorithm is complete. This restriction would further insure the display packet should not prevent the meter from receiving a valid message.


With the above firmware programming, the system 110 operates normally for LAN communications and the meter 114 occasionally transmits a short segment of a display packet outside of the LAN 25-channel spectrum. By being properly time synchronized, the display receiver 260 would be able to handle lower band communications or receive higher band display communications. The display transceiver 260 would have the capability to transmit standard packets as well. This type of system would allow the in-home display 250 to be programmed, configured or read from the collector 116 through the conventional mesh network 110 and would also allow the display to receive one-way burst updates from the meter 114 when the display refresh rate requirement was high. If two-way communication is necessary between the display 250 and the meter 114, it could be scheduled or if it is random enough, it could be accomplished on the assumption the contention would be minimal.


Alternate RF Communication


To eliminate any possibility of contention that would degrade system performance, an alternate RF or powerline technology could be implemented within the meter 114 and the in-home display 250. The intelligence for this alternate communication system is preferably independent of the meter radio controller, so in-home display traffic will have no impact on the traffic in the system 110. By using a standard radio or powerline technology there is significant opportunity to reduce display system costs.


In order to minimize the impact on system communications, the selected alternate RF or powerline technology should not impact the 902-928 MHz wireless band. An ISM solution in the 2.4 GHz wireless spectrum or broadband wired solution appears to offer the best compromise between performance, cost and industry standardization. The ZIGBEE network built on top of the IEEE 802.15.4 physical and MAC layers is an exemplary suitable alternative RF technology. The Homeplug powerline solution is a typical standard wired technology.


The alternate radio or powerline technology in the meter is preferably coupled to a microprocessor that can process the network traffic without burdening the meter intelligence. By incorporating a second communication processor the in-home display traffic will be off-loaded from the meter micro to further guarantee no contention for the system 110. Data coordination between the two networks should be handled with a standard digital interface like Rx/Tx, SPI or I2C.


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.


For example, although a great deal of the discussion was based on the use of certain devices and communication paths, it should be appreciated that the contemplated embodiments include the use of any devices, communication paths and techniques. Moreover, although device configurations have been described herein, it should be appreciated that the devices are provided merely to provide an understanding of the many techniques contemplated by the embodiments. 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.

Claims
  • 1. A method of providing commodity consumption information to a user via a remote display, comprising: communicating with a utility meter associated with the remote display, wherein the associated utility meter is part of a wireless network comprising a collector and a plurality of utility meters that bi-directionally communicate wirelessly with the collector, each of the utility meters having a wireless communication path to the collector that is either a direct communication path to the collector or an indirect communication path through one or more other utility meters that serve as repeaters, and the collector receiving commodity consumption information from the plurality of utility meters;wirelessly retrieving commodity consumption information from the associated utility meter by the remote display in response to a message from the collector received by the remote display, wherein the message received from the collector controls the time at which commodity consumption information is retrieved from the associated utility meter by the remote display; andupdating the remote display with said commodity consumption information.
  • 2. The method of claim 1, further comprising maintaining a duplicate copy of configuration information of said utility meter.
  • 3. The method of claim 2, said configuration information comprising at least one of time synch, tier pricing, and a TOU schedule.
  • 4. The method of claim 1, wherein said communicating with said associated utility meter comprises: recognizing an identifier of said associated utility meter; andupdating memory with current meter read information from said associated utility meter.
  • 5. The method of claim 1, wherein the message received from the collector is broadcast by the collector via the wireless network.
  • 6. The method of claim 1, wherein the message received from the collector is wirelessly transmitted by the collector on a frequency that is not used by the utility meters of the automated meter reading system to bi-directionally communicate with the collector.
  • 7. The method of claim 1, further comprising retrieving commodity consumption information from said associated utility meter in response to receipt of a manual read request.
  • 8. The method of claim 7, further comprising: providing a user interface on said display in response to said manual read request; andproviding a selection of types of information to be retrieved by said display in response to a user input.
  • 9. The method of claim 1, further comprising: manipulating said commodity consumption information to determine supplemental information, said supplemental information comprising at least one of projected commodity usage, a bill for a predetermined time period, and a comparison of commodity usage for first period versus a second period.
  • 10. A remote display that communicates with an automated meter reading system, the automated meter reading system comprising a collector and a plurality of utility meters that bi-directionally communicate wirelessly with the collector, each of the utility meters having a wireless communication path to the collector that is either a direct communication path to the collector or an indirect communication path through one or more other utility meters that serve as repeaters, and the collector receiving commodity consumption information from the plurality of utility meters, the remote display comprising: memory for storing commodity consumption data;firmware containing executable instructions for receiving commodity consumption data from an associated utility meter of said automated meter reading system;a microcontroller; anda radio adapted to retrieve commodity consumption data from the utility meter associated with the remote display in response to a message received from the collector of said automated meter reading system, wherein the message received from the collector controls the time at which commodity consumption information is retrieved from the associated utility meter by the remote display.
  • 11. The display as recited in claim 10, wherein the message received from the collector is wirelessly transmitted by the collector on a frequency that is not used by the utility meters of the automated meter reading system to bi-directionally communicate with the collector.
  • 12. The display as recited in claim 11, wherein the message received from the collector is broadcast by the collector via the wireless network.
  • 13. The display as recited in claim 10, farther comprising a manual read control, wherein said commodity consumption information is retrieved from said associated utility meter in response to receipt of an input via said manual read control.
  • 14. The display as recited in claim 10, wherein said automated meter reading system utilizes Frequency Hopping Spread Spectrum (FHSS) communications having a predetermined number of channels, and wherein said radio utilizes a first subset of said number of channels in which to communicate with said utility meter.
  • 15. The display as recited in claim 14, wherein said display communicates with said automated meter reading system utilizing a second subset of said number of channels, said second subset of channels not intersecting said first subset of channels.
  • 16. An automated meter reading system comprising: a collector;a plurality of utility meters that bi-directionally communicate wirelessly with the collector, each of the utility meters having a wireless communication path to the collector that is either a direct communication path to the collector or an indirect communications path through one or more other utility meters that serve as repeaters, the plurality of utility meters transmitting commodity consumption data to the collector and the collector transmitting control information to the utility meters; andat least one in-home remote display device comprising: memory for storing commodity consumption data;firmware containing executable instruction for receiving commodity consumption data from an associated utility meter of said automated meter reading system;a microcontroller; anda radio adapted to retrieve commodity consumption data from the utility meter associated with the remote display in response to a message received from the collector of said automated meter reading system, wherein the message received from the collector controls the time at which commodity consumption information is retrieved from the associated utility meter by the remote display.
  • 17. The display as recited in claim 16, wherein the message received from the collector is wirelessly transmitted by the collector on a frequency that is not used by the utility meters of the automated meter reading system to bi-directionally communicate with the collector.
  • 18. The display as recited in claim 16, wherein the message received from the collector is broadcast by the collector via the wireless network.
  • 19. The display as recited in claim 16, further comprising a manual read control, wherein said commodity consumption information is retrieved from said associated utility meter in response to receipt of an input via said manual read control.
  • 20. The display as recited in claim 16, wherein said automated meter reading system utilizes Frequency Hopping Spread Spectrum (FHSS) communications having a predetermined number of channels, and wherein said radio utilizes a first subset of said number of channels in which to communicate with said utility meter.
  • 21. The display as recited in claim 20, wherein said display communicates with said automated meter reading system utilizing a second subset of said number of channels, said second subset of channels not intersecting said first subset of channels.
US Referenced Citations (323)
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 Fitzemeyer 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
4804957 Selph et al. Feb 1989 A
4811011 Sollinger Mar 1989 A
4827514 Ziolko et al. May 1989 A
4833618 Verma 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
5007052 Flammer Apr 1991 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
5079768 Flammer 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
5130987 Flammer 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 Bonnett 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
4749992 Fitzmeyer et al. Jun 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
5570084 Ritter et al. Oct 1996 A
5572438 Ehlers et al. Nov 1996 A
5574657 Tofte 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 et al. Apr 1997 A
5627759 Bearden et al. May 1997 A
5631636 Bane May 1997 A
5636216 Fox et al. Jun 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
5696903 Mahany 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
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
5907491 Canada et al. May 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
5953319 Dutta et al. Sep 1999 A
5958018 Eng et al. Sep 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
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
6124806 Cunningham et al. Sep 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
6195018 Ragle et al. Feb 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
6333975 Brunn et al. Dec 2001 B1
6363057 Ardalan et al. Mar 2002 B1
6393341 Lawrence et al. May 2002 B1
6396839 Ardalan et al. May 2002 B1
6421731 Ciotti, Jr. et al. Jul 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
6657549 Avery Dec 2003 B1
6684245 Shuey et al. Jan 2004 B1
6751563 Spanier et al. Jun 2004 B2
6867707 Kelley et al. Mar 2005 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
20020026957 Reyman Mar 2002 A1
20020027504 Davis et al. Mar 2002 A1
20020031101 Petite et al. Mar 2002 A1
20020094799 Elliott et al. Jul 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
20030123442 Drucker et al. Jul 2003 A1
20030202512 Kennedy Oct 2003 A1
20040001008 Shuey et al. Jan 2004 A1
20040113810 Mason, Jr. et al. Jun 2004 A1
20050184881 Dusenberry et al. Aug 2005 A1
20050190074 Cumeralto et al. Sep 2005 A1
20050270173 Boaz Dec 2005 A1
Foreign Referenced Citations (20)
Number Date Country
682196 Jul 1993 CH
0 395 495 Oct 1990 EP
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
02 222 898 Mar 1990 GB
2 237 910 May 1991 GB
59-229949 Dec 1984 JP
02-67967 Mar 1990 JP
02-67967 Mar 1990 JP
4290593 Oct 1992 JP
05-260569 Oct 1993 JP
8194023 Jul 1996 JP
9302515 Feb 1993 WO
9304451 Mar 1993 WO
9532595 Nov 1995 WO
9610856 Apr 1996 WO
WO 2004004364 Jan 2004 WO
Related Publications (1)
Number Date Country
20070200729 A1 Aug 2007 US