This disclosure relates generally to wireless networks and more specifically to an apparatus and method for planning and validating a wireless network.
Industrial control and automation systems are often used to automate large and complex industrial processes. These types of systems routinely include wireless networks that facilitate communication between a wide range of wireless devices. Often times, wireless devices cannot communicate directly with one another because of excessive distances, physical obstructions, or other factors. Additional wireless routing devices can therefore be installed in a wireless network in order to route data to and from the wireless devices.
Before installing a wireless network, the cost of deploying the wireless network can be estimated by identifying the wireless devices to be used in the network. Unlike wired networks where it is often straight-forward to determine the number of devices and cabling requirements, wireless networks pose challenges due to the uncertainties of wireless communications. A typical system integrator may not be well-versed with wireless propagation characteristics and may tend to over-design or under-design a wireless network. An over-designed wireless network (with more wireless devices than needed) has a higher cost and a higher complexity. An under-designed network (with fewer wireless devices than needed) results in an unreliable network and requires additional time and cost for diagnosing and rectifying the faults in the network.
This disclosure provides an apparatus and method for planning and validating a wireless network.
In a first embodiment, a method includes displaying an image associated with a site at which a wireless network is to be installed or modified. The method also includes identifying positions of multiple wireless devices within the image. Different ones of the wireless devices are configured to support different wireless protocols, and the wireless devices and their positions form at least part of a design of the wireless network. The method further includes displaying, within the image, at least one of: (i) estimated wireless coverage areas of the wireless devices, (ii) estimated wireless connectivity between the wireless devices, and (iii) estimated communication routes between the wireless devices. In addition, the method includes validating the design of the wireless network against one or more network criteria using at least one of the estimated wireless coverage areas, the estimated wireless connectivity, and the estimated communication routes.
In a second embodiment, an apparatus includes at least one memory configured to store an image associated with a site at which a wireless network is to be installed or modified. The apparatus also includes at least one processing device configured to initiate display of the image and identify positions of multiple wireless devices within the image. Different ones of the wireless devices are configured to support different wireless protocols, and the wireless devices and their positions form at least part of a design of the wireless network. The at least one processing device is also configured to initiate display, within the image, of at least one of: (i) estimated wireless coverage areas of the wireless devices, (ii) estimated wireless connectivity between the wireless devices, and (iii) estimated communication routes between the wireless devices. The at least one processing device is further configured to validate the design of the wireless network against one or more network criteria using at least one of the estimated wireless coverage areas, the estimated wireless connectivity, and the estimated communication routes.
In a third embodiment, a non-transitory computer readable medium embodies a computer program. The computer program includes computer readable program code for initiating display of an image associated with a site at which a wireless network is to be installed or modified and identifying positions of multiple wireless devices within the image. Different ones of the wireless devices are configured to support different wireless protocols, and the wireless devices and their positions form at least part of a design of the wireless network. The computer program also includes computer readable program code for initiating display, within the image, of at least one of: (i) estimated wireless coverage areas of the wireless devices, (ii) estimated wireless connectivity between the wireless devices, and (iii) estimated communication routes between the wireless devices. The computer program further includes computer readable program code for validating the design of the wireless network against one or more network criteria using at least one of the estimated wireless coverage areas, the estimated wireless connectivity, and the estimated communication routes.
Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.
For a more complete understanding of this disclosure, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:
A controller 104 is coupled to the process elements 102. The controller 104 controls the operation of one or more of the process elements 102. For example, the controller 104 could receive information associated with the process system, such as sensor measurements from some of the process elements 102. The controller 104 could use this information to generate control signals for others of the process elements 102, such as actuators, to thereby adjust the operation of those process elements 102. The controller 104 includes any suitable structure for controlling one or more process elements 102. The controller 104 could, for example, represent a computing device executing multi-variable or other control logic.
A network 106 facilitates communication between various components in the system 100. For example, the network 106 may communicate Internet Protocol (IP) packets, frame relay frames, Asynchronous Transfer Mode (ATM) cells, or other suitable information between network addresses. The network 106 may include one or more local area networks, metropolitan area networks, wide area networks, all or a portion of a global network, or any other communication system(s) at one or more locations. As a particular example, the network 106 could include a FAULT TOLERANT ETHERNET network from HONEYWELL INTERNATIONAL INC.
As shown in
The infrastructure nodes 108a-108c and leaf nodes 110a-110c engage in wireless communications with each other. For example, the infrastructure nodes 108a-108c may receive data transmitted over the network 106 (via a gateway infrastructure node 112) and wirelessly communicate the data to the leaf nodes 110a-110c. Also, the leaf nodes 110a-110c may wirelessly communicate data to the infrastructure nodes 108a-108c for forwarding to the network 106 (via a gateway infrastructure node 112). In addition, the infrastructure nodes 108a-108c may wirelessly exchange data with one another. In this way, the nodes 108a-108c, 112 (and optionally the nodes 110a-110c) form a wireless network capable of providing wireless coverage to leaf nodes and other devices in a specified area, such as a large industrial complex.
In this example, the nodes 108a-108c and 110a-110c are divided into infrastructure nodes and leaf nodes. The infrastructure nodes 108a-108c typically represent routing devices that can store and forward messages for other devices. Infrastructure nodes 108a-108c are typically line-powered devices, meaning these nodes receive operating power from an external source. Infrastructure nodes 108a-108c are typically not limited in their operations since they need not minimize power consumption to increase the operational life of their internal power supplies. On the other hand, the leaf nodes 110a-110c are generally non-routing devices that do not store and forward messages for other devices (although they could). Leaf nodes 110a-110c typically represent devices powered by local power supplies, such as nodes that receive operating power from internal batteries or other internal power supplies. Leaf nodes 110a-110c are often more limited in their operations in order to help preserve the operational life of their power supplies.
The nodes 108a-108c and 110a-110c include any suitable structures facilitating wireless communications, such as radio frequency (RF) frequency-hopping spread spectrum (FHSS) or direct sequence spread spectrum (DSSS) transceivers. The nodes 108a-108c and 110a-110c could also include other functionality, such as functionality for generating or using data communicated over the wireless network. For example, the leaf nodes 110a-110c could include wireless sensors used to measure various characteristics within an industrial facility. The sensors could collect and communicate sensor readings to the controller 104 via the wireless network. The leaf nodes 110a-110c could also include wireless actuators that receive control signals from the controller 104 and that adjust the operation of the industrial facility. In this way, the leaf nodes may include or operate in a similar manner as the process elements 102 physically connected to the controller 104. The leaf nodes 110a-110c could further include handheld user devices (such as INTELATRAC devices from HONEYWELL INTERNATIONAL INC.), mobile stations, programmable logic controllers, process controllers, or any other or additional devices. The infrastructure nodes 108a-108c, 112 may also include any of the functionality of the leaf nodes 110a-110c or the controller 104.
The gateway infrastructure node 112 functions as an infrastructure node and communicates wirelessly with, transmits data to, and receives data from one or more infrastructure nodes and possibly one or more leaf nodes. The gateway infrastructure node 112 also converts data between protocol(s) used by the network 106 and protocol(s) used by the nodes 108a-108c and 110a-110c. For example, the gateway infrastructure node 112 could convert Ethernet-formatted data transported over the network 106 into a wireless protocol format (such as an IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.15.3, 802.15.4, or 802.16 format or an ISA100.11a format) used by the nodes 108a-108c and 110a-110c. The gateway infrastructure node 112 could also convert data received from one or more of the nodes 108a-108c and 110a-110c into Ethernet-formatted data for transmission over the network 106. In addition, the gateway infrastructure node 112 could support various functions, such as network creation and security, used to create and maintain a wireless network. The gateway infrastructure node 112 includes any suitable structure for facilitating communication between components or networks using different protocols.
In particular embodiments, various wireless nodes 108a-108c, 112 (and possibly nodes 110a-110c) in the wireless network of
A wireless configuration and OLE for Process Control (OPC) server 114 can configure and control various aspects of the system 100. For example, the server 114 could configure the operation of the nodes 108a-108c, 110a-110c, and 112. The server 114 could also support security in the system 100, such as by distributing cryptographic keys or other security data to various components in the system 100 (like to the nodes 108a-108c, 110a-110c, and 112). The server 114 includes any suitable structure for configuring wireless networks and providing security information.
In one aspect of operation, the overall design of a wireless network can be planned and validated using one or more wireless network planning and validation devices 116a-116b. For example, a planning and validation device 116a-116b can be used to create a new design for a wireless network to be installed. The planning and validation device 116a-116b can also be used to modify the design for an existing wireless network.
Among other things, a planning and validation device 116a-116b can allow a user to define different regions within a given site, where those different regions have different wireless propagation characteristics. The planning and validation device 116a-116b can also allow the user to place wireless devices over a map, drawing, or other image of the site and view wireless coverage areas provided by those wireless devices. In addition, the planning and validation device 116a-116b can identify estimated wireless paths between the wireless devices and verify whether the user-defined placement of wireless devices satisfies one or more criteria (such as a desired redundancy of wireless network paths).
In this way, a network designer or other personnel can more easily plan and validate a wireless network to meet any quality of service (QoS) requirements or other requirements. Factors that influence wireless propagation can be transformed into simple and easy-to-understand terminology for non-technical users. These factors can include propagation losses, decay exponents, environment dependencies, directional antenna gains, Fresnel zone effects, multipath propagations, signal-to-noise ratios, and equivalent isotropically radiated power (EIRP) regulations. Moreover, by selecting a few parameters and dividing an industrial facility or other site into sub-regions, a user is able to plan a multi-radio network (such as a network with ISA100.11a and WiFi devices) with ease. The parameters can include settings such as the country of deployment, the type of RF environment, any required data rate, a desired noise floor, and heights of the wireless devices.
Each planning and validation device 116a-116b includes any suitable structure for planning a design of a wireless network and verifying the design against one or more criteria. For example, each planning and validation device 116a-116b could represent a computing device that executes a wireless network planning and validation application. In this example, the planning and validation devices 116a-116b include a wireless device 116a and a wired device 116b. The wireless device 116a could represent a laptop computer, tablet computer, smartphone, personal digital assistant, or other portable computing device that communicates over a wireless connection. The wired device 116b could represent a desktop computer, laptop computer, server computer, or other suitable computing device that communicates over a wired connection.
Although
The processing device 204 executes instructions that may be loaded into a memory 212. The processing device 204 may include any suitable number(s) and type(s) of processors or other devices in any suitable arrangement. Example types of processing devices 204 include microprocessors, microcontrollers, digital signal processors, field programmable gate arrays, application specific integrated circuits, and discrete circuitry.
The memory 212 and a persistent storage 214 are examples of storage devices 206, which represent any structure(s) capable of storing and facilitating retrieval of information (such as data, program code, and/or other suitable information on a temporary or permanent basis). The memory 212 may represent a random access memory or any other suitable volatile or non-volatile storage device(s). The persistent storage 214 may contain one or more components or devices supporting longer-term storage of data, such as a ready only memory, hard drive, Flash memory, or optical disc.
The communications unit 208 supports communications with other systems or devices. For example, the communications unit 208 could include a network interface card that facilitates communications over the network 106. The communications unit 208 could also include a wireless transceiver facilitating communications over a wireless network. The communications unit 208 may support communications through any suitable physical or wireless communication link(s).
The I/O unit 210 allows for input and output of data. For example, the I/O unit 210 may provide a connection for user input through a keyboard, mouse, keypad, touchscreen, or other suitable input device. The I/O unit 210 may also send output to a display, printer, or other suitable output device.
As described in more detail below, the planning and validation device 116 can execute an application that presents a graphical user interface (GUI) to a user. The GUI can be used to import an image of an industrial facility or other site and establish various parameters for a wireless network. The GUI can also be used to identify different regions of the site that have different wireless propagation characteristics. The GUI can further be used to place representations of wireless devices on the image of the site and view the resulting wireless coverage areas provided by the wireless devices. In addition, after the planning and validation device 116 analyzes the wireless network created using the user-identified wireless devices, the GUI can present validation results indicating whether the resulting wireless network satisfies one or more criteria.
Although
As part of the description of
As shown in
The information could be obtained in any suitable manner, such as by using the GUI 400 in
The RF environment section 404 allows the user to specify the type of environment in which a wireless network has been or will be deployed. In this example, the user is allowed to select one of three options, namely an outdoor environment (where most devices are in line of sight and low interference is expected), an industrial environment (where obstacles may be present and intermediate interference is expected), or a high-interference environment. Note that these three options are for illustration only and that other or additional options could be provided and associated with different RF environments.
The design parameters section 406 allows the user to specify different parameters related to wireless communications. In this example, the design parameters section 406 includes a drop-down menu for identifying the desired data rate and a text box for identifying the desired noise floor. Other or additional design parameters could also be included. The description section 408 includes a text box that allows the user to enter a textual description, such as notes related to the site or the wireless network being designed.
The site map section 410 allows the user to identify an image of a site to be used during definition of the wireless network. In this example, the site map section 410 includes radio buttons that allow the user to identify an image of a site using on online map (such as a GOGGLE EARTH image), a user-defined image location, or a blank image of a defined size. The site map section 410 also allows the user to specify whether distances are expressed in feet, meters, or other measures of distance.
Returning to
An example of this is shown in
Once the image 502 is displayed, the user can use a mouse or other pointing device to select one of the icons 504. After selecting the icon 504, the user can select the appropriate drawing tool(s) 506 and use the pointing device to define a region 508 within the image 502. This process can be repeated any number of times to define any number of regions 508. Each defined region 508 could have any suitable size, shape, and dimensions. The shape could be a regular or irregular shape with any number of curved or straight sides. Each region 508 can also have a color or other indicator that is based on the type of that region, where different types of regions have different indicators. For each region 508, the user could identify various features of that region 508, such as via a pop-up menu. The features could include the types of materials present in that region 508, obstacles in that region 508, and the heights of any obstacles in that region 508.
In this example, the user has identified five regions 508, although any number of additional regions could be defined within the image 502. Each region 508 has an associated label that can be selected to set the features of that region 508. As described below, the defined regions are used to estimate the coverage areas of wireless devices placed within the site. If a specific region 508 is selected by the user, information about that region 508 can also be presented in the GUI 400. For instance, the size of a selected region (such as in terms of total square feet or total square meters) could be displayed within the GUI 400.
The GUI 400 in
Returning to
An example of this is shown in
A control 608 in the GUI 400 allows the user to switch between different types of wireless protocols or technologies. This allows the user to place wireless devices supporting different protocols into the same image 502 of the site. For example, the user can select a first protocol using the control 608, and the GUI 400 can present a list 604 of wireless devices that support the first protocol. The user can also select a second protocol using the control 608, and the GUI 400 can present another list 604 of wireless devices that support the second protocol. Note that a multi-radio wireless device that supports both protocols could be presented in both lists. This allows the user to design a wireless network that supports multiple protocols.
Returning to
An example of this is again shown in
Another example of this is shown in
Returning to
An example of this is shown in
Returning to
An example of this is shown in
Returning to
An example of this is shown in
Once a network design is validated, a description of the wireless network can be generated and output at step 320. This could include, for example, the planning and validation device 116 generating a bill of materials describing the wireless devices to be included in the wireless network. Any additional information could be included, such as locations and configurations of the wireless devices to be included in the wireless network.
While not shown, the user may at various points repeat certain steps of
Note that while various steps are described above as being performed based on user input, one, some, or all of these steps could also be performed in an automated manner. For example, the different regions 508 of a site could be defined automatically, such as based on image analysis. As another example, different types of wireless devices could be selected and positioned within an image automatically or parameters of the wireless devices could be selected automatically in order to meet one or more criteria. A user could be involved in this automated process in any suitable manner, such as to confirm or modify automatically-identified regions, devices, or parameters.
Although
In general, the standard model for wireless propagation losses in the presence of obstacles can be expressed as:
Here, PR denotes receive power, and PT denotes transmit power. Also, L0 denotes the path loss at distance d0, n denotes the path loss exponent, and d denotes the distance between the transmitter and the receiver. In addition, Li denotes the combined losses due to all obstacles, where i represents the index of the obstacles. However, this model does not incorporate any mechanism for recognizing that wireless signals between the transmitter and the receiver may pass through regions having different wireless propagation characteristics.
An example of this is shown in
In some embodiments of this disclosure, the model for wireless propagation losses in the presence of obstacles is modified as follows:
where:
Σdi=d (3)
Here, ζ denotes an “obstacle density” and can be expressed as attenuation per unit length (like dB/m). For each ith region, that region is characterized by its own πi value, and di denotes the distance between the transmitter and receiver in that region. The loss due to obstacles here is linear with distance. For the example shown in
In some embodiments, the wireless network planning and validation device 116 uses Equation (2) to estimate the coverage areas of wireless devices. However, the model in Equation (2) may be too computationally expensive for particular implementations of the planning and validation device 116. For example, it may be computationally difficult, for every point on a coverage contour, to find the intersection points of the Tx-Rx line with the boundaries of different regions. In other embodiments, a simplification of Equation (2) can be used to reduce the computational complexity without excessively sacrificing accuracy. In many use cases, there may be a limited number of defined regions 508 (such as less than ten), and the transmitter Tx and receiver Rx are often in the same region or in adjacent regions. As a result, Equation (2) could be simplified as follows:
where ζT and dT are associated with the transmitter's region and ζR and dR are associated with the receiver's region.
In Equation (5), instead of finding the values of dT and dR, the values can be approximated using L0. For example, each region can have an associated parameter L0i, and the location of the transmitter Tx and the receiver Rx can be sufficient to compute the receive power as follows:
where:
(a−b)=a−b if a>b (7)
=0 otherwise (8)
Here, L0Tx denotes the path loss constant in the transmitter's region, and L0Rx denotes the path loss constant in the receiver's region.
In these embodiments, the ζ value(s) could typically be in the range of about 0.05 to about 0.5. Also, average distances di could be about 100 m. As a result, variations in signal strength due to these parameters may typically be on the order of a few decibels.
Although
Among other things, the above approach supports the following features. First, the planning and validation device 116 provides the ability to plan multi-radio networks (like both ISA100.11a and WiFi networks). A user can choose the wireless coverage or connectivity for each type of radio and plan the network so that it meets the requirements of all radios. Second, the above approach provides RF environment-based and region classification-based planning. The device 116 calibrates propagation parameters for each type of environment, and the device 116 classifies different types of regions in each environment for finer calibration of propagation parameters. Third, the device 116 validates a planned network for route redundancy and device capacity. If any device does not have the required or desired number of redundant routes or has an excessive number of child nodes such that its capacity is exceeded, the user is alerted for that particular device or alerted to add an addition wireless device.
In some embodiments, various functions described above are implemented or supported by a computer program that is formed from computer readable program code and that is embodied in a computer readable medium. The phrase “computer readable program code” includes any type of computer code, including source code, object code, and executable code. The phrase “computer readable medium” includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory.
It may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term “couple” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation. The term “or” is inclusive, meaning and/or. The phrase “at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, “at least one of A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C. The phrase “associated with,” as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like.
While this disclosure has described certain embodiments and generally associated methods, alterations and permutations of these embodiments and methods will be apparent to those skilled in the art. Accordingly, the above description of example embodiments does not define or constrain this disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of this disclosure, as defined by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
5063562 | Barzilai et al. | Nov 1991 | A |
5396537 | Schwendeman | Mar 1995 | A |
5537414 | Takiyasu et al. | Jul 1996 | A |
6381215 | Hamilton et al. | Apr 2002 | B1 |
6437692 | Petite et al. | Aug 2002 | B1 |
6499006 | Rappaport et al. | Dec 2002 | B1 |
6711404 | Arpee | Mar 2004 | B1 |
6799016 | Davis et al. | Sep 2004 | B2 |
6847316 | Keller | Jan 2005 | B1 |
7168022 | Miyake et al. | Jan 2007 | B2 |
7246045 | Rappaport et al. | Jul 2007 | B1 |
7725122 | Balakrishnan et al. | May 2010 | B1 |
7813382 | Manjeshwar et al. | Oct 2010 | B2 |
8396007 | Gonia et al. | Mar 2013 | B2 |
8547906 | Budampati et al. | Oct 2013 | B2 |
8756412 | Pulini et al. | Jun 2014 | B2 |
20020120671 | Daffner et al. | Aug 2002 | A1 |
20020122230 | Izadpanah et al. | Sep 2002 | A1 |
20020152299 | Traversat et al. | Oct 2002 | A1 |
20030109270 | Shorty | Jun 2003 | A1 |
20030206535 | Shpak | Nov 2003 | A1 |
20040230899 | Pagnano et al. | Nov 2004 | A1 |
20040259533 | Nixon et al. | Dec 2004 | A1 |
20040259555 | Rappaport et al. | Dec 2004 | A1 |
20050013294 | Cypher | Jan 2005 | A1 |
20050030905 | Luo et al. | Feb 2005 | A1 |
20050041586 | Jiang | Feb 2005 | A1 |
20050059379 | Sovio et al. | Mar 2005 | A1 |
20050111416 | Ginzburg | May 2005 | A1 |
20050117515 | Miyake | Jun 2005 | A1 |
20050125602 | Fambon et al. | Jun 2005 | A1 |
20050141553 | Kim et al. | Jun 2005 | A1 |
20050201349 | Budampati | Sep 2005 | A1 |
20050228509 | James | Oct 2005 | A1 |
20050281215 | Budampati et al. | Dec 2005 | A1 |
20060002368 | Budampati et al. | Jan 2006 | A1 |
20060045011 | Aghvami et al. | Mar 2006 | A1 |
20060171344 | Subramanian et al. | Aug 2006 | A1 |
20060171346 | Kolavennu et al. | Aug 2006 | A1 |
20060227729 | Budampati et al. | Oct 2006 | A1 |
20060256740 | Koski | Nov 2006 | A1 |
20060274644 | Budampati et al. | Dec 2006 | A1 |
20060274671 | Budampati et al. | Dec 2006 | A1 |
20060287001 | Budampati et al. | Dec 2006 | A1 |
20070030816 | Kolavennu | Feb 2007 | A1 |
20070030832 | Gonia et al. | Feb 2007 | A1 |
20070073861 | Amanuddin et al. | Mar 2007 | A1 |
20070076638 | Kore et al. | Apr 2007 | A1 |
20070077941 | Gonia et al. | Apr 2007 | A1 |
20070087763 | Budampati et al. | Apr 2007 | A1 |
20070091824 | Budampati et al. | Apr 2007 | A1 |
20070091825 | Budampati et al. | Apr 2007 | A1 |
20070153677 | McLaughlin et al. | Jul 2007 | A1 |
20070155423 | Carmody et al. | Jul 2007 | A1 |
20070237137 | McLaughlin | Oct 2007 | A1 |
20070280178 | Hodson et al. | Dec 2007 | A1 |
20080074993 | Vainola | Mar 2008 | A1 |
20080075000 | Robbins | Mar 2008 | A1 |
20080125647 | Rosengren et al. | May 2008 | A1 |
20080144493 | Yeh | Jun 2008 | A1 |
20080238561 | Otsuka et al. | Oct 2008 | A1 |
20080273547 | Phinney | Nov 2008 | A1 |
20090006010 | Van Sloun et al. | Jan 2009 | A1 |
20090037998 | Adhya et al. | Feb 2009 | A1 |
20090060192 | Budampati et al. | Mar 2009 | A1 |
20090265143 | Kaufman et al. | Oct 2009 | A1 |
20100070634 | Ranjan et al. | Mar 2010 | A1 |
20140036712 | Dewey | Feb 2014 | A1 |
Number | Date | Country |
---|---|---|
10314721 | Nov 2004 | DE |
1401171 | Mar 2004 | EP |
1401171 | May 2005 | EP |
2427329 | Dec 2006 | GB |
WO0135190 | May 2001 | WO |
WO0135190 | May 2001 | WO |
WO 03079616 | Sep 2003 | WO |
WO 03089995 | Oct 2003 | WO |
WO 2004047385 | Jun 2004 | WO |
WO 2006017994 | Feb 2006 | WO |
WO 2006053041 | May 2006 | WO |
WO 2007143409 | Dec 2007 | WO |
WO 2007143420 | Dec 2007 | WO |
WO 2007143421 | Dec 2007 | WO |
WO 20071143419 | Dec 2007 | WO |
WO 2004032392 | Apr 2015 | WO |
Entry |
---|
Non-Final Rejection dated Jul. 8, 2009 in connection with U.S. Appl. No. 11/799,171; 27 pages. |
Final Rejection dated Feb. 5, 2010 in connection with U.S. Appl. No. 11/799,171; 31 pages. |
Non-Final Rejection dated Sep. 1, 2010 in connection with U.S. Appl. No. 11/799,171; 27 pages. |
Non Final Rejection dated Feb. 22, 2011 in connection with U.S. Appl. No. 11/799,171; 26 pages. |
Final Rejection dated Jun. 13, 2011 in connection with U.S. Appl. No. 11/799,171; 27 pages. |
Non-Final Rejection dated Feb. 1, 2012 in connection with U.S. Appl. No. 11/799,171; 26 pages. |
Final Rejection dated May 15, 2012 in connection with U.S. Appl. No, 11/799,171; 27 pages. |
Non-Final Rejection dated Jul. 21, 2010 in connection with U.S. Appl. No. 11/880,116; 7 pages. |
Non-Final Rejection dated Oct. 5, 2013 in connection with U.S. Appl. No. 12/106,606; 21 pages. |
Final Rejection dated Feb. 2, 2011 in connection with U.S. Appl. No. 12/106,606; 21 pages. |
Advisory Action dated Apr. 25, 2011 in connection with U.S. Appl. No. 12/106,606; 3 pages. |
Non-Final Rejection dated May 12, 2011 in connection with U.S. Appl. No. 12/106,606; 21 pages. |
Final Rejection dated Nov. 10, 2011 in connection with U.S. Appl. No. 12/106,606; 20 pages. |
Advisory Action dated Jan. 30, 2012 in connection with U.S. Appl. No. 12/106,606; 3 pages. |
Non-Final Rejection dated Mar. 30, 2012 in connection with U.S. Appl. No. 12/762,215; 12 pages. |
Final Rejection dated Sep. 20, 2012 in connection with U.S. Appl. No. 12/762,215; 14 pages. |
Non-Final Rejection dated Mar. 1, 2013 in connection with U.S. Appl. No. 12/762,215; 16 pages. |
Non-Final Rejection dated Sep. 9, 2013 in connection with U.S. Appl. No. 12/762,215; 16 pages. |
Non-Final Rejection dated Nov. 11, 2012 in connection with U.S. Appl. No. 13/077,692; 8 pages. |
Final Rejection dated Mar. 26, 2013 in connection with U.S. Appl. No. 13/077,692; 10 pages. |
International Search Report in connection with PCT/US2007/069717 filed May 25, 2007; 3 pages. |
Written Opinion in connection with PCT/US2007/069717 filed May 25, 2007; 5 pages. |
International Search Report in connection with PCT/US2007/069614 filed May 24, 2007; 22 pages. |
Written Opinion in connection with PCT/US20047/069614 filed May 24, 2007; 5 pages. |
International Search Report in connection with PCT/US2007/069710 filed May 25, 2007; 3 pages. |
Written Opinion in connection with PCT/US2007/069710 filed May 25, 2007; 6 pages. |
International Search Report in connection with PCT/US2007/069705 filed May 25, 2007; 3 pages. |
Written Opinion in connection with PCT/US2007/069705 filed May 25, 2007; 5 pages. |
International Search Report in connection with PCT/DE2003/03848 filed Nov. 11, 2003; 6 pages. |
International Search Report in connection with PCT/CN2005/001295 filed Aug. 18, 2005; 4 pages. |
International Search Report in connection with PCT/US2000/31166 filed Nov. 13, 2000; 3 pages. |
Intemational Search Report in connection with PCT/US2005/040591 filed Nov. 8, 2005; 3 pages. |
International Search Report in connection with PCT/2003/005573 filed Mar. 5, 2003; 3 pages. |
IEP Search Report in connection with EP 1401171 A3; Mar. 4, 2005; Sick AG; 2 pages. |
GB Search Report in connection with GB 2427329 A: Sep. 21, 2006; 1 page. |
Pulini, et al.; “Apparatus and Method for Measuring and Reporting Redundant Wireless Connectivity Over Time”; U.S. Appl. No. 13/947,951, filed Jul. 22, 2013; 40 pages. |
Pulini, et al.; “Apparatus and Method for Reporting of Communication Path Quality Within a Wireless Network”; U.S. Appl. No. 13/948,077, filed Jul. 22, 2013; 40 pages. |
Aiello, et al.; “Wireless Distributed Measurement System by Using Mobile Devices”; IEEE; Intelligent Data Acquisition and Advanced Computing Systems; Sep. 5-7, 2005; 4 pages. |
Chen, et al.; “Dependability Enhancement for IEEE. 802.11 Wireless LAN with Redundancy Techniques”; International Conference on Dependable Systems and Networks; 2003, 8 pages. |
Kolavenna, Dr. S.; “WNSIA MAC Layer”; Presentation at ISA SP100 Meeting; Feb. 14, 2007; 24 pages [see especially p. 17]. |
Pereira, J.M. Dias; “A Fieldbus Prototype for Educational Purposes”; IEEE Instrumentation & Measurement Magazine; New York, NY; vol. 7, No. 1; Mar. 2004; 8 pages. |
“Service Manual: SmartRadar FlexLine”; Honeywell Enraf; http://www.honeywell.com/ps; 2012; 4 pages. |
“Connect802”; Network Orange; http://www.netorange.com/products/connect802/suite—spot—survey/tt—connect802—survey.html; 2008; 3 pages. |
Screenshot of Honeywell OneWireless R120 User Interface; released Jun. 2009; 1 page. |
Number | Date | Country | |
---|---|---|---|
20150350921 A1 | Dec 2015 | US |