Dynamic self-configuring metering network

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application is related by subject matter to U.S. patent application Ser. No. (not yet known) (attorney docket number ABME-0793), filed Jun. 28, 2002, and entitled “Data Collector for an Automated Meter Reading System,” the contents of which are hereby incorporated by reference in their entirety.

FIELD OF THE INVENTION

[0002] The present invention relates to metering systems, and more particularly, to wireless networks for gathering metering data.

BACKGROUND

[0003] The collection of meter data from electrical energy, water, and gas meters has traditionally been performed by human meter-readers. The meter-reader travels to the meter location, which is frequently on the customer's premises, visually inspects the meter, and records the reading. The meter-reader may be prevented from gaining access to the meter as a result of inclement weather or, where the meter is located within the customer's premises, due to an absentee customer. This methodology of meter data collection is labor intensive, prone to human error, and often results in stale and inflexible metering data.

[0004] Some meters have been enhanced to include a one-way radio transmitter for transmitting metering data to a receiving device. A person collecting meter data that is equipped with an appropriate radio receiver need only come into proximity with a meter to read the meter data and need not visually inspect the meter. Thus, a meter-reader may walk or drive by a meter location to take a meter reading. While this represents an improvement over visiting and visually inspecting each meter, it still requires human involvement in the process.

[0005] An automated means for collecting meter data involves a fixed wireless network. Devices such as, for example, repeaters and gateways are permanently affixed on rooftops and pole-tops and strategically positioned to receive data from enhanced meters fitted with radio-transmitters. Data is transmitted from the meters to the repeaters and gateways and ultimately communicated to a central location. While fixed wireless networks greatly reduce human involvement in the process of meter reading, such systems require the installation and maintenance of a fixed network of repeaters, gateways, and servers. Identifying an acceptable location for a repeater or server and physically placing the device in the desired location on top of a building or utility pole is a tedious and labor-intensive operation. Furthermore, each meter that is installed in the network needs to be manually configured to communicate with a particular portion of the established network. When a portion of the network fails to operate as intended, human intervention is typically required to test the effected components and reconfigure the network to return it to operation. Thus, while existing fixed wireless systems have reduced the need for human involvement in the daily collection of meter data, such systems require substantial human investment in planning, installation, and maintenance and are relatively inflexible and difficult to manage.

SUMMARY

[0006] A dynamic self-configuring system for collecting meter data is disclosed herein. In an illustrative embodiment, a plurality of meter devices, which operate to track usage of a service or commodity such as, for example, electricity, water, and gas, are operable to wirelessly communicate. One of the meter devices, which is referred to as a collector, broadcasts messages to identify one or more of the meters with which it can directly communicate. The meters with which the collector is operable to directly communicate may be referred to as level one meters. Data designating these meters as level one meters is stored on the collector and the level one meters.

[0007] The collector communicates instructions to the level one meters to scan for meters that are operable to directly communicate with the level one meters. Meters that directly communicate with the level one meters may be referred to as level two meters. Data identifying the level two meters and the communication path to the level two meters is stored on the collector and the level two meters.

[0008] The collector continues the process of scanning the last defined level of meters for new meters that communicate with the last defined level. This process gradually provides identification of the meters in the network and the paths by which to communicate with each meter. Additionally, when new meters are added to the network, they are identified via subsequent scans.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Other features of systems and methods for gathering metering data are further apparent from the following detailed description of exemplary embodiments taken in conjunction with the accompanying drawings, of which:

[0010]FIG. 1 is a diagram of a wireless system for collecting meter data;

[0011]FIG. 2 depicts a flow chart of a process for exception handling;

[0012]FIGS. 3A and 3B depicts a flow chart of a process for registering nodes with a collector;

[0013]FIG. 4 depicts a flow chart of a process for registering a newly added meter;

[0014]FIG. 5 depicts a flow chart of a process for switching the communication path for a registered node to a new collector;

[0015]FIG. 6 depicts a flow chart of a process for reading usage data;

[0016]FIG. 7 depicts a flow chart of a process for reading data from a one-way meter;

[0017]FIG. 8 depicts a block diagram of a meter suitable for use with the disclosed embodiments; and

[0018]FIG. 9 is a diagram of a general purpose computing device.

DETAILED DESCRIPTION

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

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

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

[0022] System <b>110</b> further comprises collectors <b>116</b>. Collectors <b>116</b> are also meters operable to detect and record usage of a service or commodity such as, for example, electricity, water, or gas. Collectors <b>116</b> comprise an antenna and are operable to send and receive data wirelessly. In particular, collectors <b>116</b> are operable to send data to and receive data from meters <b>114</b>. In an illustrative embodiment, meters <b>114</b> may be, for example, an electrical meter manufactured by ABB Incorporated.

[0023] A collector <b>116</b> and the meters <b>114</b> for which it is configured to receive meter data define a subnet <b>120</b> of system <b>110</b>. For each subnet <b>120</b>, data is collected at collector <b>116</b> and periodically transmitted to communication server <b>122</b>. Communication server <b>122</b> stores the data for analysis and preparation of bills. Communication server <b>122</b> may be a specially programmed general purpose computing system and may communicate with collectors <b>116</b> wirelessly or via a wire line connection such as, for example, a dial-up telephone connection or fixed wire network.

[0024] Thus, each subnet <b>120</b> comprises a collector <b>116</b> and one or more meters <b>114</b>, which may be referred to as nodes of the subnet. Typically, collector <b>116</b> directly communicates with only a subset of the plurality of meters <b>114</b> in the particular subnet. Meters <b>114</b> with which collector <b>116</b> directly communicates may be referred to as level one meters <b>114</b><i>a. </i>The level one meters <b>114</b><i>a </i>are said to be one “hop” from the collector <b>116</b>. Communications between collector <b>116</b> and meters <b>114</b> other than level one meters <b>114</b><i>a </i>are relayed through the level one meters <b>114</b><i>a. </i>Thus, the level one meters <b>114</b><i>a </i>operate as repeaters for communications between collector <b>116</b> and meters <b>114</b> located further away in subnet <b>120</b>.

[0025] Each level one meter <b>114</b><i>a </i>directly communicates with only a subset of the remaining meters <b>114</b> in the subnet <b>120</b>. The meters <b>114</b> with which the level one meters <b>114</b><i>a </i>directly communicate may be referred to as level two meters <b>114</b><i>b. </i>Level two meters <b>114</b><i>b </i>are one “hop” from level one meters <b>114</b><i>a, </i>and therefore two “hops” from collector <b>116</b>. Level two meters <b>114</b><i>b </i>operate as repeaters for communications between the level one meters <b>114</b><i>a </i>and meters <b>114</b> located further away from collector <b>116</b> in the subnet <b>120</b>.

[0026] While only three levels of meters are shown (collector <b>114</b>, first level <b>114</b><i>a, </i>second level <b>114</b><i>b</i>) in FIG. 1, a subnet <b>120</b> may comprise any number of levels of meters <b>114</b>. For example, a subnet <b>120</b> may comprise one level of meters but might also comprise eight or more levels of meters <b>114</b>. In an embodiment wherein a subnet comprises eight levels of meters <b>114</b>, as many as <b>512</b> meters might be registered with a single collector <b>116</b>.

[0027] Each meter <b>114</b> and collector <b>116</b> that is installed in the system <b>110</b> has a unique identifier stored thereon that uniquely identifies the device from all other devices in the system <b>110</b>. Additionally, meters <b>114</b> operating in a subnet <b>120</b> comprise information including the following: data identifying the collector with which the meter is registered; the level in the subnet at which the meter is located; the repeater meter with which the meter communicates to send and receive data to the collector; an identifier indicating whether the meter is a repeater for other nodes in the subnet; and if the meter operates as a repeater, the identifier that uniquely identifies the repeater within the particular subnet, and the number of meters for which it is a repeater. Collectors <b>116</b> have stored thereon all of this same data for all meters <b>114</b> that are registered therewith. Thus, collector <b>116</b> comprises data identifying all nodes registered therewith as well as data identifying the registered path by which data is communicated with each node.

[0028] Generally, collector <b>116</b> and meters <b>114</b> communicate with and amongst one another using any one of several robust wireless techniques such as, for example, frequency hopping spread spectrum (FHSS) and direct sequence spread spectrum (DSSS).

[0029] For most network tasks such as, for example, reading data, collector <b>116</b> communicates with meters <b>114</b> in the subnet <b>120</b> using point-to-point transmissions. For example, a message or instruction from collector <b>116</b> is routed through a defined set of meter hops to the desired meter <b>114</b>. Similarly, a meter <b>114</b> communicates with collector <b>117</b> through the same set of meter hops, but in reverse.

[0030] In some instances, however, collector <b>117</b> needs to quickly communicate information to all meters <b>114</b> located in its subnet <b>120</b>. Accordingly, collector <b>117</b> may issue a broadcast message that is meant to reach all nodes in the subnet <b>120</b>. The broadcast message may be referred to as a “flood broadcast message.” A flood broadcast originates at collector <b>116</b> and propagates through the entire subnet <b>120</b> one level at a time. For example, collector <b>116</b> may transmit a flood broadcast to all first level meters <b>114</b><i>a. </i>The first level meters <b>114</b><i>a </i>that receive the message pick a random time slot and retransmit the broadcast message to second level meters <b>114</b><i>b. </i>Any second level meter <b>114</b><i>b </i>can accept the broadcast, thereby providing better coverage from the collector out to the end point meters. Similarly, the second level meters <b>114</b><i>b </i>that receive the broadcast message pick a random time slot and communicate the broadcast message to third level meters. This process continues out until the end nodes of the subnet. Thus, a broadcast message gradually propagates out the subnet <b>120</b>.

[0031] The flood broadcast packet header contains information to prevent nodes from repeating the flood broadcast packet more than once per level. For example, within a flood broadcast message, a field might exist that indicates to meters/nodes which receive the message, the level of the subnet the message is located; only nodes at that particular level may re-broadcast the message to the next level. If the collector broadcasts a flood message with a level of 1, only level 1 nodes may respond. Prior to re-broadcasting the flood message, the level 1 nodes increment the field to 2 so that only level 2 nodes respond to the broadcast. Information within the flood broadcast packet header ensures that a flood broadcast will eventually die out.

[0032] Generally, a collector <b>116</b> issues a flood broadcast several times, e.g. five times, successively to increase the probability that all meters in the subnet <b>120</b> receive the broadcast. A delay is introduced before each new broadcast to allow the previous broadcast packet time to propagate through all levels of the subnet.

[0033] Meters <b>114</b> may have a clock formed therein. However, meters <b>114</b> often undergo power interruptions that can interfere with the operation of any clock therein. Accordingly, the clocks internal to meters <b>114</b> cannot be relied upon to provide an accurate time reading. Having the correct time is necessary, however, when time of use metering is being employed. Indeed, in an embodiment, time of use schedule data may also be comprised in the same broadcast message as the time. Accordingly, collector <b>116</b> periodically flood broadcasts the real time to meters <b>114</b> in subnet <b>120</b>. Meters <b>114</b> use the time broadcasts to stay synchronized with the rest of the subnet <b>120</b>. In an illustrative embodiment, collector <b>116</b> broadcasts the time every 15 minutes. The broadcasts may be made near the middle of 15 minute clock boundaries that are used in performing load profiling and time of use (TOU) schedules so as to minimize time changes near these boundaries. Maintaining time synchronization is important to the proper operation of the subnet <b>120</b>. Accordingly, lower priority tasks performed by collector <b>116</b> may be delayed while the time broadcasts are performed.

[0034] In an illustrative embodiment, the flood broadcasts transmitting time data may be repeated, for example, five times, so as to increase the probability that all nodes receive the time. Furthermore, where time of use schedule data is communicated in the same transmission as the timing data, the subsequent time transmissions allow a different piece of the time of use schedule to be transmitted to the nodes.

[0035] Exception messages are used in subnet <b>120</b> to transmit unexpected events that occur at meters <b>114</b> to collector <b>116</b>. In an embodiment, the first 4 seconds of every 32-second period are allocated as an exception window for meters <b>114</b> to transmit exception messages. Meters <b>114</b> transmit their exception messages early enough in the exception window so the message has time to propagate to collector <b>116</b> before the end of the exception window. Collector <b>116</b> may process the exceptions after the <b>4</b>-second exception window. Generally, a collector <b>116</b> acknowledges exception messages, and collector <b>116</b> waits until the end of the exception window to send this acknowledgement.

[0036] In an illustrative embodiment, exception messages are configured as one of three different types of exception messages: local exceptions, which are handled directly by the collector <b>116</b> without intervention from communication server <b>122</b>; an immediate exception, which is generally relayed to communication server <b>122</b> under an expedited schedule; and a daily exception, which is communicated to the communication server <b>122</b> on a regular schedule.

[0037]FIG. 2 presents a flowchart of a process employed by collector <b>116</b> for handling these exceptions. At step <b>210</b>, the exception is received at collector <b>116</b>. At step <b>212</b>, collector <b>116</b> identifies the type of exception that has been received. If a local exception has been received, at step <b>214</b>, collector <b>116</b> takes an action to remedy the problem. For example, when collector <b>116</b> receives an exception requesting a node scan request such as discussed below, collector <b>116</b> transmits a command to initiate a scan procedure to the meter <b>114</b> from which the exception was received.

[0038] If an immediate exception type has been received, at step <b>220</b>, collector <b>116</b> makes a record of the exception. An immediate exception might identify, for example, that there has been a power outage. Collector <b>116</b> may log the receipt of the exception in one or more tables or files. In an illustrative example, a record of receipt of an immediate exception is made in a table referred to as the “Immediate Exception Log Table.”

[0039] At step <b>222</b>, collector <b>116</b> waits a set period of time before taking further action with respect to the immediate exception. For example, collector <b>116</b> may wait 64 seconds. This delay period allows the exception to be corrected before communicating the exception to communication server <b>122</b>. For example, where a power outage was the cause of the immediate exception, collector <b>116</b> may wait a set period of time to allow for receipt of a message indicating the power outage has been corrected.

[0040] If at step <b>224</b> the exception has not been corrected, at step <b>226</b>, collector <b>116</b> communicates the immediate exception to communication server <b>122</b>. For example, collector <b>116</b> may initiate a dial-up connection with communication server <b>122</b> and download the exception data. After reporting an immediate exception to communications server <b>122</b>, collector <b>116</b> may delay reporting any additional immediate exceptions for a period of time such as ten minutes. This is to avoid reporting exceptions from other meters <b>114</b> that relate to, or have the same cause as the exception that was just reported.

[0041] If a daily exception was received, at step <b>230</b>, the exception is recorded in a file or a database table. Generally, daily exceptions are occurrences in the subnet <b>120</b> that need to be reported to communication server <b>122</b>, but are not so urgent that they need to be communicated immediately. For example, when collector <b>116</b> registers a new meter <b>114</b> in subnet <b>120</b>, collector <b>116</b> records a daily exception identifying that the registration has taken place. In an illustrative embodiment, the exception is recorded in a database table referred to as the “Daily Exception Log Table.” At step <b>232</b>, collector <b>116</b> communicates the daily exceptions to communications server <b>122</b>. Generally, collector <b>116</b> communicates the daily exceptions once every 24 hours.

[0042] According to an aspect of the disclosed system <b>110</b>, a collector <b>116</b> may dynamically identify meters <b>114</b> that are operable to communicate with it in a subnet <b>120</b> as well as identify more efficient communication paths for previously registered meters. For example, when a collector <b>116</b> is initially brought into system <b>110</b>, it needs to identify and register meters in its subnet <b>120</b>. A “node scan” refers to a process of communication between connectors <b>116</b> and meters <b>114</b> whereby a collector may identify and register new nodes in a subnet <b>120</b> and allow previously registered nodes to switch paths. A collector <b>116</b> can implement a node scan on the entire subnet, referred to as a “full node scan,” or a node scan can be performed on specially identified nodes, referred to as a “node scan retry.”

[0043] A full node scan may be performed, for example, when a collector is first installed. The collector <b>116</b> must identify and register nodes from which it will collect usage data. FIGS. 3A and 3B depict a flow chart of a process for performing a “full node scan.” As shown, at step <b>310</b>, the collector <b>116</b> initiates the node scan by broadcasting a request, which may be referred to as a Node Scan Procedure request. Generally, the Node Scan Procedure request directs that all unregistered meters <b>114</b> or nodes that receive the request respond to the collector <b>116</b>. The request may comprise information such as the unique address of the collector that initiated the procedure. The signal by which collector <b>116</b> transmits this request may have limited strength and therefore is detected at meters <b>114</b> that are in proximity of collector <b>116</b>. Meters <b>114</b> that receive the Node Scan Procedure request respond by transmitting their unique identifier as well as other data.

[0044] Collector <b>116</b> receives a response from one of the meters <b>114</b> at step <b>312</b>. At step <b>313</b>, collector <b>116</b> identifies a received signal strength (RSSI) value for the response from meter <b>114</b>. At step <b>314</b>, collector <b>116</b> stores in memory the meter's <b>114</b> unique identifier along with the corresponding RSSI value.

[0045] Preferably, collector <b>116</b> attempts to register meters <b>114</b> that will have a reliable data communication path. Accordingly, at step <b>316</b>, collector <b>116</b> compares the RSSI value of the node scan response with a selected threshold value. For example, the threshold value may be −60 dBm. RSSI values above this threshold are sufficiently reliable. Collector <b>116</b> maintains a list of meters <b>114</b> that responded but which do not satisfy the RSSI threshold. For example, a database table referred to as the Straggler table may be employed to store for each meter that responded to a Node Scan Response and did not meet the RSSI value, the meter's unique identifier and the RSSI value of the response. Accordingly, if at step <b>316</b> the RSSI value is not greater than the established threshold, at step <b>318</b>, collector <b>116</b> updates its list to include the meter's unique identifier and RS SI value. Thereafter, processing continues at step <b>326</b>.

[0046] If at step <b>316</b>, the RSSI value exceeds the threshold, at step <b>324</b>, collector <b>116</b> registers the node. Registering a meter <b>114</b> comprises updating a list of the registered nodes at collector <b>116</b>. For example, the list may be updated to identify the meter's system-wide unique identifier and the communication path to the node. Collector <b>116</b> also records the meter's level in the subnet (i.e. whether the meter is a level one node, level two node, etc.), whether the node operates as a repeater, and if so, the number of meters for which it operates as a repeater. Upon initialization, the data indicates the node is not a repeater and the number of meters for which it operates as a repeater is zero. The registration process further comprises transmitting registration information to the meter <b>114</b>. For example, collector <b>116</b> forwards to meter <b>114</b> an indication that it is registered, the unique identifier of the collector with which it is registered, the level the meter exists at in the subnet, and the unique identifier of the meter with which it should communicate data. The meter stores this data and begins to operate as part of the subnet by responding to commands from its collector <b>116</b>.

[0047] At step <b>326</b>, collector <b>116</b> determines if there are additional responses to the node scan request. If so, processing continues at step <b>314</b>.

[0048] Steps <b>310</b> through <b>326</b> may be performed several times so as to insure that all meters <b>114</b> that may receive the Node Scan Procedure, have an opportunity for their response to be received at collector <b>116</b>. Accordingly, at step <b>328</b>, collector <b>116</b> determines whether the Node Scan should be implemented again. Generally, this is determined by comparing the number of times the steps have been completed with a predefined limit. If the limit has not been met, processing continues at step <b>310</b>. If the limit has been met, a first portion of the node scan procedure is complete. It is presumed that all first level meters <b>114</b> have been identified and registered at this point in the process. The Straggler list may identify one or more meters <b>114</b> that did not satisfy the RSSI threshold. The node scan process continues by performing a similar process as that described above at each of the now registered level one nodes. This process results in the identification and registration of level two nodes. After the level two nodes are identified, a similar node scan process is performed at the level two nodes to identify level three nodes, and so on.

[0049]FIG. 3B is a flow chart of the process for identifying and registering meters located above the level one meters. At step <b>340</b>, collector <b>116</b> transmits a command, which may be referred to as an Initiate Node Scan Procedure, to the first of the meters <b>114</b> registered at steps <b>310</b> through <b>328</b>, to initiate a node scan process at the particular meter <b>114</b>. The request comprises several data items that the receiving meter may use in completing the node scan. For example, the request may comprise the number of timeslots available for responding nodes, the unique address of the collector that initiated the request, and a measure of the reliability of the communications between the target node and the collector. As described below in connection with FIG. 4, the measure of reliability is employed during a process for identifying more reliable paths for previously registered nodes.

[0050] The meter that receives the Initiate Node Scan Response request responds by performing a node scan process similar to that described above at steps <b>310</b> through <b>328</b>. More specifically, the meter broadcasts a request to which all unregistered nodes respond. The request comprises the number of timeslots available for responding nodes (which is used to set the period for the node to wait for responses), the unique address of the collector that initiated the node scan procedure, a measure of the reliability of the communications between the sending node and the collector (which is used in the process of determining whether a meter's path may be switched as defined below in connection with FIG. 5), the level within the subnet of the node sending the request, and an RSSI threshold (which is used in the process of determining whether a registered meter's path may be switched as described below in connection with FIG. 4). The meter issuing the node scan request waits for and receives responses. For each response, the meter stores in memory the unique identifier and the RSSI value of the response. At step <b>342</b>, collector <b>116</b> waits while the response are collected at the meter that issued the node scan. At step <b>344</b>, collector <b>116</b> retrieves the node information that has been collected by the meter. At step <b>346</b>, collector <b>116</b> parses the information and selects one of the meters or potential nodes in the list of retrieved data.

[0051] Collector <b>116</b> attempts to register meters <b>114</b> that will have a reliable data communication path. Accordingly, at step <b>348</b>, collector <b>116</b> compares the RSSI value for the selected meter <b>114</b> with a selected threshold value. If the RSSI value is not greater than the threshold value, at step <b>350</b>, collector <b>116</b> determines if the particular meter was previously identified as having responded to a Node Scan Response request but having not met the RSSI threshold. Specifically, collector <b>116</b> may refer to its Straggler table or similar file where it maintains a list of meters <b>114</b> that meet this criteria. If so, at step <b>352</b>, collector <b>116</b> compares the RSSI value with the previously stored value. If the new RSSI value is greater than the previous value, at step <b>354</b>, collector updates the Straggler table to identify the new RSSI value and the new communication path. If at step <b>352</b>, the new RSSI value is not greater than the previous value, processing continues at step <b>362</b>. If at step <b>350</b>, it is determined that the particular meter <b>114</b> is not in the Straggler table, processing continues at step <b>354</b>, where the Straggler table is updated to reflect the meter identifier, the communication path to this meter and the RSSI value. Thereafter, processing continues at step <b>362</b>.

[0052] If at step <b>348</b>, the RSSI value exceeded the threshold, at step <b>360</b>, collector <b>116</b> registers the node. Registering a meter <b>114</b> comprises updating a list of the registered nodes at collector <b>116</b>. For example, the list may be updated to identify the meter's unique identifier and the level of the meter in the subnet, i.e. whether the meter is a level one node, level two node, etc. Additionally, the collector's <b>116</b> registration information is updated to reflect that the meter <b>114</b> from which the scan process was initiated is identified as a repeater for the newly registered node. The registration process further comprises transmitting information to the newly registered meter as well as the meter that will serve as a repeater for the newly added node. For example, the node that issued the node scan response request is updated to identify that it operates as a repeater and, if it was previously registered as a repeater, increments a data item identifying the number of nodes for which it serves as a repeater. Thereafter, collector <b>116</b> forwards to the newly registered meter an indication that it is registered, an identification of the collector <b>116</b> with which it is registered, the level the meter exists at in the subnet, and the unique identifier of the node with which it communicates to forward information to collector <b>116</b>.

[0053] At step <b>362</b>, collector <b>116</b> determines if there are additional nodes identified in the information retrieved from the meter <b>114</b> that performed the node scan request. If so, processing continues at step <b>346</b>.

[0054] If at step <b>362</b>, there are no potential nodes to be evaluated, at step <b>364</b>, collector <b>116</b> determines if there are other registered nodes on the same level that have not been directed to perform a node scan. For example, if level 1 nodes are being scanned for potential level 2 nodes, at step <b>364</b> collector <b>116</b> determines if there are any level 1 nodes that have not yet performed a node scan procedure. If so, processing continues at step <b>340</b> wherein collector requests that a node scan procedure be performed at the node.

[0055] If at step <b>364</b>, all nodes at the level of the subnet under evaluation have been reviewed, processing continues at step <b>368</b>, with collector <b>116</b> determining if there are registered meters at the next level of the subnet. If so, processing continues at step <b>340</b> with node scans being performed at this next level.

[0056] If at step <b>368</b> there are no registered nodes at the next higher level, at step <b>370</b>, collector <b>116</b> registers the nodes identified in the list of meters that have responded but did not meet the RSSI threshold. At this point in the process, presumably, the list comprises the best path identified for each of the unregistered meters that responded, even if that path does not meet the desired RSSI threshold. If during operation of the network, a meter registered in this manner fails to perform adequately, it may be assigned a different path or possibly to a different collector as described below.

[0057] As previously mentioned, a full node scan may be performed when a collector <b>116</b> is first introduced to a network. At the conclusion of the full node scan, a collector <b>116</b> will have registered a set of meters <b>114</b> with which it communicates and reads metering data. Full node scans might be periodically performed by an installed collector to identify new meters <b>114</b> that have been brought on-line since the last node scan and to allow registered meters to switch to a different path.

[0058] In addition to the full node scan, collector <b>116</b> may also perform a process of scanning specific meters <b>114</b> in the subnet <b>120</b>, which is referred to as a “node scan retry.” For example, collector <b>116</b> may issue a specific request to a meter <b>114</b> to perform a node scan outside of a full node scan when on a previous attempt to scan the node, the collector <b>116</b> was unable to confirm that the particular meter <b>114</b> received the node scan request. Also, a collector <b>116</b> may request a node scan retry of a meter <b>114</b> when during the course of a full node scan the collector <b>116</b> was unable to read the node scan data from the meter <b>114</b>. Similarly, a node scan retry will be performed when an exception procedure requesting an immediate node scan is received from a meter <b>114</b>.

[0059] According to an aspect of the disclosed embodiment, system <b>110</b> automatically reconfigures to accommodate a new meter <b>114</b> that may be added. More particularly, the system identifies that the new meter has begun operating and identifies a path to a collector <b>116</b> that will become responsible for collecting the metering data. A flow chart of a process for adding a new meter is depicted in FIG. 4. As shown, at step <b>410</b>, the new meter broadcasts an indication that it is unregistered. In one embodiment, this broadcast might be, for example, embedded in, or relayed as part of a request for an update of the real time as described above. At step <b>412</b>, the broadcast is received at one of the registered meters <b>114</b> in proximity to the meter that is attempting to register. At step <b>414</b>, the registered meter <b>114</b> forwards the time to the meter that is attempting to register. At step <b>416</b>, the registered node also transmits an exception request to its collector <b>116</b> requesting that the collector <b>116</b> implement a node scan, which presumably will locate and register the new meter. At step <b>418</b>, the collector <b>116</b> transmits a request that the registered node perform a node scan. At step <b>420</b>, the registered node performs the node scan during which it requests that all unregistered nodes respond. At step <b>422</b>, the newly added, unregistered meter responds to the node scan. At step <b>424</b>, the unique identifier of the newly added node along with the RSSI value of its response are stored on the registered node. At step <b>426</b>, collector <b>116</b> retrieves the response data. If at step <b>428</b> the RSSI value of the response from the new meter exceeds the established RSSI threshold, at step <b>430</b> collector <b>116</b> updates its data files to identify the new meter as being registered and transmits a registration notification to the new meter. If at step <b>428</b> the RSSI value does not exceed the threshold, the unique identifier is added to the list of unregistered nodes, at step <b>432</b>. The newly added meter will continue to broadcast that it is unregistered and ultimately will be registered through a meter with which it satisfies the RSSI threshold.

[0060] A collector <b>116</b> periodically retrieves meter data from the meters that are registered with it. For example, meter data may be retrieved from a meter every 4 hours. Where there is a problem with reading the meter data on the regularly scheduled interval, the collector will try to read the data again before the next regularly scheduled interval. Nevertheless, there may be instances wherein the collector <b>116</b> is unable to read metering data from a particular meter <b>114</b> for a prolonged period of time. The meters <b>114</b> store an indication of when they are read by collector <b>116</b> and keep track of the time since their data has last been collected by the collector <b>116</b>. If the length of time since the last reading exceeds a defined threshold such as for example, 18 hours, presumably a problem has arisen in the communication path between the particular meter <b>114</b> and the collector <b>116</b>. Accordingly, the meter <b>114</b> changes its status to that of an unregistered meter and attempts to locate a new path to a collector <b>116</b> via the process described above in connection with FIG. 3. Thus, the exemplary system is operable to dynamically reconfigure itself to address inadequacies in the system.

[0061] In some instances, while a collector <b>116</b> may be able to retrieve data from a registered meter <b>114</b> occasionally, the level of success in reading the meter may be inadequate. For example, if a collector <b>116</b> attempts to read meter data from a meter <b>114</b> every 4 hours but is able to read the data, for example, only 70 percent of the time or less, it may be desirable to find a more reliable path for reading the data from that particular meter. Where the frequency of reading data from a meter <b>114</b> falls below a desired frequency, the collector <b>116</b> transmits a message to the meter <b>114</b> to respond to node scans going forward. The meter <b>114</b> remains registered but will respond to node scans such as are described above in connection with FIG. 3. If the meter <b>114</b> responds to a node scan procedure, the collector <b>116</b> recognizes the response as originating from a registered meter. The collector <b>116</b> verifies that the RSSI value of the node scan response exceeds the established threshold. If it does not, the potential path is not acceptable. However, if the RSSI threshold is met, the collector <b>116</b> initiates a qualification procedure whereby it makes several attempts to reach the meter through the potential path. If the collector is successful in establishing communication with the meter through the potential path more than an acceptable percentage of the time, e.g. 80 percent, then the collector registers the meter in the new path. The registration process comprises updating the collector <b>116</b> and meter <b>114</b> with data identifying the repeater with which the meter <b>114</b> will communicate. Additionally, if the repeater is has not previously performed the operation of a repeater, the repeater would need to be updated to identify that it is a repeater. Likewise, the repeater with which the meter previously communicated is updated to identify that it is no longer a repeater for the particular meter <b>114</b>.

[0062] In some instances, a more reliable communication path for a meter may exist through a collector other than that with which the meter is registered. A meter may automatically recognize the existence of the more reliable communication path, switch collectors, and notify the previous collector that the change has taken place. FIG. 5 provides a flow chart of a method for switching the registration of a meter from a first collector to a second collector. As shown, at step <b>510</b>, a registered meter <b>114</b> receives a node scan request from a collector <b>116</b> other than that with which the meter is registered. Typically, a registered meter <b>114</b> does not respond to node scan requests. However, if the request is likely to result in a more reliable transmission path, even a registered meter may respond. Accordingly, at step <b>512</b>, the meter determines if the new collector offers a potentially more reliable transmission path. For example, the meter <b>114</b> may determine if the path to the potential new collector <b>116</b> comprises fewer hops than the path to the collector with which the meter is registered. If not, the path may not be more reliable and the meter <b>114</b> will not respond to the node scan. The meter <b>114</b> might also determine if the RSSI of the node scan packet exceeds an RSSI threshold identified in the node scan information. If so, the new collector may offer a more reliable transmission path for meter data. If not, the transmission path is not acceptable and the meter does not respond. Additionally, if the reliability of communication between the potential new collector and the repeater that would service the meter meets a threshold established when the repeater was registered with its existing collector, the communication path to the new collector may be more reliable. If the reliability does not exceed this threshold, however, the meter <b>114</b> does not respond to the node scan.

[0063] If at step <b>512</b>, it is determined that the path to the new collector may be better than the path to its existing collector, at step <b>514</b>, the meter <b>114</b> responds to the node scan. Included in the response is information regarding any nodes for which the particular meter may operate as a repeater. For example, the response might identify the number of nodes for which the meter serves as a repeater.

[0064] At step <b>516</b>, collector <b>116</b> determines if it has the capacity to service the meter and any meters for which it operates as a repeater. If not, the collector <b>116</b> does not respond to the meter that is attempting to change collectors.

[0065] If, however, the collector <b>116</b> determines that it has capacity to service the meter <b>5114</b>, at step <b>518</b>, the collector <b>116</b> stores registration information about the meter <b>114</b>. At step <b>520</b>, collector <b>116</b> transmits a registration command to meter <b>114</b>. At step <b>522</b>, the meter <b>114</b> updates its registration data to identify that it is now registered with the new collector. At step <b>524</b>, collector <b>116</b> communicates instruction to the meter <b>114</b> to initiate a node scan request. Nodes that are unregistered, or that had previously used meter <b>114</b> as a repeater respond to the request to identify themselves to collector <b>116</b>. The collector registers these nodes as is described above in connection with registering new meters/nodes.

[0066] Under some circumstances it may be necessary to change a collector. For example, a collector may be malfunctioning, and need to be taken off-line. Accordingly, a new communication path must be provided for collecting meter data from the meters serviced by the particular collector. The process of replacing a collector is performed by broadcasting a message to unregister, usually from a replacement collector, to all of the meters that are registered with the collector that is being removed from service. According to an aspect of the disclosed embodiment, registered meters may be programmed to only respond to commands from the collector with which they are registered. Accordingly, the command to unregister may comprise the unique identifier of the collector that is being replaced. In response to the command to unregister, the meters begin to operate as unregistered meters and respond to node scan requests. To allow the unregistered command to propagate through the subnet, when a node receives the command it will not unregister immediately, but rather remain registered for a defined period, which may be referred to as the “Time to Live”. During this time to live period, the nodes continue to respond to application layer and immediate s retries allowing the unregistration command to propagate to all nodes in the subnet. Ultimately, the meters register with the replacement collector as described above in connection with FIG. 3.

[0067] One of collector's <b>116</b> main responsibilities within subnet <b>120</b> is to retrieve metering data from meters <b>114</b>. The self-configuring and self-healing characteristics of system <b>110</b> provide that collectors <b>116</b> have improved reliability in reading usage data. Generally, meters <b>114</b> store data regarding usage of electricity, gas, water, etc. in memory. Collector <b>116</b> periodically retrieves this data from nodes in its subnet <b>120</b>. In an embodiment, collector <b>116</b> has as a goal to obtain at least one successful read of the metering data per day from each node in its subnet. Collector <b>116</b> attempts to retrieve the data from all nodes in its subnet <b>120</b> at a configurable periodicity. For example, collector <b>116</b> may be configured to attempt to retrieve metering data from meters <b>114</b> in its subnet <b>120</b> once every 4 hours. FIG. 6 depicts a flow chart of a process for retrieving data from meters <b>114</b> in a subnet <b>120</b>. As shown, at step <b>610</b>, collector <b>116</b> identifies one of the meters <b>114</b> in its subnet <b>120</b>. For example, collector <b>116</b> reviews a list of registered nodes and identifies one for reading. At step <b>612</b>, collector <b>116</b> communicates a command to the particular meter <b>114</b> that it forward its metering data to the collector <b>116</b>. If at step <b>614</b>, the meter reading is successful and the data is received at collector <b>116</b>, at step <b>616</b> collector <b>116</b> determines if there are other meters that have not been read during the present reading session. If so, processing continues at step <b>610</b>. However, if all of the meters <b>114</b> in subnet <b>120</b> have been read, at step <b>618</b>, collector waits a defined length of time, such as, for example, 4 hours, before attempting another read.

[0068] If at step <b>614</b>, the meter data was not received at collector <b>116</b>, at step <b>620</b> collector <b>116</b> begins a retry procedure wherein it attempts to retry the data read from the particular meter. Collector <b>116</b> continues to attempt to read the data from the node until either the data is read or the next subnet reading takes place. In an embodiment, collector <b>116</b> attempts to read the data every 60 minutes. Thus, wherein a subnet reading is taken every 4 hours, collector <b>116</b> may issue three retries between subnet readings.

[0069] The inability to read metering data may be the result of communication failures that can take place at the packet communication level. For example, if for each hop the probability of successful communications is 95%, a level 8 node requires 16 message hops, which would result in a 44% probability a successful round trip message. If 2 immediate retries are used for each hop, the per hop probability increases from 95% to 99.98% and the probability of a successful round trip message increases to 99.8%. Accordingly, in an embodiment of the disclosed system, with each successive retry to read data from a node, the number of packet level retries increases. For example, if during a normal read attempt one packet level retry is undertaken, when an application level retry to read the data is made by the collector, two or more packet level retries may be implemented. Thus, as the number of application level retries increases, so does the number of packet level retries. Furthermore, the number of packet level retries varies according to the level at which the particular meter <b>114</b> exists in the subnet <b>120</b>. The higher the level, the greater the number of packet level retries. The table below lists exemplary packet level retries for various subnet levels and various numbers of prior application level retry attempts. <tables id="TABLE-US-00001" num="1"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="77PT" align="left" /><colspec colname="1" colwidth="140PT" align="center" /><tbody valign="top"><row><entry /><entry /></row><row><entry /><entry namest="OFFSET" nameend="1" align="center" rowsep="1" /></row><row><entry /><entry>Application Layer Attempt</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="OFFSET" colwidth="77PT" align="left" /><colspec colname="1" colwidth="63PT" align="center" /><colspec colname="2" colwidth="14PT" align="center" /><colspec colname="3" colwidth="63PT" align="center" /><tbody valign="top"><row><entry /><entry>1</entry><entry>2</entry><entry>≧3</entry></row><row><entry /><entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="49PT" align="left" /><colspec colname="2" colwidth="63PT" align="center" /><colspec colname="3" colwidth="14PT" align="center" /><colspec colname="4" colwidth="63PT" align="center" /><tbody valign="top"><row><entry /><entry>Levels 1 and 2</entry><entry>1</entry><entry>2</entry><entry>3</entry></row><row><entry /><entry>Levels 3 and 4</entry><entry>2</entry><entry>3</entry><entry>4</entry></row><row><entry /><entry>Levels 5-6</entry><entry>2</entry><entry>3</entry><entry>4</entry></row><row><entry /><entry>Levels &gt;6</entry><entry>3</entry><entry>4</entry><entry>5</entry></row><row><entry /><entry namest="OFFSET" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0070] In an embodiment of system <b>120</b>, meters <b>114</b> are typically two-way meters—i.e. they are operable to both receive and transmit data. However, one-way meters that are operable only to transmit and not receive data may also be deployed in the system <b>110</b>. FIG. 7 provides a flow chart of a process for reading data from one-way meters deployed in the system. As shown, at step <b>710</b> a one-way meter broadcasts their usage data. At step <b>712</b>, this data is received at one or more two-way meters that are in proximity to the one-way meter. At step <b>714</b>, the data is stored on the two-way meter, and designated as having been received from the one-way meter. At step <b>716</b>, the data from the one-way meter is communicated to the collector with which the two-way meter is registered. For example, when the collector reads the two-way meter data, it recognizes the existence of meter data from the one-way meter and reads it as well. At step <b>718</b>, after the data from the one-way meter has been read, it is removed from memory.

[0071] A block diagram for an exemplary meter device operable to perform as meter <b>114</b> or collector <b>116</b> as described above is depicted in FIG. 8. As shown, meter device <b>810</b> comprises metering electronics <b>812</b> for physically measuring the amount of a service or commodity that is used, and wireless communications electronics <b>814</b> for transmitting and receiving data to other meter devices. Device <b>810</b> further comprises memory <b>816</b> for storing data and executable instructions for performing methods as described above. Processor <b>818</b> is operable to execute the instructions stored in memory <b>816</b>. Device <b>810</b> may further comprise visual display <b>818</b> for displaying metering data at device <b>810</b>. Wire-based communications electronics <b>820</b> provides the capability to communicate with device <b>810</b> via means other than wirelessly. For example, wire-based communications electronics <b>820</b> may comprise a modem for communicating over telephone lines or a network protocol transceiver for communicating over a dedicated local area or wide area network.

[0072]FIG. 9 is a diagram of a generic computing device, which may be operable to perform the steps described above as being performed by communications server <b>122</b>. As shown in FIG. 9, communications server <b>922</b> includes processor <b>922</b>, system memory <b>924</b>, and system bus <b>926</b> that couples various system components including system memory <b>924</b> to processor <b>922</b>. System memory <b>924</b> may include read-only memory (ROM) and/or random access memory (RAM). Computing device <b>920</b> may further include hard-drive <b>928</b>, which provides storage for computer readable instructions, data structures, program modules, data, and the like. A user (not shown) may enter commands and information into the computing device <b>920</b> through input devices such as keyboard <b>940</b> or mouse <b>942</b>. A display device <b>944</b>, such as a monitor, a flat panel display, or the like is also connected to computing device <b>920</b>. Communications device <b>943</b>, which may be a modem, network interface card, or the like, provides for communications over a network. System memory <b>924</b> and/or hard-drive <b>928</b> may be loaded with any one of several computer operating systems such as WINDOWS NT operating system, WINDOWS 2000 operating system, LINUX operating system, and the like.

[0073] Those skilled in the art understand that processor readable instructions for implementing the above-described processes, such as those described with reference to FIGS. 2 through 7 can be generated and stored in processor-readable memory and processor-readable media such as a magnetic disk or CD-ROM. Further, a computing system such as that described with reference to FIG. 9 may be arranged with metering devices such as that described in FIG. 8, and the devices loaded with processor-readable instructions for performing the above described processes. Specifically, referring to FIGS. 8 and 9, processors <b>922</b> and <b>818</b> may be programmed to operate in accordance with the above-described processes.

[0074] Thus, a dynamic self-configuring system for gathering metering data has been disclosed. This novel system and the methods performed therein provide a reliable and efficient means to collect metering data with minimal human intervention. Furthermore, the system requires minimal human interaction to configure and upgrade efficiencies.

[0075] 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, while communication server <b>122</b> has been described as communicating with collectors <b>116</b> via a dial-up connection, the communication may take place wirelessly. Accordingly, reference should be made to the following claims as describing the scope of disclosed embodiments.