Infrastructure monitoring devices, systems, and methods

Information

  • Patent Grant
  • 8823509
  • Patent Number
    8,823,509
  • Date Filed
    Thursday, May 20, 2010
    14 years ago
  • Date Issued
    Tuesday, September 2, 2014
    10 years ago
Abstract
The present disclosure relates to an infrastructure monitoring system and method that comprises multiple communications devices. An exemplary infrastructure monitoring system includes: an operations center; and a plurality of communications devices communicatively coupled to the operations center; wherein, at least one communications device of said plurality of communications devices is coupled to a component of the infrastructure; and wherein at least two communications devices are monitoring devices, the first monitoring device monitoring a first aspect of the infrastructure and the second monitoring device monitoring a second aspect of the infrastructure.
Description
BACKGROUND

1. Field of the Invention


The invention is directed to devices, systems, and methods of 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, and, in particular, to devices, methods, and systems for monitoring and controlling a municipality and alerting a user to potential faults and actions required.


2. Background of the Invention


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, leaks, contamination, and/or other issues.


Often to obtain an understanding of the state of any one system, or for billing or repair purposes, personnel must be sent into the municipality to manually check for problems within the system. This is slow, labor-intensive process can lead to overlooked problems. Furthermore, preferred aspects of the system may only be evaluated irregularly or infrequently, thereby allowing a problem to go unchecked for long periods of time. For 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 long period of time. Furthermore, a leak can lead to underground structural erosion.


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 new poles or towers to be erected for placement of the communication devices or municipalities may have to rent space on a utility company's poles.


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 shut off gas flow to the vicinity of the fire and require the water company to redirect water or additional water pressure to the vicinity. However, current systems are not interoperable. Therefore, it is 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 OF THE INVENTION

The present invention overcomes the problems and disadvantages associated with current strategies and systems and provides new systems and methods of monitoring municipality infrastructure.


One embodiment of the invention is directed to an infrastructure monitoring system. The system comprises 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 component of the infrastructure, and at least two communications devices are monitoring devices. The first monitoring device monitoring a first aspect of the infrastructure and the second monitoring device monitoring a second aspect of the infrastructure.


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


In a preferred embodiment, the operations center and the plurality of communications devices are wirelessly communicatively coupled. Preferably, at least one communications device is an output device. The output device comprises a transceiver device adapted receive or 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 a preferred embodiment, the operations center and at least one output device are wirelessly communicatively coupled. Each communications device is preferably adapted to receive transmissions for a second communications device and retransmit the transmission to the second communications device. Each communications device is preferably adapted to receive transmissions for the operations center and retransmit the transmission to the operations center.


In a preferred 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 a preferred embodiment, a monitoring device and an output device are contained within the same unit. The monitoring device and the output device preferably 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, water, electricity, tampering, leaks, GPS location, proximity, tilt, smoke, temperature, rust, corrosion, fluid flow, pressure, water quality, air quality, contamination, pH, infrastructure status, and motion.


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


Preferably, 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. Preferably, 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 preferred embodiments where the component of the infrastructure is a fire hydrant, the communications device can be 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 and/or the communications device coupled to the fire hydrant can be positioned within one of the nozzle cap, the pumper nozzle, the hose nozzle, the fire truck hookup, and the bonnet.


Another embodiment of the invention is directed to another infrastructure monitoring system. The system comprises 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 a preferred embodiment, the communications device coupled to the fire hydrant is one of a monitoring device, an output device, and a repeater. Preferably, at least one portion of the fire hydrant is comprised of a material that does not interfere with the communications. In a preferred 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 of the invention is directed to a fire hydrant. The fire hydrant comprises a bonnet and a communications device coupled to the bonnet. The communications device is an element of a infrastructure monitoring system.


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





DESCRIPTION OF THE DRAWINGS

The invention is described in greater detail by way of example only and with reference to the attached drawings, in which:



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



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



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



FIGS. 4
a-b are images of one embodiment of a device of the invention housed within a fire hydrant.



FIGS. 5
a-b are images of an embodiment of a insulation device for sealing the bonnet of the fire hydrant from the water within the fire hydrant.





DESCRIPTION OF THE INVENTION

As embodied and broadly described herein, the disclosures herein provide detailed embodiments of the invention. However, the disclosed embodiments are merely exemplary of the invention that 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 invention.


A problem in the art capable of being solved by the embodiments of the present invention is monitoring and maintaining an infrastructure. It has surprisingly 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 of the invention is capable of providing a system administrator with a full picture of the current state of the system. The network preferably includes an array of different monitoring devices each capable of sensing at least one condition. The monitoring devices may be capable of sending and receiving data to and from at least one operations center. Communication may be from the remote monitoring device 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 preferably 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 preferably over the Internet, but may be over a private network, a local area network, or a wide area network. Preferably 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 preferably, the communications are secured or encrypted such that the communications system cannot be monitored by another unknown party. Preferably access to the system is granted through user names and passwords, although additional and/or alternate encryption methods can be employed.


One embodiment of the invention 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 of the invention for monitoring, controlling, and communicating with at least one monitoring device and/or at least one control device. 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 the preferred 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 of the invention preferably 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, the monitors can be self monitoring. For example the monitors preferably 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 device 110 or 111 can be coupled to a fire hydrant, see FIGS. 4a-b. The device 110 or 111 can be located within the nozzle cap (i.e. in the pumper nozzle, the hose nozzle, or in the fire truck hook up), within the body of the fire hydrant, within the bonnet, attached to the outside of the fire hydrant, or at another location on or within the fire hydrant. Preferably, the housing for the 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 device 110 or 111. The bonnet of the fire hydrant can be isolated from the flow of water within the fire hydrant, see FIGS. 5a-b. For example, there can be a plastic, metal, or other material disc that seals off a portion of the fire hydrant to prevent water from reaching the interior regions of the bonnet.


Each node in the network of the invention preferably detects errors in transmissions. Error detection can use cyclic redundancy codes using a table based on a defined polynomial or any other method of error detection. In preferred 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 rout or rerouted.


In preferred 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. Furthermore, different types of devices 110 and 111 can have identifiers that are unique to that type of device. For example, the identifier for all water meters can start with a WM, while the identifier for all leak detectors can start with a LD. Each communication to and from a device 110 and 111 can include the unique identifier so that the message is received by the correct device 110 or 111, or operations center 105 can determine where the message was sent from.


Each monitoring device 110 and each control device 111 can be retrofitted to an existing system or device, can be coupled to a new system or device, or can be integrated into a new system or device. For example, the system can be connected to, work with, or work independently of a Supervisory control and data acquisition (SCADA) network. In preferred embodiments, 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 or device.


In preferred embodiments, 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 the preferred 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 preferred embodiments, one intermediary communications device can service multiple sectors.


In preferred 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 device 110 and/or 111 can act as a transceiver or relay by receiving messages intended for another device 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 only communicate within their sector. In other embodiments, monitoring device 110 and control device 111 can communicate with devices 110 and/or 111 in other sectors. Each remote monitoring device 110 and/or the operations center 105 may be able to determine if a transmitted message was received by the intended device 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 preferred 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 a remotely hosted operations center accessible by a device capable of accessing 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 preferred embodiments, there is a plurality of operations centers 105. One or more operations centers can be located at different entities and each control center can monitor a different aspect of system 100. For example, in embodiments where one monitoring device 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 preferred embodiments, there are redundant operations centers 105, where at least two operations centers 105 monitor the same aspect of system 100. Operations center 105, in preferred embodiments, 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. In preferred embodiments, 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. Additionally, data storage unit 230 can hold instructions for processor 205 to execute upon prompting from the operations center. In the preferred embodiments, processor 205 compiles at least some of the data stored in data storage unit 230 for transmitting to the operations center.


Each remote monitoring device 200 may collect data and/or transmit data continuously, at specific intervals, or randomly. In embodiments where the monitoring device 200 collects and transmits data in a non-continuous configuration, monitoring device 200 may turn off or reduce power consumption during the non-data collecting periods to save energy. In preferred embodiments, processor 205 is coupled to a power source 235. Power source 235 can be a device 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. In preferred embodiments, the power may derive from the operation of the infrastructure system.


In the preferred embodiment, processor 205 is coupled to at least one sensor 215 that monitors at least one condition associated with the monitoring device. In preferred embodiments, 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 preferred 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, where 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 as 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 preferred embodiments, sensor 215 is a use monitor. In such embodiments, 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 that the monitoring device is being used and/or how much of the commodity is flowing through the sensor. In preferred embodiments, the operations center can request a reading from the use monitor on demand. In preferred embodiments, the processor or the operations center 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 can generate an alarm that there is unauthorized use. For example, in embodiments where the use monitor is coupled to a fire hydrant, if the use monitor indicates that the fire hydrant is in use, however no fire is reported, the operations center can disseminate an alert that there is potential misuse of the fire hydrant.


In preferred 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 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 can generate an alarm that the device is being tampered with. In preferred embodiments, the monitoring device may activate a tamper prevention device (described below). In preferred embodiments, the operations center 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 telling processor 205 to resume monitoring for tamper events. For example, if a fire department needs to use a fire hydrant, the operations center 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 will send a message to processor 205 to start monitoring for tamper events again.


In preferred 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 preferably vapor sensors. While in liquid applications, preferably 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 for evaluation. Upon detection of a leak event, at least one of processor 205 or the operations center can generate an alert that there is a leak if the leak is determined to be severe enough to warrant attention.


In preferred 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. In the preferred embodiment, 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 for evaluation. Upon detection of smoke, at least one of processor 205 or the operations center can generate an alert that there is smoke.


In preferred 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 the preferred 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 for evaluation. Upon detection of undesirable temperatures, at least one of processor 205 or the operations center can generate an alert that there is an undesirable temperature condition.


In preferred embodiments, at least one sensor 215 is a rust and/or corrosion sensor. The 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 sensor can send a message to processor 205 when the 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 for evaluation. Upon detection of undesirable rust or corrosion, at least one of processor 205 or the operations center can generate an alert that there is an undesirable amount of rust or corrosion.


In preferred embodiments, at least one sensor 215 is a fluid flow sensor. 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 known in the art to measure the flow of fluid. The sensor can send a message to processor 205 when the 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 for evaluation. Upon detection of an anomaly, at least one of processor 205 and the operations center can generate an alert that there is an anomaly.


In preferred embodiments, at least one sensor 215 is a pressure sensor. In the preferred 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 known in the art to measure pressure. The sensor can send a message to processor 205 when the 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 for evaluation. Upon detection of an anomaly, at least one of processor 205 or the operations center can generate an alert that there is an anomaly.


In preferred 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 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 the preferred embodiment, the water quality monitors test the water continuously, however, in preferred 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 database 230 or transmit the data to the operations center. Either processor 205 or the operations center 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 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 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 can generate an alert that there is a change in the water system and output the approximate location of the change in the aspect of the water.


In preferred 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 were 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 the preferred 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 database 230 or transmit the data to the operations center. Either processor 205 or the operations center 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 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 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 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 control center can determine the approximate direction and speed at which the contaminant is moving.


In preferred 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. Preferably, 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. Preferably, 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 database 230 or transmit a message regarding the detection to the operations center. Processor 205 or the operations center can evaluative 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 can generate an alert that there are unsafe radiation levels.


In preferred 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 detection 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 database 230 or transmit a message regarding the detection to the operations center. Processor 205 or the operations center can evaluative 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 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 can cause the street lights near the monitoring device to illuminate for a predetermined period of time.


In preferred 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 sensor 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 for evaluation. Upon detection of undesirable tilt, at least one of processor 205 or the operations center 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 can alert the municipality to send out a repair crew to assess the situation and repair the utility pole.


In preferred 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 sensor can send a message to processor 205 when the 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 for evaluation. Upon detection of undesirable proximity, at least one of processor 205 or the operations center 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 preferred 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 a preferred embodiment, the device is a digital video camera that takes video images continuously. In another preferred embodiment, the device is a digital still camera that takes still images at regular intervals or upon command from processor 205. In preferred 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 be use to perform visual inspections of the systems 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 database 230 or is transmitted to the operations center. In preferred embodiments, image or sound data is streamed continuously from the device to processor 205 and from processor 205 to the operations center. 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 preferred 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 preferred embodiments, at least one sensor 215 is a Global Positioning System (GPS) receiver. In the preferred embodiment, the GPS receiver is 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 sensor can send a message to processor 205 indicating the sensor location. The processor 205 can then relay the message to the operations center for evaluation, conformation, and documenting. Upon detection of unexpected location, at least one of processor 205 or the operations center can generate an alert that the sensor 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 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 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 can 340 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 preferred embodiments, output devices 340 are capable of bidirectional communication. In preferred embodiments, control device 300 is an integral part of a monitoring device. In such embodiments, the control device and the monitoring device can share the same processor and/or transceiver.


In preferred embodiments, processor 305 is coupled to a data storage unit 330. Data storage unit 330 may store instructions for processor 305 of how to control output devices 340. In preferred 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 preferred embodiments, there is also a backup power source, such as a battery.


In preferred 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 preferred embodiments the control signal may come from the operations center. The actuator can be mechanical, electrical, or a combination thereof.


In preferred 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, remote from the system, or any other location to alert people. 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 preferred embodiments the alarm is controlled by the processor 305, while in other embodiments the alarm is controlled by the operations center. In preferred embodiments, the alarm has an on/off switch controllable locally.


In preferred 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 preferred 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.


In preferred embodiments, at least one output device 340 is a Radio-Frequency Identification (RFID) device. The RFID device can broadcast information about the device it is attached to. 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 preferred embodiments the RFID device is updateable by the processor 305 or by the operations center. 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 invention 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 invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention 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 invention indicated by the following claims. Furthermore, the term “comprising of” includes the terms “consisting of” and “consisting essentially of.” All examples illustrate embodiments of the invention, but should not be viewed as limiting the scope of the invention.

Claims
  • 1. An infrastructure monitoring system comprising: an operations center; anda plurality of communications devices communicatively coupled to the operations center;wherein at least one communications device of the plurality of communications devices is coupled to a fire hydrant and comprises a repeater, andwherein at least one communications device of the plurality of communications devices comprises a monitoring device, the monitoring device comprising at least one sensor sensing at least one condition within a water distribution system, a data storage device storing data sensed by the at least one sensor, a transceiver device adapted to transmit and receive data, and a processor communicatively coupled to the at least one sensor, the data storage device, and the transceiver device, the processor configured to: receive the data sensed by the at least one sensor,determine, based on the data sensed by the at least one sensor, if there is a problem with the at least one condition within the water distribution system that the at least one sensor is sensing,upon determining that there is a problem with the at least one condition within the water distribution system that the at least one sensor is sensing,transmitting a message to the operations center via the transceiver device, andperiodically compiling sensing data stored in the data storage device and transmitting the compiled sensing data to the operations center via the transceiver device, the monitoring device being positioned remotely from the at least one communications device coupled to the fire hydrant;wherein the monitoring device moves with a flow of water within the water distribution system and transmits the compiled sensing data to the operations center via the repeater.
  • 2. The system of claim 1, wherein the communications device coupled to the fire hydrant further comprises one of a monitoring device or an output device.
  • 3. The system of claim 1, wherein at least one portion of the fire hydrant is comprised of a material that does not interfere with communications between the plurality of communications devices with one another and the plurality of communications devices with the operations center.
  • 4. The system of claim 1, wherein the communications device coupled to the fire hydrant is positioned within one of a nozzle cap, a pumper nozzle, a hose nozzle, a fire truck hookup, and a bonnet of the fire hydrant.
REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. provisional application Ser. No. 61/180,600 filed May 22, 2009, entitled “WATER SUPPLY INFRASTRUCTURE MONITORING SYSTEM AND METHOD,” which is hereby specifically and entirely incorporated by reference.

US Referenced Citations (346)
Number Name Date Kind
691904 Hallbergh Jan 1902 A
1165429 Mass Dec 1915 A
1788618 Cover Jan 1931 A
1808209 Earl Jun 1931 A
1808212 Earl Jun 1931 A
2302529 Cornell et al. Nov 1942 A
3254660 Ray Jun 1966 A
3593957 Dolter et al. Jul 1971 A
3653261 Feldman Apr 1972 A
3705385 Batz Dec 1972 A
3731534 Painley et al. May 1973 A
3795144 Marchesi Mar 1974 A
4093997 Germer Jun 1978 A
4120031 Kincheloe et al. Oct 1978 A
4291375 Wolf Sep 1981 A
4388690 Lumsden Jun 1983 A
4414633 Churchill Nov 1983 A
4442492 Karlsson et al. Apr 1984 A
4465970 DiMassimo et al. Aug 1984 A
4516213 Gidden May 1985 A
4542469 Brandberry et al. Sep 1985 A
4591988 Klima et al. May 1986 A
4707852 Jahr et al. Nov 1987 A
4727900 Dooling et al. Mar 1988 A
4792946 Mayo Dec 1988 A
4803632 Frew et al. Feb 1989 A
4833618 Verma et al. May 1989 A
4868566 Strobel et al. Sep 1989 A
4881070 Burrowes et al. Nov 1989 A
4940976 Gastouniotis et al. Jul 1990 A
4953403 Springer Sep 1990 A
4967996 Sonoda et al. Nov 1990 A
5056107 Johnson et al. Oct 1991 A
5075792 Brown et al. Dec 1991 A
5079715 Venkataraman et al. Jan 1992 A
5239575 White et al. Aug 1993 A
5251480 Brunson, IV et al. Oct 1993 A
5267587 Brown Dec 1993 A
5298894 Cerny et al. Mar 1994 A
5381136 Powers et al. Jan 1995 A
5434911 Gray et al. Jul 1995 A
5438329 Gastouniolis et al. Aug 1995 A
5451938 Brennan, Jr. Sep 1995 A
5459459 Lee, Jr. Oct 1995 A
5481259 Bane Jan 1996 A
5493287 Bane Feb 1996 A
5519387 Besier et al. May 1996 A
5525898 Lee et al. Jun 1996 A
5553094 Johnson et al. Sep 1996 A
5590179 Shincovich et al. Dec 1996 A
5594740 LaDue Jan 1997 A
5594776 Dent Jan 1997 A
5617084 Sears Apr 1997 A
5631554 Briese et al. May 1997 A
5654692 Baxter et al. Aug 1997 A
5666655 Ishikawa et al. Sep 1997 A
5673252 Johnson et al. Sep 1997 A
5708195 Kurisu et al. Jan 1998 A
5714931 Petite et al. Feb 1998 A
5748104 Argyroudis et al. May 1998 A
5751797 Saaden May 1998 A
5754101 Tsunetomi et al. May 1998 A
5767790 Jovellana Jun 1998 A
5787358 Takahashi Jul 1998 A
5801643 Williams et al. Sep 1998 A
5815086 Ivie et al. Sep 1998 A
5852658 Knight et al. Dec 1998 A
5877703 Bloss et al. Mar 1999 A
5892441 Woolley et al. Apr 1999 A
5892758 Argyroudis Apr 1999 A
5907491 Canada et al. May 1999 A
5924051 Provost et al. Jul 1999 A
5926103 Petite Jul 1999 A
5926531 Petite Jul 1999 A
5940009 Loy et al. Aug 1999 A
5963146 Johnson et al. Oct 1999 A
5963557 Eng Oct 1999 A
5971011 Price Oct 1999 A
5979863 Lousberg Nov 1999 A
5986573 Franklin et al. Nov 1999 A
5994892 Turino et al. Nov 1999 A
6006212 Schleich et al. Dec 1999 A
6028522 Petite Feb 2000 A
6028855 Hirsch Feb 2000 A
6031455 Grube et al. Feb 2000 A
6031466 Leshets et al. Feb 2000 A
6044062 Brownrigg Mar 2000 A
6058374 Guthrie et al. May 2000 A
6060994 Chen May 2000 A
6069571 Tell May 2000 A
6081204 Lavoie et al. Jun 2000 A
6115677 Perthold et al. Sep 2000 A
6150955 Tracy et al. Nov 2000 A
6152173 Makowan Nov 2000 A
6163276 Irving et al. Dec 2000 A
6172616 Johnson et al. Jan 2001 B1
6195018 Ragle et al. Feb 2001 B1
6208266 Lyons et al. Mar 2001 B1
6218953 Petite Apr 2001 B1
6233327 Petite May 2001 B1
6246677 Nap et al. Jun 2001 B1
6249516 Brownrigg et al. Jun 2001 B1
6288641 Casais Sep 2001 B1
6317051 Cohen Nov 2001 B1
6333975 Brunn et al. Dec 2001 B1
6373399 Johnson et al. Apr 2002 B1
6392538 Shere May 2002 B1
6405047 Moon Jun 2002 B1
6424270 Ali Jul 2002 B1
6426027 Scarborough et al. Jul 2002 B1
6430268 Petite Aug 2002 B1
6437692 Petite et al. Aug 2002 B1
6453247 Hunaidi Sep 2002 B1
6456197 Lauritsen et al. Sep 2002 B1
6470903 Reyman Oct 2002 B2
6493377 Schilling et al. Dec 2002 B2
6512463 Campbell et al. Jan 2003 B1
6528957 Luchaco Mar 2003 B1
6536469 Dilger et al. Mar 2003 B2
6538577 Ehrke et al. Mar 2003 B1
6560543 Wolfe et al. May 2003 B2
6564159 Lavoie et al. May 2003 B1
6577961 Hubbard et al. Jun 2003 B1
6618578 Petite Sep 2003 B1
6618709 Sneeringer Sep 2003 B1
6624750 Marman et al. Sep 2003 B1
6628207 Hemminger et al. Sep 2003 B1
6628764 Petite Sep 2003 B1
6633781 Lee et al. Oct 2003 B1
6653945 Johnson et al. Nov 2003 B2
6657552 Belski et al. Dec 2003 B2
6675071 Griffin, Jr. et al. Jan 2004 B1
6677861 Henry et al. Jan 2004 B1
6701956 Berger Mar 2004 B1
6710721 Holowick Mar 2004 B1
6747557 Petite et al. Jun 2004 B1
6798352 Holowick Sep 2004 B2
6816072 Zoratti et al. Nov 2004 B2
6836737 Petite et al. Dec 2004 B2
6847300 Yee et al. Jan 2005 B2
6891838 Petite et al. May 2005 B1
6914533 Petite Jul 2005 B2
6914893 Petite Jul 2005 B2
6931445 Davis Aug 2005 B2
6946972 Mueller et al. Sep 2005 B2
6954701 Wolfe Oct 2005 B2
6954814 Leach Oct 2005 B1
6978210 Suter et al. Dec 2005 B1
6980079 Shintani et al. Dec 2005 B1
6982651 Fischer Jan 2006 B2
7008239 Ju Mar 2006 B1
7009530 Zigdon et al. Mar 2006 B2
7012546 Zigdon et al. Mar 2006 B1
7042368 Patterson et al. May 2006 B2
7053767 Petite et al. May 2006 B2
7054271 Brownrigg May 2006 B2
7061924 Durrant et al. Jun 2006 B1
7072945 Nieminen et al. Jul 2006 B1
7079810 Petite et al. Jul 2006 B2
7088239 Basinger et al. Aug 2006 B2
7089125 Songeregger Aug 2006 B2
7099781 Heidl et al. Aug 2006 B1
7103511 Petite Sep 2006 B2
7111817 Teti et al. Sep 2006 B2
7117051 Landry et al. Oct 2006 B2
7123628 Hwang et al. Oct 2006 B1
7124184 Chung et al. Oct 2006 B2
7137550 Petite Nov 2006 B1
7142107 Kates Nov 2006 B2
7143645 Benson et al. Dec 2006 B2
7228726 Kates Jun 2007 B2
7248179 Smit Jul 2007 B2
7248181 Patterson et al. Jul 2007 B2
7250874 Mueller et al. Jul 2007 B2
7256704 Yoon et al. Aug 2007 B2
7263073 Petite et al. Aug 2007 B2
7267014 Winter Sep 2007 B2
7272635 Longtin et al. Sep 2007 B1
7292143 Drake et al. Nov 2007 B2
7295128 Petite Nov 2007 B2
7301456 Han Nov 2007 B2
7304587 Boaz Dec 2007 B2
7315257 Patterson et al. Jan 2008 B2
7342504 Crane et al. Mar 2008 B2
7346030 Cornwall Mar 2008 B2
7349766 Rodgers Mar 2008 B2
7353280 Chiles et al. Apr 2008 B2
7356614 Kim et al. Apr 2008 B2
7363031 Aisa Apr 2008 B1
7385524 Orlosky Jun 2008 B1
7397907 Petite Jul 2008 B2
7412882 Lazar et al. Aug 2008 B2
7417557 Osterloh et al. Aug 2008 B2
7423985 Hill Sep 2008 B1
7424527 Petite Sep 2008 B2
7443313 Davis et al. Oct 2008 B2
7444401 Keyghobad et al. Oct 2008 B1
7453373 Cumeralto et al. Nov 2008 B2
D583692 Ball et al. Dec 2008 S
7468661 Petite et al. Dec 2008 B2
7478108 Townsend et al. Jan 2009 B2
7480501 Petite Jan 2009 B2
7526539 Hsu Apr 2009 B1
7533693 Colton et al. May 2009 B2
7549439 Kimura et al. Jun 2009 B2
7604216 Gebler et al. Oct 2009 B2
7650425 Davis et al. Jan 2010 B2
7671480 Pitchford et al. Mar 2010 B2
7690393 Nagle et al. Apr 2010 B2
7694934 Irwin Apr 2010 B2
7697492 Petite Apr 2010 B2
7739378 Petite Jun 2010 B2
7746246 Salser Jun 2010 B2
7752309 Keyghobad et al. Jul 2010 B2
7756086 Petite et al. Jul 2010 B2
7760703 Kubler et al. Jul 2010 B2
7775422 Winter et al. Aug 2010 B2
7783738 Keyghobad et al. Aug 2010 B2
7792946 Keyghobad et al. Sep 2010 B2
7806382 Palumbo et al. Oct 2010 B1
7817063 Hawkins et al. Oct 2010 B2
7825793 Spillman et al. Nov 2010 B1
7843379 Menzer et al. Nov 2010 B2
7870080 Budike, Jr. Jan 2011 B2
7880641 Parris et al. Feb 2011 B2
7962101 Vaswani et al. Jun 2011 B2
7980317 Preta et al. Jul 2011 B1
8014791 Guigne et al. Sep 2011 B2
8109131 Winter Feb 2012 B2
8140667 Keyghobad et al. Mar 2012 B2
8249042 Sparr et al. Aug 2012 B2
8300626 Thubert et al. Oct 2012 B2
8351409 Albert et al. Jan 2013 B2
8391177 Picard Mar 2013 B2
8407333 Keyghobad et al. Mar 2013 B2
8549131 Keyghobad et al. Oct 2013 B2
8660134 Splitz Feb 2014 B2
20010010032 Ehlers et al. Jul 2001 A1
20010013488 Fukunaga et al. Aug 2001 A1
20010024163 Petite Sep 2001 A1
20010048030 Sharood Dec 2001 A1
20020013679 Petite Jan 2002 A1
20020019725 Petite Feb 2002 A1
20020031101 Petite Mar 2002 A1
20020051546 Bizjak May 2002 A1
20020062392 Nishikawa et al. May 2002 A1
20020067717 Raschke et al. Jun 2002 A1
20020073183 Yoon et al. Jun 2002 A1
20020089802 Beckwith Jul 2002 A1
20020130768 Che et al. Sep 2002 A1
20020159434 Gosier et al. Oct 2002 A1
20020169643 Petite Nov 2002 A1
20020190956 Klein Dec 2002 A1
20030009515 Lee et al. Jan 2003 A1
20030018733 Yoon Jan 2003 A1
20030018776 Yoon et al. Jan 2003 A1
20030034900 Han Feb 2003 A1
20030036810 Petite Feb 2003 A1
20030046377 Daum Mar 2003 A1
20030074109 Jeong Apr 2003 A1
20030076241 Middleton Apr 2003 A1
20030093484 Petite May 2003 A1
20030107485 Zoratti Jun 2003 A1
20040010561 Kim et al. Jan 2004 A1
20040054747 Breh et al. Mar 2004 A1
20040129312 Cuzzo et al. Jul 2004 A1
20040139210 Lee et al. Jul 2004 A1
20040158333 Ha et al. Aug 2004 A1
20040183687 Petite et al. Sep 2004 A1
20050067022 Istre Mar 2005 A1
20050078631 Conrwell Apr 2005 A1
20050084418 Hill et al. Apr 2005 A1
20050096753 Arling May 2005 A1
20050104747 Silic et al. May 2005 A1
20050121880 Santangelo Jun 2005 A1
20050159823 Hayes Jul 2005 A1
20050190784 Stine Sep 2005 A1
20050195768 Petite Sep 2005 A1
20050195775 Petite Sep 2005 A1
20050201379 Zhang Sep 2005 A1
20050201397 Petite Sep 2005 A1
20050203647 Landry Sep 2005 A1
20050246295 Cameron Nov 2005 A1
20050251367 Kahn et al. Nov 2005 A1
20060012491 Mahowald Jan 2006 A1
20060028355 Patterson Feb 2006 A1
20060041655 Holloway Feb 2006 A1
20060046664 Paradiso et al. Mar 2006 A1
20060098576 Brownrigg May 2006 A1
20060158347 Roche Jul 2006 A1
20060181414 Bandy et al. Aug 2006 A1
20060201550 Blyth et al. Sep 2006 A1
20060218266 Matsumoto et al. Sep 2006 A1
20060273896 Kates Dec 2006 A1
20060284784 Smith et al. Dec 2006 A1
20070059986 Rockwell Mar 2007 A1
20070063866 Webb Mar 2007 A1
20070091825 Budampati et al. Apr 2007 A1
20070284293 Pitchford et al. Dec 2007 A1
20070293221 Hwang et al. Dec 2007 A1
20070298779 Wolman et al. Dec 2007 A1
20080030319 McKeena et al. Feb 2008 A1
20080061769 Junk et al. Mar 2008 A1
20080095403 Benhammou Apr 2008 A1
20080109090 Esmaili et al. May 2008 A1
20080149180 Parris et al. Jun 2008 A1
20080169910 Greene et al. Jul 2008 A1
20080186898 Petite Aug 2008 A1
20080189056 Heidl et al. Aug 2008 A1
20080281534 Hurley Nov 2008 A1
20080291054 Groft Nov 2008 A1
20090058676 Orlosky Mar 2009 A1
20090066524 Yukawa et al. Mar 2009 A1
20090068947 Petite Mar 2009 A1
20090121860 Kimmel et al. May 2009 A1
20090133887 Garcia et al. May 2009 A1
20090153357 Bushman et al. Jun 2009 A1
20090215424 Petite Aug 2009 A1
20090243840 Petite Oct 2009 A1
20090255346 Hendley et al. Oct 2009 A1
20090271045 Savelle, Jr. et al. Oct 2009 A1
20090287838 Keyghobad et al. Nov 2009 A1
20090301571 Ruhs Dec 2009 A1
20090309755 Williamson et al. Dec 2009 A1
20100017465 Brownrigg Jan 2010 A1
20100039984 Brownrigg Feb 2010 A1
20100060479 Salter Mar 2010 A1
20100156632 Hyland et al. Jun 2010 A1
20100194582 Petite Aug 2010 A1
20100250054 Petite Sep 2010 A1
20100265909 Petite Oct 2010 A1
20100295672 Hyland et al. Nov 2010 A1
20100312881 Davis Dec 2010 A1
20100329232 Tubb et al. Dec 2010 A1
20110018762 Walley et al. Jan 2011 A1
20110030482 Meeusen et al. Feb 2011 A1
20110044276 Albert et al. Feb 2011 A1
20110079402 Darby et al. Apr 2011 A1
20110108136 Margalit et al. May 2011 A1
20110140909 Olson et al. Jun 2011 A1
20120106518 Albert et al. May 2012 A1
20120271686 Silverman Oct 2012 A1
20130083722 Bhargava et al. Apr 2013 A1
20130094537 Hui et al. Apr 2013 A1
20130107772 Splitz et al. May 2013 A1
20130109319 Splitz et al. May 2013 A1
Foreign Referenced Citations (22)
Number Date Country
2476119 Feb 2005 CA
1185838 Jun 1998 CN
2305333 Apr 1997 GB
62-295674 Dec 1987 JP
06-223279 Aug 1994 JP
6300606 Oct 1994 JP
07-116285 May 1995 JP
07231363 Aug 1995 JP
H10-2744 Jan 1998 JP
2000285356 Oct 2000 JP
2002352361 Dec 2002 JP
2006285645 Oct 2006 JP
2008198044 Aug 2008 JP
2012507090 Mar 2012 JP
2012527706 Nov 2012 JP
20130109319 Jul 2013 JP
9810299 Mar 1998 WO
9810394 Mar 1998 WO
2008087911 Jul 2008 WO
2010051287 May 2010 WO
2010135587 Nov 2010 WO
2011159403 Dec 2011 WO
Non-Patent Literature Citations (126)
Entry
Splitz, David. E.; U.S. Patent Application Entitled: Systems and Methods for Time-Based Hailing of Radio Frequency Devices assigned U.S. Appl. No. 13/283,526, filed Oct. 27, 2011, 51 pages.
Hyland; U.S. Patent Application Entitled: Infrastructure Monitoring Devices, Systems and Methods under U.S. Appl. No. 13/101,235, filed May 5, 2011; 28 pgs.
Keyghobad, Seyamak; Issue Notification for U.S. Appl. No. 10/298,300, filed Nov. 18, 2002, mailed Oct. 8, 2008; 1 pg.
Keyghobad, Seyamak; Issue Notification for U.S. Appl. No. 12/243,452 filed Oct. 1, 2008 mailed Jun. 16, 2010; 1 pg.
Keyghobad, Seyamak; Issue Notification for U.S. Appl. No. 12/490,925, filed Jun. 24, 2009; mailed Aug. 18, 2010; 1 pg.
Keyghobad, Seyamak; Issue Notification for U.S. Appl. No. 12/490,957, filed Jun. 24, 2009; mailed Aug. 4, 2010; 1 pg.
Keyghobad, Seyamak; U.S. Patent Application Entitled: Method and Apparatus for Inexpensively Monitoring and Controlling Remotely Distributed Appliances under U.S. Appl. No. 12/490,957, filed Jun. 24, 2009; 33 pgs.
Keyghobad, Seyamak; U.S. Patent Application Entitled: Method and Apparatus for Inexpensively Monitoring and Controlling Remotely Distributed Appliances under U.S. Appl. No. 12/490,867, filed Jun. 24, 2009; 33 pgs.
Keyghobad, Seyamak; Non Final Rejection for U.S. Appl. No. 12/490,867, filed Jun. 24, 2009, mailed Oct. 4, 2010; 13 pgs.
Keyghobad, Seyamak; Non Final Rejection for U.S. Appl. No. 12/490,867, filed Jun. 24, 2009, mailed Mar. 21, 2011; 9 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 12/490,867 filed Jun. 24, 2006, mailed Sep. 7, 2011; 6 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 12/490,867 filed Jun. 24, 2009, mailed Nov. 21, 2011; 17 pgs.
Ball, Marty Scott; U.S. Patent Application Entitled: Valve Meter Assembly and Method under U.S. Appl. No. 13/149,720, filed May 31, 2011; 56 pgs.
Keyghobad, Seyamak; U.S. Patent Application Entitled: Method and Apparatus for Inexpensively Monitoring and Controlling Remotely Distributed Appliances under U.S. Appl. No. 13/372,408, filed Feb. 13, 2012; 34 pgs.
Hyland; International Search Report and Written Opinion for serial No. PCT/US2009/062247, filed Oct. 27, 2009, mailed Dec. 18, 2009; 2 pages.
Splitz, David E.; U.S. Patent Application Entitled: Systems and Methods for Dynamic Squelching in Radio Frequency Devices assigned U.S. Appl. No. 13/339,655, filed Dec. 29, 2011; 50 pgs.
Keyghobad, Seyamak; Non-final office action for U.S. Appl. No. 12/490,925, filed Jun. 24, 2009; mailed Dec. 23, 2009; 12 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 12/490,925, filed Jun. 24, 2009; mailed Aug. 2, 2010; 6 pgs.
Keyghobad, Seyamak; Non-final Office Action for U.S. Appl. No. 13/372,408, filed Feb. 23, 2012; mailed May 25, 2012; 17 pgs.
Keyghobad, Seyamak; Issue Notification for U.S. Appl. No. 12/490,867, filed Jun. 24, 2009, mailed Feb. 29, 2012; 1 pg.
Splitz, David; International Search Report and Written Opinion for serial No. PCT/US11/58260, filed Oct. 28, 2011, mailed Feb. 7, 2012, 3 pgs.
Splitz, David; International Search Report and Written Opinion for serial No. PCT/US12/22060, filed Jan. 20, 2012, mailed Mar. 29, 2012, 8 pgs.
Hyland; International Search Report and Written Opinion for serial No. PCT/US11/035374, filed May 5, 2011, mailed Sep. 13, 2011; 7 pgs.
Hyland; PCT Application Entitled: Infrastructure Monitoring Devices, Systems, and Methods having serial No. PCT/US11/35374, filed May 15, 2011, 24 pgs.
Splitz, David; PCT Application entitled: Systems and Methods for Dynamic Squelching in Radio Frequency Devices having serial No. PCT/US12/022060, filed Jan. 20, 2012, 39 pgs.
Splitz, David; PCT Application entitled: Systems and Methods for Time-Based Hailing of Radio Frequency having serial No. PCT/US11/058260, filed Oct. 28, 2011, 51 pgs.
Hyland; PCT Appplication entitled: Infrastructure Monitoring Devices, Systems, and Methods having serial No. PCT/US10/35666, filed May 20, 2010; 31 pgs.
Hyland; International Search Report and Written Opinion for serial No. PCT/US10/035666, filed May 20, 2010, mailed Jul. 16, 2010, 2 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 13/372,408, filed Feb. 13, 2012, mailed Jul. 27, 2012; 11 pgs.
Keyghobad, Seyamak; Supplemental Notice of Allowance for U.S. Appl. No. 13/372,408, filed Feb. 13, 2012; mailed Aug. 2, 2012; 7 pgs.
Young et al. “Real-Time Intranet-Controlled Virtual Instrument Multiple-Circuit Power Monitoring,” IEEE Transactions on Instrumentation and Measurement, Jun. 2000. vol. 49, No. 3, p. 570. [Accessed Dec. 29, 2011] http://ieeexplore.ieee.org/xpls/abs—all.jsp?.
De Almeida et al. “Advanced Monitoring Technologies for the Evaluation of Demand-Side Management Programs,” IEEE Transactions on Power Systems, Aug. 1994. vol. 9, No. 3. [Accessed Dec. 29, 2011] http://ieeexplore.ieee.org/xpls/abs—all.jsp?arnumber=336086.
Dolezilek. “Microprocesor Based Relay Information Improves the Power System,” Rural Electric Power Conference, May 1999. p. B5/1-B5/9. [Accessed Dec. 29, 2011] http://ieeexplore.ieee.org/xpls/abs—all.jsp?arnumber=768685.
Gehami et al. “Electronic Control System I Salient Feature in Substation,” Transmission & Distrubition, Mar. 1991. vol. 43, No. 3, p. 48. [Accessed Dec. 29, 2011—ProQuest].
Horlent. “New Metering and Reading Techniques Based on a Modular Design Concept,” 10th International Conference on Electricity Distribution, May 1989, vol. 5, p. 455-459. [Accessed Dec. 29, 2011—IEEExplore].
“In Brief,” Land Mobile Radio News, Jan. 16, 1998. vol. 52, No. 3, p. 1. [Accessed Dec. 29, 2011—ProQuest] http://proquest.umi.com/pqdweb?did=25435781&sid=1&Fmt=3&clientId=31810&RQT=309&VName%20=PQD.
“Landis & Gyr Utilities: Service Partnership Helps Utilities Use Available Resources More Effectively,” www.landisgyr.com/utilities/e/fr—press1—e.htm (archived Feb. 6, 1998) http://web.archive.org/web/19980206060801/http://www.landisgyr.com/utilities.
Hyland; PCT Application entitled: Infrastructure Monitoring System and Method having serial No. PCT/US09/62247, filed Oct. 27, 2009, 30 pgs.
ANSI; “Protocol Specification for ANSI Type 2 Optical Port”, American National Standard, ANSI C.12.18-2006, 11 pgs.
Federal Communications Commission; “Understanding the FCC Regulations for Low-Power, Non-Licensed Transmitters”, Office of Engineering and Technology; Oct. 1993; 34 pgs.
General Electric; “GEH-5081 kV Meter Product Manual”, Nov. 1997, 137 pgs.
General Electric; “kV RSX—RS232/RS485 Communications Options: Instructions Manual”; Mar. 1999, 33 pgs.
AMCO; “Pit Water-Meter Transponder (PWT)”; AMCO Automated Systems, LLC; PDB-14611; Sep. 2002; 2 pgs.
AMCO; “Short-Range Programmer (SRP) VRT”; AMCO Automated Systems, LLC; PDB-14555.1; Sep. 2002; 2 pgs.
AMCO; Remote Water-Meter Transponder (RWT); AMCO Automated Systems, LLC; PDB-14610; Sep. 2002; 2 pgs.
Article entitled: “Remote Meter Reading”, http://www.meter.co.uk/RMR.html; accessed on Jul. 30, 2012, 2 pgs.
Mexico Office Action for serial No. MX/a/2011/004330, filed Apr. 25, 2011, mailed Mar. 21, 2013, 4 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 13/590,954, filed Aug. 21, 2012, mailed Mar. 21, 2013, 22 pgs.
Hyland, Gregory E.; Final Office Action for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, mailed Apr. 10, 2013, 80 pgs.
Article entitled: “Datamatic, Badger Connect for AMR Solutions”, http://www.datamatic.com/badger—partnership.html; accessed on Jul. 27, 2012, 1 pg.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, mailed Oct. 18, 2012; 44 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; 31 pgs.
Hyland; U.S. Provisional Patent Application entitled: Water Supply Infrastructure Monitoring System and Method, having U.S. Appl. No. 61/108,770, filed Oct. 27, 2008, 11 pgs.
Hyland; U.S. Provisional Patent Application entitled: Water Supply Infrastructure Monitoring System and Method, having U.S. Appl. No. 61/180,600, filed May 22, 2009, 14 pgs.
Hyland; U.S. Patent Application entitled: Infrastructure Monitoring System and Method, having U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, 30 pgs.
Keyghobad, Seyamak; Requirement for Restriction/ Election for U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; mailed Feb. 9, 2006; 11 pages.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 13/372,408, filed Feb. 13, 2012; mailed Nov. 1, 2012; 18 pgs.
European Search Report for serial No. EP2433440, filed Nov. 18, 2011, mailed Nov. 21, 2012, 6 pgs.
Mexico Office Action for serial No. MX/a/2011/01283, filed May 20, 2010, mailed Nov. 21, 2012, 3 pgs.
Hyland; International Search Preliminary Report on Patentability for serial No. PCT/US11/035374, filed May 15, 2011, mailed Dec. 19, 2012; 5 pgs.
Patterson, Tim; Request for Ex Parte Reexamination under U.S. Appl. No. 90/012,468, filed Sep. 16, 2012; 52 pgs.
Patterson, Tim; Request for Ex Parte Reexamination under U.S. Appl. No. 90/012,449, filed Aug. 23, 2012; 51 pgs.
Hyland; International Preliminary Report on Patentability for serial No. PCT/US2009/062247, filed Oct. 27, 2009, mailed May 3, 2011, 7 pgs.
Keyghobad, Seyamak; Examiner Interview Summary Record for U.S. Appl. No. 10/298,300, filed Nov. 18, 2002; mailed Feb. 5, 2008; 2 pages.
Keyghobad, Seyamak; Non-Final Rejection for U.S. Appl. No. 10/298,300, filed Nov. 18, 2002; mailed Oct. 26, 2007; 36 pages.
Keyghobad, Seyamak; Requirement for Restriction/ Election for U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; mailed Feb. 27, 2006; 17 pages.
Keyghobad,Seyamak; U.S. Patent Application entitled: Method and Apparatus for Inexpensively Monitoring and Controlling Remotely Distributed Appliances under U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; 40 pages.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 12/243,452; filed Oct. 1, 2008; mailed Mar. 22, 2010; 8 pages.
Keyghobad, Seyamak; Examiner Interview Summary Record for U.S. Appl. No. 12/243,452; filed Oct. 11, 2008; mailed Dec. 7, 2009; 3 pages.
Keyghobad, Seyamak; Non-Final Rejection for U.S. Appl. No. 12/243,452; filed Oct. 1, 2008; mailed Sep. 14, 2009; 12 pages.
Keyghobad,Seyamak; Non-Final Rejection for U.S. Appl. No. 12/243,452; filed Oct. 1, 2008; mailed May 1, 2009; 5 pages.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 12/490,925; filed Jun. 24, 2009; mailed Jul. 19, 2010; 9 pages.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 12/490,925; filed Jun. 24, 2009; mailed Jun. 28, 2010; 10 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 12/490,957; filed Jun. 24, 2009; mailed Jun. 24, 2010; 10 pgs.
Keyghobad,Seyamak; Non-Final Rejection for U.S. Appl. No. 12/490,957; filed Jun. 24, 2009; mailed Dec. 23, 2009; 17 pgs.
Keyghobad, Seyamak; U.S. Patent Application Entitled: Method and Apparatus for Inexpensively Monitoring and Controlling Remotely Distributed Appliancesl under U.S. Appl. No. 12/243,452; filed Oct. 1, 2008; 33 pages.
Keyghobad, Seyamak; U.S. Patent Application Entitled: Method and Apparatus for Inexpensively Monitoring and Controlling Remotely Distributed Appliances under U.S. Appl. No. 12/490,925; filed Jun. 24, 2009; 33 pgs.
Keyghobad, Seyamak; Non-Final Rejection for U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; mailed May 18, 2006; 14 pages.
Keyghobad, Seyamak; Non-Final Rejection or U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; mailed Jun. 6, 2007; 33 pages.
Keyghobad, Seyamak; Certificate of Correction for U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; mailed Mar. 31, 2009; 1 page.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 10/298,300; filed Nov. 18, 2002; mailed Jul. 14, 2008; 6 pages.
Hyland; European Search Report for serial No. EP09824079.9, filed Oct. 27, 2009, mailed May 8, 2012; 38 pages.
Tamarkin; “Automated Meter Reading”; Public Power Magazine, vol. 50, No. 5; Sep. 1992; accessed Dec. 29, 2011 at http://www.usclcorp.com/news/Automatic—Power—reading.pdf; 7 pgs.
Keyghobad, Seyamak; Non-Final Office Action for U.S. Appl. No. 13/590,954, filed Aug. 21, 2012, mailed Dec. 13, 2012; 39 pgs.
Trace; “Pit Water-Meter Transponder User Guide”; Jan. 2003; 16 pgs.
Keyghobad, Seyamak; U.S. Patent Application entitled: Method and Apparatus for Inexpensively Monitoring and Controlling Remotely Distributed Appliances for U.S. Appl. No. 13/590,954, filed Aug. 21, 2012, 25 pgs.
Keyghobad, Seyamak; Issue Notification for U.S. Appl. No. 13/372,408, filed Feb. 13, 2012, mailed Mar. 6, 2013, 1 pg.
Japanese Office Action for serial No. 2011-533427, filed Oct. 27, 2009, mailed Apr. 13, 2013, 15 pgs.
Mexico Office Action for serial No. MX/A/2011/01283, filed May 20, 2010, mailed May 9, 2013, 8 pgs.
Hyland; International Preliminary Report on Patentability for serial No. PCT/US2010/035666, filed May 20, 2010, mailed Nov. 12, 2011, 6 pgs.
Splitz, David Edwin; Non-Final Office Action for U.S. Appl. No. 13/283,526, filed Oct. 27, 2011, mailed Jun. 18, 2013, 67 pgs.
Hyland, Gregory; Mexico Office Action for serial No. MX/a/2012/015236, filed Dec. 19, 2012, mailed Jun. 13, 2013, 4 pgs.
Keyghobad, Seyamak; Notice of Allowance for U.S. Appl. No. 13/590,954, filed Aug. 21, 2012, mailed Jul. 9, 2013, 21 pgs.
Hyland, Gregory; Mexico Office Action for serial No. MX/a/2011/004330, filed Apr. 25, 2011, mailed Jul. 18, 2013, 6 pgs.
Hyland, Gregory E., Non-Final Office Action for U.S. Appl. No. 13/101,235, filed May 5, 2011, mailed Jul. 31, 2013; 57 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, mailed Sep. 6, 2013; 53 pgs.
Splitz, David Edwin; Non-Final Office Action for U.S. Appl. No. 13/339,655, filed Dec. 29, 2011, mailed Sep. 16, 2013, 57 pgs.
Hyland, Gregory; Mexico Office Action for serial No. MX/A/2011/012383, filed May 20, 2010, mailed Sep. 3, 2013, 10 pgs.
Hyland, Gregory; Mexico Office Action for serial No. MX/a/2011/004330, filed Oct. 27, 2009, mailed Oct. 3, 2013, 6 pgs.
Hyland, Gregory; Mexico Office Action for serial No. MX/a/2012/015236, filed Nov. 18, 2011, mailed Oct. 3, 2013, 8 pgs.
Hyland, Gregory; Japanese Office Action for serial No. 2012-512048, filed May 20, 2010, mailed Oct. 22, 2013, 51 pgs.
Splitz, David Edwin; Notice of Allowance for U.S. Appl. No. 13/283,526, filed Oct. 27, 2011, mailed Oct. 9, 2013, 16 pgs.
Vonroll Hydro—Hydrojournal, pp. 1-16, May 2008.
English Translation: Vonroll Hydro—Hyrdojournal, Technology with a Future for Shut-off Systems—p. 4, Von Roll Hydro (shop) GmbH—New Concepts for Apprentice Training—p. 12, May 2008.
Von Roll Hydro—Hydrojournal, pp. 1-16, Nov. 2008.
English Translation: Von Roll Hydro—Hyrdojournal,VonRoll Hydroalert—Provides a Warning in the Event of Any Tampering with the Water Supply, p. 3, Nov. 2008.
Keyghobad, Seyamak, Issue Notification for U.S. Appl. No. 13/590,954, filed Aug. 21, 2012, mailed Sep. 11, 2013, 1 pg.
Hyland, Gregory; Australian Patent Examination Report for serial No. 2009308949, filed Oct. 27, 2009, mailed Nov. 12, 2013, 3 pgs.
Hyland, Gregory E.; Final Office Action for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, mailed Dec. 17, 2013, 54 pgs.
Hyland, Gregory E.; Japanese Office Action for serial No. 2011-533427, filed Oct. 27, 2009, mailed Feb. 4, 2014, 50 pgs.
Hyland, Gregory; Mexico Office Action for serial No. MX/a/2012/015236, filed Dec. 19, 2012, mailed Dec. 3, 2013, received by foreign associate on Jan. 9, 2014, 4 pgs.
Hyland, Gregory E.; Mexico Final Office Action for serial No. MX/A/2011/012383, filed May 20, 2010, mailed Jan. 9, 2014, 9 pgs.
Hyland, Gregory E.; Final Office Action for U.S. Appl. No. 13/101,235, filed May 5, 2011, mailed Feb. 20, 2014; 29 pgs.
Splitz, David Edwin; Issue Notification for U.S. Appl. No. 13/283,526, filed Oct. 27, 2011, mailed Feb. 5, 2014, 1 pg.
Hyland, Gregory E.; Applicant Initiated Interview Summary for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, mailed Feb. 18, 2014, 4 pgs.
Ball, Marty Scott; Non-Final Office Action for U.S. Appl. No. 13/149,720, filed May 31, 2011, mailed Mar. 11, 2014, 75 pgs.
Splitz, David Edwin: Non-Final Office Action for U.S. Appl. No. 13/339,655, filed Dec. 29, 2011, mailed Mar. 5, 2014, 18 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 12/606,957, filed Oct. 27, 2009, mailed Apr. 8, 2014, 43 pgs.
Ball, Marty Scott; Notice of Allowance for U.S. Appl. No. 13/149,720, filed May 31, 2011, mailed Jun. 24, 2014, 29 pgs.
Hyland, Gregory E.; Non-Final Office Action for U.S. Appl. No. 13/101,235, filed May 5, 2011, mailed Jun. 15, 2014, 29 pgs.
Hyland, Gregory E.; Australian Patent Examination report for serial No. 2010249499, filed Nov. 17, 2011, mailed Jun. 16, 2014, 5 pgs.
Hyland, Gregory E.; Japanese Office Action for serial No. 2013515338, filed Jan. 30, 2012, mailed Jun. 10, 2014, 8 pgs.
Splitz, David Edwin; Notice of Allowance for U.S. Appl. No. 13/339,655, filed Dec. 29, 2011, mailed May 23, 2014, 39 pgs.
Splitz, David; International Preliminary Report on Patentability for serial No. PCT/US11/58260, filed Oct. 28, 2011, mailed May 8, 2014, 7 pgs.
Splitz, David; International Preliminary Report on Patentability for serial No. PCT/US12/22060, filed Jan. 20, 2012, mailed May 8, 2014, 6 pgs.
antenna. Merriam-Webster Dictionary, 2014 [retrieved on Jun. 1, 2014]. Retrieved from the Internet: <URL:www.merriam-webster.com/dictionary/antenna>.
Related Publications (1)
Number Date Country
20100295672 A1 Nov 2010 US
Provisional Applications (1)
Number Date Country
61180600 May 2009 US