Infrastructure monitoring devices, systems, and methods

Information

  • Patent Grant
  • 10857403
  • Patent Number
    10,857,403
  • Date Filed
    Wednesday, November 6, 2019
    5 years ago
  • Date Issued
    Tuesday, December 8, 2020
    4 years ago
Abstract
An infrastructure monitoring assembly includes a fire hydrant; a pipe connected in fluid communication with the fire hydrant, a fluid at least partially filling the pipe; a sensor positioned in the fluid, the sensor configured to measure a parameter of the fluid; and a processor connected in communication with the sensor, the processor configured to receive a signal from the sensor.
Description
FIELD

The disclosure is directed to devices, systems, and methods related to monitoring and controlling an infrastructure such as, but not limited to, the supply and use of commercial, industrial or residential water, gas and/or electric utilities, and, in particular, to devices, methods, and systems for monitoring and controlling a municipality and alerting a user to potential faults and actions required.


BACKGROUND

Municipalities administer and/or outsource numerous utility and safety systems within each municipality. Such systems are usually complex infrastructures and include but are not limited to water distribution, gas distribution, electricity distribution, waste management, traffic control, fire departments, police departments, and emergency response departments. Each of these systems needs to be monitored for use (authorized or unauthorized), faults, tampering, events, interruptions or blockages, leaks, contamination, and/or other issues.


To obtain an understanding of the state of any one system, or for ordinary use, billing or repair purposes, personnel must typically be sent into the municipality to check for problems within the system manually. This process is slow, is labor-intensive, and can lead to overlooked problems. Furthermore, preferred aspects of the system may be evaluated irregularly or infrequently, thereby allowing a problem to go unchecked for long periods of time. By way of example, a leak in a water main may cost a water company a significant amount of money in lost water, energy usage, and chemical treatment, particularly if the leak is not discovered for a relatively long period of time. Furthermore, a leak can lead to underground structural erosion. Interference with a system may go unnoticed unless it is reported to a central location.


Another problem and disadvantage associated with current systems is the lack of property rights sufficient to maintain a network of monitors and device controllers capable of creating a transmission infrastructure that can adapt to multiple monitors and controllers and form an information network for providing information about the system to the utility monitoring the network. For example, some networks require that new poles or towers be erected for placement of the communication devices. Municipalities may have to rent space on a utility company's poles for placement of such devices.


Furthermore, an issue in one system may cause an issue in another system. For example, a fire reported to the fire department may require the gas company to turn off gas flow to the vicinity of the fire and may require the water company to redirect water or additional water pressure to the vicinity. However, many current systems are not interoperable.


It is, therefore, desirable to have a single system that can monitor different aspects of at least one municipality system continuously and communicate with several entities at the same time.


SUMMARY

The disclosed methods, systems, and devices overcome the problems and disadvantages associated with current strategies and systems and provides new systems and methods of monitoring municipality infrastructure.


One embodiment is directed to an infrastructure monitoring system. The system includes an operations center and two or more communications devices communicatively coupled to the operations center. At least one communications device of the plurality of communications devices is coupled to a component of the infrastructure, and at least two communications devices are monitoring devices. The first monitoring device monitors a first aspect or location of the infrastructure and the second monitoring device monitors a second aspect or location of the infrastructure.


In one embodiment each monitoring device includes at least one sensor sensing at least one condition within the infrastructure, at least one data storage device storing data sensed by the at least one sensor, at least one transceiver device adapted to transmit and receive data, and at least one processor communicatively coupled to at least one sensor, data storage device, and transceiver device.


In one embodiment, the operations center and the plurality of communications devices are wirelessly communicatively coupled. At least one communications device is an output device. The output device includes a transceiver device adapted to receive or to transmit data, at least one output port, and a processor communicatively coupled to at least one of the transceiver device and at least one output port.


In one embodiment, the operations center and at least one output device are wirelessly communicatively coupled. Each communications device is adapted to receive transmissions for a second communications device and to retransmit the transmission to the second communications device. Each communications device is adapted to receive transmissions for the operations center and to retransmit the transmission to the operations center.


In one embodiment, at least one output device is coupled to at least one of an actuator control device, an alarm, a Radio-Frequency Identification device and a tamper prevention device.


In one embodiment, a monitoring device and an output device are contained within the same unit. The monitoring device and the output device share at least one of a power source, a transceiver device, and a processor.


The infrastructure can be at least one of a water distribution system, an electricity distribution system, a gas distribution system, a traffic control system, and an emergency response system. The system can monitor for at least one of use of gas, use of water, use of electricity, tampering, leaks, GPS location, proximity, tilt, smoke, temperature, rust, corrosion, fluid flow, pressure, water quality, air quality, contamination, radiation, pH, infrastructure status, and motion.


In one embodiment, the system produces an alert when at least one monitoring device registers an event. In one embodiment, at least one monitoring device is coupled to a visual or acoustical device. The operations center may include multiple operations centers. Each operations center is uniquely located. The operations center can monitor a plurality of infrastructures concurrently.


The plurality of infrastructures are selected from the group consisting of water systems, electrical systems, gas systems, emergency response systems, traffic control systems, and combinations thereof. A component of the infrastructure is one of a fire hydrant, a utility meter, a manhole cover, a utility pole, a valve, a pipe, a traffic light, water tower, water tank, valve box, valve box cover, meter box, meter box cover, and a smoke detector. In various embodiments where the component of the infrastructure is a fire hydrant, the communications device coupled to the fire hydrant is a repeater. At least one portion of the fire hydrant can be comprised of a material that does not interfere with the communications of the communications device. Moreover, the communications device coupled to the fire hydrant may be positioned within one of a nozzle cap, a pumper nozzle, a hose nozzle, a fire truck hookup, and a bonnet.


Another embodiment is directed to another infrastructure monitoring system. The system includes an operations center and a plurality of communications devices communicatively coupled to the operations center. At least one communications device of the plurality of communications devices is coupled to a fire hydrant, a valve, a valve box, a valve box cover, a meter, a meter box, a meter box cover, a water tower, a water tank, a pumper nozzle, a hose nozzle, or a manhole cover.


In one embodiment, the communications device coupled to the fire hydrant is one of a monitoring device, an output device, and a repeater. At least one portion of the fire hydrant is comprised of a material that does not interfere with the communications. In one embodiment, the communications device coupled to the fire hydrant is positioned within one of the nozzle cap, the pumper nozzle, the hose nozzle, the fire truck hookup, and the bonnet.


Another embodiment is directed to a fire hydrant. The fire hydrant includes a bonnet and a communications device coupled to the bonnet. The communications device is an element of an infrastructure monitoring system.


In another embodiment, an infrastructure monitoring assembly can comprise a fire hydrant; a pipe connected in fluid communication with the fire hydrant, a fluid at least partially filling the pipe; a sensor positioned contacting the fluid, the sensor configured to measure a parameter of the fluid; and a processor connected in communication with the sensor, the processor configured to receive a signal from the sensor.


In another embodiment, a method for monitoring an infrastructure network can comprise positioning a sensor in contact with a fluid, the fluid at least partially filling a pipe of the infrastructure network, the pipe connected in fluid communication with a fire hydrant of the infrastructure network; measuring a parameter of the fluid with the sensor; receiving a signal from the sensor with a processor, the signal conveying information about the parameter; and transmitting the information from an antenna to an operation center, the antenna connected in wireless communication with the operation center, the antenna connected in electrical communication with the processor.


In another embodiment, an infrastructure monitoring system can comprise an infrastructure network comprising a fire hydrant and a pipe, the pipe connected in fluid communication with the fire hydrant, the pipe at least partially filled with a fluid; a monitoring device comprising a sensor, a processor, and an antenna, the processor connected in communication with the sensor and the antenna, the sensor positioned in contact with the fluid; and an operation center connected in communication with the monitoring device.


Other embodiments and advantages are set forth in part in the description, which follows, and in part, may be obvious from this description, or may be learned from practice.





DESCRIPTION OF THE DRAWINGS

The figures shown and described in greater detail are provided by way of example only.



FIG. 1 is a schematic of one embodiment of the disclosed system.



FIG. 2 is a schematic of one embodiment of a monitoring device.



FIG. 3 is a schematic of one embodiment of a control device.



FIG. 4A is an exploded view of one embodiment of a device of the disclosure as housed within a fire hydrant.



FIG. 4B is a perspective view of a device of the disclosure attached to a fire hydrant



FIG. 5A is a perspective view of one embodiment of an insulation device for sealing the bonnet of the fire hydrant from the water within the fire hydrant.



FIG. 5B is a perspective view of one embodiment of an insulation device and bonnet.



FIG. 6A is a perspective view of one embodiment of a nozzle cap for attachment to a fire hydrant.



FIG. 6B is a sectional view of one embodiment of the nozzle cap of FIG. 6A.



FIG. 6C is a sectional view of one embodiment of the nozzle cap of FIG. 6A.





DESCRIPTION

As embodied and broadly described herein, the disclosures herein provide exemplary embodiments of the disclosed systems, methods, and devices. Features may be embodied in various and alternative forms. Therefore, there is no intent that specific structural and functional details should be limiting, but rather the intention is that they provide a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure.


A problem in the art capable of being solved by the embodiments disclosed is monitoring and maintaining an infrastructure. It has been discovered that monitoring devices with one or two way communication abilities can be used to detect faults in the municipality's systems and provide on-demand, real time, or near real time device status, maintenance, and control over the systems.


A network of monitoring devices is capable of providing a system administrator with a full picture of the current state of the system. The network includes an array of different monitoring devices each capable of sensing at least one condition. The monitoring devices may be capable of sending data to and of receiving data from at least one operations center. Communication from the remote monitoring device may be directed to a central monitoring facility, to one of a number of regional monitoring centers, to a user, and/or to a research facility. Furthermore, the system includes at least one control device. Each control device is adapted to control a different aspect of the system. The control devices may be part of the monitoring devices or may be separate units. Communication is over the Internet, but may be over a private network, a local area network, or a wide area network. The communication involves a wireless component, such as from the remote monitoring device and/or control device to a regional monitoring facility or to distributed monitors. Also, the communications are secured or encrypted such that the communications system cannot be monitored by another unknown party. Access to the system is granted through user names and passwords, although additional and/or alternate encryption methods can be employed.


One embodiment is directed to water infrastructure systems. In such systems, monitoring devices can be located throughout the system, for example, as attachments to component parts, for feedback to a network that can provide real-time information to the utility operating the network. The network operators can use the information transmitted to activate controlling devices on the network, or to dispatch repair or other services as directed by the information provided by the network. For example, if water pressure monitors on a water meter indicate a variance between locations, a water leak can be reported using the network, and controlling devices can divert water. Pressure meters can be attached to fire hydrants to monitor and report pressure losses throughout the system, providing real-time information to benefit the users of the fire hydrants (fire departments who need to be assured of adequate pressure), the users of the system (water consumers who will be affected by lower pressure), and the operators of the system (who suffer asset loss as a result of lack of real-time information about losses).



FIG. 1 depicts a system 100 for monitoring, controlling, and communicating with at least one monitoring device 110 and/or at least one control device 111. System 100 includes an operations center 105 in communication with at least one monitoring device 110 and/or one control device 111. In the preferred embodiment, there is bi-directional communication between operations center 105 and devices 110 and 111. Communications can be simplex or duplex. Communication can occur over any communications network 115 known in the art, including but not limited to wired networks, wireless networks, Zigbee networks, Bluetooth networks, Z-wave networks, WiFi networks, WiMax networks, RF networks, local area networks (LAN), internet networks, wide area networks (WAN), cellular telephone network, hardwired telephone networks, 900 MHz wireless networks, and satellite networks. In one embodiment, the network is a fixed network. For example, the fixed network can be a mesh network or a star network. Additionally, devices 110 and 111 and operations center 105 can be in direct communication or can communicate through an intermediary device, such as a relay, a repeater, a gateway, or other device capable of receiving and retransmitting a message.


Each monitoring device 110 monitors at least one aspect of the infrastructure. The monitored aspect can be one or more of the components of the infrastructure (e.g. pipe conditions, valve conditions, fire hydrant conditions, service line conditions, meter conditions, power line conditions, and battery conditions), commodity conditions (e.g. fluid or gas flow, fluid or gas pressure, fluid or gas temperature, and fluid or gas contaminants), or combinations thereof. Additionally, each monitoring device 110 can be self monitoring. For example the monitoring devices 110 determine if there is a loss of communication, low battery levels, and/or internal damage (e.g. short circuits due to water damage). Additionally, each monitoring device 110 can be structurally stable (e.g. fixed to a valve, pipe, utility pole, a hydrant, a valve box, a valve box cover, a meter, a meter box, a meter box cover, a water tower, a water tank, a pumper nozzle, a hose nozzle, or an manhole cover) or movable (e.g. allowed to move with or within the flow of water or gas in the pipes).


For example, a monitoring device 110 or 111 can be coupled to a fire hydrant 405, a seen in FIG. 4B. The monitoring device 110 or 111 can be located within a nozzle cap 600 (i.e. in the pumper nozzle, the hose nozzle, or in the fire truck hook up), within a body of the fire hydrant, within a bonnet, attached to an outside of the fire hydrant, or at another location on or within the fire hydrant. A housing for the monitoring device 110 or 111 is made of plastic, nylon, other synthetic or natural materials, or any other material that does not block transmissions to and from the monitoring device 110 or 111. For example, as shown in FIG. 4A, the fire hydrant bonnet 400 can contain a monitoring device 110 and a waterproof container 420 for the monitoring device 110. In some embodiments the fire hydrant bonnet 400 can also contain a power source 425. In another example, as shown in FIG. 4B, the monitoring device 110 can be coupled to the outside of a fire hydrant 405. In another embodiment, shown in FIGS. 5A and 5B, the bonnet 500 of a fire hydrant 505 can be isolated from the flow of water within the fire hydrant 505. For example, there can be a plastic, metal, or other material disc 530 that seals off a portion of the fire hydrant 505 to prevent water from reaching the interior regions of the bonnet 500.


In another embodiment, a monitoring device 110 or control device 111 is positioned within a nozzle cap 600 of a fire hydrant. A fire hydrant nozzle cap 600 is a device attached to an outlet nozzle and covers a nozzle opening. The nozzle cap 600 is furnished with a nut 605 or other device to permit the application of force to firmly attach the nozzle cap 600 to or to remove it from the outlet nozzle. FIG. 6A depicts an isometric view of an embodiment of the nozzle cap 600. In one embodiment, nozzle cap 600 is made of a composite, plastic, nylon, other synthetic or natural materials, or any other material that does not block transmissions to and from the monitoring device 110 or control device 111. The material has the same fading characteristics of the paint used on the exterior of the fire hydrant. For example, the material can have the same resistance to water, UV rays, corrosion, oxidation, or other causes of fading. Thereby, the paint and the nozzle cap 600 appear to be of the same material.



FIGS. 6B and 6C depict cutaway views of an embodiment of the nozzle cap 600. The nozzle cap 600 has an enclosure 610 which creates a cavity into which monitoring device 110 or control device 111 may be located. The cavity is enclosed by a cover 615. The enclosure 610 and cover 615 create a water tight seal able to withstand water pressures in excess of 400 psi. In various embodiments, other pressures may be utilized. Additionally, in one embodiment, nozzle cap 600 has an antenna cover 620. Antenna cover 620 can be made of the same material as nozzle cap 600 or of a different material. The location of the antenna is kept away from metal to achieve greater efficiency.


Nozzle hydrant threading 625 is provided as a connection means between the nozzle cap 600 and the fire hydrant. The nozzle cap 600 also includes enclosure threading 630 as a connection means for the enclosure 610 to connect to the nozzle cap 600. The enclosure 610 also includes connection threading 640 designed to mate with the enclosure threading 630. An antenna 650 is shown.


Each node in the network 115 detects errors in transmissions. Error detection can use cyclic redundancy codes using a table based on a defined polynomial or another method of error detection. In alternative embodiments, transmissions can be rerouted if the primary route is blocked or otherwise unavailable. Furthermore, devices 110 and 111 can confirm receipt of a message, e.g. via a hand shake protocol. In instances where confirmation is not received, the message can be resent along the same route or rerouted.


In various embodiments, each monitoring device 110 and each control device 111 is assigned a unique identifier. The unique identifier can be related to the devices' geographical locations, street addresses, order of installation, or any other method of identifying the devices 110,111. Furthermore, different types of devices 110 and 111 can have unique identifiers that include keys that are unique to that type of device. For example, the identifier for all water meters may begin with a WM, while the identifier for all leak detectors may begin with an LD. Each communication to and from a monitoring device 110 and control device 111 may include the unique identifier so that the message is received by the correct monitoring device 110 or control device 111, or so that operations center 105 can determine from where the message was sent.


Each monitoring device 110 and each control device 111 can be retrofitted to an existing system 100 or device 110,111, can be coupled to a new system 100 or device 110,111, or can be integrated into a new system 100 or device 110,111. For example, the system 100 can be connected to, work with, or work independently of a Supervisory Control and Data Acquisition (SCADA) network. In one embodiment, each monitoring device 110 and each control device 111 has a set of adapters to facilitate coupling the monitoring device 110 or control device 111 to a new or existing system 100 or device 110,111.


In one embodiment, system 100 is divided into sectors with each sector having at least one monitoring device 110 and/or at least one control device 111. Each sector can communicate directly with operations center 105 or each sector can have at least one intermediary communications device that is in communication with the monitoring device 110 and/or control device 111 and operations center 105. In one embodiment, the sectors are divided up by geographical location. For example, all of the devices in one neighborhood can be in a single sector and there is one sector for each neighborhood. In one embodiment, one intermediary communications device can service multiple sectors.


In alternative embodiments, each monitoring device 110 and/or control device 111 can communicate with adjacent monitoring devices 110 and/or control devices 111. In such embodiments, each monitoring device 110 and/or control device 111 can act as a transceiver or relay by receiving messages intended for another device 110,111 or for the operations center 105 and forwarding the message. In embodiments where the system 100 is divided into sectors, monitoring devices 110 and control devices 111 can communicate only within their sector. In other embodiments, monitoring device 110 and control device 111 can communicate with devices 110,111 in other sectors. Each monitoring device 110, control device 111, and/or the operations center 105 may be able to determine if a transmitted message was received by the intended device 110,111 and, if not, may be able to reroute the message until the message is properly received. Additionally, relay devices can be implemented in the system to further extend the range of communications. For example, relay devices can be placed on utility poles, on municipal buildings, within fire hydrants, and/or under manhole covers. In alternative embodiments, devices 110 and 111 communicate over a mesh network. In the mesh network, devices 110 and 111 can communicate with other devices 110 and 111 within the mesh network. Operations center 105 can set specified communications pathways derived from routing tables.


Operations center 105 can be located at a municipality office, a private or public company, a fire station, a police station, or any other entity that monitors operations center 105. In other embodiments, operations center 105 can be remotely hosted and accessible by the Internet. In such embodiments, operations center 105 can take advantage of cloud computing (e.g. a network of remotely hosted computers, servers, and data storage devices). Compared to non-remotely hosted computer networks, cloud computing can increase ease of use, increase access, increase security, decrease costs, be custom tailored, and provide an unrestricted expansion of storage space. Additionally, in various embodiments, there is a plurality of operations centers 105. One or more operations centers 105 can be located at different entities and each operations center 105 can monitor a different aspect of system 100. For example, in embodiments where one monitoring device 110 monitors water usage and another monitors gas leaks, the water usage aspect can be monitored by a water utility company and the gas leaks can be monitored by the gas utility company and/or the fire department. In some embodiments, there are redundant operations centers 105, where at least two operations centers 105 monitor the same aspect of system 100. Operations center 105 can send transmissions to update the firmware of devices 110 and 111.



FIG. 2 is a schematic of a monitoring device unit 200. Monitoring device unit 200 includes a processor 205. Processor 205 is coupled to at least one input port 210 for receiving data from sensors 215. Processor 205 is also coupled to a transceiver 220 for sending and receiving signals. Processor 205 is coupled to a data storage unit 230. Data storage unit 230 can hold a predetermined amount of data received from the sensors 215. For example, data storage unit 230 can hold data for a predetermined amount of time (e.g. one day, one week, or one month), can hold a predetermined number of readings (e.g. 10 readings, 100 readings, 1000 readings), or can hold data until directed to purge the data by the operations center 105. Additionally, data storage unit 230 can hold instructions for processor 205 to execute upon prompting from the operations center 105. Processor 205 compiles at least some of the data stored in data storage unit 230 for transmitting to the operations center 105.


Each monitoring device unit 200 may collect data and/or transmit data continuously, at specific intervals, or randomly. In embodiments where the monitoring device unit 200 collects and transmits data in a non-continuous configuration, monitoring device unit 200 may turn off or reduce power consumption during the non-data collecting periods to save energy. Processor 205 is coupled to a power source 235. Power source 235 can be a unit capable of powering processor 205 and devices attached to processor 205. For example, power source 235 can be a battery, solar panel array, wind turbine, water turbine, electrical lines, or combinations thereof. In preferred embodiments, there is also a backup power source, such as a battery. The power may derive from the operation of the system 100.


In one embodiment, processor 205 is coupled to at least one sensor 215 that monitors at least one condition associated with the monitoring device. Sensors 215 can determine the status of a device. Sensors 215 can be directly wired to processor 205 or can use wireless communication to send and receive signals from processor 205. Sensors 215 can be positioned within the monitoring device or be external to the monitoring device. In alternative embodiments, sensors 215 are positioned remote from the monitoring device. For example a sensor can be positioned in a fire hydrant, on a nearby building, or on a utility pole. In the embodiments in which sensors 215 and processor 205 communicate wirelessly, the same communications protocol can be used in the sensor/processor communication as in the processor/operations center communication, or different communications protocols can be used in the sensor/processor communication from in the processor/control center communication. For example, the sensor/processor communications can use RF protocols while the processor/control center communications can be over a wired network.


In one embodiment, sensor 215 is a use monitor. In such embodiment, the use monitor records the amount of water, gas, electricity, or other commodity that is used by a customer over a specified period of time. The use monitor can continuously record the amount of the commodity used or the use monitor can provide a signal to processor 205 that the commodity is in use. Processor 205 can transmit a signal to the operations control to alert the operations center 105 that the monitoring device 110 is being used and/or how much of the commodity is flowing through the sensor 215. The operations center 105 can request a reading from the use monitor on demand. The processor 205 or the operations center 105 can determine based on the use, if there is unauthorized use of the commodity. Upon detection of unauthorized use, at least one of processor 205 or the operations center 105 can generate an alarm that there is unauthorized use. For example, in embodiments where the use monitor is coupled to a fire hydrant 405, if the use monitor indicates that the fire hydrant 405 is in use, however no fire is reported, the operations center 105 can disseminate an alert that there is potential misuse of the fire hydrant 405.


In various embodiments, at least one sensor 215 is a tamper sensor. The tamper sensor can be a motion detector, a contact sensor, a rotation sensor, a touch sensor, a proximity sensor, a biofeedback sensor, a temperature sensor, a capacitance sensor, a resistance sensor, or any other sensor that is able to detect the presence of an object. The tamper sensor can send a message to processor 205 when the tamper sensor detects an event. The processor 205 will then evaluate the event to determine if a device being monitored is being tampered with or will relay the message to the operations center 105 for evaluation. The monitored device can be a fire hydrant, utility meter, valve, manhole cover, pump, or any other device that may be tampered with. Upon detection of a tamper event, at least one of processor 205 and the operations center 105 can generate an alarm that the device is being tampered with. The monitoring device may activate a tamper prevention device (described below). The operations center 105 will send a transmission to processor 205 telling processor 205 to disregard messages from the tamper sensor for a predetermined period of time or until another message is received from the operations center 105 telling processor 205 to resume monitoring for tamper events. For example, if a fire department needs to use a fire hydrant, the operations center 105 will send a message to processor 205 to temporarily disregard any tamper events. Once the fire department is finished using the fire hydrant the operations center 105 will send a message to processor 205 to start monitoring for tamper events again.


In some embodiments at least two of sensors 215 are leak detectors. Each leak detector can include an in-pipe leak detector and/or an exterior leak detector. In gas applications, the leak detectors are vapor sensors. While in liquid applications, the leak detectors use acoustic monitoring to determine presence and location of a leak. The energy generated from a leak is transmitted within a pipe through the commodity as well as through the pipe wall. Each leak detector can detect the vibrations made by the leak in the commodity or the pipe wall, joint or service line. To determine the location of a leak, at least two detectors must detect the same leak. Based on the velocity of the sound traveling along the pipe (V), the distance between the two detectors (D) and the delay between the times each detector detects the sound (T), the location of the leak (L) can be determined by the following equation:

L=(D−(V×T))/2


When using the above equation, the typical velocity of sound in water is about 1500 m/s while the typical speed of sound through an iron pipe is 5100 m/s. The velocity can be measured empirically. For example, if the leak is exactly midway between the two detectors the sound would reach both detectors at the same time. Each detector may monitor continuously or at predetermined periods of time. The leak detectors can send a message to processor 205 when the leak detectors detect an event. The processor 205 can then evaluate the event to determine if there is a leak and how severe the leak is or can relay the message to the operations center 105 for evaluation. Upon detection of a leak event, at least one of processor 205 or the operations center 105 can generate an alert that there is a leak if the leak is determined to be severe enough to warrant attention.


In various embodiments, at least one sensor 215 is a smoke detector. The smoke detector can be a photoelectric detector, an ionization detector, or any other device that can detect the presence of smoke. The smoke detector can be located within the monitoring device or exterior to the monitoring device. The smoke detector monitors continuously for smoke. The smoke detector can send a message to processor 205 when the smoke detector detects an event. The processor 205 can then evaluate the event to determine if there is smoke or can relay the message to the operations center 105 for evaluation. Upon detection of smoke, at least one of processor 205 or the operations center 105 can generate an alert that there is smoke.


In some embodiments, at least one sensor 215 is a temperature sensor. The temperature sensor can be a contact sensor (e.g. thermocouples, thermistors, liquid-in-glass thermometers, resistance temperature detectors, filled system thermometers, bimetallic thermometers, semiconductor temperature sensors, and phase change indicators) or a non-contact sensor (e.g. radiation thermometers, thermal imagers, ratio thermometers, optical pyrometers, and fiber optic thermometers). The temperature sensor can be located within the monitoring device or exterior to the monitoring device. In one embodiment, the temperature sensor monitors continuously for the temperature to rise above or drop below a predetermined threshold. The temperature sensor can send a message to processor 205 when the temperature sensor detects a temperature beyond the thresholds. The processor 205 can then evaluate the event to determine if there the temperature is a problem (such as freezing pipes or fire) or can relay the message to the operations center 105 for evaluation. Upon detection of undesirable temperatures, at least one of processor 205 or the operations center 105 can generate an alert that there is an undesirable temperature condition.


In various embodiments, at least one sensor 215 is a rust and/or corrosion sensor. The corrosion sensor can detect rust and/or corrosion using any method known in the art, including but not limited to liquid penetration inspection, magnetic particle inspection, radiographic inspection, visual inspection, eddy current inspection, ultrasonic inspection, and thermographic inspection. The corrosion sensor can send a message to processor 205 when the corrosion sensor detects a rust or corrosion beyond a threshold value. The processor 205 can then evaluate the rust or corrosion to determine if there is a problem or can relay the message to the operations center 105 for evaluation. Upon detection of undesirable rust or corrosion, at least one of processor 205 or the operations center 105 can generate an alert that there is an undesirable amount of rust or corrosion.


In various embodiments, at least one sensor 215 is a fluid flow sensor. The fluid flow sensor can be used either in gas systems or liquid systems. The fluid flow sensor can detect direction of the flow, turbidity of the flow, velocity of the flow, density of the flow, viscosity of the flow, and/or any other aspect of the flow. The fluid flow sensor may be a velocimeter, a laser-based interferometer, a vane, a rotary potentiometer, a Hall effect sensor, a device to measure heat transfer caused by the flowing fluid, or any other device know in the art to measure the flow of fluid. The fluid flow sensor can send a message to processor 205 when the fluid flow sensor detects a flow anomaly. The processor 205 can then evaluate the event to determine if the anomaly is a problem or can relay the message to the operations center 105 for evaluation. Upon detection of an anomaly, at least one of processor 205 and the operations center 105 can generate an alert that there is an anomaly.


In various embodiments, at least one sensor 215 is a pressure sensor. In one embodiment, the pressure sensor is positioned within the flow of fluid or area in which the pressure is being sensed. For example, the pressure sensor can be positioned at the base of a fire hydrant and in the water to determine the water pressure within water system, in a pipe to determine gas or water pressure within a gas or water system, or in a room to determine air pressure within the room. The pressure sensor can be a piezoresistive strain gauge, a capacitive gauge, an electromagnetic gauge, a piezoelectric device, or any other device know in the art to measure pressure. The pressure sensor can send a message to processor 205 when the pressure sensor detects a pressure anomaly. The processor 205 can then evaluate the event to determine if the anomaly is a problem or can relay the message to the operations center 105 for evaluation. Upon detection of an anomaly, at least one of processor 205 or the operations center 105 can generate an alert that there is an anomaly.


In various embodiments, at least one sensor 215 is a water quality monitor. The water quality monitor can monitor a single aspect of water flowing through the system 100 or multiple aspects of the water. For example, the water quality monitor can monitor one or more of the water's bacteria levels, pharmaceutical levels, alkalinity, chlorine and/or chloramine levels, hardness, pH levels, peroxide content, iron levels, nitrate levels, nitrite levels, arsenic levels, pollution levels, oxygen levels, biomass levels, and/or any of the other contaminants regulated by the Environmental Protection Agency (EPA). In embodiments where there are multiple monitoring devices, all the devices can monitor the same aspects, each device can monitor a different aspect, or a combination thereof. In one embodiment, the water quality monitors test the water continuously, however, in alternative embodiments, the water quality monitors test the water at predetermined time intervals (e.g. once a hour, once a day, once a week, etc.). Each water quality monitor relays data to processor 205. Processor 205 can store the data on data storage unit 230 or transmit the data to the operations center 105. Either processor 205 or the operations center 105 can monitor the data received from the water quality monitors to determine if there is a change in the levels of the contaminants or if the levels of the contaminants rise above a threshold level. Upon detection of unsafe contamination levels, at least one of processor 205 or the operations center 105 can generate an alert that there is contamination in the water system.


In the embodiments where at least two monitoring devices are monitoring the same aspect of the water, the operations center 105 can determine if there is a change in the aspect of the water from the location of one monitoring device to the location of the other. If there is a change, the operations center 105 can generate an alert that there is a change in the water system and output the approximate location of the change in the water system.


In various embodiments, at least one sensor 215 is an air quality monitor. The air quality monitor can monitor a single aspect of the air or multiple aspects of the air. Furthermore, the air quality monitor can monitor the air within a facility or ambient air. For example, the air quality monitor can monitor one or more of the air's benzene levels, carbon disulfide levels, urethane levels, formaldehyde levels, phosphorus levels, naphthalene levels, parathion levels, quinoline levels, trifluralin levels, and/or any of the other contaminants whose acceptable levels have been set by the Environmental Protection Agency. In embodiments where there are multiple monitoring devices, all the devices can monitor the same aspects or each device can monitor a different aspect, or a combination thereof. In one embodiment, the air quality monitors test the air continuously, however, in preferred embodiments, the air quality monitors test the air at predetermined time intervals (e.g. once a hour, once a day, once a week, etc.). Each air quality monitor relays data to processor 205. Processor 205 can store the data on data storage unit 230 or transmit the data to the operations center 105. Either processor 205 or the operations center 105 can monitor the data received from the air quality monitors to determine if there is a change in the levels of the contaminants or if the levels of the contaminants rise above a threshold level. Upon detection of unsafe contamination levels, at least one of processor 205 or the operations center 105 can generate an alert that there is contamination in the air.


In the embodiments where at least two monitoring devices are monitoring the same aspect of the air, the operations center 105 can determine if there is a change in the aspect of the air from the location of one monitoring device to the location of the other. If there is a change, the operations center 105 can generate an alert that there is a change in the air and output the approximate location of the change in the aspect of the air. Furthermore, in embodiments where there is a time stamp associated with each reading, the operations center 105 can determine the approximate direction and speed at which the contaminant is moving.


In various embodiments, at least one sensor 215 is a radiation detector. The radiation detector can distinguish between natural sources of radiation and artificial sources of radiation or can distinguish between normal levels of radiation and abnormal levels of radiation. The radiation detector detects ionizing radiation. Ionizing radiation consists of subatomic particles or electromagnetic waves that are energetic enough to detach electrons from atoms or molecules, ionizing them. Examples of ionizing particles are energetic alpha particles, beta particles, and neutrons. The ability of an electromagnetic wave (photons) to ionize an atom or molecule depends on its frequency. Radiation on the short-wavelength end of the electromagnetic spectrum—high frequency ultraviolet, x-rays, and gamma rays—is ionizing. The radiation detector is one of a dosimeter, a Geiger counters, or a scintillation counters. Dosimeters measure an absolute dose received over a period of time. Ion-chamber dosimeters resemble pens, and can be clipped to one's clothing. Film-badge dosimeters enclose a piece of photographic film, which will become exposed as radiation passes through it. Ion-chamber dosimeters must be periodically recharged, and the result logged. Film-badge dosimeters must be developed as photographic emulsion so the exposures can be counted and logged; once developed, they are discarded. Another type of dosimeter is the TLD (Thermoluminescent Dosimeter). These dosimeters contain crystals that emit visible light when heated, in direct proportion to their total radiation exposure. Like ion-chamber dosimeters, TLDs can be re-used after they have been ‘read’. Geiger counters and scintillation counters measure the dose rate of ionizing radiation directly. Preferably, the radiation detector is a solid-state device.


Upon detecting radiation, the radiation detector can relay the detection to processor 205. Processor 205 can save the detection on data storage unit 230 or transmit a message regarding the detection to the operations center 105. Processor 205 or the operations center 105 can evaluate the detection and act in accordance with the purpose of the radiation detector. For example, if the radiation detector detects radiation over a threshold level, processor 205 or the operations center 105 can generate an alert that there are unsafe radiation levels.


In various embodiments, at least one sensor 215 is a motion detector. The motion detector can be a radar-based motion detector, a photo-sensor motion detector, a passive infrared motion detector, a magnetic motion detector, a pressure sensitive motion detector, or any other device capable of detecting the motion of objects. The motion detector can be used, for example, to count the number of cars passing through an intersection to control a traffic light, for tamper prevention as described above, for security purposes, and/or to control street lights. The motion detector can be placed within the monitoring device or exterior to the monitoring device. Upon detecting motion, the motion detector can relay the detection to processor 205. Processor 205 can save the detection on data storage unit 230 or transmit a message regarding the detection to the operations center 105. Processor 205 or the operations center 105 can evaluate the detection and act in accordance with the purpose of the motion detector. For example, if the motion detector detects a predetermined number of vehicles have passed the monitoring device, processor 205 or the operations center 105 can cause a traffic light to switch from green to red. As a second example, if the motion detector detects a motion after a predetermined time, e.g. after sunset, processor 205 or the operations center 105 can cause the street lights near the monitoring device to illuminate for a predetermined period of time.


In various embodiments, at least one sensor 215 is a tiltmeter. The tiltmeter can be a pendulum, a water tube, a bubble-level meter, and/or a MEMS electronic meter. The tiltmeter can be located on devices within the system, such as, but not limited to, pipes, fire hydrants, meters, valves, utility poles, manhole covers, and light posts. The tiltmeter can send a message to processor 205 when the sensor detects a tilt beyond a threshold value. The processor 205 can then evaluate the tilt to determine if there is a problem or can relay the message to the operations center 105 for evaluation. Upon detection of undesirable tilt, at least one of processor 205 or the operations center 105 can generate an alert that there is an undesirable tilt. For example, if a utility pole is struck by a car, the tiltmeter will indicate that the utility pole is tilting at an undesirable level and the operations center 105 can alert the municipality to send out a repair crew to assess the situation and repair the utility pole.


In various embodiments, at least one sensor 215 is a proximity sensor. The proximity sensor can use electromagnetic technology, electrostatic technology, infrared technology, or a touch switch. The proximity sensor can detect if devices are properly closed or if devices are improperly touching. The proximity sensor can send a message to processor 205 when the proximity sensor detects proximity beyond a threshold value. The processor 205 can then evaluate the proximity to determine if there is a problem or can relay the message to the operations center 105 for evaluation. Upon detection of undesirable proximity, at least one of processor 205 or the operations center 105 can generate an alert that there is an undesirable proximity. For example, if a valve is improperly closed, the proximity sensor will indicate that the valve is not closed and processor 205 can alert the municipality to take proper actions to close the valve.


In various embodiments, at least one sensor 215 is a visual or audio device. The device can be an infrared camera, a video camera, a still camera, a digital camera, a film camera, a mobile vision device, a microphone, a vibration detector, combinations thereof, or any other device capable of acquiring an image or sound. In one embodiment, the device is a digital video camera that takes video images continuously. In another embodiment, the device is a digital still camera that takes still images at regular intervals or upon command from processor 205. In alternative embodiments, the device can be a traffic camera and take a picture when instructed to by processor 205, for example upon determination that a vehicle is running a red light. In other embodiments, the device is used to perform visual inspections of the system infrastructure. For example, the field of view of the device can include a device within the system that is apt to corrode and the camera can provide an easy method to visually inspect any degradation of the device. The device can send image data to processor 205 where the data is stored on data storage unit 230 or is transmitted to the operations center 105. In various embodiments, image or sound data is streamed continuously from the device to processor 205 and from processor 205 to the operations center 105. The data stream can either be live or delayed. The device can be located on the monitoring device, near the monitoring device, or within the monitoring device with a portion of the device extending outside the monitoring device or with a hole in the monitoring device through which the device can obtain images or sounds. In some embodiments, the device is positioned on an actuator. The actuator can move to reposition the field of view of the device. The actuator can move upon demand from processor 205 or can move autonomously. In the embodiments where the actuator moves autonomously, the movement can be continuous or sporadic.


In various embodiments, at least one sensor 215 is a Global Positioning System (GPS) receiver. In one embodiment, the GPS receiver is located on devices within the system 100, such as, but not limited to, pipes, fire hydrants, meters, valves, utility poles, manhole covers, and light posts. The GPS receiver can send a message to processor 205 indicating GPS location. The processor 205 can then relay the message to the operations center 105 for evaluation, conformation, and documenting. Upon detection of unexpected GPS location, at least one of processor 205 or the operations center 105 can generate an alert that the GPS receiver has moved, possibly indicating that the device has been dislodged, tampered with, or stolen. Additionally, the GPS location can be used, for example, by emergency responders to locate fire hydrants, or repair crews to determine the location of a buried device. In such embodiments, the operations center 105 can disseminate information to the emergency responders or repair crews to easily locate the device. The dissemination can occur by any method, including but not limited to, verbally, over a telecommunications network (e.g. to a smart phone or portable computer), or over a shortwave radio. In embodiments where the monitoring device is moving with the flow of fluid, the sensor can provide updated locations of the monitoring device to track, for example, the flow or contamination levels within the flow.


Other possible sensors 215 connected to monitoring device unit 200 can include, but are not limited to, flow rate meters, backflow meters, system status monitors, and power level monitors.



FIG. 3 is a schematic of a control device 300. Control device 300 includes a processor 305. Processor 305 is coupled to at least one output port 310 for controlling an output device 340. Processor 305 is also coupled to a transceiver 320 for sending and receiving signals. Processor 305 is communicatively coupled to output port 310. Output port 310 is connected to at least one output device 340. Each output device 340 can have the same purpose or each output device 340 can have a different purpose, or combinations thereof. Output devices 340 can be located within control device 300 or external to control device 300, as shown. Furthermore, output devices 340 can be attached to control device 300 or can be remote from control device 300. Output devices 340 communicate with output port 310 through wired or wireless communication channels. In various embodiments, output devices 340 are capable of bidirectional communication. In various embodiments, control device 300 is an integral part of a monitoring device. In such embodiments, the control device 300 and the monitoring device can share the same processor and/or transceiver.


In various embodiments, processor 305 is coupled to a data storage unit 330 that may be a database in some embodiments. Data storage unit 330 may store instructions for processor 305 of how to control output devices 340. In various embodiments, processor 305 is coupled to a power source 335. Power source 335 can be any device capable of powering processor 305 and any devices attached to processor 305. For example, power source 335 can be a battery, solar panel array, wind turbine, water turbine, electrical lines, or combinations thereof. In various embodiments, there is also a backup power source, such as a battery.


In various embodiments, at least one output device 340 is an actuator control device. The actuator control device can control any type of actuator, including but not limited to, a tamper prevention device, a locking device, a camera motion device, a fire hydrant nut opening device, or a valve. The actuator control device can control the actuator autonomously or upon demand from processor 305. For example, upon receiving a signal that a particular event has been sensed, processor 305 may send a command to the actuator control device to act in a particular manner. Likewise, in some embodiments the control signal may come from the operations center 105. The actuator can be mechanical, electrical, or a combination thereof.


In various embodiments, at least one output device 340 is an alarm. The alarm can be a visual alarm, an audible alarm, a tactile (i.e. vibration) alarm, or a combination thereof. The alarm can be located within the monitoring device, exterior to the monitoring device, at the operations center 105, remote from the system, or any other location sufficient to alert. Furthermore, there can be more than one alarm at different locations. For example, in the embodiments where there is a smoke detector, there can be an audible alarm located within the fire detector to alert people around the monitoring device of a potential fire, there can be an audible alarm at the fire station to alert the fire department of the potential fire, and there can be a visual alarm at the gas utility company to indicate that the flow gas in the vicinity of the potential fire should be shut off. In various embodiments the alarm is controlled by the processor 305, while in other embodiments the alarm is controlled by the operations center 105. In various embodiments, the alarm has an on/off switch controllable locally.


In various embodiments, at least one output device 340 is a tamper prevention device. The tamper prevention device can be a mechanical lock, an alarm, a light, an electrical shock generator, a retaining device, an electrical lock, or any other device capable of preventing tampering. The tamper prevention device may merely deter tampering or may incapacitate a person who is trying to tamper with the device, depending on the level of security. In some embodiments the tamper prevention device is controlled by the processor 305, while in other embodiments the tamper prevention device is controlled by the operations center 105.


In various embodiments, at least one output device 340 is a Radio-Frequency Identification (RFID) device. The RFID device can broadcast information about the device to which it is attached. For example, the RFID device may broadcast manufacturer information, location information, last service date, device information (e.g. make, model, and/or year), current status (e.g. a valve can broadcast if it is open or closed), etc. In some embodiments the RFID device is updateable by the processor 305 or by the operations center 105. The RFID device can be either an active (e.g. battery powered) or passive (e.g. require an external source to provoke signal transmission) device.


EXAMPLES

A system of the disclosure is monitoring a water distribution infrastructure. The system is used to automatically control the water pressure within the system. Such a system includes a number of water meters disbursed throughout the infrastructure relaying real time use information to a control center. Upon a determination by the operations center that there is low usage of the system (e.g. at night) based on information received by a predetermined number of the water meters, the operations center causes pumps supplying pressure within the system to reduce or cease pumping. Thereby cutting down on the electricity used by the pumps while maintaining enough pressure throughout the infrastructure to satisfy any water needs. The determination to reduce or cease pumping can be also based on information received from pressure sensors disbursed throughout the infrastructure. For example, if the pressure within the infrastructure exceeds a threshold value, the operations center causes the pumps to reduce or cease pumping.


In another example, the system is used to assist in maintaining the infrastructure. Water pipes and valves are often buried underground making it difficult to locate, assess the status of the devices, and repair them if necessary. Using an example of the above described system, each device is equipped with a monitoring the device. The monitoring device, for example, may monitor for corrosion using a corrosion monitor, geographical location using a GPS receiver, and leaks using a leak detector. Upon detection of corrosion and/or a leak, the monitoring device sends a message to the operations center where the information is analyzed. The operations center is able to make a determination if the corrosion and/or leak is severe enough to warrant fixing, if the corrosion and/or leak should be watched to determine if it worsens, or if the corrosion and/or leak can be ignored. The operations center will also alert a person of the situation for further assessment.


If it is determined that the corrosion and/or leak should be fixed, the operations center disseminates information to a repair crew and redirects water flow away from the device. Such information can include location of the device, based on data received the GPS receiver, problem associated with the device, device information (e.g. make, model, and/or year), etc. The monitoring device can also be equipped with a RFID transmitter, which transmits at least some of the above information. The repair crew receives the information on a smart phone, a portable computer, or other device capable of receiving such information. Upon completion of the repair, the operations center updates the system to indicate a new last repaired date for the device.


In another Example, the system is monitored by several entities within a municipality at the same time. For example, a fire department, a gas utility, a water utility, an electric utility, and traffic control center all monitor the system concurrently. Upon detection of smoke by a monitoring device, the control center alerts each entity of a potential fire. The location of the potential fire is determined by cross-referencing the ID number of the monitoring device with a lookup table or based on information received from a GPS receiver. The fire department uses the location information to send out emergency response personnel to the vicinity of the potential fire. The gas utility uses the location information to divert or shut off gas flow to the vicinity of the potential fire. The water utility uses the location information to divert water to or increase water pressure in the vicinity of the potential fire as well as determines if any fire hydrants in the vicinity of the potential fire are potentially damaged (e.g. are tilted at an unusual angle, are receiving no or little water pressure, or have been tampered with) based on information received from monitoring devices attached to the fire hydrants. The location of the fire hydrants is determined by cross-referencing the ID number of the monitoring device with a lookup table or based on information received from a GPS receiver. The water utility automatically alerts the fire department as to which fire hydrants to use. The water utility also disables any tamper prevention devices associated with the fire hydrants. The electric utility receives a signal that additional pressure may be needed within the water system and provides an increased electrical load to the water pumps. Additionally, the traffic control center adjusts traffic lights en route from the fire station to the vicinity of the potential fire to assist the fire trucks in arriving quickly and safely.


In another example, the system is used to monitor contamination of the fluid flowing through the system. The system includes pressure sensors, leak detectors and contamination detectors. Leaks within the system can cause a pressure drop throughout the system which can lead to contaminants being drawn into the system. For example, if a pipe is under water and the pressure inside the pipe drops below the pressure outside the pipe, the exterior water will flow into the pipe. Therefore, the system has several monitoring devices to check for such potential or actual contamination. The pressure sensors will indicate if the pressure within the system drops below a threshold level at which contaminants can be drawn into the system. The leak detectors will indicate that there is a leak through which contaminants can enter the system. While the contamination detectors will indicate if there is contamination within the system, indicating a possible breach of the infrastructure of the system.


Other embodiments and uses of the disclosed systems, methods, and devices will be apparent to those skilled in the art from consideration of the specification and practice disclosed herein. All references cited herein, including all publications, U.S. and foreign patents and patent applications, are specifically and entirely incorporated by reference. It is intended that the specification and examples be considered exemplary only with the true scope and spirit of the disclosure indicated by the following claims. Furthermore, the term “comprising of” includes the terms “consisting of” and “consisting essentially of” All examples illustrate possible embodiments but should not be viewed as limiting the scope of the disclosure.

Claims
  • 1. An infrastructure monitoring assembly comprising: a fire hydrant defining a cavity, the fire hydrant comprising a body and a bonnet, the bonnet defining a top bonnet end and a bottom bonnet end, a nut defined at the top bonnet end, the body defining a top end and a bottom end, the cavity extending into the body from the bottom end of the body towards bottom bonnet end of the bonnet coupled to the top end of the body, the bonnet sealed off from the cavity, the bonnet defining an interior region;a pipe connected in fluid communication with the fire hydrant, the pipe coupled to the bottom end of the body, a fluid at least partially filling the pipe;a sensor positioned contacting the fluid, the sensor configured to measure a parameter of the fluid; anda processor connected in communication with the sensor, the processor configured to receive a signal from the sensor, the processor positioned between the nut and the bottom bonnet end inside the interior region of the bonnet and outside of the cavity.
  • 2. The infrastructure monitoring assembly of claim 1, wherein: the processor is positioned within a monitor housing;the monitor housing is coupled to the fire hydrant; andthe sensor is positioned external to the monitor housing.
  • 3. The infrastructure monitoring assembly of claim 1, wherein the processor is connected in electrical communication with the sensor.
  • 4. The infrastructure monitoring assembly of claim 1, wherein the processor is connected in wireless communication with the sensor.
  • 5. The infrastructure monitoring assembly of claim 1, wherein the sensor is positioned within the pipe.
  • 6. The infrastructure monitoring assembly of claim 1, wherein the sensor is positioned within a base of the fire hydrant.
  • 7. The infrastructure monitoring assembly of claim 1, wherein the fluid is water.
  • 8. The infrastructure monitoring assembly of claim 1, wherein the sensor is a pressure sensor, and wherein the sensor monitors a pressure of the fluid.
  • 9. The infrastructure monitoring assembly of claim 1, further comprising an antenna connected in electrical communication with the processor, the antenna configured to transmit information about the parameter of the fluid.
  • 10. The infrastructure monitoring assembly of claim 9, wherein the antenna is connected through wireless communication with an operations center.
  • 11. The infrastructure monitoring assembly of claim 1, wherein: the fire hydrant is positioned at least partially above a ground level;the pipe is positioned at least partially below the ground level; andthe sensor is positioned below the ground level.
  • 12. The infrastructure monitoring assembly of claim 1, wherein the sensor and the processor are configured to detect leaks in the pipe.
  • 13. The infrastructure monitoring assembly of claim 1, wherein: the fire hydrant defines a nozzle;the fire hydrant further comprises a nozzle cap;the nozzle cap seals the nozzle; andthe nozzle and the nozzle cap further define the cavity.
  • 14. The infrastructure monitoring assembly of claim 1, wherein the bonnet comprises a water proof container, and wherein the processor is positioned within the waterproof container.
  • 15. A method for monitoring an infrastructure network, the method comprising: positioning a sensor in contact with a fluid, the fluid at least partially filling a pipe of the infrastructure network, the pipe connected in fluid communication with a fire hydrant of the infrastructure network, the fire hydrant defining a cavity, the fire hydrant comprising a body and a bonnet, the bonnet defining a top bonnet end and a bottom bonnet end, a nut defined at the top bonnet end, the body defining a top end and a bottom end, the cavity extending into the body from the bottom end of the body towards the top end of the body, the bottom bonnet end of the bonnet coupled to the top end of the body, the bonnet sealed off from the cavity, the bonnet defining an interior region, the pipe coupled to the bottom end of the body;measuring a parameter of the fluid with the sensor;receiving a signal from the sensor with a processor, the signal conveying information about the parameter, the processor positioned between the nut and the bottom bonnet end inside the interior region of the bonnet and outside of the cavity; andtransmitting the information from an antenna to an operation center, the antenna connected in wireless communication with the operation center, the antenna connected in electrical communication with the processor.
  • 16. The method of claim 15, wherein: the processor is positioned within a monitor housing;the monitor housing is coupled to the fire hydrant; andthe sensor is positioned external to the monitor housing.
  • 17. The method of claim 15, wherein: the fire hydrant is positioned at least partially above a ground level;the pipe is positioned at least partially below the ground level; andthe sensor is positioned below the ground level.
  • 18. The method of claim 15, wherein measuring the parameter of the fluid with the sensor comprises measuring a pressure of the fluid.
  • 19. The method of claim 15, further comprises detecting a leak within the pipe.
  • 20. The method of claim 15, wherein the sensor is positioned within the pipe.
  • 21. The method of claim 15, wherein the sensor is positioned within the fire hydrant.
  • 22. The method of claim 15, wherein the sensor is connected in electrical communication with the processor.
  • 23. The method of claim 15, wherein the sensor is connected in wireless communication with the processor.
  • 24. The method of claim 15, wherein: the fire hydrant defines a nozzle;the fire hydrant further comprises a nozzle cap;the nozzle cap seals the nozzle; andthe nozzle and the nozzle cap further define the cavity.
  • 25. An infrastructure monitoring system comprising: an infrastructure network comprising a fire hydrant and a pipe, the pipe connected in fluid communication with the fire hydrant, the pipe at least partially filled with a fluid, the fire hydrant defining a cavity, the fire hydrant comprising a body and a bonnet, the bonnet defining a top bonnet end and a bottom bonnet end, a nut defined at the top bonnet end, the body defining a top end and a bottom end, the cavity extending into the body from the bottom end of the body towards the top end of the body, the bottom bonnet end of the bonnet coupled to the top end of the body, the bonnet sealed off from the cavity, the bonnet defining an interior region, the pipe coupled to the bottom end of the body;a monitoring device comprising a sensor, a processor, and an antenna, the processor connected in communication with the sensor and the antenna, the processor positioned between the nut and the bottom bonnet end inside the interior region of the bonnet and outside of the cavity, the sensor positioned in contact with the fluid, the sensor configured to measure a parameter of the fluid; andan operation center connected in communication with the monitoring device.
  • 26. The infrastructure monitoring system of claim 25, wherein the operation center is connected in wireless communication with the monitoring device.
  • 27. The infrastructure monitoring system of claim 25, wherein the sensor is positioned within the fire hydrant.
  • 28. The infrastructure monitoring system of claim 25, wherein the sensor is positioned within the pipe.
  • 29. The infrastructure monitoring system of claim 25, wherein the sensor is connected in electrical communication with the processor.
  • 30. The infrastructure monitoring system of claim 25, wherein the sensor is connected in wireless communication with the processor.
  • 31. The infrastructure monitoring system of claim 25, wherein: the monitoring device further comprises a housing;the processor is positioned within the housing; andthe housing is coupled to the fire hydrant.
  • 32. The infrastructure monitoring system of claim 31, wherein the sensor is positioned external to the housing.
  • 33. The infrastructure monitoring system of claim 25, wherein: the fire hydrant defines a nozzle;the fire hydrant further comprises a nozzle cap;the nozzle cap seals the nozzle; andthe nozzle and the nozzle cap further define the cavity.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is continuation of U.S. application Ser. No. 15/817,172, filed Nov. 18, 2017, which is a continuation of U.S. application Ser. No. 14/848,676, filed Sep. 9, 2015, which issued as U.S. Pat. No. 9,849,322 on Dec. 26, 2017, which is a continuation of U.S. application Ser. No. 14/557,754, filed Dec. 2, 2014, which issued as U.S. Pat. No. 9,861,848 on Jan. 9, 2018, which is a continuation of U.S. application Ser. No. 13/101,235, filed May 5, 2011, which issued as U.S. Pat. No. 8,931,505 on Jan. 13, 2015, which claims the benefit of U.S. Provisional Application No. 61/355,468 filed Jun. 16, 2010, all of which are hereby specifically incorporated by reference herein in their entireties.

US Referenced Citations (309)
Number Name Date Kind
1738094 Caldwell Dec 1929 A
2171173 Coyer Aug 1939 A
3254528 Michael Jun 1966 A
3592967 Harris Jul 1971 A
3612922 Furnival Oct 1971 A
3662600 Rosano, Jr. et al. May 1972 A
3673856 Panigati Jul 1972 A
3815129 Sweany Jun 1974 A
4000753 Ellis Jan 1977 A
4056970 Sollish Nov 1977 A
4083229 Anway Apr 1978 A
4333028 Panton Jun 1982 A
4431873 Dunn et al. Feb 1984 A
4462249 Adams Jul 1984 A
4467236 Kolm et al. Aug 1984 A
4543817 Sugiyama Oct 1985 A
4796466 Farmer Jan 1989 A
4844396 Norton Jul 1989 A
4930358 Motegi et al. Jun 1990 A
4984498 Fishman Jan 1991 A
5038614 Bseisu et al. Aug 1991 A
5052215 Lewis Oct 1991 A
5078006 Maresca et al. Jan 1992 A
5085082 Cantor et al. Feb 1992 A
5090234 Maresca et al. Feb 1992 A
5117676 Chang Jun 1992 A
5118464 Richardson et al. Jun 1992 A
5163314 Maresca et al. Nov 1992 A
5165280 Sternberg et al. Nov 1992 A
5170657 Maresca et al. Dec 1992 A
5174155 Sugimoto Dec 1992 A
5187973 Kunze et al. Feb 1993 A
5189904 Maresca et al. Mar 1993 A
5201226 John et al. Apr 1993 A
5203202 Spencer Apr 1993 A
5205173 Allen Apr 1993 A
5209125 Kalinoski et al. May 1993 A
5218859 Stenstrom et al. Jun 1993 A
5243862 Latimer Sep 1993 A
5254944 Holmes et al. Oct 1993 A
5272646 Farmer Dec 1993 A
5279160 Koch Jan 1994 A
5287884 Cohen Feb 1994 A
5298894 Cerny et al. Mar 1994 A
5303592 Livingston Apr 1994 A
5319956 Bogle et al. Jun 1994 A
5333501 Okada et al. Aug 1994 A
5335547 Nakajima et al. Aug 1994 A
5343737 Baumoel Sep 1994 A
5349568 Kupperman et al. Sep 1994 A
5351655 Nuspl Oct 1994 A
5361636 Farstad et al. Nov 1994 A
5367911 Jewell et al. Nov 1994 A
5385049 Hunt et al. Jan 1995 A
5396800 Drinon et al. Mar 1995 A
5408883 Clark et al. Apr 1995 A
5416724 Savic May 1995 A
5461906 Bogle et al. Oct 1995 A
5519184 Umlas May 1996 A
5526691 Latimer et al. Jun 1996 A
5531099 Russo Jul 1996 A
5548530 Baumoel Aug 1996 A
5581037 Kwun et al. Dec 1996 A
5591912 Spisak et al. Jan 1997 A
5602327 Torizuka et al. Feb 1997 A
5611948 Hawkins Mar 1997 A
5619423 Scrantz Apr 1997 A
5623203 Hosohara et al. Apr 1997 A
5633467 Paulson May 1997 A
5639958 Lange Jun 1997 A
5655561 Wendel et al. Aug 1997 A
5686828 Peterman et al. Nov 1997 A
5708211 Jepson et al. Jan 1998 A
5754101 Tsunetomi et al. May 1998 A
5760306 Wyatt et al. Jun 1998 A
5789720 Lagally et al. Aug 1998 A
5798457 Paulson Aug 1998 A
5838633 Sinha Nov 1998 A
5866820 Camplin et al. Feb 1999 A
5892163 Johnson Apr 1999 A
5907100 Cook May 1999 A
5965818 Wang Oct 1999 A
5970434 Brophy et al. Oct 1999 A
5974862 Lander Nov 1999 A
5987990 Worthington Nov 1999 A
6000277 Smith Dec 1999 A
6000288 Kwun et al. Dec 1999 A
6003376 Burns et al. Dec 1999 A
6023986 Smith et al. Feb 2000 A
6035717 Carodiskey Mar 2000 A
6058957 Honigsbaum May 2000 A
6076407 Levesque et al. Jun 2000 A
6082193 Paulson Jul 2000 A
6104349 Cohen Aug 2000 A
6125703 MacLauchlan et al. Oct 2000 A
6127823 Atherton Oct 2000 A
6127987 Maruyama et al. Oct 2000 A
6138512 Roberts et al. Oct 2000 A
6138514 Iwamoto et al. Oct 2000 A
6164137 Hancock et al. Dec 2000 A
6170334 Paulson Jan 2001 B1
6175380 Van Den Bosch Jan 2001 B1
6192352 Alouani et al. Feb 2001 B1
6243657 Tuck et al. Jun 2001 B1
6267000 Harper et al. Jul 2001 B1
6276213 Lee et al. Aug 2001 B1
6296066 Terry Oct 2001 B1
6343510 Neeson et al. Feb 2002 B1
6363788 Gorman et al. Apr 2002 B1
6389881 Yang et al. May 2002 B1
6401525 Jamieson Jun 2002 B1
6404343 Andou et al. Jun 2002 B1
6442999 Baumoel Sep 2002 B1
6453247 Hunaidi Sep 2002 B1
6470749 Han et al. Oct 2002 B1
6530263 Chana Mar 2003 B1
6561032 Hunaidi May 2003 B1
6567006 Lander et al. May 2003 B1
6578422 Lam et al. Jun 2003 B2
6595038 Williams et al. Jul 2003 B2
6606059 Barabash Aug 2003 B1
6624628 Kwun et al. Sep 2003 B1
6647762 Roy Nov 2003 B1
6651503 Bazarov et al. Nov 2003 B2
6666095 Thomas et al. Dec 2003 B2
6667709 Hansen et al. Dec 2003 B1
6707762 Goodman et al. Mar 2004 B1
6710600 Kopecki et al. Mar 2004 B1
6725705 Huebler et al. Apr 2004 B1
6734674 Struse May 2004 B1
6745136 Lam et al. Jun 2004 B2
6751560 Tingley et al. Jun 2004 B1
6763730 Wray Jul 2004 B1
6772636 Lam et al. Aug 2004 B2
6772637 Bazarov et al. Aug 2004 B2
6772638 Matney et al. Aug 2004 B2
6781369 Paulson et al. Aug 2004 B2
6782751 Linares et al. Aug 2004 B2
6789427 Batzinger et al. Sep 2004 B2
6791318 Paulson et al. Sep 2004 B2
6799455 Neefeldt et al. Oct 2004 B1
6799466 Chinn Oct 2004 B2
6813949 Masaniello et al. Nov 2004 B2
6813950 Glascock et al. Nov 2004 B2
6816072 Zoratti Nov 2004 B2
6820016 Brown et al. Nov 2004 B2
6822742 Kalayeh et al. Nov 2004 B1
6843131 Graff et al. Jan 2005 B2
6848313 Krieg et al. Feb 2005 B2
6851319 Ziola et al. Feb 2005 B2
6889703 Bond May 2005 B2
6904818 Harthorn et al. Jun 2005 B2
6912472 Mizushina et al. Jun 2005 B2
6920792 Flora et al. Jul 2005 B2
6931931 Graff et al. Aug 2005 B2
6935178 Prause Aug 2005 B2
6945113 Siverling et al. Sep 2005 B2
6957157 Lander Oct 2005 B2
6968727 Kwun et al. Nov 2005 B2
6978832 Gardner et al. Dec 2005 B2
7051577 Komninos May 2006 B2
7080557 Adnan Jul 2006 B2
7109929 Ryken, Jr. Sep 2006 B1
7111516 Bazarov et al. Sep 2006 B2
7140253 Merki et al. Nov 2006 B2
7143659 Stout et al. Dec 2006 B2
7171854 Nagashima et al. Feb 2007 B2
7231331 Davis Jun 2007 B2
7234355 Dewangan et al. Jun 2007 B2
7240574 Sapelnikov Jul 2007 B2
7255007 Messer et al. Aug 2007 B2
7261002 Gysling et al. Aug 2007 B1
7266992 Shamout et al. Sep 2007 B2
7274996 Lapinski Sep 2007 B2
7284433 Ales et al. Oct 2007 B2
7293461 Girndt Nov 2007 B1
7299697 Siddu et al. Nov 2007 B2
7310877 Cao et al. Dec 2007 B2
7328618 Hunaidi et al. Feb 2008 B2
7331215 Bond Feb 2008 B2
7356444 Blemel Apr 2008 B2
7360462 Nozaki et al. Apr 2008 B2
7373808 Zanker et al. May 2008 B2
7380466 Deeg Jun 2008 B2
7383721 Parsons et al. Jun 2008 B2
7392709 Eckert Jul 2008 B2
7405391 Ogisu et al. Jul 2008 B2
7412882 Lazar et al. Aug 2008 B2
7412890 Johnson et al. Aug 2008 B1
7414395 Gao et al. Aug 2008 B2
7426879 Nozaki et al. Sep 2008 B2
7458267 McCoy Dec 2008 B2
7475596 Hunaidi Jan 2009 B2
7493817 Germata Feb 2009 B2
7523666 Thompson et al. Apr 2009 B2
7526944 Sabata et al. May 2009 B2
7530270 Nozaki et al. May 2009 B2
7543500 Litzenberg et al. Jun 2009 B2
7554345 Vokey Jun 2009 B2
7564540 Paulson Jul 2009 B2
7587942 Smith et al. Sep 2009 B2
7590496 Blemel Sep 2009 B2
7596458 Lander Sep 2009 B2
7607351 Allison et al. Oct 2009 B2
7623427 Jann et al. Nov 2009 B2
7647829 Junker et al. Jan 2010 B2
7650790 Wright Jan 2010 B2
7657403 Stripf et al. Feb 2010 B2
7668670 Lander Feb 2010 B2
7680625 Trowbridge et al. Mar 2010 B2
7690258 Minagi et al. Apr 2010 B2
7694564 Brignac et al. Apr 2010 B2
7696940 MacDonald Apr 2010 B1
7711217 Takahashi et al. May 2010 B2
7751989 Owens et al. Jul 2010 B2
7810378 Hunaidi et al. Oct 2010 B2
7980317 Preta et al. Jul 2011 B1
8319508 Vokey Nov 2012 B2
8353309 Embry Jan 2013 B1
8614745 Al Azemi Dec 2013 B1
8674830 Lanham et al. Mar 2014 B2
8823509 Hyland et al. Sep 2014 B2
8931505 Hyland Jan 2015 B2
9291520 Fleury, Jr. et al. Mar 2016 B2
9315973 Varman Apr 2016 B2
9496943 Parish Nov 2016 B2
9528903 Zusman Dec 2016 B2
9593999 Fleury Mar 2017 B2
9772250 Richarz et al. Sep 2017 B2
9780433 Schwengler et al. Oct 2017 B2
9799204 Hyland Oct 2017 B2
9849322 Hyland Dec 2017 B2
9861848 Hyland Jan 2018 B2
10175135 Dintakurt et al. Jan 2019 B2
10283857 Ortiz et al. May 2019 B2
10305178 Gibson et al. May 2019 B2
10317384 Morrow Jun 2019 B2
10386257 Fleury, Jr. et al. Aug 2019 B2
20010045129 Williams et al. Nov 2001 A1
20020043549 Taylor et al. Apr 2002 A1
20020124633 Yang et al. Sep 2002 A1
20020159584 Sindalovsky et al. Oct 2002 A1
20030107485 Zoratti Jun 2003 A1
20040173006 McCoy et al. Sep 2004 A1
20050005680 Anderson Jan 2005 A1
20050067022 Istre Mar 2005 A1
20050072214 Cooper Apr 2005 A1
20050121880 Santangelo Jun 2005 A1
20050279169 Lander Dec 2005 A1
20060174707 Zhang Aug 2006 A1
20060201550 Blyth et al. Sep 2006 A1
20060283251 Hunaidi Dec 2006 A1
20060284784 Smith et al. Dec 2006 A1
20070044552 Huang Mar 2007 A1
20070051187 McDearmon Mar 2007 A1
20070113618 Yokoi et al. May 2007 A1
20070130317 Lander Jun 2007 A1
20080078567 Miller et al. Apr 2008 A1
20080079640 Yang Apr 2008 A1
20080168840 Seeley et al. Jul 2008 A1
20080189056 Heidl et al. Aug 2008 A1
20080281534 Hurley Nov 2008 A1
20080307623 Furukawa Dec 2008 A1
20080314122 Hunaidi Dec 2008 A1
20090044628 Lotscher Feb 2009 A1
20090133887 Garcia et al. May 2009 A1
20090139336 Trowbridge, Jr. Jun 2009 A1
20090182099 Noro et al. Jul 2009 A1
20090214941 Buck et al. Aug 2009 A1
20090278293 Yoshinaka et al. Nov 2009 A1
20090301571 Ruhs Dec 2009 A1
20100077234 Das Mar 2010 A1
20100156632 Hyland et al. Jun 2010 A1
20100290201 Takeuchi et al. Nov 2010 A1
20100295672 Hyland et al. Nov 2010 A1
20110063172 Podduturi Mar 2011 A1
20110079402 Darby et al. Apr 2011 A1
20110102281 Su May 2011 A1
20110308638 Hyland et al. Dec 2011 A1
20120007743 Solomon Jan 2012 A1
20120007744 Pal et al. Jan 2012 A1
20120169560 Lee et al. Jul 2012 A1
20120296580 Barkay Nov 2012 A1
20120324985 Gu et al. Dec 2012 A1
20130036796 Fleury et al. Feb 2013 A1
20130041601 Dintakurti et al. Feb 2013 A1
20130049968 Fleury, Jr. Feb 2013 A1
20130145826 Richarz et al. Jun 2013 A1
20130229262 Bellows Sep 2013 A1
20130321231 Flores-Cuadras Dec 2013 A1
20140373941 Varman Dec 2014 A1
20150082868 Hyland Mar 2015 A1
20160001114 Hyland Jan 2016 A1
20160013565 Ortiz Jan 2016 A1
20160018283 Fleury et al. Jan 2016 A1
20170121949 Fleury et al. May 2017 A1
20170237158 Gibson Aug 2017 A1
20170237165 Ortiz et al. Aug 2017 A1
20180080849 Showcatally et al. Mar 2018 A1
20180093117 Hyland Apr 2018 A1
20180224349 Fleury, Jr. et al. Aug 2018 A1
20190024352 Ozburn Jan 2019 A1
20190214717 Gibson et al. Jul 2019 A1
20190214718 Ortiz et al. Jul 2019 A1
20190316983 Fleury, Jr. et al. Oct 2019 A1
20200072697 Gibson et al. Mar 2020 A1
20200212549 Gibson et al. Jul 2020 A1
20200232863 Moreno Jul 2020 A1
20200232864 Moreno Jul 2020 A1
Foreign Referenced Citations (55)
Number Date Country
2011265675 May 2015 AU
2015202550 Nov 2017 AU
2017248541 Mar 2019 AU
2154433 Jan 1997 CA
2397174 Aug 2008 CA
2634739 Jun 2015 CA
3010333 Jul 2020 CA
2766850 Aug 2020 CA
3023529 Aug 2020 CA
1831478 Jun 2013 CN
4211038 Oct 1993 DE
19757581 Jul 1998 DE
0711986 May 1993 EP
1052492 Nov 2000 EP
1077370 Feb 2001 EP
1077371 Feb 2001 EP
2439990 May 1980 FR
2776065 Sep 1999 FR
2250820 Jun 1992 GB
2269900 Feb 1994 GB
2367362 Apr 2002 GB
2421311 Jun 2006 GB
59170739 Sep 1984 JP
60111132 Jun 1985 JP
11201859 Jul 1990 JP
08250777 Sep 1996 JP
H10-2744 Jan 1998 JP
H11210028 Aug 1999 JP
2000131179 May 2000 JP
2002206965 Jul 2002 JP
2002310840 Oct 2002 JP
2005315663 Nov 2005 JP
2005321935 Nov 2005 JP
2006062414 Mar 2006 JP
2006062716 Mar 2006 JP
2007047139 Feb 2007 JP
2010068017 Mar 2010 JP
2013528732 Jul 2013 JP
H5654124 Nov 2014 JP
9850771 Nov 1998 WO
0151904 Jul 2001 WO
03049528 Jun 2003 WO
2004073115 Aug 2004 WO
2009057214 May 2009 WO
2010135587 Nov 2010 WO
2011021039 Feb 2011 WO
2011058561 May 2011 WO
2011159403 Dec 2011 WO
2012000088 Jan 2012 WO
2012153147 Nov 2012 WO
2013025526 Feb 2013 WO
2014016625 Jan 2014 WO
2017139029 Aug 2017 WO
2017139030 Aug 2017 WO
2020050946 Mar 2020 WO
Non-Patent Literature Citations (152)
Entry
Oritz, Jorge Isaac; Office Action for Canadian patent application No. 3,070,690, filed Dec. 20, 2016, dated Mar. 10, 2020, 3 pgs.
Gibson, Daryl Lee; Extended European Search Report for 16890115.5, filed Dec. 20, 2016, dated Jan. 24, 2020, 10 pgs.
Hyland, Gregory E., Non-Final Office Action for U.S. Appl. No. 13/101,235, filed May 5, 2011, dated Jul. 31, 2013; 57 pgs.
Hyland, Gregory E.; Final Office Action for U.S. Appl. No. 13/101,235, filed May 5, 2011, dated Feb. 20, 2014; 29 pgs.
Hyland, Gregory E.; Issue Notification for U.S. Appl. No. 13/101,235, filed May 5, 2011, dated Dec. 23, 2014, 1 pg.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 13/101,235, filed May 5, 2011, dated Jun. 5, 2014, 29 pgs.
Hyland, Gregory E.; Notice of Allowance for U.S. Appl. No. 13/101,235, filed May 5, 2011, dated Sep. 11, 2014, 11 pgs.
Hyland, Gregory E.; Supplemental Notice of Allowability for U.S. Appl. No. 13/101,235, filed May 5, 2011, dated Nov. 25, 2014, 5 pgs.
Hyland, Gregory E.; Applicant-Initiated Interview Summary for U.S. Appl. No. 14/557,754, filed Dec. 2, 2014, dated Apr. 19, 2017, 4 pgs.
Hyland, Gregory E.; Final Office Action for U.S. Appl. No. 14/557,754, filed Dec. 2, 2014, dated Apr. 5, 2017, 23 pgs.
Hyland, Gregory E.; Final Office Action for U.S. Appl. No. 14/557,754, filed Dec. 2, 2014, dated Mar. 30, 2016, 24 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 14/557,754, filed Dec. 2, 2014, dated Jan. 19, 2016, 101 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 14/557,754, filed Dec. 2, 2014, dated Nov. 8, 2016, 48 pgs.
Hyland, Gregory E.; Notice of Allowance for U.S. Appl. No. 14/557,754, filed Dec. 2, 2014, dated Jul. 17, 2017, 14 pgs.
Hyland, Gregory E.; Notice of Decision from Post-Prosecution Pilot Program (P3) Conference for U.S. Appl. No. 14/557,754, filed Dec. 2, 2014, dated Sep. 14, 2016, 4 pgs.
Hyland, Gregory E.; Supplemental Notice of Allowability for U.S. Appl. No. 14/557,754, filed Dec. 2, 2014, dated Oct. 20, 2017, 11 pgs.
Hyland, Gregory; Issue Notification for U.S. Appl. No. 14/557,754, filed Dec. 2, 2014, dated Dec. 20, 2017, 1 pg.
Hyland, Gregory E.; Final Office Action for U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, dated Aug. 19, 2016; 20 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, dated Dec. 13, 2016, 52 pgs.
Hyland, Gregory E.; Notice of Allowance for U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, dated Sep. 6, 2017, 12 pgs.
Hyland, Gregory E.; Supplemental Notice of Allowability for U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, dated Nov. 27, 2017, 6 pgs.
Hyland, Gregory E.; Supplemental Notice of Allowability for U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, dated Sep. 19, 2017, 8 pgs.
Hyland, Gregory; Final Office Action for U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, dated Jun. 7, 2017, 25 pgs.
Hyland, Gregory; Non-Final Office Action for U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, dated Mar. 4, 2016, 94 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 15/817,172, filed Nov. 18, 2017, dated Dec. 17, 2019, 23 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 15/817,172, filed Nov. 18, 2017, dated Jul. 10, 2019, 74 pgs.
Fleury Jr., Leo W.; Non-Final Office Action for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated Nov. 5, 2014, 30 pgs.
Fleury, Jr., Leo W.; Advisory Action for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated Jul. 9, 2014, 3 pgs.
Fleury, Jr., Leo W.; Final Office Action for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated Mar. 12, 2014; 19 pgs.
Fleury, Jr., Leo W.; Issue Notification for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated Mar. 2, 2016, 1 pg.
Fleury, Jr., Leo W.; Non-Final Office Action for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated Sep. 12, 2013; 37 pgs.
Fleury, Jr., Leo W.; Notice of Allowance for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated Feb. 2, 2016, 9 pgs.
Fleury, Jr., Leo W.; Notice of Allowance for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated May 12, 2015, 9 pgs.
Fleury, Jr., Leo W.; Notice of Allowance for U.S. Appl. No. 13/492,790, filed Jun. 8, 2012, dated Sep. 23, 2015, 11 pgs.
Fleury, Leo W.; Applicant-Initiated Interview Summary for U.S. Appl. No. 14/870,070, filed Sep. 30, 2015, dated Feb. 28, 2018, 4 pgs.
Fleury, Leo W.; Final Office Action for U.S. Appl. No. 14/870,070, filed Sep. 30, 2015, dated Dec. 29, 2017, 24 pgs.
Fleury, Leo; Non-Final Office Action for U.S. Appl. No. 14/870,070, filed Sep. 30, 2015, dated Jun. 21, 2017, 88 pgs.
Fleury, Jr., Leo W.; Non-Final Office Action for U.S. Appl. No. 15/939,942, filed Mar. 29, 2018, dated Sep. 25, 2019, 92 pgs.
Richarz, Werner Guenther; Corrected Notice of Allowability for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Aug. 29, 2017, 6 pgs.
Richarz, Werner Guenther; Final Office Action for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Oct. 20, 2014, 17 pgs.
Richarz, Werner Guenther; Final Office Action for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Sep. 10, 2015, 20 pgs.
Richarz, Werner Guenther; Final Office Action for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Sep. 8, 2016, 36 pgs.
Richarz, Werner Guenther; Issue Notification for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Sep. 6, 2017, 1 pg.
Richarz, Werner Guenther; Non-Final Office Action for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Nov. 6, 2013, 39 pgs.
Richarz, Werner Guenther; Non-Final Office Action for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Jun. 4, 2014, 24 pgs.
Richarz, Werner Guenther; Non-Final Office Action for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Feb. 27, 2015, 15 pgs.
Richarz, Werner Guenther; Non-Final Office Action for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Mar. 8, 2016, 27 pgs.
Richarz, Werner Guenther; Notice of Allowance for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Jun. 13, 2017, 31 pgs.
Richarz, Werner Guenther; Restriction Requirement for U.S. Appl. No. 13/492,792, filed Jun. 8, 2012, dated Sep. 27, 2013; 5 pgs.
Chou, et al.; Article entitled: “Non-invasive Acceleration-based Methodology for Damage Detection and Assessment of Water Distribution System”, Mar. 2010, 17 pgs.
Dintakurti, Ganapathi Deva Varma; Corrected Notice of Allowance for U.S. Appl. No. 13/492,794, filed Jun. 8, 2012, dated Dec. 6, 2018, 6 pgs.
Dintakurti, Ganapathi Deva Varma; Final Office Action for U.S. Appl. No. 13/492,794, filed Jun. 8, 2012, dated Oct. 18, 2017, 38 pgs.
Fleury, Jr., Leo W.; Final Office Action for U.S. Appl. No. 15/939,942, filed Mar. 29, 2018, dated Feb. 19, 2020, 29 pgs.
Gibson, Daryl Lee; Office Action for Canadian patent application No. 3,010,345, filed Dec. 20, 2016, dated Dec. 16, 2019, 4 pgs.
Gibson, Daryl Lee; International Search Report and Written Opinion for PCT Application No. PCT/US19/45451, filed Aug. 7, 2019, dated Feb. 3, 2020, 11 pgs.
Gibson, Daryl Lee; Office Action for Canadian application No. 3,057,202, filed Oct. 1, 2019, dated Dec. 19, 2019, 3 pgs.
Fleury, Leo W.; International Search Report and Written Opinion for serial No. PCT/US12/50390 filed Aug. 10, 2012, dated Dec. 17, 2012, 18 pgs.
Fleury, Leo W.; International Preliminary Report on Patentability for serial No. PCT/US12/50390 filed Aug. 10, 2012, dated Feb. 18, 2014, 14 pgs.
Fleury, et al.; Supplemental European Search Report for application No. 12823594.2, filed Aug. 20, 2012, dated Feb. 18, 2015, 6 pgs.
Fleury Jr., Leo W.; European Search Report for serial No. 12823594, filed Aug. 10, 2012, dated Jun. 8, 2015, 11 pgs.
Fleury Jr., Leo W.; European Search Report for Serial No. 12823594, filed Aug. 10, 2012, dated May 10, 2017, 4 pgs.
Fleury Jr., Leo W.; European Search Report for Serial No. 12823594, filed Aug. 10, 2012, dated Dec. 21, 2017, 4 pgs.
Fleury, Leo W.; Office Action for Canadian application No. 2,842,042, filed Aug. 10, 2012, dated Apr. 24, 2018, 3 pgs.
Fleury, Leo W.; Office Action for Canadian application No. 2,842,042, filed Aug. 10, 2012, dated Feb. 28, 2019, 3 pgs.
Fleury, Leo W.; Office Action for Canadian patent application No. 2,842,042, filed Aug. 10, 2012, dated Dec. 5, 82019, 3 pgs.
Hyland; U.S. Provisional Patent Application entitled: Infrastructure Monitoring Devices, Systems, and Methods, having U.S. Appl. No. 61/355,468, filed Jun. 16, 2010.
Fleury, Leo W., U.S. Provisional Patent Application Entitled: Hydrant Leak Detector Communication Device, System, and Method under U.S. Appl. No. 61/523,274, filed Aug. 12, 2011; 35 pgs.
Hunaidi, Osama; Non-Final Office Action for U.S. Appl. No. 11/766,288, filed Jun. 21, 2007, dated Jan. 20, 2010, 50 pgs.
Hunaidi, Osama; Notice of Allowance for U.S. Appl. No. 11/766,288, filed Jun. 21, 2007, dated Jun. 24, 2010, 8 pgs.
Hunaidi, Osama; Issue Notification for U.S. Appl. No. 11/766,288, filed Jun. 21, 2007, dated Sep. 22, 2010, 1 pg.
Hunaidi, Osama; Non-final Office Action for U.S. Appl. No. 09/482,317, filed Jan. 14, 2000, dated Dec. 17, 2001, 6 pgs.
Hunaidi, Osama; Notice of Allowance for U.S. Appl. No. 09/482,317, filed Jan. 14, 2000, dated May 13, 2002, 4 pgs.
Peter, Russo Anthony; European Search Report for Patent Application No. EP95307807, filed Nov. 1, 1995, dated Jul. 22, 1998, 5 pgs.
Ortiz, Jorge Isaac; Non-Final Office Action for U.S. Appl. No. 15/043,057, filed Feb. 12, 2016, dated Jun. 4, 2018, 94 pgs.
Ortiz, Jorge Isaac; Final Office Action for U.S. Appl. No. 15/043,057, filed Feb. 12, 2016, dated Dec. 12, 2018, 25 pgs.
Ortiz, Jorge Isaac; Notice of Allowance for U.S. Appl. No. 15/043,057, filed Feb. 12, 2016, dated Feb. 19, 2019, 8 pgs.
Ortiz, Jorge Isaac; Issue Notification for U.S. Appl. No. 15/043,057, filed Feb. 12, 2016, dated Apr. 17, 2019, 1 pg.
Ortiz, Jorge Isaac; Supplemental Notice of Allowance for U.S. Appl. No. 15/043,057, filed Feb. 12, 2016, dated Mar. 13, 2019, 6 pgs.
Ortiz, Jorge; International Search Report and Written Opinion for PCT/US16/67689, filed Dec. 20, 2016, dated Mar. 8, 2017, 9 pgs.
Ortiz, Jorge Isaac; International Preliminary Report on Patentability for PCT Application No. PCT/US2016/067689, filed Dec. 20, 2016, dated Aug. 23, 2018, 8 pgs.
Ortiz, Jorge Isaac; Extended European Search Report for serial No. 16890114.8, filed Dec. 20, 2016, dated Sep. 26, 2019, 11 pgs.
Ortiz, Jorge Isaac; Office Action for Canadian patent application No. 3,010,333, filed Dec. 20, 2016, dated Dec. 6, 2019, 4 pgs.
Gibson, Daryl Lee; Non-Final Office Action for U.S. Appl. No. 15/255,795, filed Sep. 2, 2016, dated Feb. 23, 2018, 86 pgs.
Gibson, Daryl Lee; Final Office Action for U.S. Appl. No. 15/255,795, filed Sep. 2, 2016, dated Aug. 31, 2018, 33 pgs.
Gibson, Daryl Lee; Notice of Allowance for U.S. Appl. No. 15/255,795, filed Sep. 2, 2016, dated Jan. 17, 2019, 17 pgs.
Gibson, Daryl Lee; Corrected Notice of Allowance for U.S. Appl. No. 15/255,795, filed Sep. 2, 2016, dated Mar. 21, 2019, 6 pgs.
Gibson, Daryl Lee; International Search Report and Written Opinion for PCT Application No. PCT/US2016/067692, filed Dec. 20, 2016, dated Mar. 2, 2017,10 pgs.
Gibson, Daryl Lee; International Preliminary Report on Patentability for PCT Application No. PCT/US2016/067692, filed Dec. 20, 2016, dated Aug. 23, 2018, 9 pgs.
Gibson, Daryl Lee; Invitation to Pay Additional Fees for PCT/US19/45451, filed Aug. 7, 2019, dated Oct. 10, 2019, 2 pgs.
Gibson, Daryl Lee; Office Action for Canadian patent application No. 3,057,167, filed Aug. 7, 2019, dated Nov. 19, 2019, 7 pgs.
Gibson, Daryl Lee; U.S. Provisional Application entitled: Nozzle Cap Multi-Band Antenna Assembly having U.S. Appl. No. 62/294,973, filed Feb. 12, 2016, 54 pgs.
Antenna. Merriam-Webster Dictionary, 2014 [retrieved on Jun. 1, 2014]. Retrieved from the Internet: <URL: www.merriam-webster.com/dictionary/antenna>.
Hyland, Gregory E.; Issue Notification for U.S. Appl. No. 14/848,676, filed Sep. 9, 2015, dated Dec. 6, 2017, 1 pg.
J.A. Gallego-Juarez, G. Rodriguez-Corral and L. Gaete-Garreton, An ultrasonic transducer for high power applications in gases, Nov. 1978, Ultrasonics, published by IPC Business Press, p. 267-271.
“Non-Patent Literature Murata (entitled ““Piezoelectric Sounds Components””), accessed at http://web.archive.org/web/20030806141815/http://www.murata.com/catalog/p37e17.pdf, archived on Aug. 6, 2003.”
“Non-Patent Literature NerdKits, accessed at http://web.archive.org/web/20090510051850/http://www.nerdkits.com/videos/sound_meter/, archived on May 10, 2009.”
“Non-Patent Literature Bimorph (entitled ““Bimoprh actuators””), accessed at http://web.archive.org/web/20080122050424/http://www.elpapiezo.ru/eng/curve_e.shtml, archived on Jan. 22, 2008.”
Dintakurti, Ganapathi Deva Varma; Non-Final Office Action for U.S. Appl. No. 13/492,794, filed Jun. 8, 2012, dated Jan. 16, 2015, 60 pgs.
Dintakurti, Ganapathi Deva Varma; Non-Final Office Action for U.S. Appl. No. 13/492,794, filed Jun. 8, 2012, dated May 17, 2016, 48 pgs.
Dintakurti, Ganapathi Deva Varma; Final Office Action for U.S. Appl. No. 13/492,794, filed Jun. 8, 2012, dated Nov. 8, 2016, 31 pgs.
Dintakurti, Ganapathi Deva Varma; Non-Final Office Action for U.S. Appl. No. 13/492,794, filed Jun. 8, 2012, dated Mar. 16, 2017, 30 pgs.
Dintakurti, Ganapathi Deva Varma; Non-Final Office Action for U.S. Appl. No. 13/492,794, filed Jun. 8, 2012, dated Jan. 11, 2018, 38 pgs.
Dintakurti, Ganapathi Deva Varma; Final Office Action for U.S. Appl. No. 13/492,794, filed Jun. 8, 2012, dated Jun. 22, 2018, 39 pgs.
Dintakurti, Ganapathi Deva Varma; Notice of Allowance for U.S. Appl. No. 13/492,794, filed Jun. 8, 2012, dated Sep. 24, 2018, 21 pgs.
Dintakurti, Ganapathi Deva Varma; Issue Notification for U.S. Appl. No. 13/492,794, filed Jun. 8, 2012, dated Dec. 19, 2018, 1 pg.
Fleury Jr, Leo W.; Non-Final Office Action for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Sep. 23, 2013; 35 pgs.
Fleury, Jr., Leo W.; Final Office Action for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Apr. 23, 2014, 19 pgs.
Fleury, Jr., Leo W.; Advisory Action for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Jun. 18, 2014, 4 pgs.
Fleury, Jr., Leo W.; Non-Final Office Action for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Oct. 21, 2014, 37 pgs.
Fleury, Jr., Leo W.; Final Office Action for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated May 22, 2015, 28 pgs.
Non-Patent Literature “Radiodetection Water Leak Detection Products”, 2008, Radiodetection Ltd.—SPX Corporation.
Fleury, Jr., Leo W.; Advisory Action for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Sep. 9, 2015, 3 pgs.
Fleury, Jr., Leo W.; Non-Final Office Action for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Mar. 1, 2016, 42 pgs.
Fleury, Jr., Leo W.; Notice of Allowance for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Sep. 21, 2016, 18 pgs.
Fleury, Jr., Leo W.; Notice of Allowability for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Oct. 24, 2016, 13 pgs.
Fleury, Jr., Leo W.; Supplemental Notice of Allowance for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Nov. 22, 2016; 8 pgs.
Fleury, Jr., Leo W.; Corrected Notice of Allowability for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Feb. 14, 2017; 8 pgs.
Fleury, Jr., Leo W.; Issue Notification for U.S. Appl. No. 13/492,795, filed Jun. 8, 2012, dated Feb. 22, 2017; 1 page.
Fleury, Jr., Leo W.; Notice of Allowance for U.S. Appl. No. 15/401,457, filed Jan. 9, 2017, dated Apr. 16, 2019, 88 pgs.
Fleury, Jr., Leo W.; Corrected Notice of Allowance for U.S. Appl. No. 15/401,457, filed Jan. 9, 2017, dated Jun. 26, 2019, 55 pgs.
Hyland; International Search Report and Written Opinion for serial No. PCT/US2011/035374, filed May 5, 2011, dated Sep. 13, 2011; 7 pgs.
Hyland; International Preliminary Report on Patentability for serial No. PCT/US2011/035374, filed May 5, 2011, dated Dec. 19, 2012; 5 pgs.
Hyland, Gregory E..; Office Action for Canadian Patent Application No. 2,766,850, filed May 5, 2011, dated Mar. 13, 2017, 4 pgs.
Hyland, Gregory E.; Office Action for Canadian application No. 2,766,850, filed May 5, 2011, dated Aug. 16, 2018, 4 pgs.
Hyland, Gregory E.; Office Action for Canadian patent application No. 2,766,850, filed May 5, 2011, dated Jun. 19, 2019, 4 pgs.
Hyland, Gregory E.; Mexico Office Action for serial No. MX/a/2012/000347, filed May 5, 2011, dated May 30, 2016, 4 pgs.
Hyland, Gregory E.; Mexico Office Action for serial No. MX/a/2012/000347, filed May 5, 2011, dated Aug. 31, 2016, 4 pgs.
Hyland, Gregory E.; Mexico Office Action for serial No. MX/a/2012/000347, filed May 5, 2011, dated Dec. 13, 2016, 5 pgs.
Hyland, Gregory; Extended European Search Report for serial No. 11796120.1, filed May 5, 2011, dated Nov. 4, 2016, 8 pgs.
Hyland, Gregory E.; Office Action for European patent application No. 11796120.1, filed May 5, 2011, dated Feb. 9, 2018, 4 pgs.
Hyland, Gregory E.; Australian Patent Examination Report for serial No. 2011265675, filed Jan. 21, 2012, dated Oct. 1, 2014, 3 pgs.
Hyland, Gregory E.; Japanese Office Action for serial No. 2013515338, filed Jan. 30, 2012, dated Jun. 10, 2014, 8 pgs.
Hyland, Gregory E.; Japanese Office Action for serial No. 2014-234642, filed May 5, 2011, dated Jul. 7, 2015, 9 pgs.
Hyland, Gregory E.; Japanese Office Action for serial No. 2014-234642, filed May 5, 2011, dated Nov. 4, 2015,9 pgs.
Hyland, Gregory E.; Australian Examination Report for serial No. 2015202550, filed May 5, 2011, dated Aug. 12, 2016, 4 pgs.
Hyland, Gregory E.; Australian Examination Report for serial No. 2015202550, filed May 5, 2011, dated Feb. 9, 2017, 4 pgs.
Hyland, Gregory E.; Australian Examination Report for Serial No. 2015202550, filed May 5, 2011, dated May 16, 2017, 5 pgs.
Hyland, Gregory E.; Australian Examination Report for Serial No. 2015202550, filed May 5, 2011, dated Jul. 5, 2017, 4 pgs.
Hyland, Gregory E.; Office Action for Mexico Patent Application No. MX/a/2017/006090, filed May 5, 2011, dated Sep. 26, 2018, 4 pgs.
Hyland, Gregory E.; Examination Report for Australian patent application No. 2017248541, filed Oct. 20, 2017, dated Apr. 20, 2018, 5 pgs.
Hyland, Gregory E.; Office Action for Canadian patent application No. 3,023,529, filed May 5, 2011, dated Nov. 26, 2019, 4 pgs.
Hyland, Gregory E.; Final Office Action for U.S. Appl. No. 15/817,172, filed Nov. 18, 2017, dated Jun. 11, 2020, 33 pgs.
Fleury, Jr., Leo W.; Non-Final Office Action for U.S. Appl. No. 15/939,942, filed Mar. 29, 2018, dated May 27, 2020, 23 pgs.
Keefe, Robert Paul, Office Action for Canadian application No. 3,060,512, filed May 5, 2011, dated Apr. 22, 2020, 5 pgs.
Gibson, Daryl Lee; Requirement for Restriction/Election for U.S. Appl. No. 16/121,136, filed Sep. 14, 2018, dated May 7, 2020, 5 pgs.
Gibson, Daryl Lee; Office Action for Canadian patent application No. 3,057,167, filed Aug. 7, 2019, dated May 25, 2020, 3 pgs.
Gibson, Daryl Lee; Office Action for Canadian application No. 3,057,202, filed Oct. 1, 2019, dated Apr. 2, 2020, 4 pgs.
Gibson, Daryl Lee; Non-Final Office Action for U.S. Appl. No. 16/121,136, filed Sep. 4, 2018, dated Jun. 22, 2020, 94 pgs.
Hyland, Gregory E.; Notice of Allowance for U.S. Appl. No. 15/817,172, filed Nov. 18, 2017, dated Aug. 21, 2020, 9 pgs.
Hyland, Gregory E.; Supplemental Notice of Allowance for U.S. Appl. No. 15/817,172, filed Nov. 18, 2017, dated Oct. 28, 2020, 4 pgs.
Hyland, Gregory; Supplemental Notice of Allowance for U.S. Appl. No. 15/817,172, filed Nov. 18, 2017, dated Oct. 9, 2020, 4 pgs.
Gibson, Daryl Lee; Notice of Allowance for U.S. Appl. No. 16/121,136, filed Sep. 4, 2018, dated Sep. 29, 2020 15 pgs.
Related Publications (1)
Number Date Country
20200069987 A1 Mar 2020 US
Provisional Applications (1)
Number Date Country
61355468 Jun 2010 US
Continuations (4)
Number Date Country
Parent 15817172 Nov 2017 US
Child 16675507 US
Parent 14848676 Sep 2015 US
Child 15817172 US
Parent 14557754 Dec 2014 US
Child 14848676 US
Parent 13101235 May 2011 US
Child 14557754 US