Connect public, paid and private patent data with Google Patents Public Datasets

Wireless mesh network with pinch point and low battery alerts

Info

Publication number
WO2010036885A2
WO2010036885A2 PCT/US2009/058366 US2009058366W WO2010036885A2 WO 2010036885 A2 WO2010036885 A2 WO 2010036885A2 US 2009058366 W US2009058366 W US 2009058366W WO 2010036885 A2 WO2010036885 A2 WO 2010036885A2
Authority
WO
Grant status
Application
Patent type
Prior art keywords
device
wireless
network
pinch
devices
Prior art date
Application number
PCT/US2009/058366
Other languages
French (fr)
Other versions
WO2010036885A3 (en )
WO2010036885A4 (en )
Inventor
Daniel Clifford Carlson
Iain Peter Sharp
Mark Richard Ivison
Peter Hodgson
Kevin Andrew Shaw
Original Assignee
Fisher-Rosemount Systems, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATIONS NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATIONS NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0225Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATIONS NETWORKS
    • H04W84/00Network topologies
    • H04W84/18Self-organising networks, e.g. ad-hoc networks or sensor networks
    • Y02D70/00
    • Y02D70/22

Abstract

A wireless mesh network includes a plurality of wireless devices and a gateway organized in a multi hop mesh topology. Each wireless device maintains and reports radio statistics to the gateway, and also reports battery conditions of its power source. The device manager communicates with the gateway and provides an alert indicating existence of a pinch point within the mesh network based upon the radio statistics. When a low battery condition is reported by a device, the device manager determines whether loss of that device is a pinch point or will cause a pinch point, and provides a low battery alert prioritized based upon the pinch point analysis.

Description

WIRELESS MESH NETWORK WITH PINCH POINT AND LOW BATTERY ALERTS

CROSS-REFERENCE TO RELATED APPLICATION(S ) This application claims priority to U.S. Provisional Patent Application No. 61/099,959, filed September 25, 2008 which is hereby incorporated by reference in its entirety.

BACKGROUND

A wireless mesh network is a communication network made up of a plurality of wireless devices (i.e., nodes) organized in a mesh topology. In a true wireless mesh network, which may also be referred to as a self-organizing multi-hop network, each device must be capable of routing messages for itself as well as other devices in the network. The concept of messages hopping from node to node through the network is beneficial because lower power RF radios can be used, and yet the mesh network can span a significant physical area delivering messages from one end to the other. High power radios are not needed in a mesh network, in contrast with point-to-point systems which employ remote devices communicating directly to a centralized base-station.

The term 'self-organizing' refers to the capability of mesh networks to form alternate paths for messaging between devices and between devices and a data collector, or a bridge or gateway to some higher- level, higher-speed data bus. Having alternate, redundant paths for wireless messages enhances data reliability by ensuring there is at least one alternate path for messages to flow even if another path gets blocked or degrades due to environmental influences or due to interference.

The paths provided from each node to a bridge or gateway are dynamic, meaning the paths can change in response to a path being blocked or a new path being added. For example, when a device node is commissioned it will generate a list of devices (i.e., neighbors) with which it can communicate. This list may be particularly dynamic as the radio frequency (RF) environment and physical space occupied by the network change (e.g., a wall or metal shield is constructed between two devices limiting communication between the devices). Based on the dynamic neighbor list, the network manager associated with the gateway selects parent/child devices which define the communication paths to/from the device to the gateway device. The list of parent/child devices is also dynamic, but typically less dynamic than the neighbor list. Because of these dynamics, the organization of the wireless mesh network is continuously changing. One method of analyzing the operation of a mesh network is to review the organization of the mesh network based on the neighbor lists, parent-child lists, etc. provided by the network. Changes in the organization of the network are used to diagnose problems associated with the network. Prior art methods of analyzing the list include displaying each node in a diagram with lines connecting neighbors and/or parent- child pairs.

If a wireless device (or devices) is reliant on a single wireless device (or limited number of wireless devices) to route its message to the gateway, a pinch point (or communication bottleneck) may exist in the mesh network. A wireless device may be deemed to be a pinch point if a failure of that device would result in other wireless devices in the network no longer having a route back to the gateway. A pinch point can have several negative impacts on a wireless network.

First, the wireless devices that have to communicate through the pinch point may have decreased communication reliability. Second, bandwidth for the wireless devices that have to communicate through the pinch point may be limited, and network performance may be adversely affected. Third, a wireless device that is a pinch point will consume additional power to transmit the increased message load. This is especially significant in battery-powered devices (resulting in decreased battery life) or devices dependent on energy scavenging (e.g. a solar-powered device). Pinch points occur due to a variety of circumstances. For example, pinch points can be the result of poor network design or installation, of a constantly changing RF environment, changes in the physical space in which the network is located (which impacts the RF environment), and of wireless devices being taken out of service.

Information as to whether a wireless device is a pinch point is not provided by the wireless devices or by the gateway. In many cases, users of wireless mesh network are unaware that a pinch point exists in the network until one or more of the adverse affects mentioned above occur. At the time that the user detects the adverse affect, he or she may begin to examine and graphically build a diagram of communication links between wireless devices in order to identify pinch points. This process can take anywhere from minutes to hours, depending on the complexity of the wireless mesh network. Once the communication characteristics of the network are mapped and graphed, the user is then able to address the issues (or issues) causing a network pinch point.

A pinch point that has a low battery can be a critical situation. If a wireless device that is a pinch point runs out of power, its radio will cease to function. The wireless mesh network will lose the pinch point device, as well as those other wireless devices that depend on the pinch point to communicate with the gateway.

In other cases, the loss of a particular wireless device due to loss of power may cause another device within the network to become a pinch point. Although the device that becomes a pinch point may still have adequate battery power, negative impact on the performance of the wireless mesh network will still occur.

Wireless devices in wireless mesh networks typically report battery condition to the gateway along with the measured value of the process variable being sensed by the wireless device. If a low battery alert is recognized, a user of the wireless mesh network may prioritize the replacement of the battery based on the importance of the measurement (the process variable value) generated by that wireless device. This prioritization, however, does not take into account whether low battery condition of a particular wireless device causes that wireless device to create a pinch point failure, causes another wireless device within the network to become a pinch point, or both. Thus the user may be unaware that a device with a low battery may place the measurements of other wireless devices at risk.

SUMMARY

A wireless mesh network includes a device manager that evaluates radio statistics produced by the wireless devices of the network to determine whether the wireless mesh network has a pinch point. An alert is provided, so that a user can take action to remedy the pinch point before an adverse affect on reliability, bandwidth, or wireless device power occurs.

In another embodiment, the wireless mesh network includes a device manager that uses battery condition as well as radio statistics to evaluate and predict network performance. The device manager alerts the user to existence of a wireless device with a low battery that is a pinch point, or a wireless device with a low battery that may cause another device to become a pinch point.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating a self-organizing mesh network system in which messages are routed between a host and field devices.

FIG. 2 is a flow chart illustrating one method of determining pinch points using neighbor information. DETAILED DESCRIPTION

FIG. 1 shows process communication system 10, which includes host computer

12, highspeed network 14, wireless mesh network 16 (which includes gateway 18 and wireless field devices or nodes 20a-20i...20N), and network computer 30. Gateway 18 interfaces mesh network 16 with host computer 12 over highspeed network 14.

Messages may be transmitted from host computer 12 to gateway 18 over network 14, and are then transmitted to a selected node of mesh network 16 over one of several different paths. Similarly, messages from individual nodes of mesh network 16 are routed through mesh network 16 from node-to-node over one of several paths until they arrive at gateway 18 and are then transmitted to host 12 over highspeed network 14.

Host computer 12 may be a distributed control system host running application programs to facilitate sending messages to field devices 20a- 2ON, and receiving and analyzing data contained in messages from field devices 20a-20N. Host computer 12 may use, for example, AMS (TM) Device Manager as an application program that allows users to monitor and interact with field devices 20a- 2ON. Host computer 12 may be located, for example, in a central control room and may display process information and alarms on a control room operator screen.

Gateway 18 can communicate with host computer 12 over network 14 using a number of different communication protocols. In one embodiment, network 14 is an RS485 two wire communication link, on which gateway 18 may communicate with host computer 12 using the MODBUS protocol. In another embodiment, network 14 is an Ethernet network, and communication over network 14 can support MODBUS TCP/IP using an Ethernet interface.

Gateway 18 and wireless devices 20a-20N communicate using a wireless communication protocol. In the following discussion, the WirelessHART protocol will be used by way of example, although other protocols usable in a wireless mesh network may also be used. The WirelessHART protocol uses time division multiple access

(TDMA) and channel hopping to control communication within wireless network 16.

Network manager 32, which may be implemented as software resident on gateway 18, schedules communications among wireless field devices 20a-20N and gateway 18.

Network manager 32 also defines communication paths among the gateway and the various wireless devices 20a- 2ON.

Time division multiple access (TDMA) uses time slots. In which communication between the various devices can take place. The series of time slots are defined to form a TDMA super frame. Network manager 32 determines which devices are assigned to a particular slot within the super frame for communication. All of the devices within the network are time synchronized to form a communication. Network manager 32 also assigns the particular channel and frequency on which the assigned devices will communicate during a particular time slot.

Network manager 32 defines communication paths for messages traveling from gateway 18 to the various wireless devices 20a- 2ON, as well as communication paths of return messages from wireless devices 20a- 2ON to gateway 18. The paths of messages are assigned by network manager 32 using information received from each of the wireless devices 20a- 2ON. During commissioning of each wireless device or node, the node communicates with other nodes to determine its neighbors. A neighbor is defined as a device or gateway that is in active communication with the wireless device. During each communication, each wireless device measures received signal strength (RSSI) from and to a neighbor. It also generates a periodically reports path stability, RSSI and other radio statistics regarding wireless communication with its neighbors.

Network manager 32 makes use of the neighbor information and RSSI information in determining the communication paths to be used for outgoing and returned messages. For each message path, network manager 32 identifies the parent nodes and child nodes for the various hops or links of the path. A parent is a device that passes communications through itself for another device (its child). A child is a device that communicates through another device (a parent) to reach a third device or gateway. A neighbor may be a parent or a child. Although FIG. 1 shows wireless mesh network 16 with only a single gateway 18, in other embodiments more than one gateway may be included. In that case, the gateways share network manager 32 so that the same wireless protocol (in this case WirelessHART) is operating throughout wireless mesh network 16.

Network computer 30 may, for example, be a computer used by maintenance personnel to monitor and service wireless network 16. Network computer 30 may be located, for example, in an instrumentation and electrical (I&E) maintenance shop.

Device manager 34 (which may be, for example, AMS (TM) Device Manager and AMS wireless SNAP-ON from Emerson Process Management) can be an application program running on network computer 30. Device manager 34 is used to provide alerts to maintenance personnel regarding existence of pinch points within wireless mesh network 16, as well as alerts regarding low battery conditions in wireless devices. Device manager 34 may also advise a user of the impact or likely impact of the pinch point, and may suggest how the pinch point may be resolved.

Each of wireless devices 20a- 2ON periodically reports radio statistics to gateway 18. These radio statistics are used by network manager 32 to determine communication paths and assign time slots. Radio statistics may also be used by device manager 34 in determining the existence of actual or potential pinch points. The radio statistics may include identification of neighbors, received signal strength (RSSI) from each neighbor, received signal strength (RSSI) to each neighbor, the percentage of successful communications with each neighbor (an indication of path stability), number of parents and children to that particular device or mode, parent-to-children ratio, parent-to- neighbor ratio, and children-to-neighbor ratio, and whether the device is within range of gateway 18. These radio statistics are gathered over a period of time and reported at intervals of, for example, about 15 minutes.

Each device also senses a parameter of the process (e.g. temperature, pressure, flow rate, liquid level) and sends a message containing the measured process variable to gateway 18 according to the schedule determined by network manager 32. Along with the process variable data, each wireless device 20a- 2ON also provides diagnostic data relating to the condition of operation of that device. The diagnostic information includes power source information. For those devices that are battery powered, the diagnostic information includes an indication of battery condition. Diagnostic information is received by gateway 18 and is provided over network 14 to network computer 30 and device manager 34.

Device manager 34 uses the radio statistics received by gateway 18 from wireless devices 20a-20N to analyze wireless network 16 for pinch points. There are a number of different ways that device manager 34 may use information, either individually or in combination, to identify pinch points. For example, information regarding the number of wireless devices within range of gateway 18 can be used as an indication of a pinch point condition. If less than three devices are in range of gateway 18, or if less than a certain percentage of all of the devices in network 16 (e.g. less than 10 percent) are within range of gateway 18, one or more pinch points may exist.

Another way of identifying pinch points is using the number of neighbors. If a particular device has an unusually large number of neighbors, this may indicate that it is a pinch point. In another method described in conjunction with FIG. 2, individual analysis of each device with respect to its neighbors can be used to identify which devices are pinch points.

Another method of identifying a pinch point from radio statistics uses the parent- to-children ratio of each node. A pinch point may be identified if the device has an unusually large or unusually small parent-to-children ratio. The statistical deviation of the parent-to-children ratio from mean values within the network can also be used by device manager 34 as an indication of a pinch point. Similar analysis can be performed using other ratios such as parent-to-neighbor or child-to-neighbor ratios.

The statistical deviation of the number of neighbors at a particular device with respect to the mean number of neighbors for each device within network 16 can indicate that the device in question is a pinch point.

When device manager 34 identifies a pinch point within wireless mesh network 16, it provides an alert to maintenance personnel through network computer 30. The alert indicates that a pinch point exists, and can identify by device number or by a visual representation the particular device that is a pinch point. In providing the alerts, device manager 34 can provide visual displays in which individual devices 20a- 2ON are represented in conjunction with a visual representation of the space in which they are located. An example of such a display is described in co-pending application Serial No. 12/394,399 filed February 27, 2009, and entitled "System for Visualizing Design and Organization of Wireless Mesh Networks and Physical Space", which is assigned to the same assignee as the present application, and is incorporated by reference in its entirety.

When diagnostic information from one of wireless devices 20a-20N indicates a low battery condition, device manager 34 can prioritize the low battery alert that is provided based upon whether the device reporting the low battery condition is either a possible pinch point itself, or would cause a possible pinch point to occur upon its failure. Device manager 34 can use the existing radio statistics to determine whether the device reporting a low battery condition is currently a possible pinch point. It can also perform an analysis to identify possible pinch points in the event that the device reporting the low battery condition were no longer present within wireless mesh network 16.

By performing a pinch point analysis for wireless mesh network 16 in conjunction with a reported low battery condition, device manager 34 can provide a prioritized low battery alert to the user. Normally a low battery condition will first be reported some time prior to the anticipated power failure. By providing an indication of the priority of battery condition as it relates to pinch points, the user is provided an indication of the criticality of an early replacement of the battery power source for the wireless device reporting a low battery condition. In that way, maintenance can be scheduled so that the highest priority battery replacement occurs first. As described previously, there are a number of different ways in which pinch points can be identified. The particular method or combination of methods used to analyze radio statistics from the wireless devices can vary. FIG. 2 illustrates one method, which uses neighbor information provided by the wireless devices to identify pinch points. This method allows pinch points to be identified without requiring parent/child information to the device.

The method first eliminates all devices identified which have no neighbors. These may be, for example, devices that were active within network 16 at one time, but have been withdrawn or replaced, or which are no longer operating. Testing of the remaining devices is the performed as illustrated by FIG. 2. FIG. 2 is a flow chart showing the evaluation of each wireless device X being tested to determine whether it is a pinch point. Upon having a device X identified for testing (step 50), device manager 34 starts the test procedure (step 52). Initially, device manager 34 assumes that none of the wireless devices can reach gateway 16 (step 54). Device manager 34 then accesses the list of devices with neighbors (excluding device X). For each device A in the list of devices with neighbors (step 56), device manager 34 determines whether device A has gateway as a neighbor (step 58).

If the answer is yes, device manager 34 adds device A to the list of devices which can reach the gateway (step 60). Device manager 34 also removes device A from the list of devices which cannot reach the gateway (step 62). Device manager 34 then proceeds to the next device A within the list (step 64). Alternatively, if device A at step 58 does not have the gateway as a neighbor, device manager 34 proceeds to the next device A (step 64).

Device manager 34 then proceeds to testing of each device B in the list of devices which cannot reach the gateway (step 66). Device manager 34 determines whether device B has a neighbor which is in the list of devices which can reach the gateway (step 68). If device B does have a neighbor in the list of devices which can reach the gateway, device B is added to the list of devices which can reach the gateway (step 70), and device B is removed from the list of devices which cannot reach the gateway (step 72). Device manager 34 then proceeds from step 72 to testing of the next device B (step 74). If the answer to the inquiry at step 68 is no (i.e. device B does not have a neighbor in the list of devices which can reach the gateway), then device manager proceeds to the next device B (step 74). If there is another device B to test, device manager 34 returns to step 66 and repeats the steps. This continues until the last device B has been tested. At that point, device manager 34 determines whether the list of devices which cannot reach the gateway is empty (step 76). If the answer is yes, device X is identified as not being a pinch point (step 78), and the testing ends (step 80). On the other hand, if the list of devices which cannot reach the gateway is not empty, device manager 34 determines whether a device was removed from the list of devices that cannot reach the gateway in the latest iteration (step 82). If the answer is yes, device manager 34 returns to step 66. If the answer is no, device X is identified as a pinch point (step 84). At that point, the process ends (step 80). The process illustrated in FIG. 2 is repeated for each device X that is identified as having neighbors within mesh network 16. When all devices have been tested using the method of FIG. 2, device manager 34 has a complete list of devices that are identified as pinch points.

The method illustrated by FIG. 2 has the advantage of using only neighbor information to make pinch point identification. This method may be used by itself, or in conjunction with any of the other methods described.

While the invention has been described with reference to an exemplary embodiment(s), it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment(s) disclosed, but that the invention will include all embodiments falling within the scope of the appended claims.

Claims

CLAIMS:
1. A wireless mesh network comprising: a gateway; a plurality of wireless devices, each wireless device providing radio statistics and battery condition to the gateway; a network manager for scheduling communication among the wireless devices and gateway and defining communication paths between the gateway and the wireless devices based upon ratio statistics provided by the wireless devices; and a device manager for providing a pinch point alert indicating existence of a pinch point within the mesh network based upon radio statistics.
2. The wireless mesh network of claim 1, wherein the device manager provides a prioritized low battery alert based upon battery condition data and an actual or potential pinch point associated with a source of the battery condition data.
3. The wireless mesh network of claim 1, wherein the radio statistics include at least one of identification of neighbors, received signal strength from neighbors, percentage of successful communications with neighbors, number of parents to each wireless device, number of children to each wireless device, a parent-to-children ratio, a parent-to- neighbor ratio, and a children-to-neighbor ratio.
4. The wireless mesh network of claim 1, wherein the device manager performs a pinch point analysis based upon a number of wireless devices within radio range of the gateway.
5. The wireless mesh network of claim 1, wherein the device manager performs a pinch point analysis based upon a percentage of all wireless devices in the network that are within radio range of the gateway.
6. The wireless mesh network of claim 1, wherein the device manager performs a pinch point analysis based upon neighbors of each wireless device.
7. The wireless mesh network of claim 6, wherein the pinch point analysis includes an evaluation of standard deviation of the number of neighbors and one wireless device to a mean value of neighbors per wireless device in the network.
8. The wireless mesh network of claim 1, wherein the device manager performs a pinch point analysis based upon a parent-to-children ratio.
9. The wireless mesh network of claim 8, wherein the pinch point analysis includes an evaluation of statistical deviation of the parent- to-children ratio of one wireless device to a mean value of the parent-to-children ratio for the network.
10. The wireless mesh network of claim 1, wherein the device manager provides a visual display that includes a visual representation of a particular wireless device that is a pinch point.
11. A method comprising: collecting radio statistics from a wireless devices of a wireless mesh network; determining communication paths, parent-child relationships and communication time slots for the wireless devices based upon the radio statistics; identifying a pinch point within the wireless mesh networks based upon the radio statistics; and producing an alert that indicates existence of the pinch point.
12. The method of claim 11 and further comprising: receiving battery condition data from the wireless devices; and producing a prioritized low battery alert if a wireless device with a low battery is a pinch point.
13. The method of claim 11 and further comprising: receiving battery condition data from the wireless devices; and producing a prioritized low battery alert if failure of a wireless device with a low battery will cause a pinch point to occur.
14. The method of claim 1, wherein the radio statistics include at least one of identification of neighbors, received signal strength from neighbors, percentage of successful communications with neighbors, number of parents to each wireless device, number of children to each wireless device, a parent-to-children ratio, a parent-to- neighbor ratio, and a children-to-neighbor ratio.
15. The method of claim 11, wherein identifying a pinch point includes performing a pinch point analysis based upon a number of wireless devices within radio range of the gateway.
16. The method of claim 11, wherein identifying a pinch point includes performing a pinch point analysis based upon neighbors of each wireless device.
17. The method of claim 11, wherein identifying a pinch point includes performing a pinch point analysis based upon at least one of a parent-to-children ratio, a parent-to- neighbor ratio, and a children-to-neighbor ratio.
18. The method of claim 11 and further comprising: providing a visual display that includes a visual representation of a particular wireless device that is a pinch point.
19. A method comprising: collecting radio statistics from wireless devices of a wireless mesh network; determining communication paths, parent-child relationships, and communication time slots for the wireless devices based upon the radio statistics; receiving battery condition data from the wireless devices; and producing a low battery alert based upon the battery condition data and the radio statistics.
20. The method of claim 19, wherein the prioritized low battery alert is produced if a wireless device with a low battery condition is a pinch point, or failure of the wireless device will cause another wireless device in the wireless mesh network to become a pinch point.
PCT/US2009/058366 2008-09-25 2009-09-25 Wireless mesh network with pinch point and low battery alerts WO2010036885A4 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US9995908 true 2008-09-25 2008-09-25
US61/099,959 2008-09-25

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
JP2011529254A JP5383809B2 (en) 2008-09-25 2009-09-25 Wireless mesh network having a failure cause alarm and low battery alarm
CA 2733268 CA2733268A1 (en) 2008-09-25 2009-09-25 Wireless mesh network with pinch point and low battery alerts
US12735074 US9485649B2 (en) 2008-09-25 2009-09-25 Wireless mesh network with pinch point and low battery alerts
CN 200980137945 CN102165811B (en) 2008-09-25 2009-09-25 Wireless mesh network with pinch point and method for identifying pinch point in wireless mesh network
EP20090816902 EP2340667B1 (en) 2008-09-25 2009-09-25 Wireless mesh network with pinch point and low battery alerts

Publications (3)

Publication Number Publication Date
WO2010036885A2 true true WO2010036885A2 (en) 2010-04-01
WO2010036885A3 true WO2010036885A3 (en) 2010-08-19
WO2010036885A4 true WO2010036885A4 (en) 2012-03-08

Family

ID=42060397

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2009/058366 WO2010036885A4 (en) 2008-09-25 2009-09-25 Wireless mesh network with pinch point and low battery alerts

Country Status (6)

Country Link
US (1) US9485649B2 (en)
JP (1) JP5383809B2 (en)
CN (1) CN102165811B (en)
CA (1) CA2733268A1 (en)
EP (1) EP2340667B1 (en)
WO (1) WO2010036885A4 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2512256A (en) * 2014-02-25 2014-09-24 Cambridge Silicon Radio Ltd Mesh profiling
US20170064630A1 (en) * 2015-08-26 2017-03-02 International Business Machines Corporation Efficient usage of internet services on mobile devices
US9692538B2 (en) 2014-02-25 2017-06-27 Qualcomm Technologies International, Ltd. Latency mitigation

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2761475A4 (en) * 2011-09-27 2015-05-27 Dominopos Pte Ltd System and method for running applications from computer devices
US8938219B2 (en) * 2012-05-03 2015-01-20 Bristol, Inc. Flow computers having wireless communication protocol interfaces and related methods
US9124446B2 (en) * 2012-09-28 2015-09-01 Bristol, Inc. Methods and apparatus to implement a remote terminal unit network
US20170094494A1 (en) * 2015-09-25 2017-03-30 Osram Sylvania Inc. Active proximity based wireless network commissioning

Family Cites Families (128)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0470630B1 (en) 1990-08-10 1996-02-07 Matsushita Electric Industrial Co., Ltd. Controlling apparatus of steering angle of rear wheels of four-wheel steering vehicle
US7558557B1 (en) 1991-11-12 2009-07-07 Broadcom Corporation Low-power messaging in a network supporting roaming terminals
US6374311B1 (en) 1991-10-01 2002-04-16 Intermec Ip Corp. Communication network having a plurality of bridging nodes which transmit a beacon to terminal nodes in power saving state that it has messages awaiting delivery
US20050192727A1 (en) 1994-05-09 2005-09-01 Automotive Technologies International Inc. Sensor Assemblies
US5560021A (en) 1994-04-04 1996-09-24 Vook; Frederick W. Power management and packet delivery method for use in a wireless local area network (LAN)
US5862391A (en) 1996-04-03 1999-01-19 General Electric Company Power management control system
US6301527B1 (en) 1996-04-03 2001-10-09 General Electric Company Utilities communications architecture compliant power management control system
US6891838B1 (en) 1998-06-22 2005-05-10 Statsignal Ipc, Llc System and method for monitoring and controlling residential devices
US6711166B1 (en) 1997-12-10 2004-03-23 Radvision Ltd. System and method for packet network trunking
US6185208B1 (en) 1998-04-30 2001-02-06 Phone.Com, Inc. Method and apparatus for fragmenting messages for a wireless network using group sharing of reference numbers
US6775276B1 (en) 1998-05-27 2004-08-10 3Com Corporation Method and system for seamless address allocation in a data-over-cable system
JP3757642B2 (en) 1998-09-29 2006-03-22 富士電機機器制御株式会社 Wireless communication network system
US7640007B2 (en) 1999-02-12 2009-12-29 Fisher-Rosemount Systems, Inc. Wireless handheld communicator in a process control environment
FI111760B (en) 1999-04-16 2003-09-15 Metso Automation Oy Field Device wireless control industrial process
US6317599B1 (en) 1999-05-26 2001-11-13 Wireless Valley Communications, Inc. Method and system for automated optimization of antenna positioning in 3-D
US6363062B1 (en) 1999-06-08 2002-03-26 Caly Corporation Communications protocol for packet data particularly in mesh topology wireless networks
US6832251B1 (en) 1999-10-06 2004-12-14 Sensoria Corporation Method and apparatus for distributed signal processing among internetworked wireless integrated network sensors (WINS)
US6826607B1 (en) 1999-10-06 2004-11-30 Sensoria Corporation Apparatus for internetworked hybrid wireless integrated network sensors (WINS)
US6859831B1 (en) 1999-10-06 2005-02-22 Sensoria Corporation Method and apparatus for internetworked wireless integrated network sensor (WINS) nodes
US6971063B1 (en) 2000-07-28 2005-11-29 Wireless Valley Communications Inc. System, method, and apparatus for portable design, deployment, test, and optimization of a communication network
US7246045B1 (en) 2000-08-04 2007-07-17 Wireless Valley Communication, Inc. System and method for efficiently visualizing and comparing communication network system performance
DE60018072T2 (en) 2000-10-27 2005-12-29 Invensys Systems, Inc., Foxboro Field device having a transmitter and / or receiver for wireless data transmission
US7075892B2 (en) 2000-11-03 2006-07-11 Telecommunications Research Laboratories Topological design of survivable mesh-based transport networks
US6731946B1 (en) 2000-11-22 2004-05-04 Ensemble Communications System and method for timing detector measurements in a wireless communication system
US7882253B2 (en) 2001-04-05 2011-02-01 Real-Time Innovations, Inc. Real-time publish-subscribe system
US20020167954A1 (en) 2001-05-11 2002-11-14 P-Com, Inc. Point-to-multipoint access network integrated with a backbone network
EP1293853A1 (en) 2001-09-12 2003-03-19 ENDRESS + HAUSER WETZER GmbH + Co. KG Transceiver module for a field device
US20030151513A1 (en) * 2002-01-10 2003-08-14 Falk Herrmann Self-organizing hierarchical wireless network for surveillance and control
US7130915B1 (en) 2002-01-11 2006-10-31 Compuware Corporation Fast transaction response time prediction across multiple delay sources
US7035773B2 (en) 2002-03-06 2006-04-25 Fisher-Rosemount Systems, Inc. Appendable system and devices for data acquisition, analysis and control
US6625169B1 (en) 2002-06-14 2003-09-23 Telesys Technologies, Inc. Integrated communication systems for exchanging data and information between networks
US20040001084A1 (en) 2002-06-28 2004-01-01 Nandini Shrinidhi N x M network graphical user interface and method of use
US6741554B2 (en) 2002-08-16 2004-05-25 Motorola Inc. Method and apparatus for reliably communicating information packets in a wireless communication network
US7562393B2 (en) 2002-10-21 2009-07-14 Alcatel-Lucent Usa Inc. Mobility access gateway
US6990189B2 (en) 2003-03-31 2006-01-24 Metro One Telecommunications, Inc. Technique for providing information assistance while maintaining connection information anonymity
US7388886B2 (en) 2003-04-16 2008-06-17 Motorola, Inc. Method and device for distributing communication signals
US7114388B1 (en) 2003-04-21 2006-10-03 Ada Technologies, Inc. Geographically distributed environmental sensor system
US20040259555A1 (en) 2003-04-23 2004-12-23 Rappaport Theodore S. System and method for predicting network performance and position location using multiple table lookups
US20040259554A1 (en) 2003-04-23 2004-12-23 Rappaport Theodore S. System and method for ray tracing using reception surfaces
US7277401B2 (en) 2003-04-25 2007-10-02 Motorola, Inc. Reduced order model node location method for multi-hop networks
JP4483202B2 (en) 2003-05-28 2010-06-16 日本電気株式会社 Monitoring terminal equipment
JP2004355165A (en) 2003-05-28 2004-12-16 Nec Corp Monitor terminal equipment
US7075890B2 (en) 2003-06-06 2006-07-11 Meshnetworks, Inc. System and method to provide fairness and service differentation in ad-hoc networks
US7460865B2 (en) 2003-06-18 2008-12-02 Fisher-Rosemount Systems, Inc. Self-configuring communication networks for use with process control systems
WO2005004420A3 (en) 2003-07-02 2005-05-06 Ember Corp Method and apparatus for routing data in a personal area network
US7701858B2 (en) 2003-07-17 2010-04-20 Sensicast Systems Method and apparatus for wireless communication in a mesh network
US7376087B2 (en) 2003-08-13 2008-05-20 Tropos Networks, Inc. Method and apparatus for monitoring and displaying routing metrics of a network
US8248968B2 (en) 2003-10-03 2012-08-21 Apple Inc. Method and apparatus for providing mobile inter-mesh communication points in a multi-level wireless mesh network
US7233127B2 (en) * 2003-10-17 2007-06-19 Research In Motion Limited Battery management system and method
US7809020B2 (en) 2003-10-31 2010-10-05 Cisco Technology, Inc. Start of packet detection for multiple receiver combining and multiple input multiple output radio receivers
US7468969B2 (en) 2003-11-07 2008-12-23 Interdigital Technology Corporation Apparatus and methods for central control of mesh networks
JP2005150824A (en) 2003-11-11 2005-06-09 Hitachi Ltd Sensor with radio function
WO2005050894A3 (en) 2003-11-17 2005-10-27 Rockwell Automation Tech Inc Distributed modular input/output system with wireless backplane extender
JP4185853B2 (en) 2003-11-28 2008-11-26 株式会社日立コミュニケーションテクノロジー Wireless system, server, and the mobile station
US20050149940A1 (en) 2003-12-31 2005-07-07 Sychron Inc. System Providing Methodology for Policy-Based Resource Allocation
US7818018B2 (en) 2004-01-29 2010-10-19 Qualcomm Incorporated Distributed hierarchical scheduling in an AD hoc network
US7424698B2 (en) 2004-02-27 2008-09-09 Intel Corporation Allocation of combined or separate data and control planes
US20050201349A1 (en) 2004-03-15 2005-09-15 Honeywell International Inc. Redundant wireless node network with coordinated receiver diversity
CN1934881A (en) 2004-03-25 2007-03-21 捷讯研究有限公司 Wireless access point methods and apparatus for reduced power consumption and cost
US7881239B2 (en) 2004-03-27 2011-02-01 Dust Networks, Inc. Low-powered autonomous radio node with temperature sensor and crystal oscillator
US7529217B2 (en) 2004-03-27 2009-05-05 Dust Networks, Inc. Low-power autonomous node for mesh communication network
US20050223110A1 (en) 2004-03-30 2005-10-06 Intel Corporation Heterogeneous building block scalability
US20050238058A1 (en) 2004-04-26 2005-10-27 Peirce Kenneth L Jr Synchronization of upstream and downstream data transfer in wireless mesh topologies
US7042352B2 (en) 2004-05-27 2006-05-09 Lawrence Kates Wireless repeater for sensor system
CN1985532B (en) 2004-06-04 2010-05-12 艾维诺·赛尔维若·麦迪拿·德·苏沙 Autonomous infrastructure wireless network, and system and method thereof
US7213489B2 (en) * 2004-06-10 2007-05-08 Nu-Kote International, Inc. Ink container opener with multiple inserts for different container types
US7620409B2 (en) 2004-06-17 2009-11-17 Honeywell International Inc. Wireless communication system with channel hopping and redundant connectivity
US7697893B2 (en) 2004-06-18 2010-04-13 Nokia Corporation Techniques for ad-hoc mesh networking
US7262693B2 (en) 2004-06-28 2007-08-28 Rosemount Inc. Process field device with radio frequency communication
US8929228B2 (en) 2004-07-01 2015-01-06 Honeywell International Inc. Latency controlled redundant routing
EP1766877A4 (en) 2004-07-09 2008-01-23 Interdigital Tech Corp Logical and physical mesh network separation
US8194655B2 (en) 2004-08-05 2012-06-05 Dust Networks, Inc. Digraph based mesh communication network
US7860495B2 (en) 2004-08-09 2010-12-28 Siemens Industry Inc. Wireless building control architecture
GB0418959D0 (en) 2004-08-25 2004-09-29 Nortel Networks Ltd Mesh network evaluation methods
US7053770B2 (en) 2004-09-10 2006-05-30 Nivis , Llc System and method for communicating alarm conditions in a mesh network
US7554941B2 (en) 2004-09-10 2009-06-30 Nivis, Llc System and method for a wireless mesh network
US7505734B2 (en) 2004-09-10 2009-03-17 Nivis, Llc System and method for communicating broadcast messages in a mesh network
US8752106B2 (en) 2004-09-23 2014-06-10 Smartvue Corporation Mesh networked video and sensor surveillance system and method for wireless mesh networked sensors
US7139239B2 (en) 2004-10-05 2006-11-21 Siemens Building Technologies, Inc. Self-healing control network for building automation systems
US20060095539A1 (en) 2004-10-29 2006-05-04 Martin Renkis Wireless video surveillance system and method for mesh networking
US7408911B2 (en) * 2004-11-08 2008-08-05 Meshnetworks, Inc. System and method to decrease the route convergence time and find optimal routes in a wireless communication network
US8223027B2 (en) 2004-11-24 2012-07-17 Robertshaw Controls Company Wireless tank monitoring system having satellite communications capability
US7327998B2 (en) 2004-12-22 2008-02-05 Elster Electricity, Llc System and method of providing a geographic view of nodes in a wireless network
US7680460B2 (en) 2005-01-03 2010-03-16 Rosemount Inc. Wireless process field device diagnostics
US7515608B2 (en) 2005-01-04 2009-04-07 Intel Corporation Methods and media access controller for mesh networks with adaptive quality-of-service management
US20060159024A1 (en) 2005-01-18 2006-07-20 Hester Lance E Method and apparatus for responding to node anormalities within an ad-hoc network
US7489282B2 (en) 2005-01-21 2009-02-10 Rotani, Inc. Method and apparatus for an antenna module
JP2006211375A (en) * 2005-01-28 2006-08-10 Matsushita Electric Ind Co Ltd Load distribution method in wireless ad hoc network
US20060193262A1 (en) 2005-02-25 2006-08-31 Mcsheffrey Brendan T Collecting and managing data at a construction site
US7899027B2 (en) 2005-03-23 2011-03-01 Cisco Technology, Inc. Automatic route configuration in hierarchical wireless mesh networks
US7809013B2 (en) 2005-03-24 2010-10-05 Intel Corporation Channel scanning
US7705729B2 (en) 2005-03-30 2010-04-27 Memsic, Inc. Surveillance system and method
US20060219861A1 (en) 2005-03-30 2006-10-05 Honeywell International Inc. Low-power surveillance sensor
US7801110B2 (en) 2005-03-31 2010-09-21 Toshiba America Research, Inc. Efficient detection and/or processing in multi-hop wireless networks
US20060227729A1 (en) 2005-04-12 2006-10-12 Honeywell International Inc. Wireless communication system with collision avoidance protocol
US7746866B2 (en) 2005-05-13 2010-06-29 Intel Corporation Ordered and duplicate-free delivery of wireless data frames
US7440436B2 (en) 2005-05-13 2008-10-21 Natural Lighting Systems, Inc. Self-organizing multi-channel mesh network
US7742394B2 (en) 2005-06-03 2010-06-22 Honeywell International Inc. Redundantly connected wireless sensor networking methods
US7848223B2 (en) 2005-06-03 2010-12-07 Honeywell International Inc. Redundantly connected wireless sensor networking methods
US8463319B2 (en) 2005-06-17 2013-06-11 Honeywell International Inc. Wireless application installation, configuration and management tool
US7406060B2 (en) 2005-07-06 2008-07-29 Nortel Networks Limited Coverage improvement in wireless systems with fixed infrastructure based relays
US7801094B2 (en) 2005-08-08 2010-09-21 Honeywell International Inc. Integrated infrastructure supporting multiple wireless devices
US20070030816A1 (en) 2005-08-08 2007-02-08 Honeywell International Inc. Data compression and abnormal situation detection in a wireless sensor network
US8705360B2 (en) 2005-09-06 2014-04-22 Samsung Electronics Co., Ltd. Stream control in a MIMO-enabled mesh network
US20070071006A1 (en) 2005-09-26 2007-03-29 Peter Bosch Delivery of communications services in developing regions
US20090222541A1 (en) 2005-11-08 2009-09-03 Nortel Networks Limited Dynamic sensor network registry
US20070147255A1 (en) 2005-12-23 2007-06-28 Ozgur Oyman Routing in wireless mesh networks
US20070160020A1 (en) 2006-01-05 2007-07-12 Robert Osann Interleaved wireless mesh network
US20070297366A1 (en) 2006-01-05 2007-12-27 Robert Osann Synchronized wireless mesh network
US20070183439A1 (en) 2006-01-05 2007-08-09 Osann Robert Jr Combined directional and mobile interleaved wireless mesh network
US20070184852A1 (en) 2006-01-17 2007-08-09 Johnson David W Method and system for location of objects within a specified geographic area
US7224642B1 (en) 2006-01-26 2007-05-29 Tran Bao Q Wireless sensor data processing systems
US9166812B2 (en) 2006-01-31 2015-10-20 Sigma Designs, Inc. Home electrical device control within a wireless mesh network
US7936681B2 (en) 2006-03-06 2011-05-03 Cisco Technology, Inc. Cross-layer design techniques for interference-aware routing configuration in wireless mesh networks
EP1994696A4 (en) 2006-03-06 2011-03-02 Rosemount Inc Wireless mesh networks
US7978725B2 (en) 2006-03-06 2011-07-12 Cisco Technology, Inc. Dynamic modification of contention-based transmission control parameters achieving load balancing scheme in wireless mesh networks
US7583625B2 (en) * 2006-04-06 2009-09-01 Broadcom Corporation Access point multi-level transmission power and protocol control based on the exchange of characteristics
US8116201B2 (en) * 2006-05-11 2012-02-14 Qualcomm Incorporated Routing in a mesh network
US7558622B2 (en) 2006-05-24 2009-07-07 Bao Tran Mesh network stroke monitoring appliance
US8103316B2 (en) 2006-09-29 2012-01-24 Rosemount Inc. Power management system for a field device on a wireless network
US7746289B2 (en) 2006-11-23 2010-06-29 Fibertower Corporation Point-to-multipoint antenna structure using multiple passive antennas
US8570922B2 (en) 2007-04-13 2013-10-29 Hart Communication Foundation Efficient addressing in wireless hart protocol
US8660108B2 (en) 2007-04-13 2014-02-25 Hart Communication Foundation Synchronizing timeslots in a wireless communication protocol
US20080273486A1 (en) 2007-04-13 2008-11-06 Hart Communication Foundation Wireless Protocol Adapter
US8325627B2 (en) 2007-04-13 2012-12-04 Hart Communication Foundation Adaptive scheduling in a wireless network
US8447367B2 (en) 2007-05-07 2013-05-21 Rosemount Tank Radar Ab Process measurement instrument adapted for wireless communication
US8014329B2 (en) * 2007-07-03 2011-09-06 Cisco Technology, Inc. Path selection and power management in mesh networks
US7957775B2 (en) * 2007-11-05 2011-06-07 International Business Machines Corporation Low battery notification service for wireless device users

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of EP2340667A4 *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2512256A (en) * 2014-02-25 2014-09-24 Cambridge Silicon Radio Ltd Mesh profiling
GB2512256B (en) * 2014-02-25 2015-04-15 Cambridge Silicon Radio Ltd Mesh profiling
DE102014012379A1 (en) * 2014-02-25 2015-08-27 Cambridge Silicon Radio Ltd. Mesh profiling
DE102014012379B4 (en) * 2014-02-25 2016-05-12 Qualcomm Technologies International, Ltd. Mesh profiling
US9489506B2 (en) 2014-02-25 2016-11-08 Qualcomm Technologies International, Ltd. Linking ad hoc networks
US9672346B2 (en) 2014-02-25 2017-06-06 Qualcomm Technologies International, Ltd. Object tracking by establishing a mesh network and transmitting packets
US9692538B2 (en) 2014-02-25 2017-06-27 Qualcomm Technologies International, Ltd. Latency mitigation
US9754096B2 (en) 2014-02-25 2017-09-05 Qualcomm Technologies International, Ltd. Update management
US9842202B2 (en) 2014-02-25 2017-12-12 Qualcomm Technologies International, Ltd. Device proximity
US20170064630A1 (en) * 2015-08-26 2017-03-02 International Business Machines Corporation Efficient usage of internet services on mobile devices

Also Published As

Publication number Publication date Type
EP2340667A2 (en) 2011-07-06 application
US9485649B2 (en) 2016-11-01 grant
US20110164512A1 (en) 2011-07-07 application
CA2733268A1 (en) 2010-04-01 application
EP2340667A4 (en) 2013-12-25 application
WO2010036885A3 (en) 2010-08-19 application
CN102165811B (en) 2014-07-30 grant
JP5383809B2 (en) 2014-01-08 grant
CN102165811A (en) 2011-08-24 application
JP2012507887A (en) 2012-03-29 application
WO2010036885A4 (en) 2012-03-08 application
EP2340667B1 (en) 2015-07-08 grant

Similar Documents

Publication Publication Date Title
Ye et al. PEAS: A robust energy conserving protocol for long-lived sensor networks
Marrón et al. TinyCubus: a flexible and adaptive framework sensor networks
US20080273486A1 (en) Wireless Protocol Adapter
US20070195702A1 (en) Link duration based routing protocol for multihop ad hoc networks
US20090010203A1 (en) Efficient Addressing in Wireless Hart Protocol
Alizai et al. Bursty traffic over bursty links
US8767627B2 (en) Path control method for multihop wireless network
US20090010204A1 (en) Support for Network Management and Device Communications in a Wireless Network
Sarr et al. Bandwidth estimation for IEEE 802.11-based ad hoc networks
Ovsthus et al. An industrial perspective on wireless sensor networks—a survey of requirements, protocols, and challenges
US20020097696A1 (en) Apparatus, and associated method, for dynamically selecting frequency levels upon which to define communication channels in a radio communication system
US7376087B2 (en) Method and apparatus for monitoring and displaying routing metrics of a network
US20080279155A1 (en) Adaptive Scheduling in a Wireless Network
US20090046732A1 (en) Routing Packets on a Network Using Directed Graphs
US7327697B1 (en) Method and system for dynamically assigning channels across multiple radios in a wireless LAN
US5922051A (en) System and method for traffic management in a network management system
US20090046675A1 (en) Scheduling Communication Frames in a Wireless Network
US20080247327A1 (en) Identifying correlations within wireless networks
US20090245270A1 (en) Method and System of Updating Routing Information in a Communications Network
US20130024560A1 (en) Centrally driven performance analysis of low power and lossy networks
US20090059814A1 (en) Configuring and Optimizing a Wireless Mesh Network
US20130022084A1 (en) Dynamic common broadcast schedule parameters for overlaying an independent unicast schedule
US20030033404A1 (en) Method for automatically monitoring a network
US20110255418A1 (en) Method and System for Detecting Failures of Network Nodes
US20060171344A1 (en) Wireless routing implementation

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: 09816902

Country of ref document: EP

Kind code of ref document: A2

WWE Wipo information: entry into national phase

Ref document number: 12735074

Country of ref document: US

ENP Entry into the national phase in:

Ref document number: 2733268

Country of ref document: CA

ENP Entry into the national phase in:

Ref document number: 2011529254

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2011529254

Country of ref document: JP

NENP Non-entry into the national phase in:

Ref country code: DE

ENP Entry into the national phase in:

Ref document number: PI0919297

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20110324