# Patent

## Title
Energy use control system and method

## Abstract

Devices and systems control energy usage in accordance with instructions from a head end system. A device may be instructed to cease energy consumption. Another device may allow users to override some instructions. Messages may be provided to users to request the cessation of energy consumption; the users may, but need not comply.

## Background
CROSS-REFERENCE TO RELATED APPLICATIONS
This application claims the benefit of priority to the following United States provisional patent applications which are incorporated herein by reference in their entirety:

    
    
        Ser. No. 60/989,957 entitled “Point-to-Point Communication within a Mesh Network”, filed Nov. 25, 2007;
        Ser. No. 60/989,967 entitled “Efficient And Compact Transport Layer And Model For An Advanced Metering Infrastructure (AMI) Network,” filed Nov. 25, 2007;
        Ser. No. 60/989,958 entitled “Creating And Managing A Mesh Network Including Network Association,” filed Nov. 25, 2007;
        Ser. No. 60/989,964 entitled “Route Optimization Within A Mesh Network,” filed Nov. 25, 2007;
        Ser. No. 60/989,965, entitled “ENERGY USE CONTROL SYSTEM AND METHOD” filed on Dec. 5, 2007;
        Ser. No. 60/989,950 entitled “Application Layer Device Agnostic Collector Utilizing ANSI C12.22,” filed Nov. 25, 2007;
        Ser. No. 60/989,953 entitled “System And Method For Real Time Event Report Generation Between Nodes And Head End Server In A Meter Reading Network Including From Smart And Dumb Meters,” filed Nov. 25, 2007;
        Ser. No. 60/989,975 entitled “System and Method for Network (Mesh) Layer And Application Layer Architecture And Processes,” filed Nov. 25, 2007;
        Ser. No. 60/989,959 entitled “Tree Routing Within a Mesh Network,” filed Nov. 25, 2007;
        Ser. No. 60/989,961 entitled “Source Routing Within a Mesh Network,” filed Nov. 25, 2007;
        Ser. No. 60/989,962 entitled “Creating and Managing a Mesh Network,” filed Nov. 25, 2007;
        Ser. No. 60/989,951 entitled “Network Node And Collector Architecture For Communicating Data And Method Of Communications,” filed Nov. 25, 2007;
        Ser. No. 60/989,955 entitled “System And Method For Recovering From Head End Data Loss And Data Collector Failure In An Automated Meter Reading Infrastructure,” filed Nov. 25, 2007;
        Ser. No. 60/989,952 entitled “System And Method For Assigning Checkpoints To A Plurality Of Network Nodes In Communication With A Device Agnostic Data Collector,” filed Nov. 25, 2007;
        Ser. No. 60/989,954 entitled “System And Method For Synchronizing Data In An Automated Meter Reading Infrastructure,” filed Nov. 25, 2007;
        Ser. No. 60/992,312 entitled “Mesh Network Broadcast,” filed Dec. 4, 2007;
        Ser. No. 60/992,313 entitled “Multi Tree Mesh Networks”, filed Dec. 4, 2007;
        Ser. No. 60/992,315 entitled “Mesh Routing Within a Mesh Network,” filed Dec. 4, 2007;
        Ser. No. 61/025,279 entitled “Point-to-Point Communication within a Mesh Network”, filed Jan. 31, 2008;
        Ser. No. 61/025,270 entitled “Application Layer Device Agnostic Collector Utilizing Standardized Utility Metering Protocol Such As ANSI C12.22,” filed Jan. 31, 2008;
        Ser. No. 61/025,276 entitled “System And Method For Real-Time Event Report Generation Between Nodes And Head End Server In A Meter Reading Network Including Form Smart And Dumb Meters,” filed Jan. 31, 2008;
        Ser. No. 61/025,282 entitled “Method And System for Creating And Managing Association And Balancing Of A Mesh Device In A Mesh Network,” filed Jan. 31, 2008;
        Ser. No. 61/025,271 entitled “Method And System for Creating And Managing Association And Balancing Of A Mesh Device In A Mesh Network,” filed Jan. 31, 2008;
        Ser. No. 61/025,287 entitled “System And Method For Operating Mesh Devices In Multi-Tree Overlapping Mesh Networks”, filed Jan. 31, 2008;
        Ser. No. 61/025,278 entitled “System And Method For Recovering From Head End Data Loss And Data Collector Failure In An Automated Meter Reading Infrastructure,” filed Jan. 31, 2008;
        Ser. No. 61/025,273 entitled “System And Method For Assigning Checkpoints to A Plurality Of Network Nodes In Communication With A Device-Agnostic Data Collector,” filed Jan. 31, 2008;
        Ser. No. 61/025,277 entitled “System And Method For Synchronizing Data In An Automated Meter Reading Infrastructure,” filed Jan. 31, 2008;
        Ser. No. 61/026,097 entitled “Energy Use Control System And Method,” filed Feb. 4, 2008; and
        Ser. No. 61/094,116 entitled “Message Formats and Processes for Communication Across a Mesh Network,” filed Sep. 4, 2008.
    
    


This application hereby references and incorporates by reference each of the following United States patent applications filed contemporaneously herewith:

    
    
        Ser. No. 12/275,236 entitled “Point-to-Point Communication within a Mesh Network”, filed Nov. 21, 2008;
        Ser. No. 12/275,305 entitled “Efficient And Compact Transport Layer And Model For An Advanced Metering Infrastructure (AMI) Network,” filed Nov. 21, 2008;
        Ser. No. 12/275,238 entitled “Communication and Message Route Optimization and Messaging in a Mesh Network,” filed Nov. 21, 2008;
        Ser. No. 12/275,242 entitled “Collector Device and System Utilizing Standardized Utility Metering Protocol,” filed Nov. 21, 2008; and
        Ser. No. 12/275,252 entitled “Method and System for Creating and Managing Association and Balancing of a Mesh Device in a Mesh Network,” filed Nov. 21, 2008; and
        Ser. No. 12/275,257 entitled “System And Method For Operating Mesh Devices In Multi-Tree Overlapping Mesh Networks”, filed Nov. 21, 2008.
    
    




FIELD OF THE INVENTION
This invention pertains to systems, devices, and methods for controlling power or energy use, such as, for example, in an Automated Metering Infrastructure.
BACKGROUND
Use of a utility such as water, electricity, natural gas or other utility or energy is conventionally by the demand of a user. The user may use as much or as little as is desired, paying as the energy is used, and perhaps paying at a prevailing market rate which may vary according to a schedule or current demand. This may be undesirable because the price of a utility and especially energy may fluctuate according to schedule and/or demand and it may be that certain times are more cost effective. This may be true from either the standpoint of a control device or the standpoint of a user if the user is exposed to knowledge of wholesale pricing of the energy.
Where a user is exposed to costs, the user may find it undesirable to, for example, consume a resource or operate an appliance such as dishwasher swimming pool filter or other appliance at peak pricing. It may be more cost effective to operate the dishwasher to clean dinner or the day's dishes at, for example, 3 am because of a low demand and associated lower energy pricing where clean dishes are still available in the morning. The same may be true for operating other energy consuming appliances and for off-peak charging of electric vehicle batteries from a residential source or when such charging such vehicle batteries becomes more widespread.
Even if some users are willing to be subject to some or full control of their utility or energy use, other users may not be willing to turn over full control. Such users may have a desire to allow a control device to have influence over their utility or energy use decisions, but may not want the centralized control to have complete control.
Other users may desire that a centralized management system have no control over their utility or energy use, but may still be willing to receive messages pertaining to the cost effectiveness of energy usage at various times. They would then be in a better position to make their own informed decisions relative to utility or energy usage.
What is needed is a system and method for controlling utility and/or energy usage so that energy consumption is, at times, limited.
The foregoing examples of the related art and limitations related therewith are intended to be illustrative and not exclusive. Other limitations of the related art will become apparent to those of skill in the art upon a reading of the specification and a study of the drawings.
SUMMARY
The following embodiments and aspects thereof are described and illustrated in conjunction with systems, tools, and methods that are meant to be exemplary and illustrative, not limiting in scope. In various embodiments, one or more of the above described problems have been reduced or eliminated, while other embodiments are directed to other improvements.
In one non-limiting aspect there may be provided a system comprising: a request interface receiving an instruction to control energy use; a scheduler coupled to the request interface identifying one or more devices to provide commands to control energy use; and a command provider creating messages for the one or more identified devices to limit energy use.
In another non-limiting aspect there may be provided a method comprising: receiving a request to control energy use; providing the request to a scheduler; creating a message for a device subject to the request; and providing the request to the device.
In another non-limiting aspect there may be provided a method comprising: receiving a request to control energy use; authenticating the request to control energy use; removing message headers; and providing a table request.
In another non-limiting aspect there may be provided a device comprising: a radio coupled to a communications logic unit; an external energy using component coupled to the communications logic unit; and a memory storing tables, the memory including instructions for disabling the external energy using component coupled to the communications logic unit.
In another non-limiting aspect there may be provided a system comprising: means for receiving an instruction to disable an external energy using device; means for generating a message to the external energy using device to instruct the external energy using device to cease energy consumption; and means for providing the message to the external energy using device.
In another non-limiting aspect there may be provided a computer program stored in a computer readable form for execution in a processor and a processor coupled memory to implement a method comprising: receiving a request to control energy use; providing the request to a scheduler; creating a message for a device subject to the request; and providing the request to the device.
In another non-limiting aspect there may be provided a computer program stored in a computer readable form for execution in a processor and a processor coupled memory to implement a method comprising: receiving a request to control energy use; authenticating the request to control energy use; removing message headers; and providing a table request.
This Summary introduces concepts in a simplified form that are described more fully below in the Detailed Description. This Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 depicts a diagram of an exemplary system including a control device and a target device.
FIG. 2 depicts a diagram of an exemplary system for controlling energy use.
FIG. 3 depicts components included in an exemplary head end system.
FIG. 4 depicts a flowchart of a non-limiting example of a method for controlling energy consumption of a demand response device.
FIG. 5 depicts a diagram of an exemplary energy control device.
FIG. 6 depicts a flowchart of a non-limiting example of a method for controlling energy consumption.
FIG. 7 depicts a system for providing a message from a NAN-WAN gate to a target device on a home area network (HAN).
FIG. 8 depicts a flowchart of an exemplary method for providing a message to a target device in the ZigBee protocol.
FIG. 9 depicts a non-limiting example of an exemplary system for controlling energy use of a pool pump.
FIG. 10 depicts an exemplary configuration having a plurality of devices on an automated metering infrastructure (AMI) network.



DETAILED DESCRIPTION
In the following description, several specific details are presented to provide a thorough understanding. One skilled in the relevant art will recognize, however, that the concepts and techniques disclosed herein can be practiced without one or more of the specific details, or in combination with other components, etc. In other instances, well-known implementations or operations are not shown or described in detail to avoid obscuring aspects of various examples disclosed herein.
FIG. 1 depicts a diagram of an exemplary system 100 including a control device 102 and a target device 104.
The control device 102 could be a head end unit, or one of many distributed control devices such as a network gate. For example, the gate may be a NAN-WAN gate (neighborhood area network-wide area network gate). The control device 102 may include a radio. The control device 102 may communicate by wired or wireless communications.
The target device 104 may be any device that consumes, controls, or otherwise uses a utility such as energy. For brevity of description, references to energy will imply a reference to other utilities and is used because energy is a primary utility to be consumed, controlled, or otherwise used in this manner. By way of example, and not limitation, an energy using device could be an electricity meter, an electrically operated dishwasher, an electric pool pump, a high wattage or amperage switch or circuit breaker controlling electrical energy for a home, or any other device that consumes, controls, or otherwise uses energy. The device may optionally include nonvolatile storage for recording energy consumption readings. The energy using device or energy consuming device may be a part of the system or may be a device that is external to the system but connected or coupled to it.
The target device 104 may include a radio and a communications logic board. The target device 104 may be a demand response device, a load control device, or any device known or convenient. The radio may communicate using any known or convenient radio communications protocol. In a non-limiting example, the American National Standards Institute (ANSI) C12.22 standard in effect as of the date of filing of this application or an enhancement or extension of this standard governs the communications.
FIG. 2 depicts a diagram of an exemplary system 200 for controlling energy use. FIG. 2 includes request provider 202, head end 204, neighborhood area network to wide area network (NAN-WAN) gate 206, a gateway such as home gateway 208, and target device 210.
The request provider 202 may be a web based interface, an interface based on the simple object access protocol (SOAP), or any known or convenient interface or manner of communicating a request to control energy use.
The head end 204 may be a server, cluster of servers, or other known or convenient request processing system. As used herein, a server may be a software application executing as one or more instances on one or more hardware units. A plurality of servers may include one or more hardware units executing one or more instances of a software application. Each hardware unit may include a processor and memory storing one or more instances of the software application providing instructions for execution by the processor.
The optional NAN-WAN gate 206 may be a mesh gate, multi radio device or other device able to communicate on a mesh network as well as a wide area network such as one communicating via TCP-IP or another known or convenient communications protocol. In a non-limiting example, the NAN-WAN gate provides communications via multiple protocol stacks, including a stack dedicated to the Trilliant mesh network, and a stack dedicated to wide area communications such as the TCP/IP stack. A Trilliant mesh network may for example be or conform to networks and network architectures of Trilliant Networks, Inc. or Redwood City, Calif.
The optional home gateway 208 may include multiple radios and processing logic designed for a ZigBee network as well as a mesh network. The processing logic of the home gateway 206 may enable translation of messages from the Trilliant mesh network to a ZigBee network. A ZigBee network is a network that complies with the ZigBee Alliance and uses ZigBee features and protocols, as well as to enhancements and extensions thereto. ZigBee protocols and standards as promulgated at the date of filing of this patent application are hereby incorporated by reference.
The ZigBee Alliance is an association of companies working to enable reliable, cost-effective, low-power, wirelessly networked, monitoring and control products based on an open global standard. The ZigBee Alliance focuses on defining the network, security, and application software layers, providing interoperability and conformance testing specifications, promoting the ZigBee brand globally to build market awareness, and managing the evolution of the technology. Further information about the ZigBee Alliance may be obtained at www.zigbee.org/en/about/.
The target device 210 may be an energy using device such as a load control device, or demand response device. A load control device is a device which allows a user to override centralized control when a command is issued to cease energy consumption at the load control device. A demand response device may receive a command to cease energy use and a user may not usually be able to override the command, though exceptions may be permitted.
In the example of FIG. 2, in operation, the request provider 202 provides a request to the head end 204 to cause one or more devices to cease energy use for a duration of time to begin at a specified time. The request may be varied, and for a group of target devices, the request may or may not specify individual devices; optionally a class of target devices may be specified and the head end 204 may determine individual devices to target. The head end or head end server 204 receives the request from the request provider 202 and identifies one or more target devices 210 using the request. One or more messages are created including a message instructing the target device 210 to cease energy consumption. Absent either an optional NAN-WAN gate 206, and a home gateway 208, the message is provided directly to the target device 210.
Where a NAN-WAN gate 206 provides connectivity between the head end 204 and the target device 210, the message is provided to the NAN-WAN gate 206 via a wide area communications protocol, and the NAN-WAN gate 206 provides the message to the target device 210.
Where a home gateway 208 provides connectivity between the NAN-WAN gate 206 and the target device 210, the home gateway may use a protocol such as the ZigBee protocol or another known or convenient protocol for providing a home area network to provide the message from the NAN-WAN gate 206 to the target device 210.
FIG. 3 depicts components included in an exemplary head end system 300. FIG. 3 includes request interface 306, scheduler 308, and command provider 310. An message re-broadcaster 312 may optionally be provided.
The request interface 306 may be designed for any known or convenient protocol. In a non-limiting example, the simple object access protocol (SOAP) is used. The protocol may provide the requests to a framework, where a framework may govern communications between devices on a network. Any known or convenient framework may be used, such as for example, a framework available from Trilliant Networks of Redwood City, Calif. Security may be used to protect the contents of requests transferred. In a non-limiting example, a secure hypertext transfer protocol (HTTPS) may be used to provide SOAP protocol requests to the request interface 306 in a secure manner. A web based interface may be used to provide requests, or alternatively a software application may provide requests to the request interface 306.
A request may specify a class of devices to target for a particular energy use control request. Classes may be used to identify devices based on criteria such as the purpose, energy consumption, time of use, or other known or convenient criteria for controlling energy use.
The scheduler 308 may include a message creation engine operable to target one or more devices based on a request. A message may be created for each device to be targeted. The message may specify energy use criteria to a target device to cause the target device to operate or not operate in a particular manner, such as for example, to cease energy use at a specified time and/or for a specified duration of time. In some cases, the target device may be permitted to operate in a standby manner wherein it consumes some minimal energy to maintain settings, stored information, or to be able to wake up and transition to a higher energy consumption mode. For a class of devices the scheduler 308 may create one or more messages.
The command provider 310 may include one or more hardware units executing one or more servers to provide one or more messages to one or more devices. The command provider 310 may access a message created by the scheduler 308 as well as one or more devices. The devices may be accessible via a network such as for example including a wide area network (WAN), optionally a neighborhood area network (NAN), and optionally a home area network (HAN).
The optional message re-broadcaster 312 may include a message replication unit and a target device identification unit. The message replication unit may take an existing message and create a second message targeting a device identified by the target device identification unit. A plurality of messages may be created for a plurality of target devices.
In the example of FIG. 3 in operation, the request interface 306 may receive a request to limit energy use for a class of target devices according to a set of criteria. The scheduler 308 may create one or more messages to control energy consumption of one or more specified devices, one message per device. The command provider 310 may provide each message created to a network for transmission to the target device associated with the message.
In the example of FIG. 3, in operation, the optional message re-broadcaster 312 may be used to identify target devices to which to provide messages. If the message re-broadcaster is used then the scheduler may create one message per message re-broadcaster. A plurality of message re-broadcasters may be used. Advantageously, the scheduler 308 need not create a message for each and every target device, thus distributing work to the message re-broadcaster 312. The message re-broadcaster 312 may create a message for each target device from the message provided to the message re-broadcaster 312.
FIG. 4 depicts a flowchart of a non-limiting example of a method 400 for controlling energy consumption of a demand response device. The method is organized as a sequence of modules or steps in the flowchart. However, it should be understood that these and modules associated with other methods described herein may be reordered for parallel execution or into different sequences of modules.
In the example of FIG. 4, the method starts at module or step 402 with receiving a request to control energy use. This request to control energy use may be partial or complete. A device may be instructed to cease energy consumption entirely. A time and duration may be specified. The request may specify a class of devices, or alternatively a specific device. The request may be received in a secure format via a network. In a non-limiting example, the simple object access protocol (SOAP) is used in conjunction with the secure hypertext transfer protocol (HTTPS) to provide the request.
In the example of FIG. 4, the flowchart continues to module or step 404 with providing the request to the scheduler. The request may be re-transmitted from an interface originally receiving the message to the scheduler via an internal network.
In the example of FIG. 4, the flowchart continues to module or step 406 with creating a message for a device subject to the request. The device may be explicitly identified in the request to control energy use, or alternatively may be identified by criteria out of a pool of devices. In a non-limiting example, device class, time of use, amount of energy used, or other known or convenient criteria may be used.
In the example of FIG. 4, the flowchart continues to module or step 408 with providing the request to the device. The request may be transmitted directly to the device, or may be retransmitted by one or more intermediate devices via one or more networks. Where multiple networks are used multiple protocols may be used requiring translation between the multiple protocols. Having transmitted a message confirming the decrease of energy consumption, the flowchart terminates.
FIG. 5 depicts a diagram of an exemplary energy control device 500. The exemplary energy control device depicted in FIG. 5 includes radio 506, energy using component 508, processor 510, memory 512, optional display device 514, and optional user input 516. Energy using component 508 may be external to the energy control device 500, such as a commercial or residential appliance that is connected to or coupled with the energy control device.
The energy control device 500 may be a load control device or a demand response device. The load control device may be instructed to cease energy use, however, a user may override the instruction when desirable. The demand response device may receive a command to cease energy use and a user may not override the command.
The radio 506 may be any known or convenient combination of electronic components, e.g. transistors, resistors, inductors and other known or convenient electronic components to perform a radio or communication function. The radio 506 may operate using one or more protocols. In a non-limiting example, a mesh network protocol may be used by the radio 506 to communicate with other devices coupled or coupleable to the mesh network.
The energy using component 508 may implement the function of the device; in a non-limiting example, the energy using component 508 could be a dishwasher, a pool pump, a light, or any known or convenient device using electricity. The energy using component may be part of the system but is frequently an external component separate from the system and coupled to the system in a manner that its energy use may be controlled by the system.
The processor 510 may execute instructions found or stored in the memory 512 for communication, enabling and disabling the energy using component 508, and performing other known or convenient tasks. The clock 518 may provide a current time for the energy using device.
The memory 512 may include data structure such as a table structure formatted to a format, such as for example to the ANSI C12.19 format. A table may be specified for instructions to control energy use. The ANSI C12.19 table format is described in ANSI C12 documents and standards that are in effect as of the date of filing of this patent application, and which documents and standards are herein incorporated by reference.
The optional display device 514 may be coupled to an optional user input 516 for displaying information about the status of the energy using component 508. The optional display device 514 may generate or produce messages or warnings that the energy using component 508 will be disabled. For a load control device, the user input 516 may allow the user to prevent the disabling of the energy using component 508.
In the example of FIG. 5 in operation, the radio receives a message instructing the processor 510 to disable the energy. The message may be provided according to the table structure for the ANSI C12.19 format. In a non-limiting example, the energy using component 508 is to be disabled between specified times, such as between 5 pm and 10 pm. At the time specified by the clock 518, instructions stored in the memory 512 executed by the processor 510 cause energy using component 508 to cease energy consumption at the specified stop time (e.g., 5 pm) and to prevent the energy consumption from resuming until after the specified resume time (e.g., 10 pm). If the energy control device is a demand response device, the instruction may not be overridden; however, if the energy control device is a load control device, the instruction may be overridden by a command through the optional user input 516. Emergency override may optionally be provided for demand response device.
FIG. 6 depicts a flowchart of a non-limiting example of a method 600 for controlling energy consumption. The method 600 is organized as a sequence of modules or steps in the flowchart. However, it should be understood that these and modules associated with other methods described herein may be reordered for parallel execution or into different sequences of modules.
In the example of FIG. 6, the method starts at module or step 602 with a demand response device or load control device receiving a request to control energy use. The request may be received via a radio, or via a wired connection. The request may be structured as a table conforming to the ANSI C12.19 format.
In the example of FIG. 6, the method continues to module or step 604 with authenticating the request. The request may be encrypted, such as by using a key. Using the key, the device may decrypt the message. An inability to decrypt the message because of an incorrect key may indicate that the request was not designed for the device receiving the request.
In the example of FIG. 6, the method continues to module 606 with removing message headers. Separating the request from the headers may yield the request itself.
In the example of FIG. 6, the method continues to module or step 608 with providing a table request to a host. The table request may be stored in memory according to a table structure for the device. Storing the request in memory may make the request accessible to a processor for further action.
FIG. 7 depicts a system 700 for providing a message from a NAN-WAN gate to a target device on a home area network (HAN). FIG. 7 includes NAN-WAN gate 702, home gateway 704, and ZigBee target device 714. The NAN-WAN gate 702 may communicate on a wide area network and via a mesh network. Additional information about the ZigBee device, message translator and format is described in the Zigbee Smart Energy Profile Specification which is incorporated herein by reference, provided by the Zigbee Standards Organization and available through the world-wide web.
The home gateway 704 includes a mesh radio 706, a mesh protocol translator 708, and a ZigBee message translator 710.
The mesh radio 706 may communicate over a mesh network with the NAN-WAN gate 702. The mesh radio 706 may receive messages intended for the ZigBee target device 714. The mesh protocol translator 708 may receive a message formatted for the mesh protocol and reduce it to an intermediate format. In a non-limiting example, the mesh protocol translator 708 converts the mesh format to a plain text formatted table structure.
The ZigBee message translator 710 may receive an intermediate format and translate the format to the ZigBee format. In a non-limiting example a message in plain text is formatted as a message in the ZigBee format. The ZigBee radio 712 provides messages to devices in range of the ZigBee radio 712.
The ZigBee target device 714, may be any energy using device able to receive messages via the ZigBee protocol. The ZigBee target device 714 may be one of a plurality of ZigBee devices on a home area network (HAN).
In the example of FIG. 7 in operation, the NAN-WAN gate 702 provides a message to the mesh radio 706. The mesh protocol translator 708 translates the message from a mesh format to an intermediate format. The ZigBee message translator 710 translates the message from the intermediate format to the ZigBee format. The ZigBee radio 712 then re-transmits the message from the home gateway 704 to the ZigBee target device 714.
FIG. 8 depicts a flowchart of a method 800 for providing a message to a target device in the ZigBee protocol. The method 800 is organized as a sequence of modules or steps in the flowchart. However, it should be understood that these and modules associated with other methods described herein may be reordered for parallel execution or into different sequences of modules.
In the example of FIG. 8, the method starts at module or step 802 with receiving a message formatted for a mesh protocol. The request may be received via a radio, or via a wired connection. The request may be structured as a table to the ANSI C12.19 format.
In the example of FIG. 8, the method continues to module 804 with translating the message from the mesh format to an intermediate format. In a non-limiting example the intermediate format may be plain text or another known or convenient format to translate to the ZigBee format.
In the example of FIG. 8, the method continues to module or step 806 with translating the message from the intermediate format, such as a plain text message, to the ZigBee protocol.
In the example of FIG. 8, the method continues to module or step 808 with providing the message to the target device in the ZigBee format. The message may be transmitted via a radio or wired connection to the target device.
FIG. 9 depicts a non-limiting example of a system 900 for controlling energy use of a pool pump, where a pool pump is just an example of a type of energy consuming device that may have a relatively high energy consumption but whose operation is not usually time critical. FIG. 9 includes a request provider 902, a head end 904, a NAN-WAN gate 906, and a target device (pool pump) 922.
In the example of FIG. 9, the request provider transmits a request to disable all pool pumps at 1 pm for one hour in a given neighborhood because of decreased energy availability at 1 pm for the one hour period. The head end 904 identifies a plurality of pool pumps in the area specified by the request. Messages identifying each of the pool pumps including the pool pump 922 are generated instructing the devices to cease energy consumption for an hour (or for some other duration of time or according to some other condition, rule, or policy). The message identifying the target device 922 is transmitted to NAN-WAN gate 906, the direct route to the target device 922. The NAN-WAN gate 906 then retransmits the message to the target device 922. The message is received and stored in the target device 922 memory. At 1 pm the target device 922 is disabled, and energy consumption ceases. After an hour, the target device 922 is allowed to resume energy consumption.
FIG. 10 depicts an exemplary configuration having a plurality of devices on an automated metering infrastructure (AMI) network 1000. FIG. 10 includes head end 1002, wide area network (WAN) 1004, NAN-WAN gate 1006, neighborhood area network (NAN) 1008, node 1010-1, node 1010-2, node 1010-n (collectively nodes 1010), microportal 1016, home area network (HAN) 1018 (sometimes referred to as a premise area network (PAN)), node 1020-1, node 1020-2, node 1020-n (collectively nodes 1020).
The head end 1002, sometimes referred to as the back end, server, or head end server can include a suite of applications including functionality for an acquisition system, real-time data access, device management, network management, and other known or convenient functionality. The head end 1002 can include one or more computing devices coupled or otherwise networked together.
The WAN 1004 can be, for example, metropolitan area network (MAN), global area network such as the Internet, any combination of such networks, or any other known convenient medium for communicating data. The WAN 1004 can include routers, switches and/or other networking hardware elements coupled together to provide communications to systems or within systems and devices coupled to the network 1004.
The NAN-WAN gate 1006, sometimes referred to as a mesh gate/collector, can include an IEEE 802.15.4 PAN Coordinator, an ANSI C12.22 Relay, a device collecting messages from multiple units on the NAN and a firewall. An IEEE 802.15.4 PAN Coordinator may be a device that is responsible for communication between devices on a NAN and complies with the IEEE 802.15.4 standard for transmission of data that is in effect as of the date of filing of this patent application. An ANSI C12.22 Relay may be a device that is responsible for communication between devices on a NAN and complies with the ANSI C12.22 standard for transmission of data that is in effect as of the date of filing of this patent application. An access point operable to perform many functions including, for example, but not limited to, one or any combination of: relaying information from the head end server to the nodes, routing information, aggregating information from the nodes and micro portals within its sub-network for transmission to the head end server, acting as a HAN coordinator, transmitting mass firmware upgrades, and multicasting messages. A NAN-WAN gate 1006 may also be referred to as a collector because it collects information from the nodes 1010 and micro portal 1016 in its sub-network.
The NAN 1008, can be a wireless, wired, or mixed wireless and wired network. The NAN 1008 can transmit and receive signals using a protocol, for example, the IEEE 802.15.4 standard for transmission of data that is in effect as of the date of filing of this patent application can be used for wireless transmission. Similarly for wired transmission, the Ethernet/IEEE 802.3 interface standard could be used.
The nodes 1010 can be devices operable to collect metering information and transmit and receive signals via the NAN using any known or convenient protocol. Examples of nodes 1010 could be a meter, a thermostat, a remote appliance controller (RAC), in home display, or any known or convenient NAN device. Each of the nodes 1010 could potentially serve as a NAN-WAN gate by the addition of a WAN radio or wired device allowing communication over the WAN 1004.
The microportal 1016, sometimes referred to as a micro access portal or home gateway, may be a gateway in the sense that a protocol used by devices connected to the gateway use a different protocol than the gateway uses to connect to the nodes 1020. In a non-limiting example, ZigBee, Z-Wave, or X-4 may be used by the nodes 1020 to connect to the microportal 1016 whereas the microportal 1016 uses the Trilliant transport protocol to connect to the NAN-WAN gate 1006.
The HAN 1018 can be a wireless, wired, or mixed wireless and wired network. The NAN 1008 can transmit and receive signals using a protocol, by way of example and not limitation, the ZigBee, Z-Wave, or X-4 standard for transmission of data that is in effect as of the date of filing of this patent application can be used for wireless transmission. Similarly for wired transmission, the Ethernet/IEEE 802.3 interface standard could be used as well as other known or convenient wired interfaces.
The nodes 1020 can be devices operable to collect metering information and transmit and receive signals via the HAN 1018 using any known or convenient protocol. Examples of nodes 1020 could be a meter, a thermostat, a remote appliance controller (RAC), in home display, or any known or convenient NAN device. Each of the nodes 1010 could potentially serve as a microportal by the addition of a NAN radio or wired device allowing communication over the NAN 1008. Each of the nodes 1020 may include a radio and a processor coupled to a memory storing instructions. The nodes 1020, may each communicate using the ZigBee protocol, the Z-Wave protocol, X-10 or another known or convenient protocol.
It will be appreciated to those skilled in the art that the preceding examples and embodiments are exemplary and not limiting in scope. It is intended that all permutations, enhancements, equivalents, and improvements thereto that are apparent to those skilled in the art upon a reading of the specification and a study of the drawings are included within the true spirit and scope of these teachings. It is therefore intended that the following appended claims include all such modifications, permutations, and equivalents as fall within the true spirit and scope of these teachings.

## Claims

1. A system comprising:
a head end server;
a mesh gate in communication with the head end server;
a plurality of target devices, wherein each of the target devices is in communication with the mesh gate and each target device belongs to one of a plurality of target device classes;
a request interface in communication with the head end server receiving an instruction to control energy use of target devices belonging to a selected target device class; and
a scheduler in communication with the head end server, the scheduler receiving the instruction and identifying one or more target devices belonging to the selected target device classes;
wherein the head end server creates a message for the mesh gate in communication with the identified target devices via the mesh gate to limit energy use of the identified target devices, and transmits the message to the mesh gate; and
wherein the mesh gate, upon receiving the message, authenticates the message, removes message headers, and provides a table request to each of the identified target devices to control energy use of the identified target devices.

2. The system of claim 1, wherein the mesh gate comprises a NAN-WAN gate.

3. The system of claim 1, wherein a message includes a command to limit energy usage, and the command is overridden.

4. The system of claim 1, wherein the message includes a command to limit energy usage, and the command is not overridden.

5. The system of claim 1 further comprising a home gateway in communication with the mesh gate and the plurality of target devices.

6. The system of claim 5, wherein the table request is provided to each of the identified target devices via the home gateway.

7. A method comprising:
receiving, by a request interface, a request to control energy use of a class of target devices;
providing, by the request interface, the request to a scheduler in communication with a head end server;
identifying, by the scheduler, one or more target devices belonging to the target device class;
creating, by the head end server, a message for the identified target devices said message including a request to control energy use of the identified target devices;
providing, by the head end server, the message to a mesh gate in communication with the one or more target devices upon receiving the message at the mesh gate, authenticating the message, removing message headers, and providing a table request to each of the identified target devices to control energy use of the identified target devices.

8. The method of claim 7, wherein the request is received via the simple object access protocol (SOAP).

9. The method of claim 7, wherein the message is provided as a table request is formatted for an ANSI C12.19 table.

10. The method of claim 7, wherein the message is formatted to ANSI C12.22 format.