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