The invention generally relates to the field of metering and metering systems. More particularly, the invention relates to verifying the proper installation, configuration, and communication connectivity of meters.
Since its infancy, meters have been used to capture usage information for billing, load survey, and other purposes. Meters have progressed from simple electromechanical devices that require human meter readers to more sophisticated electronic meters that can be equipped with remote communication options. These electronic meters typically have computer processors capable of capturing and storing more detailed data and transmitting this data over communication networks to a remote computer network. The remote computer network collects, processes, and stores this metered data to support different back-office business processes like billing, load survey, customer service, and automated meter reading (AMR) to name a few.
Although the data collection and reporting processes have evolved with the advancement in metering technologies, the meter installation process has continued to be a painstaking, labor-intensive, paper-based process rife with the potential for human error. As the metering devices have become more sophisticated with many configurable options, the back-office business processes also have increased in sophistication and complexity. The increase in complexity of both the metering devices and the back-office business processes, have combined to significantly increase the potential for human error in the labor-intensive, paper-based meter installation process. In particular, today a meter installer typically leaves the installation site without having received a positive confirmation that the meter was properly installed and correctly configured to support the desired back-office business processes. This is so, in part, because positive confirmation or verification of a proper meter installation requires the interaction of the on-site installer with an operator at the remote computer network location.
As with any segregated process, the logistics of such verification are plagued by various complications including scheduling and ownership. In particular, the on-site meter installer typically completes an installation and submits paperwork to a computer data entry operator. Days or even weeks later, the data entry operator receives the paperwork and attempts to establish communication with the meter. If the operator determines from the paperwork that either the wrong metering device was installed or the metering device was configured incorrectly, the operator must then schedule another installer to re-visit the meter site. Even if the installer is able to speak directly with the operator, for example with a portable telephone, the installer cannot visually perceive what occurs at the remote network location, nor can the operator see what occurs on-site at the meter location. This manual process is further complicated by today's era of utility deregulation that ofen divides the installation process among multiple, separate entities. For example, a utility company may own and distribute the meter, a meter service provider may install the meter, and an information service provider may operate the remote network and back-office processes.
Moreover, when the back-office business processes include automated meter reading (AMR) systems, the need for immediate, on-site verification of the meter installation increases dramatically. AMR systems must be capable of remotely communicating with the meter following the physical installation of the meter. Additionally, communication between AMR systems and individual meters may occur through many different communication media. For example, one meter may be equipped with a land-line telephone modem that requires the installer to connect the meter to a telephone line, while another meter may be equipped with a radio frequency (RF) modem that requires the installer to verify proper RF coverage at the installation site. When a meter installation includes remote communication in order to participate in an AMR system, there is an increased need to verify proper installation before leaving the site because the installation verification includes the verification of communication between the AMR system and the meter.
Therefore, a need exists to allow the on-site meter installer to be able to do at least the following: verify the meter's correct installation, ensure its proper configuration, and verify proper remote communication coverage, for example.
The invention is directed to a method and system for verifying an installation of a meter, for example, and electric power meter. The inventive method includes identifying the electric power meter to a central computer using a mobile computing device. The electric power meter receives computer-executable instructions from the central computer via the mobile computing device, and transmits meter information (e.g., power consumption readings, meter identification information, and meter location) to the central computer. The meter information received from the central computer is compared with meter information available at the electric power meter. The comparison may be accomplished visually by reading the meter and comparing the readings with the information received on the mobile computing device. Also, the comparison may be accomplished automatically by the mobile computing device based on the information it receives from the central computer and the information it receives from the electric power meter.
is a block diagram of a system for verifying the installation of a meter, according to the invention;
As shown in
On-site location 110 may be any residential, commercial, and/or industrial location such that meter 111 is installed on a customer premise to collect usage information of the customer premise. It should be appreciated that the term “on-site” is used throughout to refer to a location in close proximity to installation of meter 111, and the term “remote” is used to describe any location that may not be in close proximity to meter 111. On-site location 110 may include meter 111 and a portable, wireless computer device (PCD) 112. For example, PCD 112 may include such devices a personal digital assistant (PDA), a laptop having a wireless modem or connected to a cellular telephone, and/or a computer-capable cellular telephone, etc.
Communication network 120 may include radio frequency (RF) tower-based 122 components (e.g., using Cellular Digital Packet Data (CDPD), and/or Global System for Mobile Communications (GSM), etc.), and/or RF satellite-based 125 communications components. In addition, communication network 120 may include other types of wired or wireless networking components. The components at on-site location 110 (e.g., PCD 112) may communicate with communication network 120 using any type of communication technique including modems, wide area network/local area network (WAN/LAN) using transmission control protocol/internet protocol (TCP/IP), and/or wired communications using typical communication protocols well known to those skilled in the art. In addition, it should be appreciated that meter 111 may communicate with PCD 112 using any communication technique well known to those skilled in the art, including an optical probe 114 or some other method (e.g., wired serial connection, etc.). Also, as shown in
Remote network 130 may include one or more network servers 132 and computer databases 134. Network servers 132 and computer databases 134 may provide and store information needed to ensure the proper installation of meter 111. For example, computer databases 134 may store files (for example, meter programs, meter protocols, and meter firmware, etc.) needed by an installer of meter 111 to ensure proper installation and configuration. A computer network 131 (e.g., a WAN/LAN network), databases 134, and servers 132 communicate using typical database/server techniques, well known to those skilled in the art. It should be appreciated that computer network 131, network servers 132, and computer databases 134 may represent a plurality of computing components. For example, as discussed with reference to
The files stored in computer databases 134 may allow PCD to communicate with meter 111 (e.g., drivers), and/or files for installation and configuration of meter 111. The files stored in computer databases 134 also may include data corresponding to data collection requirements, for example, the type of data to be collected (e.g., kilowatt hours) and/or an interval of data collection (e.g., hours, days, etc.). Computer databases 134 also may include certain textual instructions that provide an installer of meter 111 with, for example, step-by-step instructions for physically installing and electronically programming meter 111. These textual instructions may be delivered to the installer's PCD 112 using a hypertext markup language (HTML) or an extensible markup language (XML), both of which are well known to those skilled in the art.
Meter 111 may be an electronic meter capable of collecting performance data and transmitting the performance data (e.g., power usage measurements) over a communication link, like that provided by optical probe 114. Also, PCD 112 may be any device capable of communicating over a communication network. For example, PCD 112 may be a laptop computer, a handheld computer (Palm™, Handspring™, etc.), and/or a wireless telephone. Communication between PCD 112 and meter 111 also may occur over a wired connection 113.
It should be appreciated that the components at on-site location 110 may receive other data communications, as well as those previously discussed. These other data communications may include, for example, data that facilitates identifying a reference location of on-site location 110. For example, as shown in
On-site location 110 is in communication with remote location 130 over a communication network 120 made up of various components, as shown in system 100. As will be discussed with reference to
Base station 122 may be a receiver/transmitter-equipped location capable of transmitting and receiving communications, for example RF communications. Also, it should be appreciated that an example of a communications satellite 125 may be a low-earth orbiting satellite system. It should be appreciated that the network components of system 100 are not exclusive, but provide one example of such a communication network that allows on-site location 110 to communicate with remote location 130. Other communication systems may include a private network, an RF network, a local area network (LAN), and/or a wide-area network (WAN).
As shown in
A communication link between remote location 130 and meter 111 is facilitated by communication network 120. In system 200, a communication network 221 may include a base station 223 and/or a satellite communication device 225. Communication network 221 provides a communication path from communication server 202, for example, to meter 111 over link 226. Once link 226 has been established, AMR server 203 and communication server 202 may operate to send and receive information from meter 111 via base station 223, satellite communication device 225, or other means including a telephone line, and/or private WAN, etc. Similarly, AMR server 203 and Web server 204 may communicate with PCD 112 via link 227 and internet/intranet 121. Therefore,
As shown in
Web servers 306a-c may provide data outside to remote network 320, for example, to a wireless network 340. Wireless network 340 may be a TCP/IP-based network capable of communicating with a pen computer 322 and/or a laptop computer 321 via wireless modems 323a and 323b, respectively. Also, pen computer 322 and laptop computer 321 may be capable of communicating with optical probes 324a-b. Optical probes 324a-b may be directed toward an optical output port on meters 331a-d so as to read data captured and stored with the meters. Web server 306c, for example, may be in communication with a communication server 316. Communication server 316 may facilitate communication between web server 306c in remote network 320 with meters 331a-d. In particular, communication server 316 may transmit and/or receive data from meters 331a and 331c via public switched telephone network (PSTN) 341. Also, communication server 316 may transmit and/or receive data from meters 331b and 331d via packet-switched network 342. In the case of meters from certain vendors (e.g., meter 331c and meter 331d) communication interfaces 343a-b may be required to communicate with the meters.
As shown in
As needed, laptop computer 321 and/or pen computer 322 download meter programs, drivers, and firmware upgrades from the remote meter database 309. It is determined in step 403 if laptop computer 321 and/or pen computer 322 require additional information to read the meter's data. If laptop computer 321 and/or pen computer 322 require additional information to read the meter's data, in step 404 the meter operates to download the additional information from meter database 309. If, on the other hand, laptop computer 321 and/or pen computer 322 have the required driver to read the meter's data, it is determined whether laptop computer 321 and/or pen computer 322 require meter configuration data (e.g., meter programs), in step 405. If laptop computer 321 and/or pen computer 322 require meter configuration data then laptop computer 321 and/or pen computer 322 request and receives the additional data in step 406. If, on the other hand, laptop computer 321 and/or pen computer 322 do not require meter configuration data, in step 407 remote network 320 transmits the necessary data to laptop computer 321 and/or pen computer 322, in step 407.
As shown in
As shown in
If, on the other hand, communication is established, the AMR system 307 adds meter 331 to AMR database 311 by sending a command to communication server 316, in step 420. The communication server establishes a connection with meter 331, and may accomplish a variety of functions including verifying meter configuration, retrieving meter data, synchronizing meter time, and returns message to AMR system 307. In step 421, AMR system 307 sends a message to laptop computer 321 and/or pen computer 322 indicating that meter 331 successfully or unsuccessfully has been added to AMR database 311. In step 422, it is determined whether the meter is installed into the system. If the meter is not installed into the system, the installer attempts to fix the problem in step 419, and perhaps reinstalls the meter in step 415.
If, on the other hand, meter 331 is determined to be properly installed into the system in step 422, the installer initiates an on-demand read of meter 331 via AMR system 307 or via another application for on-site installation verification of meter registration in step 423, as shown in FIG. 4C. In step 424, AMR system 307 transmits a success message and the read data to laptop computer 321 and/or pen computer 322. Once meter 331 has been read successfully by remote network 320, the installer verifies that meter 331 as received by AMR system 307 and read by laptop computer 321 and/or pen computer 322 are correct, in step 425. This may be accomplished either with a visual reading of the display of meter 331 and/or by laptop computer 321 and/or pen computer 322 automatically may verify the meter data with data retrieved via direct connection 324 (e.g.; optical probe, serial port, etc.) to meter 331.
The installer may then mark the installation as complete and notify the remote network's various servers (e.g., work management, billing, asset management, etc.) of completion, in step 426. Once the work order has been completed, the remote network's servers may be updated to show the new disposition of the installed meter. Once meter 331 has been correctly installed and registered within the remote network, other systems (e.g., customer service 303, billing system 305, etc.) at remote network location 320 can access the meter data via AMR system 307 and communication server 316.
This invention provides a system and method for verifying the installation of a meter. It is noted that the foregoing examples have been provided merely for the purpose of explanation and are in no way to be construed as limiting of the invention. While the invention has been described with reference to preferred embodiments, it is understood that the words that have been used herein are words of description and illustration, rather than words of limitations. Further, although the invention has been described herein with reference to particular means, materials and embodiments, the invention is not intended to be limited to the particulars disclosed herein. Rather, the invention extends to all functionally equivalent structures, methods and uses, such as are within the scope of the appended claims. Those skilled in the art, having the benefit of the teachings of this specification, may effect numerous modifications thereto and changes may be made without departing from the scope and spirit of the invention in its aspects. Those skilled in the art will appreciate that various changes and adaptations of the invention may be made in the form and details of these embodiments without departing from the true spirit and scope of the invention as defined by the following claims.
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 |
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 |
4361890 | Green, Jr. et al. | Nov 1982 | 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 |
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 |
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 | Hendrikson 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 |
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 |
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 |
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 |
5090024 | Vander Mey et al. | Feb 1992 | A |
5111479 | Akazawa | May 1992 | A |
5115448 | Mori | May 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 |
5153837 | Shaffer et al. | Oct 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 |
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äackströom 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 |
5307349 | Shloss et al. | Apr 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 |
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 |
5432507 | Mussino et al. | Jul 1995 | A |
5432815 | Kang et al. | Jul 1995 | A |
5438329 | Gastouniotis et al. | Aug 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 |
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 |
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 |
5522044 | Pascucci et al. | May 1996 | A |
B 4749992 | Fitzmeyer et al. | Jun 1996 | |
5526389 | Buell et al. | Jun 1996 | A |
5528507 | McNamara et al. | Jun 1996 | A |
5528597 | Gerszberg et al. | Jun 1996 | A |
5535267 | Schull | Jul 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 |
5619685 | Schiavone | Apr 1997 | A |
5621629 | Hemminger et al. | 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 |
5680456 | Baker et al. | Oct 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 |
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 |
5751914 | Coley et al. | May 1998 | A |
5751961 | Smyk | May 1998 | A |
5754772 | Leaf | May 1998 | A |
5754830 | Butts et al. | May 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 |
5805712 | Davis | Sep 1998 | A |
5808558 | Meek et al. | Sep 1998 | A |
5822521 | Gartner et al. | Oct 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 |
5897607 | Jenney et al. | Apr 1999 | A |
5898387 | Davis et al. | Apr 1999 | A |
5910799 | Carpenter et al. | Jun 1999 | A |
5943375 | Veintimilla | Aug 1999 | A |
5963146 | Johnson et al. | Oct 1999 | A |
6000034 | Lightbody et al. | Dec 1999 | A |
6041056 | Bigham et al. | Mar 2000 | A |
6067029 | Durston | May 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 |
6100817 | Mason, Jr. et al. | Aug 2000 | A |
6112192 | Capek | Aug 2000 | A |
6150955 | Tracy et al. | Nov 2000 | A |
6160993 | Wilson | Dec 2000 | A |
6172616 | Johnson et al. | Jan 2001 | B1 |
6199068 | Carpenter | Mar 2001 | B1 |
6246677 | Nap et al. | Jun 2001 | B1 |
6351223 | DeWeerd et al. | Feb 2002 | B1 |
6785592 | Smith et al. | Aug 2004 | B1 |
Number | Date | Country |
---|---|---|
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 |
2 222 898 | Mar 1990 | GB |
2 237 910 | May 1991 | GB |
59-229949 | Dec 1984 | 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 |