System and method for efficient configuration in a fixed network automated meter reading system

Abstract

Meters are configured using either a program update method or a meter update method. In the program update method, meters associated with a specified configuration program are identified and configured with updated parameters. In the meter update method, a specified set of meters is configured with a specified set of updated configuration parameters. The meter update method enables both time of use and other configuration parameters to be updated. Both methods enable various actions to be performed in conjunction with a meter configuration. Such actions may include, for example, recording a snapshot of current billing data, resetting billing data, and resetting demand data.

Description

TECHNICAL FIELD

The invention relates to the field of service meters. More specifically, the invention relates to meter configuration for an automated meter reading system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related by subject matter to U.S. patent application Ser. No. 10/185,074, filed Jun. 28, 2002, entitled “Data Collector for an Automated Meter Reading System” and to U.S. patent application Ser. No. 10/185,664, filed Jun. 27, 2002, entitled “Dynamic Self-Configuring Metering Network” the contents of which are hereby incorporated by reference in their entireties.

This application is also related to U.S. patent application Ser. No. 10/83 1,903, filed Apr. 26, 2003, now issued as U.S. Pat. No. 7,187,906, entitled “Method And System For Configurable Qualification And Registration In A Fixed Network Automated Meter Reading System” and to U.S. patent application Ser. No. 10/832,037, filed Apr. 26, 2003, entitled “System And Method For Improved Transmission”, both of which are also hereby incorporated by reference in their entireties.

BACKGROUND OF THE INVENTION

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.

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.

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.

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

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.

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.

In an embodiment of the invention, meters are configured using either a program update method or a meter update method. In the program update method, meters associated with a specified configuration program are identified and configured with updated parameters. In the meter update method, a specified set of meters is configured with a specified set of updated configuration parameters. The meter update method enables both time of use and other configuration parameters to be updated. Both methods enable various actions to be performed in conjunction with a meter configuration. Such actions may include, for example, recording a snapshot of current billing data, resetting billing data, and resetting demand data.

BRIEF DESCRIPTION OF THE DRAWINGS

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:

FIG. 1 is a block diagram of an automated meter reading system, according to the invention;

FIG. 2 is a block diagram of a data collector/meter, according to the invention;

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;

FIG. 4 provides an example of a load profile table, according to the invention;

FIG. 5 is a flow diagram of an exemplary program update method, according to the invention;

FIG. 6 is a flow diagram of an exemplary meter update method, according to the invention;

FIG. 7 is a flow diagram of a method for performing a meter update at a particular meter, according to the invention;

FIG. 8 provides an example of a computing system, according to the invention;

FIG. 9 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

FIG. 10 provides one example of the components that may be included with a LAN Option Board, according to the invention.

DETAILED DESCRIPTION OF THE INVENTION

Automated Meter Reading System

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.

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.

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 Elster Electricity, LLC. 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.

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.10/185,664, filed Jun. 27, 2002, now issued as U.S. Pat. No. 7,119,713, 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).

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 121 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.”

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.

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.

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.

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.

Data Collector/Meter

Data collector/meter 121 may be an A3 Alpha™ meter available from Elster Electricity, LLC. 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.

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.

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.

As shown in FIG. 2, data collector/meter 121 may include a meter 210 (e.g., an A3 Alpha™ meter available from Elster Electricity, LLC.) 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.

LAN Option Board 230 also may communicate via a wired interface (e.g., RS-232) 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.

FIG. 10 provides one example of the components that may be included with LAN Option Board 230. However, FIG. 10 is not meant to be an exclusive representation of such components or their configurations.

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.

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.

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.

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.

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.

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.

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.

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.

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 by setting information in the read message that forces meter 131 to perform a demand reset. This is illustrated by the following example.

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.

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.

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.

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., 8) 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.

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).

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.

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.

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.

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.

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.

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.

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.

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.

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.”

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 will 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.

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.

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.

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.

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.

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 1000 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.

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.

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. Transmission of the TOU override schedule to served meters may be accomplished using individual or broadcast transmission, or both. 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.

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.

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.

Thus, in summary, the exemplary embodiments set forth above with reference to FIGS. 1-4 describe communication of data between a server 111, a collector 121, and a number of meters 131 and 141. The embodiments described above enable, responsive to a request, time of use (TOU) configuration parameters to be sent to a single specified meter. Furthermore, the embodiments described above enable billing and demand data to be reset responsive to separate commands.

Program Update and Meter Update

Another embodiment, as will be described below with reference to FIGS. 5-7, enables meters to be configured using either a program update method or a meter update method. In the program update method, meters associated with a specified configuration program are identified and configured with updated parameters. In the meter update method, a specified set of meters is configured with a specified set of updated configuration parameters. The meter update method enables both time of use and other configuration parameters to be updated. Both methods enable various actions to be performed in conjunction with a meter configuration. Such actions may include, for example, recording a snapshot of current billing data, resetting billing data, and resetting demand data.

A flowchart of the program update method is shown in FIG. 5. At step 510, a program update request is received at server 111. The request specifies a particular configuration program to be updated. The specified program may be identified by a corresponding unique identifier (UID).

The specified configuration program may be a time of use (TOU) program. Each TOU program may have a number of corresponding parameters such as, for example, switch point information for multiple seasons, season change dates for multiple seasons, meter display information, and optionally meter actions. Switch point information and season change dates may be stored in a number of tables, each corresponding to a particular configuration program. Meter display information and meter actions may be stored in a single table with a number of entries, each corresponding to a particular configuration program.

At step 512, server 111 updates the parameters for the specified program in its corresponding tables and table entries. At step 514, server 111 issues a command to collector 121 to update the specified program. At step 516, collector 121 identifies a set of meters that are associated with the specified configuration program. The set includes at least one meter. Collector 121 maintains a list of the configuration program with which each meter is associated.

At step 518, collector 121 sets a number of status flags for each associated meter. Each such flag corresponds to a portion of the updated configuration parameters. For example, collector 121 may set the following five status flags:

• • DISPLAY_UPDATE_PENDING
  • WEEKDAY_TOU_SCHEDULE_PENDING
  • WEEKEND_TOU_SCHEDULE_PENDING
  • SPECIAL1_TOU_SCHEDULE_PENDING
  • SPECIAL2_TOU_SCHEDULE_PENDINGThe status flags enable collector 121 to determine whether the corresponding portion of the configuration parameters are received by the associated meter.

At step 520, collector 121 sends the updated configuration parameters to the set of meters identified at step 516. The configuration parameters may be sent during the first occurring meter read after the program update command is received.

At step 522, collector 121 receives acknowledgements from the meters that they have received the sent configuration parameters. Separate acknowledgments may be sent for each received portion of the configuration parameters. At step 524, collector 121 clears the status flags for each portion of the configuration parameters for which an acknowledgment is received.

At step 526, collector 121 determines whether any of the status flags have not been cleared and still remain set. This determination may be made during the subsequent meter read after the configuration information is first sent. If a status flag remains set, then this indicates that, for the corresponding portion of the configuration parameters, the first send was unsuccessful and needs to be resent during the subsequent meter read period.

If, at step 526, it is determined that some of the status flags remain set, then, at step 528, the configuration parameters are resent. Importantly, all of the configuration parameters need not be resent. Rather, only the portions of the configuration parameters indicated by the corresponding remaining status flags are resent, thereby preserving valuable bandwidth within the system. As should be appreciated, use of the status flags is not limited to configuration updates, and the flags may be used during initial registration of the meters to efficiently send initial configuration parameters to the newly registered meters.

The update of each meter in the associated set of meters may be performed in serial. Specifically, after completing the update for a particular meter, the collector may repeat steps 518-528 for the a next meter to be updated. Once the collector 121 receives all the acknowledgements from a particular meter, the collector allocates memory space to store a configuration change copy of data from each meter. This copy of data can be retrieved by the server 111 and provided to utility billing systems.

A flowchart of an exemplary meter update method is shown in FIG. 6. At step 610, a meter update request is received at server 111. The request specifies a set of meters to be updated. The set includes at least one meter. Furthermore, the request specifies a set of configuration parameters to be updated. The set includes at least one configuration parameter. The set may include both TOU and non-TOU parameters. The request may also specify a set of actions to be performed at the set of meters. The set may include at least one action. The actions may be, for example, recording a snapshot of current billing data, resetting billing data, and resetting demand data.

The TOU configuration parameters for the specified meters may be updated by changing the TOU configuration program to which the meters are assigned. The non-TOU configuration parameters for the specified meters may also be updated as specified in the request. The non-TOU parameters may include for example but not limited to the following:

• • Demand interval length (15, 30, or 60 minutes)
  • Metered quantity (kWh-delivered, kWh-received, kWh-sum, kWh-net)
  • Trip service disconnect switch if demand threshold is exceeded (True or False)
  • Detect load side voltage when service disconnect switch is closed (True or False)
  • Load profile interval length (15, 30, or 60 minutes)
  • Load profile divisor (Used to scale the pulses stored in each load profile interval)
  • Relay divisor (Used to scale energy pulses to a relay)
  • Demand quantity 1 selector (Select demand #1 to be calculated as Total-kW or tier based kW, where the tier can be A-E)
  • Demand quantity 2 selector (Select demand #2 to be calculated as Total-kW or tier based kW, where the tier can be A-E)
  • Demand threshold
  • Demand threshold penalty (When the service disconnect switch is opened because the demand threshold has been exceeded, the time period for the switch to remain open)
  • Demand forgiveness (The time period on power restoration for which demand calculations are to be ignored).
  • Exception Message Mask (Enables individual exception messages from the REX meter to be enabled or disabled. If enabled, the REX meter will transmit an exception message to the collector when the associated exception condition occurs.)

At step 612, server 111 sends a command to collector 121 to execute the meter update request. This command may take the form of a table write at collector 121. For example, collector 121 may include a table with a list that has a maximum size of the number of its registered meters. This list is used to select the meters that will be reconfigured. In addition to the list, the table may contain the specified set of configuration parameters that is to be downloaded to the list of meters, and optionally a list of actions that can be performed at the meters in conjunction with the configuration change. Preferably, the configuration parameters stored in this table coincide with configuration parameters stored in a corresponding table at each of the specified meters.

At step 614, collector 121 sets status flags. For TOU parameters, flags may be set as described above with respect to step 518 of FIG. 5. For non-TOU parameters, an additional status flag such as the following may be set:

• • CONFIG_UPDATE_PENDINGThus, collector 121 may generate separate status flags to monitor the status of TOU and non-TOU parameters. At step 616, the configuration parameters and optionally the list of actions to be performed are sent to the set of meters. Although not specifically re-depicted in FIG. 6, after the parameters are sent at step 616, the status flags generated at step 614 may be used to detect and resend necessary configuration parameters as described above with respect to steps 520-528 of FIG. 5.

A flowchart of an exemplary method for configuring a particular meter is shown in FIG. 7. The performance of actions at steps 712, 714, 718, and 720 are optional steps, but, if any or all of these actions are performed, they must be performed in the order in which they are depicted in FIG. 7 to ensure that they result in the production of accurate data.

At step 710 the updated configuration parameters and the optional set of actions are received at the meter. At step 712, the meter records a snapshot of its current billing data. The snapshot must be recorded prior to the demand reset so that the snapshot will contain the previous maximum demand. After the snapshot is receded, the current demand data is reset at step 714. Demand data must be reset prior to reconfiguration to ensure that the reset demand processing includes only data that is consistent with the previous configuration. After demand reset, the meter is reconfigured at step 716. The meter may be reconfigured by writing a configuration table with the data in the configuration table sent by the collector 121. The reconfiguration must occur prior to the billing data reset to ensure that the reset billing data is consistent with the new configuration and does not contain data calculated from the old information. After reconfiguration, the billing data is reset at step 718. The reset of billing data also resets demand calculations but does not trigger another snapshot of the billing data. At step 720, the snapshot of the billing data recorded at step 712 is returned to the collector 121.

Each meter may have a demand reset counter, which is incremented at each demand reset. After each demand reset, the collector 121 may read each meter's demand reset count. The count can be used by the collector 121 to make sure that the meter has properly received configuration instructions and reset demand. For example, when the configuration instructions are sent at one of steps 520 or 616, the collector may specify a particular demand reset count. When the meter attempts to reset demand at step 714, the meter will do so only if the demand reset count specified by the collector is one count greater than the meter's current demand reset count.

This mechanism prevents the meter from resetting demand multiple times in conjunction with a given operation. For example, consider the scenario in which the meter receives initial configuration instructions from the collector, but the collector does not receive the initial acknowledgement from the meter. In this scenario, multiple resets could occur if the collector re-sends the configuration instructions to the meter. However, with the demand count specification mechanism, the meter will acknowledge the receipt of resent configuration instructions, but will not process the resent configuration instructions because the demand reset count is no longer valid. Thus, the meter avoids multiple resets.

When collector 121 sends out configuration instructions to a meter, the instructions may specify additional information such as tables and table locations at the meters in which the configuration parameters are to be written. For example, the collector may provide a specific table identification number, table offset (0 for example), and number of bytes to write in the table (18, for example). The meter's response to the configuration instructions may be a variable length response, where the size is determined by the number of bytes in a metering data snapshot table. Preferably, the meter returns 35 bytes of data from the metering data snapshot table.

Thus, another embodiment for efficiently configuring meters in a fixed network automated meter reading (AMR) system has been disclosed. This embodiment enables configuration according to a program update request, in which all meters associated with a specified program are updated, and a meter update request, in which specified parameters at a specified set of meters are updated.

As should be appreciated, prior to performing a program update or meter update, meters must be initially registered with collector 121. For example, during registration, a meter may be installed with a default TOU program. The meter will provide this default TOU program to the collector 121, and the collector 121 will download to the newly registered meter the configuration parameters for the default TOU program. The collector 121 may set status flags to download to the newly registered meter the TOU configuration parameters as described above. The collector will also notify the remote communication server 131 of the newly registered meter, and the communication server 131 may change the program assignment for the newly registered meter. When a program assignment is changed, the status flags may be used to verify that the changed TOU program configuration parameters are downloaded to the meter.

Illustrative Computing Environment For Automated Meter Reading System

FIG. 8 depicts an exemplary computing system 800 in accordance with the invention. Portions of computing system may be a part of computer 203 in data collector/meter 121. Computing system 800 is capable of executing a computing application 880a that allows users to gain access to data access files, for example. Example computing system 800 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) 810 to cause data processing system 800 to do work. In many known workstations and personal computers, central processing unit 810 is implemented by a single-chip CPU called a microprocessor. Coprocessor 818 is an optional processor, distinct from main CPU 810 that performs additional functions or assists CPU 810. 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 810. Recently, however, the functions of many coprocessors have been incorporated into more powerful single-chip microprocessors.

In operation, CPU 810 fetches, decodes, and executes instructions, and transfers information to and from other resources via the computer's main data-transfer path, system bus 808. Such a system bus connects the components in computing system 800 and defines the medium for data exchange. System bus 808 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 810. 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.

Memory devices coupled to system bus 808 include random access memory (RAM) 828 and read only memory (ROM) 830. Such memories include circuitry that allows information to be stored and retrieved. ROMs 830 generally contain stored data that cannot be modified. Data stored in RAM 828 can be read or changed by CPU 810 or other hardware devices. Access to RAM 828 and/or ROM 830 may be controlled by memory controller 820. Memory controller 820 may provide an address translation function that translates virtual addresses into physical addresses as instructions are executed. Memory controller 820 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.

In addition, computing system 800 may contain peripherals controller 838 responsible for communicating instructions from CPU 810 to peripherals, such as, printer 840, keyboard 848, mouse 880, and disk drive 888. Disk drive 888 may be a hard-drive device, for example.

Display 868, which is controlled by display controller 860, is used to display visual output generated by computing system 800. Such visual output may include text, graphics, animated graphics, and video. Display 868 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 863 includes electronic components required to generate a video signal that is sent to display 868.

Further, computing system 800 may contain network adapter 870, which may be used to connect computing system 800 to an external communication network 860. Communications network 860 may provide computer users with techniques for communicating and transferring software and information electronically. Additionally, communications network 860 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.

Illustrative Computer Network Environment For Automated Meter Reading System

As noted above, the computer described with respect to FIG. 8 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.

As shown in FIG. 9, a number of servers 902, 908 are interconnected via a communications network 990 (which may be a LAN, WAN, intranet or the Internet, for example) with a number of client computers 901, 909, 907, or computing devices, such as, mobile phone 901 and personal digital assistant 903. In a network environment in which the communications network 990 is the Internet, for example, the servers 902, 908 can be Web servers with which the clients 901, 909, 907 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 901, 909, 907 can be equipped with computing application 880a to gain access to the servers 902, 908. Similarly, personal digital assistant 903 can be equipped with computing application 880b and mobile phone 904 can be equipped with computing application 880c to display and receive various data. It should also be appreciated that personal digital assistant 903 and mobile phone 904 may be used to request access and/or data from servers 902, 908.

The invention is 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, the format and protocols used by the data files are not limited to any particular type.

While systems and methods have been described and illustrated with reference to specific embodiments, those skilled in the art will recognize that modification and variations may be made without departing from the principles described above and set forth in the following claims. For example, although in the embodiments described above the systems and methods are described in the context of network of metering devices, such as electricity, gas, or water meters, it is understood that the present invention can be implemented in any kind of network in which it is necessary to obtain information from or to provide information to end devices in the system, including without limitation, networks comprising meters, in-home displays, in-home thermostats, load control devices, or any combination of such devices. Accordingly, reference should be made to the following claims as describing the scope of disclosed embodiments.

Claims

1. A method for configuring a set of devices associated with a configuration program, the set including at least one device, the method comprising: storing a list that identifies a plurality of registered configuration programs and, for each registered configuration program, a set of devices associated with the registered configuration program;receiving a program update command that specifies the configuration program to be updated without specifying the set of devices associated with the configuration program;identifying the set of devices associated with the configuration program by referencing the stored list;for each device in the set of devices: sending a first portion of the configuration program corresponding to weekday time of use information to the device during a first meter read;sending a second portion of the configuration program corresponding to weekend time of use information to the device during the first meter read;determining after the first meter read whether the device has failed to receive any portion of the configuration program; andresending each non-received portion of the configuration program to the device during a second meter read.

2. The method of claim 1, comprising identifying a set of meter devices.

3. The method of claim 1, further comprising, for each device in the set, setting at least one associated status flag corresponding to each portion of the configuration program.

4. The method of claim 3, further comprising clearing each status flag when an acknowledgement is received from a corresponding device that the corresponding device has received a corresponding portion of the configuration program.

5. The method of claim 1, further comprising determining after the first meter read whether a flag is still set in order to determine whether a corresponding device has received a corresponding portion of the configuration program.

6. A method for configuring a device with a set of time of use configuration parameters, the method comprising: receiving a request identifying the device and the set of time of use configuration parameters;during a first meter read: sending a first portion of the time of use configuration parameters corresponding to weekday time of use information;sending a second portion of the time of use configuration parameters corresponding to weekend time of use information;for each portion of the time of use configuration parameters: determining during a second meter read whether or not an acknowledgment has been received from the device indicating that it has received the portion; andif the acknowledgement has not been received, then resending the portion during the second meter read.

7. The method of claim 6, further comprising sending an updated non-time of use related configuration parameter to the device.

8. The method of claim 6, comprising receiving the request further identifying at least one action to be performed at the device, the action being at least one member of a group comprising recording a current snapshot of billing data, resetting the billing data, and resetting demand data.

9. The method of claim 8, further comprising recording a current snapshot of billing data, resetting the billing data, and resetting demand data in response to a single message from the collector.

10. The method of claim 6, further comprising: receiving from the device a snapshot of billing data; andstoring the snapshot of the billing data.

11. An automated device reading system comprising: a stored table that lists a plurality of registered configuration programs and, for each registered configuration program, a set of devices associated with the registered configuration program; anda collector that receives a command to update a configuration program, the command not identifying a set of devices associated with the configuration program, wherein the collector references the stored table to identify the set of devices associated with the configuration program and sends updated configuration parameters corresponding to the configuration program to the set of devices by, for each device in the set of devices: sending a first portion of the configuration parameters corresponding to weekday time of use information to the device during a first meter read;sending a second portion of the configuration parameters corresponding to weekend time of use information to the device during the first meter read;determining after the first meter read whether the device has failed to receive any portion of the configuration parameters; andresending each non-received portion of the configuration parameters to the device during a second meter read.

12. The system of claim 11, wherein the set of devices comprises a set of meters.

13. The system of claim 11, further comprising a server that receives a request to update the configuration program and sends an update command to the collector.

14. An automated device reading system comprising: a device; anda collector that updates the device with time of use configuration parameters by performing the following steps:during a first meter read: sending a first portion of the time of use configuration parameters corresponding to weekday time of use information;sending a second portion of the time of use configuration parameters corresponding to weekend time of use information; andfor each portion of the time of use configuration parameters: determining during a second meter read whether or not an acknowledgment has been received from the device indicating that it has received the portion; andif the acknowledgement has not been received, then resending the portion during the second meter read.

15. The system of claim 14, wherein the device is a meter.

16. The system of claim 14, further comprising a server that receives a request to update the device with the set of time of use configuration parameters.

17. The system of claim 16, wherein the request further comprises a set of at least one action to be performed at the device in conjunction with updating the time of use configuration parameters.

18. The system of claim 17, wherein the action comprises one of capturing a current snapshot of billing data, resetting the billing data, and resetting demand data.

19. A processor-readable medium having stored thereon instructions for configuring a set of devices associated with a configuration program, the set including at least one device, the instructions, when executed by a processor at a collector, causing the processor at said collector to: store a list that identifies a plurality of registered configuration programs and, for each registered configuration program, a set of devices associated with the registered configuration program;receive a program update command that specifies a configuration program to be updated without specifying a set of devices associated with the configuration program;identify the set of devices associated with the configuration program by referencing the stored list;for each device in the set of devices: sending a first portion of the configuration program corresponding to weekday time of use information to the device during a first meter read;sending a second portion of the configuration program corresponding to weekend time of use information to the device during the first meter read;determining after the first meter read whether the device has failed to receive any portion of the configuration program; andresending each non-received portion of the configuration program to the device during a second meter read.

20. The processor-readable medium of claim 19, wherein the set of devices comprises a set of meters.

21. A processor-readable medium having stored thereon instructions for configuring a device with a set of time of use configuration parameters, the instructions, when executed by a processor at a collector, causing the processor at said collector to: receive a command to update the device with a set of updated time of use configuration parameters; andduring a first meter read: sending a first portion of the time of use configuration parameters corresponding to weekday time of use information;sending a second portion of the time of use configuration parameters corresponding to weekend time of use information;for each portion of the time of use configuration parameters: determining during a second meter read whether or not an acknowledgment has been received from the device indicating that it has received the portion; andif the acknowledgement has not been received, then resending the portion during the second meter read.

22. The processor-readable medium of claim 21, wherein the device is a meter.

23. The processor-readable medium of claim 21, wherein the instructions further cause the processor to: receive a command identifying an action to be performed at the device in conjunction with updating the time of use configuration parameters; andtransmit the command to the device.

24. The processor-readable medium of claim 23, wherein the action comprises one of capturing a current snapshot of billing data, resetting the billing data, and resetting demand data.

25. A method for registering a device, the method comprising: receiving a message indicating a configuration program to which the device is assigned, the configuration program being stored at a collector, the configuration program being a time of use program;sending a first portion of the configuration program corresponding to weekday time of use information to the device during a first meter read;sending a second portion of the configuration program corresponding to weekend time of use information to the device during the first meter read;determining after the first meter read whether the device has failed to receive any portion of the configuration program, and, if so, then resending each non-received portion of the configuration program to the device during a second meter read.

26. The method of claim 25, further comprising recursively resending each non-received portion of the configuration program during each successive meter read until a corresponding acknowledgement is received from the device.

27. The method of claim 25, further comprising: sending a third portion of the configuration program corresponding to display information;sending a fourth portion of the configuration program corresponding to special time of use information; andsending a fifth portion of the configuration program corresponding to additional special time of use information.

28. The method of claim 25, further comprising verifying delivery of each portion of the configuration program using a corresponding status flag set at the collector.