INTEGRATION BETWEEN UNMANNED AERIAL SYSTEM AND UNMANNED GROUND ROBOTIC VEHICLE

Abstract

Integration between unmanned aerial system and unmanned ground robotic vehicle are disclosed herein. One variation of a robotic system may generally comprise an unmanned aerial vehicle (UAV), an unmanned ground vehicle (UGV), and a base station configured to receive the UAV and replace a spent power supply cartridge from the UAV and further having a charging mechanism configured to wirelessly transfer power to the UGV when the UGV is positioned in proximity to the charging pad.

Claims

1. A robotic system, comprising: an unmanned aerial vehicle (UAV); an unmanned ground vehicle (UGV); a base station configured to receive the UAV and replace a spent power supply cartridge from the UAV and further having a charging mechanism configured to transfer power to the UGV when the UGV is positioned in proximity to the charging mechanism.

2. The system of claim 1 wherein the UAV comprises a drone.

3. The system of claim 1 wherein the UGV comprises a quadrupedal UGV.

4. The system of claim 1 wherein the base station comprises a landing zone configured to receive the UAV.

5. The system of claim 1 wherein the charging mechanism comprises a charging pad.

6. The system of claim 1 wherein the base station comprises a field server for receiving data wirelessly from the UAV or the UGV.

7. The system of claim 6 further comprising a cloud-based server in wireless communication with the field server.

8. The system of claim 7 further comprising a frontend application accessible by an operator and in wireless communication with the cloud-based server.

9. The system of claim 1 wherein the UGV comprises a computer configured to wirelessly communicate with the base station.

10. A method of monitoring an area, comprising: receiving an alert from a remote alarm; determining one or more mission requirements based on the alert; communicating with a UAV and a UGV via a base station; and deploying the UAV alone, the UGV alone, or the UAV and UGV simultaneously.

11. The method of claim 10 further comprising automatically replacing a power supply cartridge from the UAV via the base station prior to deploying the UAV.

12. The method of claim 10 further comprising automatically charging the UGV via the charging mechanism in proximity to the base station prior to deploying the UGV.

13. The method of claim 10 wherein deploying the UAV or the UGV comprises communicating with the UAV or the UGV via a server within the base station.

14. The method of claim 13 further comprising wirelessly communicating with the UAV or the UGV via a cloud-based server.

15. The method of claim 14 further comprising wirelessly communication with the cloud-based server via a frontend application.

16. The method of claim 10 wherein deploying comprises launching the UAV or the UGV from the base station.

17. The method of claim 10 wherein deploying comprises altering a mission of the UAV or the UGV.

18. A robotic system, comprising: an unmanned aerial vehicle (UAV); an unmanned ground vehicle (UGV); a base station configured to receive the UAV and replace a spent UAV power supply cartridge from the UAV, and where the base station is further configured to replace a spent UGV power supply cartridge from the UGV when the UGV is positioned in proximity to the base station.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The detailed description is described with reference to the accompanying figures.

[0020] FIG. 1A illustrates a combined UAV and UGV system.

[0021] FIG. 1B illustrates another variation of a combined UAV and UGV system.

[0022] FIG. 2A illustrates a schematic diagram of how a base station common to both the UAV and UGV may be utilized.

[0023] FIG. 2B illustrates a schematic diagram of one variation of the electrical architecture for providing power to both a UAV and UGV.

[0024] FIG. 3 illustrates a schematic diagram of a single system which may provide for command-and-control of both the UAV and UGV.

[0025] FIG. 4 illustrates a schematic diagram for how the controller may respond for various missions where the UAV and UGV are diverted automatically or affirmatively controlled to respond to an alarm or alert at a remote location.

[0026] FIG. 5 illustrates a schematic diagram of how a processor or computer may be integrated upon a UGV.

[0027] FIG. 6 illustrates a schematic diagram which represents one example of the software architecture showing how the UAV may be controlled and monitored by a human operator.

[0028] FIG. 7 illustrates a schematic diagram of one example of how the UGV may communicate with a remote operator utilizing the on-board computer integrated with the UGV.

[0029] FIG. 8 illustrates a schematic diagram of another example of how the UGV may communicate with a remote operator utilizing the on-board computer integrated with the UGV.

DETAILED DESCRIPTION OF THE INVENTION

[0030] An unmanned system which can provide command and control support as well as supply power via an automated power supply replacement system may incorporate both an Unmanned Aerial Vehicle (UAV) such as a drone and an automated Unmanned Ground Vehicle (UGV), including Quadrupedal Unmanned Ground Vehicles (Q-UGV), which may include any variation of movement mechanism such as legged, wheeled, tracked, etc. vehicle which may be fully or partially automated.

[0031] Examples of UAVs or UAV systems which may be used with any of the embodiments described here are described further detail in U.S. Pat. Nos. 9,969,285 and 9,783,075 and U.S. Pat. Pub. 2018/0222339, each of which is incorporated herein by reference in its entirety and for any purpose. Examples of UGVs or UGV systems which may also be used with any of the embodiments described here may include UGV and Q-UGV systems from Ghost Robotics Corporation (Philadelphia, Pa.), Boston Dynamics, Inc. (Waltham, Mass.), or any number of other systems.

[0032] An example of a combination UAV and UGV system 10 is illustrated in FIG. 1A which shows one variation of a base station 12 having a UAV housing 16 which may incorporate a landing zone for a UAV 14 as well as several interior bays which may hold replacement power supply swap cartridges 20 which can be automatically exchanged for spent cartridges from the UAV 14 positioned upon the landing zone of the base station 12, as illustrated in the schematic diagram of FIG. 2A. A UGV 18 such as the Q-UGV shown may be integrated with the base station 12 such that the command-and-control function may be provided by a controller positioned within the base station 12 or remotely from the base station 12 for coordinating launch and/or recovery missions, as described in further detail below. The base station 12 may provide the launch and/or recovery missions to either the UAV 14 alone, UGV 18 alone, or to both the UAV 14 and UGV 18 in an integrated mission. The base station 12 may also provide a replaceable power supply for the UGV 18 or may provide for a charging station through which the UGV 18 may be powered or recharged 22, as shown in FIG. 2A.

[0033] FIG. 1B illustrates another example where the UGV 18 may be powered and/or housed in a UGV housing unit 17 which is physically separated from or separatable from the base station 12. While the UGV 18 may be powered by the base station 12, the UGV housing unit 17 may be used to not only house UGV 18 but also charge the UGV 18 when not deployed. UGV housing unit 17 may incorporate one or more wireless charging pads or wired power couplings which may engage with corresponding power couplings on the UGV 18. UGV 18 may also be seen incorporating a computer module 15 integrated with the UGV 18 and which may enable the UGV 18 to receive and transmit data to and/or from base station 12 or another remote station or controller.

[0034] The combined UAV and UGV system 10 may provide a single command-and-control platform which may allow for the response to, e.g., an external alarm or internet-of-things (IoT) trigger, by deploying the UAV 14 or UGV 18 separately or simultaneously to an area of interest along pre-programmed routes. Video and telemetry from both the UAV 14 and UGV 18 may be streamed, e.g., in near real-time, to an operator at a central controller, as described in further detail herein. Moreover, while the UAV 14 and UGV 18 may follow predetermined waypoints and/or routes, an operator may optionally control one or both of the UAV 14 and UGV 18 manually. Upon completion of a mission, the UAV 14 and/or UGV 18 may be programmed to autonomously return back to the base station 12 for docking and recharging. Examples of a UAV system for monitoring and/or alerting an operator based on an external alarm or IoT trigger which may be implemented in combination with UGV 18, as described herein, are shown and described in further detail in U.S. patent application Ser. No. 17/185,495 filed Feb. 25, 2021, which is incorporated herein by reference in its entirety and for any purpose.

[0035] As the base station 12 may be configured for charging both the UAV 14 and UGV 18 simultaneously, the base station 12 may be powered by an external power source 24 (e.g., standard 110V/20A outlet), as schematically illustrated in the electrical architecture diagram of FIG. 2B. The external power source 24 may be used to power battery charging bays 28 (e.g., six or more bays) contained within the base station 12 for holding and charging swappable battery cartridges contained within each of the bays 28 for the automated swapping of a depleted power supply from the UAV 14 for a charged power supply from within the base station 12.

[0036] While the base station for the UAV 14 may be combined with a charging pad 30 for the UGV 18 into a single charging station, the UGV charge station may also be physically separated so that the UAV charging station may be physically separated from the UGV charging station which may also be standalone. Even with the UAV and UGV charging stations physically separated, they may still be linked through the single command and control system so that they remain in communication with one another, e.g., wirelessly or wired.

[0037] In other variations, the base station 12 may also hold and/or charge swappable battery cartridges within bays in the base station 12 for swapping out with a depleted power supply from the UGV 18 as well. In such an embodiment, an exchange mechanism (e.g., an automated robotic arm) may remove a depleted power supply from the UGV 18 and exchange it for a charged power supply stored within the base station 12.

[0038] A charging pad 30 such as a wireless transducer configured to remotely transmit electromagnetic energy for charging may be electrically coupled to the base station 12 such that the charging pad 30 is located to allow for the UGV 18 to position itself into proximity to the base station 12 and charging pad 30 for recharging when “docked”. Such remote charging pads 30 may be provided through sources such as WiBotic Inc. (Seattle, Wash.). A power relay 26 which may be optionally ethernet-enabled may be provided within the base station 12 for electrically coupling to the battery charging bays 28 and/or charging pad 30 to optionally enable for a remotely located operator to control or monitor the charging state of the UAV 14 or UGV 18 when docked to the base station 12 or charging pad 30 for recharging.

[0039] Because a single system may provide for command-and-control of both the UAV 14 and UGV 18, a single controller 42 incorporating the controller software may be in wireless communication with both, as illustrated in the schematic diagram 40 of FIG. 3. The controller 42 may accordingly be configured to incorporate any number of various functions for controlling both UAV 14 and UGV 18. For example, the controller 42 may view the payload 44, view telemetry data 46, provide an alarm response 48 which may be preprogrammed, provide for command-and-control 50 functionality, as well as provide for various mission planning 52 options for UAV 14 and UGV 18 individually or for both.

[0040] The controller 42 may respond according to the particular functionality or mission required. For example, FIG. 4 illustrates a schematic diagram 60 for how the controller 42 may respond for user planned missions 62, auto patrols 64 where the UAV 14 and UGV 18 follow predetermined mission profiles, and alarm responses 66 when the UAV 14 and UGV 18 are diverted automatically or affirmatively controlled to respond to an alarm or alert at a remote location.

[0041] In the event that the UAV 14 and UGV 18 are in a standby mode docked at the base station 12 or on another mission or patrol, the controller 42 may determine the mission requirements 68 and either automatically launch or divert 70 the UAV 14, launch or divert 72 the UGV 18, or launch or divert 74 both UAV 14 and UGV 18. Alternatively, the controller 42 may determine the mission requirements 68 and alert a human operator who may then either affirm or selectively affirm the launch or diversion of the UAV 14 and/or UGV 18 or take control of either the UAV 14 or UGV 18.

[0042] In order to enable command-and-control of the UGV 18 as well as to enable communication and transmission of data such as streaming of telemetry and video from the UGV 18 to the base station 12 or remote server, a processor or computer 86 may be integrated upon the UGV 18 and may be powered directly by the UGV 18 on-board power supply 88 (e.g., 5V, 2 A power line), as illustrated in the schematic diagram 80 in FIG. 5. The processor or computer 86 may enable the receipt of data such as video data from the on-board camera payload 90 and telemetry data from central control computer 84 of the UGV 18 to be routed via an on-board network switch 82 for wireless transmission, e.g., via an on-board LTE cellular modem 92, to communicate with the base station 12 or remote server.

[0043] FIG. 6 illustrates a schematic diagram 100 which represents one example of the software architecture showing how the UAV 14 may be controlled and monitored by a human operator. The flight controller 102 and camera payload 106 of UAV 14 may communicate via encrypted RF communication wirelessly through an on-board wireless RF radio 104 directly with a wireless RF radio 114 contained within the base station 12. The base station 12 may further incorporate a video encoder 116 which may receive video data transmitted from the camera payload 106 of the UAV 14. The video encoder 116 may transmit the video data to the on-board computer 108 in the base station 12 and specifically to a server 112 contained within that utilizes Transport Layer Security (TLS) certificates to establish secure web sockets to enable encrypted communications. The on-board computer 108 may also contain an API server 110 which may also receive the data received from the flight controller 102 of the UAV 14.

[0044] With the base station 12 located in the field in proximity to the UAV 14 (and UGV 18 as further described), the local server 112 may enable wireless encrypted communication via the TLS web sockets to a cloud-based server 118 which may be accessed and operated from anywhere in the world so long as the operator has an internet connection. The cloud-based server 118 may receive the telemetry and video data from the server 112 within the base station 12 via a server 124 which may receive the data into a digital video recording (DVR) application 126 in the cloud-based server 118 that receives the video data from the field server 112 and records it to secure storage for streaming and playback. The server 124 may also communication with a cloud-based backend server 122 that sends and receives data between the frontend application 130 through encrypted communications from a remotely located web browser 128 which may be loaded by an operator. The backend server 122 may also communicate with a cloud-based database 120. In this manner, an operator located anywhere in the world may communicate command-and-control data as well as receive telemetry and video data from a remote UAV 14 by communicating through the cloud-based server 124 and field based on-board server 112 located locally within the base station 12.

[0045] With this architecture, the UGV 18 may similarly communicate with the remote operator utilizing the on-board computer 86 integrated with the UGV 18, as illustrated in the schematic diagram 140 of FIG. 7. With the integrated computer 86, the on-board server 146 may communicate with the integrated API server 142 which may interface directly with the central computer 144 of the UGV 18. The telemetry and video data from the UGV 18 may be communicated through the server 146 of integrated computer 86 directly with the cloud-based server 124 which may then enable a remote operator to provide command-and-control to the UGV 18 as well as receive the telemetry and video data through the frontend application 130, as similarly described above. Alternatively, the UGV 18 may communicate directly with the API server 110 and server 112 within the base station 12 which may in turn communicate with the cloud-based server 124.

[0046] An alternative embodiment for software architecture which may be utilized to extend video streaming from the UGV 18 is shown in the schematic diagram 150 of FIG. 8. Similar to the embodiment described above, the integrated computer 86 within the UGV 18 may be configured to automatically receive video data from the camera payload 152 of the UGV 18 directly to the on-board server 146. The video data may be pushed in real time to the cloud-based DVR application 126 for storage and real-time streaming.

[0047] The architecture may be implemented alone or in combination with the telemetry data communication for any of the various embodiments described herein and in any combination, as desired.

[0048] The applications of the disclosed invention discussed above are not limited to the embodiments described, but may include any number of other non-flight applications and uses. Modification of the above-described methods and devices for carrying out the invention, and variations of aspects of the invention that are obvious to those of skill in the arts are intended to be within the scope of this disclosure. Moreover, various combinations of aspects between examples are also contemplated and are considered to be within the scope of this disclosure as well.