Dynamic self-configuring metering network

• US 7,145,474 B2
• Filed: 08/27/2004
• Issued: 12/05/2006
• Est. Priority Date: 06/27/2002
• Status: Expired due to Term

• Current Assignee: Elster Electricity LLC (Honeywell International Inc.)
• Original Assignee: Elster Electricity LLC (Honeywell International Inc.)
• Inventors: Hodges, Eugene W., Shuey, Kenneth C., Hemminger, Rodney C., Mason, Robert T. Jr.
• Primary Examiner(s): Garber, Wendy R.
• Assistant Examiner(s): Dang, Hung Q
• Application Number:
  US10/928,825
• Publication Number:
  US 20050083210A1
• Time in Patent Office: 830 Days
• Field of Search: 340/870.02, 340/10.41, 340/3.51, 340/870.01, 340/870.03, 340/870.16, 702/62
• US Class Current: 340/870.03
• CPC Class Codes: H04Q 2209/60 for transmitting utility meters data, i.e. transmission of data from the reader of the utility meter
• CPC Class Codes: H04Q 9/00 Arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom

Abstract

A dynamic self-configuring system for collecting metering data comprises a collector meter. The collector meter scans for meters that are operable to directly communicate with the collector and registers such meters as level one meters. The collector transmits instructions to the level one meters to scan for meters that are operable to directly communicate with the level one meters. The collector registers meters that respond as level two meters.

Claims

1. In a network having a collector that receives data from nodes and communicates the data to a communication server, a method of retrieving data from a node, comprising:

examining a list of nodes registered with said collector;

identifying a registered node with which communication is to be established;

reading data from said registered node by sending a request to said node to forward said data to said collector;

determining if said request resulted in a successful data read from said registered node;

retrying reading data from said registered node if said request was not successful;

increasing a number of packet level retries for each successive retry to read data from said registered node; and

storing said data at said collector.

2. The method of claim 1, further comprising:

determining if additional data is to be read from additional registered nodes; and

reading said additional data from said additional registered nodes.

3. The method of claim 2, further comprising:

determining if said additional data has been read from all registered nodes registered with said collector; and

waiting a predetermined time period before again reading from said registered nodes.

4. The method of claim 1, wherein said retrying is performed until the data is read or a predetermined subnet reading interval.

5. The method of claim 4, wherein said predetermined subnet reading interval is approximately 4 hours.

6. The method of claim 1, wherein said retrying occurs periodically.

7. The method of claim 1, wherein said nodes are organized into levels, and the method further comprising:

increasing said number of packet level retries in accordance with an increasingly higher level to which said registered node is assigned.

8. The method of claim 1, wherein said retrying said reading is an application level retry made by said collector, said method further comprising increasing packet level retries with each increasing application level retry.

9. In a collector that receives data from nodes and communicates the data to a communication server, said collector maintaining a list of registered nodes with which said collector communicates, and said nodes being organized into levels within a subnet that communicates with said collector, a method of reading data from nodes within said subnet, comprising:

identifying a registered node with which communication is to be established from said list of registered nodes;

requesting data from said registered node;

determining if data was successfully received from said registered node;

retrying requesting data from said node if said data was not successfully received;

increasing a number of packet level retries for each successive retry to request data from said registered node;

receiving said data; and

storing said data at said collector.

10. The method of claim 9, further comprising:

determining if additional data is to be read from additional registered nodes; and

reading said additional data from said additional registered nodes.

11. The method of claim 10, further comprising:

determining if said additional data has been read from all registered nodes registered with said collector; and

waiting a predetermined time period before again reading from said registered nodes.

12. The method of claim 9, wherein said retrying is performed until the data is read or a predetermined subnet reading interval.

13. The method of claim 12, wherein said predetermined subnet reading interval is approximately 4 hours.

14. The method of claim 9, wherein said retrying occurs periodically.

15. The method of claim 9, further comprising:

increasing said number of packet level retries in accordance with an increasingly higher level to which said registered node is assigned.

16. The method of claim 9, wherein said retrying is an application level retry made by said collector, said method further comprising increasing packet level retries with each increasing application level retry.