Patent Application
20210021913
This application relates generally to data capture and transmission, and, more particularly, to an underwater data capture and transmission system.
Underwater data acquisition systems can be deployed from vessels of opportunity to collect remote underwater sensor data. Such systems do not require permanent infrastructure for deployment or operation. However, the cost and effort associated with collecting deep water data from the sensors of such systems can be expensive and problematic. The present disclosure is directed to overcoming these and other problems of the prior art.
In an embodiment, the present disclosure is directed to an underwater data capture and transmission system. The system includes a base configured to sink in water, a sensor configured to capture data while submerged in water, a data buoy sized and configured to be at least partially disposed within a housing and configured to receive data collected by the sensor, a processing unit configured to selectively release the data buoy from the housing to allow the data buoy to travel toward a surface of the water, and a tether for coupling the housing and sensor to the base.
In other embodiments, the present disclosure is directed to a data buoy. The data buoy includes a controller configured to execute software instructions, a data storage in signal communication with the controller, the data storage configured to store data collected from one or more sensors, a communication module comprising a transceiver and an antenna, the communication module in signal communication with the controller and configured to transmit data to a remote location, a power module for providing power to the controller and the communication module, a float constructed of a buoyant material, and a coupler configured to engage a housing. The float is configured to cause the data buoy to move toward a water surface when the coupler is disengaged from the housing.
Various exemplary embodiments are described in detail below with reference to the following Figures. The drawings are provided for purposes of illustration only and merely depict exemplary embodiments. These drawings are provided to facilitate the reader's understanding of the embodiments and should not be considered limiting of the breadth, scope, or applicability of the disclosure. It should be noted that for clarity and ease of illustration these drawings are not necessarily drawn to scale.
This description of embodiments is intended to be read in connection with the accompanying drawings, which are to be considered part of the entire written description. The drawing figures are not necessarily to scale and certain features of the invention may be shown exaggerated in scale or in somewhat schematic form in the interest of clarity and conciseness. In the description, relative terms such as “horizontal,” “vertical,” “up,” “down,” “top,” and “bottom” as well as derivatives thereof (e.g., “horizontally,” “downwardly,” “upwardly,” etc.) should be construed to refer to the orientation as then described or as shown in the drawing figure under discussion. These relative terms are for convenience of description and normally are not intended to require a particular orientation. Terms including “inwardly” versus “outwardly,” “longitudinal” versus “lateral” and the like are to be interpreted relative to one another or relative to an axis of elongation, or an axis or center of rotation, as appropriate. Terms concerning attachments, coupling and the like, such as “connected” and “interconnected,” refer to a relationship wherein structures are secured or attached to one another either directly or indirectly through intervening structures, as well as both movable or rigid attachments or relationships, unless expressly described otherwise. The term “operatively or operably connected” is such an attachment, coupling or connection that allows the pertinent structures to operate as intended by virtue of that relationship.
The data acquisition systems described herein may include one or more releasable data buoys (RDB) that are configured to relay acquired subsea data to a surface client. In various embodiments, the system may include multiple RDBs configured to couple to a single primary processing unit (PPU) allowing for multiple sensor data sets to be recovered over long-term deployments of the system. Subsea data may be collected, stored and then transmitted (e.g., utilizing Iridium satellite or other suitable transmission technology) to any shore base or mobile asset equipped with a transceiver (e.g., an Iridium transceiver). Because data may be transmitted at multiple times during the deployment of the system, this intermittent data may be used to validate operations and augment modeling efforts. In addition, near real-time events can be captured with event notification to clients on a global scale.
The housing 112 may include a plurality of RDBs 104 and be configured to release an RDB 104 to allow the RDB 104 to float to the ocean surface.
The system 100 may include any appropriate type of sensors and may include multiple sensors of the same type as well as combinations of different types of sensors. For example, the system 100 may include oceanographic sensors—such as conductivity sensors, temperature sensors, pressure sensors, depth sensors, turbidity sensors, dissolved oxygen sensors, current sensors, water level sensors, tsunami sensors, optics and various other analog and digital instruments. The system 100 may also include sensors for gathering acoustic data—such as sensors configured for passive acoustic monitoring, detection of mammals, detection of vessel traffic, and/or surveillance. The system 100 may also include sensors configured for subsea communications monitoring—such as sensors configured to provide a cable status indication, node monitoring, and/or security.
The plurality of sensors 106 may be configured for underwater data collection. The plurality of sensors 106 may be spaced from each other along the tether 110 to collect data at different locations (e.g., different ocean depths). The sensors 106 may be configured to generate a signal indicative of a monitored parameter (e.g., pressure, flow rate, presence or absence of a material or compound, to list only a few non-exclusive examples). In some embodiments, one or more of the sensors 106 may be image capture devices configured to capture image data. The sensors 106 may be configured to transmit data to the RDBs 104.
The base 108 may include a weighted component configured to anchor the sensors 106 and the tether 110 to locations under the water. The base 108 may be configured as a stationary component configured to maintain the PPU 102 and sensors 106 in a general area under the water. In some embodiments, the base 108 may be configured for remote control to move the base 108 to another location on the ocean floor. For example, the base may include wheels and/or ballast system to assist in moving the base 108 from one location to another on the ocean floor.
The base 108 may be configured such that it can release the tether 110 to allow the PPU 102, sensors 106, and/or housing 112 to float to the surface where they can be recovered. For example, in one embodiment, the base 108 is configured to release the tether 110 based on an acoustic signal. In such embodiments, the base 108 may include an acoustic release or burn wire. For example, an acoustic signal may be sent from a vessel to the system 100 to trigger release of the tether 110. In response to receipt of the acoustic signal, the base 108 releases the tether 110, thereby allowing the PPU 102, sensors 106, and/or housing to float toward surface while leaving the base 108 on the sea floor. Upon release, or upon surfacing, the PPU 102 may transmit a datagram containing information regarding its geographic position to allow it to be tracked and located. For example, the PPU 102 may transmit Iridium Short Burst Data (SBD) transmissions.
The tether 110 may be fabricated from a strong and durable material to form a reliable connection between the base 108, sensors 106, PPU 102, and housing 112. The tether 110, in some embodiments, may be and/or include data transmission capability between the sensors 106 and the PPU 102. For example, the tether 110 may include a data transmission wire to enable the sensors 106 to transmit data to the PPU 102 and the RDBs 104.
The PPU 102 may also include a release mechanism 122 configured to selectively retain and release the RDBs 104 disposed in the housing 112 and coupled to an RDB docking station 124. In embodiments in which the PPU 102 and the housing 112 are collocated or adjacent, the release mechanism 122 may be a mechanical release mechanism. In other embodiments, in which the PPU 102 and the housing 112 are spaced apart, the PPU 102 may be mechanically or electrically coupled to a release mechanism within, or coupled to, the housing 112 to release the RDBs 104 from the RDB docking station 124. The PPU 102 may further include a receiver 126 to receive signals and an A/D converter 128 to convert analog signals to digital data. In exemplary embodiments, the receiver 126 is configured to receive acoustic signals for controlling the release mechanism 122. For example, such an acoustic signal may be sent from a vessel of opportunity to trigger release of an RDB 104. The release mechanism 122 may include a mechanical latch that is electrically actuated to retain and release the RDBs 104 by moving a sliding pin or a rotating mechanical stop that secures the RDBs in place. One or more of the RDBs 104 be held in place with an electromagnetic latch that releases upon command or automatically in the event of power failure in a “fail safe” mode
The coupler 142 of the RDB 104 and the release mechanism 122 of the PPU 102 are configured such that each of the RDBs 104 can be selectively released to allow the RDB 104 to float to the surface of the water (e.g., ocean, lake, or other water body) to allow the RDB 104 to transmit data to a satellite or other recipient. In various embodiments, the RDB 104 includes a float 146 constructed of a buoyant material (e.g., syntactic foam) to facilitate the RDB 104′s progression to the surface.
As described above, each RDB 104 may be positively buoyant, creating an upward buoyancy force on the RDB 104. In some embodiments, the release mechanism 122 of the PPU 102 may include a mechanical attachment point engaged with the coupler 142 to hold the RDB 104 in place. In such embodiments, upon activation of a release command the PPU 102 will activate a mechanical actuator to physically open the release mechanism 122 that is holding the RDB 104 in place to release the RDB 104. In other embodiments, the release mechanism 122 of the PPU 102 may include a magnetic attachment point engaged with the coupler 142 to hold the RDB 104 in place. In such embodiments, upon activation of a release command, the PPU 102 may release the magnetic coupling by moving the magnets apart or depowering an electromagnetic force.
In at least one embodiment, one of the sensors 106 is a (water) current meter. In use, for example, a data set containing six months of current meter data may be used to verify operation of the system 100 and provide preliminary results. In such embodiments, the PPU 102 may be programmed to collect current meter data from the current sensor, store the data (in the data storage module 116 of the PPU 102), and forward it to one of the RDBs 104 for storage in the data storage module 132 of the RDB 104. After the RDB 104 is powered on and data is transferred to the RDB 104, the RDB 104 is released by the release mechanism 122 and the RDB 104 floats to the surface. With the RDB 104 at or near the surface, the antenna 140 and transceiver 134 establishes a connection with a recipient (e.g., via an Iridium antenna) and data is transferred to the recipient.
Further, in various embodiments, one of the sensors 106 is an acoustic sensor configured to acquire an acoustic signature of interest. Based on the acoustic signature, the distance and bearing of the source of the acoustic signature is calculated (e.g., by the controller 114 of the PPU 102). This data may then be transferred or copied to an RDB 104 and the RDB 104 may be released by the release mechanism 122 to allow the RDB 104 to float to the surface. The data may then be transferred to a recipient via the transceiver 134 and antenna 140.
In some embodiments, the PPU 102 is configured to release RDBs 104 at predetermined intervals. Alternatively, or additionally, the PPU 102 may be configured to release RDBs 104 upon the occurrence of certain events. For example, if data generated by the sensors crosses a predetermined threshold, the PPU 102 may release an RDB 104 so that such data may be transmitted to a recipient. In addition, time and event based occurrences can be programmed, for example, through a graphical user interface (GUI) to control the timing of the release of the RDBs 104.
Alternatively, or additionally, the PPU 102 may be configured to release RDBs 104 in response to the receipt of a release signal. For example, once on site, a vessel may lower a transducer and send a release command to the subsea PPU 102. In response to receipt of the signal (e.g., by the acoustic receiver 126), the PPU 102 releases the appropriate RDB 104, thereby allowing it to float to the ocean surface. Once it is at or near the surface, the RDB 104 transmits the data (e.g., via satellite communications). The release mechanism 122 may take different forms for different applications. For example, in some embodiments (e.g., applications in which an automatic release is desired in the event of a power loss), a magnetic release may be used. In other embodiments, a mechanical latch that is operated by an electromechanical actuator may be used. In some applications, the RDB 104 may only be released at times determined by the PPU 102, for example.
In various embodiments, the RDB 104 transmits the data to a satellite for further transmission to desired recipients. Alternatively, or additionally, data can be transmitted directly to a vessel of opportunity or other recipient. In some embodiments, the RDB 104 may also be configured to transmit the position (e.g., GPS coordinates) of the RDB 104 to allow for recovery of the RDB 104. In other embodiments, the RDB 104 may be configured to be a single use device.
At 202, the system 100 is deployed. For example, the base 108 may be released into a water body (e.g., ocean, lake, river, man-made body, etc.) and sink to the floor or to a designated depth. The base 108 may thereby pull the PPU 102, RDBs 104, sensors 106, and tether 110 underwater.
At 204, the sensors 106 may collect data while underwater. For example, the sensors 106 may detect signals indicative of one or more parameters. In some embodiments, the sensors 106 may collect image data.
At 206, the PPU 102 may receive and store the collected sensor data. For example, the PPU 102 may store the collected data in the data storage module 116 of the PPU 102.
At 208, the PPU 102 may transfer the received data to an RDB 104. For example, the controller 114 may execute stored software instructions to initiate a data transfer from the PPU 102 to the RDB 104. The data storage module 132 of the RDB 104 may be configured to receive the transferred data. The PPU 102 may select an RDB 104 to receive the data. For example, some RDBs 104 may be particularly configured for certain data transmission and the controller 114 may select such an RDB 104 for data receipt. In other embodiments, the PPU 102 may select a next RDB 104 in a sequence. In still other embodiments, the PPU 102 may transmit the data to a plurality of (e.g., all of) the RDBs 104.
At 210, the PPU 102 may release the RDB 104 from the housing 112 to allow the RDB 104 to float or otherwise travel to the surface. For example, the PPU 102 may transmit a signal to the release mechanism 122 (e.g., an electromechanical latch) to cause release of the RDB 104 from the housing 112. The controller 114 may transmit an electronic signal to the controller 130 with instructions to actuate or otherwise disconnect the coupler 142 to cause the RDB 104 to be released from the housing 112. The RDB 104 may thereafter float or travel toward the surface of the water.
At 212, the released RDB 104 may transmit data from the RDB 104 to a recipient. For example, the RDB 104 that has floated to the surface may include the controller 130 causing the transceiver 134 and/or antenna 140 to establish a remote connection with a recipient to enable wireless transmission of the data collected by the sensor(s) 106 and transferred to the RDB 104.
In some embodiments, the method may further include, at 214, releasing the tether 110 of the system 100 to allow the PPU 102 and sensors 106 to float or otherwise travel to the surface (e.g., for subsequent tracking and collection).
While the foregoing description and drawings represent preferred or exemplary embodiments, it will be understood that various additions, modifications and substitutions may be made therein without departing from the spirit and scope and range of equivalents. In particular, it will be clear to those skilled in the art that the disclosed systems and methods may be embodied in other forms, structures, arrangements, proportions, sizes, and with other elements, materials, and components, without departing from the spirit or essential characteristics thereof. In addition, numerous variations in the methods/processes described herein may be made without departing from the spirit of the disclosure. One of ordinary skill in the art will further appreciate that the disclosed systems and methods may be used with many modifications of structure, arrangement, proportions, sizes, materials, and components and otherwise, used in the practice of the invention, which are particularly adapted to specific environments and operative requirements without departing from the principles of the disclosure. The presently disclosed embodiments are therefore to be considered in all respects as illustrative and not restrictive.
This application claims priority to U.S. Provisional Patent Application No. 62/875,026, filed on Jul. 17, 2019, which is herein incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 62875026 | Jul 2019 | US |
