WO2024165865A1

WO2024165865A1 - Flow meter

Info

Publication number: WO2024165865A1
Application number: PCT/GB2024/050350
Authority: WO
Inventors: Daniel Milne KRYWYJ
Original assignee: Aquam Water Services Ltd
Current assignee: Aquam Water Services Ltd
Priority date: 2023-02-10
Filing date: 2024-02-08
Publication date: 2024-08-15
Anticipated expiration: 2025-08-10
Also published as: AU2024218716A1; EP4662461A1

Abstract

Apparatuses and methods for detecting and/or characterizing fluid flow through a hydrant in a recess below ground level are provided. An apparatus includes a housing, one or more sensors, and a processor. The housing is configured to connect to the hydrant. The one or more sensors are in the housing and are configured to output sensed data in response to fluid flow through the hydrant. The processor is in the housing and is configured to determine one or more sensed data characteristics from the sensed data, the one or more sense data characteristics representing one or more properties of the sensed data, and to transmit, via a wireless communication interface, the one or more sensed data characteristics to a remote computational device for conversion, outside the processor, to one or more flow characteristics of the fluid flow through the hydrant.

Description

FLOW METER

REUATED APPEICATION(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 types of fluid extraction assemblies. For example, fresh-water distribution systems in municipalities have a network of water mains and other pipes that carry water to various customers and destinations, such as an array of fire hydrants, which may not only be used for extinguishing fires, but may also be utilized as water sources for flushing distribution system lines, testing the hydraulic capacity of a supply network, satisfying commercial and/or municipal construction needs, cleaning areas such as sewers, streets, storm drains, etc., irrigating land such as agricultural, residential, industrial, etc., land, and/or the like. It, however, is becoming increasingly difficult to monitor and control the disposition of water throughout a network, particularly in real time. This is especially true as the network grows and as water release elements, such as standpipes, hoses, etc., can be easily obtained and installed at various locations throughout the network without drawing scrunty.

[0003] The background provided herein is for the purposes of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent that it is described in this background, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the disclosure.

SUMMARY

[0004] Details of one or more implementations of the subject matter described in this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. The following, non-limiting implementations are considered part of the disclosure; other implementations will be evident from the entirety of this disclosure and the accompanying drawings as well.

[0005] According to some embodiments, an apparatus includes a housing, one or more sensors, and a processor. The housing is configured to connect to a hydrant in a recess below ground level. The one or more sensors are in the housing. The one or more sensors are configured to output sensed data in response to fluid flow through the hydrant. The processor is in the housing. The processor is configured to: determine one or more sensed data characteristics from the sensed data, the one or more sense data characteristics representing one or more properties of the sensed data; and transmit, via a wireless communication interface, the one or more sensed data characteristics to a remote computational device for conversion, outside the processor, to one or more flow characteristics of the fluid flow through the hydrant.

[0006] In some embodiments, the sensed data may include an indication of an initiation of the fluid flow through the hydrant.

[0007] In some embodiments, the sensed data may include an indication of an amount of the fluid flow through the hydrant and/or a rate of the fluid flow through the hydrant.

[0008] In some embodiments, the sensed data may include at least one vibration signal caused, at least in part, by the fluid flow through the hydrant.

[0009] In some embodiments, at least one of the one or more sensors is an accelerometer.

[0010] In some embodiments, the sensed data may include at least one acoustic signal caused, at least in part, by the fluid flow through the hydrant.

[0011] In some embodiments, the one or more sensed data characteristics may include a duration of the sensed data and/or a statistical characteristic of the sensed data.

[0012] In some embodiments, the one or more sensed data characteristics may include an average value of the sensed data, a maximum value of the sensed data, a minimum value of the sensed data, or any combination thereof.

[0013] In some embodiments, the one or more flow characteristics may include an amount of the fluid flow through the hydrant and/or a rate of the fluid flow through the hydrant. [0014] In some embodiments, the one or more flow characteristics may include an initiation time of the fluid flow through the hydrant.

[0015] In some embodiments, the wireless communication interface may be at least partially supported within the housing.

[0016] In some embodiments, the wireless communication interface may include communications logic configured to establish and/or maintain a connection with at least one wireless network.

[0017] In some embodiments, the at least one wireless network may be a cellular network.

[0018] In some embodiments, the apparatus may further include a bracket assembly configured to support the housing adjacent to a body of the hydrant and/or an outlet fitting of the hydrant.

[0019] In some embodiments, the apparatus may further include a bracket assembly configured to support an antenna of the wireless communication interface at a higher elevation within the recess than the housing.

[0020] In some embodiments, the processor may be further configured to discriminate between the sensed data caused, at least in part, by the fluid flow through the hydrant and noise caused, at least in part, by at least one source other than the fluid flow through the hydrant.

[0021] In some embodiments, the noise may be caused, at least in part, by one or more automobiles.

[0022] In some embodiments, the processor may be configured to exclude the noise prior to determination of the sensed data characteristics.

[0023] In some embodiments, wherein the hydrant may be compliant with British Standard (BS) 750.

[0024] According to some embodiments, an apparatus includes at least one processor, at least one communication interface, and at least one memory. The at least one memory includes one or more sequences of one or more instructions that, in response to being executed by the at least one processor, cause the apparatus at least to: receive vibration data from at least one sensor; determine whether the vibration data is indicative of fluid flow through a hydrant; generate, in response to the vibration data being indicative of fluid flow through the hydrant, flow information based on the vibration data; and transmit, via the communication interface over a wireless network, the flow information to a remote server configured to receive flow information from a plurality of apparatuses including the apparatus. The apparatus is co-located with the hydrant within an underground recess.

[0025] In some embodiments, the apparatus may include the at least one sensor, and the at least one sensor may be configured to generate the vibration data in response to fluid flow through the hydrant.

[0026] In some embodiments, the at least one sensor may be at least one accelerometer.

[0027] In some embodiments, the apparatus may further include a housing configured to support the at least one processor, the at least one memory, and the at least one sensor therein. The housing may be configured to support the least one communication interface at least partially therein.

[0028] In some embodiments, the apparatus may further include a first support structure configured to connect the housing adjacent to an output fitting of the hydrant.

[0029] In some embodiments, the apparatus may further include a second support structure configured to support an antenna of the communication interface at a higher elevation within the underground recess than the housing.

[0030] In some embodiments, the flow information may include a duration of the fluid flow through the hydrant.

[0031] In some embodiments, the flow information may include at least one of a maximum vibration level, a minimum vibration level, and an average vibration level.

[0032] In some embodiments, the flow information may include a unique identification of the hydrant.

[0033] In some embodiments, the unique identification of the hydrant may include a location of the hydrant and/or a serial number of the hydrant.

[0034] In some embodiments, at least a body of the hydrant may separate the at least one sensor from the fluid flow.

[0035] In some embodiments, the one or more sequences of the one or more instructions may be configured to, in response to being executed by the at least one processor, cause the apparatus at least to transmit the flow information to the remote server according to a first determined reporting interval.

[0036] In some embodiments, the one or more sequences of the one or more instructions may be configured to, in response to being executed by the at least one processor, cause the apparatus at least to adjust, after a determined amount of elapsed time, the first determined reporting interval to a second determined reporting interval different from the first determined reporting interval.

[0037] In some embodiments, the one or more sequences of the one or more instructions may be configured to, in response to being executed by the at least one processor, cause the apparatus at least to at least partially filter the vibration data to exclude vibratory noise unrelated to the fluid flow through the hydrant.

[0038] In some embodiments, the hydrant may be compliant with British Standard (BS) 750.

[0039] In some embodiments, the remote server may be configured to determine an amount of the fluid flow through the hydrant based on the flow information and/or a rate of the fluid flow through the hydrant based on the flow information.

[0040] According to some embodiments, a method of detecting and/or characterizing fluid flow through a hydrant in a recess below ground level includes: logging, during a flow event, vibration data caused, at least in part, by the fluid flow through the hydrant; determining that the flow event has stopped and/or a time limit for the flow event has expired; determining one or more vibration characteristics from the vibration data, the vibration characteristics representing one or more properties of the vibration data; and transmitting, via a wireless network, the one or more vibration characteristics to a remote computational device for conversion to one or more flow characteristics of the fluid flow through the hydrant.

[0041] In some embodiments, the method may further include, prior to logging the vibration data: detecting vibration from the hydrant; determining whether the vibration qualifies as fluid flow through the hydrant; and starting, in response to determining that the vibration qualifies as fluid flow through the hydrant, a timer for the flow event.

[0042] In some embodiments, determining that the flow event has stopped may include determining that the vibration no longer qualifies as fluid flow through the hydrant.

[0043] In some embodiments, the method may further include stopping, in response to determining that the vibration no longer qualifies as fluid flow through the hydrant, the timer. [0044] In some embodiments, the method may further include determining, via the remote computational device, the one or more flow characteristics utilizing the vibration characteristics.

[0045] In some embodiments, the vibration characteristics may include a duration of the vibration data logged during the flow event and/or a statistical characteristic of the vibration data logged during the flow event.

[0046] In some embodiments, the vibration characteristics may include an average value of the vibration data, a maximum value of the vibration data, a minimum value of the vibration data, or any combination thereof.

[0047] In some embodiments, the flow characteristics may include an amount of the fluid flow through the hydrant and/or a rate of the fluid flow through the hydrant.

[0048] In some embodiments, the flow characteristics may include an initiation time of the fluid flow through the hydrant.

[0049] In some embodiments, the method may further include transmitting, via the wireless network, information indicating when the flow event initiated.

[0050] In some embodiments, the information may be transmitted to an entity responsible for detecting and/or monitoring authorized and/or unauthorized fluid flow from the hydrant.

[0051] In some embodiments, the hydrant may be compliant with British Standard (BS) 750.

[0052] Additional aspects will be set forth in the detailed description which follows, and, in part, will be apparent from the disclosure, or may be learned by practice of the disclosed embodiments and/or the claimed subject matter. Accordingly, 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

[0053] Various embodiments disclosed herein are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings, in which like reference numerals refer to similar elements.

[0054] FIG. 1 depicts an underground fluid release assembly according to some embodiments. [0055] FIG. 2 depicts the underground fluid release assembly of FIG. 1 including a flow meter according to some embodiments.

[0056] FIG. 3 depicts a partially exploded perspective view of the flow meter of FIG. 2 according to some embodiments.

[0057] FIG. 4 depicts a perspective view of the flow meter of FIG. 3 according to some embodiments.

[0058] FIGS. 5 and 6 depict various orthographic views of a first support structure of the fluid release assembly of FIG. 2 according to some embodiments.

[0059] FIGS. 7 and 8 depict various orthographic views of a second support structure of the fluid release assembly of FIG. 2 according to some embodiments.

[0060] FIG. 9 depicts a block diagram of the flow meter of FIG. 2 according to some embodiments.

[0061] FIG. 10 depicts a method of operating the flow meter of FIG. 2 according to some embodiments.

[0062] FIG. 11 depicts a graph comparing acceleration and time according to some embodiments.

[0063] FIG. 12 depicts a graph comparing aggregate volume of fluid extraction and time according to some embodiments.

[0064] FIG. 13 depicts a map showing multiple fluid release assemblies according to some embodiments.

[0065] FIG. 14 depicts an aggregated record according to some embodiments.

DETAILED DESCRIPTION OF SOME EMBODIMENTS

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

Context

[0067] Many water utility districts have numerous underground water access points or taps where water may be drawn from an overall water distribution system. These water access points may include, for example, fire hydrants, waterspouts, spigots, standpipes, etc. A single water utility district may have thousands of 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, industrial, and other municipal uses. The uses may include fdling water tanks for commercial construction, fdling up a fire truck tank, filling up a ferry tank, irrigating an agricultural area, cleaning sewers, streets, storm drains, etc., providing drinkable water to remote locations, and/or the like.

[0068] The discharge locations generally do not have a means for easily tracking from which access point water was (or is being) 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 conventional meter values at access points, but this is a slow and inconvenient technique and frequently misses significant amounts of water release.

[0069] As a consequence, much water dispensed from access points in a water distribution network is wasted or is consumed without payment. Uncompensated water drawn from access points is typically referred to as 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 and flow meters 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. Water release assemblies according to various embodiments may also be used to quickly alert one or more interested parties of the initiation of a flow event and help stop undesired water releases, such as leaks or unauthorized access. In some embodiments, the water release assemblies automatically monitor and report any of various forms of data or information, such as sensed data, sensed data characteristics, flow characteristics, flow information, and/or the like, via wireless communication.

[0070] As stated above, water utilities may provision hydrants or other similar structures within underground enclosures that serve as water access points not only for extinguishing fires, but that may also be utilized for flushing distribution system lines, testing the hydraulic capacity of a supply network, satisfying commercial and/or municipal construction needs, cleaning areas such as sewers, streets, storm drains, etc., irrigating land, and/or the like. Although various types of hydrants exist, hydrants typically include a main body having an inlet flange capable of being connected to a water conduit of a water supply or system, and an outlet flange to which an outlet coupling (or fitting) may be mounted for quick access, such as via a standpipe, hose, etc. In some cases, the outlet coupling may be standardized, such as a British Standard (BS) 750 compliant London Round Thread outlet coupling, which may be used by firefighters for hose, standpipe, or other suitable attachment. Once installed, a hydrant typically remains in a fixed geographic location until uninstalled, unlike access attachments that 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 an access point, such as a hydrant. It is also noted that a service employee may remove a standpipe in one location and may install it in a different location. Although some attention has been directed towards tracking the installation and use of water extraction attachments, such as standpipes, in a water distribution system, this can be burdensome and typically requires use trackable equipment, which is typically supplied by a limited number of merchants or organizations. In light of this and the inconvenience of manually reading meters of water access points or water extraction attachments, water utilities often do not know from which discharge locations water was taken, how much water was taken, etc. As such, one or more embodiments seek to provide flow meters that may be configured to perform one or more of the following functions: receiving and storing sensed data, generating and storing at least one of sensed data characteristics and flow characteristics, acquiring and storing location data, and transmitting (e.g., wirelessly transmitting) data, such as one or more of the sensed data, the sensed data characteristics, and/or the flow characteristics to at least address the above-noted issues, but embodiments are not limited thereto.

Example Fluid Release Assemblies

[0071] FIGS. 1 and 2 depict an underground fluid release assembly with and without a flow meter according to some embodiments. FIGS. 5 and 6 depict various orthographic views of a first support structure of the water release assembly of FIG. 2 according to some embodiments. FIGS. 7 and 8 depict various orthographic views of a second support structure of the water release assembly of FIG. 2 according to some embodiments. [0072] Referring to FIGS. 1 and 2, fluid release assembly (e.g., a fire hydrant) 100 may include main body 101 through which flow path 103 may be formed. Flow path 103 may extend from fluid inlet 105 to fluid outlet 107. Main body 101 may include valve housing 109 and bonnet (or lid) 111. Valve housing 109 may have a generally cylindrical shape from which an elbow-shaped branch pipe 113 outwardly protrudes in a first direction (e.g., the x-axis direction) and bends into (or towards) a second direction (e.g., the z-axis direction). A valve assembly may be supported within an internal cavity of fluid release assembly 100 that may be defined by valve housing 109 and bonnet 111. In this manner, not only may a proximal end of valve housing 109 be sealed closed by bonnet 111 and an associated gasket, but a distal end of valve housing 109 may also include a connection, such as a flange connection. The connection may enable fluid release assembly 100 to be fluidically connected to supply conduit 115, such as a water main. In some cases, conduit riser 117 may be fluidically connected between the connection of valve housing 109 and supply conduit 115. In some cases, a distal end of branch pipe 113 may include coupling portion 119 configured to mate with various outlet fittings, such as outlet fitting 121. An associated gasket may be disposed between coupling portion 119 and a proximal end of outlet fitting 121 to form a fluidic seal therebetween. In some embodiments, a distal end portion of outlet fitting 121 may be BS 750 compliant. For instance, outlet fitting 121 may have a London Round thread portion 123. When fluid release assembly 100 is not in use, outlet fitting 121 may be protected by cover (or cap) 125 to prevent or reduce the incursion of foreign debris into fluid outlet 107.

[0073] Fluid release assembly 100 may be manually actuated through stem cap 127, which may be connected to stem (or spindle) 129 of the above-noted valve assembly. Stem 129 may be constrained within bonnet 111 by at least stem cap 127, but may be rotated about axis 131 to configure fluid release assembly in an open or closed position or configuration. For instance, rotation of stem cap 127 (and, thereby, stem 129) about axis 131 in a first direction (e.g., a counterclockwise direction) may open the valve assembly to allow fluid, such as water, to flow through fluid release assembly 100. Rotation of stem cap 127 about axis 131 in a second direction (e.g., a clockwise direction) opposite the first direction may close the valve assembly to prevent or otherwise stop the flow of fluid through fluid release assembly 100.

[0074] According to some embodiments, fluid release assembly 100 may be supported below ground level 133 within internal cavity 135 of underground enclosure 137, such as a boundary box, manhole, etc. Access to internal cavity 135, and thereby, to fluid release assembly 100 may be provided via selective removable of cover (or lid) 139, which may be detachably coupled to or mated with a proximal end (e.g., upper portion) of underground enclosure 137. A distal end of underground enclosure 137 may include opening 141 in terminal surface 143 through which fluid release assembly 100 may be connected to supply conduit 115. In some instances, underground enclosure 137 may be installed in ground 145 so that an exposed surface of cover 139 is flush (or substantially flush) with ground level 133, which may correspond to a street, pavement, floor, open terrain, and/or the like. For convenience, ground level 133 is shown in FIGS. 1 and 2 as corresponding to a street upon which automobile 147, such as a car, motorcycle, truck, or the like, may traverse. It is noted that an uppermost portion of outlet fitting 121 may be recessed below ground level 133 by distance 151, the magnitude of which may be governed by one or more laws, regulations, or standards, such as BS 750, which specifies the operational and health and safety requirements for underground fire hydrants installed in a water supply system.

[0075] In some implementations, flow meter 201 may be connected (e.g., detachably connected) to fluid release assembly 100 via first support structure 203, which may include one or more bracket portions, such as first and second bracket portions 203 1 and 203 2. First support structure 203 will be described in more detail in association with FIGS. 5 and 6. It is generally noted, however, that first support structure 203 may be configured to rest upon one or more surfaces (e.g., surface 205) of outlet fitting 121 such that flow meter 201 is positioned adjacent to at least one of branch pipe 113 and outlet fitting 121. In this manner, flowmeter 201 may be positioned (or co-located) with fluid release assembly 100 to detect fluid flow through fluid release assembly 100, generate or otherwise output sensed data corresponding to the fluid flow (e.g., vibration data, acoustic data, and/or the like), and generate, extract, or otherwise determine sensed data characteristics from the sensed data, such as a maximum valve of the sensed data, a minimum valve of the sensed data, a duration of the sensed data, and/or one or more statistical characteristics of or about the sensed data, such as average, kurtosis, root mean square, skewness, etc., valves about the sensed data. As such, the sensed data characteristics may represent one or more properties of the sensed data, and thereby, one or more properties of fluid flow through fluid release assembly 100. In some cases, flow meter 201 may also be configured to determine one or more flow characteristics (or information) from or utilizing the sensed data, such as an indication of an initiation of fluid flow through fluid release assembly 100, an amount of fluid flow through fluid release assembly 100, a rate of fluid flow through fluid release assembly 100, etc. Although described as different concepts, at least two among the sensed data, the sensed data characteristics, and the flow characteristics (or information) may correspond to similar aspects of or information about fluid flow through fluid release assembly 100. For example, the sensed data and the flow characteristics may each correspond to or include an indication of an initiation of fluid flow through fluid release assembly 100, an indication of an amount of fluid flow through fluid release assembly 100, and/or a rate of fluid flow through fluid release assembly 100. Whatever the case, flow meter 201 will be described in more detail in association with FIGS. 3-9.

[0076] In some embodiments, one or more fasteners, such as set screws 207, may be utilized to constrain translational and/or rotational displacement of first support structure 203 relative to fluid release assembly 100. It, of course, it contemplated that any other suitable fastening structure may be utilized, such as bolts, clamps, clips, nuts, pins, rivets, screws, etc. For instance, set screws 207 may interface with first bracket portion 203 1 and respective portions of outlet fitting 121 to prevent or at least reduce the likelihood of displacement of flow meter 201. It is noted that constraining the displacement of flow meter 201 relative to fluid release assembly 100 may, in some embodiments, increase the reliability of sensed data output by flow meter 201 in association with a flow event of fluid through fluid release assembly 100. For instance, constraining the displacement of flow meter 201 relative to fluid release assembly 100 may prevent or at least reduce the likelihood of noise being introduced into sensed data output by flow meter 201. Some noised, however, may be inevitable. Accordingly, and as will become more apparent below, flow meter 201 may, in some implementations, include filtering logic to discriminate between sensed data caused, at least in part, by fluid flowthrough fluid release assembly 100 and noise caused, at least in part, by at least one other source other than fluid flow through fluid release assembly 100, such as sensed data associated with automobile 147 traversing over fluid release assembly 100, sensed data associated with displacement of flow meter 201 relative to fluid release assembly 100, and/or other sources of signal noise, such as environmental events, maintenance, etc. In some cases, flow meter 201 may be configured to exclude or filter out noise introduced into the sensed data by one or more sources other than fluid flow through fluid release assembly 100. The exclusion or filtering out of the noise may be performed prior to flow meter 201 determining the one or more sensed data characteristics about the sensed data, but embodiments are not limited thereto.

[0077] According to some embodiments, flow meter 201 may be configured to transmit sensed data, sensed data characteristics, and/or flow characteristics to at least one remote computational device for additional and/or alternative processing, as will become more apparent below. For instance, flow meter 201 may include or may be associated with one or more communication interfaces configured to establish and/or maintain such transmission(s) over one or more wired and/or wireless networks. As shown, flow meter 201 is configured to wirelessly communicate with at least one remote computational device or other equipment via at least one antenna, such as antenna 209, which may be communicatively connected to flow meter 201 via transmission line (or wire) 211. In some cases, second support structure 213 may be utilized to support antenna 209 at a higher elevation within underground enclosure 137 than flow meter 201. Second support structure 213 may include one or more brackets (or other components), such as first, second, and third brackets 213 1, 213_2, and 213 3. Second support structure 213 will be described in more detail in association with FIGS. 7 and 8. It is noted, however, that second support structure 213 may, in some implementations, be supported from or otherwise connected to first support structure 203. In some instances, second support structure 213 may be supported within underground enclosure 137 via fluid release assembly 100, a wall (or surface) of underground enclosure 137, etc. Whatever the case, antenna 209 may be supported within underground enclosure 137 such that antenna 209 is recessed from ground level 133 by first distance 215. First distance 215 may be sized to enable wireless communication via antenna 209. Flow meter 201, however, may be recessed from ground level 133 by second distance 217, which may be different from first distance 215. In some cases, second distance 217 may not only be greater than first distance 215, but may also be greater than distance 151. Embodiments, however, are not limited thereto.

[0078] Adverting to FIGS. 5 and 6, first support structure 203 may include first and second bracket portions 203 1 and 203 2. First bracket portion 203 1 may have a generally annular platelike configuration when viewed along the Z-axis direction, but embodiments are not limited thereto. As such, first bracket portion 203 1 may, in some cases, be formed from stamped and bent sheetmetal, but embodiments are not limited thereto. For instance, first bracket portion 203 1 may be casted, machined, additively manufactured, or fabricated in any other suitable manner from any suitable material. Whatever the case, first bracket portion 203_l may have a main body with inner opening (or through-hole) 601 formed therethrough. For example, inner opening 601 may extend from first surface 501 through second surface 503 in the Z-axis direction. Inner opening 601 may have maximum dimension (e.g., diameter) 603 in, for instance, a plane parallel (or substantially parallel) to the X-Y plane and may be sized to allow outlet fitting 121 of fluid release assembly 100 to extend therethrough. In the case of fluid release assembly 100 including outlet fitting 121 being compliant with BS 750, inner opening 601 may be sized to ensure the London Round threads fit within inner opening 601 and/or any other expanded portions of outlet fitting 121. In some cases, when incorporated as part of or on fluid release assembly 100, second surface 503 of the main body of first bracket portion 203 1 may rest upon or otherwise abut against surface 205 of outlet fitting 121, such as illustrated in FIG. 2.

[0079] According to some embodiments, at least one portion of an outer periphery of the generally annular configuration of first bracket portion 203 1 may include corresponding flat sections, such as flat sections 605, 607, 609, and 611. Flat sections 607 and 611 may be respectively formed in association with the formation of protrusions 505 and 507, which may extend from first surface 501 of the main body of first bracket portion 203 _1 in the Z-axis direction. In some cases, protrusions 505 and 507 may be bent sections of the main body that are bent from, for example, the plane parallel (or substantially parallel) to the X-Y plane towards the Z-axis direction, but embodiments are not limited thereto. For instance, at least one of protrusions 505 and 507 may be connected to the main body such as via one or more fasteners, welds, adhesives, etc. At least one of protrusions 505 and 507, such as both of protrusions 505 and 507, may include one or more through-holes, such as through-holes 509 and 511, which may be configured to interface with, for example, set screws 207 or other fasteners. When incorporated as part of or on fluid release assembly 100, portions of set screws 207 may be received in through-holes 509 and 511 to enable distal ends of set screws 207 to abut against or engage with respective portions of outlet fitting 121 to prevent or at least reduce the likelihood of displacement of first support structure 203, and thereby, flow meter 201. For example, utilization of set screws 207 may constrain or at least limit translational and/or rotational displacement of first support structure 203 relative to fluid release assembly 100.

[0080] Second bracket portion 203 2 may be formed in association with flat section 609 in a manner similar to the formation of protrusions 505 and 507 in association with flat sections 607 and 611. It is noted, however, that second bracket portion 203 2 may extend in a direction opposite the Z-axis direction, and thereby, in a direction opposite protrusions 505 and 507. In some instances, second bracket portion 203 2 may be a bent section of the main body of first bracket portion 203 1 that is bent from, for example, the plane parallel (or substantially parallel) to the X-Y plane towards the direction opposite the Z-axis direction, but embodiments are not limited thereto. In some cases, second bracket portion 203 2 may be connected to the main body of first bracket portion 203 1 via, for instance, one or more fasteners, welds, adhesives, and/or the like. Second bracket portion 203_2 may have a generally rectangular plate-shape when viewed in the Y-axis direction, but embodiments are not limited thereto. Further, second bracket portion 203 2 may include one or more first openings (or through-holes) 513 and at least one second opening (or through-hole) 515 extending therethrough. First and second openings 513 and 515 may extend through second bracket portion 203 2 in the Y-axis direction, but embodiments are not limited thereto.

[0081] First openings 513 may correspond to connection regions configured to align with corresponding connection regions, e.g., connection regions 333, in flow meter 201 to allow flow meter 201 to be coupled (e.g., detachably coupled) to second bracket portion 203 2. For instance, first openings 513 may be sized to allow shaft portions of fasteners (e.g., clamps, bolts, pins, rivets, screws, ties, wingnuts, or the like) to pass therethrough and connect with (e.g., detachably connect with) the corresponding connection regions (e.g., connection regions 333) in flow meter 201, but may be sized smaller than the head portions of the fasteners. For example, connection regions 333 in flowmeter 201 may be threaded openings that threadedly engage with corresponding portions of the fasteners, which may be respectively passed through first openings 513 in first support structure 203. In this manner, flow meter 201 may be detachably coupled to second bracket portion 203 2. It is contemplated, however, that flow meter 201 may be permanently or semi -permanently connected to first support structure 203 or fluid release assembly 100 via, for instance, one or more welds, adhesives, fasteners, etc. In some cases, flow meter 201 may abut against surface 613 of second bracket portion 203 2 when connected to second bracket portion 203 2.

[0082] Similar to first openings 513, second opening 515 may correspond to a connection region configured to interface with a fastener (e.g., clamp, bolt, nut, pin, rivet, screw, tie, wingnut, and/or the like) configured to connect (e.g., detachably connect) second support structure 213 to first support structure 203. For instance, second opening 513 may be a threaded opening configured to engage with a wingnut configured to detachably connect second support structure 213 to first support structure 203, as will become more apparent below. It is contemplated, however, that second support structure 213 may be permanently or semi -permanently connected to at least one of first support structure 203 or fluid release assembly 100 via, for instance, one or more welds, adhesives, fasteners, etc.

[0083] Referring to FIGS. 7 and 8, second support structure 213 may include first, second, and third brackets (or components) 213 1, 213_2, and 213 3. First and second brackets 213 1 and 213_2 may be generally rectangular plates having elongated slots 701 and 703 respectively formed therein. Similar to first bracket portion 203_l, first and second brackets 213 1 and 213_2 may, in some cases, be formed from stamped sheet-metal, but embodiments are not limited thereto. For example, first and second brackets 213 1 and 213_2 may be casted, machined, additively manufactured, or fabricated in any other suitable manner from any suitable material. In some embodiments, first and second brackets 213 1 and 213 2 may be adjustably connected to one another via one or more fasteners, such as wingnut 705 and, in some instances, a corresponding locknut. For example, elongated slots 701 and 703 of first and second brackets 213_1 and 213_2 may be aligned within one another in any suitable fashion and fixed in position via, for instance, wingnut 705 and the corresponding locknut, such as shown in FIG. 7. Although two of these generally rectangular brackets are shown, any suitable number of these components may be utilized to achieve any suitable support structure configuration. This may allow second support structure 213 to be adaptively configured to the available space within underground enclosure 137 and to provide a determined elevation for antenna 209.

[0084] Third bracket 213 3 may have a generally L-shaped plate-like configuration having first portion 801 extending parallel (or substantially parallel) to a direction opposite the X-axis direction and second portion 803 extending parallel (or substantially parallel) to a direction opposite the Z- axis direction. According to some embodiments, third bracket 213 3 may be connected (e.g., detachably connected) to a distal end portion of second bracket 213 2. For instance, second portion 803 of third bracket 213 3 may include first through-hole 805 extending therethrough and configured to align with a portion of elongated slot 703 in second bracket 213 2 to allow third bracket 213 3 to be detachably coupled to second bracket portion 213 2. For instance, first through-hole 805 may be sized to allow a shaft portion of a fastener, such as wingnut 707, to not only pass therethrough, but also pass through the portion of elongated slot 703 aligned therewith. A corresponding lock nut may be threaded onto wingnut 707 to detachably couple second portion 803 of third bracket 213 3 with the distal end of second bracket 213 2. It is contemplated, however, that any other suitable fastener(s), weld(s), adhesive(s), and/or the like may be utilized to connect second and third brackets 213 2 and 213 3 to one another.

[0085] First portion 801 of third bracket 213 3 may provide resting surface 807 upon which antenna 209 may rest or otherwise be mounted. For example, first portion 801 of third bracket 213 3 may include second through-hole 809, which may be configured to align with a corresponding connection region formed in antenna 209 to allow antenna 209 to be fixed to third bracket 213 3. For instance, second through-hole 809 may be sized to allow a shaft portion of a fastener, such as fastener 811 to pass therethrough and connect with (e.g., detachably connect with) the corresponding connection region in antenna 209, but may be smaller than the head portion of fastener 811. Additionally or alternatively, antenna 209 may be coupled to resting surface 807 (or any other surface of second support structure 213) via, for example, one or more welds, adhesives, and/or fasteners. It is also noted that a distal end of first bracket 213 1 may be connected to first support structure 203 via one or more fasteners, such as wingnut 709. For example, a portion of elongated slot 701 may be aligned with second opening 515 in first support structure 203 to enable wingnut 709 to pass therethrough and engage with opening 515. It is contemplated, however, that second support structure 213 may be detachably, permanently, or semi-permanently connected to first support structure 203, fluid release assembly 100, and/or at least one other structure of or within underground enclosure 137.

Example Flow Meters

[0086] FIG. 3 depicts a partially exploded perspective view of the flow meter of FIG. 2 according to some embodiments. FIG. 4 depicts a perspective view of the flow meter of FIG. 3 according to some embodiments. FIG. 9 depicts a block diagram of the flow meter of FIG. 2 according to some embodiments.

[0087] Referring to FIGS. 3, 4, and 9, flow meter 201 may include housing 301, printed circuit board (PCB) 303, at least one processor (e.g., processor 305), one or more sensors 307, communication interface 309, and power source 311. It is contemplated, however, that flow meter 201 may take many forms and may include one or more additional and/or different components than as described herein. In some embodiments, processor 305, sensors 307, communication interface 309, and/or power source 311 may be mounted (e.g., surface mounted) on surface 313 of PCB 303, which may be supported within a cavity of housing 301. Interconnections between and amongst, for instance, processor 305, sensors 307, communication interface 309, and/or power source 311 may be formed in at least one signal layer of PCB 303. The interconnections of the at least one signal layer may also be connected to one or more cable connections, such as a cable connection enabling communication interface 309 to be electrically connected to, for example, antenna 209 via, for instance, transmission line 211. In this manner, data/information (such as sensed data) may be transmitted to processor 305 for the determination of sensed data characteristics and/or flow characteristics in association with fluid flow through fluid release assembly 100. PCB 303 may also include one or more connection regions (e.g., through slots) 315 configured to align with corresponding connection regions formed in surface 317 of bottom portion 319 of (or connected to) housing 301. As such, connection regions 315 may be sized to allow shaft portions of fasteners (e.g., clamps, bolts, pins, rivets, screws, ties, or the like) to pass therethrough and connect with (e.g., detachably connect with) the corresponding connection regions in surface 317 of bottom portion 319 of housing 301, but may be smaller than head portions of the fasteners so as to enable PCB 303 to be supported within housing 301.

[0088] According to some implementations, at least one of housing 301 and bottom portion 319 of flow meter 201 may be constructed of one or more durable materials (e.g., so that they may withstand impacts and/or thermal exposure, such as to temperatures 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 operation of other components of flow meter 201. Some examples of the durable material(s) may include metallic material(s), e.g., aluminum, copper, stainless steel, etc., non-metallic material(s), such as one or more polymers, plastics, thermoplastics, e.g., polyethylene (PE), polypropylene (PP), polystyrene (PS), polyvinyl chloride (PVC), etc., and/or the like. In this manner, bottom portion 319 may be formed as a unitary body with housing 301 or may be separately formed and connected to housing 301. For instance, housing 301 and bottom portion 319 may be connected with one another via, for instance, one or more fasteners, welds, and/or adhesives, such as an epoxy, silicone, cyanoacrylate, ultraviolet (UV) cure adhesive, etc. It is also contemplated that, in some cases, a pressure-sensitive adhesive may be additionally or alternatively utilized. In this manner, the internal cavity of housing 301 may be bounded by bottom portion 319 and one or more end caps, such as end caps 321 and 323. As such, housing 301, bottom portion 319, and/or end caps 321 and 323 may be shaped with rounded edges and a relatively slim profde, for example, to minimize or at least reduce the likelihood of damage that might be caused by flow meter 201 catching or being physically impacted during use or transport, such as being thrown in the back or bed of a truck.

[0089] Selective access to the cavity of housing 301 (and, thereby, the components supported therein) may be provided by at least one of end caps 321 and 323 being configured in a removable fashion. For instance, end caps 321 and 323 may respectively include one or more connection regions (e.g., through slots), such as connection regions 325, configured to align with corresponding connection regions formed in, for example, distal end surfaces of housing 301. In a similar fashion to connection regions 315, connection regions 325 may be sized to allow shaft portions of one or more fasteners (e.g., clamps, bolts, pins, rivets, screws, ties, or the like) to pass therethrough and connect with (e.g., detachably connect with) the corresponding connection regions in the distal end surfaces of housing 301, but may be smaller than the head portions of the fasteners. In some cases, one or more gaskets (e.g., first and second gaskets 327 and 329) may be at least partially compressed between corresponding surfaces of housing 301 and end caps 321 and 323 to prevent or at least reduce the likelihood of contaminate (e.g., debris, moisture, etc.) ingress into the cavity of housing 301. In some implementations, end cap 323 may include an opening through which transmission line 211 may traverse, and thereby, enable connection between flow meter 201 and, for instance, antenna 209.

[0090] As seen in FIG. 4, outward facing surface 331 of bottom portion 319 of flow meter 201 may, in some embodiments, include one or more connection regions (e.g., blind openings), such as connection regions 333, configured to align with corresponding connection regions formed in first support structure 203. In this manner, connection regions 333 may be, for instance, threaded openings sized to interface with threaded portions of fasteners enabling flow meter 201 to be connected with (e.g., detachably connected with) first support structure 203. In some cases, flow meter 201 may be additionally or alternatively connected to first support structure 203 via one or more adhesives, welds, and/or the like, or via one or more non-threaded openings. In some instances, flow meter 201 may be configured to be removably connected to first support structure 203 and/or fluid release assembly 100 without damaging first support structure 203 and/or fluid release assembly 100. Such a connection may be made possible via one or more straps, bands, pipe bands, etc., positioned around one or more portions of flow meter 201, first support structure 203, and/or fluid release assembly 100. It is also contemplated that one or more magnetic attachment mechanisms may be used.

[0091] Adverting to FIG. 9, processor 305 of flow meter 201 may include detector 901, counter (or timer) 903, at least one memory (e.g., memory 905), and filter 907. Memory 905 may be a program memory that stores one or more sequences of one or more instructions that may be executed by processor 305 to cause flow meter 201 to perform one or more of the features, functions, processes, etc., described herein. In some cases, memory 905 may buffer data for analysis and other processing. Detector 901 may be configured to detect a signal (or other output) generated by sensors 307, such as accelerometer 909. In some cases, sensors 307 may include one or more other sensors 911, such as one or more ultrasonic sensors, one or more vibration sensors, one or more velocimeters, one or more position sensors, one or more humidity sensors, one or more temperature sensors, one or more pressure sensors, and/or the like.

[0092] Accelerometer 909 (which may be a multi-axis, such as a three-axis accelerometer) and/or one or more of sensors 911 may supported in housing 301, such as illustrated in FIGS. 3 and 9, or may be external to flow meter 201. For example, accelerometer 909 may be configured as a wireless sensor module having or being connected to a communication interface (such as a wireless communication interface) for conveyance of sensed data to processor 305 via any suitable transmission protocol. In the case of a wireless protocol, the communication interface may operate in accordance with Zigbee™, Bluetooth™, Wi-Fi, ultra-wideband, infrared, and/or any other suitable wireless protocol (such as a short-range wireless protocol) or near-field wireless communication protocol, but embodiments are not limited thereto. It is noted, however, that in instances when, for example, accelerometer 909 is configured as a wireless sensor module, accelerometer 909 may be mounted on or supported adjacent to at least one of branch pipe 113 and outlet fitting 121 of fluid release assembly 100 and housing 301 may be supported elsewhere within underground enclosure 137 or any other suitable location within range of the wireless sensor module. For convenience, it will be assumed and described that accelerometer 909 and any other sensors 911 of flow meter 201 are supported within housing 301.

[0093] According to various embodiments, counter/timer 903 (hereinafter, referred to as counter 903) may be configured to count or otherwise keep track of one or more time periods, which may be utilized, for example, to determine whether fluid flow through fluid release assembly 100 has been initiated or terminated, to regulate transmission of sensed data, sensed data characteristics, and/or flow characteristics via communication interface 309, and/or to execute one or more of the other features or functions described herein. In some cases, counter 903 may include a real-time clock or a timer to facilitate tracking of the time period(s). Memory 905 and/or any other suitable memory or storage device may be configured to store sensed data output form or otherwise generated by accelerometer 909, any other sensors 911, and/or other aspects of flow meter 201, such as data associated with counter 903. [0094] Power source 311 may be, for instance, a battery and/or a capacitor, and may be configured to provide power to the various components of flow meter 201, such as processor 305, communication interface 309, accelerometer 909, sensor(s) 911, etc. In some cases, power source 311 may be or include a rectifier configured to receive an alternating current (AC) from, for instance, a conventional power grid and convert the AC into direct current (DC) to power the various components of flow meter 201 and/or to store energy via, for example, a battery and/or a capacitor. Energy from a conventional power grid source may be particularly useful when fluid flows through fluid release assembly 100 for a relatively long period of time or to recharge an energy store of or associated with flow meter 201. However, as will become more apparent below, flow meter 201 may have or otherwise provide various features and/or functions to enable flow meter 201 to operate for extended periods of time, such as days, weeks, months, or even years without having to replace or replenish power source 311. It is also contemplated that power source 311 may be, include, or operate in association with any other energy storage device, such as sup er capacitors, fuel cells, and/or the like.

[0095] In some embodiments, power source 311 may be connected to an information retrieval (IR) PCB containing one or more light sources (e.g., light emitting diodes (LEDs)) and an IR programming device. The IR PCB and IR device may be configured for diagnostics and/or fault detection. For instance, the IR device may be configured to collect and/or analyze textual descriptions contained in bug reports generated by, for instance, processor 305 and identifier names and comments in source code files stored to, for example, memory 905 to identify and localize (or otherwise associate) fault conditions with certain processes and/or components of flow meter 201. In some cases, the IR device 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 flow meter 201 being executed or utilized around the time of the fault condition. As such, the IR device 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 a remote device (e.g., remote device 913) via, for example, communication interface 309. The information provided by the IR device may be utilized to remotely diagnose and resolve issues without having to uninstall, dismantle, test, fix, assemble, and reinstall flow meter 201. To this end, over-the-air firmware updates may be provided to flow meter 201 via communication interface 309 to address various remotely diagnosed issues, which may help reduce the likelihood of contaminate (e.g., dirt, water, etc.) ingress into flow meter 201 as it does not need to be dismantled and reassembled to fix issues. In some embodiments, the IR device may also be configured to provide, for instance, at least one of sensed data, sensed data characteristics, and flow characteristics via its information providing interface.

[0096] Processor 305 may execute machine-readable system control instructions, which may be cached locally on memory 905 and/or may be loaded into memory 905 from a different memory device, such as an external memory, and may include instructions for controlling any aspect of flow meter 201. The instructions may be configured in any suitable way and may by implemented in software, firmware, hard-coded as logic in an application specific integrated circuit (ASIC), or, in any other suitable implementation. In some cases, the instructions may be executed in a general- purpose microprocessor, a microcontroller, or other computational device. In some embodiments, the instructions may be implemented as a combination of software and hardware. It is also contemplated that flow meter 201 may additionally include one or more analog and/or digital input/output connection(s) 915 and/or one or more analog-to-digital and/or digital-to-analog converters. For instance, flow meter 201 may include one or more analog and/or digital input/output connection(s) 915 to enable communication with user interface 917 for local download and/or upload of data/information from/to flow meter 201.

[0097] Communication interface 309 may include one or more modules having associated communications logic to establish and/or maintain communication with a corresponding network, such as radio/wireless module 919 and positioning module 921. In some cases, radio/wireless module 919 and positioning module 921 may be associated with respective antennas, such as first and second antennas 923 and 925. It is generally noted that antenna 209 may represent the respective antennas associated with communications interface 309. In any event, communication interface 309 may be configured to acquire location data about the location of fluid release assembly 100 and/or flow meter 201 using positioning module 921 and second antenna 925, which may be 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 of, for example, flow meter 201 that includes and/or is connected to positioning module 921 and antenna 925. For example, positioning module 921 and antenna 925 may be components of a global positioning satellite (“GPS”) interface that can establish a connection(s) with multiple GPS satellites, such as GPS satellites 927. Using data from communications with such satellites, communication interface 309 may determine alone or in association with processor 305 the location of flow meter 201, and, thereby, fluid release assembly 100. In some cases, the location of flow meter 201/fluid release assembly 100 may be determined as part of the installation of flow meter 201 in association with fluid release assembly 100, and may be transmitted to a remote device, such as remote device 913, for association in a repository configured to store various forms of data/information in association with a plurality of fluid release assemblies of a fluid distribution system. As such, a unique identifier may be assigned to flow meter 201 and/or fluid release assembly 100, which may be utilized in lieu of (or in addition to) the transmission of location information with sensed data, sensed data characteristics, and/or flow characteristics. This may enable flow meter 201 to reduce its power consumption as the use of positioning module 921 and antenna 925 may be minimized or otherwise limited.

[0098] The term “GPS” as used herein may mean the broader concept of a location/positioning system employing one or more satellites that transmit ephemeris (e.g., a table or data file that provides the calculated position(s) 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 — communication interface 309 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, such as satellites 927, may be satellites in a GPS system, or 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, the Chinese Compass navigation system, etc.

[0099] Some GPS systems may use a relatively lethargic data transfer speed of, for instance, 50 bits per second, which may mean that a GPS receiver, in some cases, may remain operational 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 may involve the GPS receiver being powered for the entire initial lock-on. This can be taxing on devices with small battery or capacitor capacities. As such, it is even more apparent that the use of a unique identifier for flow meter 201 and/or fluid release assembly 100 in lieu of the determination and transmission of location information with sensed data, sensed data characteristics, and/or flow characteristics may enable reduced power consumption of power source 311.

[0100] Communication interface 309 may also be configured to wirelessly connect with, and transmit and receive data from, for example, remote device 913 (e.g., a computer, server, router, handset, user equipment, etc.), which may be part of or communicatively coupled to one or more networks, such as network 929, using radio/wireless module 919 and antenna 923, which may be configured to connect with remote device 913. Radio/wireless module 919 and antenna 923 may be configured to communicate by any suitable wireless protocol. For example, radio/wireless module 919 and antenna 923 may be configured to communicate using any suitable radio or cellular protocol, such as Advanced Mobile Phone System (AMPS), Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), and/or the like. Alternatively, or additionally, radio/wireless module 919 and antenna 923 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 any other sufficiently long-range protocol. As an example, radio/wireless module 919 may be the SIM808 from SIMCom Wireless Solutions Co., Ltd., Shanghai, China. The product may be packaged on a printed circuit assembly (“PC A”) with support integrated circuits from Adafruit, Industries of New York, New York. In some embodiments, radio/wireless module 919 may be a NimbeLink Skywire LTE-M/NB-IoT modem having part number NL-SW-LTE-QBG96-B, but embodiments are not limited thereto. It is contemplated, however, that the non-cellular wireless protocol may be any suitable wireless wide area network (WWAN) protocol, wireless local area network (WLAN) protocol, wireless metropolitan area network (WMAN) protocol, and/or wireless personal area network (WPAN) protocol. In some cases, any form of wired communication may be utilized.

[0101] Processor 305 may be configured to cause power to be delivered to communication interface 309 and to stop the power to communication interface 309. Although radio/wireless and positioning modules 919 and 921 are depicted as part of a single communication interface 309, they may be, in some embodiments, separate units that are individually connected to power source 311 such that they may be individually powered. For instance, a first communication interface may include positioning module 921 and antenna 925, such as a GPS unit with a GPS antenna, and may be powered on while a second communication interface, which may include radio/wireless module 919 and antenna 923, such as a wireless communication interface having a wireless antenna, is powered off, or vice versa. This too may help reduce the power consumption of power source 311 in association with the operation of flow meter 201 as unused components may be prevented from receiving power.

[0102] According to some embodiments, memory 905 and/or any other suitable memory or storage device of or associated with flowmeter 201 may be configured to store data received from processor 305, sensor(s) 307, radio/wireless module 919, and/or positioning module 921, such as count, time, sensed data, sensed data characteristics, flow characteristics, location data, and/or the like. Firmware updates, which may be received via antenna 923 and radio/wireless module 919, may be stored at an appropriate location (e.g., an external memory) accessible to processor 305. Processor 305 may also be configured to access and transmit data stored in memory 905 and/or a different memory /storage device over network 929 via, for instance, radio/wireless module 919 and antenna 923. In some embodiments, the various components of processor 305 may be communicatively connected with one another (such as via a system level bus and/or an internal datapath bus) and processor 305 may be configured to control each of such components, as well as any other component of flow meter 201.

[0103] As previously mentioned, flow meter 201 may include one or more sensors 307, which may provide various information directly or indirectly related to fluid flowthrough or location about fluid release assembly 100. In some cases, the information provided by sensors 307 may be considered or categorized as sensed data. Examples of sensors include one or more accelerometers (e.g., accelerometer 909), one or more ultrasonic sensors, one or more vibration sensors, one or more velocimeters, one or more position sensors, one or more humidity sensors, one or more temperature sensors, one or more pressure sensors, and/or the like. Sensors 307 may be disposed internally within housing 301 or externally. In general, accelerometer 909 may be configured to provide information about vibrations, orientation, and/or transport of flow meter 201 caused, at least in part, by fluid flow through fluid release assembly 100. A further discussion of information from accelerometer 909 will be provided elsewhere. Similar information, however, may be provided via a vibration sensor, which may include an accelerometer or any other type of sensor capable of detecting vibration. A velocimeter may be utilized to measure velocity of, for instance, flow meter 201. A position sensor may be used to detect the absolute position (or location) of, for example, flow meter 201 or its relative position (e.g., displacement) in terms of linear travel, rotational angle, and/or three-dimensional space. In some cases, positional information may be utilized to determine vibration information associated with fluid flow through fluid release assembly 100. One type of positional sensor may be a laser Doppler vibrometer, which may be configured to obtain noncontact vibration measurements (e.g., amplitude, frequency, duration, etc.) of a surface of fluid release assembly 100 utilizing one or more laser beams and determining such measurements based on the Doppler shift of the frequency of one or more reflected laser beams that may result from the motion of a surface of fluid release assembly 100 caused, at least in part, by fluid flow through fluid release assembly 100. Any other form of positional sensor, however, may be utilized. A humidity sensor may be used to detect tampering with flow meter 201, such as the opening of housing 301. In some cases, a humidity sensor may provide information relevant to a failure (or fault condition) of flow meter 201 and/or fluid release assembly 100, such as water ingress to flow meter 201, unexpected water egress from fluid release assembly 100, etc. A temperature sensor may be used to acquire temperature data at various points in time, such as each time a component of flow meter 201 is operated or when fluid flow through fluid release assembly 100 is detected or confirmed. A pressure sensor may, in some implementations, be used to determine pressure (e.g., differential pressure) applied to one or more surfaces of fluid release assembly 100 caused, at least in part, by fluid flow through fluid release assembly 100. Whatever the case, sensed data received from at least one of sensors 307, such as accelerometer 909, may be utilized by processor 305 to generate sensed data characteristics and/or flow characteristics.

[0104] According to some embodiments, processor 305 may be configured to connect sensors 307, such as accelerometer 909, to power source 311, as well as configured to receive sensed data and/or signals, such as voltages, from sensors 307. For instance, accelerometer 909 may be continuously, periodically, or even randomly powered by power source 311 so that accelerometer 909 can detect flow events associated with movement or vibration of fluid release assembly 100 to which flow meter 201 may be connected. This may include vibration of one or more surfaces of at least one of branch pipe 113 and outlet fitting 121 through which fluid may flow during a flow event. As described below, sensed data from, for instance, accelerometer 909 may assist with “waking up” at least one component or module of processor 305 during a flow event.

[0105] According to various embodiments, flow meter 201 may be configured to perform one or more of the following functions: receiving and storing sensed data, generating and storing at least one of sensed data characteristics and flow characteristics, acquiring and storing location data, and wirelessly transmitting data, such as one or more of the sensed data, the sensed data characteristics, and/or the flow characteristics. As previously discussed, sensed data may correspond to one or more parameters generated in response to fluid flow through fluid release assembly 100, such as vibration data, acoustic data, and/or the like, that relates to, for instance, one or more surfaces of fluid release assembly 100 that are affected as fluid flows through fluid release assembly 100. Sensed data characteristics generated from the sensed data may include one or more characteristics representing one or more properties of the sensed data, such as a maximum valve of the sensed data, a minimum valve of the sensed data, a duration of the sensed data, and/or one or more statistical characteristics of or about the sensed data, such as average, kurtosis, root mean square, skewness, etc., valves about the sensed data. The flow characteristics (or information) which may be determined from or utilizing the sensed data and/or sensed data characteristics may include an indication of an initiation of fluid flow through fluid release assembly 100, an amount of fluid flow through fluid release assembly 100, a rate of fluid flowthrough fluid release assembly 100, etc. The location data, as described below, may include information directly or indirectly specifying the geographic location, e.g., altitude, latitude, and longitude, or address of fluid release assembly 100.

Example Processing Sequences

[0106] FIG. 10 depicts a method of operating the flow meter of FIG. 2 according to some embodiments. FIG. 11 depicts a graph comparing acceleration and time according to some embodiments. FIG. 12 depicts a graph comparing aggregate volume of fluid extraction and time according to some embodiments. FIG. 13 depicts a map showing multiple fluid release assemblies according to some embodiments. FIG. 14 depicts an aggregated record according to some embodiments.

[0107] As previously discussed, flow meter 201 may be configured to receive and store signals related to fluid flowthrough fluid release assembly 100 that are generated by one or more sensors, such as accelerometer 909, (and optionally convert those signals/sensed data into values representing sensed data characteristics and/or flow characteristics; to receive and store location data), and to transmit at least one of the sensed data, sensed data characteristics, flow characteristics, and location data to at least one remote device, such as remote device 913. This configuration may include instructions stored on at least one memory, such as memory 905, that are executable by at least one processor, such as processor 305. One or more example processing sequences of flow meter 201 will now described in association with FIGS. 10-14. It is noted that the various blocks shown in FIG. 10 may be implemented by at least one of the components of flow meter 201, such as accelerometer 909, processor 305, communication interface 309, etc., executing instructions stored on, for example, memory 905.

[0108] Example process (or technique) 1000 may begin at block 1001 in which a pulse or other form of sensed data output from flow meter 201 is detected. This pulse may be a signal from or generated by one or more of sensors 307 that may be an electrical voltage output from, for example, accelerometer 909 relating to vibration of flow meter 201 and potentially to fluid flow through fluid release assembly 100. Before receiving a pulse or other sensed data at block 1001, processor 305 may be in a sleep state in which power may be on to processor 305, but in a low power mode, with few, if any, operations being performed. It is noted, however, that communication interface 309 may not be powered on. At block 1003, processor 305 may exit the low power state and “wake up” in response to detecting (or otherwise receiving) the signal from, for instance, accelerometer 909. The detection and/or reception of the signal may be performed by detector 901. The “waking up” of processor 305 may activate counter/timer 903 of processor 305, but counter/timer 903 may not actually starting counting/timing upon being “woken up” by, for example, detector 901.

[0109] According to various embodiments, the pulse or signal may be interpreted or otherwise analyzed in association with one or more other pulses or signals to discriminate between sensed data caused, at least in part, by fluid flow through fluid release assembly 100 and noise caused, at least in part, by at least one source other than fluid flow through fluid release assembly 100. In some instances, the noise may be caused by automobile 147 traversing over underground enclosure 137, and thereby, over fluid release assembly 100 that may cause, at least in part, flow meter 201 and/or fluid release assembly 100 to vibrate. Of course any other stimuli may be the cause of the noise, such as an environmental event (e.g., an earthquake, storm, etc.), maintenance being performed on fluid release assembly 100, an accessory (e.g., standpipe, hose, etc.) being coupled to fluid release assembly 100, etc. For example, automobile 147 may cause a significant amount of vibration to be detected via accelerometer 909, such as vibration corresponding to acceleration spike 1101 shown in graph 1100 of FIG. 11. In other cases, below threshold amounts of vibration may be detected via accelerometer 909, such as detected in acceleration period 1103 shown in FIG. 11. These below threshold amounts of vibration may originate from, for instance, normal planetary vibration, such as from the aggregate effects of the “hustle and bustle” of everyday life. Utilizing, for instance, filtering logic and/or one or more machine learning algorithms, processor 305 and/or filter 907 may determine in block 1005 that the sensed vibration corresponding to acceleration spike 1101 or the below threshold amount of vibration in acceleration period 1103 does not qualify as fluid flow through fluid release assembly 100. Processor 305 and/or filter 907 may, in some cases, perform a frequency analysis on the sensed data to determine whether, for example, vibration data corresponds to a flow event or is from another source. This may include conversion or transformation of the sensed data between time, frequency, and/or joint domains, but other suitable techniques may be utilized to, for example, analyze and/or filter the sensed data, which as previously mentioned, may correspond to vibration data. For instance, processor 305 and/or filter 907 may utilize a modal analysis in which one or more measured frequency response functions of flow meter 201 may be input to a computer model (or other conceptual model) to determine whether the sensed data (or any portion thereof) corresponds to fluid flow, noise, and/or the like. It is also contemplated that any other suitable technique may be utilized, such as time waveform analysis, fast Fourier transform analysis, phase measurement, order variation analysis, power spectral density, envelope analysis, resonance analysis, monitoring overall levels of sensed data, shock pulses, discrete frequencies, averaging, cepstrum analysis, and/or the like. In those instances when sensed data does not correspond to fluid flow, processor 305, and, thereby, counter/timer 903 of processor 305 may return to the sleep state or low power mode, per block 1007.

[0110] Alternatively, the vibration sensed via accelerometer 909 in association with block 1001 may be caused, at least in part, by fluid flow through fluid release assembly 100. For instance, the vibration sensed via accelerometer 909 may be above one or more determined threshold levels and continue for a determined amount of time and/or be otherwise characteristic of fluid flow through fluid release assembly 100, such as depicted in acceleration period 1105 of FIG. 11. In such cases, processor 305 and/or filter 907 may determine in block 1005 that the sensed vibration corresponding to acceleration period 1105 qualifies as a flow event (e.g., fluid flow through fluid release assembly 100) and may cause processor 305 to simultaneously (or sequentially) cause various functions to be performed, as described below. As seen in FIG. 10, processor 305, often in with one or more other components of flow meter 201, may execute one or more different operations, sometimes concurrently. Some of these operations are depicted as separate branches from block 1005.

[0111] For example, after waking up, processor 305 may, at block 1009, start or initiate a timer for the flow event via counter/timer 903. In some cases, processor 305 may also, whether concurrently or sequentially, create a flow initiation record for the flow event in block 1011, and attempt to establish a network connection with, for example, network 929 via radio/wireless module 919 and antenna 923 of communication interface 309. Processor 305 may, in some implementations, also attempt to acquire location data or cause another component to make the attempt via, for instance, positioning module 921 and antenna 925 of communication interface 309. Accordingly, the content of the flow initiation record may be stored in, for instance, memory 905 and/or any other suitable memory or storage device of or associated with flow meter 201. The flow initiation record may at least include, for instance, an initiation time of fluid flow through fluid release assembly 100 and an identification of fluid release assembly 100, whether in the form of location information of fluid release assembly 100 or at least one unique identifier of fluid release assembly 100 or flow meter 201. It is contemplated, however, that any other suitable information may be provided, such as one or more of the pieces of information described in association with FIG. 14.

[0112] According to various embodiments, processor 305 may power on one or more modules of communication interface 309 to establish the network connection and/or acquire the location data. With respect to acquiring the location data, positioning module 921 and antenna 925 may begin attempting to receive a signal from one or more GPS satellites, such as GPS satellites 927. Alternatively, in some other embodiments, communication interface 309 may attempt to acquire a signal via a different location providing method, such as by triangulation or other approach using a cellular transmission tower via radio/wireless module 919 and antenna 923. Per block 1013, processor 305 may enter various pieces of information into the flow initiation record, such as time, date, battery voltage of power source 311, and/or other like information. In some cases, processor 305 may enter, in block 1015, position information, such as GPS data, if such information is to be acquired in association with block 1011. It is noted that the GPS protocol may have 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 as part of blocks 1011 and/or 1015. As previously mentioned, a unique identifier may be assigned to flow meter 201 and/or fluid release assembly 100, which may be utilized in lieu of (or in addition to) to the position information. In other words, given the relatively static position of fluid release assembly 100 (and, thereby, flow meter 201), the unique identifier may be utilized and stored in the flow initiation record to reduce power consumption of power source 311. As such, the unique identifier may be utilized by, for example, remote device 913 to associate flow meter 201 and fluid release assembly 100 with a particular geographic location and/or address, such as a street or postal address. [0113] Sometime after at least one of blocks 1011-1015, oval 1017 may be performed by at least one of processor 305 and communication interface 309. Oval 1017 is a decision or assessment by processor 305 and/or communication interface 309 as to whether a network connection with network 929 has been successfully established via, for instance, radio/wireless module 919 and antenna 923. If a network connection with network 929 is established, then processor 305 may enter various pieces of network information, such as carrier information, radio/wireless module 919 identifier, and/or the like information, into the flow initiation record, per block 1019. As will be described in more detail below, such information may come from communication interface 309 and/or at least logic of communication interface 309 associated with wireless communications.

[0114] According to some embodiments, the detected fluid flow through fluid release assembly 100 may be an unauthorized or undesired fluid extraction event, and as such, may be in the interest of one or more parties to curtail or otherwise stop the fluid extraction event as soon as feasibly possible. As such, processor 305 may be configured, in association with radio/wireless module 919 and antenna 923, to transmit the flow initiation record associated with the flow event (and any nontransmitted flow initiation records associated with other flow events that may be stored to a memory of flow meter 201, such as memory 905) to at least one entity responsible for detecting and/or monitoring authorized and/or unauthorized fluid flow from fluid release assembly 100, per block 1021. For example, the flow initiation record(s) may be transmitted to at least one of a private, a commercial, and a governmental agency or organization, such as one or more of a law enforcement agency, municipal water provider, etc. This may allow such entities to be dispatched to fluid release assembly 100 relatively quickly, and thereby, to stop any unauthorized/undesired fluid extraction before the flow event becomes burdensome and/or costly. It may be the case that the flow event is authorized, and as such, the responsible entities may simply allow the flow event to continue and to be billed accordingly.

[0115] Adverting back to oval 1017, if a network connection was not successfully established, then processor 305 and/or communication interface 309 may re-attempt to establish the network connection one or more times or until a network connection is established. It is noted, however, that continuously repeating to establish a network connection without success may drain power source 311 or otherwise interfere with the operation flow meter 201. As such, processor 305 and/or communication interface 309 may stop making attempts to establish a network connection 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) an initial attempt is made, a first timer may be started using counter/timer 903. 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 attempts to acquire the network connection may be stopped by, for instance, powering off communication interface 309. 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 counter/timer 903. If the timer has not expired, then attempts to establish a network connection may be repeated, but once the timer has reached the first threshold time and expired, then processor 305 may store the flow initiation record to, for example, memory 905 or any other memory or storage device of or associated with flow meter 201 for later transmission, per block 1023. In some cases, the flow initiation record may be stored in association with a sequence number, which may define a temporal order of the flow event within a number of flow events that have been initiated without successful establishment of a network connection to transmit the flow initiation record(s) to, for example, remote device 913. In some embodiments, progressing from block 1023 (and, in some cases, from block 1021) may lead to block 1025, in which case processor 305 may power off communication interface 309 and/or one or more timers of counter/timer 903. In some implementations, radio/wireless module 919 and positioning module 921 may be powered off at the same time or at different times. From block 1025, flow meter 201 may wait for a new/next vibration at block 1027.

[0116] Returning to the point after or while processor 305 starts or initiates a timer for the flow event via counter/timer 903, per block 1009, processor 305 via one or more sensors 307 and detector 909 may log sensed data (e.g., vibration data from accelerometer 909) for the flow event to, for instance, memory 905, per block 1029. Depending on the type of sensor employed to capture sensed data associated with fluid flowthrough fluid release assembly 100, processor 305 may log pulses or other indicia of the fluid flow. In some embodiments, processor 305 may store or log such sensed data to memory 905 and/or to at least one other memory or storage device of or associated with flow meter 201. In the case of accelerometer 909, the sensed data may be provided as a series of voltage pulses or other indicia of fluid flow through fluid release assembly 100. The voltage pulses may correspond to measures of the vibration or proper acceleration of one or more surfaces of fluid release assembly 100 caused, at least in part, by the fluid flow therethrough. In some cases, the voltage pulses may correspond to measures of the vibration or proper acceleration of flow meter 201 caused, at least in part, by the fluid flow through fluid release assembly 100. Other examples of the types of information that may be provided to indicate or capture fluid flow through fluid release assembly 100 include optical signals, acoustic signals, electrical signals (e.g., capacitive and/or inductive), and/or the like. In addition, processor 305 via at least one of sensors 911 may detect other quantities related to the fluid or fluid release assembly 100, such as temperature, pressure, humidity, etc. For compressible fluids, such as gases, pressure, temperature, and volume may be detected/monitored to determine the mass of the fluid that is flowing or has flowed.

[0117] The sensed data relating to the fluid flow may be organized into discrete flows through fluid release assembly 100, with each use being considered a flow event. For example, the fluid may flow for twenty minutes and then 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 flow events. In some embodiments, a flow event may begin with receipt of a first pulse, which wakes up processor 305 and qualifies as a valid fluid flow vibration, and ends with a timer timing out after a defined period from detection of a last pulse. In one implementation, simultaneously with or soon after (e.g., within 5 seconds) an indicator of fluid flow may be received by processor 305, such as a pulse from accelerometer 909, and a second timer may be started using counter/timer 903. Each time processor 305 receives such an indicator, the timer may be reset, but embodiments are not limited thereto. If the second timer reaches a second threshold time, such as at about 5 minutes, or about 10 minutes, such as 15 minutes, and therefore, expires without receiving during that period an indicator of flow, processor 305 may conclude that the flow event has ended. This second timer may perform like the first timer described above, e.g., counting up from zero. Once the flow event has ended, the information entered into the record, the record itself, and/or one or more sensed data characteristics representing one or more properties of the sensed data may be determined and stored in a memory, such as memory 905, as indicated by blocks 1031 and 1033. In some cases, the sensed data characteristics may include a maximum valve of the sensed data (e.g., a maximum vibration VM), a minimum valve of the sensed data (e.g., a minimum vibration VMIN), a duration of the sensed data (e.g., a duration of vibration Vs), and/or one or more statistical characteristics of or about the sensed data, such as average (e.g., average vibration VA), kurtosis, root mean square, skewness, etc., valves about the sensed data. Some other forms of information are described in association with FIG. 14.

[0118] In some embodiments, at least one of processor 305 and filter 907 may be configured to exclude noise from the sensed data prior to determining the sensed data characteristics. The sensed data characteristics may be stored to a sensed data characteristics record at block 1035. In some cases, one or more flow characteristics (or information) may be determined by processor 305 from or utilizing the sensed data/sensed data characteristics, such as an indication of an initiation of fluid flowthrough fluid release assembly 100, an amount of fluid flow through fluid release assembly 100, a rate of fluid flow through fluid release assembly 100, etc. This information may be additionally or alternatively stored to the sensed data characteristics record created in association with block 1035. It is noted, however, that the determination of one or more flow characteristics (or information) may be reserved for at least one remote computational device, such as remote device 913, to conserve power stored to, for example, power source 311.

[0119] At block 1037, at least one of processor 305 and communication interface 309 may attempt to establish a network connection. This may include causing, at least in part, radio/wireless module 919 via antenna 923 to attempt to wirelessly connect with a wireless network (e.g., network 929) as previously described. Similar to oval 1017, oval 1039 may indicate a determination whether the network connection was successfully established. If the network connection was not successful, then at least one of processor 305 and communication interface 309 may repeat operations associated with block 1037 until the connection is successful. However, as previously described, continuously repeating this attempt without success may drain power source 311, and therefore, in some embodiments, flow meter 201 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 previously described in association with oval 1017. In some embodiments, for instance, if the third timer reaches a third threshold time without making a connection, then the attempt is stopped. In embodiments in which communication interface 309 includes separately powered radio/wireless and positioning modules 919 and 921, this stopping may be effectuated by powering off at least radio/wireless module 919, per block 1025, but embodiments are not limited thereto. For instance, the powering off may include powering off both radio/wireless and positioning modules 919 and 921, and in some cases, one or more counters/timers of counter/timer 903 of processor 305. Additionally, even if the network connection was not established, then the sensed data characteristics record may still be stored to a memory or storage device of or associated with flow meter 201 (e.g., memory 905) and transmitted at a later time once a network connection is successfully established, such as during another flow event. See block 1041. This may result in multiple records being sent at one time. In such instances, the multiple records may be stored in association with a sequence number, which may define a temporal order of the flow event within a number of other flow events that have been initiated without successful establishment of a network connection.

[0120] If the network connection is successfully established, then the network information may be entered into the sensed data characteristics record as indicated by block 1043. Additionally, after the sensed data characteristics record is stored, the record may be transmitted (e.g., wirelessly transmitted) over one or more networks (e.g., network 929) to, e.g., remote device 913, such as a computer, server, cell phone, mobile device, or user equipment, for instance. See block 1045. In some embodiments, processor 305 and/or communication interface 309 may not only transmit the most recent sensed data characteristics record (e.g., for the just concluded flow event), but one or more other sensed data characteristics records for other recent events stored to a memory or storage device of or accessible to flow meter 201. After this transmission, communication interface 309 may be powered off. Further, as illustrated per block 1047, a determination may be made whether an on-going flow event is occurring. If so, process 1000 may revert to oval 1005, and if not, process 1000 may traverse to block 1027.

[0121] In some embodiments, processor 305 and/or communication interface 309 may be configured to periodically send complete and/or partial records of one or more flow events, such as in the event of an extended flow event lasting several hours, days, weeks, months, etc. In this manner, a sensed data characteristics record may be transmitted to remote device 913 at the conclusion of a fourth timer, such as at every 5-minute, 10-minute, 15-minute, 20-minute, or the like interval. In some cases, after a determined number of these partial flow event record transmissions, processor 305 and/or communication interface 309 may transition to one or more longer intervals, such as every 30-miuntes, 60-minutes, 90-minutes, or the like intervals. This may be done to converse power source 311.

[0122] According to various embodiments, remote device 913 may be configured to receive the various records from one or more flow meters, such as flow meter 201, and aggregate such information into a centralized repository. Remote device 913 may also be configured to generate one or more flow characteristics (or information) from or utilizing the sensed data and/or sensed data characteristics received from the flow meter(s), such as an indication of an initiation of fluid flow through fluid release assembly 100, an amount of fluid flow through fluid release assembly 100, a rate of fluid flow through fluid release assembly 100, etc. This information may be made available to one or more user interfaces for monitoring, billing, etc., purposes. In some cases, the information may be made available via a map interface such as described in association with FIG.

13 or a graphic representation, such as shown in FIG. 12. It is also noted that the data and/or information transmitted over network 929 may be ultimately transmitted to a computer or server and stored on a memory device of that computer or server. This data may include any data described above, such as sensed data, sensed data characteristics, flow characteristics, and location data. Such data can be stored in the format of a record 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 fluid release assembly, such as fluid release assembly 100. This data may also be used to determine how much fluid was drawn from that fluid release assembly and potentially who drew the fluid therefrom. 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/or the like, that fluid is being drawn from a specific fluid release assembly. This alert may be in the form of an email, pop-up screen, text message, light, and/or audio signal, for instance.

[0123] Location determination coupled with fluid transport (volume, mass, rate, etc.) may not only be useful for identifying where fluid is consumed, but also for providing performance indicators based on the functionality and behavior of the fluid release assemblies, pipes, valves, and/or other infrastructure components, as well as services used by the infrastructure.

[0124] In some embodiments, the data provided by flow meters may be used to provide real-time use of one or more fluid 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 fluid release assembly. The map may include other information, such as historical use data of the geographic locations of all fluid 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 that indicate each use of a fluid release assembly within, for instance, 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 fluid drawn or the number of flow events at the location.

[0125] Referring to FIG. 13, map 1301 may be depicted on screen 1303 of a device, such as a computer, and includes region 1305 that represents a geographical region, such as the boundary of a city or utility district. Map 1301 includes first geographic icons 1307A and 1307B that each may represent the real-time use of a single fluid release assembly, such as fluid release assembly 100. First geographic icons 1307A and 1307B may provide information about the real-time use, such as sensed data, sensed data characteristics, and/or flow characteristics of fluid drawn during a flow event, as indicated by pop-up bubble 1309 over first geographic icon 1307B that may be generated in response to first geographic icon 1307B being interacted with or otherwise selected. Second geographic icons 1311 A and 131 IB 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/or historical uses of a fluid release assembly or geographic location may be displayed in a chart adjacent to map 1301 on screen 1303 or may be conveyed via a graphical representation, such as graphical representation 1201 shown in FIG. 12.

[0126] As seen in FIG. 14, example record 1400 may generated by one or more of flow meter 201 and remote device 913. As shown, record 1400 includes various data, such as unique identifier (or ID) 1401 of a fluid release assembly, unique data identifier (or DATA ID) 1403 of a flow meter, network (or carrier) 1405 information, general packet radio service identifier (or GPRS_SN) 1407, position information 1409 (e.g., one or more of latitude 1409a, longitude 1409b, altitude 1409c, and address 1409d), date 1411, time 1413, flow rate (or flow) 1415, volume (or aggregate fluid extraction) 1417, battery voltage (or battery) 1419, and various other information 1421, e.g., firmware version 1421a of processor 305, cumulative count (or time) (CC) 1421b of fluid extraction, average vibration 1421c, maximum vibration 1421 d, sequence number of flow events (SEQ) 1421e, and flow event count (or time) (EC) 142 If of a particular flow event, and/or the like. It is noted that the sequence number of any given flow event may correspond to the temporal ordering of that flow event within a plurality of flow events that have occurred (or are occurring) without successful establishment of a network connection, such as in association with at least one of blocks 1017 and 1039 within process 1000. In this manner, processor 305 of flow meter 201 may store the sensed data, sensed data characteristics, and/or fluid characteristics in, for instance, memory 905 (or any other suitable memory or storage location) in correspondence with the flow event related thereto. To this end, data/information transmission over, for instance, network 929 may also be associated with a particular flow event utilizing its sequence number. In some cases, data/information transmission may be aggregated for a number of flow events and the sequencing numbers of the particular flow events may be utilized by, for example, remote device 913 to ensure data/information is kept in association with its particular flow event. Any combination of the aforementioned items may be included in a record, such as record 1400. In various embodiments, record 1400 includes at least one of position information 1409 and a fluid characteristic, such as aggregate fluid extraction (or use) 1417 over an appropriate time period for a particular fluid release assembly, such as fluid release assembly 100.

[0127] Any one or more of various sensors may participate in the controlling operation and/or collecting and processing data of a module or system as described herein. Such sensors may include inertial sensors (e.g., accelerometers and/or gyroscopes), temperature sensors, acoustic sensors, optical sensors, material sensors (e.g., humidity sensor or volatile organic compound sensors), and/or the like. In some embodiments, accelerometers or other inertial sensors are integral to operation of a module. In some embodiments, accelerometer data is employed to measure fluid consumption from a fluid release assembly 100 without having to rely on another form of flow meter, such as a rotational or magnetic device. In some embodiments, accelerometer data is used to determine flow characteristics other than merely flow rate. For example, accelerometer data may identify blockages and poor hydraulic conditions based on vibration signatures.

Other Embodiments

[0128] While various embodiments described herein have focused on fluid (e.g., water) dispensing pipes and distribution networks, embodiments are not limited thereto. For example, the fluid measured may be a fluid other than water or even a liquid. For instance, the fluid may be any gas or liquid for which a dispensed or transmitted quantity may be measured and reported over a network. Examples of liquids include petroleum (e.g., in a pipeline), chemical feedstocks in chemical plants, and/or the like. Examples of gases include, for instance, 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.

[0129] 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.

[0130] 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. [0131] 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.

[0132] 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.

[0133] 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.

[0134] 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.

[0135] 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.

[0136] 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.

[0137] 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.

[0138] 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 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). 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.

[0139] 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.

[0140] 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.

[0141] 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. [0142] 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. An apparatus comprising: a housing configured to connect to a hydrant in a recess below ground level; one or more sensors in the housing, the one or more sensors being configured to output sensed data in response to fluid flow through the hydrant; and a processor in the housing, the processor being configured to: determine one or more sensed data characteristics from the sensed data, the one or more sense data characteristics representing one or more properties of the sensed data; and transmit, via a wireless communication interface, the one or more sensed data characteristics to a remote computational device for conversion, outside the processor, to one or more flow characteristics of the fluid flow through the hydrant.

2. The apparatus of claim 1, wherein the sensed data comprises an indication of an initiation of the fluid flow through the hydrant.

3. The apparatus of claim 1, wherein the sensed data comprises an indication of an amount of the fluid flow through the hydrant and/or a rate of the fluid flow through the hydrant.

4. The apparatus of claim 1, wherein the sensed data comprises at least one vibration signal caused, at least in part, by the fluid flow through the hydrant.

5. The apparatus of claim 1, wherein at least one of the one or more sensors is an accelerometer.

6. The apparatus of claim 1, wherein the sensed data comprises at least one acoustic signal caused, at least in part, by the fluid flow through the hydrant.

7. The apparatus of claim 1, wherein the one or more sensed data characteristics comprise a duration of the sensed data and/or a statistical characteristic of the sensed data.

8. The apparatus of claim 1, wherein the one or more sensed data characteristics comprise an average value of the sensed data, a maximum value of the sensed data, a minimum value of the sensed data, or any combination thereof.

9. The apparatus of claim 1, wherein the one or more flow characteristics comprise an amount of the fluid flow through the hydrant and/or a rate of the fluid flow through the hydrant.

10. The apparatus of claim 1, wherein the one or more flow characteristics comprise an initiation time of the fluid flow through the hydrant.

11. The apparatus of claim 1, wherein the wireless communication interface is at least partially supported within the housing.

12. The apparatus of claim 1, wherein the wireless communication interface comprises communications logic configured to establish and/or maintain a connection with at least one wireless network.

13. The apparatus of claim 12, wherein the at least one wireless network is a cellular network.

14. The apparatus of claim 1, further comprising: a bracket assembly configured to support the housing adjacent to a body of the hydrant and/or an outlet fitting of the hydrant.

15. The apparatus of claim 1, further comprising: a bracket assembly configured to support an antenna of the wireless communication interface at a higher elevation within the recess than the housing.

16. The apparatus of claim 1, wherein the processor is further configured to discriminate between the sensed data caused, at least in part, by the fluid flow through the hydrant and noise caused, at least in part, by at least one source other than the fluid flow through the hydrant.

17. The apparatus of claim 16, wherein the noise is caused, at least in part, by one or more automobiles.

18. The apparatus of claim 16, wherein the processor is configured to exclude the noise prior to determination of the sensed data characteristics.

19. The apparatus of claim 1, wherein the hydrant is compliant with British Standard (BS) 750.

20. An apparatus comprising: at least one processor; at least one communication interface; and at least one memory comprising one or more sequences of one or more instructions that, in response to being executed by the at least one processor, cause the apparatus at least to: receive vibration data from at least one sensor; determine whether the vibration data is indicative of fluid flow through a hydrant; generate, in response to the vibration data being indicative of fluid flow through the hydrant, flow information based on the vibration data; and transmit, via the communication interface over a wireless network, the flow information to a remote server configured to receive flow information from a plurality of apparatuses including the apparatus, wherein the apparatus is co-located with the hydrant within an underground recess.

21. The apparatus of claim 20, wherein: the apparatus comprises the at least one sensor; and the at least one sensor is configured to generate the vibration data in response to fluid flow through the hydrant.

22. The apparatus of claim 21, wherein the at least one sensor is at least one accelerometer.

23. The apparatus of claim 21, wherein: the apparatus further comprises a housing configured to support the at least one processor, the at least one memory, and the at least one sensor therein; and the housing is configured to support the least one communication interface at least partially therein.

24. The apparatus of claim 23, wherein the apparatus further comprises a first support structure configured to connect the housing adjacent to an output fitting of the hydrant.

25. The apparatus of claim 23, wherein the apparatus further comprises a second support structure configured to support an antenna of the communication interface at a higher elevation within the underground recess than the housing.

26. The apparatus of claim 20, wherein the flow information comprises a duration of the fluid flow through the hydrant.

27. The apparatus of claim 20, wherein the flow information comprises at least one of a maximum vibration level, a minimum vibration level, and an average vibration level.

28. The apparatus of claim 20, wherein the flow information comprises a unique identification of the hydrant.

29. The apparatus of claim 28, wherein the unique identification of the hydrant comprises a location of the hydrant and/or a serial number of the hydrant.

30. The apparatus of claim 20, wherein at least a body of the hydrant separates the at least one sensor from the fluid flow.

31. The apparatus of claim 20, wherein the one or more sequences of the one or more instructions are configured to, in response to being executed by the at least one processor, cause the apparatus at least to transmit the flow information to the remote server according to a first determined reporting interval.

32. The apparatus of claim 31, wherein the one or more sequences of the one or more instructions are configured to, in response to being executed by the at least one processor, cause the apparatus at least to adjust, after a determined amount of elapsed time, the first determined reporting interval to a second determined reporting interval different from the first determined reporting interval.

33. The apparatus of claim 20, wherein the one or more sequences of the one or more instructions are configured to, in response to being executed by the at least one processor, cause the apparatus at least to at least partially filter the vibration data to exclude vibratory noise unrelated to the fluid flow through the hydrant.

34. The apparatus of claim 20, wherein the hydrant is compliant with British Standard (BS) 750.

35. The apparatus of claim 20, wherein the remote server is configured to determine an amount of the fluid flow through the hydrant based on the flow information and/or a rate of the fluid flow through the hydrant based on the flow information.

36. A method of detecting and/or characterizing fluid flow through a hydrant in a recess below ground level, the method comprising: logging, during a flow event, vibration data caused, at least in part, by the fluid flow through the hydrant; determining that the flow event has stopped and/or a time limit for the flow event has expired; determining one or more vibration characteristics from the vibration data, the vibration characteristics representing one or more properties of the vibration data; and transmitting, via a wireless network, the one or more vibration characteristics to a remote computational device for conversion to one or more flow characteristics of the fluid flow through the hydrant.

37. The method of claim 36, further comprising, prior to logging the vibration data: detecting vibration from the hydrant; determining whether the vibration qualifies as fluid flow through the hydrant; and starting, in response to determining that the vibration qualifies as fluid flow through the hydrant, a timer for the flow event.

38. The method of claim 37, wherein determining that the flow event has stopped comprises determining that the vibration no longer qualifies as fluid flow through the hydrant.

39. The method of claim 38, further comprising: stopping, in response to determining that the vibration no longer qualifies as fluid flow through the hydrant, the timer.

40. The method of claim 36, further comprising: determining, via the remote computational device, the one or more flow characteristics utilizing the vibration characteristics.

41. The method of claim 36, wherein the vibration characteristics comprise a duration of the vibration data logged during the flow event and/or a statistical characteristic of the vibration data logged during the flow event.

42. The method of claim 36, wherein the vibration characteristics comprise an average value of the vibration data, a maximum value of the vibration data, a minimum value of the vibration data, or any combination thereof.

43. The method of claim 36, wherein the flow characteristics comprise an amount of the fluid flow through the hydrant and/or a rate of the fluid flow through the hydrant.

44. The method of claim 36, wherein the flow characteristics comprise an initiation time of the fluid flow through the hydrant.

45. The method of claim 36, further comprising: transmitting, via the wireless network, information indicating when the flow event initiated.

46. The method of claim 45, wherein the information is transmitted to an entity responsible for detecting and/or monitoring authorized and/or unauthorized fluid flow from the hydrant.

47. The method of claim 36, wherein the hydrant is compliant with British Standard (BS) 750.