Suche Bilder Maps Play YouTube News Gmail Drive Mehr »
Anmelden
Nutzer von Screenreadern: Klicke auf diesen Link, um die Bedienungshilfen zu aktivieren. Dieser Modus bietet die gleichen Grundfunktionen, funktioniert aber besser mit deinem Reader.

Patentsuche

  1. Erweiterte Patentsuche
VeröffentlichungsnummerUS20040113810 A1
PublikationstypAnmeldung
AnmeldenummerUS 10/185,074
Veröffentlichungsdatum17. Juni 2004
Eingetragen28. Juni 2002
Prioritätsdatum28. Juni 2002
Auch veröffentlicht unterCA2491412A1, CA2491412C, US7312721, US20060071812, WO2004003772A1
Veröffentlichungsnummer10185074, 185074, US 2004/0113810 A1, US 2004/113810 A1, US 20040113810 A1, US 20040113810A1, US 2004113810 A1, US 2004113810A1, US-A1-20040113810, US-A1-2004113810, US2004/0113810A1, US2004/113810A1, US20040113810 A1, US20040113810A1, US2004113810 A1, US2004113810A1
ErfinderRobert Mason, Eugene Hodges, Kathryn Smith, Andrew Borleske
Ursprünglich BevollmächtigterMason Robert T., Hodges Eugene W., Smith Kathryn J., Borleske Andrew J.
Zitat exportierenBiBTeX, EndNote, RefMan
Externe Links: USPTO, USPTO-Zuordnung, Espacenet
Data collector for an automated meter reading system
US 20040113810 A1
Zusammenfassung
The invention includes an electronic utility meter, a data collector/meter and a method for communicating data in an automated meter reading system. The inventive method includes communicating data with a network and a first electronic utility meter, and communicating the data with the first electronic utility meter and one or more other meters.
Bilder(8)
Previous page
Next page
Ansprüche(60)
What is claimed is:
1. An electronic utility meter, comprising:
a first port for communicating data with one or more other electronic meters;
a second port for communicating data with a network;
a transceiver in communication with the first port and the second port, wherein the transceiver communicates data between the other electronic meter and the computer; and
a computer in communication with the transceiver.
2. The meter of claim 1, wherein the electronic utility meter is at least one of the following: a gas meter, a water meter, and an electric power meter.
3. The meter of claim 1, wherein the network comprises a central computer at a utility in communication with a billing system.
4. The meter of claim 1, wherein the data is communicated as a function of predetermined criteria.
5. The meter of claim 4, wherein the predetermined criteria filter the data provided by the electronic utility meter to the other meters.
6. The meter of claim 1, wherein the transceiver routes the data from the network to the other meters.
7. The meter of claim 1, further comprising a data storage device for data received from the other meters and from the network.
8. The meter of claim 7, wherein the data storage device provides the stored data to the network when requested by the network.
9. The meter of claim 7, wherein the data storage device provides the stored data to the other meters when requested by the network.
10. The meter of claim 1, wherein the computer provides timing data to the other meters.
11. The meter of claim 10, wherein the timing data is transmitted to the other meters at a substantially similar time.
12. The meter of claim 10, wherein the timing data is transmitted to the other meters at different times.
13. The meter of claim 1, wherein the data comprises at least one of the following: time-of-use data and demand data.
14. The meter of claim 1, wherein the communication between the electronic utility meter and the other meters is accomplished via wireless techniques.
15. The meter of claim 1, wherein the communication between the electronic utility meter and the other meters is accomplished via wired techniques.
16. The meter of claim 1, wherein the communication between the electronic utility meter and the network is accomplished via wireless techniques.
17. The meter of claim 1, wherein the communication between the electronic utility meter and the network is accomplished via wired techniques.
18. The meter of claim 1, wherein the communication between the electronic utility meter and the other meters is accomplished using at least one of the following techniques: TCP/IP, Internet, electronic messaging, XML, digital encryption, digital signature, Ethernet, DSL, Cable Modem, 802.11, Bluetooth, and X10.
19. The meter of claim 1, wherein the communication between the electronic utility meter and the computer is accomplished using at least one of the following techniques: TCP/IP, Internet, electronic messaging, XML, digital encryption, digital signature, Ethernet, DSL, Cable Modem, 802.11, Bluetooth, and X10.
20. The meter of claim 1, further comprising receiving a query from a customer premise to the electronic utility meter via the other meter.
21. The meter of claim 20, wherein the customer premise provides the query to the electronic utility meter using access identification.
22. The meter of claim 1, wherein the data represents utility usage.
23. The meter of claim 22, wherein the utility includes at least one of the following: water, gas, and electricity.
24. The meter of claim 22, wherein the utility usage is determined over a billing period.
25. The meter of claim 24, wherein the billing period represents one or more days.
26. The meter of claim 24, wherein the billing period represents a season of the year.
27. The meter of claim 1, wherein the data represents a billing rate to be applied to utility usage.
28. The meter of claim 27, wherein the billing rate is provided for one or more days.
29. The meter of claim 27, wherein the billing rate is provided for a season of the year.
30. The meter of claim 1, further comprising communicating a demand reset request from the electronic utility to the other meters at a predetermined interval.
31. The meter of claim 30, wherein the predetermined interval is at least one of the following: a billing change date, and a season change date.
32. The meter of claim 30, further comprising continuously verifying that the demand reset was accomplished in the other meters.
33. The meter of claim 1, wherein the electronic utility meter transmits identification designations to the other meters.
34. The meter of claim 1, wherein the electronic utility meter transmits time-of-use designations to the other meters.
35. The meter of claim 34, wherein the electronic utility meter transmits time-of-use schedules to the other meters as a function of the time-of-use designations.
36. The meter of claim 1, wherein the electronic utility meter registers the other meters such that data is not lost.
37. The meter of claim 1, wherein the electronic utility meter receives load profile data from the other meters.
38. The meter of claim 37, wherein receiving the load profile data is a function of at least one of the following predetermined criteria: the quantity of load profile data, a time of the day, a day of the year, and a season of the year.
39. A method for communicating data in an automated meter reading system, comprising:
communicating data with a network and a first electronic utility meter; and
communicating the data with the first electronic utility meter and one or more other meters.
40. The method of claim 39, further comprising communicating the data as a function of predetermined criteria.
41. The method of claim 40, wherein the predetermined criteria filter the data provided by the first meter to the other meters.
42. The method of claim 39, further comprising routing data from the network to the other meters via the first meter.
43. The method of claim 39, further comprising storing the data in the first meter received from the other meters.
44. The method of claim 43, further comprising providing the stored data to the network when requested by the network.
45. The method of claim 39, further comprising the first meter providing timing data to the other meters.
46. The method of claim 45, wherein the timing data is transmitted to the other meters by the first meter at a substantially similar time.
47. The method of claim 45, wherein the timing data is transmitted to the other meters at distinct times.
48. The method of claim 39, further comprising receiving a query from a customer premise to the first meter via the other meter.
49. The method of claim 48, wherein the customer premise provides the query to the first meter using access identification.
50. The method of claim 39, wherein the data represents utility usage.
51. The method of claim 39, wherein the data represents a billing rate to be applied to utility usage.
52. The method of claim 39, further comprising communicating a demand reset request from the first meter to the other meters at a predetermined interval.
53. The method of claim 52, wherein the predetermined interval is at least one of the following: a billing change date, a season change date.
54. The method of claim 52, further comprising continuously verifying that the demand reset was accomplished in the other meters.
55. The method of claim 39, further comprising the first meter assigning identification designations to the other meters.
56. The method of claim 39, further comprising the first meter assigning time-of-use designations to the other meters.
57. The method of claim 56, further comprising the first meter assigning time-of-use schedules to the other meters as a function of the time-of-use designations.
58. The method of claim 39, further comprising the first meter registering the other meters such that data is not lost.
59. The method of claim 39, further comprising the first meter receiving load profile data from the other meters.
60. A data collector device, comprising:
a first port for communicating data with one or more other electronic meters;
a second port for communicating data with a network;
a transceiver in communication with the first port and the second port, wherein the transceiver communicates data between the other electronic meter and the computer; and
a computer in communication with the transceiver, wherein the computer routes the data from the network to the electronic meter.
Beschreibung
    CROSS-REFERENCE TO RELATED APPLICATIONS
  • [0001]
    The present application is related to U.S. patent application Ser. No. ______ (Attorney Docket No. ABME-0796), filed Jun. 27, 2002, and entitled “Dynamic Self-Configuring Metering Network,” which is incorporated herein by reference.
  • TECHNICAL FIELD
  • [0002]
    The invention relates to the field of service meters. More specifically, the invention relates to a data collector for an automated meter reading system.
  • BACKGROUND OF THE INVENTION
  • [0003]
    Since its infancy, the electric power industry has used electromechanical meters to capture power usage. Similarly, electromechanical meters have been used for water and gas usage. In the context of electric power meters, the electromechanical meters collected little more than total power usage. Also, the electric power meters required human meter readers to travel to the millions of customer premises in order to read the usage totals captured by the meters. Over time, electromechanical meters began to be replaced by electronic meters.
  • [0004]
    Electronic meters have computer processing components that allow the meters to capture more data in an intelligent way. For example, today's meters are able to ascertain periodic usage (e.g., which time of day is more power used) or demand determinations (e.g., the peak power), power quality, and power factor considerations. In addition to capturing more data, electronic meters also are able to communicate the more detailed data to the utility over telephone lines or over wireless networks. In fact, the communication sophistication of today's meters is nearly limitless. For example, today's high cost meters are able to communicate directly with a utility's central computing system over fixed communication networks.
  • [0005]
    Although fixed communication networks provide a sophisticated and reliable communication network, they also require a complex and costly infrastructure. For example, a fixed wireless communication system often requires the installation of pole or roof mounted repeaters or gateways. Such equipment, while important to the reliability of the communication system, creates additional equipment and installation efforts. In addition, the fixed wireless communication systems require a higher cost meter so as to communicate directly with the utility's central server. As a result, AMR systems that rely on the sophisticated meters and fixed wireless networks have become cost prohibitive.
  • [0006]
    Therefore, there is a need to employ more low cost electronic meters, while maintaining the communication and networking capabilities of today's AMR systems.
  • SUMMARY OF THE INVENTION
  • [0007]
    The invention includes an electronic utility meter, a data collector/meter and a method for communicating data in an automated meter reading system. The inventive method includes communicating data with a network and a first electronic utility meter, and communicating the data with the first electronic utility meter and one or more other meters.
  • [0008]
    The inventive data collector/meter includes a first port for communicating data with one or more other electronic meters, a second port for communicating data with a network, and a transceiver in communication with the first port and the second port. The transceiver communicates data between the other electronic meter and the computer. Also, the inventive device includes a computer in communication with the transceiver. The electronic utility meter may be a gas meter, a water meter, and an electric power meter. Also, the network may include a central computer at a utility in communication with a billing system. The data may be communicated as a function of predetermined criteria that filters the data provided by the electronic utility meter to the other meters. The transceiver routes the data from the network to the other meters. The meter may include a data storage device for data received from the other meters and from the network. The data storage device may provide the stored data to the network when requested by the network, and may provide the stored data to the other meters when requested by the network. Also, the computer may provide timing data to the other meters, where the timing data is transmitted to the other meters at a substantially similar time and/or at different times. The data comprises at least one of the following: time-of-use data and demand data. The communication between the electronic utility meter and the other meters may be accomplished via wireless and/or wired techniques. Similarly, the communication between the electronic utility meter and the network may be accomplished via wireless and/or wired techniques. The communication between the electronic utility meter and the other meters is accomplished using at least one of the following techniques: TCP/IP, Internet, electronic messaging, XML, digital encryption, digital signature, Ethernet, DSL, Cable Modem, 802.11, Bluetooth, and X10, for example. Also, the meter may receive a query from a customer premise to the electronic utility meter via the other meter. The meter may communicate a demand reset request from the electronic utility to the other meters at a predetermined interval, where the predetermined interval is at least one of the following: a billing change date, and a season change date.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0009]
    Other features of the invention are further apparent from the following detailed description of the embodiments of the invention taken in conjunction with the accompanying drawings, of which:
  • [0010]
    [0010]FIG. 1 is a block diagram of an automated meter reading system, according to the invention;
  • [0011]
    [0011]FIG. 2 is a block diagram of a data collector/meter, according to the invention;
  • [0012]
    [0012]FIG. 3 is a flow diagram of a method of selling access to data captured by the power meter on the Internet, according to the invention;
  • [0013]
    [0013]FIG. 4 provides an example of a load profile table, according to the invention;
  • [0014]
    [0014]FIG. 5 provides an example of a computing system, according to the invention;
  • [0015]
    [0015]FIG. 6 illustrates an example of a network environment, with a server computer in communication with client computers via a communications network, in which the invention may be employed; and
  • [0016]
    [0016]FIG. 7 provides one example of the components that may be included with a LAN Option Board, according to the invention.
  • DETAILED DESCRIPTION OF THE INVENTION
  • [0017]
    Automated Meter Reading System
  • [0018]
    [0018]FIG. 1 is a block diagram of an automated meter reading system 100 for processing data that is captured by an electric power meter. Although FIG. 1 is discussed with reference to an electric power meter, it should be appreciated that the invention applies equally to other meters and other systems. For example, FIG. 1 also may have been described in the context of a gas meter system, or a water meter system, or other similar system. Accordingly, the invention is not limited by the example embodiment described with reference to FIG. 1.
  • [0019]
    System 100 includes a remote location 110 in communication with an on-site location 120. On-site location 120 also is in communication with on-site locations 130 and 140. Remote location 110 includes equipment capable of processing and centrally serving AMR system 100. In particular, remote location 110 may include computer servers 111 in communication with a network 112, which is further in communication with databases 113. Although other components may be included at remote location 110, the components depicted in FIG. 1 have been shown for the purposes of clarity and brevity. Generally, remote location 110 may be located within a utility's organization, and may be capable of processing the usage data collected at on-site locations 120, 130 and 140. As such, remote location may include equipment capable of providing information related to billing for the use of electric power at on-site locations 120, 130 and 140.
  • [0020]
    On-site location 130 includes a meter 131 and on-site location 140 includes a meter 141. Meters 131 and 141 collect electrical power usage at on-site locations 130 and 140, respectively. For example, on-site locations 130 and 140 may be residential customer premise locations, and meters 131 and 141 may collect the electrical power used by the customer premises. Meters 131 and 141 may be single phase or three phase electrical or electronic meters. For example, meters 131 and 141 may be an A3 Alpha meter modified to communicate with data collector/meter 121 wirelessly or otherwise (e.g., 900 MHz radio) and manufactured by ABB Inc. Although just two meters are shown in FIG. 1, it should be appreciated that any number of meters may be in communication with data collector/meter 121. Also, although just one data collector/meter 121 is shown in FIG. 1, it should be appreciated that there may be any number of such collectors in communication with remote location 110. Furthermore, although the description focuses on the interaction with meter 131, it should be understood that all such discussion applies equally to meter 141, or any other meters in communication with data collector/meter 121.
  • [0021]
    Data collector/meter 121 may be responsible for reading and storing billing data from meter 131 and similar meters. As is described in detail U.S. patent application Ser. No. ______ (Attorney Docket No. ABME-0796), filed Jun. 27, 2002, and entitled “Dynamic Self-Configuring Metering Network,” which is incorporated herein by reference, meter 131 registers with collector 121. Once meter 131 is registered to collector 131, collector 121 may then be responsible for reading current billing data from meter 131 and storing the billing data in a database (not shown) located within data collector/meter 121. Such data reads may be accomplished intermittently, continually (e.g., every 4 hours), or as a function of available network resources (e.g., during minimum data traffic times).
  • [0022]
    Data collector/meter 121 also may be responsible for knowing the billing date for meter 131. Data collector/meter 121 may then notify meter 131 as to when to store a copy of the current billing data and when to reset or clear its data. For example, data collector/meter 121 may notify meter 131 to store a copy of its billing data at midnight of the billing date. Data collector/meter 131 may then notify meter 131 to conduct a reset demand and to start the next billing cycle. When data collector/meter 121 reads the data on the particular billing date, the data is stored within data collector/meter 121. For example, data collector/meter 121 may store the data in a storage device called “Previous Billing Data Table” located in data collector/meter 121. Data collector/meter 121 also may be responsible for notifying meter 131 of a particular TOU schedule to be used by meter 131 and of notifying meter 131 of any TOU season changes. Season change dates are similar to billing dates in that data collector/meter 121 notifies meter 131 to store a copy of the current data, and to conduct a reset demand. Data collector/meter 121 may then read this season change copy of data and store it in a data location within data collector/meter 121 called “Previous Season Data Table.”
  • [0023]
    As meters 131 and 141 collect electric power usage data, the data may be stored within meters 131 and 141, and/or may be communicated with data collector/meter 121 at on-site location 120. As will be discussed in greater detail, the communication of the data from meters 131 and 141 to data collector/meter 121 may be accomplished immediately, or after some predetermined time period depending upon certain circumstances like the type of data to be communicated, the availability of the communication link, the time of day, and the time of year, etc.
  • [0024]
    Data may be communicated between meter 131 and data collector/meter 121 over communication link 105. Similarly, data may be communicated between meter 141 and data collector/meter 121 over communication link 106. Data provided to and collected at data collector/meter 121 from meters 131 and 141 may then be provided to remote location 110 over communication link 104. Also, although not shown with reference to FIG. 2, it should be appreciated that meter 131 and meter 141 may communicate directly with one another, and that data collector/meter 121 may communicate to meter 131 through meter 141, using meter 141 as a repeater.
  • [0025]
    Communication links 104-106 may be wireless or wired links. For example, it may be desirable to provide low cost wireless communication techniques for communication links 105 and 106, as on-site locations 120, 130, and 140 tend to be in relatively closer proximity to each other. Also, for example, it may be desirable to provide a wired communication technique for communication link 104, as remote location 110 tends to be a relatively greater distance from on-site location 120 with data collector/meter 121. Because the availability of on-site location 120 with data collector/meter 121 limits the number of longer distance links with remote location 110, the often more reliable wired communication techniques may be a cost effective solution for communication link 104. However, it should be appreciated that the invention contemplates communication links 104-106 being either wired or wireless in any combination. For example, communication links 104-106 are not limited to any network configuration, but may include any of the following techniques: Local Area Network (LAN), Wide Area Network (WAN), Ethernet, Digital Subscriber Lines (DSL), and/or coaxial cable network, for example. In addition, communication links 104-106 may employ secure communication methods including, for example, digital encryption and/or digital signature techniques well known to those skilled in the art.
  • [0026]
    Also, it should be appreciated that the formatting of the communicated data over communication links 104-106 may be in any desirable format including transmission control protocol/internet protocol (TCP/IP), electronic messaging format, extensible markup language (XML), Institute of Electrical/Electronic Engineers (IEEE) Standard 802.11, Bluetooth™, and X10™, and ANSI C12.21 Remote Communication Protocol, for example, to communicate data between data collector/meter 121 and remote location 110.
  • [0027]
    Data Collector/Meter
  • [0028]
    Data collector/meter 121 may be an A3 Alpha™ meter available from ABB Inc. The A3 Alpha™ meter may be modified to include one or more network communication option boards including a WAN option board for communication link 104 and a LAN Option Board (LANOB) for communication links 105, 106, etc. An example embodiment may use a Plain Old Telephone Service (POTs) modem option board for the wired WAN and a 900 MHz radio option board for the wireless LAN.
  • [0029]
    By serving as a central point of communication between remote location 110 and any number of on-site locations 130 and 140, data collector/meter 121 serves to reduce the overall complexity and corresponding cost of AMR system 100. For example, the ability of data collector/meter 121 to act as a gateway between remote location 110 and on-site locations 130 and 140, while data collector/meter 121 retains its operation as an electrical power meter, reduces the need for additional networking equipment. Also, because data collector/meter 121 centralizes some of the intelligence and functionality found in higher cost meters, meters 131 and 141 may be lower cost meters capable of engaging in two-way communication with data collector/meter 121.
  • [0030]
    [0030]FIG. 2 provides a block diagram further detailing one example of a data collector/meter 121. Although certain components are designated and discussed with reference to FIG. 2, it should be appreciated that the invention is not limited to such components. In fact, various other components typically found in an electronic meter will be a part of data collector/meter 121, but have not been shown in FIG. 2 for the purposes of clarity and brevity. Also, the invention may use other components to accomplish the operation (as will be discussed) of data collector/meter 121. The components that are shown and the functionality described for data collector/meter 121 are provided as examples, and are not meant to be exclusive of other components or other functionality.
  • [0031]
    As shown in FIG. 2, data collector/meter 121 may include a meter 210 (e.g., an A3 Alpha™ meter available from ABB Inc.) a WAN Option Board 220 (e.g., a telephone modem) and a LAN Option Board 230 (e.g., a 900 MHz radio). WAN Option board 220 routes messages from network 112 (via interface port 202) to either meter 210 or LAN Option Board 230. LAN Option Board 230 may use a transceiver (not shown), for example a 900 MHz radio, to communicate data to meter 131. Also, LAN Option Board 230 may have sufficient memory to store data from meter 131. This data may include, but is not limited to the following: current billing data (e.g., the present values stored and displayed by meter 131), previous billing period data, previous season data, and load profile data.
  • [0032]
    LAN Option Board 230 also may communicate via a wired interface (e.g., RS232) to meter 210. LAN Option Board 230 may be capable of synchronizing its time to a real time clock (not shown) in meter 210 and thereby synchronize the LAN reference time to the time in meter 210. The communication interfaces and the collection and storage of metering data are handled by a computer (not shown) within data collector/meter 121. The computer may include various other components (not shown) including programmable computer memory, databases, timing components (e.g., quartz crystals), application specific (ASIC) hardware circuits, network interface cards, and computer firmware, for example. Generally, the computer includes any computer hardware, software, or firmware needed to satisfy the operation of data collector/meter 121 in AMR system 100.
  • [0033]
    [0033]FIG. 7 provides one example of the components that may be included with LAN Option Board 230. However, FIG. 7 is not meant to be an exclusive representation of such components or their configurations.
  • [0034]
    The responsibility of data collector/meter 121 in AMR system 100 is wide and varied. Generally, data collector/meter 121 is responsible for managing, processing and routing data communicated with remote location 110 and on-site locations 130 and 140.
  • [0035]
    Data collector/meter 121 reads usage data from meter 131 via interface port 201. Meter 131 is generally a less complex device than data collector/meter 121. In order to reduce the cost of AMR system 100, meter 131 may have a computer with equal or less functionality as the computer in data collector/meter 121. In order to provide two-way communication with data collector/meter 121, meter 131 may have a transceiver device similar to the transceiver in data collector/meter 121.
  • [0036]
    Usage data gathered by meter 131 may be stored within meter 131, or it may be provided immediately to data collector/meter 121. Meter 131 typically has limited storage capacity, and therefore may rely on data collector/meter 121 to periodically read the data before it is overwritten. Meter 131 may store and display the current energy consumption (kWh). Meter 131 also may display the TOU energy consumption and the current peak demand for the billing period. In addition to this current data, meter 131 may store a copy of this data taken at a critical interval, such as the monthly billing date or a season change date.
  • [0037]
    Data collector/meter 121 may continually or intermittently read the current data from meter 131 and store the data in a database (not shown) in data collector/meter 121. Such current data may include but is not limited to the total kWh usage, the TOU kWh usage, the peak kW demand, and other status information from meter 131. Data collector/meter 121 also may read and store previous billing and previous season data from meter 131 and store the data in the database in data collector/meter 121. Meter 131 may store a smaller quantity of load profile data (e.g, 24 hours of 15 minute data). Data collector/meter 121 may read this data and store several days of profile data, for example, that otherwise may not be able to be stored in the limited memory of meter 131. Whether data collector/meter 121 reads previous billing, previous season, or load profile data from meter 131 is configurable and may vary. Accordingly, the invention is not limited to reading this or any other type of data over any particular interval. When data collector/meter 121 is configured to read and store load profile data, the amount of data stored in data collector/meter 121 is configurable and may vary.
  • [0038]
    It is well known to those skilled in the art that electrical energy consumption may be measured in any number of ways including: TOU and demand-based reading. TOU-based usage reading refers to the notion of time-stamping the usage of electricity, such that a utility may bill a premium for power used at certain times of the day or year, as compared to other times. For example, in the summer, peak electric power usage times traditionally occur during the late afternoon. Therefore, meter 131 may be equipped to measure the amount of electric power used during these intervals, so that the power usage may be billed differently (and perhaps higher) than at other time intervals.
  • [0039]
    Demand-based usage readings determine peak power usages for a particular customer. For example, a demand-based usage reading may allow a utility to bill a premium for a customer that uses 20 kWh in a one hour time span, as compared to another customer that uses 20 kWh in a twenty-four hour time span. Because such concentrated electric power usage taxes the utility's power generation plants and distribution system, the customer may be billed at a higher rate.
  • [0040]
    AMR system 100 may be designed to permit meter 131 to measure usage based on these specific types of usage techniques, for example. Also, data collector/meter 121 may be able to configure meter 131 with specific instructions to accomplish such usage reading techniques. For example, data collector/meter 121 may be designed to instruct meter 131 as to a particular time interval that demand-based data should be captured. When meter 131 is registered with data collector/meter 121, computer servers 111 assign meter 131 to a billing identifier, where the billing identifier defines the billing date for meter 131. Data collector/meter 121 also is programmed by computer server 111 with a calendar of billing dates for each billing identification. It may be the responsibility of data collector/meter 121 to notify meter 131 to store a copy of the current billing data and reset the peak demand at a certain time (e.g., midnight) of the billing date. This process is described in more detail in the following paragraphs.
  • [0041]
    At a defined time interval (e.g., midnight crossing), data collector/meter 121 checks if the billing date for meter 131 is to occur at the next interval. For example, if the billing date is at the midnight crossing of Jun. 1, 2002, data collector/meter 121 checks to ensure that meter 131 is to perform a demand reset on Jun. 2, 2002. If data collector/meter 121 determines that a billing date should occur within an upcoming period (e.g., within the next 24 hours), data collector/meter 121 provides a message to meter 131 to “arm” and to perform a demand reset at the next midnight crossing (e.g., Jun. 2, 2002). When this midnight crossing occurs, meter 131 stores a copy of the current billing data, increments a demand reset count, where the demand reset count is used to identify the specific instance of billing data. Data collector/meter 121 then resets the current billing data demand value (kW) to start a new billing cycle. After the midnight crossing occurs, data collector/meter 121 reads the billing data copy stored in meter 131 so that it is readily available for retrieval by remote location 110.
  • [0042]
    Because meter 131 does not typically have a real time clock, if meter 131 were to lose power between the time that it is armed to perform the demand reset and the midnight crossing, it is possible that meter 131 would not properly perform the demand reset at midnight. In addition to reading the billing data copy from meter 131, data collector/meter 121 may continually read the current billing data from meter 131. After meter 131 's billing date has occurred, data collector/meter 121 will insure that meter 131 has properly performed a demand reset setting information in the read message that forces meter 131 to perform a demand reset. This is illustrated by the following example.
  • [0043]
    On Jun. 1, 2002, the demand reset count in meter 131 is 12. Data collector/meter 121 recognizes that meter 131 should perform a demand reset at midnight Jun. 2, 2002, and sends information in the read command to “arm” meter 131 to perform the demand reset. At midnight on Jun. 2, 2002, meter 131 stores a copy of the current billing data, increments the demand reset count to 13 and resets the current peak demand. Subsequent reads from data collector/meter 121 instruct meter 131 to perform a demand reset if the demand reset count in meter 131 is not equal to 13. Since the demand reset count is already equal to 13, meter 131 does not perform another demand reset. However, if meter 131 had missed the midnight crossing due to a power loss, the message from data collector/meter 121 would force meter 131 to immediately store a copy of the billing data and reset demand.
  • [0044]
    Also, data collector/meter 121 can inform meter 131 of upcoming events, such as day type, season type, etc. In particular, data collector/meter 121 may let meter 131 know if a day type (e.g., holiday) change or season change is upcoming, so as to prevent meter 131 from placing the data in the incorrect billing tier.
  • [0045]
    With respect to certain TOU-based data collection techniques, data collector/meter 121 may be capable of instructing meter 131 with certain information to facilitate such readings. Meter 131 stores TOU switchpoints for a weekday schedule, a weekend schedule, and two holiday schedules. Data collector/meter 121 is responsible for sending these schedules to meter 131 and updating the schedules when required by time of year changes or emergency conditions. For example, during a change of season (i.e., a time of the year when usage rates are adjusted), data collector/meter 121 may send messages to meter 131 to update the weekday, weekend and holiday switchpoints that define the TOU schedule for the new season.
  • [0046]
    Similar to the handling of billing dates, data collector/meter 121 has a calendar that defines the season change dates for each TOU identifier, where each meter in the system may be defined to one of several (e.g., 5) TOU identifiers. Data collector/meter 121 checks for season changes in advance (e.g., one day) and typically instructs meter 131 to perform a billing data copy and demand reset some time prior to (e.g., at midnight) the billing date. In addition to handling the demand reset as is done for the billing date, data collector/meter 121 reads the billing data copy from meter 131 and stores it in data collector/meter 121 (e.g., Previous Season Data Table). Data collector/meter 121 may then send messages to meter 131 (e.g., broadcast to all meters associated with the TOU Id) to update the TOU schedules per the new season.
  • [0047]
    The updating of TOU schedules on season changes events may be accomplished using unicast (i.e., directed to a particular meter) or broadcast techniques (i.e., directed to all of the meters served by the collector).
  • [0048]
    TOU schedules may be provided by data collector/meter 121 using any number of techniques. For example, data collector/meter 121 may “broadcast” TOU schedules to each of the meters it serves. The TOU schedules may be broadcast along with the standard network reference time signal, discussed above. As such, the TOU schedules may be broadcast intermittently or continuously, as desired by the network configuration. When a new meter enters AMR system 100, data collector/meter 121 may send the new meter a default TOU schedule. Transmission of the TOU schedule to the new meter may be accomplished using individual or broadcast transmission, or both.
  • [0049]
    Data collector/meter 121 also is responsible for communicating any change of a meter's identification information (e.g., billing identification or TOU identification). For example, if remote location 110 changes a TOU identification that is assigned to meter 131, data collector/meter 121 will conduct a registration procedure (as discussed with reference to FIG. 3) to update the storage in meter 131 that defines the TOU identification.
  • [0050]
    Generally, although data collector/meter 121 receives the pertinent usage data from meter 131, data collector/meter 121 may not be required to interpret or process such data. In the interest of simplifying data collector/meter 121, certain intelligence and functionality may be placed within the components at remote location 110 (e.g., computer servers 111). For example, data collector/meter 121 may identify data from meter 131 to remote location 110 with a certain alphanumeric code that is understood at remote location 110. Similarly, meter 131 may have multiple data sets, each with a unique identification code provided by data collector/meter 121. In this way, remote location 110 may be responsible for collating and processing the usage data, and data collector/meter 121 may just be responsible for routing the data from meter 131 with the proper identifier. Alternatively, data collector/meter 121 is not so limited, and may accomplish some data interpretation as is necessary.
  • [0051]
    One particular operation that may be accomplished by data collector/meter 121 is the maintenance, synchronization, and distribution of network time references. Lower cost meters, like meter 131, may not be equipped with a real time clock. As a result, when meter 131 loses power, it will lose its network time reference when power returns. Therefore, data collector/meter 121 may provide network time references to meter 131. In this way, data collector/meter 121 ensures that meter 131 (and any other meters served by data collector/meter 121—e.g., meter 141) is operating on a proper time reference. As described above, for TOU and demand-based usage measurements, having meter 131 operate on a particular standard time reference ensures that power usage will be billed properly and in accordance with predetermined time-based billing rates.
  • [0052]
    Providing the proper time standard at the point of data collection (i.e., meter 131), instead of at another point in AMR system 100 (e.g., remote location 110) provides greater synchronization between when a particular quantity of energy was used. Also, allowing data collector/meter 121 to distribute and synchronize time to meter 131 limits the dependence on the often unreliable communication links from remote location 110 to meter 131. In this way, AMR system 100 provides an added level of assurance that a certain quantity of energy was used during the designated time interval; a correlation that is significant to the operation of TOU and demand-based usage measurement techniques. Also, distributing the time reference from data collector/meter 121 to meter 131 provides additional reliability due to the closer proximity of data collector/meter 121 to meter 131.
  • [0053]
    In order to facilitate allowing data collector/meter 121 to communicate the proper time reference to each of the meters it servers (e.g., meter 131 and 141), a “broadcast” transmission technique may be employed. The broadcast technique refers to allowing data collector/meter 121 to transmit one time signal to all of the meters that it serves. Where communication links 105 and 106 are wireless, for example, data collector/meter 121 may simply transmit one wireless signal to meters 131 and 141. The time reference signal may be sent at certain intervals (e.g., hourly, daily) or continuously to ensure that the meters served by data collector/meter 121 receive the time reference signal.
  • [0054]
    Data collector/meter 121 may be responsible for registering and identifying particular meters on AMR system 100. Such registration may occur, for example, when a new meter is added to AMR system 100, when a new collector is added, and/or when an existing meter determines that it will be best served by another (perhaps closer in proximity) collector. In fact, in maintaining AMR system 100, data collector/meter 121 allows meters 131 and 141 to switch from data collector/meter 121 to a different collector (not shown). In order to ensure that data is not lost during the collector transition, both data collector/meter 121 and the new collector may retrieve information from the switching meter, as will be discussed. Also, the old collector (i.e., the collector from which the meter has transitioned) will store the data from the meter before it switches to the new collector. Such data may be stored in a table called “Old Node Data Log.” By storing the data in such a log, the system is ensured of collecting the data from the switching meter, in case the data is lost when the meter switches to the new collector.
  • [0055]
    [0055]FIG. 3 provides a flow diagram describing the method by which data collector/meter 121 registers meter 131. In step 301, data collector/meter 121 finds and registers meter 131 and reads the TOU Id from meter 131. When initially installed, meter 131 will have a default TOU Id. If meter 131 had previously been registered to a different collector, the TOU Id read by data collector/meter 121 would be the id assigned by the old data collector/meter. In step 302, data collector/meter 121 updates its internal data tables to list meter 131 and assign it to the TOU Id read from meter 131. In step 303, data collector/meter 121 reads the previous billing data from meter 131 and stores the data in data collector/meter 121. For example, data may be stored in a “Previous Billing Data Table” and a “Previous Season Data Table.” In step 304, data collector/meter 121 may make an exception call to remote location 110 to inform computer servers 111 indicating that it has registered a new meter (e.g., meter 131). In step 305, remote location 110 assigns meter 131 to a billing id and a TOU Id.
  • [0056]
    In step 306, it is determined whether meter 131 had previously been registered with a different collector. If meter 131 had previously been registered with a different collector, the TOU Id would have been set in meter 131 and would typically be set correctly in data collector/meter 121, and the process is done in step 309. Transferring the TOU Id to the new collector prevents meter 131 from reverting to a default TOU Id, which would likely cause meter 131 to use an incorrect TOU schedule and store data in the incorrect TOU billing locations or “buckets.”
  • [0057]
    The billing id may be assigned by remote location 110 and updated in data collector/meter 121. The billing id may be stored in data collector/meter 121 and may be used to determine the date that data collector/meter 121 communicates a demand reset message to meter 131. Until updated by remote location 110, data collector/meter 121 assigns meter 131 to billing id 0. A billing date for this id is not defined, which means that data collector/meter 121 may not tell meter 131 to perform a demand reset. This mechanism prevents data collector/meter 121 from telling meter 131 to perform a demand reset on the incorrect billing date.
  • [0058]
    If it is determined in step 306 that meter 131 is not switching from data collector/meter 121 to another collector, in step 307, remote location 110 ensures that the demand reset or previous billing data from meter 131 stored in data collector/meter 121 is relevant data that has not yet been read by remote location 110. The demand reset count read from meter 131 is used by remote location 110 to determine if the data is previous billing or previous season data.
  • [0059]
    In step 308, the data collector/meter uses a Registration Procedure to communicate the assigned TOU Id to meter 131. Meter 131 uses the TOU Id to store the correct TOU schedules.
  • [0060]
    Data collector/meter 121 also may be designed to gather load profile data from any configurable set of meters. In particular, because as discussed, meter 131 may be capable of storing a certain interval of data (e.g., data collected over a 24-hour period), data collector/meter 121 may be variably configured to retrieve the stored load profile data over a group of meters. For example, the number of meters profiled by data collector/meter 121 and the amount of data stored for each meter may be configured within data collector/meter 121.
  • [0061]
    In just one embodiment, for example, data collector/meter 121 could be configured to store data for fifty meters having forty days of stored data for each meter. In another embodiment, for example, data collector/meter 121 could be configured to store data for five hundred meters having four days of stored data for each meter. FIG. 4 provides an example of a load profile table that is capable of storing 13 intervals of data. Data collector/meter 121 may be configured to read the load profile data from meters 131 and 141 frequently enough to ensure that there is no data lost in the transmission. Data collector/meter 121 may read the similar interval data multiple times, but it only appends new data to the existing data in the collector database.
  • [0062]
    In addition to dynamically allocating the amount of memory used to collect load profile data, the number of meters for which data collector/meter 121 stores basic data (e.g., current billing data, previous billing data, and previous season data) is configurable. Changing the number of meters supported changes the amount of memory available for load profile. A data collector may support, for example more than 500 meters, but any number of meters may be supported. To increase the amount of memory available for load profile data, the data collector could be configured to only store data for 250 meters, for example.
  • [0063]
    Data collector/meter 121 also permits remote location 110 to direct specific real-time commands to meter 131. For example, if certain emergency conditions exist (e.g., rolling brownout or blackout), the utility may desire to modify a TOU schedule on a short-term basis. Also, short-term TOU schedule adjustments may be desirable for certain extreme weather conditions (e.g., hottest or coldest days). AMR system 100 permits data collector/meter 121 to send instructions to meter 131 to conduct a temporal “override” of the set TOU schedule. When the interval for the override expires, meter 131 is directed to return to the set TOU schedule. For example, data collector/meter 121 may direct meter 131 to bill at a higher rate tomorrow from 4 pm to 6 pm, due to expected weather conditions. At 6 pm, meter 131 may be directed to resume normal TOU scheduling.
  • [0064]
    Data collector/meter 121 may accomplish such short-term override of TOU schedule on a broad basis by using a broadcast transmission procedure to all of its served meters. Such messaging may be carried further to alert the customer premise of the impending TOU schedule change, so as to counteract the increased billing rate and promote lower energy usage. For example, meter 131 may send a message to a unit within the customer premise (e.g., an electronic thermostat) to increase the energy usage during the lower billing period, and decrease the energy usage during the higher billing period.
  • [0065]
    Similar to short-term overrides of TOU schedules, data collector/meter 121 may accomplish on-demand reads and writes with meter 131. For example, the utility may desire certain usage data immediately over a range of meters, or all data from a particular meter. Data collector/meter 121 accommodates such on-demand reads. Also, on-demand writes from data collector/meter 121 to meter 131 may be desired. For example, if a customer desires to change its billing schedule/date or TOU schedule/rate, a utility's customer service can initiate a write to meter 131 via data collector/meter 121 as the customer is on the telephone making the request. Such on-demand reads and writes may be conducted directly by remote location 110 to a particular meter, using a “pass through” procedure, where data collector/meter 121 simply routes the request to meter 131.
  • [0066]
    Data collector/meter 121 also provides support for certain special requests from remote location 110. For example, if remote location 110 wants certain meter data (e.g., meters with billing dates on a certain date, or get previous season data for all the meters that changed seasons), data collector/meter 121 supports filtered requests. Such filtered data requests can request data from all meters, a particular meter, all meters associated with a particular billing identification, and/or all meters associated with a particular TOU identification, for example. Also, specific data-based filters may be applied to the request. For example, a filter may provide only report data for a meter if the meter's data is out of date by a certain number of hours.
  • [0067]
    Illustrative Computing Environment for Automated Meter Reading System
  • [0068]
    [0068]FIG. 5 depicts an exemplary computing system 500 in accordance with the invention. Portions of computing system may be a part of computer 203 in data collector/meter 121. Computing system 500 is capable of executing a computing application 580 a that allows users to gain access to data access files, for example. Example computing system 500 is controlled primarily by computer-readable instructions, which may be in the form of software, hardware, and/or firmware, wherever, or by whatever means such software is stored or accessed. Such software may be executed within central processing unit (CPU) 510 to cause data processing system 500 to do work. In many known workstations and personal computers, central processing unit 510 is implemented by a single-chip CPU called a microprocessor. Coprocessor 515 is an optional processor, distinct from main CPU 510 that performs additional functions or assists CPU 510. One common type of coprocessor is the floating-point coprocessor, also called a numeric or math coprocessor, which is designed to perform numeric calculations faster and better than general-purpose CPU 510. Recently, however, the functions of many coprocessors have been incorporated into more powerful single-chip microprocessors.
  • [0069]
    In operation, CPU 510 fetches, decodes, and executes instructions, and transfers information to and from other resources via the computer's main data-transfer path, system bus 505. Such a system bus connects the components in computing system 500 and defines the medium for data exchange. System bus 505 typically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the system bus. An example of such a system bus is the PCI (Peripheral Component Interconnect) bus. Some of today's advanced busses provide a function called bus arbitration that regulates access to the bus by extension cards, controllers, and CPU 510. Devices that attach to these busses and arbitrate to take over the bus are called bus masters. Bus master support also allows multiprocessor configurations of the busses to be created by the addition of bus master adapters containing a processor and its support chips.
  • [0070]
    Memory devices coupled to system bus 505 include random access memory (RAM) 525 and read only memory (ROM) 530. Such memories include circuitry that allows information to be stored and retrieved. ROMs 530 generally contain stored data that cannot be modified. Data stored in RAM 525 can be read or changed by CPU 510 or other hardware devices. Access to RAM 525 and/or ROM 530 may be controlled by memory controller 520. Memory controller 520 may provide an address translation function that translates virtual addresses into physical addresses as instructions are executed. Memory controller 520 also may provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in user mode can access only memory mapped by its own process virtual address space; it cannot access memory within another process's virtual address space unless memory sharing between the processes has been established.
  • [0071]
    In addition, computing system 500 may contain peripherals controller 535 responsible for communicating instructions from CPU 510 to peripherals, such as, printer 540, keyboard 545, mouse 550, and disk drive 555. Disk drive 555 may be a hard-drive device, for example.
  • [0072]
    Display 565, which is controlled by display controller 560, is used to display visual output generated by computing system 500. Such visual output may include text, graphics, animated graphics, and video. Display 565 may be implemented with a CRT-based video display, an LCD-based flat-panel display, gas plasma-based flat-panel display, or a touch-panel. Display controller 563 includes electronic components required to generate a video signal that is sent to display 565.
  • [0073]
    Further, computing system 500 may contain network adapter 570, which may be used to connect computing system 500 to an external communication network 560. Communications network 560 may provide computer users with techniques for communicating and transferring software and information electronically. Additionally, communications network 560 may provide distributed processing, which involves several computers and the sharing of workloads or cooperative efforts in performing a task. It will be appreciated that the network connections shown are examples and other means of establishing a communications link between the computers may be used.
  • [0074]
    Illustrative Computer Network Environment for Automated Meter Reading System
  • [0075]
    As noted above, the computer described with respect to FIG. 5 can be deployed as part of a computer network. In general, the above description applies to both server computers and client computers deployed in a network environment. FIG. 6 provides an example of a network environment 600, with a server computer 602, 605 in communication with client computers 601, 606, 607 via a communications network 660, in which the invention may be employed.
  • [0076]
    As shown in FIG. 6, a number of servers 602, 605 are interconnected via a communications network 660 (which may be a LAN, WAN, intranet or the Internet, for example) with a number of client computers 601, 606, 607, or computing devices, such as, mobile phone 601 and personal digital assistant 603. In a network environment in which the communications network 660 is the Internet, for example, the servers 602, 605 can be Web servers with which the clients 601, 606, 607 communicate via any of a number of known protocols, such as, hypertext transfer protocol (HTTP) or wireless application protocol (WAP), as well as other innovative communication protocols. Each client computer 601, 606, 607 can be equipped with computing application 580 a to gain access to the servers 602, 605. Similarly, personal digital assistant 603 can be equipped with computing application 580 b and mobile phone 604 can be equipped with computing application 580 c to display and receive various data. It should also be appreciated that personal digital assistant 603 and mobile phone 604 may be used to request access and/or data from servers 602, 605.
  • [0077]
    The invention is directed to a system, method, and metering device communicating data in an automated meter reading system. The invention was described in the context of wired and wireless data communication system, but is not so limited to, regardless of any specific description in the drawing or examples set forth herein. For example, the invention may be applied to non-traditional networks like Voice-over-IP-based networks, or virtual private networks, for example. Also, although the invention was described in the context of electrical power meters, it should be appreciated that the invention applies equally to communications with any type of service meter, including water and gas meters, for example. Also, the format and protocols used by the data files are not limited to any particular type.
  • [0078]
    It will be understood that the invention is not limited to use of any of the particular components or devices herein. Indeed, this invention can be used in any application that requires controlling access to data captured by an electric power meter. Further, the system disclosed in the invention can be used with the method of the invention or a variety of other applications.
  • [0079]
    While the invention has been particularly shown and described with reference to the embodiments thereof, it will be understood by those skilled in the art that the invention is not limited to the embodiments specifically disclosed herein. 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.
Patentzitate
Zitiertes PatentEingetragen Veröffentlichungsdatum Antragsteller Titel
US4804957 *17. Sept. 198614. Febr. 1989Triad Communications, Inc.Utility meter and submetering system
US4811011 *29. Apr. 19877. März 1989Johann SollingerAutomatic metering apparatus
US4833618 *20. Febr. 198623. Mai 1989Net Laboratories, Inc.System for automatically reading utility meters from a remote location
US4939726 *18. Juli 19893. Juli 1990Metricom, Inc.Method for routing packets in a packet communication network
US5007052 *11. Apr. 19899. Apr. 1991Metricom, Inc.Method for routing packets by squelched flooding
US5079768 *11. Sept. 19907. Jan. 1992Metricom, Inc.Method for frequency sharing in frequency hopping communications network
US5115433 *20. Apr. 199019. Mai 1992Metricom, Inc.Method and system for routing packets in a packet communication network
US5129096 *4. Mai 19907. Juli 1992Tunstall Telecom LimitedSystem which routes radio transmissions to selected repeaters for retransmission
US5130987 *11. Sept. 199114. Juli 1992Metricom, Inc.Method for synchronizing a wide area network without global synchronizing
US5295154 *3. Mai 199315. März 1994Norand CorporationRadio frequency local area network
US5428636 *7. Mai 199327. Juni 1995Norand CorporationRadio frequency local area network
US5455569 *6. Okt. 19943. Okt. 1995Aes CorporationLink layered communications network and method
US5488608 *14. Apr. 199430. Jan. 1996Metricom, Inc.Method and system for routing packets in a packet communication network using locally constructed routing tables
US5521910 *5. Okt. 199428. Mai 1996Cabletron Systems, Inc.Method for determining a best path between two nodes
US5525898 *16. Dez. 199411. Juni 1996General Electric CompanyProgrammable multi-channel load profile recorder and method of recording electrical energy metering quantities therein
US5570084 *28. Juni 199429. Okt. 1996Metricom, Inc.Method of loose source routing over disparate network types in a packet communication network
US5617084 *24. Okt. 19951. Apr. 1997Sears; Lawrence M.Apparatus for communicating utility usage-related information from a utility usage location to a utility usage registering device
US5636216 *8. Apr. 19943. Juni 1997Metricom, Inc.Method for translating internet protocol addresses to other distributed network addressing schemes
US5732078 *16. Jan. 199624. März 1998Bell Communications Research, Inc.On-demand guaranteed bandwidth service for internet access points using supplemental user-allocatable bandwidth network
US5748619 *26. Dez. 19965. Mai 1998Meier; Robert C.Communication network providing wireless and hard-wired dynamic routing
US5757783 *15. Juni 199526. Mai 1998Lucent Technologies Inc.Method and apparatus for routing ATM cells in an AD-ATM LAN
US5907491 *4. Apr. 199725. Mai 1999Csi Technology, Inc.Wireless machine monitoring and communication system
US5907540 *19. Sept. 199525. Mai 1999Hitachi, Ltd.Radio data communication apparatus having a relay function and radio data communication method and system using the same
US5953319 *29. Sept. 199514. Sept. 1999Amsc Subsidiary CorporationWide area mobile communication networks with multiple routing mode options
US5960074 *23. Sept. 199628. Sept. 1999Curtis ClarkMobile tele-computer network for motion picture, television and tv advertising production
US5974236 *17. Aug. 199526. Okt. 1999Aes CorporationDynamically reconfigurable communications network and method
US5986574 *16. Okt. 199716. Nov. 1999Peco Energy CompanySystem and method for communication between remote locations
US6078785 *15. Okt. 199620. Juni 2000Bush; E. WilliamDemand reporting of electricity consumption by radio in relays to a base station, and demand relays wattmeters so reporting over a wide area
US6112237 *26. Nov. 199629. Aug. 2000Global Maintech, Inc.Electronic monitoring system and method for externally monitoring processes in a computer system
US6124806 *11. Sept. 199826. Sept. 2000Williams Wireless, Inc.Wide area remote telemetry
US6195018 *7. Febr. 199627. Febr. 2001Cellnet Data Systems, Inc.Metering system
US6249516 *27. Jan. 200019. Juni 2001Edwin B. BrownriggWireless network gateway and method for providing same
US6333975 *3. März 199925. Dez. 2001Itron, Inc.Method and system for reading intelligent utility meters
US6374254 *30. Juni 199916. Apr. 2002International Business Machines CorporationScalable, distributed, asynchronous data collection mechanism
US6393341 *7. Dez. 199921. Mai 2002Abb Automation Inc.Architecture neutral device abstraction layer for interfacing devices and applications
US6396839 *12. Febr. 199828. Mai 2002Abb Automation Inc.Remote access to electronic meters using a TCP/IP protocol suite
US6421731 *29. Okt. 199616. Juli 2002Telxon CorporationDynamic next hop routing protocol
US6437692 *12. Nov. 199920. Aug. 2002Statsignal Systems, Inc.System and method for monitoring and controlling remote devices
US6657549 *2. Aug. 20002. Dez. 2003Koninklijke Philips Electronics N.V.Location finding system and method
US6867707 *24. Apr. 200215. März 2005Elster Electricity, LlcAutomated on-site meter registration confirmation using a portable, wireless computing device
US20020026957 *1. Okt. 19997. März 2002Mark ReymanEnhanced and remote meter reading with vibration actuated valve
US20030123442 *27. Dez. 20013. Juli 2003Drucker Benjamin T.Distributed usage metering of multiple networked devices
US20030202512 *29. Apr. 200230. Okt. 2003Harris CorporationTemporal transition network protocol (TTNP) in a mobile ad hoc network
US20050270173 *2. Mai 20058. Dez. 2005Boaz Jon AAutomated meter reading system, communication and control network for automated meter reading, meter data collector program product, and associated methods
Referenziert von
Zitiert von PatentEingetragen Veröffentlichungsdatum Antragsteller Titel
US6985087 *15. März 200210. Jan. 2006Qualcomm Inc.Method and apparatus for wireless remote telemetry using ad-hoc networks
US7089125 *27. Okt. 20048. Aug. 2006Itron, Inc.Distributed asset optimization (DAO) system and method
US7116243 *30. Aug. 20043. Okt. 2006Itron, Inc.System and method for automatic meter reading with mobile configuration
US7185131 *18. Nov. 200427. Febr. 2007Amron Technologies, Inc.Host-client utility meter systems and methods for communicating with the same
US72314827. Okt. 200512. Juni 2007Universal Smart Technologies, Llc.Method and system for monitoring and transmitting utility status via universal communications interface
US7239250 *26. Apr. 20043. Juli 2007Elster Electricity, LlcSystem and method for improved transmission of meter data
US7289887 *5. Dez. 200330. Okt. 2007Smartsynch, Inc.Systems and methods for remote power management using IEEE 802 based wireless communication links
US7308369 *28. Sept. 200511. Dez. 2007Elster Electricity LlcEnsuring automatic season change demand resets in a mesh type network of telemetry devices
US7336065 *13. Jan. 200326. Febr. 2008Power Measurement Ltd.Energy device with an extended dynamic range on current readings
US7349766 *8. März 200625. März 2008Smartsynch, Inc.Systems and methods for remote power management using 802.11 wireless protocols
US73797912. Aug. 200527. Mai 2008Uscl CorporationIntegrated metrology systems and information and control apparatus for interaction with integrated metrology systems
US74510198. Febr. 200811. Nov. 2008Smartsynch, Inc.Systems and methods for remote power management using 802.11 wireless protocols
US74872826. Febr. 20073. Febr. 2009Leach Mark AHost-client utility meter systems and methods for communicating with the same
US7554320 *30. Okt. 200630. Juni 2009Electro Industries/Gauge Tech.Intelligent electronic device for providing broadband internet access
US756106222. Sept. 200614. Juli 2009Itron, Inc.System and method for automatic meter reading with mobile configuration
US768326118. Mai 200723. März 2010Schweitzer Engineering Laboratories, Inc.Article and method for providing a seal for an encapsulated device
US768822016. Dez. 200530. März 2010Hunt Power, L.P.Device and method for processing meter data from multiple meters
US769253818. Mai 20076. Apr. 2010Schweitzer Engineering Laboratories, Inc.User interface for monitoring a plurality of faulted circuit indicators
US770259424. Sept. 200420. Apr. 2010Elster Electricity, LlcSystem and method for automated configuration of meters
US772045922. Juni 200518. Mai 2010Actaris Uk LimitedMethod of remote collection of data for the account of an entity, using a third party data communication network, e.g. for automatic meter reading
US774197616. Dez. 200522. Juni 2010Hunt Power, L.P.Server and method for processing meter data into a common format
US774243024. Sept. 200422. Juni 2010Elster Electricity, LlcSystem for automated management of spontaneous node migration in a distributed fixed wireless network
US774624118. Mai 200729. Juni 2010Schweitzer Engineering Laboratories, Inc.Magnetic probe apparatus and method for providing a wireless connection to a detection device
US774773319. Jan. 200529. Juni 2010Electro Industries/Gauge TechPower meter having multiple ethernet ports
US776503528. Okt. 200827. Juli 2010Smartsynch, Inc.Systems and methods for remote power management using 802.11 wireless protocols
US786877618. Mai 200711. Jan. 2011Schweitzer Engineering Laboratories, Inc.Apparatus and system for adjusting settings of a power system device using a magnetically coupled actuator
US787762418. Mai 200725. Jan. 2011Schweitzer Engineering Laboratories, Inc.Faulted circuit indicator monitoring device with wireless memory monitor
US800031415. Dez. 200516. Aug. 2011Ipco, LlcWireless network system and method for providing same
US800557628. Mai 201023. Aug. 2011Smartsynch, Inc.Method for deactivating a utility meter
US80137323. Juni 20096. Sept. 2011Sipco, LlcSystems and methods for monitoring and controlling remote devices
US802269029. Juni 200920. Sept. 2011Electro Industries/Gauge TechIntelligent electronic device for providing broadband internet access
US80316503. März 20044. Okt. 2011Sipco, LlcSystem and method for monitoring remote devices with a dual-mode wireless communication protocol
US805900618. Mai 200715. Nov. 2011Schweitzer Engineering Laboratories, Inc.System and method for communicating power system information through a radio frequency device
US80644129. Mai 200522. Nov. 2011Sipco, LlcSystems and methods for monitoring conditions
US807338414. Dez. 20066. Dez. 2011Elster Electricity, LlcOptimization of redundancy and throughput in an automated meter data collection system using a wireless network
US808206827. Mai 201020. Dez. 2011Smartsynch, Inc.System for managing power loads
US810339028. Mai 201024. Jan. 2012Smartsynch, Inc.Methods for reading data in a utility meter in connection with a load reduction initiative
US811691727. Mai 201014. Febr. 2012Smartsynch, Inc.System for controlling a power load
US813893421. Nov. 200820. März 2012Trilliant Networks, Inc.System and method for false alert filtering of event messages within a network
US814459621. Nov. 200827. März 2012Trilliant Networks, Inc.Communication and message route optimization and messaging in a mesh network
US8157160 *23. Juni 201017. Apr. 2012Arad Measuring Technologies Ltd.Meter register and remote meter reader utilizing a stepper motor
US817113615. Juni 20101. Mai 2012Sipco, LlcSystem and method for transmitting pollution information over an integrated wireless network
US817136421. Nov. 20081. Mai 2012Trilliant Networks, Inc.System and method for power outage and restoration notification in an advanced metering infrastructure network
US817617428. Juni 20108. Mai 2012Electro Industries/Gauge TechPower meter having multiple ethernet ports
US820346313. Febr. 200919. Juni 2012Elster Electricity LlcWakeup and interrogation of meter-reading devices using licensed narrowband and unlicensed wideband radio communication
US821266730. Juni 20113. Juli 2012Sipco, LlcAutomotive diagnostic data monitoring systems and methods
US822301030. Aug. 201117. Juli 2012Sipco LlcSystems and methods for monitoring vehicle parking
US823347111. Juni 200931. Juli 2012Ipco, LlcWireless network system and method for providing same
US828918221. Nov. 200816. Okt. 2012Trilliant Networks, Inc.Methods and systems for virtual energy management display
US830666826. Mai 20086. Nov. 2012Uscl CorporationIntegrated metrology systems and information and control apparatus for interaction with integrated metrology systems
US8312103 *29. Aug. 200713. Nov. 2012Itron, Inc.Periodic balanced communication node and server assignment
US831965811. März 201027. Nov. 2012Trilliant Networks, Inc.Process, device and system for mapping transformers to meters and locating non-technical line losses
US833205521. Nov. 200811. Dez. 2012Trilliant Networks, Inc.Energy use control system and method
US833478727. Okt. 200818. Dez. 2012Trilliant Networks, Inc.Gas meter having ultra-sensitive magnetic material retrofitted onto meter dial and method for performing meter retrofit
US83507184. Mai 20108. Jan. 2013Itron, Inc.Secure collector diagnostic portal activation
US837069716. März 20125. Febr. 2013Trilliant Networks, Inc.System and method for power outage and restoration notification in an advanced metering infrastructure network
US837956429. Aug. 201119. Febr. 2013Sipco, LlcSystem and method for monitoring remote devices with a dual-mode wireless communication protocol
US841093131. Aug. 20112. Apr. 2013Sipco, LlcMobile inventory unit monitoring systems and methods
US84468842. Juli 201021. Mai 2013Sipco, LlcDual-mode communication devices, methods and systems
US84488456. Febr. 201228. Mai 2013Arad Measuring Technologies Ltd.Meter register and remote meter reader utilizing a stepper motor
US8477794 *30. Apr. 20092. Juli 2013Elster Electricity, LlcMultiple communications protocol routing in advanced metering infrastructure context
US84890636. Mai 201116. Juli 2013Sipco, LlcSystems and methods for providing emergency messages to a mobile device
US850264021. Nov. 20086. Aug. 2013Trilliant Networks, Inc.System and method for transmitting and receiving information on a neighborhood area network
US852569211. Juni 20093. Sept. 2013Elster Solutions, LlcTechniques for limiting demand from an electricity meter with an installed relay
US852615621. Dez. 20113. Sept. 2013Schweitzer Engineering Laboratories IncHigh speed signaling of power system conditions
US862549623. Mai 20127. Jan. 2014Ipco, LlcWireless network system and method for providing same
US866510218. Juli 20084. März 2014Schweitzer Engineering Laboratories IncTransceiver interface for power system monitoring
US866635720. Jan. 20094. März 2014Sipco, LlcSystem and method for transmitting an emergency message over an integrated wireless network
US86993774. Sept. 200915. Apr. 2014Trilliant Networks, Inc.System and method for implementing mesh network communications using a mesh network protocol
US87252748. Nov. 201213. Mai 2014Trilliant Networks, Inc.Energy use control system and method
US878146223. Sept. 201015. Juli 2014Itron, Inc.Methodology and apparatus for validating network coverage
US878724629. Mai 201222. Juli 2014Ipco, LlcSystems and methods for facilitating wireless network communication, satellite-based wireless network systems, and aircraft-based wireless network systems, and related methods
US883242815. Nov. 20119. Sept. 2014Trilliant Holdings Inc.System and method for securely communicating across multiple networks using a single radio
US88563239. Febr. 20127. Okt. 2014Trilliant Holdings, Inc.Device and method for facilitating secure communications over a cellular network
US889133829. Jan. 200918. Nov. 2014Itron, Inc.Measuring the accuracy of an endpoint clock from a remote device
US890765719. Sept. 20119. Dez. 2014Electro Industries/Gauge TechIntelligent electronic device for providing broadband internet access
US89245871. Juni 201230. Dez. 2014Sipco, LlcSystems and methods for controlling communication between a host computer and communication devices
US89245881. Juni 201230. Dez. 2014Sipco, LlcSystems and methods for controlling communication between a host computer and communication devices
US893057118. Jan. 20106. Jan. 2015Sipco, LLPSystems and methods for controlling communication between a host computer and communication devices
US896470812. Apr. 201024. Febr. 2015Sipco LlcSystems and methods for monitoring and controlling remote devices
US897039424. Jan. 20123. März 2015Trilliant Holdings Inc.Aggregated real-time power outages/restoration reporting (RTPOR) in a secure mesh network
US89828563. Febr. 200917. März 2015Ipco, LlcSystems and methods for facilitating wireless network communication, satellite-based wireless network systems, and aircraft-based wireless network systems, and related methods
US900178719. Sept. 20127. Apr. 2015Trilliant Networks Inc.System and method for implementing handover of a hybrid communications module
US901317313. Sept. 201121. Apr. 2015Trilliant Networks, Inc.Process for detecting energy theft
US90413497. März 201226. Mai 2015Trilliant Networks, Inc.System and method for managing load distribution across a power grid
US908412026. Aug. 201114. Juli 2015Trilliant Networks Inc.System and method for interference free operation of co-located transceivers
US91112401. Mai 201218. Aug. 2015Sipco, Llc.System and method for transmitting pollution information over an integrated wireless network
US912949721. Dez. 20118. Sept. 2015Statsignal Systems, Inc.Systems and methods for monitoring conditions
US918982219. Okt. 201217. Nov. 2015Trilliant Networks, Inc.Process, device and system for mapping transformers to meters and locating non-technical line losses
US91947203. Mai 201224. Nov. 2015Electro Industries/Gauge TechPower meter having multiple Ethernet ports
US92820293. März 20148. März 2016Sipco, Llc.System and method for transmitting an emergency message over an integrated wireless network
US928238313. Jan. 20128. März 2016Trilliant IncorporatedProcess, device and system for volt/VAR optimization
US92882158. März 201315. März 2016Itron, Inc.Utilizing routing for secure transactions
US943093624. Febr. 201530. Aug. 2016Sipco LlcSystems and methods for monitoring and controlling remote devices
US943912625. Jan. 20066. Sept. 2016Sipco, LlcWireless network protocol system and methods
US951569110. Aug. 20156. Dez. 2016Sipco, Llc.System and method for transmitting pollution information over an integrated wireless network
US9565513 *2. März 20157. Febr. 2017Thirdwayv, Inc.Systems and methods for providing long-range network services to short-range wireless devices
US957158217. Juni 201414. Febr. 2017Sipco, LlcSystems and methods for monitoring and controlling remote devices
US961213224. Dez. 20084. Apr. 2017Elster Solutions, LlcOptimized data collection in a wireless fixed network metering system
US96152268. März 20164. Apr. 2017Sipco, LlcSystem and method for transmitting an emergency message over an integrated wireless network
US962145717. Febr. 201411. Apr. 2017Trilliant Networks, Inc.System and method for implementing mesh network communications using a mesh network protocol
US96781225. Dez. 201413. Juni 2017Electro Industries/Gauge TechIntelligent electronic device for providing broadband internet access
US969126326. Aug. 201527. Juni 2017Sipco, LlcSystems and methods for monitoring conditions
US9714964 *18. Mai 201225. Juli 2017Bob Holding GmbhVoltage-dependent meter
US9729943 *13. März 20138. Aug. 2017Trimble Inc.Utility meter reporting network
US20030174067 *15. März 200218. Sept. 2003Soliman Samir S.Method and apparatus for wireless remote telemetry using ad-hoc networks
US20030208554 *3. Mai 20026. Nov. 2003Holder Helen A.Wireless network access point with computing capability and method of operation thereof
US20040239522 *2. Juni 20032. Dez. 2004Gallagher Todd JohnRemotely accessed electrical metering system
US20050065742 *5. Dez. 200324. März 2005Smartsynch, Inc.Systems and methods for remote power management using IEEE 802 based wireless communication links
US20050068194 *30. Aug. 200431. März 2005Michael SchleichSystem and method for automatic meter reading with mobile configuration
US20050090995 *27. Okt. 200428. Apr. 2005Itron Inc.Distributed asset optimization (DAO) system and method
US20050119841 *8. Nov. 20042. Juni 2005Landisinc.Method of timing demand and time-of-use functionality with external clock source
US20050268322 *3. Mai 20051. Dez. 2005Watson Scott FApparatus and method for utilizing a pre-existing power grid to provide internet access to a home or office or the like
US20060023853 *22. Juni 20052. Febr. 2006Christopher ShelleyMethod of remote collection of data for the account of an entity, using a third party data communication network, e.g. for automatic meter reading
US20060031180 *2. Aug. 20059. Febr. 2006Uscl CorporationIntegrated metrology systems and information and control apparatus for interaction with integrated metrology systems
US20060036795 *7. Okt. 200516. Febr. 2006Mark LeachMethod and system for monitoring and transmitting utility status via universal communications interface
US20060045105 *18. Juli 20052. März 2006Dobosz Paul JSystem and method for using a utility meter
US20060184288 *8. März 200617. Aug. 2006Smartsynch, IncorporatedSystems and methods for remote power management using 802.11 wireless protocols
US20060217936 *27. Sept. 200528. Sept. 2006Elster Electricity LlcUsing a fixed network wireless data collection system to improve utility responsiveness to power outages
US20070005519 *20. Juni 20054. Jan. 2007Ravi GuptaSystems and methods for utility meter demand data collection
US20070013549 *22. Sept. 200618. Jan. 2007Itron, Inc.System and method for automatic meter reading with mobile configuration
US20070114987 *30. Okt. 200624. Mai 2007Electro Industries/Gauge Tech.Intelligent electronic device for providing broadband Internet access
US20070130408 *6. Febr. 20077. Juni 2007Universal Smart Technologies, LlcHost-Client Utility Meter Systems And Methods For Communicating With The Same
US20070139219 *16. Dez. 200521. Juni 2007Hunt Power, L.P.Server and method for processing meter data into a common format
US20070210933 *14. Mai 200713. Sept. 2007Universal Smart Technologies, LlcSystems and Methods For Monitoring and Transmitting Utility Status Information Via A Universal Communications Interface
US20070267210 *18. Mai 200722. Nov. 2007Kesler James RArticle and method for providing a seal for an encapsulated device
US20070268644 *18. Mai 200722. Nov. 2007Schweitzer Edmund OUser interface for monitoring a plurality of faulted circuit indicators
US20070269219 *18. Mai 200722. Nov. 2007Teller Witold RSystem and apparatus for optical communications through a semi-opaque material
US20080010528 *18. Mai 200710. Jan. 2008Park Douglas AFaulted circuit indicator monitoring device with wireless memory monitor
US20080071911 *29. Aug. 200720. März 2008Holbrook Kenneth JOrchestration manager
US20080071930 *29. Aug. 200720. März 2008Holbrook Kenneth JNative network transport
US20080074285 *29. Aug. 200727. März 2008Guthrie Kevin DInterface between meter and application (IMA)
US20080147243 *8. Febr. 200819. Juni 2008Smartsynch, Inc.Systems and Methods For Remote Power Management Using 802.11 Wireless Protocols
US20090055032 *28. Okt. 200826. Febr. 2009Smartsynch, Inc.Systems and Methods For Remote Power Management Using 802.11 Wireless Protocols
US20090058676 *3. Juni 20085. März 2009James Robert OrloskyAutomated meter reading, billing and payment processing system
US20090109056 *26. Mai 200830. Apr. 2009Uscl CorporationIntegrated metrology systems and information and control apparatus for interaction with integrated metrology systems
US20090135753 *21. Nov. 200828. Mai 2009Michel VeillettePower-conserving network device for advanced metering infrastructure
US20090135762 *21. Nov. 200828. Mai 2009Michel VeillettePoint-to-point communication within a mesh network
US20090135836 *21. Nov. 200828. Mai 2009Michel VeilletteCollector device and system utilizing standardized utility metering protocol
US20090135851 *21. Nov. 200828. Mai 2009Michel VeilletteTransport layer and model for an advanced metering infrastructure (ami) network
US20090138617 *21. Nov. 200828. Mai 2009Michel VeilletteMethod and system for creating and managing association and balancing of a mesh device in a mesh network
US20090265124 *29. Juni 200922. Okt. 2009Electro Industries/Gauge TechIntelligent Electronic Device for Providing Broadband Internet Access
US20090278706 *20. Mai 200912. Nov. 2009Enel Distribuzone S.P.AMethod and system for remote updates of meters for metering the consumption of electricity, water or gas
US20100026517 *1. Juli 20094. Febr. 2010Itron, Inc.Utility data collection and reconfigurations in a utility metering system
US20100127889 *21. Nov. 200827. Mai 2010William Steven VogelMethods and systems for virtual energy management display
US20100176967 *4. Jan. 200815. Juli 2010Scott CumeraltoCollecting utility data information and conducting reconfigurations, such as demand resets, in a utility metering system
US20100182743 *29. Dez. 200622. Juli 2010Carrier CorporationUniversalthermostat expansion port
US20100278187 *30. Apr. 20094. Nov. 2010Elster Electricity, LlcMultiple Communications Protocol Routing In Advanced Metering Infrastructure Context
US20100302061 *23. Juni 20102. Dez. 2010Arad Measuring Technologies Ltd.Meter Register and Remote Meter Reader Utilizing a Stepper Motor
US20100302064 *28. Mai 20102. Dez. 2010Smartsynch, Inc.Method for deactivating a utility meter
US20100305771 *27. Mai 20102. Dez. 2010Smartsynch, Inc.System for controlling a power load
US20100305772 *27. Mai 20102. Dez. 2010Smartsynch, Inc.System for managing power loads
US20100305891 *28. Mai 20102. Dez. 2010Smartsynch, Inc.Methods for reading data in a utility meter
US20110050454 *18. März 20093. März 2011Fernando Luis SanchezWireless system and method for remotely reading counters
US20110054814 *28. Juni 20103. März 2011Electro Industries/Gauge TechPower meter having multiple ethernet ports
US20110161468 *31. Dez. 200930. Juni 2011Schneider Electric USA, Inc.Method and system for cascading peer-to-peer configuration of large systems of ieds
US20120296785 *18. Mai 201222. Nov. 2012Bernhard BeckVoltage-dependent meter
US20130060395 *25. Mai 20127. März 2013Hunt Energy Iq, LpAutomated field provisioning for energy management systems
US20130234863 *8. März 201312. Sept. 2013Trilliant Networks, Inc.Method and apparatus for mobile metering
US20130300577 *16. Juli 201314. Nov. 2013Itron, Inc.Collecting utility data information and conducting reconfigurations, such as demand resets, in a utility metering system
US20140085103 *2. Dez. 201327. März 2014Electro Industries/Gauge TechOn-line web accessed energy meter
US20140156093 *4. Dez. 20125. Juni 2014General Electric CompanyAuto-discovery of smart meter update interval
US20140266778 *13. März 201318. Sept. 2014Trimble Navigation LimitedUtility meter reporting network
US20140365026 *4. März 201411. Dez. 2014Kabushiki Kaisha ToshibaSignature generating apparatus, signature generating method, computer program product, and electrical power consumption calculation system
CN101065646B *3. Aug. 200514. Sept. 2011Uscl有限公司Integrated metrology system and information and control apparatus for interaction with integrated metrology systems
EP1613048A1 *21. Juni 20054. Jan. 2006Actaris UK LimitedA method and a system for the remote automatic meter reading using the free capacity of a data network
EP1631009A1 *5. Aug. 20051. März 2006Delphi Technologies, Inc.System and method for using a utility meter
EP2302326A1 *3. Aug. 200530. März 2011USCL CorporationIntegrated metrology system and information and control apparatus for interaction with integrated metrology systems
WO2005027357A2 *2. Sept. 200424. März 2005Itron, Inc.System and method for automatic meter reading with mobile configuration
WO2005027357A3 *2. Sept. 20041. Juni 2006Itron IncSystem and method for automatic meter reading with mobile configuration
WO2005106819A1 *22. Apr. 200510. Nov. 2005Elster Electricity Llc.System and method for improved transmission of meter data
WO2006017671A1 *3. Aug. 200516. Febr. 2006Uscl CorporationIntegrated metrology system and information and control apparatus for interaction with integrated metrology systems
WO2006036780A2 *23. Sept. 20056. Apr. 2006Elster Electricity, LlcSystem for automatically enforcing a demand reset in a fixed network of electricity meters
WO2006036780A3 *23. Sept. 200518. Mai 2006Elster Electricity LlcSystem for automatically enforcing a demand reset in a fixed network of electricity meters
WO2008111858A1 *12. März 200818. Sept. 2008Telecom Ip LimitedMonitoring method, system and device
WO2009115627A1 *18. März 200924. Sept. 2009Aira Networks, S.L.Wireless system and method for remotely reading counters
WO2014000741A1 *28. Juni 20123. Jan. 2014Ista Danmark A/SData integration
Klassifizierungen
US-Klassifikation340/870.02, 709/200
Internationale KlassifikationH04L12/56, H04L12/28, G01D4/00, H04Q9/00
UnternehmensklassifikationH04W84/00, H04Q2209/60, Y04S20/322, H04Q9/00, Y02B90/242, G01D4/004, Y02B90/246, Y04S20/42
Europäische KlassifikationG01D4/00R1, H04Q9/00
Juristische Ereignisse
DatumCodeEreignisBeschreibung
14. Aug. 2002ASAssignment
Owner name: ABB INC., CONNECTICUT
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MASON, ROBERT T., JR.;HODGES, EUGENE W.;SMITH, KATHRYN J.;AND OTHERS;REEL/FRAME:013187/0846;SIGNING DATES FROM 20020730 TO 20020731
23. Juli 2003ASAssignment
Owner name: ELSTER ELECTRICITY, LLC, PENNSYLVANIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ABB INC.;REEL/FRAME:014302/0037
Effective date: 20030312