WO2011094500A1 - Mesh infrastructure utilizing alternative communication paths - Google Patents
Mesh infrastructure utilizing alternative communication paths Download PDFInfo
- Publication number
- WO2011094500A1 WO2011094500A1 PCT/US2011/022868 US2011022868W WO2011094500A1 WO 2011094500 A1 WO2011094500 A1 WO 2011094500A1 US 2011022868 W US2011022868 W US 2011022868W WO 2011094500 A1 WO2011094500 A1 WO 2011094500A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- communication
- node
- path
- alternative
- collector
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
- H04W40/04—Communication route or path selection, e.g. power-based or shortest path routing based on wireless node resources
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01D—MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
- G01D4/00—Tariff metering apparatus
- G01D4/002—Remote reading of utility meters
- G01D4/004—Remote reading of utility meters to a fixed location
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01D—MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
- G01D2204/00—Indexing scheme relating to details of tariff-metering apparatus
- G01D2204/40—Networks; Topology
- G01D2204/45—Utility meters networked together within a single building
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01D—MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
- G01D4/00—Tariff metering apparatus
- G01D4/002—Remote reading of utility meters
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02B—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO BUILDINGS, e.g. HOUSING, HOUSE APPLIANCES OR RELATED END-USER APPLICATIONS
- Y02B90/00—Enabling technologies or technologies with a potential or indirect contribution to GHG emissions mitigation
- Y02B90/20—Smart grids as enabling technology in buildings sector
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
- Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
- Y04S20/00—Management or operation of end-user stationary applications or the last stages of power distribution; Controlling, monitoring or operating thereof
- Y04S20/30—Smart metering, e.g. specially adapted for remote reading
Definitions
- Fixed communication networks can operate using wire line or radio technology.
- distribution line carrier systems are wire-based and use the utility lines themselves for communications. Radio technology has tended to be preferred due to higher data rates and independence from the distribution network. Radio technology in the 902-928 MHz frequency range can operate without a Federal Communications Commission (FCC) license by restricting power output and by spreading the transmitted energy over a large portion of the available bandwidth.
- FCC Federal Communications Commission
- Some conventional utility meter reading communication networks use multiple repeaters. In some such networks, a head end computer system keeps track of the distribution network configuration and configures the repeaters to work within that distribution network. Such networks work well as long as the power line network do not change
- AMI Advanced Metering Infrastructure
- MRD meter reading devices
- the wireless communication circuitry may include a transponder that is uniquely identified by a transponder serial number.
- the endpoint nodes may either transmit their meter data directly to the central node, or indirectly though one or more intermediate bi-directional nodes which serve as repeaters for the meter data of the transmitting node.
- Some networks may employ a mesh networking architecture.
- 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. Accordingly, mesh networks are self-configuring and self-healing, significantly reducing installation and maintenance efforts.
- polling the route from a collector to an endpoint is established and data is pulled from the endpoint by sending a unicast packet to the endpoint and back.
- bubble up the data may be originated at the endpoint based on a schedule or a prior instruction, and the route to the collector or gateway can be dynamically determined.
- the communication node and the central node at a given time. If a break occurs in this path, the communication node will be unresponsive until the wireless mesh network can reconfigure and establish a different path from the communication node to the central node. For some network operations, this delay in the healing of the path may be unacceptable.
- a wireless mesh network, method, and processor-readable storage medium for maintaining both a primary communication path and an alternative communication path for a communication node are disclosed herein.
- the control node determines an alternative communication path for each node in communication with the control node and stores, for each node, primary communication path information and alternative communication path information.
- One embodiment is directed to a wireless network comprising a control node and a plurality of communication nodes in wireless communication with the control node.
- Each of the communication nodes has a wireless communication path to the control node that is either a direct path or an indirect path through one or more other communication nodes that serve as repeaters.
- the control node determines an alternative communication path and stores primary
- Another embodiment is directed to a method of operating a network that has a control node that communicates with a plurality of communication nodes.
- Each of the communication nodes has a wireless communication path to the control node that is either a direct path or an indirect path through one or more other communication nodes that serve as repeaters.
- the method involves causing the control node to instruct the communication nodes in wireless communication with the control node to respond to node scans.
- the control node is caused to instruct a first communication node in wireless communication with the control node to conduct a node scan to identify a plurality of second communication nodes within communication range of the first communication node.
- the control node is further caused to determine an alternative communication path from the control node to the first communication node and to store primary communication path information and alternative communication path information associated with the first communication node.
- the method may be implemented using a processor readable storage medium that stores instructions that, when executed by the processor, cause the processor to carry out the method.
- control node can switch from the primary path to the alternative path when a failure in the primary path is detected. Because the control node determines and stores information relating to the alternative path before the failure occurs, switching from the primary path to the alternative path involves little, if any, delay.
- Figure 1 is a diagram of an exemplary metering system
- Figure 2 expands upon the diagram of Fig. 1 and illustrates an exemplary metering system in greater detail
- Figure 3 A is a block diagram illustrating an exemplary collector
- Figure 3B is a block diagram illustrating an exemplary meter
- Figure 4 is a diagram of an exemplary subnet of a wireless network for collecting data from remote devices
- Figure 5 illustrates an example method for identifying an alternative communication path in a wireless mesh network according to one embodiment
- Figure 6 is a diagram illustrating an example wireless mesh network in which an alternative communication path is identified using the method of Figure 5.
- 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.
- Figure 1 provides a diagram of one exemplary metering system 110.
- System 1 10 comprises a plurality of meters 114, which are operable to sense and record consumption or usage of a service or commodity such as, for example, electricity, water, or gas.
- Meters 114 may be located at customer premises such as, for example, a home or place of business.
- Meters 114 comprise circuitry for measuring the consumption of the service or commodity being consumed at their respective locations and for generating data reflecting the consumption, as well as other data related thereto.
- Meters 114 may also comprise circuitry for wirelessly transmitting data generated by the meter to a remote location.
- Meters 114 may further comprise circuitry for receiving data, commands or instructions wirelessly as well.
- meters that are operable to both receive and transmit data may be referred to as “bi-directional” or “two- way” meters, while meters that are only capable of transmitting data may be referred to as “transmit-only” or “one-way” meters.
- the circuitry for transmitting and receiving may comprise a transceiver.
- meters 114 may be, for example, electricity meters manufactured by Elster Electricity, LLC and marketed under the tradename REX.
- System 110 further comprises collectors 116.
- collectors 116 are also meters operable to detect and record usage of a service or commodity such as, for example, electricity, water, or gas.
- collectors 116 are operable to send data to and receive data from 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.
- 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).
- FHSS frequency hopping spread spectrum
- DSSS direct sequence spread spectrum
- a collector 116 and the meters 114 with which it communicates define a subnet/LAN 120 of system 110.
- meters 114 and collectors 116 may be referred to as "nodes" in the subnet 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.
- 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.
- PSTN public switched telephone network
- FHSS Frequency Ho
- the system 110 comprises a network management server 202, a network management system (NMS) 204 and the data collection server 206 that together manage one or more subnets/LANs 120 and their constituent nodes.
- NMS network management system
- the NMS 204 tracks changes in network state, such as new nodes
- Each of the meters 114 and collectors 116 is assigned an identifier (LAN
- 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.
- a utility's identifier for a node e.g., a utility serial number
- manufacturer serial number i.e., a serial number assigned by the manufacturer of the meter
- 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.
- 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.
- 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.
- 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.
- Figure 3 A is a block diagram illustrating further details of one
- collector 116 Although certain components are designated and discussed with reference to Figure 3 A, it should be appreciated that the invention is not limited to such components. In fact, various other components typically found in an electronic meter may be a part of collector 116, but have not been shown in Figure 3 A for the purposes of clarity and brevity. Also, the invention may use other components to accomplish the operation of collector 116. The components that are shown and the functionality described for collector 116 are provided as examples, and are not meant to be exclusive of other components or other functionality.
- collector 1 16 may comprise metering circuitry
- the collector 1 16 may further comprise a display 310 for displaying information such as measured quantities and meter status and a memory 312 for storing data.
- the collector 1 16 further comprises wireless LAN communications circuitry 306 for communicating wirelessly with the meters 1 14 in a subnet/LAN and a network interface 308 for communication over the network 1 12.
- the metering circuitry 304, processor 305, display 310 and memory 312 are implemented using an A3 ALPHA meter available from Elster Electricity, Inc.
- 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
- the network interface 308 may be implemented by a WAN Option Board (e.g., a telephone modem) also installed within the A3 ALPHA meter.
- the WAN Option Board 308 routes messages from network 1 12 (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 1 14. Also, LAN Option Board 306 may have sufficient memory to store data received from meters 1 14. This data may include, but is not limited to the following: current billing data (e.g., the present values stored and displayed by meters 1 14), previous billing period data, previous season data, and load profile data.
- current billing data e.g., the present values stored and displayed by meters 1 14
- previous billing period data e.g., previous billing period data
- previous season data e.g., previous season data
- load profile data e.g., 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 1 16 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.
- collector 1 16 The responsibility of a collector 1 16 is wide and varied. Generally, collector 1 16 is responsible for managing, processing and routing data communicated between the collector and network 1 12 and between the collector and meters 1 14. Collector 1 16 may continually or intermittently read the current data from meters 1 14 and store the data in a database (not shown) in collector 1 16. 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.
- TOU Time-Of-Use
- FIG. 3B is a block diagram of an exemplary embodiment of a meter 114 that may operate in the system 110 of Figures 1 and 2.
- the meter 114 comprises metering circuitry 304' for measuring the amount of a service or commodity that is consumed, a processor 305' that controls the overall functions of the meter, a display 310' for displaying meter data and status information, and a memory 312' for storing data and program instructions.
- the meter 114 further comprises wireless communications circuitry 306' for transmitting and receiving data to/from other meters 114 or a collector 116.
- a collector 116 directly communicates with only a subset of the plurality of meters 114 in its particular subnet/LAN.
- Meters 114 with which collector 116 directly communicates may be referred to as "level one" meters 114a.
- the level one meters 114a are said to be one "hop" from the collector 116. Communications between collector 116 and meters 114 other than level one meters 114a are relayed through the level one meters 114a.
- the level one meters 114a operate as repeaters for communications between collector 116 and meters 114 located further away in subnet 120.
- 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.
- a subnet 120 may comprise any number of levels of meters 114.
- a subnet 120 may comprise one level of meters but might also comprise eight or more levels of meters 114.
- a subnet comprises eight levels of meters 114, as many as 1024 meters might be registered with a single collector 116.
- 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.
- 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 1 16 have stored thereon all of this same data for all meters 1 14 that are registered therewith. Thus, collector 1 16 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 1 14 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.
- collector 1 16 communicates with meters 1 14 in the subnet 120 using point-to-point transmissions.
- a message or instruction from collector 1 16 is routed through the designated set of repeaters to the desired meter 1 14.
- a meter 1 14 communicates with collector 1 16 through the same set of repeaters, but in reverse.
- collector 1 16 may need to quickly
- collector 1 16 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 1 16 and propagates through the entire subnet 120 one level at a time. For example, collector 1 16 may transmit a flood broadcast to all first level meters 1 14a.
- the first level meters 1 14a that receive the message pick a random time slot and retransmit the broadcast message to second level meters 1 14b. Any second level meter 1 14b can accept the broadcast, thereby providing better coverage from the collector out to the end point meters.
- the second level meters 1 14b 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.
- 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.
- time of use schedule data may also be comprised in the same broadcast message as the time.
- 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.
- 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
- 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.
- 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 1 16 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.
- 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.
- 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.
- 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 1 14 that relate to, or have the same cause as, the exception that was just reported.
- a daily exception is received, the exception is recorded in a file or a database table.
- 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.
- collector 116 registers a new meter 114 in subnet 120
- collector 116 records a daily exception identifying that the registration has taken place.
- 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.
- collector 116 communicates the daily exceptions once every 24 hours.
- a collector assigns designated communications paths to meters with bi-directional communication capability, and may change the
- 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 1 16 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.
- 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.
- 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.
- RSSI Received Signal Strength Indication
- 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.
- 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).
- 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 1 16 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- other measures of the communications reliability may be provided, such as an RSSI value.
- 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. [0066] 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.
- 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.
- 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.
- a maximum number of levels e.g., seven levels
- 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.
- 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.
- 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.
- 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.”
- collector 1 16 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.
- 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.
- 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.
- 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:
- RptPath the communication path to the destination meter (i.e., the list of identifiers of each repeater in the path from the collector to the destination node);
- the packet may also include integrity check information (e.g., CRC), a pad to fill-out unused portions of the packet and other control information.
- integrity check information e.g., CRC
- CRC integrity check information
- Inbound packets are packets transmitted from a meter at a given level to the collector.
- inbound packets contain the following fields, but other fields may also be included:
- DestAddr the ID of the collector to which the packet is to be transmitted
- RptAddr the ID of the parent node that serves as the next repeater for the sending node
- each meter knows the identifier of its parent node (i.e., the node in the next lower level that serves as a repeater for the present node).
- an inbound packet need only identify who is the next parent.
- a node receives an inbound packet, it checks to see if the RptAddr matches its own identifier. If not, it discards the packet. If so, it knows that it is supposed to forward the packet on toward the collector. The node will then replace the RptAddr field with the identifier of its own parent and will then transmit the packet so that its parent will receive it. This process will continue through each repeater at each successive level until the packet reaches the collector.
- 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.
- the level two node with the matching identifier 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.
- the exemplary system is operable to reconfigure itself to address inadequacies in the system.
- 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.
- 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.
- the collector 116 recognizes the response as originating from a registered meter but that by reregistering 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).
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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 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.
- 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.
- 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.
- the unregistered command to propagate through the subnet
- 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”.
- the nodes continue to respond to application layer and immediate retries allowing the unregistration command to propagate to all nodes in the subnet.
- the meters register with the replacement collector using the procedure described above.
- collector 116 One of collector's 116 main responsibilities within subnet 120 is to retrieve metering data from meters 114.
- 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.
- the data collection process begins with the collector 1 16 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.
- collector 116 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.
- Figure 4 is a block diagram illustrating a subnet 401 that includes a number of one-way meters 451-456. As shown, meters 1 14a-k are two-way devices. In this example, the two-way meters 1 14a-k operate in the exemplary manner described above, such that each meter has a communication path to the collector 1 16 that is either a direct path (e.g., meters 1 14a and 1 14b have a direct path to the collector 1 16) or an indirect path through one or more intermediate meters that serve as repeaters.
- a direct path e.g., meters 1 14a and 1 14b have a direct path to the collector 1 16
- an indirect path through one or more intermediate meters that serve as repeaters.
- meter 1 14h has a path to the collector through, in sequence, intermediate meters 1 14d and 1 14b.
- a one-way meter e.g., meter 451
- the data may be received at one or more two-way meters that are in proximity to the one-way meter (e.g., two- way meters 1 14f and 1 14g).
- the data from the one-way meter is stored in each two-way meter that receives it, and the data is designated in those two-way meters as having been received from the one-way meter.
- the data from the one-way meter is communicated, by each two-way meter that received it, to the collector 1 16.
- the collector reads the two-way meter data, it recognizes the existence of meter data from the one-way meter and reads it as well. After the data from the one-way meter has been read, it is removed from memory.
- embodiments disclosed herein involve a wireless mesh network in which a collector maintains both a primary path and an alternative path to each communication node. If the primary path becomes unavailable, the collector can immediately attempt the communication on the alternative path without incurring the time penalty of reconfiguring the network.
- FIG. 5 illustrates an example method 500 for operating a wireless mesh network according to one embodiment.
- a communication node is registered into the network at a step 502, for example, after being qualified by determining the reliability of communications between the communication node and the collector or central node, that communication node is marked as needing an alternative path at a step 504.
- the network switches to an alternative path discovery mode at a step 506. In this mode, the collector or central node instructs all communication nodes to respond to node scans at a step 508.
- the collector or central node instructs all communication nodes that have been marked as needing an alternative path to conduct a node scan and to qualify communication nodes that are identified in the node scan.
- the communication node that conducts the node scan evaluates the quality of the link between it and the identified communication node.
- the identified communication node is qualified if the quality of the link meets a performance criterion. For example, the communication node that conducts the node scan may repeatedly send a message that requires a response to the identified communication node and wait for a response from the identified communication node. Signal strength may affect the link quality, but other factors may also enter this determination. For instance, if interfering devices are present and communicate using the ISM band, the link quality may be adversely affected even though the signal strength is relatively high.
- a communication node After a communication node has evaluated the link quality with identified neighboring communication nodes and has qualified appropriate communication nodes, it sends a list of qualified neighboring communication nodes to the collector. The collector then evaluates the list of neighboring communication nodes at a step 514.
- the collector identifies an alternative path to the
- Figure 6 illustrates a portion of a wireless mesh network 600 having a collector 602, communication nodes 604a-604g, and an endpoint node 606. Assuming that all of the depicted communication nodes 604a-604g are appropriately qualified, there are three communication paths from the collector 602 to the endpoint node 606.
- One path the primary path indicated by bold circles and bold arrows in Figure 6, comprises communication nodes 604a, 604c, and 604f.
- a second path comprising communication nodes 604a, 604c, and 604e.
- a third path comprising communication nodes 604b, 604d, and 604g.
- the second path shares a common parent node with the primary path, namely, communication node 604c. That is, communication node 604c is common to both the primary path and the second path. As shown in Figure 6, communication node 604c is located two hops away from the collector 602.
- the third path shares only the collector 602 itself as a common parent node with the primary path. Because the collector 602 is a higher level common parent node than communication node 604c, the third path is deemed the most different from the primary path and is selected as the alternative path.
- the alternative path is formed by the existing primary path to the new alternative path parent node, e.g., communication node 604g in the example shown in Figure 6, plus the last hop from the alternative path parent device to the endpoint device.
- the alternative path comprises communication nodes 604b, 604d, and 604g.
- the collector assigns a new repeater address to the alternative path parent node at a step 518.
- the alternative path parent node can be used as a router to the endpoint device.
- the collector can store the network identifier associated with the alternative path parent node as the alternative path address for the endpoint device at a step 520.
- the collector uses the primary path to the alternative path parent node and the last hop from that node to the endpoint device as the full alternative communication path.
- the collector may automatically switch to the alternative path. Since the alternative path parent node has already been discovered and made a repeater at step 518 of Figure 5, the switch between the primary path and the alternative path consumes a negligible amount of time.
- the collector may permanently designate the alternative communication path as a new primary communication path to a communication node and may repeat the process of Figure 5 to find a new alternative communication path for the end device. Failure of communications may be defined, for example, as a configurable number of successive communication failures or as a communication success rate that falls below a threshold.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Selective Calling Equipment (AREA)
- Small-Scale Networks (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Arrangements For Transmission Of Measured Signals (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
MX2012008612A MX2012008612A (en) | 2010-01-29 | 2011-01-28 | Mesh infrastructure utilizing alternative communication paths. |
NZ600572A NZ600572A (en) | 2010-01-29 | 2011-01-28 | Mesh infrastructure utilizing alternative communication paths |
CA2788320A CA2788320A1 (en) | 2010-01-29 | 2011-01-28 | Mesh infrastructure utilizing alternative communication paths |
AU2011210806A AU2011210806A1 (en) | 2010-01-29 | 2011-01-28 | Mesh infrastructure utilizing alternative communication paths |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US29958310P | 2010-01-29 | 2010-01-29 | |
US61/299,583 | 2010-01-29 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011094500A1 true WO2011094500A1 (en) | 2011-08-04 |
Family
ID=44319795
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2011/022868 WO2011094500A1 (en) | 2010-01-29 | 2011-01-28 | Mesh infrastructure utilizing alternative communication paths |
PCT/US2011/022898 WO2011094523A1 (en) | 2010-01-29 | 2011-01-28 | Clearing redundant data in wireless mesh network |
PCT/US2011/022881 WO2011094511A1 (en) | 2010-01-29 | 2011-01-28 | High priority data reads for acquisition of real-time data in wireless mesh network |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2011/022898 WO2011094523A1 (en) | 2010-01-29 | 2011-01-28 | Clearing redundant data in wireless mesh network |
PCT/US2011/022881 WO2011094511A1 (en) | 2010-01-29 | 2011-01-28 | High priority data reads for acquisition of real-time data in wireless mesh network |
Country Status (6)
Country | Link |
---|---|
US (3) | US20110188452A1 (en) |
AU (3) | AU2011210731A1 (en) |
CA (3) | CA2788320A1 (en) |
MX (3) | MX2012008065A (en) |
NZ (3) | NZ600572A (en) |
WO (3) | WO2011094500A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8792409B2 (en) | 2010-01-29 | 2014-07-29 | Elster Solutions, Llc | Clearing redundant data in wireless mesh network |
US8855102B2 (en) | 2010-01-29 | 2014-10-07 | Elster Solutions, Llc | Wireless communications providing interoperability between devices capable of communicating at different data rates |
EP3479068B1 (en) | 2016-07-01 | 2021-09-22 | 3F Security AB | Decentralized measuring system and network |
Families Citing this family (41)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8792341B2 (en) * | 2010-10-27 | 2014-07-29 | Futurewei Technologies, Inc. | System and method for machine-to-machine application based congestion control |
US8848521B1 (en) * | 2011-12-22 | 2014-09-30 | Landis+Gyr Technologies, Llc | Channel allocation and device configuration |
US20130279410A1 (en) * | 2012-04-18 | 2013-10-24 | Draker, Inc. | Communicating Data in a Mesh Network |
US9247480B2 (en) | 2012-04-24 | 2016-01-26 | Honeywell International Inc. | Dynamic threading gateway for embedded health management systems |
EP3611905B1 (en) | 2012-05-04 | 2024-06-12 | Itron, Inc. | Efficient firmware update in a narrow bandwidth system |
US8767744B2 (en) | 2012-05-04 | 2014-07-01 | Itron, Inc. | Prioritized reporting of metering data |
US9621411B2 (en) * | 2012-07-25 | 2017-04-11 | Itron, Inc. | Relaying information for an unreliably heard utility node |
US9160682B2 (en) * | 2013-03-14 | 2015-10-13 | Elster Solutions, Llc | Wireless network communication nodes with opt out capability |
US9722918B2 (en) | 2013-03-15 | 2017-08-01 | A10 Networks, Inc. | System and method for customizing the identification of application or content type |
US9912555B2 (en) | 2013-03-15 | 2018-03-06 | A10 Networks, Inc. | System and method of updating modules for application or content identification |
US9838425B2 (en) | 2013-04-25 | 2017-12-05 | A10 Networks, Inc. | Systems and methods for network access control |
US9306839B2 (en) | 2013-07-22 | 2016-04-05 | Symbol Technologies, Llc | IEEE 802.11U failover for a mesh network |
US9294503B2 (en) | 2013-08-26 | 2016-03-22 | A10 Networks, Inc. | Health monitor based distributed denial of service attack mitigation |
US9668198B2 (en) * | 2013-11-01 | 2017-05-30 | Qualcomm Incorporated | Method and apparatus for determining to use X2 gateway for X2 interface |
US9756071B1 (en) | 2014-09-16 | 2017-09-05 | A10 Networks, Inc. | DNS denial of service attack protection |
US9537886B1 (en) | 2014-10-23 | 2017-01-03 | A10 Networks, Inc. | Flagging security threats in web service requests |
US9621575B1 (en) | 2014-12-29 | 2017-04-11 | A10 Networks, Inc. | Context aware threat protection |
US9584318B1 (en) | 2014-12-30 | 2017-02-28 | A10 Networks, Inc. | Perfect forward secrecy distributed denial of service attack defense |
US9900343B1 (en) * | 2015-01-05 | 2018-02-20 | A10 Networks, Inc. | Distributed denial of service cellular signaling |
US9848013B1 (en) | 2015-02-05 | 2017-12-19 | A10 Networks, Inc. | Perfect forward secrecy distributed denial of service attack detection |
US10063591B1 (en) | 2015-02-14 | 2018-08-28 | A10 Networks, Inc. | Implementing and optimizing secure socket layer intercept |
WO2016188567A1 (en) * | 2015-05-26 | 2016-12-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Reconfiguration in a wireless mesh network |
US10948379B2 (en) * | 2015-05-26 | 2021-03-16 | Sensor Industries Corp. | Building sensor network for monitoring environmental conditions |
US20170041861A1 (en) * | 2015-08-06 | 2017-02-09 | Amir Fuhrmann | Method of Communicating to Selected Nodes in a Mesh Network |
US10448310B2 (en) | 2015-08-06 | 2019-10-15 | Gooee Limited | Method of mapping optimal communication routes through a mesh network |
US9787581B2 (en) | 2015-09-21 | 2017-10-10 | A10 Networks, Inc. | Secure data flow open information analytics |
US10505984B2 (en) | 2015-12-08 | 2019-12-10 | A10 Networks, Inc. | Exchange of control information between secure socket layer gateways |
US10469594B2 (en) | 2015-12-08 | 2019-11-05 | A10 Networks, Inc. | Implementation of secure socket layer intercept |
US10721639B2 (en) * | 2016-03-31 | 2020-07-21 | Lenovo (Singapore) Pte. Ltd. | Ascertaining a region of interest in a wireless network |
EP3258656B1 (en) * | 2016-06-14 | 2019-08-07 | Deutsche Telekom AG | Method, system and computer program comprising computer-readable program code for dynamic load balancing using different data transmission paths in a telecommunications network, comprising a mobile network part, a fixed network part and a plurality of router devices |
US10116634B2 (en) | 2016-06-28 | 2018-10-30 | A10 Networks, Inc. | Intercepting secure session upon receipt of untrusted certificate |
US10158666B2 (en) | 2016-07-26 | 2018-12-18 | A10 Networks, Inc. | Mitigating TCP SYN DDoS attacks using TCP reset |
US10292060B2 (en) | 2016-10-13 | 2019-05-14 | Eaton Intelligent Power Limited | Autonomous, power-dictated message routing for multi-hop mesh network outage communications |
US10638418B2 (en) * | 2016-11-04 | 2020-04-28 | Ford Global Technologies, Llc | Method and apparatus for data transfer connection management |
JP7114236B2 (en) * | 2017-10-19 | 2022-08-08 | キヤノン株式会社 | Communication device, control method, and program |
US10701670B2 (en) * | 2018-01-03 | 2020-06-30 | Wirepas Oy | System for co-operative repetition of broadcast messages |
EP3825858A4 (en) * | 2018-07-05 | 2022-03-23 | Nouvenn Corporation | Secure meshnet system for sharing data and respective coupling and interface devices |
US11940311B2 (en) * | 2021-07-14 | 2024-03-26 | Itron Global Sarl | Metrology module adaptable for use in multiple gas meters |
US11483224B1 (en) | 2021-08-13 | 2022-10-25 | Itron, Inc. | Determining network reliability using message success rates |
US11924077B2 (en) * | 2021-08-13 | 2024-03-05 | Itron, Inc. | Determining network reliability using message success rates |
US12047264B2 (en) | 2021-08-13 | 2024-07-23 | Itron, Inc. | Determining network reliability using message success rates |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6862263B1 (en) * | 1998-12-28 | 2005-03-01 | At&T Corp. | Hierarchical telecommunications network with fault recovery |
US20070286205A1 (en) * | 2006-01-31 | 2007-12-13 | Johansen Niels T | Node repair in a mesh network |
US20080043637A1 (en) * | 2006-08-15 | 2008-02-21 | Rahman Shahriar I | Route tree building in a wireless mesh network |
US20100157838A1 (en) * | 2007-06-15 | 2010-06-24 | Silver Spring Networks, Inc. | Route and Link Evaluation in Wireless Mesh Communications Networks |
Family Cites Families (67)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5115495A (en) * | 1988-10-18 | 1992-05-19 | The Mitre Corporation | Communications network system using full-juncture and partial-juncture station status information for alternate-path distance-vector routing |
US5553094A (en) * | 1990-02-15 | 1996-09-03 | Iris Systems, Inc. | Radio communication network for remote data generating stations |
US5530808A (en) * | 1993-12-10 | 1996-06-25 | International Business Machines Corporation | System for transferring ownership of transmitted data packet from source node to destination node upon reception of echo packet at source node from destination node |
US5590119A (en) * | 1995-08-28 | 1996-12-31 | Mci Communications Corporation | Deterministic selection of an optimal restoration route in a telecommunications network |
CA2241937C (en) * | 1996-01-03 | 2004-04-27 | International Business Machines Corporation | Robust method and apparatus enabling multi-mode wireless optical communication |
US5706428A (en) * | 1996-03-14 | 1998-01-06 | Lucent Technologies Inc. | Multirate wireless data communication system |
US5913921A (en) * | 1996-07-12 | 1999-06-22 | Glenayre Electronics, Inc. | System for communicating information about nodes configuration by generating advertisements having era values for identifying time reference for which the configuration is operative |
US8982856B2 (en) * | 1996-12-06 | 2015-03-17 | Ipco, Llc | Systems and methods for facilitating wireless network communication, satellite-based wireless network systems, and aircraft-based wireless network systems, and related methods |
US5999286A (en) * | 1997-01-09 | 1999-12-07 | Alcatel | Method and system for restoring a distributed telecommunications network |
JP2002501251A (en) * | 1998-01-22 | 2002-01-15 | イナリ、インコーポレイテッド | Method and apparatus for a universal data exchange gateway |
US6111672A (en) * | 1998-02-20 | 2000-08-29 | Mci Communications Corporation | Method, apparatus, and computer program product for optical network restoration |
US6223317B1 (en) * | 1998-02-28 | 2001-04-24 | Micron Technology, Inc. | Bit synchronizers and methods of synchronizing and calculating error |
WO2000074306A2 (en) * | 1999-05-28 | 2000-12-07 | Basic Resources, Inc. | Wireless transceiver network employing node-to-node data messaging |
US6917603B2 (en) * | 2000-01-20 | 2005-07-12 | Nortel Networks Limited | Servicing multiple high speed data users in shared packets of a high speed wireless channel |
US6934248B1 (en) * | 2000-07-20 | 2005-08-23 | Nortel Networks Limited | Apparatus and method for optical communication protection |
DE60041875D1 (en) * | 2000-09-20 | 2009-05-07 | Lucent Technologies Inc | Communication system and method with variable training means |
US7072976B2 (en) * | 2001-01-04 | 2006-07-04 | Sun Microsystems, Inc. | Scalable routing scheme for a multi-path interconnection fabric |
US7007189B2 (en) * | 2001-05-07 | 2006-02-28 | Sun Microsystems, Inc. | Routing scheme using preferred paths in a multi-path interconnection fabric in a storage network |
US7092402B1 (en) * | 2001-05-08 | 2006-08-15 | Rockwell Collins, Inc. | Adaptive data rate link mechanism for high frequency data communication |
US7490165B1 (en) * | 2001-07-18 | 2009-02-10 | Cisco Technology, Inc. | Method and apparatus for computing a path in a system with nodal and link diverse constraints |
EP1430619B1 (en) * | 2001-09-25 | 2007-05-02 | Meshnetworks, Inc. | A system and method employing algorithms and protocols for optimizing carrier sense multiple access (CSMA) protocols in wireless networks |
US8386303B2 (en) * | 2001-11-02 | 2013-02-26 | Jerry L. McKinney | Sparse data environmental equipment threshold compliance alarm system and method |
US7362709B1 (en) * | 2001-11-02 | 2008-04-22 | Arizona Board Of Regents | Agile digital communication network with rapid rerouting |
US7626508B2 (en) * | 2002-03-05 | 2009-12-01 | Aeromesh Corporation | Monitoring system and method |
CN1640033A (en) * | 2002-03-08 | 2005-07-13 | 艾威尔公司 | Systems and methods for high rate OFDM communications |
US7080156B2 (en) * | 2002-03-21 | 2006-07-18 | Sun Microsystems, Inc. | Message routing in a torus interconnect |
US7119713B2 (en) * | 2002-06-27 | 2006-10-10 | Elster Electricity, Llc | Dynamic self-configuring metering network |
US7701858B2 (en) * | 2003-07-17 | 2010-04-20 | Sensicast Systems | Method and apparatus for wireless communication in a mesh network |
US7738836B2 (en) * | 2003-09-26 | 2010-06-15 | Andrew Corporation | System and method of operation for network overlay geolocation system with repeaters using AM Golay Hadamard signatures |
US7075906B2 (en) * | 2003-09-30 | 2006-07-11 | Cisco Technology, Inc. | Method and apparatus for cell identification in wireless data networks |
US7239250B2 (en) * | 2004-04-26 | 2007-07-03 | Elster Electricity, Llc | System and method for improved transmission of meter data |
US7656804B2 (en) * | 2004-08-16 | 2010-02-02 | Motorola, Inc. | Method and apparatus for operating an AD-HOC communication system |
US7706745B2 (en) * | 2004-12-03 | 2010-04-27 | M&Fc Holding, Llc | Method, system, apparatus, and computer program product for communications relay |
MX2007011378A (en) * | 2005-03-16 | 2008-03-18 | Sensus Metering Systems Inc | Method, system, apparatus, and computer program product for determining a physical location of a sensor. |
US7308370B2 (en) * | 2005-03-22 | 2007-12-11 | Elster Electricity Llc | Using a fixed network wireless data collection system to improve utility responsiveness to power outages |
US7899027B2 (en) * | 2005-03-23 | 2011-03-01 | Cisco Technology, Inc. | Automatic route configuration in hierarchical wireless mesh networks |
GB2467657B (en) * | 2005-07-21 | 2010-09-15 | Firetide Inc | Method for enabling the efficient operation of arbitrarily interconnected mesh networks |
US7558294B2 (en) * | 2005-07-27 | 2009-07-07 | Intellon Corporation | Time synchronization in a network |
US7468952B2 (en) * | 2005-11-29 | 2008-12-23 | Sony Computer Entertainment Inc. | Broadcast messaging in peer to peer overlay network |
US7706376B2 (en) * | 2005-12-30 | 2010-04-27 | Intel Corporation | System and method for communicating with mobile stations over an extended range in a wireless local area network |
US7782835B2 (en) * | 2006-01-17 | 2010-08-24 | Motorola, Inc. | System and method for multihop packet forwarding |
CA2644139A1 (en) * | 2006-03-31 | 2007-11-10 | Qualcomm Incorporated | Memory management for high speed media access control |
US20090146839A1 (en) * | 2006-05-17 | 2009-06-11 | Tanla Solutions Limited | Automated meter reading system and method thereof |
US8350717B2 (en) * | 2006-06-05 | 2013-01-08 | Neptune Technology Group, Inc. | Fixed network for an automatic utility meter reading system |
JP4697068B2 (en) * | 2006-06-27 | 2011-06-08 | ソニー株式会社 | Wireless communication system, wireless communication apparatus, wireless communication method, and computer program |
US9304964B2 (en) * | 2006-06-30 | 2016-04-05 | Intel Corporation | Separable transport layer in cache coherent multiple component microelectronic systems |
US7843834B2 (en) * | 2006-09-15 | 2010-11-30 | Itron, Inc. | Use of minimal propagation delay path to optimize a mesh network |
US8103316B2 (en) * | 2006-09-29 | 2012-01-24 | Rosemount Inc. | Power management system for a field device on a wireless network |
EP1914930A1 (en) * | 2006-10-17 | 2008-04-23 | Matsushita Electric Industrial Co., Ltd. | User plane entity selection in a mobile communication system having overlapping pool areas |
US7609158B2 (en) * | 2006-10-26 | 2009-10-27 | Cooper Technologies Company | Electrical power system control communications network |
US8248921B2 (en) * | 2006-11-03 | 2012-08-21 | At&T Intellectual Property I, L.P. | System and method of distributing digital content |
CN101242342B (en) * | 2007-02-05 | 2012-09-19 | 华为技术有限公司 | Multicast method and multicast route method |
US8325627B2 (en) * | 2007-04-13 | 2012-12-04 | Hart Communication Foundation | Adaptive scheduling in a wireless network |
US8169974B2 (en) * | 2007-04-13 | 2012-05-01 | Hart Communication Foundation | Suspending transmissions in a wireless network |
US7903756B2 (en) * | 2007-10-22 | 2011-03-08 | Harris Corporation | System and method for communicating data using waveform with extended preamble |
US20090109955A1 (en) * | 2007-10-31 | 2009-04-30 | Qualcomm Incorporated | Method and apparatus for improved frame synchronization in a wireless communication network |
EP2215556B1 (en) * | 2007-11-25 | 2019-08-28 | Trilliant Networks, Inc. | System and method for transmitting power status notifications in an advanced metering infrastructure network |
WO2009067254A1 (en) * | 2007-11-25 | 2009-05-28 | Trilliant Networks, Inc. | System and method for operating mesh devices in multi-tree overlapping mesh networks |
US9612132B2 (en) * | 2007-12-26 | 2017-04-04 | Elster Solutions, Llc | Optimized data collection in a wireless fixed network metering system |
US7940679B2 (en) * | 2008-05-08 | 2011-05-10 | Elster Electricity, Llc | Power outage management and power support restoration for devices in a wireless network |
US8275404B2 (en) * | 2008-10-29 | 2012-09-25 | Google Inc. | Managing and monitoring emergency services sector resources |
US8730056B2 (en) * | 2008-11-11 | 2014-05-20 | Itron, Inc. | System and method of high volume import, validation and estimation of meter data |
US20100157889A1 (en) * | 2008-12-18 | 2010-06-24 | Motorola, Inc. | System and method for improving efficiency of broadcast communications in a multi-hop wireless mesh network |
US8411746B2 (en) * | 2009-06-12 | 2013-04-02 | Qualcomm Incorporated | Multiview video coding over MPEG-2 systems |
US8437245B2 (en) * | 2009-08-31 | 2013-05-07 | Texas Instruments Incorporated | Wireless network system |
NZ600572A (en) | 2010-01-29 | 2014-09-26 | Elster Solutions Llc | Mesh infrastructure utilizing alternative communication paths |
US8683027B2 (en) * | 2011-06-08 | 2014-03-25 | International Business Machines Corporation | Utilization of uncertainty dependency relationships between items in a data stream |
-
2011
- 2011-01-28 NZ NZ600572A patent/NZ600572A/en not_active IP Right Cessation
- 2011-01-28 CA CA2788320A patent/CA2788320A1/en not_active Abandoned
- 2011-01-28 WO PCT/US2011/022868 patent/WO2011094500A1/en active Application Filing
- 2011-01-28 AU AU2011210731A patent/AU2011210731A1/en not_active Abandoned
- 2011-01-28 WO PCT/US2011/022898 patent/WO2011094523A1/en active Application Filing
- 2011-01-28 NZ NZ601064A patent/NZ601064A/en not_active IP Right Cessation
- 2011-01-28 US US13/015,920 patent/US20110188452A1/en not_active Abandoned
- 2011-01-28 WO PCT/US2011/022881 patent/WO2011094511A1/en active Application Filing
- 2011-01-28 US US13/015,814 patent/US8792409B2/en active Active
- 2011-01-28 US US13/015,780 patent/US20110188444A1/en not_active Abandoned
- 2011-01-28 CA CA2788325A patent/CA2788325C/en not_active Expired - Fee Related
- 2011-01-28 MX MX2012008065A patent/MX2012008065A/en active IP Right Grant
- 2011-01-28 AU AU2011210743A patent/AU2011210743A1/en not_active Abandoned
- 2011-01-28 CA CA2788327A patent/CA2788327A1/en not_active Abandoned
- 2011-01-28 NZ NZ600995A patent/NZ600995A/en not_active IP Right Cessation
- 2011-01-28 AU AU2011210806A patent/AU2011210806A1/en not_active Abandoned
- 2011-01-28 MX MX2012008613A patent/MX2012008613A/en active IP Right Grant
- 2011-01-28 MX MX2012008612A patent/MX2012008612A/en active IP Right Grant
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6862263B1 (en) * | 1998-12-28 | 2005-03-01 | At&T Corp. | Hierarchical telecommunications network with fault recovery |
US20070286205A1 (en) * | 2006-01-31 | 2007-12-13 | Johansen Niels T | Node repair in a mesh network |
US20080043637A1 (en) * | 2006-08-15 | 2008-02-21 | Rahman Shahriar I | Route tree building in a wireless mesh network |
US20100157838A1 (en) * | 2007-06-15 | 2010-06-24 | Silver Spring Networks, Inc. | Route and Link Evaluation in Wireless Mesh Communications Networks |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8792409B2 (en) | 2010-01-29 | 2014-07-29 | Elster Solutions, Llc | Clearing redundant data in wireless mesh network |
US8855102B2 (en) | 2010-01-29 | 2014-10-07 | Elster Solutions, Llc | Wireless communications providing interoperability between devices capable of communicating at different data rates |
EP3479068B1 (en) | 2016-07-01 | 2021-09-22 | 3F Security AB | Decentralized measuring system and network |
Also Published As
Publication number | Publication date |
---|---|
MX2012008613A (en) | 2012-10-05 |
AU2011210743A1 (en) | 2012-07-26 |
US20110188444A1 (en) | 2011-08-04 |
WO2011094523A1 (en) | 2011-08-04 |
WO2011094511A1 (en) | 2011-08-04 |
AU2011210731A1 (en) | 2012-07-19 |
CA2788327A1 (en) | 2011-08-04 |
US8792409B2 (en) | 2014-07-29 |
NZ600995A (en) | 2014-09-26 |
US20110188452A1 (en) | 2011-08-04 |
AU2011210806A1 (en) | 2012-07-05 |
MX2012008065A (en) | 2012-07-30 |
CA2788325A1 (en) | 2011-08-04 |
CA2788325C (en) | 2016-01-19 |
NZ601064A (en) | 2014-08-29 |
US20110188445A1 (en) | 2011-08-04 |
MX2012008612A (en) | 2012-10-05 |
CA2788320A1 (en) | 2011-08-04 |
NZ600572A (en) | 2014-09-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2788325C (en) | High priority data reads for acquisition of real-time data in wireless mesh network | |
CA2612939C (en) | Optimization of reduncancy and throughput in an automated meter data collection system using a wireless network | |
US8855102B2 (en) | Wireless communications providing interoperability between devices capable of communicating at different data rates | |
AU2010235877B2 (en) | Packet acknowledgement for polled mesh network communications | |
AU2012200453B2 (en) | Mesh infrastructure utilizing priority repeaters and multiple transceivers | |
US9078050B2 (en) | Techniques for clock recovery in a mobile information collection network following a power outage | |
AU2013200542B2 (en) | Scalable packets in a frequency hopping spread spectrum (fhss) system | |
CA2830601A1 (en) | Phase detection in mesh network smart grid system | |
CA2781351C (en) | Synchronized communication for mesh connected transceiver | |
CA2717641C (en) | Packet acknowledgment for polled mesh network communications | |
CA2727311C (en) | Wireless communications providing interoperability between devices capable of communicating at different data rates | |
NZ600893B (en) | Synchronised communication for mesh connected transceiver |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11737705 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011210806 Country of ref document: AU |
|
ENP | Entry into the national phase |
Ref document number: 2011210806 Country of ref document: AU Date of ref document: 20110128 Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: MX/A/2012/008612 Country of ref document: MX |
|
ENP | Entry into the national phase |
Ref document number: 2788320 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 11737705 Country of ref document: EP Kind code of ref document: A1 |