Abstract:
Systems and methods for over-the-air firmware distribution to battery-powered devices are disclosed. Such over-the-air distribution is accomplished, for example, using a non-battery-powered device as a buffer, for example, to reduce or eliminate the delay time of the over-the-air network. The firmware can be sent to and stored on a nearby, non-battery-powered device and then sent from there to the battery-powered endpoint device. The distribution of firmware to battery-powered devices may be implemented in an AMI system, a mesh network, a multi-channel radio network, or any other environment in which firmware distribution is desirable.

Description:
TECHNICAL FIELD 
       [0001]    This disclosure relates generally to distributing firmware, including methods and systems of distributing firmware to battery-powered devices used in advanced metering infrastructure (AMI) systems, among other environments. 
       BACKGROUND 
       [0002]    Radio communication-based networks are widespread and used for a variety of applications. Such networks are commonly employed in AMI systems that measure, collect, and/or analyze utility usage from electricity, gas, water, and other meters through various communication media. Network node devices and/or endpoint devices of such systems typically include firmware. Over-the-air download of firmware is generally only feasible for non-battery-powered devices. Sending firmware to battery-powered devices has required that such devices stay “awake” for an extended period of time, for example, while packets are exchanged between the device and a firmware providing host. Staying awake, with transmission hardware draining the battery, for these extended periods of time uses a significant portion of the battery&#39;s life and makes such techniques unfeasible. 
       SUMMARY OF THE INVENTION 
       [0003]    Systems and methods for over-the-air firmware distribution to battery-powered devices are disclosed. Such over-the-air distribution is accomplished, for example, using a non-battery-powered device located closer to the battery-powered device. For example, to minimize the burden on the network access points and reduce or eliminate the delay time of the over-the-air network, the firmware can be sent to and stored on a nearby non-battery-powered device and then sent from there to the battery-powered endpoint device. The distribution of firmware to battery-powered devices may be implemented as part of an AMI system, a mesh network, a multi-channel radio network, or in any other environment in which firmware distribution is desirable. 
         [0004]    These embodiments are mentioned to provide examples and aid understanding. Additional embodiments and advantages are also discussed in the Detailed Description and will become readily apparent to those skilled in the art. As will be realized, the invention is capable of other and different embodiments, and its several details are not essential, but rather are capable of modifications in various obvious respects, all without departing from the invention. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive. 
     
    
     
       BRIEF DESCRIPTION OF THE FIGURES 
         [0005]    The above described and other features, aspects, and advantages of the present disclosure are better understood when the following Detailed Description is read with reference to the accompanying drawings, wherein: 
           [0006]      FIG. 1  is a system diagram illustrating an exemplary network environment; 
           [0007]      FIGS. 2   a - b  are system diagrams illustrating exemplary communication of firmware to a battery-powered device; 
           [0008]      FIG. 3  is a system diagram illustrating firmware download from a non-battery-powered network node devices to a battery-powered network node device; and 
           [0009]      FIG. 4  is a flow diagram illustrating an exemplary method of providing firmware to a battery-powered network node device. 
       
    
    
     DETAILED DESCRIPTION 
       [0010]      FIG. 1  is a system diagram illustrating an exemplary network environment. Other embodiments may be utilized. The network  10  shown in  FIG. 1  comprises access points  20 ,  21  and other devices, referred to herein as network node devices  30 - 41 . The network node devices  30 - 41  work together to create a mesh network in which each network node device generally comprises a radio that can speak to and respond to neighboring radio devices of neighboring network node devices. Each network node devices may comprise or connect to an endpoint device such as a utility meter or appliance, or may not itself comprise or connect to an endpoint device. Thus, a network node device may interact with an endpoint device, act as part of the network, or both, and may do so simultaneously. The radio of each network node devices may have a programmable logic controller (PLC)—like device. Such a device can enable the radio to function like a small computer, carrying out appropriate computing and command functions. Thus, intelligence in some or all of the radios may be used to delegate and distribute commands throughout the network  10 . The radio may, but need not necessarily, allow two-way communication. 
         [0011]    As an example of a utility monitoring network, each network node device of network  10  that comprises or connects to an endpoint may collect information about utility consumption at that endpoint and send such information through the network  10  to an access point  20 ,  21 , where it may be collected by a utility company, for example, for billing and/or monitoring purposes. As a more specific example, an endpoint device radio may generate a packet of data that is transmitted to some destination, such as an access point destination. The packet may be addressed to the destination and entered into the network. The data packet traverses the network by hopping from radio to radio (network node device to network node device) in the direction of the destination-addressed radio. The route chosen for traversing the network may be dynamic and/or may employ automatic rerouting in the event a particular data path is not clear. Generally, the network  10  will attempt to minimize the number of hops to increase transmission speed. The radio and/or other components at a network node device/endpoint device may be battery-powered, line-powered, or powered by any other suitable power source and attached via any suitable connection. 
         [0012]      FIGS. 2   a - b  are flow diagrams illustrating exemplary communication of firmware to a battery-powered device  230 . Each of the network node devices  220   a,    220   b,    230  of the network  220  may have a storage area for the device&#39;s main code and additional download space providing a buffer memory area. In the example depicted in  FIGS. 2   a - 2   b,  a non-battery-powered device  220   b  of the system  200  is used to assist a battery-powered device  230  with firmware upgrades. The non-battery-powered device  220   b  has a memory space allocated for holding its own firmware upgrades as they are downloaded over the network  220  from a host  210 . That memory space of the non-battery-powered device  220   b  is also used to store new firmware that is ultimately sent to the battery-powered device  230 . 
         [0013]    The non-battery-powered network node devices  220   b  may be selected to assist with the firmware download based on its network proximity to the battery-powered device  230 . For example, the non-battery-powered device  220   b  may be, but need not be, adjacent to or the nearest neighbor to the battery-powered device  230 . The non-battery-powered device may be a device that communicates directly with the battery-powered devices for other purposes, e.g., to communicate consumption data in a consumption data collection system. Node  220   b,  once it has received a full copy of the battery-node&#39;s firmware, may provide the firmware to multiple battery-nodes. A non-battery-powered device can service one to any number of battery-powered devices by direct node-to-node communication, through some form of broadcast, or otherwise. The number of non-battery-powered devices used to distribute the firmware may depend on the specific network. For example, if the network consists of electric meters, non-battery-powered devices may be very common and, in many cases, quite close to a battery powered device. As another example, if the network was involved only water utility meters, then the number of non-battery devices might be relatively small. In certain embodiments, the download of firmware (for a battery-powered device) to a non-battery-powered device may not all the way from the host. For example, the system may have the capability of commanding a node in the network to go and get a copy of code from another node (presumably nearby) without going all the way back to the host. 
         [0014]    In  FIG. 2   a,  a firmware providing host  210  sends the firmware in one or more communications  240  into the network  220 . The firmware is stored on a non-battery-powered network node device  220   b.  In response to each communication  240 , the non-battery-powered network node device  220   b  may send an acknowledgement  250  through the network  220  and back to the host  210 . In this example, the host utilized an access network node device  220   a  to access the network  220 . However, a host or other firmware providing device may access the network in any suitable manner and/or may itself be considered a part of the network  220 . During the potentially lengthy time that the firmware is traversing the network  220  and being compiled in the non-battery-powered network node device  220   b,  the battery-powered network node device will generally remain asleep, i.e., having its radio receiver powered down or otherwise not in a state of readiness to receive a transmission. 
         [0015]    In  FIG. 2   b,  the non-battery-powered network node device  220   b  sends the firmware in one or more communications  260  to the battery-powered network node device  230 . In response to each communication  260 , the battery-powered network node device  230  may send an acknowledgement  270  back to the non-battery-powered network node device  220   b.  The communications  260  and acknowledgements  270  may be directly between the network node devices  220   b,    230  or may involve additional network node devices. Once the firmware is completely downloaded to the battery-powered device  230 , the device  230  may be made aware of and begin using it the next time the device  230  wakes up. 
         [0016]    A battery-powered node device is, in general, aware that a firmware download is in-process, because such a high quantity of communication is abnormal for it. It will have special memory spaces for the code currently executing, and the new code being downloaded. If the process gets interrupted for any reason (like a power outage in the powered-part of the network) the process may be resumed where it left off. 
         [0017]    A non-battery-powered node device may make a battery-powered node device that it has firmware available and the battery-powered node device may then determine whether it wants or needs the firmware. For example, a battery-powered node device may already have the current firmware image and determine to decline the offered firmware download. At the conclusion of a download, a battery-powered node device may send a message to the firmware providing host indicating it is now running newer firmware. 
         [0018]    Because the firmware is locally stored in a network node device  220   b  that is in close or direct communication with the battery-powered device  230 , the firmware can be quickly copied, greatly reducing the associated battery power consumption and making viable the download of firmware to the battery-powered device  230 , where it might otherwise be unfeasible to do so. We should be clear that simply splitting the code into two pieces, and downloading it from the host in 2 steps is still the same—essentially buffering the code at the neighbor for fast transfer to the end node in larger pieces. 
         [0019]    The download to the battery-powered device  230  may be initiated in a variety of ways. For example, a battery-powered node device may be programmed to wake and listen at intervals between regular data transmission. During these listen periods, the device can be informed if there is something that requires their attention, such as a new firmware download or portion thereof. As another example, a battery-powered node device may be awoken with a wake-up signal from a host or other network node. An example of a wake-up signal is a strong, brief RF tone on a known frequency received by an ultra-low powered tuned-circuit that is always active to pick up the signal and wake the processor. 
         [0020]    The download to the battery-powered device  230  may be initiated after a transmission from the battery-powered device  230 . For example, if the battery-powered device  230  is an endpoint metering device in an AMI system, the endpoint device may periodically transmit commodity consumption information collected at the endpoint. Transmission hardware at an endpoint device, such as a radio receiver, may stay awake after such a transmission waiting for an acknowledgement of receipt. A device component may be considered “awake” when it is receiving power from a battery or non-battery power source and is capable of receiving a transmission, and “asleep” when it is powered down or otherwise not in a state of readiness to receive a transmission. 
         [0021]    In the case where a firmware download is desired for an endpoint device, an acknowledgement may tell the transmission components at the endpoint device to stay awake, so that a firmware download from an adjacent or nearby network node devices can begin. Whether the transmission portion of a device is awake or asleep generally will not interfere with the endpoint device&#39;s other functions, for example, monitoring consumption of a commodity. 
         [0022]    As an alternative to two-way streaming and other download techniques, consumption information transmission acknowledgements may themselves be used to provide the firmware. For example, the firmware could be provided within a series of acknowledgement transmissions, e.g., acknowledging receipt of consumption data at a nearby network node device. This nearby network node device, in addition to receiving the buffered data and sending it on through the network, may also buffer firmware to be downloaded to the battery-powered network node. Each acknowledgement transmission may carry a small portion of the firmware to the battery-powered network node. 
         [0023]      FIG. 3  is a system diagram illustrating firmware download from a non-battery-powered network node device  300  to a battery-powered network node device  310 . The non-battery-powered network node devices  300  comprises firmware  301 , a data storage area  302 , transmission hardware  304 , and a non-battery power source  305 . The battery-powered network node device  310  comprises firmware  311 , a data storage area  312 , transmission hardware  314 , and a battery power source  315 . The data storage area  302  of the non-battery-powered network node device  300  may be used as a buffer to store firmware  303  intended for the battery-powered network node device  310 . 
         [0024]    The firmware  303  may be sent from the non-battery-powered network node device  300  to the battery-powered network node device  310  in one or more communications  320 , each of which may or may not be acknowledged by an acknowledgment  330 . The downloaded firmware  303  may be stored in the data storage area  312  of the battery-powered network node device  310  while the download occurs, may be transferred directly to replace the device&#39;s existing firmware  311 , or downloaded in any other suitable manner. If downloaded to a data storage area  312 , the downloaded firmware  303  will generally be transferred to replace the device&#39;s existing firmware  311 . 
         [0025]      FIG. 4  is a flow diagram illustrating an exemplary method  400  of providing firmware to a battery-powered network node device. The method comprises providing a mesh network comprising network node devices, as shown in block  410 . In some cases, at least some of the network node devices will be endpoint devices, such as endpoint devices of a commodity consumption collection network or AMI system. 
         [0026]    The method  400  further comprises providing firmware to a non-battery-powered network node device of the mesh network. For example, a firmware-providing host may send the firmware to the non-battery-powered network node device. The host may select the non-battery-powered network node device as an appropriate device to assist in providing firmware to battery-powered device. As another example, the non-battery-powered device may recognize that a battery-powered device with which it communicates is in need of a firmware upgrade and request the updated firmware from a firmware source. Other techniques for identifying battery-powered devices in need of firmware and non-battery-powered devices usable to assist in downloading may be used. 
         [0027]    The method  400  further comprises storing the firmware on the non-battery-powered network node device in a memory. For example, the non-battery-powered device may have a data storage memory area that it uses to buffer its own firmware downloads. This buffer area may be used to store the firmware that is to be provided to the battery-powered network node device. 
         [0028]    The method  400  further comprises providing the firmware to a battery-powered network node device of the mesh network from the memory of the non-battery-powered network node device. This may involve downloading the firmware in a single session in which the battery-operated network node device remains awake or may involve discrete sessions in which a portion of firmware is received. For example, in a consumption data collection system, consumption information transmission acknowledgements may be used to provide segments of the firmware. 
         [0029]    One embodiment of the present disclosure is a method that involves providing a mesh network of network node devices and storing firmware in a memory of a non-battery-powered network node device. The method involves providing a first portion of the firmware in a first transmission to a battery-powered network node device from the memory of the non-battery-powered network node device. The method further involves providing a second portion of the firmware in a second transmission to the battery-powered network node device from the memory of the non-battery-powered network node device. The transmissions may be acknowledgement transmissions of received data such as commodity consumption data. The method may further involve configuring a transmission component of the battery-powered network node to send data to the non-battery-powered network node and remain awake after sending data only while awaiting an acknowledgement. The transmission component of the battery-powered network node may be asleep for a period of time between a receipt of the first acknowledgement and a receipt of the second acknowledgement. 
         [0030]    One embodiment of the present disclosure is a method that involves providing a mesh network comprising network node devices and configuring a transmission component of the battery-powered network node to send data to the non-battery-powered network node and remain awake after sending data only while awaiting acknowledgement of receipt of the data. The method may involve storing firmware in a memory of a non-battery-powered network node device of the mesh network and providing the firmware in a series of acknowledgement transmissions to the battery-powered network node device from the memory of the non-battery-powered network node device. Each of the acknowledgment transmissions acknowledges receipt of data from the battery-powered network node and comprising a portion of the firmware. The transmission component of the battery-powered network node may not be awake for a download time period over which the firmware is provided to the battery-powered network node and/or for a time period after each acknowledgement of the series of acknowledgements is received. 
       General 
       [0031]    The foregoing description of the embodiments of the invention has been presented only for the purpose of illustration and description and is not intended to be exhaustive or to limit the invention to the precise forms disclosed. For example, the uses of firmware downloading and updating on battery-powered devices are numerous and not limited by the examples described herein. The techniques of the invention are not limited to AMI systems, mesh networks, or any other particular network configuration. Thus, in general, numerous modifications and adaptations are apparent to those skilled in the art without departing from the spirit and scope of the invention.