EP4630767A1

EP4630767A1 - Location and flow rate meter

Info

Publication number: EP4630767A1
Application number: EP23824954.4A
Authority: EP
Inventors: Daniel Milne KRYWYJ
Original assignee: Aquam Water Services Ltd
Current assignee: Aquam Water Services Ltd
Priority date: 2022-12-06
Filing date: 2023-12-06
Publication date: 2025-10-15
Also published as: AU2023391257A1; WO2024121550A1

Abstract

Apparatuses and methods for detecting and determining flow in a water release assembly using a flow monitoring module are provided. The flow monitoring module includes an attachment structure for attaching to an external fluid flow conduit, a flow meter for detecting fluid flow through the external fluid flow conduit, a fluid flow processing module, and a solar cell configured to provide electrical energy to the fluid flow processing module. The fluid flow processing module is configured to acquire and store location data related to a geographic location of the flow monitoring module; to store fluid flow data related to fluid flow through the external fluid flow conduit and based, at least in part, on the fluid flow detected by the flow meter; and to wirelessly transmit the location data and the fluid flow data to an external computer.

Description

LOCATION AND FLOW RATE METER

RELATED APPLICATION(S)

[0001] A PCT Request Form is filed concurrently with this specification as part of the present application. Each application that the present application claims benefit of or priority to as identified in the concurrently filed PCT Request Form is incorporated by reference herein in its entirety and for all purposes.

BACKGROUND

[0002] Fluid may be flowed through various conduits of a fluid delivery system and flowed out of the fluid delivery system at multiple geographical locations using various fluid extraction assemblies.

[0003] F or example, fresh water distribution systems in municipalities have a network of water mains and other pipes that carry water to various customers and other destinations. It is difficult to monitor and control disposition of water throughout the network, particularly in real time.

This is particularly true when water release elements such as standpipes can be easily installed at various locations throughout the network.

SUMMARY

[0004] The systems, methods and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein. Included among these aspects are at least the following implementations, although further implementations may be set forth in the detailed description or may be evident from the discussion provided herein.

[0005] According to some embodiments, a flow monitoring module includes an attachment structure, a flow meter, a fluid flow processing module, and a solar cell. The flow meter is configured to detect fluid flow through the external fluid flow conduit. The fluid flow processing module is configured to acquire and store location data. The location data is related to a geographic location of the flow monitoring module. The fluid flow processing module is also configured to store fluid flow data. The fluid flow data is related to fluid flow through the external fluid flow conduit and is based, at least in part, on the fluid flow detected by the flow meter. The fluid flow processing module is further configured to wirelessly transmit the location data and the fluid flow data to an external computer. The solar cell is configured to generate and provide electrical energy to the fluid flow processing module.

[0006] In some embodiments, the flow monitoring module may further include a battery charging circuit configured to control charging of a battery using electrical energy generated by the solar cell.

[0007] In some embodiments, the external fluid flow conduit may include at least a portion of a standpipe.

[0008] In some embodiments, the flow monitoring module may further include a circuit configured to provide the fluid flow processing module with electrical power from the battery.

[0009] In some embodiments, the battery charging circuit may be configured to limit the charging of the battery to a threshold fraction of the battery’s charge capacity.

[0010] In some embodiments, the threshold fraction may be about 40% to about 80% of the battery’s charge capacity.

[0011] In some embodiments, the flow monitoring module may further include a housing having a transparent or semitransparent enclosure that allows solar radiation to reach the solar cell.

[0012] In some embodiments, the attachment structure may include a clamp.

[0013] In some embodiments, the fluid flow processing module may include a global positioning satellite (GPS) antenna and a wireless antenna, and the fluid flow processing module may be further configured to acquire the location data using the GPS antenna and to transmit the location data and the fluid flow data using the wireless antenna.

[0014] In some embodiments, the wireless antenna may be one or more of: a cellular antenna, a Code Division Multiple Access (CDMA) antenna, a Global System for Mobile Communications (GSM) antenna, a low power wide area network (LoRaWAN) antenna, an antenna capable of operating between 850 MHz and 1,900 MHz, an antenna capable of operating between 2.4 GHz and 5 GHz, a Bluetooth antenna, an omnidirectional antenna, or a directional antenna.

[0015] According to some embodiments, a method includes controlling power delivery from a solar cell of a flow monitoring module to one or more components of the flow monitoring module, attempting to acquire location data of the flow monitoring module, acquiring and storing fluid flow data related to fluid flow through a fluid flow conduit attached to the flow monitoring module, creating a record that includes the fluid flow data and the location data, and attempting to wirelessly connect with a wireless network and transmit the fluid flow data and the location data.

[0016] In some embodiments, the method may further include controlling charging of a battery with electrical energy generated by the solar cell in the flow monitoring module.

[0017] In some embodiments, the new record may further include a time and date when the record was created.

[0018] In some embodiments, the new record may further include information about the battery.

[0019] In some embodiments, the information about the battery may include the battery’s voltage and/or the battery’s charge level.

[0020] In some embodiments, the external fluid flow conduit may include at least a portion of a standpipe.

[0021] In some embodiments, controlling charging of a battery may include limiting the charging of the battery to a threshold fraction of the battery’s charge capacity.

[0022] In some embodiments, the threshold fraction may be about 40% to about 80% of the battery’s charge capacity.

[0023] In some embodiments, the flow monitoring module may include a housing having a transparent or semitransparent enclosure that allows solar radiation to reach the solar cell.

[0024] In some embodiments, the flow monitoring module may include an attachment structure attached to the fluid flow conduit.

[0025] In some embodiments, attempting to acquire location data may include using a GPS antenna, and attempting to wirelessly connect with the wireless network may include using a wireless antenna.

[0026] In some embodiments, acquiring and storing fluid flow data may further include detecting fluid flow through the fluid flow conduit, and the method may further include, after the detecting, the attempting to acquire location data.

[0027] In some embodiments, the method may further include acquiring and storing the location data of the flow monitoring module; after acquiring and storing the location data, acquiring a wireless connection with the wireless network; and after acquiring the wireless connection, wirelessly transmitting the location data and the fluid flow data to an external computer.

[0028] The foregoing general description and the following detailed description are illustrative and explanatory and are intended to provide further explanation of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

[0029] F igure 1 depicts an example water release assembly.

[0030] Figure 2 depicts another example water release assembly, which is a standpipe.

[0031] Figures 3 A and 3B depict a cross-sectional view of an example flow meter having a movement mechanism inside a chamber.

[0032] Figure 4 depicts a schematic of an example processing module.

[0033] Figure 5 A schematically depicts an example of a flow monitoring and processing module.

[0034] Figures 5B-5D depict various views of an upper partial enclosure of the flow monitoring and processing module of Figure 5 A.

[0035] Figure 6 depicts an example technique of operating a water release assembly.

[0036] F igure 7 depicts an example record.

[0037] Figure 8 depicts an example map showing multiple water release assemblies.

DETAILED DESCRIPTION OF SOME EMBODIMENTS

[0038] In the following description, numerous specific details are set forth in order to provide a thorough understanding of the presented concepts. The presented concepts may be practiced without some or all of these specific details. In other instances, well known process operations have not been described in detail so as to not unnecessarily obscure the described concepts. While some concepts will be described in conjunction with the specific embodiments, it will be understood that these embodiments are not intended to be limiting.

Introduction

[0039] Many water utility districts have numerous above-ground water access points or taps where water may be drawn from an overall water distribution system. These water access points may include fire hydrants, water spouts, spigots, and standpipes. A single water utility district may have thousands of these access points distributed throughout geographic regions that could be tens or hundreds of miles in size. These access points are available and used for many types of uses, such as commercial, residential, and other municipal uses; these uses may include filling water tanks for commercial construction, filling up a fire truck tank, filling up a ferry tank, irrigating an agricultural area, and providing drinkable water to remote locations.

[0040] These discharge locations generally do not have a means for easily tracking from which access point water was drawn, who drew water from an access point, and how much water was drawn from an access point. Employees or contractors may go to field sites and read meter values at access points, but this is a slow and inconvenient technique and frequently misses significant amounts of water release. In some instances, a meter is connected to an electronic device for detecting water flow and/or transmitting information about water flow. But such device may require routine service such as replacement of a battery or other power source.

[0041] As a consequence, much water dispensed from access points in water distribution network is wasted or is consumed without payment. Such uncompensated water drawn from access points is deemed nonrevenue water (NRW). Commonly, up to 20% or more of the total water discharged by a water utility across its entire distribution system is NRW. Water release assemblies described herein may be used to determine the location and amount of water drawn from a specific access location in order to determine who drew the water and how much water was drawn, which may be used to generate revenue from the extracted water. These water release assemblies may also be used to quickly stop undesired water releases. In certain embodiments, these assemblies automatically monitor and report water flow by wireless communication.

[0042] As stated above, some water utilities often employ standpipes or similar structures that serve as the aboveground access points. A standpipe may be a free-standing pipe that can be connected to a water conduit of a water supply or system, such as a water main or water delivery pipe. The standpipe may have an inlet through which water enters the standpipe, an outlet from which the water exits the standpipe, and an attachment mechanism configured to connect the inlet to a tap of the water conduit or delivery pipe. This attachment mechanism may be a threaded fitting that may be screwed onto a threaded port of the water conduit. When installed, a standpipe remains in a fixed geographic location until uninstalled. In some cases, standpipes are designed to be easily transportable. For example, a service employee or team may transport a group of standpipes via truck to multiple water access points that each have a tap to which the standpipe may be connected and draw water from any such access point. Further, a service employee can remove a standpipe in one location and install it in a different location. Tracking the installed locations of all the various standpipes in a water distribution system can be challenging. Given this and the inconvenience of manually reading meters of standpipes, water utilities often do not know from which discharge locations water was taken and how much water was taken.

Example Water Release Assemblies

[0043] Some embodiments of the water release assembly described herein (e.g., a standpipe) include a fluid flow passage, a flow meter configured to detect fluid flow through the fluid flow passage and generate fluid flow data related to the fluid flow, and a processing module configured to acquire location data related to the geographic location of the water release assembly and to transmit the location data and the fluid flow data. Figure 1 depicts an example water release assembly 100 that includes a fluid flow passage 102 with two sections of pipe 104A and 104B, a flow meter 106 (encompassed by the dashed line) that has a chamber 108, a first flow sensor 110, and a fluid flow monitoring and processing module 112. As can be seen, the chamber 108 is interposed between the two sections of pipe 104A and 104B such that fluid flowing through the fluid flow passage 102 flows through the chamber 108. While not shown in this figure, chamber 108 includes, in its interior, a flow responsive mechanism that generates signals responsive to the flow rate through chamber 108. These signals may be captured by the first flow sensor 110. Thus, the depicted embodiment has flow sensing components in three parts: the interior of chamber 108, the first flow sensor 110, and fluid flow monitoring and processing module 112. The first flow sensor 110 is depicted positioned on the chamber 108 and may, in practice, be positioned outside, inside, or partially inside the chamber 108.

[0044] The flow meter 106 can take many forms, and need not have the separate components depicted in Figure 1. For example, all the components necessary for detecting flow or quantitating flow rate may be housed in fluid flow monitoring and processing module 112. In another example, all the components are contained in fluid flow monitoring and processing module 112 and first flow sensor 110. Further, while first flow sensor 110 and fluid flow monitoring and processing module 112 are shown connected by a wire, in alternative embodiments they are configured to communicate wirelessly. The flow sensor may also be any of the other sensors, or a combination of sensors, described herein below.

[0045] The fluid flow monitoring and processing module 112 is depicted positioned outside the fluid flow passage 102 and the chamber 108, and may be connected to any of these elements, such as the first section of pipe 104A in Figure 1. This connection may be through the use of mechanical fastening features, such as screws, bolts, ties, clamps, or the like; it may also be through the use of a weld or an adhesive, such as an epoxy, silicone, cyanoacrylate, or UV cure adhesive. The fluid flow monitoring and processing module 112 is shaped with rounded edges and a slim profile, for example, in order to minimize damage to it that could be caused by it catching or being physically impacted during use or transport, such as being thrown in the back or bed of a truck. As described below, in certain embodiments, the flow meter uses magnets on a movable component in order to detect flow, and the fluid flow monitoring and processing module 112 uses antennas to wirelessly transmit and receive data. In certain embodiments, the housing of the fluid flow monitoring and processing module 112 is constructed of a durable material (e.g., so that it may withstand impacts as well as thermal exposure, such as to temperatures of greater than 48 °C and 60 °C, for example, and less than 0 °C and -34 °C, for instance) that does not interfere with the antennas and magnets. As an example, the durable material may be a non-metallic material like a polymer, a plastic, a thermoplastic such as polyethylene (PE), polypropylene (PP), polystyrene (PS), and polyvinyl chloride (PVC). In some embodiments, the material of the housing of the fluid flow monitoring and processing module 112 may be transparent, semitransparent, or at least translucent (hereinafter, collectively or individually referred to as “transparent”) to light of one or more wavelengths or wavelength ranges. For example, the material may be transparent to light in the visible spectrum, e.g., light having a wavelength (or range of wavelengths) between about 380 nm and about 740 nm. In some cases, the level or extent of the transparency of the housing may be contingent upon the inclusion of one or more other components, such as the inclusion of one or more solar cells in association with flow meter 106, etc.

[0046] Figure 2 depicts a more detailed example of a water release assembly, which is a standpipe. Like the water release assembly 100 of Figure 1, the standpipe 200 includes a fluid flow passage 202 having two sections of pipe 204 A and 204B, similar to the two sections of pipe 104A and 104B in Figure 1, a flow meter 206 that has a chamber 208 and a sensor 210, and a fluid flow monitoring and processing module 212. Unless otherwise characterized, these elements may be considered the same as their counterparts in Figure 1. The water release assembly 200 of Figure 2 also includes an inlet 214, an outlet 216, and an attachment structure 218 for attaching the standpipe to an external fluid flow conduit such as a municipal water main (not shown). As discussed above, this attachment structure 218 may be a threaded collar that is configured to be threaded onto a tap of a fluid conduit or pipe. As with Figure 1, the chamber 208 is interposed between the two sections of pipe 204A and 204B such that fluid flowing between these two sections of pipe must flow through the chamber 208. [0047] In some embodiments, the flow meter 206 includes a movement mechanism positioned within the chamber 208 and configured to be contacted and moved by fluid flowing through the chamber. In certain embodiments, the movement mechanism within the chamber is a positive displacement component that responds to fluid flowing between rotating components housed within the chamber. In response to continuous flow, this movement mechanism may repeatedly move along a movement path, which may be cyclic or reciprocating along or around one or more rotational or linear axes, or a combination. This movement can be detected by a signal pick up such as the first flow sensor, which alone or in combination with the fluid flow monitoring and processing module 212 determines a quantity of flow through the chamber. For instance, a first point on the movement mechanism may, in response to flowing fluid, move past a second point on the chamber once per movement cycle and each time this occurs generate a pulse at the second point. Detecting each time the first point passes by the second point, i.e., detecting a pulse, effectively detects one complete movement cycle. Therefore, a total volume or mass of fluid flowing through this chamber may be determined by counting or totaling each cycle detection, and multiplying this total by the known volume of fluid that flows through the chamber each cycle. This detection may also be used for determining specific quantities of flow information, such as a flow rate.

[0048] In some embodiments, the movement mechanisms have magnets which, during flow, generate repeated variations in magnetic field pulses that are detected by sensors located outside the chamber. These pulses are used to determine fluid flow through the chamber. As used herein, a pulse includes any detectable variation in a magnetic field (or other field if magnets are not used). Many waveforms may be employed, including sinusoidal waveforms, square waveforms, triangle waveforms, saw-tooth waveforms, and the like. Various other types of mechanical movement mechanisms may be used to generate signals reflecting a quantity of flow through the water release assembly. Examples include mechanisms that rely on the rotation to drive either a magnetic coupling or a direct gear train connected to a mechanical counter. Further, the mechanism for detecting flowing fluid can produce any of a number of detectable signals, not just magnetic field signals. Examples include capacitive signals, optical signals, acoustic signals, inductive signals, etc.

[0049] Figures 3 A and 3B depict cross-sectional views of an example component of a flow meter, including a movement mechanism in the interior of a water release assembly. The depicted cross-section is through, for example, chamber 208 of Figure 2 and, during operation, fluid flows into (or from) the plane of the page. The depicted component of a flow meter includes a chamber wall 308 with an inner inlet 320, an inner outlet 322, and a movement mechanism with a ring 324 positioned inside a wall with a slot 326. In this example flow meter, fluid enters the inside of the chamber 208 through the inner inlet 320, flows around the inside of the chamber wall 308 and contacts the ring 324, and then exits through the inner outlet 322, as indicated by the arrows. The arrangement of the ring 324 and the slot 326 within the chamber 208 is configured to enable and cause cyclic movement of the ring 324 when it is contacted by fluid flowing through the chamber wall 308. In this embodiment, the ring 324 and slot 326 engage so that, during flow, the ring 324 reciprocates in a radial direction along the slot 326. As it does so, the ring 324 also traverses an angular path, effectively swiveling back-and-forth as it reciprocates along the slot 326. For example, as can be seen in Figures 3A and 3B, fluid flowing in a general clockwise movement, as indicated by the arrows, while also flowing in a z-direction through the chamber 208 causes the ring 324 to also move in a counterclockwise movement. As fluid continues to flow through the chamber wall 308, the ring 324 is caused to repeatedly move along the same movement path which may be considered the cyclic movement.

[0050] In the depicted embodiment, the flow meter 206 includes a magnet 328 that is attached to the ring 324 and an external sensor 210 configured to detect changes in magnetic field produced by the movement of magnet 328. The magnet 328 is seen in Figures 3A and 3B and may be considered positioned at a first point on the ring 324, as described above. The sensor 210 is positioned such that it can detect the variations in magnetic field produced by the movement of the magnet 328. The location of sensor 210 may be considered to be a second point on the chamber 208, as discussed above. The movement of the magnet 328 past the sensor 210 produces a magnetic pulse. The repeated, cyclic movement of the movement mechanism moves the magnet 328 past the sensor 210 each complete cycle, thereby enabling the sensor 210 to repeatedly detect the magnet 328 each time this occurs, thus detecting the magnetic pulse of the movement mechanism at this location. The sensor 210 may respond to each cycle by generating or altering a voltage, which may be detected and stored by the fluid flow monitoring and processing module 212.

[0051] In certain embodiments, the sensor 210 is a Hall effect sensor or a reed switch. A reed switch generally includes two spring loaded metal contacts that are separated from each other within a sealed region. When a magnetic flux of suitable strength, such as produced by near proximity of a magnet within a flow meter component, is applied near the reed switch, the two contacts are caused to touch each other which completes a circuit to generate a voltage applied across the two contacts or otherwise produce a detectable response. Once the magnet is moved away, the two contacts separate and open the electrical circuit. A Hall effect sensor is a transducer that varies a voltage output in response to a magnetic field, such as a magnetic field from a magnet.

[0052] An example chamber and movement mechanism may be a positive displacement volumetric flow meter, such as the Honeywell Elster VI 00. The volumetric meter may have a chamber diameter between about 80 millimeters and about 260 millimeters, a minimum flowrate between about 10 liters per hour and about 100 liters per hour, a starting flowrate between about 2 liters per hour and about 20 liters per hour, and an output pulse of about 0.5 to about 5 liters per pulse.

[0053] In some embodiments, the fluid flow monitoring and processing module is configured to preform one or more of the following functions: receiving and storing fluid flow data, acquiring and storing location data, generating electrical energy from solar radiation, storing electrical energy, and wirelessly transmitting data. The fluid flow data may be related to fluid flow through the fluid flow passage and may be based, at least in part, on the fluid flow detected by the flow meter, which may be sensed data as detected by the sensor. For example, this fluid flow data may be the count of the magnetic pulses produced by the movement mechanism, which may be transmitted as voltage or current pulses from the sensor. The location data, as described below, may include information directly or indirectly specifying the geographic location, e.g., altitude, latitude, and longitude, of the water release assembly.

[0054] Figure 4 schematically depicts an example of a flow monitoring and processing module 430. The depicted fluid flow monitoring and processing module 430 includes a processor 432 that includes a signal detector 434, a counter 436, a clock 438, and a first memory 440. The first memory 440 may be a program memory that stores instructions to be executed by the processor 432 and buffers data for analysis and other processing. The signal detector 434 may be configured to detect a signal generated by the sensor 210. The sensor 210 may be part of the flow meter (e.g., flow meter 206) and external to the fluid flow monitoring and processing module 430. For example, as described above, the sensor 210 may be a reed switch that closes each time the magnet 328 passes by the sensor 210, which in turn generates a voltage signal that is passed to the signal detector 434. Although only one sensor 210 is depicted, the processor 432 may be configured to receive and store signals and data from more than one sensor. The counter 436 may be configured to count and store each signal or pulse from the sensor 210. The clock 438 may be a real time clock or a timer. The fluid flow monitoring and processing module 430 also includes a second memory 442 that may be a rewritable memory that is configured to store data generated by the sensor 210 or other aspects of the fluid flow monitoring and processing module 430, such as the counter 436 and the clock 438. A power source 444, such as a battery, is also a part of the fluid flow monitoring and processing module 430 and is configured to provide power to the elements of the fluid flow monitoring and processing module 430, such as the processor 432 and a communications unit 446. In the depicted embodiment, processing module 430 includes a solar cell and charging circuit 443 connected to power source 444. In some embodiments, electrical energy generated by the solar cell may be provided to power source 444 to charge a battery or other energy storage device. In some embodiments, electrical energy generated by the solar cell may be utilized to power components of the fluid flow monitoring and processing module 430 without flowing to and/or having to be first stored to the battery, and in this manner, energy stored to the battery may be conserved. It is noted, however, that energy stored to the battery may, in some embodiments, be drawn in instances when the energy supplied by the solar cell is insufficient to power components of the fluid flow monitoring and processing module 430 that are being and/or are scheduled to be used. These power management decisions may be provided by one or more of processor 432 and the charging circuit. As such, at least one of the processor 432 and the charging circuit may allow the fluid flow monitoring and processing module 430 to monitor battery levels versus solar current versus operational current requirements and allow power to the delivered from one or more of the solar cell and the power source 444 to power the various components of the fluid flow monitoring and processing module 430. It is also contemplated that the fluid flow monitoring and processing module 430 may be configured to monitor the charge level of a battery in (or of) power source 444 to thereby modulate the battery’s charge level. In certain embodiments, the solar cell and charging circuit 443 may be configured to limit the battery charge level to a defined charge level, such as about 40% to about 80% of the battery’s charge capacity, or about 40% to about 60% of the battery’s charge capacity, or about 50% of the battery’s capacity, but embodiments are not limited thereto. In certain embodiments, the solar cell and charging circuit 443 may be configured to implement other limits on the battery’s charging or discharging process, such as the rate of charge, current profile of the charge, voltage profile of the charge, and/or the like. In some embodiments, one or more of the modes of power delivery, battery charging, battery discharging, etc., processes may be remotely monitored and improved over time through firmware updates to extract more longevity and performance from the charging circuit, the power source 444, the solar cell, and/or other components of the fluid flow monitoring and processing module 430. In some cases, the firmware updates may be provided over-the-air (OTA) or through a physical connection, such as a universal serial bus (USB) connection, but embodiments are not limited thereto. [0055] The processor 432 may execute machine-readable system control instructions that may be cached locally on the first memory 440 and/or may be loaded into the first memory 440 from a second memory 442 and may include instructions for controlling any aspect of the fluid flow monitoring and processing module 430. The instructions may be configured in any suitable way and may by implemented in software, firmware, hard-coded as logic in an ASIC (application specific integrated circuit), or, in other suitable implementation. In some implementations, the instructions are executed in a general-purpose microprocessor, a microcontroller, or other computational device. In some embodiments, the instructions are implemented as a combination of software and hardware. While not shown in Figure 4, the fluid flow monitoring and processing module 430 may additionally include one or more analog and/or digital input/output connection(s) and one or more analog-to-digital and/or digital-to-analog converters.

[0056] The communications unit 446 may include a first antenna 448 and a second antenna 450. The communications unit 446 may be configured to acquire location data about the location of the water release assembly using the first antenna 448, which is configured to connect with an external location device and receive location data from the external location device. The location data may include the latitude, longitude, and altitude, for example, of the fluid flow monitoring and processing module 430, which houses the first antenna 448. For example, the first antenna 448 may be a global positioning satellite (“GPS”) antenna that can establish a connection with multiple GPS satellites, such as GPS satellites 454. Using data from communications with such satellites, the communications unit 446 can determine the location of the water release assembly and thereafter send location data to the processor 432.

[0057] The term “GPS” herein may mean the broader concept of a location system employing one or more satellites, such as satellites 454, that transmit ephemeris (e.g., a table or data file that gives the calculated positions of a satellite at regular intervals throughout a period) and/or position fixing data to a GPS receiver or antenna on a device. The location of the device may be calculated from the position fixing data on the device itself — communications unit 446 in this case — on a secondary device. Multiple satellites may be used in the system with each one communicating ephemeris data and/or position fixing data. The same satellite may communicate both ephemeris data and position fixing data, or ephemeris data and position fixing data may be communicated through separate satellites. The satellites 454 may be satellites in a GPS system, or it may be satellites in another satellite system, such as the Russian Global Navigation Satellite System, the European Union Compass system, the Indian Regional Navigational Satellite System, or the Chinese Compass navigation system. [0058] Some GPS systems use a very slow data transfer speed of 50 bits per second, which means that a GPS receiver, in some cases, has to be on for as long as 12 minutes before a GPS positional fix may be obtained. Once a positional fix is obtained, subsequent positional fixes may take much less time to obtain (assuming that the subsequent positional fix occurs within a sufficiently close interval), but this initial lock-on period requires that the GPS receiver be powered for the entire initial lock-on, which can be taxing on devices with small battery capacities.

[0059] The communications unit 446 may also be configured to wirelessly connect with, and transmit and receive data from, an external device, like a network 458 or remote device 546 (such as computer, server, etc.), using the second antenna 450 that is configured to connect with the external device 456. The communications unit 446 and second antenna 450 may be configured to communicate by an appropriate cellular protocol, such as Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), Long-Term Evolution (LTE), etc. Alternatively or in addition, the communication unit 446 and second antenna 450 may be configured to communicate by a non-cellular wireless protocol, such as a low power wide area network (LoRaWAN) protocol, which operates between 850 MHz and 1,900 MHz, or other sufficiently long range protocol. As an example, the communications unit 446 may be the SIM808 from SIMCom Wireless Solutions, Shanghai, China. The product may be packaged on a printed circuit assembly (“PCA”) with support integrated circuits from Adafruit, Industries of New York, New York. In some embodiments, the communications unit 446 may be a NimbeLink Skywire LTE-M/NB-IoT modem having part number NL-SW-LTE-QBG96-B, but embodiments are not limited thereto.

[0060] As depicted in Figure 4, the processor 432 is connected to a switch 452 that is interposed between the power source 444 and the communications unit 446. The processor 432 may cause the switch 452 to close, which causes power to be delivered to the communications unit 446, or to open which stops the power to the communications unit 446. Although the first and second antennas 448 and 450 are depicted in a single communications unit 446, they may be, in some embodiments, separate units that are individually connected to the power source 444 such that they may be individually powered or powerable. For instance, a first communications unit that includes the first antenna 348, such as a GPS unit with the GPS antenna, may be powered on while a second communications unit that includes the second antenna 450, such as a wireless communications unit that has a wireless antenna, is powered off.

[0061] In certain embodiments, the second memory 442 is configured to store data received from the processor 432 (e.g., count or flow rate data), the first antenna 448 and the second antenna 450, such as location data from the first antenna 448. Firmware updates, which may be received from the second antenna 450, are stored at an appropriate location (e.g., second memory 442) accessible to the processor 432. The processor 432 is also configured to access and transmit data stored in the second memory 442 over the second antenna 448. In some embodiments, the elements of the processor 432 may be communicatively connected with each other and the processor 432 is configured to control each such element, as well as any element of the fluid flow monitoring and processing module 430.

[0062] Figure 5 A illustrates an example structure and housing of a fluid flow monitoring and processing module 510. Figures 5B-5D provide various views of an upper partial enclosure of the housing of the fluid flow monitoring and processing module 510. The module can be divided into an “upper partial enclosure” 512 and a lower “half’ 514. Upper partial enclosure 512 comprises a semitransparent shell designed to permit solar radiation to penetrate and impinge on a solar cell within the fluid flow monitoring and processing module 510. In Figures 5B-5D, the upper partial enclosure 512 is separately illustrated in respective top, side, and perspective views.

[0063] In certain embodiments, upper partial enclosure 512 and/or the lower half 514 may be shaped with rounded edges and a slim profile, for example, to minimize (or at least reduce) damage to it that might be caused by it catching or being physically impacted during use or transport, such as being thrown in the back or bed of a truck. In certain embodiments, upper partial enclosure 512 may include optional geometric protrusions, holes, and/or other features designed to integrate with other components or couplings for or of the fluid flow monitoring and processing module 510.

[0064] As depicted, the semitransparent upper partial enclosure 512 covers a daughter (or secondary) printed circuit board (PCB) 516, which may be configured to support a solar cell 517, a charging circuit (such as the solar cell and charging circuit 443), and an information retrieval (IR) programmer. In this manner, the upper partial enclosure 512 may include a window region 512w overlapping the solar cell 517 to allow predetermined light to propagate therethrough and impinge on the solar cell 517. In some cases, the material of the upper partial enclosure 512 may be opaque (or substantially opaque) to the predetermined light, but may include the window region 512w overlapping the solar cell 517 to allow the predetermined light to propagate therethrough and impinge on the solar cell 517. The secondary PCB 516 may be communicatively coupled to a main PCB 519, and thereby, communicatively coupled to various other components of the flow monitoring and processing module 510 via, for instance, a cable or other communicative connection. For instance, the secondary PCB 516 may support the solar cell 517, the charging circuit, and the IR programmer, and the main PCB 519 may support one or more of a processor (e.g., processor 432), a communication unit (e.g., communication unit 446), a second memory (e.g., second memory 442), a switch (e.g., switch 452), and/or the like.

[0065] The IR programmer may be configured to collect and/or analyze textual descriptions contained in bug reports generated by, for instance, the processor 432 and identifier names and comments in source code files stored to, for example, at least one of the first and second memories 440 and 442 to identify and localize (or otherwise associate) fault conditions with certain processes and/or components of the fluid flow monitoring and processing module 510. For instance, the IR programmer may be configured to localize fault conditions based on similarities between the content of a bug report and the source code, as well as a history of bug reports/solutions and the processes and components of the fluid flow monitoring and processing module 510 being executed and utilized around the time of the fault condition. As such, the IR programmer may be further configured to rank the likelihood of different potential causes (e.g., code blocks or statements) for any given fault condition and provide such information to an external device (e.g., remote device 456) via, for example, communications unit 446. The information provided by the IR programmer may be utilized to remotely diagnose and resolve issues without having to uninstall, dismantle, test, fix, assemble, and reinstall the fluid flow monitoring and processing module 510. To this end, over-the-air firmware updates may be provided to the fluid flow monitoring and processing module 510 via communications unit 446 to address various remotely diagnosed issues. This also helps reduce the likelihood of contaminate (e.g., dirt, water, etc.) ingress into the fluid flow monitoring and processing module 510 as it does not need to be dismantled and reassembled to fix issues. In some embodiments, the IR programmer may also be configured to provide, for instance, water volume measurements via its information providing interface.

[0066] As depicted, the semitransparent upper partial enclosure 412 engages with the lower half 514 of the fluid flow monitoring and processing module 510. The lower half 514 may be configured to provide support for the secondary printed circuit board 516, the mam printed circuit board 519, the solar cell 517, the IR programmer, a power source (e.g., battery 521), and/or the like. A material of the lower half 514 may be the same as or different from the material of the upper partial enclosure 512. Also, the lower half 514 may couple with connection features, e.g., clamps 522, which may be utilized to couple, e g., detachably couple, the fluid flow monitoring and processing module 510 to a pipe or other fluid conduit. Additionally, at least one of the upper partial enclosure 512 and the lower half 514 may include one or more informational portions, such as a display, label, etc., that provide, for instance, instructions, warnings, etc. [0067] According to various embodiments, the fluid flow monitoring and processing module 510 may further include a blanking plug 518, which may be used to cover a charging port and/or one or more auxiliary interfaces/electrical connections of the fluid flow monitoring and processing module 510. In some embodiments, the fluid flow monitoring and processing module 510 may include a magnetically coupled charging point accessible through an opening 512o in the upper partial enclosure 512. The magnetically coupled charging point may be utilized to charge, for example, battery 521 during manufacture. The opening 512o, however, may be sealed via blanking plug 518 after charging the battery 521 as the solar cell 517 may be later utilized to recharge the battery 521.

Example Processing Sequences

[0068] As stated above, the fluid flow monitoring and processing module may be configured to receive and store signals related to fluid flow that are generated by a sensor (and optionally convert those signals to values representing fluid flow rates or volumes, to receive and store location data, and to transmit the fluid flow data and location data). This configuration may include instructions stored on the first or second memories that are executable by the processor. Figure 6 depicts an example processing sequence for a processing module of a water release assembly. The blocks shown in Figure 5 may be implemented by the processor 332 and other components of processing module 330 of Figure 3 executing instructions stored on, for example, the first or second memories 340 and 342.

[0069] The example technique 601 of Figure 5 begins at block 603 in which a pulse from the flow meter is detected. This pulse may be a signal from or generated by the sensor 210 that, as described above, may be an electrical voltage from a reed switch sensor 210. Before receiving a pulse at block 603, the fluid flow monitoring and processing module 430 may be in a sleep state in which power is on to the processor 432, but in a low power mode, with few, if any, operations being performed. At the same time, the communications unit 446 is not powered on. In block 605, the processor 432 exits the low power state, and “wakes up”, in response to detecting the signal from the sensor 210. The pulse or signal is typically interpreted to indicate that flow has started in the flow meter and fluid flow passage. The processor 432 may then simultaneously or sequentially cause various functions to be performed, as described below. The embodiment depicted in Figure 6, the processor, often in conjunction with other components of the processing module, executes four different operations, sometimes concurrently. As shown, the operations are acquiring GPS data, creating and populating a record, logging fluid flow information, and making a network connection. These operations are depicted as separate branches from operation 605. [0070] For example, after waking up, the processor 432 may attempt to acquire location data or cause another component to make the attempt. For example, the processor may power on the communications unit 446 by, for example, causing the switch 452 to close. In response, the communications unit 446 begins attempting to receive a signal from one or more GPS satellites. Alternatively, in some other embodiments, the communications unit may attempt to acquire a signal via a different location providing method, such as by triangulation or other approach using a cellular transmission tower After block 607, oval 609 indicates that a decision or assessment may be made as to whether the signal was successfully acquired. A successful signal acquisition may include both the establishment of a signal as well as the receipt of location data. In some embodiments, the receipt of the location data may be a separate operation. The GPS protocol, for example, has its own sequence of operations, including obtaining or using ephemeris data, obtaining position fixing data, and determining a geographical location. These operations may be performed within operations 607 and 609.

[0071] If the signal was not acquired, then the processing module may repeat operation 607 until a signal is successfully acquired. However, continuously repeating this attempt without success may drain the power source or otherwise interfere with the operation of the fluid flow monitoring and processing module 430. In some embodiments, the processing module 430 may stop making attempts to acquire the signal after a defined number of attempts or a defined period of time has elapsed. For example, simultaneously with or soon after (e.g., within 5 seconds) the attempt of 607 is made, a first timer may be started using the clock 438. If the first timer reaches a first threshold time, such as about 3 minutes or about 5 minutes, (which may be considered the expiration of the first timer), then the attempt to acquire the signal may be stopped by, for instance, powering off the communications unit 446. The first timer may count up from zero to the threshold time, may count down from the threshold time to zero, or may count up from a specific time according to the clock 438. This decision regarding the first timer is represented by block 609 A; if the timer has not expired, then block 607 may be repeated, but if it has reached the first threshold time and expired, then block 611 may be executed. In some embodiments, the turning off of block 611 may include powering off the communications unit 346 that includes both the first and second antennas. In some other embodiments in which the GPS antenna is a part of the GPS unit that is separated powered from the network communications unit, this attempt to acquire the signal may be stopped by powering off the GPS unit.

[0072] If the GPS signal was acquired in operation 607 and with it, sufficient location data to determine the location of the water release assembly, then the GPS antenna may be powered off as indicated in block 611. As described above, this may include powering off the first communications unit that is the GPS unit, or the communications unit that includes both the first and second antennas. In some other embodiments, like the one depicted in Figure 4, if the GPS antenna (the first antenna 448) and a cellular antenna (the second antenna 450) are both part of the same communications unit 446, then the communications unit 446 may remain powered on (thereby skipping block 611) until a record has been stored and/or transmitted. In block 613, the GPS location data, such as the latitude, altitude, and longitude, may be reported to a record in the second memory 442. In some embodiments in which a GPS signal was not acquired, GPS data may still be reported which could include zero values or other information indicating that a GPS signal, and therefore location data, were not acquired. In some embodiments in which the GPS data was not acquired, GPS is not reported (e.g., data is not updated in a record).

[0073] Returning to the point where the processor wakes up (block 605), a record may be created as indicated by block 615. In some embodiments, the contents of the record are stored in the second memory 442. The record may include, at least, some of the location data and the fluid flow data. After creating the record, the processor enters various pieces of information, such the time, date, and power level (e.g., battery voltage) of the power source 444 and other information, into the record. See block 617. Next, as illustrated in block 619, the location data, if available, may be entered into the record. As illustrated such data may be provided via operation 613 in the GPS branch of the process. As stated above, even if location data is not available, some information may be entered such as null or zero values. Next, as illustrated in block 621, the processor enters information about the network to which the communications device is connected, such as the wireless carrier, if available. As explained below such information may come from the communications unit or at least its logic associated with wireless communications.

[0074] Returning to the point where the processor wakes up (block 605), the processing module may capture information associated with fluid flow in a branch of the overall process. As illustrated in block 623, the module logs pulses or other indicia of fluid flow, depending on the type of sensor used. In certain embodiments, the processing module stores or logs such information in the second memory 442. As discussed above, fluid flow data may be provided as voltage pulses from the sensor, a count or counts from the counter 436, or other indicia of fluid flow. Other examples of the types of information that may be provided to indicate a quantity of fluid transferred include optical signals, acoustic signals, electrical signals (e.g., capacitive and/or inductive), and the like. In addition to fluid flow rate or quantity of fluid passed, the processing module may detect other quantities related to the fluid or the conduit; examples include temperature, pressure, etc. For compressible fluids such as gases, pressure, temperature, and volume may all need to be detected/monitored to determine the mass of the fluid that is flowing (or has flowed). Examples of other indicia of fluid flow, particularly acoustic signals, are described in more detail below.

[0075] The fluid flow data may be organized into discrete flows through the water release assembly, with each use being considered an “event.” For example, the water may flow for twenty minutes and the stop for five hours, followed by a second flow for three minutes. The twenty-minute flow and the three-minute flow may be treated as two separate events. In some embodiments, an event begins with receipt the first pulse, which wakes up the processor at operation 605, and ends with a timer timing out after defined period from detection of the last pulse. In one implementation, simultaneously with or soon after (e.g., within 5 seconds) an indicator of fluid flow is received by the fluid flow monitoring and processing module 430, such as a pulse from the sensor 210, a second timer is started using the clock 438. This is indicated by block 625. Each time the fluid flow monitoring and processing module 430 receives such an indicator, the timer is reset. If the second timer reaches a second threshold time, such at about 5 minutes or about 10 minutes, and therefore expires without receiving during that period an indicator of flow, the processing module may conclude that the event has ended. This second timer may perform like the first timer described above, e.g., counting up from zero. Once the event has ended, the information entered into the record, and the record itself, may be stored in a memory, such as the second memory 442, as indicated by block 629.

[0076] In another embodiment, before or after a pulse is detected at operation 603, a check may be made as to whether a detected pulse is a part of an ongoing event. This may include determining whether the second timer, which was started after a previous pulse was detected, has reached the second threshold time. If not, then the detected pulse may be associated with the ongoing event; i.e., the pulse is included in data indicating an accumulated amount of fluid flow during the event.

[0077] Returning to the point where the processor wakes up (block 605), the fluid flow monitoring and processing module may attempt to make a network connection. See block 631. This may include causing the communications unit 446 to attempt to wirelessly connect with a wireless network using the second antenna 450, described above. Similar to operation 609, an operation 633 determines whether the connection was successfully made.

[0078] If the connection was not made, then the processing module may repeat operation 631 until the connection is successful. However, as described in the context of acquiring GPS data, continuously repeating this attempt without success may drain the power source and therefore, in some such embodiments, the fluid flow monitoring and processing module 430 may stop making such attempts. This cessation of attempts may occur after a number of attempts have been made or a period of time has elapsed as determined by a third timer, similar to those described above with reference to blocks 607, 609 and 609A. In some embodiments, for instance, if the third timer reaches a third threshold time without making a connection, then the attempt is stopped. In the embodiments in which the fluid flow processing module includes separately powered GPS unit and wireless communications units, this stopping may be made by powering off the wireless communications unit without powering off the GPS unit. In some other embodiments, this may include powering off the entire communications unit 446 of Figure 4. Additionally, even if the network connection was not made, then the record may still be stored on the memory and sent at a later time once the network connection is made, such as during another event. This may result in multiple records being sent at one time.

[0079] In some implementations, if the attempt to wirelessly connect (631) fails, the processing module may reattempt to connect. If such second attempt fails, the module may store the data on board in memory and shut down operation. Upon a next detected pulse, the module may transmit the stored data as well as any new data.

[0080] If the connection is made, then the network information may be entered into the record as indicated by block 621. Additionally, after the record is stored in block 629, the record may be wirelessly transmitted over the network to, e.g., an external device, such as a computer, server, cell phone, or mobile device, for instance. See block 635. In certain embodiments, the processing module sends not only the most recent record (the one for the just concluded event) but other records for other recent events (e.g., the ten or twenty most recent events). After this transmission, as illustrated by block 637, the communications unit 446 may be powered off. Further, as illustrated in block 639, the fluid flow monitoring and processing module 430 may be placed into a sleep state or low power mode as described above.

[0081] In some embodiments, the fluid flow monitoring and processing module 430 may be configured to periodically send records of multiple events (e.g., the last ten or the last twenty or all of the records stored on the second memory 442) even if there is no location data stored in the records. This may occur, for example, one time per day so to enable the data to be periodically transferred off the fluid flow processing module and to the external device.

[0082] F igure 7 depicts an example record generated by a processing unit. In the depicted example, the record includes the version of firmware on the processor, fluid flow data such as a count or other information related to the fluid flow, the battery voltage, the number of GPS satellites to which the communications unit is connected, the time, the date, the location data that includes the latitude, longitude, and altitude, and network information which may include the cellular network to which the communications unit is connected, such as T-Mobile. Any combination of these items may be included in the record. In various embodiments, the record includes, at least, the location and captured fluid flow information over an appropriate time period for a particular water release assembly.

[0083] In some embodiments, the first antenna 348 and the second antenna 450 are oriented within the fluid flow monitoring and processing module 430 to minimize any interference between the antennas and to maximize their abilities when positioned on the water release assembly. For example, many water release assemblies will be installed in a vertical position, similar to the position of the water release assembly 200 of Figure 2. The first and second antennas 448 and 450 may therefore be positioned such that when the fluid flow monitoring and processing module 212 is in this in-use vertical position, the first and second antennas 448 and 450 are each in their optimal orientations. For instance, an optimal orientation of a GPS antenna may be one that receives vertically directed signals such that its longitudinal axis is parallel to the center axis of the fluid flow passage 202; an optimal orientation of a wireless antenna, like a GSM antenna, may be one that transmits and receives horizontally directed signals, such that its longitudinal axis is perpendicular to the center axis of the fluid flow passage 202. These antennas may also be positioned on opposite ends of the fluid flow monitoring and processing module 212 m order to minimize their interference with each other.

[0084] The data sent over the external network may be ultimately transmitted to a computer or server and stored on a memory device of that computer or server. This data includes any data described above, such as the fluid flow data and location data. Such data can be stored in the format of a record as described above or any other suitable format. In some cases, the data indicates to a user, a municipality, or a company that fluid was flowed out of a specific water access point. This data may also be used to determine how much water was drawn from that water access point and who drew the water. The computer or server may be configured to send an alert to one or more other external devices, such as other servers, mobile devices, and the like, that fluid is being drawn from a specific water access point. This alert may be in the form of an email, pop-up screen, text message, light, and audio signal, for instance.

[0085] Location determination coupled with fluid transport (volume, mass, rate, etc.) is useful not only for identifying where fluid is consumed but also for providing performance indicators based on the functionality and behavior of the pipes, valves, and other infrastructure, as well as services used by the infrastructure. [0086] In some embodiments, this data may be used to provide real-time use of one or more water release assemblies. This may be in the form of a chart or a map that is correlated with the geographic location of each in-use water release assembly. The map may include other information, such as historical use data of the geographic locations of all water release assemblies that were used to draw fluid from a fluid delivery system in a particular region over a certain amount of time. For example, the map may be of sub-region of a water utility district that includes geographic icons which indicate each use of a water release assembly within the past 24 hours. The geographic icons may provide any of the data included in the record as well as other flow related information, such as the total amount of water drawn or the number of events at the location.

[0087] Figure 8 depicts an example map showing multiple water release assemblies. The map 852 is depicted on a screen 854 of a device, such as a computer, and includes a region 862 that represents a geographical region, such as the boundary or a city or utility district. The map 852 includes first geographic icons 856A and 856B that each may represent the real-time use of a single water release assembly, such as a standpipe. The first geographic icons 856A and 856B may provide information about the real-time use, such as the flow rate and total volume drawn during an event, as indicated by the pop-up bubble 860 over the first geographic icon 856A that may be generated when the first geographic icon 856A is selected. Second geographic icons 858A and 858B may indicate past historical use at a particular location and similar pop-up bubbles may be generated to provide the past use at each of those icons. In some embodiments, the real-time and historical uses of a water release assembly or geographic location may be displayed in a chart adjacent to the map 852 on the screen 854.

Other Embodiments

[0088] While the embodiments described herein have focused on water dispensing pipes and water distribution networks, this disclosure extends to other systems and contexts. For example, the fluid measured is not necessarily water or even a liquid. It may be any gas or liquid for which a dispensed or transmitted quantity may need to be measured and reported over a network. Examples of liquids include petroleum (e.g., in a pipeline), chemical feedstocks in chemical plants, and the like. Examples of gases include natural gas (e.g., in pipelines, whether within residences or in gas delivery network administered by a utility), gaseous chemical feedstocks, steam, pressurized air, etc. Further the quantity of fluid transported and the associated location can be detected and transmitted for any fluid conduit, not just pipes. Aqueducts, canals, troughs, and the like may benefit from the embodiments disclosed herein. And the conduits may be used in various contexts including utilities, municipalities, manufacturing plants, large buildings, compounds, complexes, and residences.

[0089] Unless otherwise specified, the illustrated embodiments are to be understood as providing example features of varying detail of some embodiments. Thus, unless otherwise specified, the features, components, modules, regions, aspects, structures, etc. (hereinafter individually or collectively referred to as an “element” or “elements”), of the various illustrations may be otherwise combined, separated, interchanged, and/or rearranged without departing from the teachings of the disclosure.

[0090] The terminology used herein is for the purpose of describing some embodiments and is not intended to be limiting. As used herein, the singular forms, “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It is to be understood that the phrases “for each <item> of the one or more <items>,” “each <item> of the one or more <items>,” and/or the like, if used herein, are inclusive of both a single-item group and multiple-item groups, i.e., the phrase “for . . . each” is used in the sense that it is used in programming languages to refer to each item of whatever population of items is referenced. For example, if the population of items referenced is a single item, then “each” would refer to only that single item (despite dictionary definitions of “each” frequently defining the term to refer to “every one of two or more things”) and would not imply that there must be at least two of those items. Similarly, the term “set” or “subset” should not be viewed, in itself, as necessarily encompassing a plurality of items — it is to be understood that a set or a subset can encompass only one member or multiple members (unless the context indicates otherwise). The terms “comprises,” “comprising,” “includes,” and/or “including,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, components, and/or groups thereof, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It is also noted that, as used herein, the terms “substantially,” “about,” and other similar terms, are used as terms of approximation and not as terms of degree, and, as such, are utilized to account for inherent deviations in measured, calculated, and/or provided values that would be recognized by one of ordinary skill in the art. Accordingly, the term “substantially” as used herein, unless otherwise specified, means within 5% of a referenced value. For example, substantially parallel means within ±5% of parallel. To this end, numerical or mathematical values, including end points of numerical ranges, are not to be interpreted with more significant digits than presented and may be understood to include some variation, such as within 5% of the referenced value or within 1% of the referenced value. For example, perpendicular may, in certain embodiments, mean within +/- 5% of 90 degrees. [0091] The use of cross-hatching and/or shading in the accompanying drawings is generally provided to clarify boundaries between adjacent elements. As such, neither the presence nor the absence of cross-hatching or shading conveys or indicates any preference or requirement for particular materials, material properties, dimensions, proportions, commonalities between illustrated elements, and/or any other characteristic, attribute, property, etc. , of the elements, unless specified. Further, in the accompanying drawings, the size and relative sizes of elements may be exaggerated for clarity and/or descriptive purposes. As such, the sizes and relative sizes of the respective elements are not necessarily limited to the sizes and relative sizes shown in the drawings. When an embodiment may be implemented differently, a specific process order may be performed differently from the described order. For example, two consecutively described processes may be performed substantially at the same time or performed in an order opposite to the described order.

[0092] When an element, such as a layer, is referred to as being “on,” “connected to,” or “coupled to” another element, it may be directly on, directly connected to, or directly coupled to the other element or at least one intervening element may be present. When, however, an element is referred to as being “directly on,” “directly connected to,” or “directly coupled to” another element, there are no intervening elements present. Other terms and/or phrases if used herein to describe a relationship between elements should be interpreted in a like fashion, such as “between” versus “directly between,” “adjacent” versus “directly adjacent,” “on” versus “directly on,” etc. Further, the term “connected” may refer to physical, electrical, and/or fluid connection. To this end, for the purposes of this disclosure, the phrase “fluidically connected” is used with respect to volumes, plenums, holes, etc. , that may be connected to one another, either directly or via one or more intervening components or volumes, to form a fluidic connection, similar to how the phrase “electrically connected” is used with respect to components that are connected to form an electric connection. The phrase “fluidically interposed,” if used, may be used to refer to a component, volume, plenum, hole, etc., that is fluidically connected with at least two other components, volumes, plenums, holes, etc. , such that fluid flowing from one of those other components, volumes, plenums, holes etc., to the other or another of those components, volumes, plenums, holes, etc., would first flow through the “fluidically interposed” component before reaching that other or another of those components, volumes, plenums, holes, etc.. For example, if a pump is fluidically interposed between a reservoir and an outlet, fluid flowing from the reservoir to the outlet would first flow through the pump before reaching the outlet. The phrase "fluidically adjacent," if used, refers to placement of a fluidic element relative to another fluidic element such that no potential structures fluidically are interposed between the two elements that might potentially interrupt fluid flow between the two fluidic elements. For example, in a flow path having a first valve, a second valve, and a third valve arranged sequentially therealong, the first valve would be fluidically adjacent to the second valve, the second valve fluidically adjacent to both the first and third valves, and the third valve fluidically adjacent to the second valve.

[0093] For the purposes of this disclosure, “at least one of X, Y, . . ., and Z” and “at least one selected from the group consisting of X, Y, . . ., and Z” may be construed as X only, Y only, . . ., Z only, or any combination of two or more of X, Y, . . ., and Z, such as, for instance, XYZ, XYY, YZ, and ZZ. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items. In addition, when the word “or” is used in reference to a list of two or more items, that word covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.

[0094] Although the terms “first,” “second,” “third,” etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used to distinguish one element from another element. Thus, a first element discussed below could be termed a second element without departing from the teachings of the disclosure. To this end, use of such identifiers, e.g., “a first element,” should not be read as suggesting, implicitly or inherently, that there is necessarily another instance, e.g., “a second element.” Further, the use, if any, of ordinal indicators, such as (a), (b), (c), . . ., or (1), (2), (3), . . ., or the like, in this disclosure and accompanying claims, is to be understood as not conveying any particular order or sequence, except to the extent that such an order or sequence is explicitly indicated. For example, if there are three steps labeled (i), (ii), and (iii), it is to be understood that these steps may be performed in any order (or even concurrently, if not otherwise contraindicated), unless indicated otherwise. For example, if step (ii) involves the handling of an element that is created in step (i), then step (ii) may be viewed as happening at some point after step (i). In a similar manner, if step (i) involves the handling of an element that is created in step (ii), the reverse is to be understood.

[0095] Spatially relative terms, such as “beneath,” “below,” “under,” “lower,” “above,” “upper,” “over,” “higher,” “side” (e.g., as in “sidewall”), and the like, may be used herein for descriptive purposes, and, thereby, to describe one element’s spatial relationship to at least one other element as illustrated in the drawings. Spatially relative terms are intended to encompass different orientations of an apparatus in use, operation, and/or manufacture in addition to the orientation depicted in the drawings. For example, if the apparatus in the drawings is turned over, elements described as “below” or “beneath” other elements or features would then be oriented “above” or “over” the other elements or features. Thus, the term “below” can encompass both an orientation of above and below. Furthermore, the apparatus may be otherwise oriented (e.g., rotated 90 degrees or at other orientations), and, as such, the spatially relative descriptors used herein interpreted accordingly.

[0096] The term “between,” as used herein and when used with a range of values, is to be understood, unless otherwise indicated, as being inclusive of the start and end values of that range. For example, between 1 and 5 is to be understood as inclusive of the numbers 1, 2, 3, 4, and 5, not just the numbers 2, 3, and 4.

[0097] If used herein, the phrase “operatively connected” is to be understood as referring to a state in which two components and/or systems are connected, either directly or indirectly, such that, for example, at least one component or system can control the other. For instance, a controller may be described as being operatively connected with (or to) a resistive heating unit, which is inclusive of the controller being connected with a sub-controller of the resistive heating unit that is electrically connected with a relay that is configured to controllably connect or disconnect the resistive heating unit with a power source that is capable of providing an amount of power that is able to power the resistive heating unit so as to generate a desired degree of heating. The controller itself likely will not supply such power directly to the resistive heating unit due to the current(s) involved, but it is to be understood that the controller is nonetheless operatively connected with the resistive heating unit.

[0098] As used herein, the singular forms, “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It is also to be understood that the phrases “for each <item> of the one or more <items>,” “each <item> of the one or more <items>,” and/or the like, if used herein, are inclusive of both a single-item group and multipleitem groups, i.e., the phrase “for . . . each” is used in the sense that it is used in programming languages to refer to each item of whatever population of items is referenced. For example, if the population of items referenced is a single item, then “each” would refer to only that single item (despite dictionary definitions of “each” frequently defining the term to refer to “every one of two or more things”) and would not imply that there must be at least two of those items. Similarly, the term “set” or “subset” should not be viewed, in itself, as necessarily encompassing a plurality of items — it is to be understood that a set or a subset can encompass only one member or multiple members (unless the context indicates otherwise). In addition, the terms “comprises,” “comprising,” “includes,” and/or “including,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, components, and/or groups thereof, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

[0099] Various embodiments are described herein with reference to sectional views, isometric views, perspective views, plan views, and/or exploded illustrations that are schematic depictions of idealized embodiments and/or intermediate structures. As such, variations from the shapes of the illustrations as a result of, for example, manufacturing techniques and/or tolerances, are to be expected. Thus, embodiments disclosed herein should not be construed as limited to the particular illustrated shapes of regions, but are to include deviations in shapes that result from, for instance, manufacturing. To this end, regions illustrated in the drawings may be schematic in nature and shapes of these regions may not reflect the actual shapes of regions of a device, and, as such, are not intended to be limiting.

[0100] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure is a part. Terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and are not to be interpreted in an idealized or overly formal sense, unless expressly so defined herein.

[0101] As customary in the field, some embodiments are described and illustrated in the accompanying drawings in terms of functional blocks, units, and/or modules. Those skilled in the art will appreciate that these blocks, units, and/or modules are physically implemented by electronic (or optical) circuits, such as logic circuits, discrete components, microprocessors, hard-wired circuits, memory elements, wiring connections, and the like, which may be formed using semiconductor-based fabrication techniques or other manufacturing technologies. In the case of the blocks, units, and/or modules being implemented by microprocessors or other similar hardware, they may be programmed and controlled using software (e.g., microcode) to perform various functions discussed herein and may optionally be driven by firmware and/or software. It is also contemplated that each block, unit, and/or module may be implemented by dedicated hardware, or as a combination of dedicated hardware to perform some functions and a processor (e.g., one or more programmed microprocessors and associated circuitry) to perform other functions. Also, each block, unit, and/or module of some embodiments may be physically separated into two or more interacting and discrete blocks, units, and/or modules without departing from the inventive concepts. Further, the blocks, units, and/or modules of some embodiments may be physically combined into more complex blocks, units, and/or modules without departing from the teachings of the disclosure. [0102] Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, it will be apparent that certain changes and modifications may be practiced within the scope of the appended claims. It should be noted that there are many alternative ways of implementing the processes, systems, and apparatuses of the disclosed embodiments. Accordingly, embodiments are to be considered as illustrative and not as restrictive, and embodiments are not to be limited to the details given herein.

Claims

CLAIMS What is claimed is:

1. A flow monitoring module comprising: an attachment structure configured to attach to an external fluid flow conduit; a flow meter configured to detect fluid flow through the external fluid flow conduit; a fluid flow processing module configured to: acquire and store location data, wherein the location data is related to a geographic location of the flow monitoring module, store fluid flow data, wherein the fluid flow data is related to fluid flow through the external fluid flow conduit and is based, at least in part, on the fluid flow detected by the flow meter, and wirelessly transmit the location data and the fluid flow data to an external computer; and a solar cell configured to generate and provide electrical energy to the fluid flow processing module.

2. The flow monitoring module of claim 1, further comprising: a battery charging circuit configured to control charging of a battery using electrical energy generated by the solar cell.

3. The flow monitoring module of claim 1, wherein the external fluid flow conduit comprises at least a portion of a standpipe.

4. The flow monitoring module of claim 2, further comprising: a circuit configured to provide the fluid flow processing module with electrical power from the battery.

5. The flow monitoring module of claim 2, wherein the battery charging circuit is configured to limit the charging of the battery to a threshold fraction of the battery’s charge capacity.

6. The flow monitoring module of claim 5, wherein the threshold fraction is about 40% to about 80% of the battery’s charge capacity.

7. The flow monitoring module of claim 1, further comprising: a housing having a transparent or semitransparent enclosure that allows solar radiation to reach the solar cell.

8. The flow monitoring module of claim 1 , wherein the attachment structure comprises a clamp.

9. The flow monitoring module of claim 1 , wherein: the fluid flow processing module includes a global positioning satellite (GPS) antenna and a wireless antenna, and the fluid flow processing module is further configured to: acquire the location data using the GPS antenna; and transmit the location data and the fluid flow data using the wireless antenna.

10. The flow monitoring module of claim 9, wherein the wireless antenna is one or more of: a cellular antenna, a Code Division Multiple Access (CDMA) antenna, a Global System for Mobile Communications (GSM) antenna, a low power wide area network (LoRaWAN) antenna, an antenna capable of operating between 850 MHz and 1,900 MHz, an antenna capable of operating between 2.4 GHz and 5 GHz, a Bluetooth antenna, an omnidirectional antenna, or a directional antenna.

11. A method comprising: controlling power delivery from a solar cell of a flow monitoring module to one or more components of the flow monitoring module; attempting to acquire location data of the flow monitoring module; acquiring and storing fluid flow data related to fluid flow through a fluid flow conduit attached to the flow monitoring module; creating a record that includes the fluid flow data and the location data; and attempting to wirelessly connect with a wireless network and transmit the fluid flow data and the location data.

12. The method of claim 11, further comprising: controlling charging of a battery with electrical energy generated by the solar cell in the flow monitoring module.

13. The method of claim 11, wherein the new record further comprises a time and date when the record was created.

14. The method of claim 12, wherein the new record further comprises information about the battery.

15. The method of claim 14, wherein the information about the battery comprises the battery’s voltage and/or the battery’s charge level.

16. The method of claim 11, wherein the external fluid flow conduit comprises at least a portion of a standpipe.

17. The method of claim 12, wherein controlling the charging of the battery comprises limiting the charging of the battery to a threshold fraction of the battery’s charge capacity.

18. The method of claim 17, wherein the threshold fraction is about 40% to about 80% of the battery’s charge capacity.

19. The method of claim 11, wherein the flow monitoring module comprises a housing having a transparent or semitransparent enclosure that allows solar radiation to reach the solar cell.

20. The method of claim 11, wherein the flow monitoring module comprises an attachment structure attached to the fluid flow conduit.

21. The method of claim 11, wherein: attempting to acquire the location data comprises using a GPS antenna, and attempting to wirelessly connect with the wireless network comprises using a wireless antenna.

22. The method of claim 11, wherein: acquiring and storing the fluid flow data further comprises detecting fluid flow through the fluid flow conduit, and the method further comprises, after the detecting, the attempting to acquire the location data.

23. The method of claim 11, further comprising: acquiring and storing the location data of the flow monitoring module; after acquiring and storing the location data, acquiring a wireless connection with the wireless network; and after acquiring the wireless connection, wirelessly transmitting the location data and the fluid flow data to an external computer.