Point-to-point communication with low-power devices

Abstract

A method for establishing a communications link is described. The method includes transmitting, by a diagnostic tool, a wireless wake signal on a wake radio channel to a low-power endpoint in a measurement mesh network. The wake radio channel is selected using a unique identifier of the low-power endpoint. The method also includes receiving, at the diagnostic tool, a confirmation message from the low-power endpoint that the wireless wake signal was received at the low-power endpoint. The method further includes establishing, by the diagnostic tool, a communications link between the diagnostic tool and the low-power endpoint on a wireless communication channel different from the wake radio channel. The method further includes performing, by the diagnostic tool, a diagnostic operation on the low-power endpoint.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of and priority to U.S. Provisional Application No. 62 / 826,370, filed March 29, 2019, and entitled "POINT TO POINT COMMUNICATION WITH LOW-POWER DEVICE," the entire contents of which are incorporated herein by reference.

[0002] Technical Field Examples of the subject matter of this disclosure relate to communication between devices, and in particular, to communication between diagnostic tools and low power or battery operated devices. [Background technology]

[0003] Advanced Metering Infrastructure (AMI) technology is transitioning metering infrastructure to a system of smart communication devices and technologies. Low power or battery operated endpoints in AMI are designed to operate for decades before battery replacement. While extending battery life, low power or battery operated endpoints have inherent operational limitations due to the limited power available to them. For example, a low power or battery operated endpoint may periodically communicate with a fully functional parent endpoint. When the low power or battery operated endpoint is not communicating with the parent electrical endpoint, the low power or battery operated endpoint may operate in a sleep mode to limit power consumption.

[0004] Magnet busting techniques may be performed to wake up a low power or battery operated endpoint (e.g., to perform diagnostic or other communication operations outside of the endpoint's normal operating parameters). Magnet busting techniques include waking a low power or battery operated endpoint from a sleep mode. Using magnet busting techniques to wake a low power or battery operated endpoint increases power consumption compared to the low power or battery operated endpoint's power consumption during normal operation. Additionally, magnet busting techniques require a technician to be physically close to the low power or battery operated endpoint to perform diagnostic operations. As an example, a low power or battery operated endpoint may be located several feet underground or within the basement of a building. In such an example, a technician must place a magnet near the magnet receptor of the low power or battery operated endpoint at an underground location or within the basement of a building to control the low power or battery operated endpoint from a sleep mode to an operating mode, which may require excavation in an underground location and may cause inconvenience to building occupants in a building basement. Summary of the Invention [Problem to be solved by the invention]

[0005] SUMMARY OF THE DISCLOSURE Systems and methods are provided for providing point-to-point communication in low power devices. [Means for solving the problem]

[0006] According to various aspects of the present disclosure, a method for establishing a communications link is provided. The method includes transmitting, by a diagnostic tool, a wireless wake signal on a wake radio channel to a low power endpoint in a measurement mesh network. The wake radio channel is selected using a unique identifier of the low power endpoint. The method also includes receiving, at the diagnostic tool, a confirmation message from the low power endpoint indicating that the wireless wake signal was received at the low power endpoint. The method further includes establishing, by the diagnostic tool, a communications link between the diagnostic tool and the low power endpoint on a wireless communication channel different from the wake radio channel. The method further includes performing, by the diagnostic tool, a diagnostic operation of the low power endpoint.

[0007] In a further example, a node of the networked system includes a processor that executes computer readable instructions and a memory that stores computer readable instructions that, when executed by the processor, cause the processor to perform operations. The operations include transitioning to a sleep mode and transitioning to a wake mode that listens for a wake signal from a diagnostic tool. The operations also include receiving, in the wake mode, the wake signal from the diagnostic tool on a wake radio channel. The wake radio channel is selected using a unique identifier of the node. Additionally, the operations include establishing a communications link with the diagnostic tool on a communications channel different from the wake radio channel, and performing a diagnostic operation with the diagnostic tool on the communications channel.

[0008] In a further example, a non-transitory computer readable medium having instructions stored therein is provided. The instructions are executable by a processing device to perform operations including controlling the low power endpoint to transition to a sleep mode and controlling the low power endpoint to listen for a wake signal from a diagnostic tool and transition to the wake mode. The operations further include receiving, at the low power endpoint, the wake signal from the diagnostic tool on a wake radio channel. The wake radio channel is determined from a unique identifier of the low power endpoint. The operations further include controlling the low power endpoint to establish a communications link between the low power endpoint and the diagnostic tool on a communications channel different from the wake radio channel. The operations further include controlling the low power endpoint to perform a diagnostic operation with the diagnostic tool on the communications channel.

[0009] These exemplary aspects and features are mentioned not to limit or define the subject matter of the disclosure, but to provide examples to aid in understanding the concepts described in the present application. Other aspects, advantages, and features of the subject matter of the disclosure will become apparent after consideration of the entire application. [Brief description of the drawings]

[0010] BRIEF DESCRIPTION OF THE DRAWINGS Aspects and features of various embodiments will become more apparent from the following detailed description of the embodiments, taken in conjunction with the accompanying drawings.

[0011] [Figure 1] FIG. 1 is a block diagram of a networked system and a mesh network of smart devices according to one or more embodiments. [Diagram 2] FIG. 2 is a flow chart of a process for establishing a point-to-point communication link between a diagnostic tool 110 and a battery-powered endpoint according to one or more embodiments. [Figure 3A]3A and 3B include example workflows for establishing point-to-point communications between a battery-powered endpoint and a communications tool according to one or more embodiments. [Figure 3B] 3A and 3B include example workflows for establishing point-to-point communications between a battery-powered endpoint and a communications tool according to one or more embodiments. [Figure 4] FIG. 4 is an example block diagram of a node of the networked system of FIG. 1 according to one or more embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Although specific embodiments are described herein, these embodiments are presented by way of example only and are not intended to limit the scope of protection. The devices, methods and systems described herein can be embodied in various other forms. Furthermore, various omissions, substitutions and changes in the form of the exemplary methods and systems described herein can be made without departing from the scope of protection.

[0013] Certain aspects and embodiments of the present disclosure relate to systems and methods used to communicate with a Battery Operated Endpoint (BEP), which may be a component of a mesh network related to resource metering. In such examples, the BEP may be used to provide resource metering information or BEP status information to other devices in the mesh network, such as additional metering endpoints or a head-end system of the mesh network.

[0014] A technician may implement point-to-point communication techniques to perform diagnostic services on the BEP. For example, point-to-point communication techniques may be used by a technician to communicatively link a diagnostic communication tool with the BEP without relying on magnet busting operations. By avoiding magnet busting operations, the BEP may conserve battery power and extend the life of the batteries that power the BEP. Additionally, point-to-point communication techniques may avoid a requirement that a technician be in physical proximity to the BEP.

[0015] In one example, an external software application (e.g., a diagnostic application or a field application) executing on a diagnostic tool can receive authorization from a central system (e.g., an Advanced Metering Infrastructure (AMI) head-end system). A user of the diagnostic tool initiates a connection between the device running the external software application and a local radio (e.g., a communications adapter). The communications adapter provides the functionality to send data to and receive data from the BEP.

[0016] In operation, the communications adapter sends a connection command (e.g., a wake-up message) to the battery-powered endpoint using a particular frequency channel based on a unique identifier (e.g., a serial number or LAN ID) of the battery-powered endpoint. The battery-powered endpoint periodically listens for a wake-up message from a parent endpoint or other device. In one example, the battery-powered endpoint listens for a wake-up message on a particular frequency channel based on the unique identifier of the battery-powered endpoint. When the battery-powered endpoint receives the connection command, the battery-powered endpoint provides an indication to the communications adapter that the connection command was received.

[0017] Once a response is received from the battery powered endpoint at the communications adapter, the diagnostic tool running the external software application can communicatively connect to the battery powered endpoint through the communications adapter. This connection can occur upon completion of an authentication process that verifies that the device running the external software application has authorization to access the restricted electronic data of the battery powered endpoint. Once connected, the diagnostic tool can use the external software application to initiate a diagnostic process related to wireless operation of the battery powered endpoint, a diagnostic process related to a metering device in communication with the battery powered endpoint, or a combination thereof.

[0018] The described embodiments provide a point-to-point communication technique that enables communication between a diagnostic device and a battery-powered endpoint. Although the point-to-point communication technique is generally described for use with battery-powered endpoints that provide resource metering functionality, it is by no means limited to such. Rather, embodiments of the point-to-point communication technique may be used as desired, such as with any type of low-power device. For example, the point-to-point communication technique may be used with any low-power endpoint, such as a battery-powered endpoint, an endpoint with limited access to a power source, or an endpoint that is not connected to a mains power source.

[0019] FIG. 1 is a block diagram illustrating an embodiment of a networked system 100 and a mesh network 101. The networked system 100 and the mesh network 101 provide a network infrastructure for smart devices (e.g., resource consumption meters, vehicles, home appliances, etc., including communication technology) to communicate over a network of nodes (i.e., other smart devices), the Internet, and / or an intranet. The networked system 100 includes a head-end system 102, which may act as a central processing system that receives a stream of data from a network 104. The network 104 may be the Internet, an intranet, or any other data communication network. The mesh network 101 may include a root node 106 and other nodes 108a-108h that collect data relevant to the root node 106 and other nodes 108a-108h that transmit the collected data to the network 104 and ultimately to the head-end system 102 of the networked system 100. The root node 106 may be a personal area network (PAN) coordinator, an Internet gateway, or any other device capable of connecting to the network 104 .

[0020] The root node 106 may be generally referred to as a parent node due to data links with nodes 108a and 108b located in a node layer (e.g., layer 1) below the root node 106. For example, the root node 106 is shown in direct communication with the network 104. As shown, the nodes 108a and 108b may also be referred to as parent nodes due to data links with nodes 108c, 108d, 108e, and 108g located in a node layer (e.g., layer 2) below the nodes 108a and 108b. Additionally, the nodes 108e and 108g may also be referred to as parent nodes due to data links with nodes 108f and 108h located in a node layer (e.g., layer 3) below the nodes 108e and 108g. The nodes 108a-108h may all funnel information through the node layers to the root node 106 and ultimately to the head-end system 102.

[0021] In operation, fewer or more nodes 108 may be included in the mesh network 101, and more root nodes 106 may be included in the networking system 100. Additionally, the mesh network 101 depicted in FIG. 1 includes a root node layer (i.e., root node 106), layer 1 (i.e., nodes 108a and 108b), layer 2 (i.e., nodes 108c, 108d, 108e, and 108g), and layer 3 (i.e., nodes 108f and 108h), although fewer or more node layers are contemplated. Additionally, while FIG. 1 depicts a particular network topology (e.g., a DODAG tree topology), other network topologies (e.g., ring topology, mesh topology, star topology, etc.) are possible.

[0022] The head-end system 102 may track the operating and non-operational nodes 106 and 108a-108h. To track the status of the nodes 106 and 108a-108h, the nodes 106 and 108a-108h may track periodic communications between the nodes 106 and 108a-108h and report interrupted communications that are up over the mesh network 101 to the head-end system 102. The reported communications may indicate to the head-end system 102 that one or more of the nodes 106 and 108a-108h are no longer operating. Other techniques may also be used to track the operational status of the nodes 106 and 108a-108h.

[0023] When the head-end system 102 receives an indication of one or more of the non-operational nodes 106 and 108a-108h, the head-end system 102 may notify a technician of the problem and instruct the technician to perform diagnostics on the non-operational nodes 106 and 108a-108h. In another example, a technician may be deployed to perform routine preventative diagnostics on the nodes 106 and 108a-108h regardless of their operational status. For example, a technician may be deployed to diagnose, repair, or replace the nodes 106 and 108a-108h that have been identified as being out of service or for scheduled maintenance. As used herein, the nodes 106 and 108a-108h may be considered "out of service" when the nodes 106 and 108a-108h do not meet one or more specified performance thresholds. In one example, the specified performance threshold may include a detected lack of communication from a particular node 106 or node 108a-108h for a specified period of time. In another example, the specified performance threshold may include the quality of measurement data received from a particular node 106 or node 108a-108h.

[0024] The technician may receive an indication that node 108d is non-operational or scheduled for routine maintenance. As shown, node 108d is a battery-powered endpoint. Because node 108d is a battery-powered endpoint, node 108d transitions in and out of sleep status during normal operation to conserve battery power. To wake node 108d from sleep status to perform diagnostics on node 108d, diagnostic tool 110 may transmit a wake signal 112 using communications adapter 114. Wake signal 112 may be a specific frequency or channel based on node 108d's serial number, LAN ID, or other identification source. For example, if node 108d's LAN ID is AABBCCDD, the last or final byte of the LAN ID may be used to determine node 108d's wake-up channel or frequency. Node 108d's wake-up channel or frequency may be a channel or frequency not used in mesh network 101. Upon receiving a wake-up signal 112 on the wake-up channel or frequency, node 108d may wake up from its sleep mode.

[0025] In one example, node 108d may wake up from a sleep mode at set intervals to listen for standard communications from other nodes (e.g., node 108a). Node 108d may also listen for a wake signal 112 at set intervals. In one example, the set intervals for listening for the wake signal 112 are less frequent than the standard communication intervals. Once the wake signal 112 is received, a communication link between the diagnostic tool 110 and node 108d may then be established, as described in more detail below with respect to FIGS. 2 and 3.

[0026] Because the diagnostic tool 110 provides the wake signal 112 to the node 108d as a wireless signal, only the communications adapter 114 needs to be within wireless range of the node 108d. In some examples, the communications adapter 114 may be a wireless communication device in communication with the Internet at the premises of the node 108d, and the diagnostic tool 110 may be a computing device also in communication with the Internet, such that the diagnostic tool 110 has access to control the communications adapter 114. In such examples, the diagnostic tool 110 may be located remotely from the communications adapter 114. In other examples, the diagnostic tool 110 and the communications adapter 114 may be integrated into a single device for use by a technician at the premises of the node 108d.

[0027] 2 is a flow chart of a process 200 for establishing a point-to-point communications link between a diagnostic tool 110 and a battery powered endpoint, such as node 108d. At block 202, process 200 includes receiving an indication of an inoperative, battery powered endpoint, such as node 108d, or receiving an indication of scheduled maintenance for the battery powered endpoint. Upon receiving the indication of the inoperative, battery powered endpoint or the indication of scheduled maintenance, a technician may be dispatched to the premises of the battery powered endpoint.

[0028] At block 204, process 200 includes transmitting a wake signal 112 from the communications adapter 114 within wireless range of the battery powered endpoint. Because the battery powered endpoint wakes periodically to check for the wake signal 112, the communications adapter may transmit a constant signal for a set period of time to ensure that the wake signal 112 is transmitted during one or more wake periods of the battery powered endpoint. In an example where the battery powered endpoint listens for the wake signal 112 for a short period every 5 seconds, the communications adapter 114 may transmit the wake signal 112 for 5 seconds or more to ensure that the battery powered endpoint receives the wake signal 112.

[0029] At block 206, process 200 includes performing an authentication process to authenticate the wake signal 112. In some examples, the authentication process may be any step that ensures that the diagnostic tool 110 is a device authorized to communicate with the battery-powered endpoint. For example, the diagnostic tool 110 may provide a Mobile Authentication Token (MAT) to the battery-powered endpoint via the communications adapter 114, and the battery-powered endpoint may respond with a message indicating that the MAT was accepted and a secure connection was established.

[0030] At block 208, process 200 includes establishing a communication link between diagnostic tool 110 and the battery-powered endpoint. In one example, establishing the communication link may include synchronizing a communication channel between the battery-powered endpoint and diagnostic tool 110. For example, the battery-powered endpoint may provide a message to diagnostic tool 110 indicating a communication channel to be used for further diagnostic communications. In some examples, the battery-powered endpoint and diagnostic tool 110 may communicate using a frequency hopping pattern.

[0031] At block 210, process 200 includes performing diagnostic activities on the battery powered endpoint. The diagnostic activities may include diagnostic processes on the wireless operation of the battery powered endpoint, diagnostic processes on the metering operation of the battery powered endpoint, or a combination thereof. The diagnostic activities may provide a technician with information regarding the system of the battery powered endpoint that is functioning properly or not.

[0032] At block 212, the process 200 includes releasing the communication link upon completion of the diagnostic process. Once the communication link is released, the battery powered endpoint may resume a standard sleep and wake pattern with other nodes 108 of the mesh network 101. In one or more examples, creating a communication link between the diagnostic tool 110 and the battery powered endpoint may include removing the battery powered endpoint from communications on the mesh network 101. Upon releasing the communication link after completion of the diagnostic operation, the battery powered endpoint may rejoin the mesh network 101 to resume communications on the mesh network 101.

[0033] 3A and 3B include an example of a workflow 300 for establishing point-to-point communication between an external software application running on the diagnostic tool 110 and a node 108d (e.g., a low-power or battery-operated endpoint). By using the workflow 300, a technician does not need to be within a certain physical proximity of the node 108d. That is, the technician does not need to physically contact the node 108d. Furthermore, excessive power consumption due to the wake-up process associated with the magnet busting operation is avoided. In one example, an external software application running on the diagnostic tool 110 can establish a communication link with the node 108d using wireless communication without first performing a magnet busting operation. In the example of FIG. 3A and 3B, the node 108d is represented by a water communication module 302 (e.g., a radio) that communicates with a water meter 304. Other metering systems and devices, such as electrical metering systems, can also perform point-to-point communication techniques in a similar manner. In one example, workflow 300 can be executed in the field to receive diagnostic information from a water module deployed at a customer premises, or workflow 300 can be executed in a test environment where a water module is not deployed at a metering location (e.g., not deployed inside a test lab).

[0034] The workflow 300 can be used in an RF mesh environment or in an RF mesh IP environment. For illustrative purposes, the workflow 300 is depicted as an interaction between a diagnostic tool 110 running an external diagnostic software application and an endpoint 108d including a water module 302 and a water meter 304. However, other software applications and endpoint configurations are contemplated within the scope of this disclosure. As shown in FIG. 3A, the endpoint 108d may initially register with the head-end system 102 so that the endpoint 108d can receive communications from the head-end system 102 over the mesh network 101. After successful registration with the head-end system 102, the wake and sleep cycle modes of the endpoint 108d may be disabled to conserve battery. To enable the wake and sleep cycle modes, the head-end system 102 may send an "Enable Tool Mode" command when it receives an indication that a technician will be performing a diagnostic operation on the endpoint 108d. The “Enable Tool Mode” command instructs the water module 302 to begin a wake and sleep cycle for the period of time expected by the technician so that the endpoint 108 d can listen for a wake signal from the communications adapter 114 .

[0035] Diagnostic tool 110 communicates with communications adapter 114 using Bluetooth or a serial communications link. Over the Bluetooth or serial communications link, diagnostic tool 110 sends a message to communications adapter 114 to initiate establishment of a communications adapter communications link. In response, communications adapter 114 provides a success response. If a success response is returned to diagnostic tool 110, diagnostic tool 110 then provides an indication to communications adapter 114 that it has established a connection (e.g., a communications link) with node 108d (e.g., via water module 302 or other wireless portion of node 108d).

[0036] When the communications adapter 114 receives an indication of connection to the meter from the diagnostic tool 110, it sends a wake-up message (e.g., wake signal 112 in FIG. 1) to the water module 302. The wake-up message is sent on a frequency or channel associated with the meter's unique identifier (e.g., serial number or LAN ID). For example, the communications adapter 114 and the water module 302 may use a channel corresponding to the low-order byte of the LAN ID. To ensure that the wake-up message is sent while the water module 302 is in a periodic listening state for a limited time, the communications adapter may send the wake-up message for a time sufficient to ensure that the water module 302 has cycled through at least one wake and sleep cycle. For example, if the water module 302 wakes for 1 ms every 5 seconds, the communications adapter 114 may send the wake-up message for at least 10 seconds. When the water module 302 receives the wake-up message, the water module 302 exits sleep mode and provides an acknowledgment to the communications adapter 114 that the wake-up message was received. Upon exiting sleep mode, the water module may disconnect from any parent endpoints of the mesh network 101 in which the water module 302 was operating (eg, node 108a in FIG. 1).

[0037] In response to an acknowledgement from the water module 302 that the wake-up message was received, the communications adapter 114 provides a radio frequency configuration message to the water module on the frequency or channel on which the wake-up message was sent. The radio frequency configuration message may establish a different channel over which the communications adapter 114 and the water module 302 can communicate. The water module 302 may approve the new channel or the water module 302 may propose a different communications channel. This process may continue until a communications channel is agreed upon by the communications adapter 114 and the water module 302.

[0038] Other methods of establishing a communication link between the communication adapter 114 and the water module 302 are also contemplated. For example, the communication adapter 114 may match the frequency hopping pattern of the water module 302 to establish a communication link. If the water module 302 operates with a frequency hopping pattern, the communication adapter 114 may transmit an RF configuration message on a number of different frequency channels to identify the frequency hopping pattern of the water module 302. For example, the water module 302 may return an acknowledgement on the frequency channel on which the water module 302 is currently operating. The communication adapter 114 may know the hopping pattern of the water module 302, and the communication adapter 114 may synchronize to that pattern based on an indication of the current frequency channel of the water module 302. In one example, the hopping pattern may be developed based on the serial number of the module, which is unique across the mesh network 101. The channel or frequency spectrum may be derived from the capabilities of the hardware and firmware based on the country. For example, in the United States, an RF spectrum of 902-928 MHz is used.

[0039] Once a communication channel between the communication adapter 114 and the water module 302 is established, the communication adapter 114 may provide a "get encryption mode" command to the node 108d to initiate an authentication process between the diagnostic tool 110 and the node 108d if an authentication process is desired. In one example, upon receiving an indication that the water module 302 recognized the "get encryption mode" command, the diagnostic tool 110 provides a Mobile Authentication Token (MAT) to the water module 302 via the communication adapter 114. The MAT provides an indication to the water module 302 that the diagnostic tool 110 is authorized to access the electronically restricted data of the water module 302. Turning to FIG. 3B, the water module 302 may respond with an indication that the MAT was accepted and a secure connection was established.

[0040] Other types of workflows may also be used and may be based on the type of communication used by the communication adapter 114 and the water module 302. The types of communication may include, but are not limited to, RF mesh, RF mesh IP, wireless smart utility network (Wi-SUN), and other standards-based communications. In some implementations, the water module 302 wakes up and begins channel hopping. The channel hopping may be different from any channel hopping used for typical network communications (e.g., on the mesh network 101). In this implementation, the communication adapter 114 may send a wake-up message to the water module 302 on multiple channels, and the workflow may include determining one of the channels for communication between the communication adapter 114 and the water module 302.

[0041] Upon establishing a communications link, the diagnostic tool 110 can provide diagnostic commands to the water module 302 via the communications adapter 114. The diagnostic commands include diagnostic requests for radio parameter configurations of the water module 302. Upon receiving a successful response from the water module 302, the diagnostic tool 110 can initiate a radio operation diagnostic process 306, a metering operation diagnostic process 308, or both. The radio operation diagnostic process 306 can include performing diagnostic operations on the radio of the water module 302 to verify that the radio of the water module 302 is functioning properly or to identify issues with how the radio of the water module 302 is operating. In one example, a radio operation diagnostic command is sent to the water module 302 via the communications adapter 114.

[0042] The metering operation diagnostic process 308 may include performing diagnostic operations on the water meter 304 associated with the water module 302 to verify that the water meter 304 is functioning properly or to identify problems with how the water meter 304 is operating. In one example, a metering operation diagnostic command is sent to the water module 302 via the communications adapter 114. The water module then sends a diagnostic message to the water meter 304, receives a response from the water meter 304, and sends a diagnostic response to the diagnostic tool 110 via the communications adapter 114.

[0043] Upon completion of the diagnostic process, the diagnostic tool 110 sends a command to the water module 302 to disconnect the communication link. The water module 302 confirms the disconnection in a response to the diagnostic tool 110 and attempts to reconnect with a parent device (e.g., node 108a) in the mesh network 101. For example, the water module 302 may initiate a join process to create a communication link with the mesh network 101. Upon receiving confirmation from the water module 302, the diagnostic tool 110 may send a message to the communication adapter 114 to disconnect the communication link between the diagnostic tool 110 and the communication adapter 114. The communication adapter 114 then confirms the disconnection in a response to the diagnostic tool 110.

[0044] FIG. 4 is an example block diagram of components of a node 106 or 108 of a mesh network 101. Some or all of the components of a computing system 400 may belong to one or more of the nodes 106 or nodes 108a-108h of FIG. 1. The computing system 400 includes one or more processors 402 communicatively coupled to one or more memory devices 414. The computing system 400 executes program code that configures the processor 402 to perform one or more operations described above with respect to FIGS. 1-3. For example, the memory device 414 may include a metering application 416 (e.g., controlling the water meter 304) and a communication application 418 (e.g., controlling the water module 302). The program code of the metering application 416 and the communication application 418, which may be in the form of non-transitory computer-executable instructions, may reside in the memory device 414 or any suitable computer-readable medium and may be executed by the processor 402. Execution of such program code causes the processor to configure or perform the operations described herein with respect to node 106 and nodes 108a-108h. Although FIG. 4 depicts the metrology application 416 stored within the memory device 414, other applications relating to other operations of node 106 and nodes 108a-108h may replace or be added to the metrology application 416 depending on the functionality of node 106 and nodes 108a-108h. Additionally, the communication application 418 may provide instructions for node 106 and nodes 108a-108h to implement multiple communication standards, including RF mesh or any other wired or wireless communication standard.

[0045] The computing system 400 may also include an input / output ("I / O") interface 408 that can receive input from an input device or provide output to an output device. The interface 408 may include an RF antenna that can send and receive RF communications from other nodes 106 or 108 in the mesh network 101 and from the diagnostic tool 110. The computing system 400 may also be able to communicate with one or more other computing devices or computer readable data sources using the interface 408. Additionally, a bus 406 may be included in the computing system 400. The bus 406 may communicatively couple one or more components of the computing system 400 and enable communication between those components.

[0046] Although the subject matter of the embodiments of the present disclosure has been specifically described herein to meet statutory requirements, this description is not necessarily intended to limit the scope of the subject matter of the present disclosure. The subject matter of the present disclosure may be embodied in other ways, may include different elements or steps, and may be used in combination with other existing or future technologies. This description should not be construed as implying a particular order or arrangement between or among the various steps or elements, unless the order of the particular steps or arrangement of the elements is explicitly described.

[0047] The above content has been provided for purposes of illustrating, explaining, and describing various embodiments. Having described these examples, one skilled in the art will recognize that various modifications, alternative configurations, and equivalents may be used without departing from the spirit of the disclosure. Various arrangements of the components depicted in the figures or described above, as well as additional components and steps not shown or described, are possible. Certain features and subcombinations of certain features disclosed herein are useful and may be employed without reference to other features and subcombinations. Moreover, in order to avoid unnecessarily obscuring the embodiments, many well-known processes and elements have not been described. The embodiments have been described for purposes of illustration and not limitation, and alternative embodiments will become apparent to the reader of this patent. Thus, the embodiments are not limited to those described above or depicted in the figures, and various modifications may be made without departing from the spirit and scope of the disclosure.

Claims

1. 1. A method for establishing a communication link, comprising: transmitting, by a diagnostic tool, a wireless wake signal on a wake radio channel to a low-power endpoint in a measurement mesh network, the wake radio channel being selected using a unique identifier of the low-power endpoint; receiving, at the diagnostic tool, a confirmation message from the low power endpoint indicating that the wireless wake signal was received at the low power endpoint; establishing, by the diagnostic tool, a communications link between the diagnostic tool and the low power endpoint on a wireless communication channel different from the wake wireless channel; and performing, with the diagnostic tool, a diagnostic operation on the low power endpoint; A method comprising:

2. Furthermore, performing an authentication process between the low power endpoint and the diagnostic tool to verify that the diagnostic tool is authorized to interact with the low power endpoint. The method of claim 1 , comprising:

3. transmitting the wireless wake signal includes transmitting the wireless wake signal for a transmission period longer than wake and sleep cycles of the low power endpoint. The method of claim 1.

4. and establishing the communication link between the diagnostic tool and the low power endpoint over the wireless communication channel includes synchronizing a frequency hopping pattern between the low power endpoint and the diagnostic tool. The method of claim 1.

5. the diagnostic operations include wireless diagnostic operations, instrumentation diagnostic operations, or a combination thereof, on the low power endpoint; The method of claim 1.

6. Furthermore, releasing the communication link between the low power endpoint and the diagnostic tool upon completion of the diagnostic operation. The method of claim 1 , comprising:

7. The method of claim 1 , wherein the unique identifier of the low power endpoint comprises a LAN ID (Local Area Network Identification) or a serial number of the low power endpoint.

8. the unique identifier of the low power endpoint comprises a LAN ID (Local Area Network Identification); the wake radio channel for the low power endpoint is determined from a low order byte of the LAN ID; The method of claim 1.

9. The communication link is established using RF (Radio Frequency) Mesh, RF Mesh IP (Internet Protocol), or Wireless Smart Utility Network (Wi-SUN) standards; The method of claim 1.

10. A node of a networked system, A processor configured to execute computer readable instructions; a memory configured to store the computer readable instructions; Including, The computer readable instructions, when executed by the processor, cause the processor to: transitioning to a sleep mode; entering a wake mode to listen for a wake signal from a diagnostic tool; receiving, in the wake mode, the wake signal from the diagnostic tool on a wake radio channel, the wake radio channel being selected using a unique identifier of the node; establishing a communication link with the diagnostic tool on a communication channel different from the wake radio channel; and performing a diagnostic operation with said diagnostic tool over said communication channel; Perform an action including node.

11. The computer readable instructions further include causing the processor to: performing an authentication process with the diagnostic tool to verify that the diagnostic tool is authorized to interact with the node. The node of claim 10 , which causes operations including:

12. performing the authentication process includes receiving a mobile authentication token from the diagnostic tool; The node according to claim 11.

13. the diagnostic operations include wireless diagnostic operations, instrumentation diagnostic operations, or a combination thereof, at the node; The node of claim 10.

14. Furthermore, a radio configured to communicate with the diagnostic tool; a measurement device in communication with the radio; and a battery configured to power the processor, the memory, the radio, and the measurement device; The node of claim 10, comprising:

15. The node of claim 14 , wherein the metering device is configured to meter consumption of electricity, water, or natural gas.

16. A non-transitory computer-readable medium having instructions stored therein, comprising: The instruction: controlling a low power endpoint to enter a sleep mode; controlling the low power endpoint to enter a wake mode to listen for a wake signal from a diagnostic tool; receiving, at a low power endpoint, the wake signal from the diagnostic tool on a wake radio channel, the wake radio channel being determined from a unique identifier of the low power endpoint; controlling the low power endpoint to establish a communication link between the low power endpoint and the diagnostic tool on a communication channel different from the wake radio channel; and controlling the low power endpoint to perform a diagnostic operation with the diagnostic tool over the communication channel; Executable by a processing device to perform operations including: Non-transitory computer-readable medium.

17. The instructions may further include: performing an authentication process with the diagnostic tool to verify that the diagnostic tool is authorized to interact with the low power endpoint. and wherein the processing device is executable to perform operations including:

20. The non-transitory computer-readable medium of claim 16.

18. 20. The non-transitory computer-readable medium of claim 16, wherein the unique identifier of the low power endpoint comprises a LAN ID (local area network identification) or a serial number of the low power endpoint.

19. 20. The non-transitory computer-readable medium of claim 16, wherein a wake mode for listening for the wake signal from the diagnostic tool is different from a communication wake mode of the low power endpoint for communicating in a mesh network.

20. The communication link is established using RF (Radio Frequency) Mesh, RF Mesh IP (Internet Protocol), or Wireless Smart Utility Network (Wi-SUN) standards; 20. The non-transitory computer-readable medium of claim 16.

Images