Patent Application
20110158160
Automated systems exist for collecting data from meters that measure usage of resources, such as gas, water and electricity. Such systems may employ a number of different infrastructures for collecting this meter data from the meters. For example, some automated systems obtain data from the meters using a fixed wireless network that includes, for example, a central node in communication with a number of endpoint sensor nodes (e.g., meter reading devices (MRDs) connected to meters). At the endpoint nodes, the wireless communications circuitry may be incorporated into the meters themselves, such that each endpoint node in the wireless network comprises a meter connected to an MRD that has wireless communication circuitry that enables the MRD to transmit the meter data of the meter to which it is connected.
One type of infrastructure, known in the art as Advanced Metering Infrastructure (AMI), uses two-way communications between collectors and single phase (SP) metering nodes and polyphase (PP) metering nodes to enable collection of metering data, such as kilowatt-hour (kWh), demand, interval, and time-of-use (TOU) data, as well as to enable control actions, such as disconnect, load management, or thermostat control. An AMI system typically consists of meter points connected to a collector via a local area network (LAN). The collector, in turn, is connected to a central head end system via a wide area network (WAN). Because these systems are typically deployed throughout a distribution grid at each point of service, it is desirable that such systems be economical for very large scale deployments. Another type of infrastructure is known in the art as Automatic Meter Reading (AMR). AMR and AMI systems are part of utility planning in the United States and many foreign countries. There are a large number of different communications systems concepts being offered for sale. Most of these concepts use the 900 MHz ISM frequency band and implement frequency hopping spread spectrum techniques. Because most of these systems are developed by communications experts rather than meter/utility systems experts, they can be highly complex and difficult to troubleshoot.
Some networks may employ a mesh networking architecture. In such networks, known as “mesh networks,” endpoint nodes are connected to one another through wireless communication links such that each endpoint node has a wireless communication path to the central node. One characteristic of mesh networks is that the component nodes can all connect to one another via one or more “hops.” Due to this characteristic, mesh networks can continue to operate even if a node or a connection breaks down.
In a mesh network, some endpoint nodes may transmit their meter data directly to the central node. These endpoint nodes are known as “level 1” nodes because a data communication only needs to complete one “hop” to travel from the endpoint node to the central node or vice versa. Other endpoint nodes may transmit their meter data to the central node indirectly through one or more intermediate bidirectional nodes that serve as repeaters for the meter data of the transmitting node. For example, a “level 2” node transmits its meter data to the central node through one bidirectional node, while a “level 5” node transmits its meter data through four bidirectional nodes.
Various non-standard communication protocols have been developed to route and translate data across wireless mesh networks. Although the Internet Protocol (IP) is a network protocol that has been used for standardized data transfer in other contexts, networks of wireless sensor nodes do not support or work well with IP packet routing or translation. IP networks generally use relatively high-speed two-way data transmission that requires support for IP protocol stacks and routing protocols, as well as support for applications that use the capabilities provided by IP protocol stacks and routing protocols. By contrast, wireless mesh networks are generally characterized by lower data rates and, in some cases, smaller packet sizes. Thus, wireless mesh networks have generally not supported IP protocols. Adding support of IP protocols and associated IP addressing to wireless mesh networks using conventional techniques would require the use of sensor nodes that have additional power, processing, and memory than are traditionally implemented. Such upgrades would represent a significant additional cost. In addition, if support for IP protocols and IP addressing were added to a wireless mesh network, IP access to the wireless node sensors would need to be managed effectively despite ever growing risks involved in data networks, such as IP spoofing, denial of service (DOS) attacks, man in the middle attacks, etc.
Accordingly, a need exists for a way to provide IP addressing of a wireless radio mesh network of nodes that have relatively little computational power and that lack inherent support for the IP protocol stack.
Various methods of operating a wireless mesh network are disclosed herein. According to various embodiments, an Internet Protocol (IP) router generates IP addresses for wireless sensor nodes that do not have native support for the IP protocol stack. The IP router then receives and translates an incoming IP request and routes the incoming IP request to the appropriate wireless sensor node. In some embodiments, an IP data packet can be encapsulated and routed using an IP router and an IP bridge device. In other embodiments, an Internet Control Message Protocol (ICMP) session can be managed over a wireless mesh network.
One embodiment is directed to a method for addressing a first node device of a wireless mesh network comprising a plurality of node devices. The first node device lacks Internet Protocol (IP) compatibility and is detected at an Internet Protocol (IP) router. The IP router is used to generate an IP address and to associate the generated IP address with the first node device. An incoming IP request is received at the IP router from an originating device. The IP router is used to translate the incoming IP request. If the incoming IP request is directed to the generated IP address that is associated with the first node device, then the IP router is used to manage a session between the originating device and the first node device.
Another embodiment is directed to a method for transferring an Internet Protocol (IP) data packet from an originating device to a receiving device. The IP data packet, which is associated with a first IP address, is received from the originating device at an Internet Protocol (IP) router. The IP router is used to translate the first IP address associated with the IP data packet to a node device in a wireless mesh network. The node device lacking IP compatibility. The step of using the IP router to translate the IP address to the node device includes using the IP router to generate a plurality of second IP addresses each associated with a respective node device of a plurality of node devices. One of the second IP addresses is associated with the receiving device. The IP router is used to encapsulate the IP data packet into a wireless data gram that is compliant with a wireless network protocol used by the receiving device. The wireless data gram is forwarded to an IP bridge device, which is used to unencapsulate the wireless data gram to the IP data packet. The IP bridge device is then used to forward the unencapsulated IP data packet to the receiving device based on a mapping between the first IP address and the one of the second IP addresses associated with the receiving device.
According to yet another embodiment, an Internet Control Message Protocol (ICMP) data packet, which is associated with a first IP address, is transferred from an originating device to a receiving device by receiving the ICMP data packet from the originating device at an Internet Protocol (IP) router, which is used to translate the first IP address associated with the ICMP data packet to a node device in a wireless mesh network. The node device lacks IP compatibility. Using the IP router to translate the IP address to the node device comprises using the IP router to generate a plurality of second IP addresses each associated with a respective node device of a plurality of node devices. One of the second IP addresses is associated with the receiving device. The IP router is used to translate the ICMP data packet to a network command that is compatible with a wireless network protocol used by the receiving device. The network command is forwarded to and is received by an IP bridge device, which is used to forward the network command to the receiving device based on a mapping between the first IP address and the one of the second IP addresses associated with the receiving device. If the receiving device generates a reply in response to the network command, the reply is received at the IP router, which generates a first ICMP response data packet and forwards the first ICMP response data packet to the originating device.
Various embodiments may realize certain advantages. For example, using an IP router or gateway device to define the mesh network IP assigned addressing for each wireless mesh network device allows IP-based systems outside the wireless mesh network to route IP addressed messages to the wireless mesh network using the IP router or gateway device that manages the IP sessions for that network. The routing of IP addressed messages can be achieved without modifying the hardware of existing wireless sensor nodes; accordingly, costs associated with implementing the embodiments described herein may be relatively manageable. Further, the lack of support of IP addressing by the wireless mesh network devices themselves reduces the risk of IP security risks (e.g., denial of service attacks) at each wireless mesh network device. Access to the wireless mesh network is controlled through the IP router or gateway device, providing a firewall for the private wireless mesh network.
Other features and advantages of the described embodiments may become apparent from the following detailed description and accompanying drawings.
The foregoing summary, as well as the following detailed description of various embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there are shown in the drawings exemplary embodiments of various aspects of the invention; however, the invention is not limited to the specific methods and instrumentalities disclosed. In the drawings:
Exemplary systems and methods for gathering meter data are described below with reference to
Generally, a plurality of meter devices, which operate to track usage of a service or commodity such as, for example, electricity, water, and gas, are operable to wirelessly communicate. One or more devices, referred to herein as “collectors,” are provided that “collect” data transmitted by the other meter devices so that it can be accessed by other computer systems. The collectors receive and compile metering data from a plurality of meter devices via wireless communications. A data collection server may communicate with the collectors to retrieve the compiled meter data.
System 110 further comprises collectors 116. In one embodiment, collectors 116 are also meters operable to detect and record usage of a service or commodity such as, for example, electricity, water, or gas. In addition, collectors 116 are operable to send data to and receive data from meters 114. Thus, like the meters 114, the collectors 116 may comprise both circuitry for measuring the consumption of a service or commodity and for generating data reflecting the consumption and circuitry for transmitting and receiving data. In one embodiment, collector 116 and meters 114 communicate with and amongst one another using any one of several wireless techniques such as, for example, frequency hopping spread spectrum (FHSS) and direct sequence spread spectrum (DSSS).
A collector 116 and the meters 114 with which it communicates define a subnet/LAN 120 of system 110. As used herein, meters 114 and collectors 116 may be referred to as “nodes” in the subnet 120. In each subnet/LAN 120, each meter transmits data related to consumption of the commodity being metered at the meter's location. The collector 116 receives the data transmitted by each meter 114, effectively “collecting” it, and then periodically transmits the data from all of the meters in the subnet/LAN 120 to a data collection server 206. The data collection server 206 stores the data for analysis and preparation of bills, for example. The data collection server 206 may be a specially programmed general purpose computing system and may communicate with collectors 116 via a network 112. The network 112 may comprise any form of network, including a wireless network or a fixed-wire network, such as a local area network (LAN), a wide area network, the Internet, an intranet, a telephone network, such as the public switched telephone network (PSTN), a Frequency Hopping Spread Spectrum (FHSS) radio network, a mesh network, a Wi-Fi (802.11) network, a Wi-Max (802.16) network, a land line (POTS) network, or any combination of the above.
Referring now to
Each of the meters 114 and collectors 116 is assigned an identifier (LAN ID) that uniquely identifies that meter or collector on its subnet/LAN 120. In this embodiment, communication between nodes (i.e., the collectors and meters) and the system 110 is accomplished using the LAN ID. However, it is preferable for operators of a utility to query and communicate with the nodes using their own identifiers. To this end, a marriage file 208 may be used to correlate a utility's identifier for a node (e.g., a utility serial number) with both a manufacturer serial number (i.e., a serial number assigned by the manufacturer of the meter) and the LAN ID for each node in the subnet/LAN 120. In this manner, the utility can refer to the meters and collectors by the utilities identifier, while the system can employ the LAN ID for the purpose of designating particular meters during system communications.
A device configuration database 210 stores configuration information regarding the nodes. For example, in the metering system 200, the device configuration database may include data regarding time of use (TOU) switchpoints, etc. for the meters 114 and collectors 116 communicating in the system 110. A data collection requirements database 212 contains information regarding the data to be collected on a per node basis. For example, a utility may specify that metering data such as load profile, demand, TOU, etc. is to be collected from particular meter(s) 114a. Reports 214 containing information on the network configuration may be automatically generated or in accordance with a utility request.
The network management system (NMS) 204 maintains a database describing the current state of the global fixed network system (current network state 220) and a database describing the historical state of the system (historical network state 222). The current network state 220 contains data regarding current meter-to-collector assignments, etc. for each subnet/LAN 120. The historical network state 222 is a database from which the state of the network at a particular point in the past can be reconstructed. The NMS 204 is responsible for, amongst other things, providing reports 214 about the state of the network. The NMS 204 may be accessed via an API 220 that is exposed to a user interface 216 and a Customer Information System (CIS) 218. Other external interfaces may also be implemented. In addition, the data collection requirements stored in the database 212 may be set via the user interface 216 or CIS 218.
The data collection server 206 collects data from the nodes (e.g., collectors 116) and stores the data in a database 224. The data includes metering information, such as energy consumption and may be used for billing purposes, etc. by a utility provider.
The network management server 202, network management system 204 and data collection server 206 communicate with the nodes in each subnet/LAN 120 via network 110.
As shown in
In one embodiment, the metering circuitry 304, processor 305, display 310 and memory 312 are implemented using an A3 ALPHA meter available from Elster Electricity, Inc. In that embodiment, the wireless LAN communications circuitry 306 may be implemented by a LAN Option Board (e.g., a 900 MHz two-way radio) installed within the A3 ALPHA meter, and the network interface 308 may be implemented by a WAN Option Board (e.g., a telephone modem) also installed within the A3 ALPHA meter. In this embodiment, the WAN Option Board 308 routes messages from network 112 (via interface port 302) to either the meter processor 305 or the LAN Option Board 306. LAN Option Board 306 may use a transceiver (not shown), for example a 900 MHz radio, to communicate data to meters 114. Also, LAN Option Board 306 may have sufficient memory to store data received from meters 114. This data may include, but is not limited to the following: current billing data (e.g., the present values stored and displayed by meters 114), previous billing period data, previous season data, and load profile data.
LAN Option Board 306 may be capable of synchronizing its time to a real time clock (not shown) in A3 ALPHA meter, thereby synchronizing the LAN reference time to the time in the meter. The processing necessary to carry out the communication functionality and the collection and storage of metering data of the collector 116 may be handled by the processor 305 and/or additional processors (not shown) in the LAN Option Board 306 and the WAN Option Board 308.
The responsibility of a collector 116 is wide and varied. Generally, collector 116 is responsible for managing, processing and routing data communicated between the collector and network 112 and between the collector and meters 114. Collector 116 may continually or intermittently read the current data from meters 114 and store the data in a database (not shown) in collector 116. Such current data may include but is not limited to the total kWh usage, the Time-Of-Use (TOU) kWh usage, peak kW demand, and other energy consumption measurements and status information. Collector 116 also may read and store previous billing and previous season data from meters 114 and store the data in the database in collector 116. The database may be implemented as one or more tables of data within the collector 116.
Referring again to
Each level one meter 114a typically will only be in range to directly communicate with only a subset of the remaining meters 114 in the subnet 120. The meters 114 with which the level one meters 114a directly communicate may be referred to as level two meters 114b. Level two meters 114b are one “hop” from level one meters 114a, and therefore two “hops” from collector 116. Level two meters 114b operate as repeaters for communications between the level one meters 114a and meters 114 located further away from collector 116 in the subnet 120.
While only three levels of meters are shown (collector 116, first level 114a, second level 114b) in
As mentioned above, each meter 114 and collector 116 that is installed in the system 110 has a unique identifier (LAN ID) stored thereon that uniquely identifies the device from all other devices in the system 110. Additionally, meters 114 operating in a subnet 120 comprise information including the following: data identifying the collector with which the meter is registered; the level in the subnet at which the meter is located; the repeater meter at the prior level with which the meter communicates to send and receive data to/from the collector; an identifier indicating whether the meter is a repeater for other nodes in the subnet; and if the meter operates as a repeater, the identifier that uniquely identifies the repeater within the particular subnet, and the number of meters for which it is a repeater. Collectors 116 have stored thereon all of this same data for all meters 114 that are registered therewith. Thus, collector 116 comprises data identifying all nodes registered therewith as well as data identifying the registered path by which data is communicated from the collector to each node. Each meter 114 therefore has a designated communications path to the collector that is either a direct path (e.g., all level one nodes) or an indirect path through one or more intermediate nodes that serve as repeaters.
Information is transmitted in this embodiment in the form of packets. For most network tasks such as, for example, reading meter data, collector 116 communicates with meters 114 in the subnet 120 using point-to-point transmissions. For example, a message or instruction from collector 116 is routed through the designated set of repeaters to the desired meter 114. Similarly, a meter 114 communicates with collector 116 through the same set of repeaters, but in reverse.
In some instances, however, collector 116 may need to quickly communicate information to all meters 114 located in its subnet 120. Accordingly, collector 116 may issue a broadcast message that is meant to reach all nodes in the subnet 120. The broadcast message may be referred to as a “flood broadcast message.” A flood broadcast originates at collector 116 and propagates through the entire subnet 120 one level at a time. For example, collector 116 may transmit a flood broadcast to all first level meters 114a. The first level meters 114a that receive the message pick a random time slot and retransmit the broadcast message to second level meters 114b. Any second level meter 114b can accept the broadcast, thereby providing better coverage from the collector out to the end point meters. Similarly, the second level meters 114b that receive the broadcast message pick a random time slot and communicate the broadcast message to third level meters. This process continues out until the end nodes of the subnet. Thus, a broadcast message gradually propagates outward from the collector to the nodes of the subnet 120.
The flood broadcast packet header contains information to prevent nodes from repeating the flood broadcast packet more than once per level. For example, within a flood broadcast message, a field might exist that indicates to meters/nodes which receive the message, the level of the subnet the message is located; only nodes at that particular level may re-broadcast the message to the next level. If the collector broadcasts a flood message with a level of 1, only level 1 nodes may respond. Prior to re-broadcasting the flood message, the level 1 nodes increment the field to 2 so that only level 2 nodes respond to the broadcast. Information within the flood broadcast packet header ensures that a flood broadcast will eventually die out.
Generally, a collector 116 issues a flood broadcast several times, e.g. five times, successively to increase the probability that all meters in the subnet 120 receive the broadcast. A delay is introduced before each new broadcast to allow the previous broadcast packet time to propagate through all levels of the subnet.
Meters 114 may have a clock formed therein. However, meters 114 often undergo power interruptions that can interfere with the operation of any clock therein. Accordingly, the clocks internal to meters 114 cannot be relied upon to provide an accurate time reading. Having the correct time is necessary, however, when time of use metering is being employed. Indeed, in an embodiment, time of use schedule data may also be comprised in the same broadcast message as the time. Accordingly, collector 116 periodically flood broadcasts the real time to meters 114 in subnet 120. Meters 114 use the time broadcasts to stay synchronized with the rest of the subnet 120. In an illustrative embodiment, collector 116 broadcasts the time every 15 minutes. The broadcasts may be made near the middle of 15 minute clock boundaries that are used in performing load profiling and time of use (TOU) schedules so as to minimize time changes near these boundaries. Maintaining time synchronization is important to the proper operation of the subnet 120. Accordingly, lower priority tasks performed by collector 116 may be delayed while the time broadcasts are performed.
In an illustrative embodiment, the flood broadcasts transmitting time data may be repeated, for example, five times, so as to increase the probability that all nodes receive the time. Furthermore, where time of use schedule data is communicated in the same transmission as the timing data, the subsequent time transmissions allow a different piece of the time of use schedule to be transmitted to the nodes.
Exception messages are used in subnet 120 to transmit unexpected events that occur at meters 114 to collector 116. In an embodiment, the first 4 seconds of every 32-second period are allocated as an exception window for meters 114 to transmit exception messages. Meters 114 transmit their exception messages early enough in the exception window so the message has time to propagate to collector 116 before the end of the exception window. Collector 116 may process the exceptions after the 4-second exception window. Generally, a collector 116 acknowledges exception messages, and collector 116 waits until the end of the exception window to send this acknowledgement.
In an illustrative embodiment, exception messages are configured as one of three different types of exception messages: local exceptions, which are handled directly by the collector 116 without intervention from data collection server 206; an immediate exception, which is generally relayed to data collection server 206 under an expedited schedule; and a daily exception, which is communicated to the communication server 122 on a regular schedule.
Exceptions are processed as follows. When an exception is received at collector 116, the collector 116 identifies the type of exception that has been received. If a local exception has been received, collector 116 takes an action to remedy the problem. For example, when collector 116 receives an exception requesting a “node scan request” such as discussed below, collector 116 transmits a command to initiate a scan procedure to the meter 114 from which the exception was received.
If an immediate exception type has been received, collector 116 makes a record of the exception. An immediate exception might identify, for example, that there has been a power outage. Collector 116 may log the receipt of the exception in one or more tables or files. In an illustrative example, a record of receipt of an immediate exception is made in a table referred to as the “Immediate Exception Log Table.” Collector 116 then waits a set period of time before taking further action with respect to the immediate exception. For example, collector 116 may wait 64 seconds. This delay period allows the exception to be corrected before communicating the exception to the data collection server 206. For example, where a power outage was the cause of the immediate exception, collector 116 may wait a set period of time to allow for receipt of a message indicating the power outage has been corrected.
If the exception has not been corrected, collector 116 communicates the immediate exception to data collection server 206. For example, collector 116 may initiate a dial-up connection with data collection server 206 and download the exception data. After reporting an immediate exception to data collection server 206, collector 116 may delay reporting any additional immediate exceptions for a period of time such as ten minutes. This is to avoid reporting exceptions from other meters 114 that relate to, or have the same cause as, the exception that was just reported.
If a daily exception was received, the exception is recorded in a file or a database table. Generally, daily exceptions are occurrences in the subnet 120 that need to be reported to data collection server 206, but are not so urgent that they need to be communicated immediately. For example, when collector 116 registers a new meter 114 in subnet 120, collector 116 records a daily exception identifying that the registration has taken place. In an illustrative embodiment, the exception is recorded in a database table referred to as the “Daily Exception Log Table.” Collector 116 communicates the daily exceptions to data collection server 206. Generally, collector 116 communicates the daily exceptions once every 24 hours.
In the present embodiment, a collector assigns designated communications paths to meters with bi-directional communication capability, and may change the communication paths for previously registered meters if conditions warrant. For example, when a collector 116 is initially brought into system 110, it needs to identify and register meters in its subnet 120. A “node scan” refers to a process of communication between a collector 116 and meters 114 whereby the collector may identify and register new nodes in a subnet 120 and allow previously registered nodes to switch paths. A collector 116 can implement a node scan on the entire subnet, referred to as a “full node scan,” or a node scan can be performed on specially identified nodes, referred to as a “node scan retry.”
A full node scan may be performed, for example, when a collector is first installed. The collector 116 must identify and register nodes from which it will collect usage data. The collector 116 initiates a node scan by broadcasting a request, which may be referred to as a Node Scan Procedure request. Generally, the Node Scan Procedure request directs that all unregistered meters 114 or nodes that receive the request respond to the collector 116. The request may comprise information such as the unique address of the collector that initiated the procedure. The signal by which collector 116 transmits this request may have limited strength and therefore is detected only at meters 114 that are in proximity of collector 116. Meters 114 that receive the Node Scan Procedure request respond by transmitting their unique identifier as well as other data.
For each meter from which the collector receives a response to the Node Scan Procedure request, the collector tries to qualify the communications path to that meter before registering the meter with the collector. That is, before registering a meter, the collector 116 attempts to determine whether data communications with the meter will be sufficiently reliable. In one embodiment, the collector 116 determines whether the communication path to a responding meter is sufficiently reliable by comparing a Received Signal Strength Indication (RSSI) value (i.e., a measurement of the received radio signal strength) measured with respect to the received response from the meter to a selected threshold value. For example, the threshold value may be −60 dBm. RSSI values above this threshold would be deemed sufficiently reliable. In another embodiment, qualification is performed by transmitting a predetermined number of additional packets to the meter, such as ten packets, and counting the number of acknowledgements received back from the meter. If the number of acknowledgments received is greater than or equal to a selected threshold (e.g., 8 out of 10), then the path is considered to be reliable. In other embodiments, a combination of the two qualification techniques may be employed.
If the qualification threshold is not met, the collector 116 may add an entry for the meter to a “Straggler Table.” The entry includes the meter's LAN ID, its qualification score (e.g., 5 out of 10; or its RSSI value), its level (in this case level one) and the unique ID of its parent (in this case the collector's ID).
If the qualification threshold is met or exceeded, the collector 116 registers the node. Registering a meter 114 comprises updating a list of the registered nodes at collector 116. For example, the list may be updated to identify the meter's system-wide unique identifier and the communication path to the node. Collector 116 also records the meter's level in the subnet (i.e. whether the meter is a level one node, level two node, etc.), whether the node operates as a repeater, and if so, the number of meters for which it operates as a repeater. The registration process further comprises transmitting registration information to the meter 114. For example, collector 116 forwards to meter 114 an indication that it is registered, the unique identifier of the collector with which it is registered, the level the meter exists at in the subnet, and the unique identifier of its parent meter that will server as a repeater for messages the meter may send to the collector. In the case of a level one node, the parent is the collector itself. The meter stores this data and begins to operate as part of the subnet by responding to commands from its collector 116.
Qualification and registration continues for each meter that responds to the collector's initial Node Scan Procedure request. The collector 116 may rebroadcast the Node Scan Procedure additional times so as to insure that all meters 114 that may receive the Node Scan Procedure have an opportunity for their response to be received and the meter qualified as a level one node at collector 116.
The node scan process then continues by performing a similar process as that described above at each of the now registered level one nodes. This process results in the identification and registration of level two nodes. After the level two nodes are identified, a similar node scan process is performed at the level two nodes to identify level three nodes, and so on.
Specifically, to identify and register meters that will become level two meters, for each level one meter, in succession, the collector 116 transmits a command to the level one meter, which may be referred to as an “Initiate Node Scan Procedure” command. This command instructs the level one meter to perform its own node scan process. The request comprises several data items that the receiving meter may use in completing the node scan. For example, the request may comprise the number of timeslots available for responding nodes, the unique address of the collector that initiated the request, and a measure of the reliability of the communications between the target node and the collector. As described below, the measure of reliability may be employed during a process for identifying more reliable paths for previously registered nodes.
The meter that receives the Initiate Node Scan Response request responds by performing a node scan process similar to that described above. More specifically, the meter broadcasts a request to which all unregistered nodes may respond. The request comprises the number of timeslots available for responding nodes (which is used to set the period for the node to wait for responses), the unique address of the collector that initiated the node scan procedure, a measure of the reliability of the communications between the sending node and the collector (which may be used in the process of determining whether a meter's path may be switched as described below), the level within the subnet of the node sending the request, and an RSSI threshold (which may also be used in the process of determining whether a registered meter's path may be switched). The meter issuing the node scan request then waits for and receives responses from unregistered nodes. For each response, the meter stores in memory the unique identifier of the responding meter. This information is then transmitted to the collector.
For each unregistered meter that responded to the node scan issued by the level one meter, the collector attempts again to determine the reliability of the communication path to that meter. In one embodiment, the collector sends a “Qualify Nodes Procedure” command to the level one node which instructs the level one node to transmit a predetermined number of additional packets to the potential level two node and to record the number of acknowledgements received back from the potential level two node. This qualification score (e.g., 8 out of 10) is then transmitted back to the collector, which again compares the score to a qualification threshold. In other embodiments, other measures of the communications reliability may be provided, such as an RSSI value.
If the qualification threshold is not met, then the collector adds an entry for the node in the Straggler Table, as discussed above. However, if there already is an entry in the Straggler Table for the node, the collector will update that entry only if the qualification score for this node scan procedure is better than the recorded qualification score from the prior node scan that resulted in an entry for the node.
If the qualification threshold is met or exceeded, the collector 116 registers the node. Again, registering a meter 114 at level two comprises updating a list of the registered nodes at collector 116. For example, the list may be updated to identify the meter's unique identifier and the level of the meter in the subnet. Additionally, the collector's 116 registration information is updated to reflect that the meter 114 from which the scan process was initiated is identified as a repeater (or parent) for the newly registered node. The registration process further comprises transmitting information to the newly registered meter as well as the meter that will serve as a repeater for the newly added node. For example, the node that issued the node scan response request is updated to identify that it operates as a repeater and, if it was previously registered as a repeater, increments a data item identifying the number of nodes for which it serves as a repeater. Thereafter, collector 116 forwards to the newly registered meter an indication that it is registered, an identification of the collector 116 with which it is registered, the level the meter exists at in the subnet, and the unique identifier of the node that will serve as its parent, or repeater, when it communicates with the collector 116.
The collector then performs the same qualification procedure for each other potential level two node that responded to the level one node's node scan request. Once that process is completed for the first level one node, the collector initiates the same procedure at each other level one node until the process of qualifying and registering level two nodes has been completed at each level one node. Once the node scan procedure has been performed by each level one node, resulting in a number of level two nodes being registered with the collector, the collector will then send the Initiate Node Scan Response command to each level two node, in turn. Each level two node will then perform the same node scan procedure as performed by the level one nodes, potentially resulting in the registration of a number of level three nodes. The process is then performed at each successive node, until a maximum number of levels is reached (e.g., seven levels) or no unregistered nodes are left in the subnet.
It will be appreciated that in the present embodiment, during the qualification process for a given node at a given level, the collector qualifies the last “hop” only. For example, if an unregistered node responds to a node scan request from a level four node, and therefore, becomes a potential level five node, the qualification score for that node is based on the reliability of communications between the level four node and the potential level five node (i.e., packets transmitted by the level four node versus acknowledgments received from the potential level five node), not based on any measure of the reliability of the communications over the full path from the collector to the potential level five node. In other embodiments, of course, the qualification score could be based on the full communication path.
At some point, each meter will have an established communication path to the collector which will be either a direct path (i.e., level one nodes) or an indirect path through one or more intermediate nodes that serve as repeaters. If during operation of the network, a meter registered in this manner fails to perform adequately, it may be assigned a different path or possibly to a different collector as described below.
As previously mentioned, a full node scan may be performed when a collector 116 is first introduced to a network. At the conclusion of the full node scan, a collector 116 will have registered a set of meters 114 with which it communicates and reads metering data. Full node scans might be periodically performed by an installed collector to identify new meters 114 that have been brought on-line since the last node scan and to allow registered meters to switch to a different path.
In addition to the full node scan, collector 116 may also perform a process of scanning specific meters 114 in the subnet 120, which is referred to as a “node scan retry.” For example, collector 116 may issue a specific request to a meter 114 to perform a node scan outside of a full node scan when on a previous attempt to scan the node, the collector 116 was unable to confirm that the particular meter 114 received the node scan request. Also, a collector 116 may request a node scan retry of a meter 114 when during the course of a full node scan the collector 116 was unable to read the node scan data from the meter 114. Similarly, a node scan retry will be performed when an exception procedure requesting an immediate node scan is received from a meter 114.
The system 110 also automatically reconfigures to accommodate a new meter 114 that may be added. More particularly, the system identifies that the new meter has begun operating and identifies a path to a collector 116 that will become responsible for collecting the metering data. Specifically, the new meter will broadcast an indication that it is unregistered. In one embodiment, this broadcast might be, for example, embedded in, or relayed as part of a request for an update of the real time as described above. The broadcast will be received at one of the registered meters 114 in proximity to the meter that is attempting to register. The registered meter 114 forwards the time to the meter that is attempting to register. The registered node also transmits an exception request to its collector 116 requesting that the collector 116 implement a node scan, which presumably will locate and register the new meter. The collector 116 then transmits a request that the registered node perform a node scan. The registered node will perform the node scan, during which it requests that all unregistered nodes respond. Presumably, the newly added, unregistered meter will respond to the node scan. When it does, the collector will then attempt to qualify and then register the new node in the same manner as described above.
Once a communication path between the collector and a meter is established, the meter can begin transmitting its meter data to the collector and the collector can transmit data and instructions to the meter. As mentioned above, data is transmitted in packets. “Outbound” packets are packets transmitted from the collector to a meter at a given level. In one embodiment, outbound packets contain the following fields, but other fields may also be included:
Length—the length of the packet;
SrcAddr—source address—in this case, the ID of the collector;
DestAddr—the LAN ID of the meter to which the packet addressed;
“Inbound” packets are packets transmitted from a meter at a given level to the collector. In one embodiment, inbound packets contain the following fields, but other fields may also be included:
Length—the length of the packet;
SrcAddr—source address—the address of the meter that initiated the packet;
DestAddr—the ID of the collector to which the packet is to be transmitted;
For example, suppose a meter at level three initiates transmission of a packet destined for its collector. The level three node will insert in the RptAddr field of the inbound packet the identifier of the level two node that serves as a repeater for the level three node. The level three node will then transmit the packet. Several level two nodes may receive the packet, but only the level two node having an identifier that matches the identifier in the RptAddr field of the packet will acknowledge it. The other will discard it. When the level two node with the matching identifier receives the packet, it will replace the RptAddr field of the packet with the identifier of the level one packet that serves as a repeater for that level two packet, and the level two packet will then transmit the packet. This time, the level one node having the identifier that matches the RptAddr field will receive the packet. The level one node will insert the identifier of the collector in the RptAddr field and will transmit the packet. The collector will then receive the packet to complete the transmission.
A collector 116 periodically retrieves meter data from the meters that are registered with it. For example, meter data may be retrieved from a meter every 4 hours. Where there is a problem with reading the meter data on the regularly scheduled interval, the collector will try to read the data again before the next regularly scheduled interval. Nevertheless, there may be instances wherein the collector 116 is unable to read metering data from a particular meter 114 for a prolonged period of time. The meters 114 store an indication of when they are read by their collector 116 and keep track of the time since their data has last been collected by the collector 116. If the length of time since the last reading exceeds a defined threshold, such as for example, 18 hours, presumably a problem has arisen in the communication path between the particular meter 114 and the collector 116. Accordingly, the meter 114 changes its status to that of an unregistered meter and attempts to locate a new path to a collector 116 via the process described above for a new node. Thus, the exemplary system is operable to reconfigure itself to address inadequacies in the system.
In some instances, while a collector 116 may be able to retrieve data from a registered meter 114 occasionally, the level of success in reading the meter may be inadequate. For example, if a collector 116 attempts to read meter data from a meter 114 every 4 hours but is able to read the data, for example, only 70 percent of the time or less, it may be desirable to find a more reliable path for reading the data from that particular meter. Where the frequency of reading data from a meter 114 falls below a desired success level, the collector 116 transmits a message to the meter 114 to respond to node scans going forward. The meter 114 remains registered but will respond to node scans in the same manner as an unregistered node as described above. In other embodiments, all registered meters may be permitted to respond to node scans, but a meter will only respond to a node scan if the path to the collector through the meter that issued the node scan is shorter (i.e., less hops) than the meter's current path to the collector. A lesser number of hops is assumed to provide a more reliable communication path than a longer path. A node scan request always identifies the level of the node that transmits the request, and using that information, an already registered node that is permitted to respond to node scans can determine if a potential new path to the collector through the node that issued the node scan is shorter than the node's current path to the collector.
If an already registered meter 114 responds to a node scan procedure, the collector 116 recognizes the response as originating from a registered meter but that by re-registering the meter with the node that issued the node scan, the collector may be able to switch the meter to a new, more reliable path. The collector 116 may verify that the RSSI value of the node scan response exceeds an established threshold. If it does not, the potential new path will be rejected. However, if the RSSI threshold is met, the collector 116 will request that the node that issued the node scan perform the qualification process described above (i.e., send a predetermined number of packets to the node and count the number of acknowledgements received). If the resulting qualification score satisfies a threshold, then the collector will register the node with the new path. The registration process comprises updating the collector 116 and meter 114 with data identifying the new repeater (i.e. the node that issued the node scan) with which the updated node will now communicate. Additionally, if the repeater has not previously performed the operation of a repeater, the repeater would need to be updated to identify that it is a repeater. Likewise, the repeater with which the meter previously communicated is updated to identify that it is no longer a repeater for the particular meter 114. In other embodiments, the threshold determination with respect to the RSSI value may be omitted. In such embodiments, only the qualification of the last “hop” (i.e., sending a predetermined number of packets to the node and counting the number of acknowledgements received) will be performed to determine whether to accept or reject the new path.
In some instances, a more reliable communication path for a meter may exist through a collector other than that with which the meter is registered. A meter may automatically recognize the existence of the more reliable communication path, switch collectors, and notify the previous collector that the change has taken place. The process of switching the registration of a meter from a first collector to a second collector begins when a registered meter 114 receives a node scan request from a collector 116 other than the one with which the meter is presently registered. Typically, a registered meter 114 does not respond to node scan requests. However, if the request is likely to result in a more reliable transmission path, even a registered meter may respond. Accordingly, the meter determines if the new collector offers a potentially more reliable transmission path. For example, the meter 114 may determine if the path to the potential new collector 116 comprises fewer hops than the path to the collector with which the meter is registered. If not, the path may not be more reliable and the meter 114 will not respond to the node scan. The meter 114 might also determine if the RSSI of the node scan packet exceeds an RSSI threshold identified in the node scan information. If so, the new collector may offer a more reliable transmission path for meter data. If not, the transmission path may not be acceptable and the meter may not respond. Additionally, if the reliability of communication between the potential new collector and the repeater that would service the meter meets a threshold established when the repeater was registered with its existing collector, the communication path to the new collector may be more reliable. If the reliability does not exceed this threshold, however, the meter 114 does not respond to the node scan.
If it is determined that the path to the new collector may be better than the path to its existing collector, the meter 114 responds to the node scan. Included in the response is information regarding any nodes for which the particular meter may operate as a repeater. For example, the response might identify the number of nodes for which the meter serves as a repeater.
The collector 116 then determines if it has the capacity to service the meter and any meters for which it operates as a repeater. If not, the collector 116 does not respond to the meter that is attempting to change collectors. If, however, the collector 116 determines that it has capacity to service the meter 114, the collector 116 stores registration information about the meter 114. The collector 116 then transmits a registration command to meter 114. The meter 114 updates its registration data to identify that it is now registered with the new collector. The collector 116 then communicates instructions to the meter 114 to initiate a node scan request. Nodes that are unregistered, or that had previously used meter 114 as a repeater respond to the request to identify themselves to collector 116. The collector registers these nodes as is described above in connection with registering new meters/nodes.
Under some circumstances it may be necessary to change a collector. For example, a collector may be malfunctioning and need to be taken off-line. Accordingly, a new communication path must be provided for collecting meter data from the meters serviced by the particular collector. The process of replacing a collector is performed by broadcasting a message to unregister, usually from a replacement collector, to all of the meters that are registered with the collector that is being removed from service. In one embodiment, registered meters may be programmed to only respond to commands from the collector with which they are registered. Accordingly, the command to unregister may comprise the unique identifier of the collector that is being replaced. In response to the command to unregister, the meters begin to operate as unregistered meters and respond to node scan requests. To allow the unregistered command to propagate through the subnet, when a node receives the command it will not unregister immediately, but rather remain registered for a defined period, which may be referred to as the “Time to Live”. During this time to live period, the nodes continue to respond to application layer and immediate retries allowing the unregistration command to propagate to all nodes in the subnet. Ultimately, the meters register with the replacement collector using the procedure described above.
One of collector's 116 main responsibilities within subnet 120 is to retrieve metering data from meters 114. In one embodiment, collector 116 has as a goal to obtain at least one successful read of the metering data per day from each node in its subnet. Collector 116 attempts to retrieve the data from all nodes in its subnet 120 at a configurable periodicity. For example, collector 116 may be configured to attempt to retrieve metering data from meters 114 in its subnet 120 once every 4 hours. In greater detail, in one embodiment, the data collection process begins with the collector 116 identifying one of the meters 114 in its subnet 120. For example, collector 116 may review a list of registered nodes and identify one for reading. The collector 116 then communicates a command to the particular meter 114 that it forward its metering data to the collector 116. If the meter reading is successful and the data is received at collector 116, the collector 116 determines if there are other meters that have not been read during the present reading session. If so, processing continues. However, if all of the meters 114 in subnet 120 have been read, the collector waits a defined length of time, such as, for example, 4 hours, before attempting another read.
If during a read of a particular meter, the meter data is not received at collector 116, the collector 116 begins a retry procedure wherein it attempts to retry the data read from the particular meter. Collector 116 continues to attempt to read the data from the node until either the data is read or the next subnet reading takes place. In an embodiment, collector 116 attempts to read the data every 60 minutes. Thus, wherein a subnet reading is taken every 4 hours, collector 116 may issue three retries between subnet readings.
Meters 114 are often two-way meters—i.e. they are operable to both receive and transmit data. However, one-way meters that are operable only to transmit and not receive data may also be deployed.
While the collection of data from one-way meters by the collector has been described above in the context of a network of two-way meters 114 that operate in the manner described in connection with the embodiments described above, it is understood that the present invention is not limited to the particular form of network established and utilized by the meters 114 to transmit data to the collector. Rather, the present invention may be used in the context of any network topology in which a plurality of two-way communication nodes are capable of transmitting data and of having that data propagated through the network of nodes to the collector.
According to various embodiments, an Internet Protocol (IP) router generates IP addresses for wireless sensor nodes that do not have native support for the IP protocol stack. The IP router then receives and translates an incoming IP request and routes the incoming IP request to the appropriate wireless sensor node. In some embodiments, an IP data packet can be encapsulated and routed using an IP router and an IP bridge device. In other embodiments, an Internet Control Message Protocol (ICMP) session can be managed over a wireless mesh network.
The embodiments disclosed herein may realize certain advantages. For example, using an IP router or gateway device to define the mesh network IP assigned addressing for each wireless mesh network device allows IP-based systems outside the wireless mesh network to route IP addressed messages to the wireless mesh network using the IP router or gateway device that manages the IP sessions for that network. The routing of IP addressed messages can be achieved without modifying the hardware of existing wireless sensor nodes; accordingly, costs associated with implementing the embodiments described herein may be relatively manageable. Further, the lack of support of IP addressing by the wireless mesh network devices themselves reduces the risk of IP security risks (e.g., denial of service attacks) at each wireless mesh network device. Access to the wireless mesh network is controlled through the IP router or gateway device, providing a firewall for the private wireless mesh network.
The IP router 502 provides an access point into the private wireless mesh network that includes wireless sensor nodes 508, 510, and 512, and has a priori knowledge of wireless mesh routing tables or translations that map IP addresses, either in an IPv4 address space or an IPv6 address space, to the wireless sensor nodes 508, 510, and 512. Given inputs of a wireless routing identifier and a routing path, the IP router 502 can dynamically generate a private IP address from these parameters. This Dynamic Host Configuration Protocol (DHCP) generation function in the IP router 502 can alternatively provide updates to an existing Domain Name Server (DNS) on the IP network 504 to allow remote queries or lookups for applications or users to obtain the assigned IP addresses for the private wireless mesh network. In some embodiments, the IP router 502 can alternatively provide the ability to generate static IP addresses in either an IPv4 address space or an IPv6 address space derived from the individual wireless device identifier to obviate both the need to manage dynamic IP addresses and the need to update a DNS. Advantageously, such embodiments may exhibit reduced complexity.
After the IP router 502 associates the IP address with the node device at step 606, the IP router 502 may optionally update a DNS server with the IP address at a step 608. At a step 610, the IP router 502 receives an incoming IP request, such as an echo request, from an originating device. The IP router 502 then translates the IP request to the wireless mesh device that is associated with the IP request at a step 612. In particular, if it is decided at a step 614 that the IP request is directed to the generated IP address that is associated with, for example, the wireless sensor node 508, then the IP router 502 manages a session between the originating device and the wireless sensor node 508 at a step 616.
The method 600 may provide a number of benefits. Because the IP router 502 generates the IP address for each non-IP compatible wireless device, the IP router 502 can provide an access point to the IP network 504 to translate incoming IP addressed requests to wireless devices on the private wireless mesh network. Accordingly, the IP router 502 can update an existing DNS on the IP network 504 with generated dynamic IP addresses or provide a list of generated static IP addresses. For devices that are connected to the edge of the wireless mesh network, e.g., via an IP bridge device, and that are already IP compatible, the IP router 502 can manage private IP address generation similarly.
After a node device has been assigned an IP address by the IP router 502, IP data can be transferred to and from the node device and the IP network 504. Transfer of IP data in this way may involve encapsulating the IP data. As described above, the IP router 502 is connected to the IP network 504, allowing routing of assigned IP addresses against the existing wireless sensor nodes, e.g., wireless sensor nodes 508, 510, and 512. The IP router 502 provides the mapping and translations of an IPv4 or IPv6 address against the existing routing address of a wireless sensor node. Once the IP mapping is translated in the IP router 502, the IP data packet can be encapsulated into the protocol used by the wireless sensor node and sent across the wireless mesh network to its destination node. Once the IP data packet is received, it is unencapsulated and delivered to a terminating device that supports the IP incoming packet, which may be formatted, for example, according to the Transmission Control Protocol (TCP) or the User Datagram Protocol (UDP). In some mesh networks, the IP bridge device 506 of
Incoming IP packets are captured at the IP level of the protocol stack. The IP router 502 then encapsulates the incoming IP packets into the wireless network protocols that are used by the wireless node devices. In some cases, at an optional step 706, the IP router 502 divides the IP data packet into a number of segments to fit within the constraints of the wireless network protocols that are used by the wireless node devices. At a step 708, the IP router 502 encapsulates either the segmented IP data packet or, if the IP data packet was not segmented, the original IP data packet, into a wireless data gram that is compliant with the wireless network protocol that is used by the destination device. At a step 710, the IP router 502 forwards the wireless data gram to the IP bridge device 506.
When the IP bridge device 506 receives the wireless data gram, it unencapsulates the wireless data gram to the IP data packet or data packet segments at a step 712. If the wireless data gram contains a segmented IP data packet, the IP bridge device 506 then reassembles the data packets into a complete IP data packet at an optional step 714. At a step 716, either the original IP packet or the reassembled IP data packet is routed to an IP side of the IP bridge device 506 for delivery according to the physical layer used, such as Ethernet, Universal Serial Bus (USB) or RS232. At a step 718, the unencapsulated IP data packet is forwarded to the destination device based on a mapping between the destination IP address and the IP addresses assigned to the wireless node devices.
IP devices that are physically connected to the IP bridge device 506 terminating the incoming IP data packets, based on the destination IP address, can then respond to the IP request by sending a response IP data packet back to the IP bridge device 506 at an optional step 720. At an optional step 722, the IP bridge device 506 encapsulates the response IP data packet into the wireless mesh protocol. Finally, the IP bridge device 506 forwards the encapsulated response IP data packet to the IP router 502 at an optional step 724 for transmission across the IP network 504.
According to another embodiment, after a node device has been assigned an IP address by the IP router 502, Internet Control Message Protocol (ICMP) data packets can be routed over the wireless mesh network without the need to modify the hardware of existing wireless sensor nodes to support IP protocol stacks and the associated ICMP protocols. As described above, the IP router 502 is connected to the IP network 504 to allow routing of any assigned IP address against existing wireless sensor nodes, such as wireless sensor nodes 508, 510, and 512. The IP router 502 provides mapping and translations of an IP address against the existing routing addresses of wireless sensor nodes. Once the IP mapping is translated in the IP router 502, an ICMP request can be translated into an equivalent wireless mesh network command and sent across the wireless mesh network to an associated terminating device. When the terminating device receives the ICMP request, the IP router 502 may generate an ICMP response and send the response back to the originating IP address on the IP network 504.
In some wireless mesh networks, the IP bridge device 506 can be used to provide the bridge from the wireless mesh network to an IP based network, allowing the IP termination to an IP supporting device that does not support the wireless mesh network wireless radio. In such embodiments, the IP bridge device 506 provides the same function as the IP router 502 in that it converts the wireless protocol message, e.g., a ping equivalent, to an ICMP request and routes the ICMP request to an IP compatible device connected to the IP bridge device 506. The IP terminating device can transmit ICMP responses back through the IP bridge device 506 to allow conversion back to the wireless protocol equivalent response of the wireless sensor nodes. The equivalent response can then be routed back across the wireless mesh network to the IP router 502. When the IP router 502 receives the response, the IP router 502 creates an ICMP response and routes it back to the IP network 504 for delivery to the originating IP device.
Next, at a step 806, the IP router 502 translates the ICMP data packet to an equivalent network command, such as an echo request, that is compatible with a wireless network protocol used by the receiving device. The IP router 502 forwards the network command to the IP bridge device 506 at a step 808. At a step 810, the IP bridge device 506 receives the network command. The network command is then routed to an IP side of the IP bridge device 506 at a step 812 for delivery according to the physical layer used, such as Ethernet, Universal Serial Bus (USB) or RS232. The network command is then forwarded to the receiving device based on a mapping between the destination IP address and the IP addresses assigned to the wireless node devices at a step 814.
At a step 816, the receiving device may or may not generate a reply. If the receiving device does generate a reply, then at a step 818, the IP router 502 receives the reply. The IP router 502 then generates an appropriate ICMP response data packet, such as an echo response, at a step 820, which it forwards to the originating device at a step 822.
On the other hand, if the receiving device does not generate a reply, then the IP router 502 generates a different ICMP response data packet at a step 824. The IP router 502 then forwards this ICMP response data packet to the originating device at a step 826.
While systems and methods have been described and illustrated with reference to specific embodiments, those skilled in the art will recognize that modification and variations may be made without departing from the principles described above and set forth in the following claims. For example, although in the embodiments described above, while the wireless sensor nodes are described as lacking support for the IP protocol stack and associated protocols, it will be appreciated that the techniques described herein can be applied to wireless mesh networks in which some devices support the IP protocol stack and associated protocols. Accordingly, reference should be made to the following claims as describing the scope of the present invention.
