Abstract: Techniques for path selection in a network include a first node in a mesh network receiving, from a second node in the mesh network, a first battery life metric for a path through the mesh network, determining a value representing a remaining battery life of the first node, calculating a second battery life metric based on at least one of the first battery life metric for the path or the value representing the remaining battery life for the first node, and transmitting, to a third node in the mesh network, the second battery life metric.

Abstract: Techniques for path selection in a network include a first node in a mesh network receiving, from a second node in the mesh network, a first battery life metric for a path through the mesh network, determining a value representing a remaining battery life of the first node, calculating a second battery life metric based on at least one of the first battery life metric for the path or the value representing the remaining battery life for the first node, and transmitting, to a third node in the mesh network, the second battery life metric.

Abstract: A wireless network includes nodes configured to implement an improved parent and path selection process to efficiently and reliably manage energy consumption of a battery powered device node. When a given node selects a path, the node transmits requests to multiple potential parent nodes. Each potential parent node transmits a metric that is indicative of the remaining battery life of the nodes in the path that includes the respective potential parent node. The given node then selects a parent node, and corresponding path, based on the metrics. More specifically, the given node selects a path, where at least one node on the selected path is less likely to prematurely exhaust the remaining battery life of the node, relative to the nodes in the other potential paths. As a result, the given node selects a path that optimizes battery consumption of the various battery powered nodes in the wireless network.

Abstract: A data collection device capable of communicating with an endpoint device over a network comprises a first communication means for low data rate messaging, a second communication means for high data rate messaging, and a controller configured to send a wake-up command including a request for data to the endpoint device at a low data rate via the first communication means, the wake-up command requiring the requested data to be transmitted at a high data rate, and receive the requested data from the endpoint device at the high data rate via the second communication means. When transmission via a high data rate is not required, data may be transmitted to the data collection device at the low data rate via the first communication means. The wake-up command may involve a regularly scheduled request for data, an unscheduled request for data, and/or an alarm event. Various methodologies are also disclosed.

Abstract: A wireless network includes nodes configured to implement an improved parent and path selection process to efficiently and reliably manage energy consumption of a battery powered device node. When a given node selects a path, the node transmits requests to multiple potential parent nodes. Each potential parent node transmits a metric that is indicative of the remaining battery life of the nodes in the path that includes the respective potential parent node. The given node then selects a parent node, and corresponding path, based on the metrics. More specifically, the given node selects a path, where at least one node on the selected path is less likely to prematurely exhaust the remaining battery life of the node, relative to the nodes in the other potential paths. As a result, the given node selects a path that optimizes battery consumption of the various battery powered nodes in the wireless network.

Abstract: An advanced metering infrastructure may be configured for automated meter reading, such as of utility (electric, natural gas, etc.) meters. Within a network, a data collector communicates with, and receives meter data from, a plurality of endpoints. Firmware on the endpoints may be updated by transmission, from the data collector, of a new firmware image. In one example, the data collector sends an announcement of a firmware update to the plurality of endpoints. At a time indicated by the announcement, the data collector multicasts the firmware update a plurality of times. The data collector then receives indications from a plurality of endpoints that did not successfully receive all blocks of the multicast firmware update. In response, the data collector sends missing blocks to the plurality of endpoints according to the indications.

Abstract: A data collection device capable of communicating with an endpoint device over a network comprises a first communication means for low data rate messaging, a second communication means for high data rate messaging, and a controller configured to send a wake-up command including a request for data to the endpoint device at a low data rate via the first communication means, the wake-up command requiring the requested data to be transmitted at a high data rate, and receive the requested data from the endpoint device at the high data rate via the second communication means. When transmission via a high data rate is not required, data may be transmitted to the data collection device at the low data rate via the first communication means. The wake-up command may involve a regularly scheduled request for data, an unscheduled request for data, and/or an alarm event. Various methodologies are also disclosed.

Abstract: An advanced metering infrastructure may be configured for automated meter reading, such as of utility (electric, natural gas, etc.) meters. Within a network, a data collector communicates with, and receives meter data from, a plurality of endpoints. Firmware on the endpoints may be updated by transmission, from the data collector, of a new firmware image. In one example, the data collector sends an announcement of a firmware update to the plurality of endpoints. At a time indicated by the announcement, the data collector multicasts the firmware update a plurality of times. The data collector then receives indications from a plurality of endpoints that did not successfully receive all blocks of the multicast firmware update. In response, the data collector sends missing blocks to the plurality of endpoints according to the indications.

Abstract: An endpoint device capable of communicating with a data collection device comprises a first communication subsystem for low data rate messaging, a second communication subsystem for high data rate messaging, and a controller in communication with the first and second communication subsystems, where the first communication subsystem may be used as a primary means of communications with the data collection device, and the second communication subsystem may be used as needed for high data rate communications with the data collection device. The controller may turn on the second communication subsystem for scheduled or unscheduled transfer of data at a high data rate, in response to receiving a wake-up command from the data collection device, in response to receiving an alarm event at the endpoint device, etc. A wake-up command may include a request for data between scheduled data transfers, a parameter change request, etc. Various methodologies are also disclosed.

Abstract: An advanced metering infrastructure may be configured for automated meter reading, such as of utility (electric, natural gas, etc.) meters. Within a network, a data collector communicates with, and receives meter data from, a plurality of endpoints. Firmware on the endpoints may be updated by transmission, from the data collector, of a new firmware image. In one example, the data collector sends an announcement of a firmware update to the plurality of endpoints. At a time indicated by the announcement, the data collector multicasts the firmware update a plurality of times. The data collector then receives indications from a plurality of endpoints that did not successfully receive all blocks of the multicast firmware update. In response, the data collector sends missing blocks to the plurality of endpoints according to the indications.

Abstract: To determine network coverage of a device within a network a user may send an instruction to the device using a mobile configuration tool of a mobile device. Upon receiving the instruction, the device of which the network coverage is to be determined may broadcast a message using a standard protocol, and listen to one or more responses from other devices in the network. In response to receiving the one or more responses, the device at issue may relay the one or more responses, or a processing result of the network coverage (determined based on the one or more responses) to the mobile configuration tool for display to the user. The user may determine whether the network coverage of that device meets one or more network coverage criteria and, if not, may take some corrective action.

Abstract: An endpoint device capable of communicating with a data collection device comprises a first communication subsystem for low data rate messaging, a second communication subsystem for high data rate messaging, and a controller in communication with the first and second communication subsystems, where the first communication subsystem may be used as a primary means of communications with the data collection device, and the second communication subsystem may be used as needed for high data rate communications with the data collection device. The controller may turn on the second communication subsystem for scheduled or unscheduled transfer of data at a high data rate, in response to receiving a wake-up command from the data collection device, in response to receiving an alarm event at the endpoint device, etc. A wake-up command may include a request for data between scheduled data transfers, a parameter change request, etc. Various methodologies are also disclosed.

Abstract: Collection of resource consumption data may be coordinated by designating, for each endpoint in a utility communication network, a single data collector to be responsible for reporting resource consumption data of the respective endpoints to a head-end computing device. If the head-end computing device does not receive resource consumption data from one or more endpoints, the head-end computing device may request the missing resource consumption data from one or more secondary or tertiary data collectors that receive resource consumption data from the one or more endpoints. Additionally, if a data collector is missing resource consumption data from an endpoint during a reporting period, upon receiving resource consumption data from the endpoint during a subsequent reporting period, the data collector may request the missing resource consumption data.

Abstract: Data of a utility node that is unreliably heard may be relayed through another utility node. In some examples, utility nodes of a star network may attempt to transmit data to a collector, a repeater, a relay, a router, or a mobile device. When it is determined that a utility node is unable to reliably transmit data, a relay relationship may be established so that data of the unreliable utility node is relayed through the network.

Abstract: An advanced metering infrastructure may be configured for automated meter reading, such as of utility (electric, natural gas, etc.) meters. Within a network, a data collector communicates with, and receives meter data from, a plurality of endpoints. Firmware on the endpoints may be updated by transmission, from the data collector, of a new firmware image. In one example, the data collector sends an announcement of a firmware update to the plurality of endpoints. At a time indicated by the announcement, the data collector multicasts the firmware update a plurality of times. The data collector then receives indications from a plurality of endpoints that did not successfully receive all blocks of the multicast firmware update. In response, the data collector sends missing blocks to the plurality of endpoints according to the indications.

Abstract: A utility company may schedule when and how endpoints report resource consumption data based on relative priorities of endpoints or the customers associated therewith. By associating endpoints with one of multiple different quality of service (QoS) levels, and sending each endpoint a reporting schedule based on its respective QoS level, the utility company may configure prioritized reporting of resource consumption data by endpoints of an advanced metering infrastructure (AMI) with automatic meter reading (AMR).

Abstract: An advanced metering infrastructure may be configured for automated meter reading, such as of utility (electric, natural gas, etc.) meters. Within a network, a data collector communicates with, and receives meter data from, a plurality of endpoints. Firmware on the endpoints may be updated by transmission, from the data collector, of a new firmware image. In one example, the data collector sends an announcement of a firmware update to the plurality of endpoints. At a time indicated by the announcement, the data collector multicasts the firmware update a plurality of times. The data collector then receives indications from a plurality of endpoints that did not successfully receive all blocks of the multicast firmware update. In response, the data collector sends missing blocks to the plurality of endpoints according to the indications.

Abstract: Techniques for limited data messaging with standards compliance are described herein. A network may be configured as an advanced metering infrastructure (AMI) for automatic meter reading (AMR). A plurality of endpoints (EP) may each be associated with a meter configured to measure consumption of a resource, such as electricity or natural gas. The plurality of EPs may communicate consumption data to a data collector (DC), which transfers the data to a central office. In one example, network traffic and battery power consumption of the EPs may be reduced if each endpoint packages data as a compact array, having minimal data formatting and tagging. A class object associated with each EP and stored at the DC allows the DC to interpret the compact array. Based on this interpretation, the DC is able to reformulate the data as a COSEM (or other standards-based object) for transmission to the central office.

Abstract: An advanced metering infrastructure may be configured for automated meter reading, such as of utility (electric, natural gas, etc.) meters. Within a network, a data collector communicates with, and receives meter data from, a plurality of endpoints. Firmware on the endpoints may be updated by transmission, from the data collector, of a new firmware image. In one example, the data collector sends an announcement of a firmware update to the plurality of endpoints. At a time indicated by the announcement, the data collector multicasts the firmware update a plurality of times. The data collector then receives indications from a plurality of endpoints that did not successfully receive all blocks of the multicast firmware update. In response, the data collector sends missing blocks to the plurality of endpoints according to the indications.

Abstract: To determine network coverage of a device within a network a user may send an instruction to the device using a mobile configuration tool of a mobile device. Upon receiving the instruction, the device of which the network coverage is to be determined may broadcast a message using a standard protocol, and listen to one or more responses from other devices in the network. In response to receiving the one or more responses, the device at issue may relay the one or more responses, or a processing result of the network coverage (determined based on the one or more responses) to the mobile configuration tool for display to the user. The user may determine whether the network coverage of that device meets one or more network coverage criteria and, if not, may take some corrective action.