Abstract:
A set sleep period is coordinated among a plurality of mesh network nodes to conserve power, and a temporarily reduced sleep period is coordinated among the plurality of nodes to facilitate mesh network node service or installation activity. The reduced sleep period comprises scheduling a period of time during which the sleep period is reduced, or reverting from the temporarily reduced sleep period to the original set sleep period after predetermined period of time. Temporarily reducing the sleep period includes distributing a message throughout the mesh network when the mesh network nodes are awake.

Description:
FIELD OF THE INVENTION 
       [0001]    The invention relates generally to mesh networks, and more specifically in one embodiment to mesh network commissioning by variable sleep. 
       LIMITED COPYRIGHT WAIVER 
       [0002]    A portion of the disclosure of this patent document contains material to which the claim of copyright protection is made. The copyright owner has no objection to the facsimile reproduction by any person of the patent document or the patent disclosure, as it appears in the U.S. Patent and Trademark Office file or records, but reserves all other rights whatsoever. 
       BACKGROUND 
       [0003]    Although computer networks have become relatively common both in office and in home networking environments, such networks are typically fairly sophisticated and require significant processing power, electrical power, and infrastructure to work well. Some networking applications do not require so robust a network environment, but can benefit from the ability to provide electronic communications between devices. 
         [0004]    One such example is the Bluetooth technology that enables a cell phone user to associate and use an earpiece in what is sometimes referred to as a personal area network or PAN. Another example is a mesh network, in which a number of devices work together to form a mesh, such that data can be sent from a source device to a destination device via other devices in the mesh network. 
         [0005]    Mesh networks often include multiple links from a network node to other network nodes nearby, and can thereby provide routing around broken links or paths by discovering other routes through the mesh to a destination node. New nodes to a mesh network are typically able to automatically discover the mesh network when they are activated in the vicinity of a compatible mesh network, and can easily join the network. 
         [0006]    But, joining a mesh network becomes somewhat more complex in network environments where different frequencies or network identifiers are used. In ZigBee mesh networks, for example, different frequencies or channels can be used for different networks, such as to prevent nodes from one network from interfering with another network. A new node wishing to join a network must therefore find the appropriate frequency or channel being used by the intended network before it can join the intended network. This is performed in one example by searching among the various available channels until a mesh network is found, but confirming that the node has joined the intended network is difficult. 
         [0007]    In addition to searching various frequencies or channels, some wireless mesh network technologies also sleep, or become inactive, to conserve power. For example, an array of battery powered sensors might be configured to wake up once every two hours and take a measurement, report the measurement via the mesh network, and go back to sleep. Use of sleeping nodes typically includes allowing end devices with reduced functionality to sleep, such as between taking and reporting measurements via router nodes that do not sleep. In other embodiments sleep times are synchronized between nodes in the network during configuration, so that all nodes are awake and able to contribute to mesh network communication at the same time. 
         [0008]    But, in environments where mesh network nodes sleep for extended periods of time, it becomes difficult to add new nodes to the network or perform certain other node or network operations. There exists a need to provide wireless mesh network technology that addresses management of a mesh network with sleeping nodes. 
       SUMMARY 
       [0009]    Some example embodiments of the invention comprise a mesh network of nodes having a set sleep period coordinated among the nodes to conserve power, and a temporarily reduced sleep period is coordinated among the plurality of nodes to facilitate mesh network node service or installation activity. In further examples, the reduced sleep period comprises scheduling a period of time during which the sleep period is reduced, or reverting from the temporarily reduced sleep period to the original set sleep period after a predetermined period of time. Temporarily reducing the sleep period includes distributing a message throughout the mesh network when the mesh network nodes are awake. 
     
    
     
       BRIEF DESCRIPTION OF THE FIGURES 
         [0010]      FIG. 1  shows an example wireless mesh network environment, consistent with an example embodiment of the invention. 
           [0011]      FIG. 2  is a flowchart illustrating a method of temporarily reducing sleep time in a wireless mesh network, consistent with an example embodiment of the invention. 
       
    
    
     DETAILED DESCRIPTION 
       [0012]    In the following detailed description of example embodiments of the invention, reference is made to specific examples by way of drawings and illustrations. These examples are described in sufficient detail to enable those skilled in the art to practice the invention, and serve to illustrate how the invention may be applied to various purposes or embodiments. Other embodiments of the invention exist and are within the scope of the invention, and logical, mechanical, electrical, and other changes may be made without departing from the subject or scope of the present invention. Features or limitations of various embodiments of the invention described herein, however essential to the example embodiments in which they are incorporated, do not limit the invention as a whole, and any reference to the invention, its elements, operation, and application do not limit the invention as a whole but serve only to define these example embodiments. The following detailed description does not, therefore, limit the scope of the invention, which is defined only by the appended claims. 
         [0013]    Mesh networks are often used to route data between various elements or nodes in a network made up of a number of loosely assembled nodes. Many mesh networks are designed such that a compatible node can easily join the network and receive and send data, including passing received data along a route to an intended destination node. Mesh networks are therefore often self-healing, in that if a node becomes inoperable or loses a connection to another node, data can be easily routed around the broken network link. 
         [0014]    Many mesh network technologies use wireless communication, further enhancing the ease of use of mesh networking for certain applications. Because mesh network nodes are typically stationary, wireless connections between various nodes can be formed and characterized by searching a known frequency or radio band for other mesh network nodes as new wireless nodes are added to the mesh network. Recent reductions in cost and advancement in wireless networking technology has made use of mesh networking for a variety of applications a desirable alternative to using a more structured network such as a TCP/IP network. 
         [0015]    One example of a mesh network standard using wireless radio communication is the ZigBee mesh network, which was developed by an industry alliance and is related to IEEE standards including 802.15.4. The retail price of ZigBee-compliant transceivers is nearly a dollar, and a transceiver, memory, and processor can be bought for a few dollars in quantity, making integration of mesh network technology into inexpensive electronic devices economically practical. The standard is intended to support low power consumption at reasonably low data rates, and provides a self-organizing network technology that works well for applications such as control, monitoring, sensing, and home automation. 
         [0016]    In this example of wireless mesh technology, one node operates as a coordinator, forming the root of the mesh network and performing other functions such as bridging to other networks and handling encryption keys. Most nodes are router nodes, which can receive and send data, including passing data along to other nodes. In some embodiments, end device nodes contain just enough functionality to receive and send data, but cannot route or pass data from a sending node to a different receiving node. While this preserves battery life and reduces the cost of the node, end device nodes are unable to contribute to the routing functions of the mesh network, and so will typically not make up a large percentage of a mesh network&#39;s nodes. 
         [0017]    Nodes in some mesh networks can also conserve power by entering a sleep mode, or becoming inactive for extended periods of time when operation is not necessary. For example, a mesh network of ground moisture sensors may only need to take and report measurements every two hours, and need only be awake for a few milliseconds every two hour period. The sleeping nodes in a further embodiment of such a network are synchronized during configuration of the network so that they wake at the same time, enabling the nodes to communicate with each other while awake and route data from neighboring nodes. 
         [0018]    New nodes are typically able to join an existing network by searching known radio channels on which the mesh network technology operates, and in further examples by looking for other mesh network nodes broadcasting data having a PAN ID that matches the PAN ID of the network that the new node wishes to join. But, this becomes more difficult if the other nodes in the network are asleep, and if it is unknown when or for how long the nodes will be awake. Further, the sleep timing of the network can be several hours or longer as illustrated by the previous example, which is likely longer than an installer will be willing to wait to install a new node or perform other network functions such as replacing or reconfiguring a node. 
         [0019]    This is solved in some embodiments by leaving at least one node powered, such as the coordinator node of the mesh network. The new node can join the network and synchronize its sleep schedule from the coordinator node, and will link to neighboring nodes in the mesh once placed in the mesh during the next wake cycle. Another option is to have all nodes in the mesh network remain awake after a certain wake cycle, so that the nodes remain awake while the installer works. This requires planning the service before the preceding wake period, and requires that all nodes remain on for an extended period of time which may significantly impact battery life. 
         [0020]    An improved approach includes sending the network a command to adjust the sleep/wake interval from a period that may not be tolerable, such as several hours, to a shorter period that is within the installer&#39;s tolerated waiting period, such as every two minutes. The reduced sleep cycle is in a further embodiment set on a temporary basis, such as for the next hour, after which time the sleep cycle reverts to its normal sleep period of several hours. 
         [0021]    In a more detailed example, a command is sent throughout the network before a planned service event to adjust the sleep interval of the mesh network to a significantly lower time, such as from several hours to seconds or minutes. The command is sent before the planned service time, so that the change in sleep period can be distributed to all nodes in the mesh network before the installation or service is to take place. Because the nodes need typically be on for only a few milliseconds, the reduction in power from being active once every minute or two relative to leaving the network nodes powered on full time is significant. 
         [0022]    Once the mesh network nodes have entered a reduced sleep period state, installation or service of nodes can take place without having to wait potentially hours or more between awake periods, or without having to be near a control node or other node that is constantly powered on. In a further example, a regular maintenance schedule is set, such as a half hour period occurring at the same time of day every Wednesday, during which the sleep interval is reduced to a matter of seconds or minutes. Using a regularly scheduled maintenance period removes the need to reconfigure the network for reduced sleep periods as long as maintenance or installation can be performed during the scheduled maintenance period. 
         [0023]      FIG. 1  is a diagram of a mesh network, consistent with an example embodiment of the invention. A gateway device  101  here includes a mesh network radio, and serves as a control node for the mesh network  102  as well as a bridge between the mesh network and an external network  105 . A number of mesh network nodes  102  are distributed about an area within radio contact of one another, such as security monitoring devices within a store or warehouse, water monitoring devices distributed about a golf course or farm, or military surveillance devices distributed about a hostile area. A mesh network device  103  is being newly installed, or is under maintenance. 
         [0024]    The gateway device  101  is also linked to a computer system  104  via the Internet  105 , such that the computer system is able to access the gateway  101  and configure the mesh network. In a further example, an Internet-enabled cell phone  106  is also able to access the gateway device  101  and configure or control the mesh network, enabling mesh network management from remote locations such as locations within the mesh network. 
         [0025]      FIG. 2  is a flowchart of a method of setting a reduced sleep period in a mesh network, consistent with an example embodiment of the invention. In this example, a network sensor has been damaged and needs to be replaced. The technician in charge of managing the network expects to be in the area to replace the failed sensor the next day between 2 pm and 4 pm. 
         [0026]    The installer therefore sends a network command to the mesh network at  201 , altering the sleep period from 2 pm to 4 pm the next day at  201 . The mesh network gateway device that remains powered receives the command via a network such as the Internet to alter the mesh network sleep timing, and at  202  the mesh network nodes wake, and the altered sleep period and schedule is distributed to the mesh network nodes. 
         [0027]    The next day at 2 pm, the mesh network nodes adjust their sleep periods from two hours to one minute for the next two hours at  203 . When the technician arrives between 2 pm and 4 pm, he powers on the new mesh network sensor device and waits a maximum of one minute for the surrounding nodes to wake and communicate with the new device at  204 . The technician confirms the node has joined the network, such as by observing a light or other indicator on the device, or by querying the network via an Internet-enabled cell phone. The technician then leaves the network site, and the network resumes its normal sleep period of two hours starting at 4 pm. In an alternate embodiment, the technician indicates that he is done by communicating with the gateway device via an Internet connection, and the network reverts to its normal sleep period when it next wakes as shown at  205 . 
         [0028]    Use of an adjustable sleep period to facilitate service such as in the above examples provides for significantly improved battery life of the mesh network devices, requiring in some embodiments hundreds of times less power than would be consumed if the nodes were left powered on over the same service period. The technician can also install or maintain a device in its intended location, and need not find or travel to a continually powered node or gateway device to perform node maintenance. 
         [0029]    Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiments shown. This application is intended to cover any adaptations or variations of the example embodiments of the invention described herein. It is intended that this invention be limited only by the claims, and the full scope of equivalents thereof.