Source: http://www.google.com/patents/US8160574?dq=5998925
Timestamp: 2015-04-25 21:58:02
Document Index: 635754963

Matched Legal Cases: ['Application No. 2004100794746', 'Application No. 2004', 'Application No. 2004100794746', 'Application No. 200610086707', 'Application No. 200710301629', 'Application No. 2006', 'Application No. 2004', 'Application No. 2004100794746', 'Application No. 200610086707', 'Application No. 2004100794746']

Patent US8160574 - Wireless architecture utilizing geo-referencing - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA wireless communication system for use in a process control environment includes a reference node adapted to determine geographic positions of at least some of the reference node, a base node, and a field node and determine RF power settings of transceivers attached to the reference node, the base node,...http://www.google.com/patents/US8160574?utm_source=gb-gplus-sharePatent US8160574 - Wireless architecture utilizing geo-referencingAdvanced Patent SearchPublication numberUS8160574 B1Publication typeGrantApplication numberUS 11/644,758Publication dateApr 17, 2012Filing dateDec 22, 2006Priority dateJun 17, 2005Also published asCN101206479A, CN101206479B, DE102007061239A1, US20120076007Publication number11644758, 644758, US 8160574 B1, US 8160574B1, US-B1-8160574, US8160574 B1, US8160574B1InventorsJoe NelsonOriginal AssigneeFisher-Rosemount Systems, Inc.Export CitationBiBTeX, EndNote, RefManPatent Citations (109), Non-Patent Citations (42), Referenced by (1), Classifications (24), Legal Events (2) External Links: USPTO, USPTO Assignment, EspacenetWireless architecture utilizing geo-referencing
US 8160574 B1Abstract
A wireless communication system for use in a process control environment includes a reference node adapted to determine geographic positions of at least some of the reference node, a base node, and a field node and determine RF power settings of transceivers attached to the reference node, the base node, and the field node based on the position of determined geographic positions. Additionally, the reference node is adapted to determine RF noise level at a plurality of locations within the process control environment at a plurality of times and to adjust the RF power settings based on the determined RF noise levels. The reference node may be implemented on a hand-held device.
a base node, a field node, a reference node and a host;
the base node communicatively coupled to the host;
the base, field and reference nodes each comprising a wireless conversion unit and a wireless transceiver;
the wireless transceivers of the base, the field and the reference nodes effecting wireless communications amongst the base, field and reference nodes;
the field node comprising at least one field device providing process control data;
the reference node comprising a geographical positioning apparatus to determine geographical position of the reference node;
an RF noise measurement apparatus located on at least one of the base, field and reference nodes, wherein the RF noise measurement apparatus is to determine RF ambient noise levels at the RF noise measurement apparatus over a predetermined time period; and
a power settings apparatus located on at least one of the base and reference nodes, wherein the power setting apparatus is to
determine the geographic position of each of the base and field nodes relative to the reference node, and
determine RF power settings of the wireless transceivers of at least one of the base, the field and the reference nodes using the geographic position of the at least one of the base and field nodes and using the RF ambient noise levels determined by the RF noise measurement apparatus.
2. The wireless communication network of claim 1, wherein the reference node is implemented using a handheld device.
3. The wireless communication network of claim 1, wherein the RF noise measurement apparatus is further to generate an RF ambient noise predictive function predicting the RF ambient noise level as a function of at least one of: (1) time of day, (2) day of week, and (3) day of month.
4. The wireless communication network of claim 3, wherein the power settings apparatus is further to adjust RF power settings of the wireless transceivers of at least one of the base, the field and the reference nodes using the RF ambient noise predictive function.
5. The wireless communication network of claim 1, wherein:
the RF noise measurement apparatus is to measure RF ambient noise levels at a plurality of locations of the reference node;
the power setting apparatus is to measure and record the distance of the reference node at each of the plurality of locations from at least one of the base and field nodes; and
the power setting apparatus determines an optimal location for the reference node based on the RF ambient noise levels at the plurality of locations and distance between the reference node at each of the plurality of locations and at least one of the base and field nodes.
6. The wireless communication network of claim 5, wherein the power setting apparatus is further to determine geographic location of at least one of the base and field nodes based on the RF ambient noise levels at the plurality of locations and the distance between the reference node at each of the plurality of locations and the at least one of the base and field nodes.
7. The wireless communication network of claim 1 further comprising a repeater node comprising a wireless conversion unit and a wireless transceiver, the repeater node effecting wireless communications amongst the base, field and environmental nodes.
8. The wireless communication network of claim 1 wherein the reference node further comprises a plurality of sensor devices, each of the plurality of sensor devices providing data selected from a group consisting of temperature, barometric pressure, humidity, rainfall and radio frequency ambient noise.
9. The wireless communication network of claim 1 wherein the at least one field device of the field node comprises at least one of a HART protocol device and a Fieldbus� protocol device.
10. The wireless communication network of claim 1 further comprising a plurality of environmental nodes strategically placed about a process area for communicating environmental data for different locations within the process area.
11. The wireless communication network of claim 1 wherein the base, environmental and field nodes form at least one of a mesh communications network and a point-to-point communications network.
12. The wireless communication network of claim 11, wherein the power setting apparatus is further to determine a network configuration based on the RF ambient noise levels at a plurality of locations and the distance of the reference node at each of the plurality of locations from at least one of the base and field nodes.
13. The wireless communication network of claim 12, further comprising a switch device to convert the base, environmental and field nodes from a mesh communications network to a point-to-point communications network and vice versa.
14. The wireless communication network of claim 1, wherein the host comprises a monitor, the host being programmed to provide a topology screen display on the monitor illustrating wireless communications between each of the base, field and reference nodes of the network.
15. The wireless communication network of claim 14, wherein the topology screen display also illustrates structural features of a process area in which the base, field and environmental nodes are disposed.
16. The wireless communication network of claim 14, wherein the topology screen display also illustrates strength of RF reception at some of the base node, the reference node and the field node.
17. The wireless communication network of claim 1, wherein the host comprises a monitor, the host being programmed to provide a tabular screen display on the monitor listing a hop count between each of the field and environmental nodes and the base node of the network.
18. The wireless communication network of claim 1, wherein the power settings apparatus is to adjust a routing table of the base, the field and the reference nodes using the RF ambient noise levels.
19. A method for monitoring a wireless process control network, the method comprising:
receiving a geographic position data from a reference node;
receiving data indicative of a radio frequency (RF) ambient noise level from one or more environmental field devices of the reference node;
wirelessly transmitting the data indicative of the RF ambient noise level and the geographic position data to a base node communicatively attached to a host;
interpreting the data indicative of the RF ambient noise level and the geographic position data at the host,
sending a command from the host to the base node to adjust at least one operating parameter of the wireless network based on the data indicative of the RF ambient noise level and the geographic position data, and
wirelessly transmitting the command from the base node to at least one field node attached to a field device.
20. The method of claim 19, further comprising receiving, from the one or more environmental field devices, data selected from a group consisting of temperature, barometric pressure, humidity, and rainfall.
21. The method of claim 20, wherein the geographic position data further includes geographic position of at least one of the base node, the reference node and the field node.
22. The method of claim 21, wherein the data indicative of the RF ambient noise level includes data indicative of RF ambient noise levels at the reference node over a pre-determined period of time.
23. The method of claim 19, wherein the operating parameter is an RF power setting for each of the at least one field node.
24. The method of claim 19, wherein the operating parameter is a routing table for the wireless network.
This application is a continuation-in-part of U.S. patent application Ser. No. 11/156,215, filed Jun. 17, 2005 and entitled �Wireless Architecture and Support for Process Control Systems,� now U.S. Pat. No. 7,436,797 (which is hereby expressly incorporated by reference herein). This application is also related to U.S. patent application Ser. No. 10/464,087, filed Jun. 18, 2003 and entitled �Self-Configuring Communication Networks for use with Process Control Systems,� now U.S. Pat. No. 7,460,865 (which is hereby expressly incorporated by reference herein).
As used herein, the term �field device� encompasses these devices, as well as any other device that performs a function in a control system. In any event, field devices may include, for example, input devices (e.g., devices such as sensors that provide status signals that are indicative of process control parameters such as, for example, temperature, pressure, flow rate, etc.), as well as control operators or actuators that perform actions in response to commands received from controllers and/or other field devices.
More, recently, field devices that are part of hybrid systems become available that superimpose digital data on the current loop used to transmit analog signals. One such hybrid system is known in the control art as the Highway Addressable Remote Transducer (HART) protocol. The HART system uses the magnitude of the current in the current loop to send an analog control signal or to receive a sensed process variable (as in the traditional system), but also superimposes a digital carrier signal upon the current loop signal. The HART protocol makes use of the Bell 202 Frequency Shift Keying (FSK) standard to superimpose the digital signals at a low level on top of the 4-20 mA analog signals. This enables two-way field communication to take place and makes it possible for additional information beyond just the normal process variable to be communicated to/from a smart field instrument. The HART protocol communicates at 1200 bps without interrupting the 4-20 mA signal and allows a host application (master) to get two or more digital updates per second from a field device. As the digital FSK signal is phase continuous, there is no interference with the 4-20 mA signal.
Thus, due to the costs associated with installing a wireless I/O communication network (e.g., site surveys, expert configuration, etc.), and the relatively little amount of faith that current process control system operators have in wireless communications, wireless I/O communication networks are often cost prohibitive for what they provide, particularly for relatively large process control systems such as those typically used in industrial applications.
In a refinement, one or more environmental nodes are used to control and optimize the operation of the wireless communication network. The environmental node(s) are linked to field �environmental� devices providing signals indicative of one or more environmental factors such as temperature, barometric pressure, humidity, rainfall and radio frequency (RF) ambient noise, amongst other environmental factors that could alter the operation of the network.
In another refinement, the network includes a main controller linked to a wireless card. The wireless card is in communication with an optical repeater node which, in turn, is in communication with a field node. The field node is linked to a plurality of field devices. In another refinement, the repeater node is eliminated. In another refinement, an environmental node and environmental detection devices as discussed above are incorporated with or without one or more repeater nodes. In a further refinement, the field and environmental nodes include a plurality of ports for communication with the field devices.
In an embodiment, a process control wireless communication network is disclosed which comprises a base node, a field node, an environmental node and a host. The base node is communicatively coupled to the host. The base, field and environmental nodes each comprise a wireless conversion unit and a wireless transceiver. The wireless transceivers of the base, the field and environmental nodes effect wireless communication among the base, field and environmental nodes. The field node comprises at least one field device providing process controlled data. The environmental node comprises at least one field device providing data regarding environmental factors that may affect operation of the wireless communication network.
In another refinement, at least some of the field devices are HART protocol devices. In another refinement, at least some of the field devices are FIELDBUS� protocol devices.
In another refinement, a wireless communication network comprises a base node, a field node, a reference node and a host. The base node is communicatively coupled to the host. The base, field and reference nodes each comprise a wireless conversion unit and a wireless transceiver. The wireless transceivers of the base, the field and the reference nodes effect wireless communications amongst the base, field and reference nodes. The field node comprises at least one field device providing process control data. The reference node comprises a geographical positioning apparatus adapted to determine geographical position of the reference node. The reference node also comprises a RF power settings apparatus located on at least one of the base and reference nodes. The RF power setting apparatus is adapted to: determine the geographic position of each of the base and field nodes relative to the reference node, and determine RF power settings of the wireless transceivers of at least one of the base, the field and the reference nodes using the geographic position of the at least one of the base and field nodes.
In another refinement, a method for monitoring a wireless process control network comprises: receiving a geographic position data from a reference node; receiving environmental data from one or more environmental field devices of the reference node; wirelessly transmitting the environmental data and the geographic position data to a base node communicatively attached to a host; interpreting the environmental data and the geographic position data at the host, sending a command from the host to the base node to adjust at least one operating parameter of the wireless network based on the environmental data and the geographic position data, and wirelessly transmitting the command from the base node to at least one field node attached to a field device.
Other advantages and features will be come apparent upon reading the following detailed description and independent claims, and upon reference to the accompanying drawings.
For more complete understanding of this disclosure, reference should not be made to the embodiments illustrated in greater detail in the accompanying drawings and described below by way of examples. In the drawings:
FIG. 7 is an example of a topology screen display created by a wireless network analysis tool illustrating the wireless communications within a graphic of a plant layout to enable an operator or other user to view the specific communications occurring within the wireless communication network and potential physical obstacles presented by the plant layout;
FIG. 9 is an example screen display created by a wireless network analysis tool illustrating graphical displays of information about the wireless communications between different devices within the wireless communication system to enable a user or operator to analyze the operational capabilities and parameters of the wireless communication network;
FIG. 10 is a block diagram of a wireless communication device that implements a HART communication protocol wirelessly using a second communication protocol, e.g. the EMBER� protocol;
FIG. 11 is a combined block and schematic diagram of a wireless communication network within a portion of a process environment designed in accordance with this disclosure;
FIG. 12 is a block diagram of a process for initializing a wireless communication system formed of a cluster of wireless communication devices having a routing table and a power setting table;
FIG. 13 is an example of a screen display illustrating a process environment layout with wireless communication devices forming a wireless communication system in accordance with this disclosure;
FIG. 14 is a table indicating a distance calculated between wireless communication devices of a wireless communications system as determined by an initialization process in accordance with this disclosure;
FIG. 15 is an example of a geometric topology screen display created by the process of FIG. 12;
FIG. 16 is an example of a topology screen display illustrating the wireless communications within a graphic of a plant layout, and showing a wireless communication system formed in the layout of FIG. 13 and having node paths as set forth in FIG. 15, but for clarity reasons not showing the differences in paths, path directionality, and path strength between the nodes as shown in FIG. 15;
FIG. 17 is an example screen display presented in the tabular form of a cost matrix illustrating the number of hops or the hop count between each wireless communication device within the wireless communication system of FIG. 15;
FIG. 18 is a block diagram of a process for adjusting the power setting table or routing table in response to changes in measured environmental conditions in accordance with this disclosure;
FIG. 19 is an example screen display illustrating graphical displays of information about the wireless communications system, including the connectivity and the RF noise level at various wireless communication devices;
FIG. 20 is an example of a power setting table for wireless communication devices in a wireless communication system; and
FIGS. 21 and 22 are examples of a routing table for a network cluster under a first RF noise level condition and an adjusted routing table under a second RF noise level condition, respectively, where both routing tables have at most two hops between nodes.
FIG. 1 illustrates a typical hardwired distributed process control system 10 which includes one or more process controllers 12 connected to one or more host workstations or computers 14 (which may be any type of personal computer or workstation). The process controllers 12 are also connected to banks of input/output (I/O) devices 20, 22 each of which, in turn, is connected to one or more field devices 25-39. The controllers 12, which may be, by way of example only. DeltaV� controllers sold by Fisher-Rosemount Systems, Inc., are communicatively connected to the host computers 14 via, for example, an Ethernet connection 40 or other communication link. Likewise, the controllers 12 are communicatively connected to the field devices 25-39 using any desired hardware and software associated with, for example, standard 4-20 mA devices and/or any smart communication protocol such as the Fieldbus or HART protocols. As is generally known, the controllers 12 implement or oversee process control routines stored therein or otherwise associated therewith and communicate with the devices 25-39 to control a process in any desired manner.
On the other hand, each of the field nodes 68 is generally coupled to one or more devices within the process plant environment and, generally speaking, is coupled to one or more field devices, illustrated as field devices 80-85 in FIG. 2. The field devices 80-85 may be any type of field devices including, for example, four-wire devices, two-wire devices, HART devices, Fieldbus devices, 4-20 mA devices, smart or non-smart devices, etc. For the sake of illustration, the field devices 80-85 of FIG. 2 are illustrated as HART field devices, conforming to the HART communication protocol. Of course, the devices 80-85 may be any type of device, such as a sensor/transmitter device, a valve, a switch, etc. Additionally, the devices 80-85 may be other than traditional field devices such as controllers. I/O devices, work stations, or any other types of devices.
Using the communication system 60 of FIG. 2, an application running on the workstation 70 can send packets of data to and receive packets of wireless data from the wireless conversion unit in the form of the wireless base card 74 residing in a standard controller 75 at the base node 62. This controller 75 may be, for example, a DeltaV controller and the communications may be the same as with a standard I/O card via the Ethernet connection to the DeltaV controller. The I/O card in this case includes the wireless base card 74, though as far as the controller and PC Application goes, it appears as a standard HART I/O card.
Turning to FIGS. 3 and 4, it is anticipated that the wireless network 60 of FIG. 2 may need to be switched back and forth between mesh and point-to-point communication modes. FIG. 3 illustrates a network 100 with a base node 101 in communication with repeater nodes 102 a, 102 b, 102 c. The repeater nodes 102 a-102 c are, in turn, in communication with a plurality or a cluster of either environmental nodes, field nodes or combination of the two as shown generally at 104. A point-to-point wireless communication system for FIG. 3 is shown in solid line while an alternative mesh configuration is shown in phantom line.
Turning to FIG. 4, a switch device 105 is shown schematically which may be disposed in the base node 101 in addition to the wireless transceiver 76. The switch 105 is intended to convert the network 100 from a mesh wireless network as shown by the phantom lines in FIG. 3 to a point-to-point wireless network as shown by way of example in the solid line of FIG. 3. Of course, the point-to-point communications can be configured in any manner and the solid lines shown in FIG. 3 are but one example. The switch device 105 as shown in FIG. 4 can include an electronic switch element 106 that shifts the device 105 between a mesh wireless transceiver 76 a and a point-to-point wireless transceiver 76 b. As noted above, the disclosed network 60 includes a base node 62 and host 70 that may be programmed to provide a variety of graphical interfaces that will be useful to the operator. Examples of such graphical interfaces are shown in FIGS. 5-9. Turning to FIG. 5, a geometric topology screen display 110 is disclosed which illustrates a wireless network between a base node BA and a plurality of other nodes which may be one or more repeater nodes, field nodes and environmental nodes numbered in FIG. 5 as 03, 04, 05, 07, 08, 09, 10 (0A), and 11 (0B). The topology display 110 of FIG. 5 illustrates a successful communication between two nodes with a solid line, one example of which is the communication between the base node BA and the node 7. A successful communication in one direction only is illustrated by a line with cross hatches, one example of which is the line between the nodes 03 and 10 (0A). An unsuccessful communication is indicated by a dashed or phantom line, one example of which is the lack of communication illustrated by the dashed line between nodes 05 and 11 (0B). FIG. 5 also illustrates the �hop count� between nodes. For example, looking at nodes 04 and 07, the dashed or phantom line between nodes 04 and 07 of FIG. 5 make it clear that there is no direct wireless communication between nodes 04 and 07 while there is communication between nodes 04 and 05 and one-way communication between nodes 05 and 07. Thus, for one-way communication between nodes 04 and 07, there is a hop count of 2 (node 04 to node 05 and node 05 to node 07). Alternatively, for two-way communication between nodes 04 and 07, there is also a hop count of 2 (node 07 to node 03 and node 03 to node 04). Obviously, the lower the hop count the better and the more reliable the communication.
Turning to FIG. 10, it will be noted that many of the devices 80-85 shown in FIG. 2 would be HART field devices, and therefore the field node 68 will be sending a HART signal to either a repeater node 64 or directly to a conversion node 140 which, in the embodiment shown in FIG. 10, may be a separate element or may comprise part of the base node 62. A HART signal may also be sent from an environmental node 66 as shown. The conversion node 140 includes software to convert the HART signal to a different protocol, e.g., the EMBER protocol used with low-power wireless networking software and radio technology. See http://www.ember.com/. Of course, other protocols are available and will be apparent to those skilled in the art. The conversion node 140 converts the HART signal to an EMBER data packet at 141. The data packet includes an origin indication 142 and a destination indication 143 which is determined by software either in the base node 62 or in the conversion node 140. The HART message 144 is sandwiched between the origin data 142 and destination data 143. The signal is then sent to a routing node 145 which determines, from the destination information 143, which object device 146 to send the data to. The routing node 145 then transmits the data through one or more repeaters 64 and/or field nodes 68 to the object device 146. One type of software that could be used to convert the field device signal from one protocol (HART) to another protocol is the JTS software sold by Acugen (http://www.acugen.com/jts.htm).
Generally speaking process control environments are less dynamic regarding initial installation and permanent location of field devices such as smart valves, etc. Therefore, it may be possible to determine an initial configuration of wireless nodes attached to field devices based on the initial location of the field devices, where such node configurations can be downloaded to the wireless nodes. Because most of the wireless nodes available in the market support a number of different configuration settings, including pathway routing tables and transmission power level settings, the initial configuration setting may be updated over time based on revised locations, changes in RF noise signatures over time, or other environmental determinant factors.
An alternate embodiment of the communication network 60 that utilizes the information regarding the locations of various wireless nodes to determine configuration settings of the wireless nodes and of the network is illustrated in FIG. 11. Specifically, FIG. 11 illustrates a modified wireless communication network 200 (with components similar to those of network 60 bearing the same reference numbers) that includes a reference node 210 including a geographic positioning apparatus that may be used to determine geographic position of the reference node 210 with respect to a plurality of other nodes. The communication network 200 may also include one or more base nodes 62, one or more repeater nodes 64, one or more environment nodes 66 (illustrated in FIG. 11 as 66 a and 66 b) and one or more field nodes 68 (illustrated in FIG. 2 as nodes 68 a, 68 b and 68 c). The functioning of these nodes is described in further detail in FIG. 2 above.
The reference node 210 may be a portable node, e.g., a handheld device, capable of being located at various positions in the wireless communication network 200. The reference node 210 may include a transceiver 212 that may be used to communicate with one or more of the various wireless nodes located in the communication network 200 and a geographic positioning system (GPS) transceiver 214 that may be used to communicate with a satellite providing geographic positioning signal to the reference node 210. A geographic positioning apparatus 214 on the reference node 210 may be used to determine the location of the reference node 210 and one or more of the other communication nodes in the communication network 200. A power setting apparatus 216 on the reference node 210 may be used to determine configuration settings of the one or more of the other communication nodes in the network 200.
Note that while in the illustrated embodiment of the communication network 200 the geographic positioning apparatus 214 and the power setting apparatus 216 are located on the reference node 210, in an alternate embodiment, the geographic positioning apparatus 214 and the power setting apparatus 216 may be located at some alternate location on communication network 200, such as at any of the other nodes such as the base node 62 for the host 70, the repeater node 64 or any of the other nodes 66, 68, etc. It may be advantageous to locate the geographic positioning apparatus 214 and the power setting apparatus 216 in the reference node 214 as the reference node 210 may be a portable node that may be easily replaced or updated with newer software, etc.
The geographic positioning apparatus 214 may be implemented by a GPS program stored on the memory of the reference node 210. Such a GPS program may be activated every time the location of the reference node 210 is changed. Alternatively, such a GPS program may register with a GPS satellite at every predetermined interval to determine the coordinates of the reference node 210. In some examples, the reference node 210 may also provide manual control for overriding automatic GPS registration. Further upon establishing a communication link with other nodes, the GPS program of the reference node 210 may be remotely controlled to set the conditions, frequency, etc. for registering with a GPS satellite. This control may also include, for example, synchronizing reference node registration with other nodes or synchronizing reference node registration with processes existing in a processing environment.
The power setting apparatus 216 may be implemented by a program stored on the memory of the reference node 210. The power setting apparatus 216 may be capable of determining the geographic position of the reference node 210 based on the GPS signal from the geographic positioning apparatus 214. Further, the power setting apparatus 216 is coupled to receive a signal from a sensor apparatus 218 of the reference node 210. The sensor apparatus 218 may be an RF noise measurement apparatus, for example, capable of measuring RF noise levels at the reference node 210. In the example of an RF noise measurement apparatus, in response to the data from the sensing apparatus 218, the power settings apparatus 216 may determine RF power settings of the reference node, base node, and/or field node to counteract changes in the RF noise level. Such information may be recorded in a power settings table, or other form in the memory, and then communicated to each of the nodes (base, field, reference, etc.) of the network 200 for setting power policy.
In some examples, the power setting apparatus 216 is adapted to measure and record the distance of the reference node 210 to other nodes. The distance may be derived from the GPS data of the geographic positioning apparatus 214. The power setting apparatus 216 may determine an optimal location for the reference node, base node, field nodes, etc. based on the RF noise levels measured at each of a plurality of locations and the distances between nodes.
The power setting apparatus 216 may also provide the functionality of a network configuration switch, such as the switch device 105. For example, based on measured RF noise levels at a plurality of locations and distances between locations, the power setting apparatus 216 may determine whether the nodes of the network 200 should operate as a mesh communication network or a point-to-point communication network.
The RF noise measurement apparatus 218 may be programmed to determine RF noise levels over a period of time that may be preset or adjusted during operation. The power setting apparatus 216 may be programmed to adjust the power settings of the transceivers of the nodes of the network based on the RF noise level data gathered over time. For example, power settings for each node may be adjusted throughout the day, or over a weekend, etc. to compensate for actual or predicted changes in RF noise level. That is, in some examples, the RF noise measurement apparatus 218 may be adapted to produce an RF noise predictive function based on previously recorded RF noise level data. The predictive function may for example predict increases in RF levels that occur each day at sun rise. With expanding the RF data collection window to longer periods of time, the predictive function may further predict when each day that sun rise is expected, as that time changes throughout the year. Of course, this is an example, the predictive function may be programmed to predict RF level based any number of parameters that can be correlated to changes in measured RF levels. Predictive values may be based on any unit of time measure, e.g., time of day, day or week, day of month, etc.
In some examples, predictive values may be based on a time value that is synchronized to or triggered by a particular event, such as a time value based on a clock that starts with a particular processing operation. In a processing environment, for example, certain events like a unit shutdown or turn-around may alter RF noise level patterns in predictive ways, but the timing for these changes would be correlated to (and thus based on) the timing of the event and not necessarily correlated to a particular time of day, week, month, etc.
Although RF noise is discussed in the examples, the measurement apparatus 218 may include a plurality of sensor devices, such as those of an environmental node as described above, including a sensors of temperature, barometric pressure, humidity, and rainfall, or the measurement apparatus 218 may include any one of these sensor devices. Data from such sensors may be used in setting power levels for the transmitters at various nodes in the network, e.g., based on the measurement of RF frequency ambient noise. In some examples, the sensor data may be used to set the routing tables for the wireless communication system, thus establishing the cluster of nodes and routing paths from the nodes in the wireless communication system. Of course, the data from the sensors may be used for decisional control unrelated to RF frequency measurement.
FIG. 12 illustrates a flowchart of a power setting program 250 to determine power setting of the various transceivers used in the network 200. As with the apparatuses 212-218, the power setting program 250 may be implemented on any node of the network 200. In an implementation, the power setting program 250 may be implemented on the power setting apparatus 216 in conjunction with GPS transceiver 214 and the sensor apparatus 218 located on the reference node 210. For explanation purposes, the program 250 will be explained in reference to FIGS. 13-17.
A block 252 performs initial loading of a plant layout map that identifies the different processing locations, units, etc. within the plant. FIG. 13 shows an example plant layout map 254 with various locations labeled. The block 252 then binds the plant layout map to a GPS coordinate system defined by a series of GPS reference points, marked by Geo2, Geo2, Geo3, and Geo4, that have known or measurable longitude, latitude, and altitude coordinates. As shown in FIG. 13, these GPS reference points may set the boundaries within which a reference node may be placed for measuring optimal positions for nodes on a network, RF noise levels, and distances between nodes.
With the layout data loaded and the GPS coordinates defined, a block 256 begins georeferencing various reference nodes, such as the nodes labeled BA, 01, 02, 03, 04, 05, 06, 08, 09, BA, 11, and 12. The block 256 may register one node at a time with the GPS satellite through the GPS transceiver. The block 256 may compare the GPS data received from the GPS satellite to stored data from other nodes to determine a distance between the present position of the reference node and the remaining other nodes in the network. Alternatively, the distance between nodes may be determined based on measured signal strength from other nodes and the inverse square law. For example, each node may be programmed to periodically transmit node specific identifiers, either through the use of an encoded node identifier information on the transmitted signal, through different nodes being allotted different time windows to transmit, or through other techniques. The transceiver 212 may receive a signal and identify the source node, e.g., though decoding or time division identification, and measure signal strength from which the distance between the reference node 210 and the transmitting mode may be determined.
FIG. 14 illustrates a tabular form that may be produced from program 250 and which lists the distances between nodes on a network.
Once registered, a block 258 may measure RF noise levels at the reference node 210, recording that data locally at the reference node 210 and/or transmitting that data for centralized recording at a host machine, such as machine 70.
If the reference node includes environmental condition sensors, block 260 measures and records those conditions. As with the other functional control units illustrated within the example reference node 210 of FIG. 12, the environmental sensor may be located exterior to the reference node, for example, at an environmental node within the network. From here, a block 262 determines if additional reference node observations are to be measured, in which case the program 250 returns to block 256. If the block 256 is programmed to measure georeference only one node at a time, the block 262 can determine if any remaining nodes (e.g., nodes BA or 01-12 of FIG. 13) must be georeferenced. If no additional observations are needed, the program 250 passes control to block 264.
Block 264 determines a power setting table based on the data measured at blocks 256-260 to develop a power settings for the nodes on the network. The block 264 may develop those power settings based on actual RF noise levels or RF noise predictive functions, determined at the block 264 from the data of block 258. The block 264 may also determine the network configuration type, for example mesh communication network or point-to-point configuration network.
The block 264 may execute a power setting algorithm that selectively adjusts output power at each node, collectively or individually, while measuring the effect on network operation. For example, the block 264 may cycle output power at the nodes while simultaneously measuring the resulting total node count and total hop count for the network. These total values may be compared to total values measured at other power settings to determine an optimum power setting given an acceptable network coverage area and minimal total hop count. Particular regions with a plant layout may be of higher priority than others, so the comparisons at different power settings may be weighted as desired. A power setting table is created from these comparisons. Prior to, during, or after power setting, the block 264 may determine the routing table, reflecting a desired network path for the wireless communications network. The above are example descriptions of the instructions that may be executed by the block 264. The block 264 may be implemented using other algorithms and techniques to form or modify the power setting table and routing table.
These determinations from the block 264 are communicated to the nodes of the network by block 266. For example, if environmental conditions are measured by a measurement apparatus on a remote node, such as the reference node 210 or environmental node 66, then a power settings apparatus at a centralized controller station, such as a base node, may calculate a power setting table for all the nodes, thus identifying power levels and power level changes across a given time window. After initialization of the network via program 250, the centralized controller, through block 266, may communicate the calculated power setting table to each of the nodes for local storage and power control.
In the illustrated example, the block 264 may be capable of calculating a routing table in addition to the power setting table. The routing table pathway defines a network cluster from among the georeferenced nodes and more specifically the possible paths from each node to each other node. A controller may identify and set a network configuration (e.g., mesh or point-to-point communication) for a cluster of nodes based on the measured RF noise levels or other environmental data, power settings, and measured distances between nodes, whether that configuration is identified through a routing table. The block 266 may communicate the calculated routing table to each of the nodes for local storage and use in wireless communications.
FIG. 15 provides a geometric topology screen display 300 of a network cluster defined for the plant layout map 254. After georeferencing each of the nodes as shown in FIG. 13, the block 264 in defining the power settings and routing table, identifies a cluster 302 (shown in FIG. 16) portion of the plant layout map 254 for forming a communication network. In the illustrated example, that cluster 302 is formed of the nodes BA, 01, 02, 03, 04, 05, 08, 09, and 12 and in a mesh communication network. Nodes 06 and 11 have been excluded from the network by the block 264, for example due to being capable of sending or receiving a signal to at least one of the nodes forming the mesh cluster 302. In the convention of FIG. 15, the thick dark solid line represents a strong 2-way direct connection between nodes (e.g., between nodes 04 and 03); the think dark solid line with a cross hatch represents a weak 2-way direct connection between nodes (e.g., between nodes 09 and 05); the thinner dark solid line represents a 1-way direct, strong connection between nodes (e.g., one way between nodes 12 and 04); the thinner dark solid line with cross hatches represents a weak 1-way direct connection (e.g., one way between nodes 01 and 03); and the dashed or phantom line represents a poor or unsuccessful direct communication between nodes (e.g., between nodes 05 and 04).
The cluster 302 may be characterized by a topology cost matrix that identifies the number of hops a signal will have to make between any two nodes of the cluster. FIG. 17 shows a cost matrix 400 for the cluster 302. The matrix 400 shows the possible node connections with the nodes listed across a row 402 and a column 404. Within the table are numbers reflecting the number of hops determined for each connection between two nodes, where the column 404 indicates the transmitting node and the row 402 represents the receiving node. For example, a signal transmitted from node 08 and received at node 12 will require 4 hops, which can be determined by going to indictor 08 in column 404 and indicator 12 in row 402, where a value 406 indicates that 4 hops are necessary in the illustrated cost matrix 400. It is noted that given any two nodes, the transmission path may be different than the receive path. The characteristics of a propagation pattern may be unique to the local environment. As a result, pathways between two nodes may be different depending upon the source of the transmission.
Depending on the strength of the signal and the presence of one-way communication paths, the number of nodes for the converse path, i.e., with the receiving and transmitting nodes reversed, may be different. In the matrix 400, for example, a signal transmitted from node 12 to node 08 would experience 2 hops, as indicated by going to node 12 in column 404 and node 08 in row 402 where a value 408 shows 2 hops.
Generally, the fewer the number of hops the stronger the connection and the less likely there will be signal loss, bit failure, etc. However, within many environments the signal strength between nodes will vary, from strong to weak, such that even a single direct path between two nodes may not reflect the ideal path due if much stronger multiple hop paths exists. It depends on the preference settings of the reference node or base node that establishes the routing table and power settings table.
This cost matrix 400 is based on one particular set of values from a corresponding routing table. The same cluster of nodes 302 may have a different routing table and thus a different cost matrix. That is, any given number of node pairs may have numerous different connection possibilities, and matrix 400 represents just one.
Further, the wireless mesh network may be adjusted, for example, in response to environmental settings, such as RF noise. In response to actual or predicted changes in the RF noise level, routing tables at the nodes may be re-adjusted to establish different pathways to different nodes on the network. Another adjustment technique is through adjusting the power settings for the transceivers at the remote node to compensate for the changes in RF noise, whether those changes reflect RF noise increases which would suggest increased transmitter power levels for the affected nodes or RF noise decreases which would suggest decreased transmitter power levels for the affected nodes. In predictive systems in particular, the network may maintain integrity by re-routing those pathways affected by the RF noise or adjusting the power setting, without time out or down time.
Adjustment of the routing table may be based on empirical data developed during operation, for example, through an RF noise measurement apparatus at the reference or other nodes constantly measuring for changes in RF noise levels. Whereas program 250 may reflect an initialization sequence, program 500 shown in FIG. 18 may be used to adjust the power settings and/or rotating tables in response to changes in the RF noise level during operation. With the plant layout and all geoferenced nodes identified, along with a cluster forming a mesh or point-to-point network, a reference node or base node may receive RF noise update data from nodes in the system. The update data, for example, may include the measured environment data from a measurement apparatus such as that described above. In examples with a centralized controller like a base node, remote nodes may be programmed to constantly or periodically update the host computer with such data. Alternatively, the remote nodes may be programmed to communicate only upon charges in the environmental data, e.g., when the RF noise changes by a certain threshold value. In examples where a reference node or other remote node operates as the control node for adjusting RF power settings and routing tables for the network, the other remote nodes communicate with the power setting apparatus at this remote control node.
In any event, the centralized or distributed controller receives environmental data from each remote node at block 502. Along with environmental data, the remote nodes may transmit actual power levels, time, and other data. In some examples, the controller would already have access to the desired power levels for comparison to actual power levels, e.g., when the controller also set the initial power settings for the wireless communication system. Further, the controller and remote nodes should be synchronized, such that if time information is sent that information may be used for synchronization confirmation and correction purposes. At block 504, the controller analyzes the update data from the remote nodes to determine a predictive function of when similar changes will occur again. For RF noise update data, the block 504 may compare the update data to historical RF noise data to determine if a pattern exists, such as an increase in RF noise at sunrise of each morning.
The block 504 produces a predictive function and provides that function to a block 506, for example, a power setting apparatus as described above, which determines whether the predictive function should be used to adjust the power settings table. For example, the block 506 may determine that the change in RF noise level may be compensated for through increasing or decreasing the RF power settings at the affected remote units. Block 508 performs the adjustments to the power setting table. A block 510 similarly determines if the predictive function is such that the routing table itself should be adjusted, and a block 512 performs the adjustments to the routing table. In the illustrated example, the program 500 may be set to adjust both the RF power setting table and the routing table. A block 514 determines whether an adjustment has been made, and a block 516 transmits the adjusted data or the program 500 ends.
The adjustment procedures just discussed may be achieved on a centralized control node or they may be achieved at one or more remote nodes in a distributed manner. That is, the initial routing table and power settings may be centrally determined by a host computer at the base station, which may wirelessly communicate data to each node, while adjustment (including re-optimization) of the routing table and/or power settings may be performed at this central location or elsewhere in the wireless communication system.
In some examples, the base node may communicate multiple routing tables and power settings to the other nodes for local storage and access. The base node, for example, may transmit a primary routing table that is to be used under normal conditions and secondary and tertiary routing tables for non-normal conditions. For example, the base node may communicate a secondary routing table to be used upon generator turn on, and which routing table is initiated in response to instruction from the base node.
FIG. 19 is an example screen display 400 created by a wireless network analysis tool and illustrating RF ambient noise levels for various nodes. The graph portion provides four graphs one on top of another, each measured across time on the horizontal axis. The top graph 402 plots connectivity over time, as a percentage of the overall cost. The connectivity may for example reflect the cost, measured in total hops, for a network cluster as a function of time. The remaining graphs plot RF noise levels at different nodes, or unit locations in the plant layout map 254. Graph 404 plots the RF noise level measured at the node 09; graph 406 plots the RF noise level measured at the node 08; and graph 408 plots the RF noise level measured at the node 12. As can be seen, the highest RF noise level spikes are present at unit 12 (60.69 cost value as a highest plotted value). While RF noise is plotted in the illustrated example, other environmental data may be displayed instead.
An example power setting table 600 with arbitrary units in power and set as a function of time for each node is shown in FIG. 20. For illustration purposes, the table 600 includes time slots 602 that are the result of changes in the power settings. A full table may include time slots formed in repeating units of time, e.g., each 30, 15, 10, 5, or 1 minute in length. The changes in power settings are the result of analysis from a power setting apparatus and based on RF noise data collected over time. The base station node BA, for example, is predicted as seeing an RF noise level increase around 5:30 am�an arbitrary time for sunrise�which results in a power setting 604 of 40 for 12:00 am to 5:30 am changing to higher power setting 606 of 60 for 5:30 am to 6:30 am. In the illustrated example, the RF noise level at node BA peaks within this time window, for example, as employees initially arrive to a unit and increase the overall RF noise level. Over the next time window, power setting 608 for node BA is ramped down to 55, reflecting a predicted smaller drop in RF noise levels. Other changes and differences in power settings for the different nodes are apparent from the table. These power settings may represent optimal setting values, meaning that the overall minimum number of hops are used throughout the network at the minimum power settings.
FIGS. 21 and 22 illustrate example routing tables for a node cluster containing 2 or fewer hops, similar to the illustration of FIG. 6. FIG. 21 illustrates a first routing table 700 under a first set of RF noise levels. All routes listed are single hop count routes with the exception of entries 702-712 which reflect two hops between nodes in one direction, with the transmitting node on the vertical axis and the receiving node on the horizontal axis. FIG. 22 illustrates that same routing table, labeled 700′, after it has been adjusted in response to RF noise levels. The two-hop entries 702, 704, and 708 have not changed, but the remaining two-hop entries, now 706′, 710′, and 712′, have now changed to reflect a different routing path as a result of measured or predicted RF noise level changes at the remote nodes.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5566356Dec 15, 1994Oct 15, 1996Nec CorporationMobile communication system and its multiple connection method enabling to perform concise and high quality multiplex communicationUS5640400Feb 27, 1996Jun 17, 1997Sharp Kabushiki KaishaMutual connecting apparatus between networksUS5682476Jan 9, 1997Oct 28, 1997Fisher-Rosemount Systems, Inc.Distributed control system having central control providing operating power to wireless transceiver connected to industrial process control field device which providing redundant wireless accessUS5771174Dec 13, 1996Jun 23, 1998Measurex CorporationDistributed intelligence actuator controller with peer-to-peer actuator communicationUS5793963Jul 15, 1997Aug 11, 1998Fisher Rosemount Systems, Inc.Apparatus for providing non-redundant secondary access to field devices in a distributed control systemUS5796602Jul 12, 1996Aug 18, 1998Fisher-Rosemount Systems, Inc.Method and apparatus using a device description for a conventional deviceUS5960214Dec 4, 1996Sep 28, 1999Fisher-Rosemount Systems, Inc.Integrated communication network for use in a field device management systemUS5973643Apr 11, 1997Oct 26, 1999Corsair Communications, Inc.Method and apparatus for mobile emitter locationUS5974320May 21, 1997Oct 26, 1999Telefonaktiebolaget Lm Ericsson (Publ)Providing a neighborhood zone within a mobile telecommunications networkUS6091951Sep 3, 1997Jul 18, 2000Telxon CorporationSeamless roaming among multiple networksUS6091954Apr 7, 1997Jul 18, 2000Telefonaktiebolaget Lm EricssonChannel assignment in enhanced fixed-plan mobile communications systemsUS6199018Mar 4, 1998Mar 6, 2001Emerson Electric Co.Distributed diagnostic systemUS6246320Feb 25, 1999Jun 12, 2001David A. MonroeGround link with on-board security surveillance system for aircraft and other commercial vehiclesUS6286038Aug 3, 1998Sep 4, 2001Nortel Networks LimitedMethod and apparatus for remotely configuring a network deviceUS6304556 *Aug 24, 1998Oct 16, 2001Cornell Research Foundation, Inc.Routing and mobility management protocols for ad-hoc networksUS6490297Jun 4, 1999Dec 3, 2002Lucent Technologies Inc.System and method for automatic signaling channel identificationUS6711148 *Apr 10, 2000Mar 23, 2004Carnegie Mellon UniversityMethod for configuring a wireless networkUS6728262Oct 2, 2000Apr 27, 2004Coi Software, Inc.System and method for integrating process control and network managementUS6735448 *Nov 7, 2000May 11, 2004Hrl Laboratories, LlcPower management for throughput enhancement in wireless ad-hoc networksUS6748233 *Oct 27, 2000Jun 8, 2004Telcordia Technologies, Inc.System and method for energy-efficient transmission power control, routing and transmission scheduling in wireless communication networksUS6775707Oct 15, 1999Aug 10, 2004Fisher-Rosemount Systems, Inc.Deferred acknowledgment communications and alarm managementUS6826385Feb 22, 2002Nov 30, 2004Nokia CorporationMethod and system for distributing geographical addresses across the surface of the earthUS6847997Apr 19, 2000Jan 25, 2005Motorola, Inc.Communications network utilizing transmitter and channel diversity to mitigate path impairmentsUS6862460May 18, 2001Mar 1, 2005General Instrument CorporationSelf-configurable multipurpose modular portable device and methods for configuring sameUS6970183Jun 14, 2000Nov 29, 2005E-Watch, Inc.Multimedia surveillance and monitoring system including network configurationUS6970714 *Apr 30, 2002Nov 29, 2005Lucent Technologies Inc.Adaptive power level setting in an ad-hoc wireless networkUS6975873Dec 28, 2001Dec 13, 2005At&T Corp.System and method for tracking the relative location of mobile stations belonging to a pre-defined group of mobile stationsUS6985087 *Mar 15, 2002Jan 10, 2006Qualcomm Inc.Method and apparatus for wireless remote telemetry using ad-hoc networksUS7019637 *Mar 28, 2003Mar 28, 2006Sandia National LaboratoriesSystems and methods for detecting and processingUS7068605 *Sep 9, 2003Jun 27, 2006Harris CorporationMobile ad hoc network (MANET) providing interference reduction features and related methodsUS7106703 *May 28, 2002Sep 12, 2006Meshnetworks, Inc.System and method for controlling pipeline delays by adjusting the power levels at which nodes in an ad-hoc network transmit data packetsUS7106707 *Dec 20, 2001Sep 12, 2006Meshnetworks, Inc.System and method for performing code and frequency channel selection for combined CDMA/FDMA spread spectrum communication systemsUS7184770 *Mar 5, 2003Feb 27, 2007Aruba Networks, Inc.System and method for positioning and calibrating wireless network devicesUS7251224 *Oct 9, 2001Jul 31, 2007Intel CorporationCommunications meshesUS7283832Mar 1, 2004Oct 16, 2007Koninklijke Philips Electronics, N.V.Method and system for establishing wireless peer-to-peer communicationsUS7353023Apr 2, 2001Apr 1, 2008At&T Delaware Intellectual Property, Inc.Method and apparatus for delivering messages to wireless devicesUS7436797Jun 17, 2005Oct 14, 2008Fisher-Rosemount Systems, Inc.Wireless architecture and support for process control systemsUS7460865Jun 18, 2003Dec 2, 2008Fisher-Rosemount Systems, Inc.Self-configuring communication networks for use with process control systemsUS7482929May 1, 2006Jan 27, 2009International Business Machines CorporationPoint-of-sale activation of consumer electronicsUS7496059 *Dec 9, 2004Feb 24, 2009Itt Manufacturing Enterprises, Inc.Energy-efficient medium access control protocol and system for sensor networksUS7512079 *Jul 28, 2005Mar 31, 2009University Of South FloridaSystem and method to assure node connectivity in an ad hoc networkUS7606938Feb 28, 2003Oct 20, 2009Enterasys Networks, Inc.Verified device locations in a data networkUS7708707Jul 31, 2003May 4, 2010Gordon CookInflatable device for use in impulse therapyUS7933594Jun 17, 2008Apr 26, 2011Fisher-Rosemount Systems, Inc.Self-configuring communication networks for use with process control systemsUS20020102995Nov 15, 2001Aug 1, 2002Intech 21, Inc.Method for tracking the location of mobile unitsUS20020125998 *May 6, 2002Sep 12, 2002Petite Thomas D.System and method for monitoring and controlling remote devicesUS20020130846Sep 13, 2001Sep 19, 2002Nixon Mark J.Portable computer in a process control environmentUS20020160771Dec 29, 2000Oct 31, 2002Massie Rodney ESystem and method of transmitting data messages between subscriber units communicating with/between Complementary/Disparate NetworksUS20020169514Feb 28, 2002Nov 14, 2002Evren EryurekAutomatic work order/parts order generation and trackingUS20020169977May 11, 2001Nov 14, 2002Mazen ChmaytelliSystem, methods, and apparatus for distributed wireless configuration of a portable deviceUS20030043052Mar 8, 2001Mar 6, 2003Fisher-Rosemount Systems, Inc.Apparatus for providing redundant wireless access to field devices in a distributed control systemUS20030054868Sep 20, 2001Mar 20, 2003International Game TechnologyGame service interfaces for player tracking touch screen displayUS20030099221Nov 26, 2002May 29, 2003Sokwoo RheeNetwork protocolUS20030171827Mar 6, 2002Sep 11, 2003Keyes Marion A.Appendable system and devices for data acquisition, analysis and controlUS20030198208Apr 19, 2002Oct 23, 2003Koos William M.Data network having a wireless local area network with a packet hopping wireless backboneUS20030218996Jul 24, 2002Nov 27, 2003Hiromitsu SuminoConnection cutting method and associated link cut reporting methodUS20040015609Jul 18, 2002Jan 22, 2004International Business Machines CorporationMethod and system for conversion of message formats in a pervasive embedded network environmentUS20040103165Nov 25, 2002May 27, 2004Nixon Mark J.Interactive two-way collaboration in process control plantsUS20040153594Jan 30, 2003Aug 5, 2004Rotvold Eric D.Interface module for use with a Modbus device network and a Fieldbus device networkUS20040203355Jul 3, 2002Oct 14, 2004Light Jeffrey RossSystem and method for enabling a mobile phoneUS20040203434Oct 23, 2002Oct 14, 2004Rosemount, Inc.Virtual wireless transmitterUS20040203762 *Oct 15, 2002Oct 14, 2004Jiewen LiuOperating an ad-hoc wireless network in one or more regulatory regionsUS20040203863Jun 28, 2002Oct 14, 2004Heikki HuomoSystem and method for initiating location-dependent applications on mobile devicesUS20040203897 *Dec 17, 2002Oct 14, 2004Comarco Wireless TechnologiesSystem and method for precise navigation in testing wireless communication networksUS20040203989 *Dec 9, 2002Oct 14, 2004Broadcom CorporationUsing location information to control transmission signal levels of wireless devicesUS20040235468 *May 19, 2003Nov 25, 2004Luebke Charles J.Wireless network clustering communication system, wireless communication network, and access port for sameUS20040242216Jun 2, 2003Dec 2, 2004Nokia CorporationSystems and methods for transferring data between mobile stationsUS20040242275May 30, 2003Dec 2, 2004Corbett Christopher J.Using directional antennas to enhance wireless mesh networksUS20040259533Jun 18, 2003Dec 23, 2004Mark NixonSelf-configuring communication networks for use with process control systemsUS20040260405Jun 18, 2003Dec 23, 2004Ron EddieModular monitoring, control and device management for use with process control systemsUS20050062677Sep 9, 2004Mar 24, 2005Nixon Mark J.Portable computer in a process control environmentUS20050130605Dec 12, 2003Jun 16, 2005Karschnia Robert J.Bus powered wireless transmitterUS20050276233Jun 17, 2005Dec 15, 2005Fisher-Rosemount Systems, Inc.Wireless architecture and support for process control systemsUS20060077917Oct 7, 2004Apr 13, 2006Honeywell International Inc.Architecture and method for enabling use of wireless devices in industrial controlUS20080250162Jun 17, 2008Oct 9, 2008Mark NixonSelf-configuring communication networks for use with process control systemsUS20080291013Aug 8, 2008Nov 27, 2008Battelle Energy Alliance, LlcWireless device monitoring systems and monitoring devices, and associated methodsUS20090097415Oct 13, 2008Apr 16, 2009Fisher-Rosemount Systems, Inc.Wireless architecture and support for process control systemsCN1258991ADec 24, 1999Jul 5, 2000三星电子株式会社Apparatus for selectively inverting clock frequency in digital signal receiverCN1387324AMay 20, 2002Dec 25, 2002通用仪器公司Multifunctional modular portable apparatus capable of automatic configurating, and configurating method thereforEP0748085A1May 29, 1996Dec 11, 1996General Electric CompanyLocal communication network for power reduction and enhanced reliability in a multiple node tracking systemEP0961184A2Feb 5, 1997Dec 1, 1999Fisher-Rosemount Systems, Inc.System and method for managing a transaction database of records of changes to field device configurationsEP1045302A1Apr 12, 2000Oct 18, 2000Neles Field Controls OyA wireless control of a field device in an industrial processEP1258991A2May 17, 2002Nov 20, 2002General Instrument CorporationSelf-configurable multipurpose modular portable device and methods for configuring sameEP1326349A1Jun 25, 2002Jul 9, 2003Siemens AktiengesellschaftMethod for transmission power control of a mobile station, and corresponding radio system and mobile stationEP1689094A2Jan 24, 2006Aug 9, 2006Samsung Electronics Co., Ltd.Wireless communication method and system for differentially controlling power according to distanceGB2277849A Title not availableGB2318252A Title not availableGB2345827A Title not availableGB2352539A Title not availableGB2403043A Title not availableGB2423443A Title not availableGB2427797A Title not availableGB2464411A Title not availableGB2466740A Title not availableJP2000092117A Title not availableJP2001036542A Title not availableJP2001277962A Title not availableJP2002006941A Title not availableJP2002044722A Title not availableJP2002064648A Title not availableJP2002523928A Title not availableJP2005050313A Title not availableJP2005051746A Title not availableWO1992011736A1Dec 17, 1991Jun 22, 1992Ericsson Telefon Ab L MQuality check for a mobile cellular radio systemWO1998036335A2Feb 6, 1998Aug 20, 1998Fisher Rosemount Systems IncProcess control system using a layered-hierarchy control strategy distributed into multiple control devicesWO2001035190A2Nov 13, 2000May 17, 2001Statsignal Systems IncSystem and method for monitoring and controlling remote devicesWO2001090773A1May 8, 2001Nov 29, 2001Koninkl Philips Electronics NvA method of estimating the location of a deviceWO2004079919A2Feb 28, 2004Sep 16, 2004Koninkl Philips Electronics NvWireless performance optimization based on network topology and peer responsivenessWO2004109984A2May 28, 2004Dec 16, 2004Adaptive Instr CorpIndustrial wireless network and message authentication system* Cited by examinerNon-Patent CitationsReference1Chinese Rejection Decision for Application No. 2004100794746, dated Oct. 29, 2008.2Combined Search and Examination Report for Application No. GB0922268.8, dated Feb. 15, 2010.3Combined Search and Examination Report for Application No. GB0922269.6, dated Feb. 15, 2010.4Combined Search and Examination Report for Application No. GB1 107853.2, dated Jun. 27, 2011.5Combined Search and Examination Report under Sections 17 and 18(3) issued in GB0922269.6 application by United Kingdom Patent Office on Sep. 27, 2010.6Combined Search and Examination Report under Sections 17 and 18(3) issued in GB1006300.6 application by United Kingdom Patent Office on Apr. 29, 2010.7Combined search and examination report, The Patent Office, United Kingdom, Oct. 25, 2006. Four sheets.8Decision of Rejection for Japanese Application No. 2004-179085, dated Nov. 16, 2010.9Examination Reoort for Application No. GB0922269.6, dated Feb. 15, 2010.10Examination Report for Application No. GB0611940.8, dated Feb. 15, 2010.11Examination Report for Application No. GB0611940.8, dated Jul 7, 2009.12Examination Report for Application No. GB0616898.3, dated Jun. 13, 2007.13Examination Report for Application No. GB0724804.0, dated Jan. 12, 2011.14Examination Report for Application No. GB0922268.8, dated Feb. 15, 2010.15Examination Report for Application No. GB0922269.6, dated May 13, 2010.16First Chinese Office Action for Application No. 2004100794746, dated Aug. 24, 2007.17First Chinese Office Action for Application No. 200610086707.4, dated Aug. 14, 2009.18First Chinese Office Action for Application No. 200710301629.X, dated Dec. 22, 2010.19Great Britain Search Report, Oct. 13, 2004, 3 sheets.20Notice of Reasons for Rejection for Japanese Application No. 2006-168850, dated Jun. 9, 2011.21Notice of Reasons of Rejection for Japanese Application No. 2004-179085, dated Feb. 23, 2010.22Office Action for U.S. Appl. No. 10/464,087, dated Jun. 9, 2006.23Office Action for U.S. Appl. No. 10/464,087, dated Nov. 1, 2005.24Office Action for U.S. Appl. No. 10/464,087, dated Nov. 6, 2006.25Office Action for U.S. Appl. No. 11/156,215, dated Sep. 24, 2007.26Office Action for U.S. Appl. No. 12/140,571, dated Dec. 3, 2009.27Office Action for U.S. Appl. No. 12/140,571, dated Jul. 6, 2010.28Office Action for U.S. Appl. No. 12/250,410, dated Feb. 4, 2011.29Office Action for U.S. Appl. No. 12/250,410, dated Jan. 12, 2010.30Office Action for U.S. Appl. No. 12/250,410, dated May 6, 2010.31Product Description: JTS (retrieved Apr. 7, 2010). Available at: http://www.acugen.com/jts.htm.32Reexamination Notification for Chinese Application No. 2004100794746, dated Nov. 6, 2009.33Restriction Requirement for U.S. Appl. No. 10/464,087, dated May 25, 2005.34Search Report for Application No. GB0611940.8, dated Sep. 21, 2006.35Search Report for Application No. GB0724804.0, dated Apr. 21, 2008.36Search Report under Section 17 for Application No. GB0724804.0, dated Apr. 21, 2008.37Second Chinese Office Action for Application No. 200610086707.4, dated Jun. 29, 2010.38Second Office Action for Chinese Application No. 2004100794746, dated May 9, 2008.39The Patent Office, Examination Report, Sep. 29, 2005. 4 pages.40U.S. Appl. No. 12/250,410, filed Oct. 13, 2008.41ZigBee Wireless Networking Systems-Ember (retrieved Apr. 7, 2010). Available at: http://www.ember.com.42ZigBee Wireless Networking Systems�Ember (retrieved Apr. 7, 2010). Available at: http://www.ember.com.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8456278 *Mar 24, 2010Jun 4, 2013Resolution Products, Inc.Communicating within a wireless security system* Cited by examinerClassifications U.S. Classification455/426.2, 455/115.1, 340/517, 455/501, 340/539.22, 455/522, 455/404.2, 455/453, 455/67.11, 340/521, 455/456.1, 340/539.29, 455/62, 455/63.1International ClassificationH04W24/00Cooperative ClassificationH04W52/245, H04W52/283, H04W52/24, H04W24/00, H04W64/00, H04W52/243European ClassificationH04W64/00, H04W52/28L, H04W52/24Legal EventsDateCodeEventDescriptionApr 29, 2014CCCertificate of correctionDec 22, 2006ASAssignmentEffective date: 20061220Owner name: FISHER-ROSEMOUNT SYSTEMS, INC., TEXASFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NELSON, JOE;REEL/FRAME:018729/0142RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services