# US 2008/0187116 A1 · Flow-through provisioning in utility AMR/AMI networks

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0187116 A1
- Document ID: US20080187116A1
- Status: Published application
- Kind: A1
- Application number: 11/796,767
- Filed: 2007-04-30
- Published: 2008-08-07
- Earliest claimed: 2007-02-02
- Assignees: Silver Sring Networks, Inc.
- Inventors: Donald L. Reeves; James Pace; Brian Grady; Raj Vaswani
- Web page: https://patentgrep.com/patent/US20080187116A1

## CPC

- H04L 69/16: Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- G01D 4/004: {Remote reading of utility meters to a fixed location}
- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q 30/04: Billing or invoicing
- H04L 61/5007: Internet protocol [IP] addresses
- H04L 67/125: involving control of end-device applications over a network
- H04L 69/167: Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6 (translation of Internet protocol [IP] addresses H04L61/2503)
- G06Q 50/06: Energy or water supply
- H04W 8/26: Network addressing or numbering for mobility support
- H04W 84/18: Self-organising networks, e.g. ad-hoc networks or sensor networks
- H04W 92/02: Inter-networking arrangements
- Y02B 90/20: Smart grids as enabling technology in buildings sector (smart grids supporting the management or operation of end-user stationary applications in general, or like technologies with no associated climate change mitigation effect Y04S20/00)
- Y04S 20/30: Smart metering, e.g. specially adapted for remote reading
- Y04S 40/18: Network protocols supporting networked applications, e.g. including control of end-device applications over a network
- Y04S 50/12: Billing, invoicing, buying or selling transactions or other related activities, e.g. cost or usage evaluation
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G01D: MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- Y02B: CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO BUILDINGS, e.g. HOUSING, HOUSE APPLIANCES OR RELATED END-USER APPLICATIONS
- Y04S: SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS

## Abstract

A system associated with a utility network having product distribution pathways, including a device management module for automatically provisioning at least a subset of a plurality of electronic utility devices associated with the pathways based on configuration state information received from the subset of the plurality of electronic utility devices and a comparison of the received configuration state information and predefined configuration state information.

## Claims

### Claim 1

A system associated with a utility network having product distribution pathways, the system comprising:
a device management module for automatically provisioning at least a subset of a plurality of electronic utility devices associated with the pathways based on configuration state information received from the subset of the plurality of electronic utility devices and a comparison of the received configuration state information and predefined configuration state information.

### Claim 2 (depends on 1)

The system of claim 1, wherein at least one of the subset of electronic utility devices includes at least one of frequency-hopping spread spectrum communication protocol capability, broadband communication capability, and IPv6 communication capability.

### Claim 3 (depends on 1)

The system of claim 1, wherein the device management module is operable to calculate a program seal for at least one of the subset of electronic utility devices from the configuration state information received from the electronic utility device.

### Claim 4 (depends on 3)

The system of claim 3, wherein the device management module is operable to verify integrity of the electronic utility device using the calculated program seal.

### Claim 5 (depends on 4)

The system of claim 4, wherein, if the integrity of the electronic utility device is not verified, the device management module is operable to send a status message to the electronic utility device.

### Claim 6 (depends on 5)

The system of claim 5, wherein the device management module is operable to include a configuration change in the status message, the configuration change corresponding to read software installed in the electronic utility device.

### Claim 7 (depends on 4)

The system of claim 4, wherein, if the integrity of the electronic utility device is not verified, the device management module is operable to initiate an alert.

### Claim 8 (depends on 4)

The system of claim 4, wherein the device management module includes a database operable to record data associated with integrity verification failures.

### Claim 9 (depends on 4)

The system of claim 4, wherein the device management module is operable to changing billing rules for services associated with the electronic utility device based on the integrity of the electronic utility device.

### Claim 10 (depends on 4)

The system of claim 4, wherein, if the integrity of the electronic utility device is not verified, the device management module is operable to initialize the electronic utility device.

### Claim 11 (depends on 1)

The system of claim 1, wherein the device management module is operable to receive billing information from at least one of the subset of electronic utility devices for services associated with the electronic utility device.

### Claim 12 (depends on 1)

The system of claim 1, wherein the device management module is operable to receive one of time of use information and interval channel information from at least one of the subset of electronic utility devices for services associated with the electronic utility device.

### Claim 13 (depends on 1)

The system of claim 1, wherein the device management module is operable to change billing rules for services associated with at least one of the subset of the electronic utility devices based on the configuration state information received from the electronic utility device.

### Claim 14 (depends on 1)

The system of claim 1, wherein the device management module is operable to provision at least one of the subset of electronic utility devices based on a change to billing rules for services associated with the electronic utility device.

### Claim 15 (depends on 1)

The system of claim 1, wherein the device management module is operable to poll at least one of the subset of the electronic utility devices and to request a program seal from the electronic utility device to verify an identity of the electronic utility device before exchanging information with the electronic utility device.

### Claim 16 (depends on 1)

The system of claim 1, wherein the device management module is operable to assign a hash key to each of the subset of the electronic utility devices, and wherein the device management module is operable to query the subset of electronic utility devices for the hash keys before exchanging information with the subset of electronic utility devices.

### Claim 17 (depends on 1)

The system of claim 1, wherein the device management module is operable to communicate with at least one of the plurality of electronic utility devices using a hash key to reduce network bandwidth required for the communication.

### Claim 18 (depends on 1)

The system of claim 1, wherein, during provisioning, the device management module is operable to assign the subset of the electronic utility devices to schedule-based tasks.

### Claim 19 (depends on 1)

The system of claim 1, wherein the device management module is operable to initialize at least one of the plurality of electronic utility devices.

### Claim 20

A device management system comprising:
software, stored in computer readable medium, for receiving configuration state information from at least one of a plurality of electronic utility devices associated with a product distribution pathway of a utility network, and determining whether to configure the electronic utility device based on a comparison of the received configuration state information and predefined configuration state information.

### Claim 21 (depends on 20)

The device management system of claim 20, wherein the electronic utility device includes at least one of frequency-hopping spread spectrum communication protocol capability, broadband communication capability, and IPv6 communication capability.

### Claim 22 (depends on 20)

The device management system of claim 20, wherein the device management system is operable to calculate a program seal for the electronic utility device from the configuration state information received from the electronic utility device.

### Claim 23 (depends on 22)

The device management system of claim 22, wherein the device management system is operable to verify integrity of the electronic utility device using the calculated program seal.

### Claim 24 (depends on 23)

The device management system of claim 23, wherein, if the integrity of the electronic utility device is not verified, the device management system is operable to send a status message to the electronic utility device.

### Claim 25 (depends on 24)

The device management system of claim 24, wherein the device management system is operable to include a configuration change in the status message, the configuration change corresponding to read software installed in the electronic utility device.

### Claim 26 (depends on 23)

The device management system of claim 23, wherein, if the integrity of the electronic utility device is not verified, the device management system is operable to initiate an alert.

### Claim 27 (depends on 23)

The device management system of claim 23, wherein the device management system includes a database operable to record data associated with integrity verification failures.

### Claim 28 (depends on 23)

The device management system of claim 23, wherein the device management system is operable to changing billing rules for services associated with the electronic utility device based on the integrity of the electronic utility device.

### Claim 29 (depends on 23)

The device management system of claim 23, wherein, if the integrity of the electronic utility device is not verified, the device management system is operable to initialize the electronic utility device.

### Claim 30 (depends on 20)

The device management system of claim 20, wherein the device management system is operable to receive billing information from the electronic utility device for services associated with the electronic utility device.

### Claim 31 (depends on 20)

The device management system of claim 20, wherein the device management system is operable to receive at least one of time of use and interval channel information from the electronic utility device for services associated with the electronic utility device.

### Claim 32 (depends on 20)

The device management system of claim 20, wherein the device management system is operable to change billing rules for services associated with the electronic utility device based on the configuration state information received from the electronic utility device.

### Claim 33 (depends on 20)

The device management system of claim 20, wherein the device management system is operable to poll the electronic utility device and to request a program seal from the electronic utility device to verify an identity of the electronic utility device before exchanging information with the electronic utility device.

### Claim 34 (depends on 20)

The device management system of claim 20, wherein the device management system is operable to assign a hash key to each of the plurality of the electronic utility devices, and wherein the device management system is operable to query the electronic utility devices for the hash keys before exchanging information with the electronic utility devices.

### Claim 35 (depends on 20)

The device management system of claim 20, wherein the device management system is operable to communicate with at least one of the plurality of electronic utility devices using a hash key to reduce network bandwidth required for the communication.

### Claim 36

A method of provisioning electronic utility devices associated with product distribution pathways of a utility network, comprising:
receiving information from an electronic utility device;
identifying a configuration state for the electronic utility device from the received electronic utility device information; and
determining whether to configure the electronic utility device based upon the identified configuration state.

### Claim 37 (depends on 36)

The method of claim 36, wherein the electronic utility device is a commodity meter, and wherein the received information specifies the configuration state of the commodity meter.

### Claim 38 (depends on 36)

The method of claim 36, wherein the received information is an initial message sent by the electronic utility device upon connection to the utility network.

### Claim 39 (depends on 36)

The method of claim 36, further comprising:
if the configuration state does not match predefined configuration state information, sending a status message to the electronic utility device.

### Claim 40 (depends on 39)

The method of claim 39, wherein the status message includes a configuration change, the configuration change corresponding to electronic utility device read software installed in the electronic utility device.

### Claim 41 (depends on 39)

The method of claim 39, wherein the status message includes a program seal, and wherein the method includes verifying the program seal before authorizing communication between the electronic utility device and the device management system.

### Claim 42 (depends on 39)

The method of claim 39, wherein the status message includes administrative state information.

### Claim 43 (depends on 36)

The method of claim 36, wherein the received information includes a program seal corresponding to the electronic utility device.

### Claim 44 (depends on 36)

The method of claim 36, wherein the received information includes customer identification information.

### Claim 45 (depends on 36)

The method of claim 36, wherein the received information includes at least one of utility identification information and manufacturer identification information.

### Claim 46 (depends on 36)

The method of claim 36, wherein the received information includes information specifying a release characteristic of the electronic utility device providing the received information.

### Claim 47 (depends on 39)

The method of claim 39, wherein the status message includes at least one of time of use information and interval channel information.

### Claim 48 (depends on 39)

The method of claim 39, further comprising:
storing program seal information, wherein the program seal information is based upon the sent status message.

### Claim 49 (depends on 36)

The method of claim 36, further comprising:
if the configuration state information matches a predefined configuration state information, adding the electronic utility device to an electronic utility device read database.

### Claim 50 (depends on 49)

The method of claim 49, further comprising:
changing an administrative state in the electronic utility device read database from active to inactive.

### Claim 51 (depends on 50)

The method of claim 50, further comprising:
in response to the change in administrative state to inactive, reducing frequency of electronic utility device reads for the electronic utility device corresponding to the inactive electronic utility device.

### Claim 52 (depends on 36)

The method of claim 36, further comprising:
reading an electronic utility device having an inactive administrative state; and
comparing information received from the inactive electronic utility device to anticipated information for electronic utility devices having inactive administrative states.

### Claim 53

A method of provisioning a plurality of electronic utility devices associated with product distribution pathways of a utility network, comprising:
receiving configuration state information from an electronic utility device;
comparing the received configuration state information to predefined configuration state information;
calculating an electronic utility device program seal from the received configuration state information; and
verifying the integrity of the electronic utility devices according to the calculated program seal.

### Claim 54 (depends on 53)

The method of claim 53, further comprising:
if the integrity of the electronic utility device is not verified, sending a status message to the electronic utility device.

### Claim 55 (depends on 53)

The method of claim 53, further comprising:
if the integrity of the electronic utility device is not verified, initiating an alert.

### Claim 56 (depends on 53)

The method of claim 53, further comprising:
if the integrity of the electronic utility device is not verified, indicating in a database that the integrity of the electronic utility device has failed verification.

### Claim 57 (depends on 53)

The method of claim 53, further comprising:
if the integrity of the electronic utility device is not verified, applying a failed integrity verification billing rule.

### Claim 58 (depends on 53)

The method of claim 53, further comprising:
if the integrity of the electronic utility device is not verified, initializing the electronic utility device corresponding to the failed verification.

### Claim 59 (depends on 53)

The method of claim 53, further comprising:
if the integrity of the electronic utility device is not verified, sending a status message to the electronic device.

### Claim 60 (depends on 59)

The method of claim 59, wherein the status message includes a configuration change corresponding to read software installed in the electronic utility device.

### Claim 61 (depends on 53)

The method of claim 53, wherein the received configuration state information includes electronic utility devices billing information.

### Claim 62 (depends on 61)

The method of claim 61, wherein the electronic utility devices billing information specifies at least one of time of use information and interval channel information.

### Claim 63 (depends on 53)

The method of claim 53, further comprising:
if the integrity of the electronic utility device is not verified, discarding at least a portion of electronic utility device reads from a last known verified integrity.

### Claim 64 (depends on 53)

The method of claim 53, wherein the received configuration state information is received in response to a request from a device management system.
