Patent ID: 12214895

DETAILED DESCRIPTION

The present disclosure relates to devices, system and methods for fluid and/or energy transportation and distribution using an unmanned aerial vehicle (“UAV”).

Although the present disclosure will be described in terms of specific aspects, the present disclosure will be readily apparent to those skilled in this art that various modifications, rearrangements, and/or substitutions may be made without departing from the spirit of the present disclosure. The scope of the present disclosure is defined by the claims appended hereto. For example, the present disclosure will be described encompassing one UAV, however, it is contemplated that the system may include multiple UAVs or even an unmanned land vehicle. Using manned aircraft or vehicles is also contemplated in accordance with the present disclosure, such as, for example, manned vertical takeoff and landing (“VTOL”) aircraft or vehicles.

For purposes of promoting an understanding of the principles of the present disclosure, reference will now be made to exemplary aspects illustrated in the drawings, and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the present disclosure is thereby intended. Any alterations and further modifications of the inventive features illustrated herein, and any additional applications of the principles of the present disclosure as illustrated herein, which would occur to one skilled in the relevant art and having possession of this disclosure, are to be considered within the scope of the present disclosure.

Generally, unmanned systems having an unmanned vehicle (e.g., systems typically having a robot, controllers, station, or base) may be limited by the battery capacity and/or the location of the charging station associated with the unmanned vehicle. Most unmanned vehicles lack compartments to store fluids and means to generate energy. As the unmanned vehicle moves (e.g., a UAV flies), the battery discharges or the source of power may reduce the amount of outputted power, and at a certain point, the unmanned vehicle must recharge (e.g., a UAV lands for recharging).

The present disclosure provides a novel system and method for powering an unmanned vehicle and ultimately transporting energy and/or fluid. The system and method generally involve collecting, processing, and transporting energy and/or fluid, which may be used in scenarios such as charging machinery, powering buildings, irrigating land, extinguishing fires and/or other scenarios where using an unmanned vehicle without the need of a charging station may be contemplated. The systems and methods provided in the present disclosure can be used to collect and process a fluid, for example, to desalinate and collect a fluid such as water (e.g., seawater). The fluid, before or after a selected process (e.g., desalination) may be used for power generation (e.g., to generate energy to power the unmanned vehicle) and/or irrigation of a selected area. For example, the system may include an unmanned vehicle, which may be configured to fly and irrigate a vegetable plantation in a controlled manner (e.g., through a controlled drop), and/or configured to drop water above a house or a forest fire. It is contemplated that the system may provide pre-emptive irrigation and/or irrigation in a responsive capacity.

In aspects, elements that may be associated with the functional enablement of elements to the UAV, desalinator, hydro cell, and the PV panel may not be described in detail (e.g., screws, wires, circuitry, connectors, etc.). However, some examples may be noted. The desalinator and/or the hydro cell and/or the PV panel may be described to an extent as to enable the functionality of the described aspects yet may not be described in detail.

Referring toFIGS.1and2, an exemplary unmanned system UAV system100is shown. The UAV system100generally includes a UAV200(e.g., a helidrone) configured to collect and transport a fluid120(e.g., seawater or fresh water). In aspects, the UAV200of the present disclosure may be a commercially available flying robot, VTOL or other vehicle. The UAV system100may generate electricity (e.g., by solar desalination and/or by a desalination battery), for example, to power and/or charge the UAV200.

In aspects, the UAV200may include a controller300, a desalinator600configured to process the fluid120, and/or a hydro cell700.

The desalinator600is configured to process seawater or brine to produce a low-salt content water. In aspects, the desalinator600may also be part of an energy generation system of the UAV200. For example, the desalinator600may include a solar desalinator, and/or a desalination battery. Solar desalination is a technique to produce water with a low salt concentration from seawater or brine using solar energy. Solar desalination may operate using direct heat from the sun or using electricity generated by solar cells to power a membrane process. For a detailed description of solar desalination, one or more aspects of which may be included or modified for use with the disclosed aspects, reference may be made to U.S. Pat. No. 10,538,435, the entire contents of which are incorporated herein by reference. A desalination battery is an aqueous energy storage device for the use of seawater deionization. The desalination battery, which generally consists of sodium and chloride dual-ion electrochemical electrodes, is an aqueous energy storage device for the use of seawater deionization. The desalination battery uses an electrical energy input (e.g., solar power) to extract sodium and chloride ions from seawater or brine and to generate fresh water. The desalination battery operates in a similar way to capacitive desalination techniques, but instead of storing charge in an electrical double layer (e.g., built at the surface of the electrode) it is held in the chemical bonds (e.g., in the bulk of the electrode material). In aspects, the process for separating seawater into fresh water and brine streams may include immersing fully charged electrodes in seawater, which do not contain mobile sodium or chloride ions when charged. Next, a constant current is applied to the electrodes in the solution in order to remove the ions from the solution. Next, the freshwater solution is extracted from the cell and the fresh water solution is replaced with additional seawater. Next, the electrodes are recharged in this solution, releasing ions, and creating brine. Finally, the brine solution is replaced with new seawater, and the desalination battery is ready for the next cycle. For a detailed description of a desalination battery, one or more aspects of which may be included or modified for use with the disclosed aspects, reference may be made to U.S. Pat. No. 10,822,254, the entire contents of which are incorporated herein by reference.

In aspects, the UAV system100may further include at least one supplemental battery (not shown) configured to store energy. The supplemental battery may include a lithium-based battery, for example, a lithium polymer battery. The supplemental battery (not shown) may be operably connected to a device that converts other energy forms (e.g., a PV collecting solar energy which can be converted into electricity) into mechanical energy, e.g., a motor (not shown). In further aspects, the supplemental battery (not shown) may be operably connected to the desalinator600, the hydro cell700, and/or the UAV200.

In aspects, the UAV system100may be configured for receiving and/or storing location data (e.g., location data in the form of GPS coordinates) and pre-determined fluid characteristics (e.g., salt content of water) in a memory320(FIG.4). In aspects, the UAV system100may be configured to interpret mapping software techniques that may aid in identifying and/or interpreting various terrains, flying paths, optimal irrigation patterns, environmental conditions and/or configurations. Thus, the UAV system100may include one or more sensors configured to collect environmental conditions. For example, a rain sensor may be configured to detect rain, and/or a GPS may be configured to detect features defining a specific area, (e.g., mountains and windmills), and communicate the results to the controller300.

Referring toFIG.3, a hydro cell700is shown. The hydro cell700is an electro chemical cell that converts chemical energy of hydrogen to an oxidizing agent (e.g., oxygen). Generally, the hydro cell700includes an anode, a cathode, and an electrolyte (e.g., salt-water) that enables ions to move between the two sides of the hydro cell700. At the anode, a catalyst (e.g., platinum) causes the fuel to undergo oxidation reactions that generate ions (often positively charged hydrogen ions) and electrons. The ions move from the anode to the cathode through the electrolyte (e.g., salt water). At the same time, electrons flow from the anode to the cathode through an external circuit, producing direct current electricity.

With reference toFIGS.1and2, the UAV200may include PV panel230, fluid chamber240, and energy tank260. The PV panel230may be of any suitable size to generate power for storage and/or use by the UAV system100. The fluid chamber240is configured to store a fluid210, such as fresh or desalinated water. The fluid chamber240may include two or more sub-chambers240a,240b. For example, a first sub-chamber240a, may be configured to hold fresh water (e.g., desalinated water), while the second sub-chamber may be configured to hold salt-water. The fluid chamber240may include an automated release valve configured to enable the release or entry of water to a body of water or release of water to a destination (e.g., a field for irrigation).

In aspects, the UAV system100may be configured to conduct an electrolysis process such as separating a fluid into oxygen and hydrogen gases and ultimately transporting the fluid(s) to a location (e.g., a first location). For example, the electrolysis process may include a polymer electrolyte membrane (PEM) electrolyzer. Water reacts at the anode to form oxygen and positively charge hydrogen ions (protons). The electrons flow through an external circuit and the hydrogen ions selectively move across the PEM to the cathode. The energy tank260may be operably connected to the hydro cell700and configured to store hydrogen, which may be generated as a by-product after the fluid120is processed at the hydro cell700. The hydrogen generated from the electrolysis of the fluid120may be used to power the UAV200. The energy tank260may be similar in shape and/or configuration to a gas holding tank, e.g., a spherical and/or bulbous design. In aspects, the spherical and/or bulbous design may aid the UAV200with buoyancy when the tank is resting in water. In aspects, the energy tank260may be a container of any kind or shape capable of storing a gas and/or liquid.

In aspects, the UAV200may be configured to be stationary at a first location (e.g., the UAV200may be waiting for instructions while floating in the ocean, similar to a buoy) prior to, during, or after fluid collection (e.g., the UAV200may be configured to wait for a pre-determined event while sitting on the ocean or other body of water). The UAV200is configured to collect the fluid120and receive the fluid120in the fluid chamber240(e.g., by a pump292of the UAV, or by opening the automated release valve241). For example, the UAV200can be configured to collect fluid such as water from the ocean while waiting for instructions, which may depend on a pre-determined task (e.g., if instructed, travel to a field which requires irrigation and deliver the fresh water). For example, the UAV may sit strategically for an indefinite period of time in a given location waiting for instructions. In aspects, the UAV may be on stand-by while floating in the ocean, similar to a buoy. For example, the UAV200may be configured to deliver water to an agricultural area, to aid agricultural productivity and the local environment/ecosystem.

In aspects, the PV panel230may be operably connected to the desalinator600to desalinate a fluid. As noted above, the desalinator600of the system100can be configured to desalinate a fluid having salt (e.g., seawater). The desalinator600may utilize solar energy collected via the PV panel230. In aspects, the UAV200may be configured to wait in the ocean while gathering energy from the sun and/or collecting ocean water. In aspects, the PV panel230may be connected to an energy storage element (e.g., a battery) from which energy may be drawn to power the UAV200. For example, an energy storage element (e.g., a battery) may be configured to power a motor (not shown) configured to drive a selected element of the UAV200(e.g., a propeller or roto-fan).

As noted above, the UAV system100may include fluid chamber240. In aspects, after a pre-determined amount of fluid120(e.g., seawater) is collected in the fluid chamber240, the UAV system100may enable the UAV200to transport the fluid120to a desired location (e.g., a house on fire). Thus, the fluid chamber240may be configured to host a fluid having salt (e.g., seawater). In further aspects, the fluid chamber240may be operably connected to the hydro cell700and/or the desalinator600and configured for receiving fresh water from the hydro cell700and/or the desalinator600.

In aspects, the UAV system may pump salt water (e.g., via the pump292of the UAV system100) to the hydro cell700and/or the desalinator600. For example, a fluid path (not shown) may be defined between the fluid chamber240, the desalinator600, and/or the hydro cell700. In aspects, the fluid path (not shown) may be a closed-loop path. In further aspects, the fluid chamber240can be configured to receive a fluid from the environment (e.g., from a lake, rainwater, or the ocean) prior to and/or post-processing of the fluid. For example, the fluid chamber240may be part of a closed-loop fluid path (not shown) in fluid communication with the external environment (e.g., the fluid chamber240may be configured to receive water from a lake and water leaving the desalinator600). In further aspects, the fluid chamber240may be configured to collect rainwater.

In aspects, the fluid chamber240may be disposed at a selected portion of the UAV200. For example, the fluid chamber240may be connected to lower portion204of the UAV200such that a user may be able to disconnect the fluid chamber240, or the fluid chamber240may be monolithically formed with the UAV200. In aspects, the fluid chamber240may be configured to collect and store a fluid (e.g., seawater) and may include a valve290in fluid communication with the fluid chamber240.

Generally, the valve290is configured for selective passing of the fluid therethrough and into the fluid chamber240.

In aspects, the UAV system100may include additional valves, e.g., valves to control fluid communication between elements mounted and/or monolithically formed in the UAV200(e.g., a valve may be disposed between the desalinator600and the fluid chamber240, when in fluid communication). In aspects, the fluid chamber240may be configured to include a selected shape (e.g., a bulbous plastic water container shaped like a buoy).

In aspects, the fluid chamber240may act as a buoy for the UAV200. In some aspects, the fluid chamber240and/or the valve290may be configured for collecting/releasing a selected fluid based on a selected determination. In another example, the UAV system may be configured to determine if the UAV200has arrived at a particular location (e.g., by comparing a GPS location of the UAV to the particular location). In aspects, the UAV system100may include a second fluid chamber291, which can be configured to receive a selected fluid. For example, the second fluid chamber291may be configured to receive desalinated water after ocean water has been desalinated via the desalinator600. In some aspects, the second fluid chamber291may be in fluid communication with the fluid path (not shown) noted above.

In aspects, the fluid chamber240may be configured to receive a selected fluid after desalination. For example, the fluid chamber240may be operably connected to the desalinator600such that the system100feeds salt-water to the desalinator600from the fluid chamber240. Generally, the desalinator600processes the salt-water by substantially removing the salt from the salt-water and ultimately generates energy, e.g., desalinator600may be configured as a sodium ion desalination battery, which may include a membrane.

After the salt-water or seawater is processed, the processed water may be removed from the UAV200and fed back into the body of salt-water (and/or stored in the second sub-chamber240b). Further, after the water is processed, the processed water can be fed to the hydro cell700from the desalinator600.

Turning now toFIG.4, a block diagram illustrating aspects of an exemplary controller (e.g., controller300) of UAV system100is shown. The controller300generally includes a processor310, memory320, a wireless network interface330, and a storage device340. The memory320may include instructions that, when executed by the controller300, may cause the UAV system100to execute the methods disclosed herein.

In various aspects, the memory320may include random access memory, read-only memory, magnetic disk memory, solid-state memory, optical disc memory, and/or another type of memory. In various aspects, the memory320can be separate from the controller300and can communicate with the processor310through communication buses of a circuit board and/or through communication cables such as serial ATA cables or other types of cables. The memory320includes computer-readable instructions that are executable by the controller300to operate the controller300.

In various aspects, the controller300may include a wireless network interface330to communicate with other computers or a server (not shown). In aspects, a storage device340may be used for storing data. In various aspects, the controller300may be, for example, without limitation, a digital signal processor, a microprocessor, an ASIC, a graphics processing unit (“GPU”), field-programmable gate array (“FPGA”), or a central processing unit (“CPU”).

Referring toFIG.5, a flow diagram for a method of fluid transport is shown as500.FIG.5shows a flow chart of an exemplary computer-implemented method500for location-based and fluid transportation in accordance with aspects of the present disclosure.

Although the steps ofFIG.5are shown in a particular order, the steps need not all be performed in the specified order, and certain steps can be performed in another order. For example,FIG.5will be described below with a server (not shown) performing the operations. However, in various aspects, the operations ofFIG.5may be performed all or in part by the controller300ofFIG.4. In aspects, the operations ofFIG.5may be performed all or in part by another device, for example, a mobile device and/or a client computer system (e.g., device110inFIGS.1and6). These variations are contemplated to be within the scope of the present disclosure.

Initially, at step502, the UAV200receives a first location to collect and/or release a fluid (e.g., fluid120), by a UAV200(FIG.2). The UAV200may be initially positioned in a body of salt-water (e.g., a bay). The UAV200may receive the first location via wireless communications. The first location may include, for example, a field to be irrigated and/or a location where a fire has broken out, and water is needed to put out the fire. As another example, the first location may be a flood zone from which fluid is to be collected, removed, and relocated. In aspects, the UAV200can remain in the body of water for a period of time and be used as a floating desalination plant.

Next, at step504, the controller300determines a fluid level within the fluid chamber240. In aspects, the controller300may compare the current fluid level to a stored pre-determined fluid level. For example, the pre-determined level may be any pre-determined threshold that can supply enough water for irrigation use.

Next, at step506, the UAV travels to the first location. In aspects, the UAV may collect solar energy (e.g., collection by a PV panel) and/or fluid (e.g., water) to generate electricity to be used by the UAV200. In aspects, the UAV may desalinate the fluid to generate electricity to power the UAV200and/or charge the UAV200to a pre-determined level of energy. The controller300may instruct the UAV200to deliver the fluid to the first location.

In further aspects, UAV200may receive a first location for collecting or releasing a selected fluid. For example, the controller300may determine a fluid level relative to a pre-determined fluid level for the selected fluid and fly to a location (e.g., a second location different from the first location). In aspects, the controller300may prepare the hydro cell700to produce electricity, determine if the UAV200is charged, and/or if the UAV200has enough power to fly to the location, prepare the UAV system100for fluid release, and deliver the fluid to the location.

In aspects, the controller300may receive a first voltage from the PV panel230(or a battery which may be connected to the photovoltaic panel230) to charge, or power, the hydro cell700and/or the UAV200and/or the desalinator600. Further, the controller300may determine if the hydro cell700has reached a pre-determined level of charge (e.g., if the UAV system100has enough power to desalinate salt-water, and/or if the UAV system100has enough power (or a selected voltage passing thereof) to produce hydrogen, or if the UAV system100has enough energy to fly the UAV200from a fluid collection location to a water delivering location).

In some aspects, the controller300may feed a fluid to the hydro cell700, determine if the fluid can be used to generate a current and/or if hydrogen can be separated (or extracted) from the fluid, process the fluid by splitting the fluid into hydrogen and oxygen-based on the determination, and store the hydrogen (e.g., in energy tank260). In various aspects, the controller300may determine collection of a fluid and/or determine salt in a fluid. In aspects, the controller300may energize the UAV200hydrogen stored in the energy tank260.

The controller300may determine fluid communication between a fluid source (e.g., a lake, the ocean, water chamber240) and the hydro cell700. The controller300may manipulate the valve290based on a fluid communication determination (e.g., open the valve, or leave the valve closed).

With reference toFIG.6, a system for energy transport600is shown. The system600may include UAV200and energy tank810configured for the transport and storage of energy. The energy tank810may be configured to store a gas and/or a liquid (e.g., hydrogen, natural gas, biofuels, and/or oil), or a power supply (e.g., a battery). The energy tank810may be a flexible chamber, which may be configured to maintain a pressurized payload. The energy tank810generally includes a less rigid material than the energy tank260(FIG.1), such as a polymer or other form of plastic. However, in aspects, the energy tank810may include more rigid materials such as metals hard plastics, and/or composites in order to maintain multiple types of payload (e.g., hydrogen and water).

The energy tank810may include a connection hookup812, a connection nozzle814, and a sensor816. The connection hookup812may be configured to connect the energy tank810to the UAV200. Generally, the connection hookup812includes a durable material, such as a metal or hard plastic, in order to support the payload of energy tank800. In aspects, the connection hookup812may be a hook that easily interlocks with UAV200(e.g., a heavy-duty lifting hook such as an eye hook, clevis hook, or swivel hook), such that UAV200may connect to connection hookup812while in motion or idling. Connection hookup812is not limited to hook connectors and various alternative removable and/or permanent connection methods may be employed (e.g., nozzles, screws, and/or soldering).

The connection nozzle814may be any form of gas or liquid bearing nozzle. For example, the connection nozzle814may be a natural gas connection nozzle, a diffusion nozzle, or a fueling nozzle. In various aspects, the connection nozzle may use male and female interlocking connectors to ensure compatibility with nozzle(s) at a collection and/or delivery site820. While the connection nozzle814is pictured in a tubular shape, various alternative shapes may be contemplated.

In aspects, the energy tank810may be connected to the lower portion204of the UAV200such that a user may be able to easily disconnect the energy tank800. In aspects, the energy tank810may be interchangeable with the fluid chamber240of the UAV.

In aspects, the energy tank810may be similar in shape and/or configuration to a gas holding tank, e.g., a spherical and/or bulbous design. In aspects, the spherical and/or bulbous design may aid the UAV200with buoyancy when the tank is resting in water. In aspects, the energy tank810may be a container of any kind or shape capable of storing energy.

In aspects, the UAV200may be configured to be stationary at a first location (e.g., waiting for instructions while floating in the ocean, similar to a buoy) prior to, during, or after energy collection (e.g., the UAV200may be configured to wait for a pre-determined event while sitting on the ocean or other body of water). For example, the UAV200may sit strategically for an indefinite period of time in a given location waiting for instructions. The UAV may be on stand-by while floating in the ocean, similar to a buoy.

In aspects, the energy tank810may be configured to store electrical energy (e.g., a high-voltage electrical charge). The energy tank810may include a conductive metal coating (e.g., metal foil, metal film, and/or two metal plates) on an inner surface and/or an outer surface of the energy tank, and an electrode (e.g., a metal rod and/or metal wire) electrically connected to the inner surface of the energy tank810to permit charging. The inner surface and the outer surface may store equal but opposite charges. In aspects, the connection nozzle814may be an electrical connector (e.g., a plug or other suitable electrical conduit) configured to create an electrical connection with the collection and/or delivery site820for receiving and/or delivering electrical energy.

Referring toFIG.7, a flow diagram for a computer-implemented method900of energy transport is shown. Although the steps ofFIG.7are shown in a particular order, the steps need not all be performed in the specified order, and certain steps can be performed in another order. For example,FIG.7will be described below with a server (not shown) performing the operations. However, in various aspects, the operations ofFIG.7may be performed all or in part by the controller300ofFIG.4. In aspects, the operations ofFIG.7may be performed all or in part by another device, for example, a mobile device and/or a client computer system (e.g., device110inFIGS.1and6). These variations are contemplated to be within the scope of the present disclosure.

Initially, at step902, the UAV200receives a first location to collect and/or release (i.e., deliver) energy (e.g., hydrogen, natural gas, biofuels, and/or oil). For example, the first location may be a power plant where hydrogen is ready for collection or a warehouse from which a battery is to be collected, removed, and/or relocated. In another example, the first location may be a building awaiting an energy delivery. In aspects, the UAV200may initially be positioned at a storage location, although any suitable location may be contemplated. The UAV200may then receive the first location via wireless communications (e.g., Bluetooth, Wi-Fi, or broadband) and/or an electronic order. In aspects, the UAV200may receive the first location from a remote server.

Next, at step904, the controller300determines an energy level within the energy tank800. In aspects, the energy level may be determined based on a reading from the sensor816. For example, the sensor816may send the controller300a current energy level within the energy tank800. In aspects, the controller300may compare the current energy level to a stored pre-determined energy level. For example, the pre-determined energy level may be any pre-determined threshold that can supply enough energy to power to a designated device at the first location (e.g., a pre-determined energy level required to power a specific machine or building). The pre-determined energy level may be determined prior to arrival at the first location via user instructions sent to controller300. In aspects, the pre-determined energy level may be determined upon arrival at the first location. For example, sensor816may scan a device to determine a level of energy required to charge a device at the first location.

Next, at step906, the controller300instructs the UAV200to travel to the first location to deliver and/or collect energy. In aspects, the UAV200may travel to a second location based on further instructions received from controller300. For example, the UAV200may deliver energy to the first location and then travel to the second location to collect additional energy for delivery back to the first location and/or delivery to a third location.

Referring toFIG.8, a flow diagram for a computer-implemented method1000of UAV logistics management is shown. Although the steps ofFIG.8are shown in a particular order, the steps need not all be performed in the specified order, and certain steps can be performed in another order. For example,FIG.8will be described below with a server (not shown) performing the operations. However, in various aspects, the operations ofFIG.8may be performed all or in part by the controller300ofFIG.4. In aspects, the operations ofFIG.8may be performed all or in part by another device, for example, a mobile device and/or a client computer system (e.g., device110inFIGS.1and6). These variations are contemplated to be within the scope of the present disclosure.

Initially, at step1002, the UAV200receives a first order and a second order. The first order and the second order may each include a location to deliver energy, fluid, and/or additional items by a UAV200(FIG.2). The UAV200may receive the first order and the second order via wireless communications and/or through an electronic order. The first order and second order may include, for example, requests to deliver energy to particular locations and/or individuals. In aspects, the first and/or second locations may be entered by a user (e.g., a customer) with GPS delivery coordinates either numerically and/or drawn on a geospatial tool, which may later be translated into coordinates.

Next, at step1004, the controller300determines a proximity of the location of the first order to the location of the second order. In aspects, the controller300may also translate the locations into delivery coordinates for the UAV200to use during navigation. For example, a pre-determined location drawn on a geospatial tool may translate to about 40.6106° N, about 73.4445° W (e.g., location data in the form of GPS coordinates).

Next, at step1006, the controller300transports the first order with the second order, based on the proximity of the location of the first order to the location of the second order. For example, the locations may be the same, and therefore both orders may be transported together. In aspects, the location of the second order may be at a second location in close proximity to the location of the first order, although transportation to the second location is not limited to close proximity to the first location. In aspects, the controller300may also transport orders together based on time received, such as orders placed and/or orders required to be delivered within a certain timeframe (e.g., within the same hour, day, and/or week).

In aspects, a logistics management system may be used for general global positioning of UAVs and automation of UAVs. Automation may be used to coordinate procurement points, delivery points, and scenarios for UAVs in the context of adverse conditions, in order to achieve logistical efficiency and protect physical assets (e.g., to protect UAV200against damage and/or delay due to rough oceans, hurricanes, or floods). In aspects, the logistics management system may include fleet management components. The fleet management components may manage UAVs, infrastructure, and markets within a territory. It is contemplated that the logistics management system may cover hundreds to thousands of UAVs within a single fleet.

In aspects, the logistics management system may be configured to address hourly and/or seasonal weather changes. For example, for hourly events (e.g., naturally occurring phenomenon causing adverse conditions, such as rough seas, storms, high winds, and other atmospheric conditions), the logistics management system will ensure that locations (e.g., collection and delivery points, and/or routes between the points) do not present adverse conditions.

In aspects, method1000may leverage artificial intelligence (“AI”) and/or various machine learning networks (e.g., convolutional neural networks and/or long-term short memory networks), to detect and/or predict the presence of adverse conditions. In aspects, the AI and/or machine learning networks may be leveraged by controller300for routing purposes. For example, the controller300may identify that a current route presents high winds that are too dangerous for UAV200to fly through and may reroute UAV200along a different path. In aspects, the AI and/or machine learnings networks may be trained using prior data from memory320and/or an external source (e.g., third party data or cloud storage).

In aspects, for seasonal events (e.g., the general changing of seasons causing changes in temperature, wind, and humidity), the logistics management system may ensure a gradual shift in UAV(s) service away from areas with less demand towards higher demand areas to optimize service offerings. For example, because wildfires may not occur as often in the winter, UAVs may be shifted biannually between hemispheres to avoid high presence during winter months. In aspects, gradual shifting may occur on a global scale, such that UAVs may avoid routing inefficient distances (e.g., avoid traveling across multiple states and/or countries within a short period of time). In aspects, the UAVs may be moved on demand based on user-entered parameters. For example, the UAVs may be routed to an area where a natural disaster recently occurred to provide needed fluid and energy resources.

In aspects, the fleet management components may include pairings of hemisphere territories for year-round management. For example, UAVs may only be needed during the spring and summer months for crop irrigation, and therefore will travel to designated locations of the northern hemisphere and southern hemisphere, respectively, for those seasons.

The fleet management components may include flexible territory boundaries within one or multiple regions. In aspects, the region(s) may be pre-determined (e.g., pre-programmed by a user). The flexible territory boundaries may include a pre-determined flux, which may be associated with hourly or seasonal events. For example, territories may expand in size during the winter season due to decreased demand (e.g., less UAVs are required to service demand in winter). In another example, territories may decrease during the summer season due to increased demand (e.g., more UAVs are required to service demand in summer). When territories decrease in size, additional UAVs may be employed, in order to cover the entirety of the original territory. In aspects, territory demand may be calculated based on demand per square mile and/or demand per square foot.

In aspects, the logistics management system includes UAV condition monitoring, routine UAV maintenance tracking, and/or sensor. For example, UAV condition monitoring may utilize sensor(s) (e.g., sensor816) to detect damage to UAVs. When damage is detected, the UAV logistics management system may send the damaged UAV for repair and reroute other UAVs to cover the damaged UAV's tasks and ensure continuity of service. In aspects, routine UAV maintenance tracking may include UAVs that are unavailable due to maintenance and reroute other UAVs to cover the unavailable UAV's tasks.

Certain aspects of the present disclosure may include some, all, or none of the above advantages and/or one or more other advantages readily apparent to those skilled in the art from the drawings, descriptions, and claims included herein. Moreover, while specific advantages have been enumerated above, the various aspects of the present disclosure may include all, some, or none of the enumerated advantages and/or other advantages not specifically enumerated above.

The aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For instance, although certain aspects herein are described as separate aspects, each of the aspects herein may be combined with one or more of the other aspects herein. Specific structural and functional details disclosed herein are not to be interpreted as limiting, but as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure. Like reference numerals may refer to similar or identical elements throughout the description of the figures.

The phrases “in an aspect,” “in aspects,” “in various aspects,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects in accordance with the present disclosure. A phrase in the form “A or B” means “(A), (B), or (A and B).” A phrase in the form “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).”

Any of the herein described methods, programs, algorithms, or codes may be converted to, or expressed in, a programming language or computer program. The terms “programming language” and “computer program,” as used herein, each include any language used to specify instructions to a computer, and include (but is not limited to) the following languages and their derivatives: Assembler, Basic, Batch files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, scripting languages, Visual Basic, metalanguages which themselves specify programs, and all first, second, third, fourth, fifth, or further generation computer languages. Also included are database and other data schemas, and any other meta-languages. No distinction is made between languages which are interpreted, compiled, or use both compiled and interpreted approaches. No distinction is made between compiled and source versions of a program. Thus, reference to a program, where the programming language could exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. Reference to a program may encompass the actual instructions and/or the intent of those instructions.

Is understood that the foregoing description is only illustrative of the present disclosure. Various alternatives and modifications can be devised by those skilled in the art without departing from the disclosure. Accordingly, the present disclosure is intended to embrace all such alternatives, modifications, and variances. The aspects described with reference to the figures are presented only to demonstrate certain examples of the present disclosure. Other aspects, elements, steps, methods, and techniques that are insubstantially different from those described above and/or in the appended claims are also intended to be within the scope of the present disclosure.