The present invention relates in general to measuring meters, and, more specifically, to remotely managing usage of a water distribution system.
To the extent that conventional utility meters can transmit usage data, these meters are typically capable of transmitting data only relatively infrequently due to power constraints. Moreover, this transmission distance is generally limited, requiring field technicians to either read the meter directly or from a relatively short distance away. Furthermore, conventional utility meters do not allow for rapid and tailored response to emergency situations that may require an immediate shut-off of a utility to a selected customer or group of customers.
In addition, although water meters generally require recalibration after about 3-5 years of operation, it is typical for many water meters to remain uncalibrated due to the effort and expense required to systematically check and calibrate individual meters in a given service area. As a result, the utility company or the customer may suffer significant losses due to undercharging or overcharging. Another disadvantage of conventional meters is that the meters typically must be completely disconnected or removed before repairs, part replacements, or upgrades may be performed.
Accordingly, there is a need for a water meter and system that provides real-time access to usage data, two-way communication over a significant distance, and remote calibration and control functions.
In view of the foregoing and other considerations, the present invention relates to a system and method for remotely managing and monitoring the usage and distribution of water utilities.
Accordingly, a meter that monitors usage of a water distribution system by a client is provided. The meter includes a wireless communications system operable to communicatively couple the meter to a wireless network to provide two-way communication between the meter and the wireless network; a calibration system operable to calibrate the meter, wherein the calibration system may calibrate the meter in response to an instruction received from the wireless network; and a power system operable to maintain a sufficient level of power for the meter to allow substantially real-time communication between the meter and the wireless network.
A system for managing client water usage is provided. The system includes a network operations center comprising a server, a database, and a wireless communications transmitter and receiver operable to communicatively couple the network operations center to a wireless network; and a self-powered water meter operable to monitor the client water usage, wherein the meter is communicatively coupled to the wireless network and operable to provide two-way communication with the network operations center, and wherein the meter is operable to transmit data concerning the client water usage to the network operations center.
A method for remotely managing client water usage in connection with a water distribution system, wherein the client is located within a service region, is provided. The method includes the steps of providing a self-powered wireless water meter communicatively coupled to a wireless network and operable to monitor client water usage; transmitting a request to the meter for data concerning the client water usage via the wireless network; and receiving data concerning the client water usage of the client via the wireless network.
The foregoing has outlined the features and technical advantages of the present invention in order that the detailed description of the invention that follows may be better understood. Additional features and advantages of the invention will be described hereinafter which form the subject of the claims of the invention.
The foregoing and other features and aspects of the present invention will be best understood with reference to the following description of a specific embodiment of the invention, when read in conjunction with the accompanying drawings, wherein:
Refer now to the drawings wherein depicted elements are not necessarily shown to scale and wherein like or similar elements are designated by the same reference numeral through the several views.
The present invention is directed towards a wireless water meter and a system and method for remotely managing and monitoring usage of a water distribution system implementing the wireless water meter. The wireless water meter of the present invention may be substantially self-powered and is operable to maintain two-way communication over a wireless network with a network operations center to provide real-time access to water usage data, and remote monitoring and control of the wireless water meter.
System 10 includes a wireless water meter 35 of the present invention. Wireless water meter 35 comprises a valve (not shown in
System 10 includes network operations center 50 to manage and monitor the distribution of water utilities in system 10. Network operations center 50 may be operated by a water utility company, for example. Network operations center 50 includes a wireless communications transmitter/receiver 55 to send and receive data over wireless network 70. Network operations center 50 includes one or more servers 60 to manage data transmission through system 10. For example, transmitter/receiver 55 may receive radio frequency (RF) signals via wireless network 70 and convert these signals to Internet Protocol (IP) signals, or other suitable network protocol, for transmission to server 60, or other components of system 10. Network operations center 50 may also include database 65 to store data concerning client water usage and service area water usage, among other information.
Network operations center 50 may receive data from wireless water meter 35 concerning the water usage of client 45. Moreover, network operations center 50 may send data or instructions to wireless water meter 35. System 10 may include one or more mobile field technicians 75 to facilitate data collection and transmission throughout the service area associated with system 10. For example, network operations center 50 may send data to and receive data from wireless water meter 35 via mobile field technician 75. Mobile field technicians 75 may include transmitter/receivers 75a, portable computers 75b, and cell phones or personal digital assistants (PDA) 75c, for example, to communicate with wireless water meter 35 and wireless network 70.
System 10 may also allow communication with client 45 concerning the status or usage of the water utility. For example, network operations center 50 may transmit e-mail correspondence to client 45 regarding alerts or notices. For example, if network operations center 50 receives data indicating a potential water leak, network operations center 50 may request that client 45 verify whether a water leak has been observed. If the service area is subject to water rationing or similar form of controlled distribution, for instance, network operations center 50 may provide a notice to client 45 concerning the remaining amount of water client 45 is allowed to use for a given rationing period.
System 10 may include one or more emergency response centers 80. Emergency response center 80 may be any city, state or federal government agency responsible for responding to emergencies and with authority to redirect or shut off utilities based on the circumstances, e.g., natural disasters or contamination, for example. For example, emergency response center 80 may include local fire departments, the Federal Emergency Management Agency (FEMA), the United States Department of Homeland Security (DHS), or similar entities. Network operations center 50 may communicate with emergency response center 80, via wireless network 70, for example, and manage the distribution of utilities throughout system 10 in accordance with instructions received from emergency response center 80.
Wireless water meter 35 may include display 145, such as an LCD readout for example, to display information and water usage data, for instance. Display 145 may be connected to electronic systems module 150 to provide both local and remote field meter readings and measurements to field technicians 75 or network operations center 50 (both not shown in
Power system 95 provides sufficient power to wireless water meter 35 to permit substantially real-time access to wireless water meter 35 over wireless network 70 and permit wireless water meter 35 to perform actions such as transmitting data and self-calibrating as needed and on a fairly regular basis. As shown in the embodiment in
Battery system 100 provides power for wireless water meter 35. As shown in
Charging system 90 provides charge current to battery system 100 to put a selected amount of energy into the cells of battery 170. For example, for the polymer lithium batteries discussed above, charging system 90 may provide a 4 to 12 V DC current. Charging system 90 may include a miniature hydroelectric turbine AC or DC alternator or generator 180. Generator 180 may utilize the water flow within wireless water meter 35, e.g., water flow through interior channel 165 rotates generator paddle 230 to generate power. A suitable hydroelectric turbine AC/DC alternator/generator is manufactured by Graupner GmbH & Co. KG of Germany, for example. Accordingly, charging system 90 provides a built-in battery charging system for providing power to maintain the on-board battery, electronic components and network communications. As a result, wireless water meter 35 may be substantially self-powered and may generate enough power to provide substantially real time access and communications capability over wireless network 70 for greater periods of time and also perform actions such as calibrating itself without being constrained by power limitations. In addition, the components of power system 95 are modular, and allow a user to replace components, e.g., battery 170, quickly and easily, and without necessitating the removal of the entire meter 35. Wireless water meter 35 may use other devices to maintain a constant power source, including solar panels, for example.
Flow measurement system 115 measures water flow volume through wireless water meter 35 to allow for a determination of the water usage by client 45 (not shown in
Meter shut-off system 110 allows wireless water meter 35 to shut-off water to client 45 (not shown in
Wireless water meter 35 includes primary wireless communications module 130, which may be communicatively coupled to wireless water meter 35 via an expansion card slot 215. Primary wireless communications module 130 may comprise any module operable to support two-way communication over a wireless network. For example, primary wireless communications module 130 may include a plug-in radio communications card to support cellular, Wi-Fi, Wi-Max, 400 MHz, 900 MHz or proprietary radio network protocols, among other wireless protocols. Wireless water meter 35 may also include backup wireless communications module 135 in the event that primary wireless communications module 130 becomes inoperable or the communications network for primary wireless communications module 130 goes down. Backup wireless communications module 135 preferably uses a different communications protocol than module 130, e.g., communicates via a different network, to provide greater reliability or emergency response. Wireless water meter 35 may include additional expansion card slots 215 to allow for additional wireless communications modules 130 or electronic systems modules 150. Wireless water meter 35 may include an antenna 300, e.g., connected to electronic systems module 150 or communications modules 130 or 135, for example, to facilitate wireless communication.
Electronic systems module 150 comprises a circuit board or similar electronic device comprising a microprocessor, memory and similar components. Electronic systems module 150 includes firmware-based programs for operating wireless water meter 35 and handling communications with network operations center 50 (not shown in
Wireless water meter 35 may include one or more sensors to determine selected properties of the water and help determine water flow volume and water usage. For example, wireless water meter 35 may include temperature and pressure sensor 140. One suitable example of temperature and pressure sensor 140 is the AST-4000 sensor manufactured by American Sensor Technologies, Inc. of Mt. Olive, N.J.
Calibration system 105 allows system 10 (not shown in
Upon initiating calibrate mode, network operations center 50 instructs water meter 35 to shut off water to client 45 (not shown in
For example, water flow measurement system 115 determines water usage based on the number of revolutions of paddle wheel 125 within water chamber 220 as measured by optic sensor 120. During the calibration process, network operations center 50 or electronic system module 150 measures the number of turns for a given flow volume against a lab calibrated value. Accordingly, network operations center 50 may reset optic sensor 120 based on the new number of revolutions on paddle wheel 125.
Alternatively, or in addition, calibration system 105 may allow wireless water meter 35 to be self-calibrating. For example, electronic system module 150 may issue instructions to calibration system 105 to perform the calibration test in accordance with a selected schedule or in response to certain events or apparent water usage behavior. Calibration system 105 may then send the data to electronic systems module 150 for processing. If necessary, electronic systems module 150 may adjust water flow measurement system 115 to correct for any loss in calibration, e.g., reset optic sensor 120. A log or record of the calibration results may then be automatically transmitted to network operations center 50 for storage, analysis or review.
CAD interface software 280 allows a user to access database 65 and use the stored usage data for the purposes of system modeling, analysis and design, for example. Two-way communications software 255 interacts with communications control software 235 to provide two-way communication between network operations software 265 and wireless water meter 35. For example, network operations software 265 may send specified commands to one or more meters 35. Once the selected meters 35 have responded and completed the commands, the selected meters 35 may verify their status with a response.
Utility billing interface 260 may interface with selected conventional billing software platforms and provide billing information such as water usage, reading date, cost per gallon, time and date of water use, multiple billing rates by time of usage, date of usage, and amount of usage or overages, among other information. This information may be stored to or retrieved from database 65 and output as detailed utility bills 285 or reports 290.
Meter alert monitor 270 monitors usage characteristics for each meter 35 connected to wireless network 70 to establish a standard pattern of usage for each meter 35 for each season. Once a standard pattern has been established, network operations software 265 monitors the current usage patterns of a selected meter 35 and compares the current usage patterns against the associated standard pattern of usage. By comparing the patterns, network operations software may detect any major changes which may be attributed to tampering, leakage, broken pipes, low pressure and backflow, among other problems. Upon detecting a potential problem, an alert may be issued to a user via network operations center 50. Accordingly, meter alert monitor 270 may prevent or minimize substantial losses to both the utility company and client. Meter alert monitor 270 may also allow network operations center 50 to monitor mainline distribution for volume purchased and volume sold to facilitate the system audit process.
Remote activation/deactivation software 275 may poll the utility company's billing system, e.g., via utility billing interface 260, for delinquent accounts and notify network operations center 50 or the user to initiate remote deactivation and/or reactivation of any selected meter 35. Network operations software 265 may receive new customer activation requests and accordingly test, calibrate and activate the meter via remote activation/deactivation software 275. During ration or conservation periods, network operations software 265 and activation/deactivation software 275 may monitor water usage per meter 35 by selected day or hour for violations of local ordinances and automatically send a violation charge to the billing system along with data confirming the violation and/or initiate water shut-off to prevent violations. During emergency situations or in response to critical conditions such as loss of pressure, backflow issues, or water pump failure, network operations software 265 and activation/deactivation software 275 may respond quickly and deactivate meters 35 one by one, grid by grid, or even the entire system, and reactivate the system as needed without requiring the dispatch of field technicians or personnel.
As discussed above, water meter 35 may include firmware-based software resident on electronic systems module 150 to communicate, control aspects of wireless water meter 35 or collect data. As shown in
Communications control firmware 235 may be programmed for the selected wireless communication module 130 to manage reception and transmission of data across wireless network 70. The programmability of radio control firmware 235 allows a user to use the same base hardware and utilize different networks or radio modules in different areas as needed. Battery module firmware 245 monitors the status of battery system 100 and charging system 90 to determine the power levels of batteries 170. Battery module firmware 245 may interact with power safety monitor firmware 240 to manage power for wireless water meter 35.
Power safety monitor firmware 240 monitors power consumption and power generation to maintain a safe battery level for normal onboard operation requirements. Power safety monitor firmware 240 allows wireless water meter 35 to operate and store required data during low power generation cycles and refrain from broadcasting on wireless network 70 to conserve power. Power safety monitor firmware 240 may also monitor command requests from network operation software 265 and permit a broadcast on wireless network 70 during low battery periods only in emergency operations. Power safety monitor firmware 240 may update network operation software 265 on a selected schedule, e.g., weekly, and alert network operation software 265 when any status condition is out of the normal range, e.g., battery power, generator performance, and system pressure, among other examples.
Meter calibration firmware 250 interacts with calibration system 105 to manage the self-calibration or remote calibration of wireless water meter 35. A user of network operations center 50 may remotely activate meter calibration firmware 250 from network operations software 265. Once activated, meter calibration firmware 250 may run a calibration test. For example, meter calibration firmware 250 may interact with other system components to shut water off to client 45, test and store the system pressure data, register the output of optic sensor 120 via display 145, open calibration port 185 and, after a selected time, close calibration port 185. Once calibration port 185 is closed, meter calibration firmware 250 may re-test the system pressure and register the new readout from display 145. Meter calibration firmware 250 may calculate any changes from calibration port 185, readjust the readout for display 145 and transmit the results to central operations software 265.
The present invention provides a number of advantages and benefits over conventional utility meters. The wireless water meter of the present invention is operable to provide two-way communication over a wireless network to provide substantially real-time access to usage data, allow remote control and monitoring of the meter, and provide communications over a relatively large distance. The wireless water meter may also provide and maintain enough power to allow for substantially real-time access and control, rather than sporadic or periodic activity. The present invention may also provide automated or remote calibration (and enough power to do so fairly regularly) to avoid significant losses of revenue. Moreover, the present invention may allow a utility company to recognize potential emergencies through monitoring and respond to such emergencies over the wireless network and without the need to dispatch a single field technician. In addition, the present invention may facilitate automated and remote billing practices.
Because the wireless water meter may utilize plug-in wireless communications cards, the present invention may be implemented in an existing legacy environment. As a result, a user may keep the existing legacy technology in place while implementing the present invention as the water utility distribution system expands. In addition, the components of the wireless water meter of the present invention are substantially modular, allowing a user to replace or upgrade components quickly and easily, and without removing the entire meter. Other benefits will be apparent to one of ordinary skill in the relevant arts.
Although the invention has been described with reference to specific embodiments, these descriptions are not meant to be construed in a limiting sense. Various modifications of the disclosed embodiments, as well as alternative embodiments of the invention will become apparent to persons skilled in the art upon reference to the description of the invention. It should be appreciated by those skilled in the art that the conception and the specific embodiment disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present invention. It should also be realized by those skilled in the art that such equivalent constructions do not depart from the spirit and scope of the invention as set forth in the appended claims. It is therefore, contemplated that the claims will cover any such modifications or embodiments that fall within the true scope of the invention.
This application claims the benefit of U.S. Provisional Patent Application No. 60/797,540 filed May 4, 2006.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/US2007/068242 | 5/4/2007 | WO | 00 | 3/24/2009 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2007/131169 | 11/15/2007 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
3795144 | Marchesi | Mar 1974 | A |
4050301 | Cushing | Sep 1977 | A |
4237454 | Meyer | Dec 1980 | A |
4253341 | Ikeda et al. | Mar 1981 | A |
4258568 | Boetes et al. | Mar 1981 | A |
4474049 | Hansen et al. | Oct 1984 | A |
4695052 | Berkhof | Sep 1987 | A |
4940976 | Gastouniotis et al. | Jul 1990 | A |
4945754 | Wissman, Jr. et al. | Aug 1990 | A |
5056107 | Johnson et al. | Oct 1991 | A |
5187989 | Bulteau | Feb 1993 | A |
5199307 | Onoda et al. | Apr 1993 | A |
5251480 | Brunson, IV et al. | Oct 1993 | A |
5261275 | Davis | Nov 1993 | A |
5369365 | Waitman | Nov 1994 | A |
5434911 | Gray et al. | Jul 1995 | A |
5438329 | Gastouniotis et al. | Aug 1995 | A |
5451938 | Brennan, Jr. | Sep 1995 | A |
5481259 | Bane | Jan 1996 | A |
5493287 | Bane | Feb 1996 | A |
5548990 | Northedge | Aug 1996 | A |
5553094 | Johnson et al. | Sep 1996 | A |
5574229 | Castillo | Nov 1996 | A |
5594740 | LaDue | Jan 1997 | A |
5597963 | Smart et al. | Jan 1997 | A |
5659300 | Dresselhuys et al. | Aug 1997 | A |
5689540 | Stephenson et al. | Nov 1997 | A |
5714931 | Petite et al. | Feb 1998 | A |
5748104 | Argyroudis et al. | May 1998 | A |
5751797 | Saadeh | May 1998 | A |
5801643 | Williams et al. | Sep 1998 | A |
5815086 | Ivie et al. | Sep 1998 | A |
5907491 | Canada et al. | May 1999 | A |
5926103 | Petite | Jul 1999 | A |
5926531 | Petite | Jul 1999 | A |
5963146 | Johnson et al. | Oct 1999 | A |
6028522 | Petite | Feb 2000 | A |
6044062 | Brownrigg et al. | Mar 2000 | A |
6058374 | Guthrie et al. | May 2000 | A |
6060994 | Chen | May 2000 | A |
6079263 | Beddies | Jun 2000 | A |
6082169 | Bach | Jul 2000 | A |
6163276 | Irving et al. | Dec 2000 | A |
6172616 | Johnson et al. | Jan 2001 | B1 |
6191687 | Dlugos et al. | Feb 2001 | B1 |
6195018 | Ragle et al. | Feb 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 |
6288641 | Casais | Sep 2001 | B1 |
6333975 | Brunn et al. | Dec 2001 | B1 |
6351223 | DeWeerd et al. | Feb 2002 | B1 |
6373399 | Johnson et al. | Apr 2002 | B1 |
6424270 | Ali | Jul 2002 | B1 |
6430268 | Petite | Aug 2002 | B1 |
6437692 | Petite et al. | Aug 2002 | B1 |
6493377 | Schilling et al. | Dec 2002 | B2 |
6508116 | Adachi et al. | Jan 2003 | B1 |
6512463 | Campbell et al. | Jan 2003 | B1 |
6560543 | Wolfe et al. | May 2003 | B2 |
6612188 | Hamilton | Sep 2003 | B2 |
6618578 | Petite | Sep 2003 | B1 |
6618680 | Ross et al. | Sep 2003 | B2 |
6624750 | Marman et al. | Sep 2003 | B1 |
6626048 | Dam Es et al. | Sep 2003 | B1 |
6628764 | Petite | Sep 2003 | B1 |
6633781 | Lee et al. | Oct 2003 | B1 |
6650543 | Lai et al. | Nov 2003 | B2 |
6653945 | Johnson et al. | Nov 2003 | B2 |
6657552 | Belski et al. | Dec 2003 | B2 |
6677861 | Henry et al. | Jan 2004 | B1 |
6747557 | Petite et al. | Jun 2004 | B1 |
6778099 | Meyer et al. | Aug 2004 | B1 |
6836737 | Petite et al. | Dec 2004 | B2 |
6891838 | Petite et al. | May 2005 | B1 |
6914533 | Petite | Jul 2005 | B2 |
6914893 | Petite | Jul 2005 | B2 |
6931445 | Davis | Aug 2005 | B2 |
6945122 | Foss et al. | Sep 2005 | B2 |
6947854 | Swarztrauber et al. | Sep 2005 | B2 |
6954701 | Wolfe | Oct 2005 | B2 |
6980079 | Shintani et al. | Dec 2005 | B1 |
7009530 | Zigdon et al. | Mar 2006 | B2 |
7012546 | Zigdon et al. | Mar 2006 | B1 |
7053767 | Petite et al. | May 2006 | B2 |
7054271 | Brownrigg et al. | May 2006 | B2 |
7072945 | Nieminen et al. | Jul 2006 | B1 |
7079810 | Petite et al. | Jul 2006 | B2 |
7083158 | Burt et al. | Aug 2006 | B1 |
7088239 | Basinger et al. | Aug 2006 | B2 |
7089125 | Sonderegger | Aug 2006 | B2 |
7103511 | Petite | Sep 2006 | B2 |
7117051 | Landry et al. | Oct 2006 | B2 |
7124184 | Chung et al. | Oct 2006 | B2 |
7137550 | Petite | Nov 2006 | B1 |
7142107 | Kates | Nov 2006 | B2 |
7256704 | Yoon et al. | Aug 2007 | B2 |
7263073 | Petite et al. | Aug 2007 | B2 |
7295128 | Petite | Nov 2007 | B2 |
7301456 | Han | Nov 2007 | B2 |
7353280 | Chiles et al. | Apr 2008 | B2 |
7356614 | Kim et al. | Apr 2008 | B2 |
7363031 | Aisa | Apr 2008 | B1 |
7397907 | Petite | Jul 2008 | B2 |
7417557 | Osterloh et al. | Aug 2008 | B2 |
7424527 | Petite | Sep 2008 | B2 |
7443313 | Davis et al. | Oct 2008 | B2 |
7444401 | Keyghobad et al. | Oct 2008 | B1 |
7453373 | Cumeralto et al. | Nov 2008 | B2 |
7468661 | Petite et al. | Dec 2008 | B2 |
7480501 | Petite | Jan 2009 | B2 |
7526539 | Hsu | Apr 2009 | B1 |
7650425 | Davis et al. | Jan 2010 | B2 |
7697492 | Petite | Apr 2010 | B2 |
7739378 | Petite | Jun 2010 | B2 |
7752309 | Keyghobad et al. | Jul 2010 | B2 |
7756086 | Petite et al. | Jul 2010 | B2 |
7783738 | Keyghobad et al. | Aug 2010 | B2 |
7792946 | Keyghobad et al. | Sep 2010 | B2 |
7880641 | Parris et al. | Feb 2011 | B2 |
20010048030 | Sharood et al. | Dec 2001 | A1 |
20020013679 | Petite | Jan 2002 | A1 |
20020031101 | Petite et al. | Mar 2002 | A1 |
20020062392 | Nishikawa et al. | May 2002 | A1 |
20020067717 | Raschke et al. | Jun 2002 | A1 |
20020073183 | Yoon et al. | Jun 2002 | A1 |
20020083778 | Hamilton | Jul 2002 | A1 |
20020190956 | Klein et al. | Dec 2002 | A1 |
20030009515 | Lee et al. | Jan 2003 | A1 |
20030018733 | Yoon et al. | Jan 2003 | A1 |
20030018776 | Yoon et al. | Jan 2003 | A1 |
20030036810 | Petite | Feb 2003 | A1 |
20030046377 | Daum et al. | Mar 2003 | A1 |
20030074109 | Jeong et al. | Apr 2003 | A1 |
20040010561 | Kim et al. | Jan 2004 | A1 |
20040054747 | Breh et al. | Mar 2004 | A1 |
20040139210 | Lee et al. | Jul 2004 | A1 |
20040158333 | Ha et al. | Aug 2004 | A1 |
20040183687 | Petite et al. | Sep 2004 | A1 |
20050096753 | Arling et al. | May 2005 | A1 |
20050159823 | Hayes et al. | Jul 2005 | A1 |
20050195768 | Petite et al. | Sep 2005 | A1 |
20050195775 | Petite et al. | Sep 2005 | A1 |
20050201397 | Petite | Sep 2005 | A1 |
20050203647 | Landry et al. | Sep 2005 | A1 |
20060041655 | Holloway et al. | Feb 2006 | A1 |
20060098576 | Brownrigg et al. | May 2006 | A1 |
20080143109 | Pitchford et al. | Jun 2008 | A1 |
20080186898 | Petite | Aug 2008 | A1 |
20080284174 | Nagler | Nov 2008 | A1 |
20080295895 | Vincent et al. | Dec 2008 | A1 |
20090068947 | Petite | Mar 2009 | A1 |
20090215424 | Petite | Aug 2009 | A1 |
20090243840 | Petite et al. | Oct 2009 | A1 |
20100017465 | Brownrigg et al. | Jan 2010 | A1 |
20100039984 | Brownrigg | Feb 2010 | A1 |
20100194582 | Petite | Aug 2010 | A1 |
20100250054 | Petite | Sep 2010 | A1 |
20100265909 | Petite et al. | Oct 2010 | A1 |
20100312881 | Davis et al. | Dec 2010 | A1 |
Number | Date | Country |
---|---|---|
1858144 | Jan 2011 | EP |
WO 0107783 | Feb 2001 | WO |
Entry |
---|
International Search Report for PCT/GB 00/02831 mailed Jun. 1, 2000. |
Number | Date | Country | |
---|---|---|---|
20090309755 A1 | Dec 2009 | US |
Number | Date | Country | |
---|---|---|---|
60797540 | May 2006 | US |