Patent Publication Number: US-2021179290-A1

Title: System for storing, autonomously launching and landing unmanned aerial vehicles

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application claims the benefit of and priority to U.S. Provisional Patent Application No. 62/948,764 filed Dec. 16, 2019 and entitled “SYSTEMS FOR STORING, AUTONOMOUSLY LAUNCHING AND LANDING UNMANNED AERIAL VEHICLES,” which is incorporated herein by reference in its entirety. 
    
    
     TECHNICAL FIELD 
     One or more embodiments of the present disclosure relate generally to unmanned aerial vehicles (UAVs) and more particularly, for example, to devices, systems and methods for storing, remotely launching, and controlling one or more UAVs. 
     BACKGROUND 
     In many military and civilian operations, it is often desirable to have personnel remain in positions where they are protected, such as the inside of a vehicle. The confinement of a vehicle, however, offers few possibilities to investigate areas of interest and limited situational awareness and overview. In many scenarios, it may be critical to increase situational awareness when confined to a vehicle, such as by use of a UAV. However, it may be difficult to launch a UAV without putting personnel at risk. In view of the foregoing, there is a continued need for improved systems and methods for launching, storing and controlling UAVs from mobile locations, such a vehicle. 
     SUMMARY 
     The present disclosure is directed to systems and methods for storing, launching and landing unmanned aerial vehicles (UAVs). Systems and methods disclosed herein include improved UAV and launch/land pad designs allowing for protected storage and remote launching and landing of UAVs in mobile scenarios. 
     In various embodiments, specialized launch systems and methods are provided to enable an operator to launch and operate one or more unmanned aerial vehicles (UAVs) from a safe location. A launch system comprises a launch device and an operator terminal. The launch device is configured to be mounted on an exterior surface of a mobile structure and is communicably coupled to the operator terminal, which may be operable from the interior of the mobile structure (e.g., inside an armored vehicle) or other protected location. The mobile launch system allows an operator to control one or more UAVs from inside the vehicle, without requiring the operator to step outside of the vehicle to interact with the UAV or launch device. In various embodiments, the UAV and the launch/land pad include articulating arms that fold for storage in a protective housing. An actuator controls the vertical positioning of the launch/land pad in the protective housing between a storage state and a launching/landing state. 
     The scope of the invention is defined by the claims, which are incorporated into this section by reference. A more complete understanding of embodiments of the disclosure will be afforded to those skilled in the art, as well as a realization of additional advantages thereof, by a consideration of the following detailed description of one or more embodiments. Reference will be made to the appended sheets of drawings that will first be described briefly. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIGS. 1A-B  illustrate example funnel concepts for launching/landing pads for unmanned aerial vehicles (UAVs), in accordance with embodiments of the disclosure. 
         FIGS. 2A-B  illustrate an example system for storing, launching and landing a UAV, in accordance with embodiments of the present disclosure. 
         FIGS. 3A-B  illustrate a UAV in a storage and launch/land state, in accordance with embodiments of the present disclosure. 
         FIGS. 4A-B  illustrate an example launching/landing unit in a storage and launch/land state, in accordance with embodiments of the present disclosure. 
         FIGS. 5A-B  illustrate an example launching/landing unit and protective housing in a storage and launch/land state, in accordance with embodiments of the present disclosure. 
         FIGS. 6A-B  illustrate an example vehicle launch system, in accordance with embodiments of the present disclosure. 
         FIG. 7  illustrates example components of a vehicle launch system, in accordance with embodiments of the present disclosure. 
         FIG. 8  illustrates electrical and processing components for a vehicle launch system, in accordance with embodiments of the present disclosure. 
         FIG. 9  illustrates a method for using a vehicle launch device, in accordance with one or more embodiments. 
     
    
    
     Embodiments of the disclosure and their advantages are best understood by referring to the detailed description that follows. It should be appreciated that like reference numerals are used to identify like elements illustrated in one or more of the figures. 
     DETAILED DESCRIPTION 
     Aspects of the present disclosure relate generally to systems and methods for launching, storing and controlling unmanned aerial vehicles (UAVs). In various embodiments, specialized vehicle launch systems and methods are provided to enable personnel to launch and operate one or more UAVs from the safety of a vehicle or other mobile location. In various embodiments, the UAV and launch/land pad are stored inside a protective structure and deployed by an actuator. 
     Unmanned Aerial Vehicles are increasingly autonomous, and the demand for fully automatic launch and landing capabilities are on the rise. Additionally, the demand for vehicle-based UAV systems further emphasize the need for smaller, more robust fully autonomous solutions that work in a multitude of environments. Vehicle systems may also need to function in motion and/or when the vehicle is inclined. Solutions currently on the market are typically very large and mechanically complex or completely lacking. One challenge is to move the UAV from a dynamic, flying state, affected by variations in wind and navigation conditions to one where it is constrained mechanically and connected electronically in a separate device (stationary or on a vehicle which may in turn be moving). The electrical connections typically require a degree of accuracy that must be met for a remote system to operate effectively in the field. The solutions disclosed herein address several of these problems. 
     Conventional UAV systems are designed with large, flat landing surfaces to facilitate landing of a UAV and the subsequent mechanical aligning of the UAV to the electrical infrastructure associated with the launch pad. These large landing surfaces consume valuable space on a vehicle or other mobile structure, limiting the number of UAVs that may be launched and the placement of the launching/landing structures on the vehicle. 
     Referring to  FIG. 1A  and  FIG. 1B , example funnel concepts are illustrated that facilitate self-centering and alignment of a UAV with an LLU that includes docking features. In these illustrated approaches, the UAV is shaped to self-center within a single funnel to account for inaccuracies. In  FIG. 1A , a system  100  includes a wide landing surface  102  allowing a UAV  104  to safely dock and connect electronics (e.g., at the center of the dock). In  FIG. 1B , a system  120  illustrates a landing surface  122 , which is the shape of a funnel for guiding a UAV  124  to land. Electrical connections  126  are provided at the bottom of the funnel to connect to the electrical system of the UAV  124  for charging and/or communications. 
     Referring to  FIGS. 2A and 2B , an example embodiment of an improved system for storing, launching and landing a UAV will now be described. A system  200  includes a housing  202  for storing and launching a UAV and a cover  204  to protect the UAV and internal components of the housing  202  during storage. In some embodiments, the housing  202  is a cylindrical tube or other shape for storing and launching a UAV as described herein. The cover  204  is connected to the housing  202  at a hinge  206 , which allows the cover to swing open and closed during operation. In some embodiments, the hinge  206  includes a spring or other bias to cause the cover to close over an opening of the housing  202  as illustrated in  FIG. 2A  when not in use. 
     As illustrated in  FIG. 2B , the system  200  includes a launching/landing state providing access to a landing platform  208 . In operation, an actuator (not shown) within the housing  202  is configured to selectively raise and lower the landing platform  208  to move between a protective storage state (as illustrated in  FIG. 2A ) to the launch/landing state illustrated in  FIG. 2B . The landing platform  208  includes a funnel shaped landing surface which allows a UAV  226  to position itself on the landing platform  208  to provide a charging and/or communication coupling between the UAV  226  and components of the landing platform  208 . The landing platform  208  further includes a plurality of articulating arms  222  that are rotatably attached around a perimeter of the landing platform  208 . As illustrated, the landing platform  208  includes hinges that bias the arms  222  outward away from the center of the landing platform  208  when the landing platform  208  in the launching/landing state. A foldable surface  220  is connected between the arms to extend the landing surface in the launching/landing state. 
     When the actuator is controlled to lower the landing platform, the landing platform  208  is lowered within the housing  202  to move the UAV  226  inside the housing  202  into a protective storage state. As the landing platform  208  is lowered, each of the arms  222  is folded into the housing  202  at its respective hinge  224  by the interior wall of the housing  202 . In addition, one or more of the mechanisms including the landing platform  208  and/or the arms  222  engage the cover  204  to open the cover  204  when in the launch and landing state. As the landing platform  208  is lowered, the pressure against the cover  204  is released and the cover  204  closes as the arms  222  are pulled inside the housing  202 . Thus, the system  200  includes a landing platform  208  that may be raised and lowered to change states from the protective storage state to the unfolded state for extending the landing platform size. In accordance with one or more embodiments, the LLU is shaped like a funnel to facilitate positioning of the UAV  226  in the center of the landing platform  208  for electrical connection with components of the housing  202  (e.g., power and/or communications). The UAV  226  is similarly shaped so that wherever it lands within the LLU funnel, it will self-center. This compensates for last second variations and inaccuracies. This method can be used with any type of airframe but lends itself particularly well to multirotor devices due to their symmetrical design. 
     Another example embodiment of a UAV will now be described with reference to  FIGS. 3A and 3B , which show a UAV  300  in a storage and launch state, respectively. The UAV  300  is fitted with articulated arms  302 , loaded with more force that its own weight can produce in flight. These arms fold upwards by use of an actuator in the LLU, which ensures a compact storage mode for the UAV. As illustrated, the UAV  300  includes a body  316  including hinges  320  for connecting the arms  302 . Each arm  302  has a first end connected to the body  316  through a corresponding hinge  320 , and a second end adapted to mount a motor  306  and rotor  304 . The body  316  may house control electronics, a memory, a gyroscope, a battery for powering the UAV during flight, a payload such as a camera for capturing image during flight, and communications components for receiving remote control instructions and/or communicating data between the drone and a host device. 
     In some embodiments, the UAV  300  is configured to land in the landing platform (e.g., the landing platform of  FIG. 2A-B ) and settle into the center of the funnel-shaped platform. The folding of the arms may be controlled through one or more mechanisms depending on the configuration. In one embodiment, the landing platform is configured to engage a member  310  of the UAV  300  and pull the UAV down as the landing platform descends into the housing. The arms  302  are then pushed and inside the housing up by the sides of the housing into the folded position illustrated in  FIG. 3A . As the landing platform is raised, the second end of the arms  302  clear the sides of the housing and the bias in the hinge  320  pushes the arms  302  out to the flight position as illustrated in  FIG. 3B . 
     Referring to  FIG. 4A  and  FIG. 4B , a corresponding LLU  400  in a storage state and launch/land state, respectively, will now be described in accordance with one or more embodiments. In one embodiment, the LLU  400  transforms its shape between a launch/land state and a storage state. As illustrated, a connector platform  440  with a flexible fabric  422  between an actuated set of arms  420  (e.g., similar to an upside-down umbrella) provides an extended launch platform. The launch/land-device forms a funnel when in the launch/land state ( FIG. 4B ). The arms  420  fold upward when in a storage state to reduce its footprint. In one embodiment, the UAV  410  stored on the platform will fold its arms  402  upwards along with the arms of the platform when it changes state. The platform  440  may be driven up and down inside a housing along one or more guides  450 , which may include a servo mechanism including a motor and one or more lead screws or rods for driving the platform up and down. In some embodiments, the platform  440  includes one or more side portions  442  that include a threaded portion that engages with the treads of a lead screw causing the platform  440  to move up and down when the lead screw is rotated. 
     Referring to  FIG. 5A  and  FIG. 5B , a cylindrical housing for storing the UAV and LLU is illustrated in a storage and launch/land state, respectively. As illustrated, the housing  500  includes a cylinder portion  505  for storing the UAV/LLU  510  in the storage state and a top portion  512  above which the landing funnel extends in the land/launch state to increase the landing area. A landing platform  504  is configured to fit within the housing  500  and includes one or more side portions  506  adapted to engage a threaded lead screw  508 , shaft or rod to enable the landing platform to travel up and down the cylinder portion  505 . 
     In one embodiment, the platform is positioned within the cylinder with a linear actuator that moves the platform vertically in the cylinder. This has the effect of moving the platform higher up from the ground level when in use. In some embodiments, a pack of several cylinders placed tightly together without obstructing each other are provided to allow for storage and launching of multiple UAVs. When in the launch/land state, the active platform is raised above the others and may be as wide as desired. On a vehicle with limited real estate, this can be very valuable. The cylinders may be attached to the sides of a vehicle or slotted into it, so that they do not raise the vehicles profile when in storage state. The platform is only present in the moment of launch or landing and otherwise safely stored. The UAV may be pulled downward by a gripping mechanism in the raising platform. This could be a separate mechanism, or a latching element at the end of the actuator and/or platform. 
     Various embodiments of a vehicle launch system will now be described with reference to  FIGS. 6A and 6B . The vehicle launch system comprises a launch box  600  (also referred to herein as a launch device) and an operator terminal  660 . The launch box  600  is adapted to be mounted on an exterior surface of a vehicle  650 , such as a ground vehicle, water vehicle or other mobile structure. In various embodiments, the launch box  600  may be mounted to another device or structure and/or be operated as a standalone unit. The operator terminal  660  is a mobile computing device communicably coupled to the launch box  600  and operable from the interior of the vehicle  650  or another protected location. The vehicle launch system allows an operator to control one or more UAVs (such as UAV  620 ) and launch the UAV  620  from inside the vehicle  650 , without requiring the operator to step outside of the vehicle  650  to interact with the UAV  620  or launch box  600 . 
     In the illustrated embodiment, a launch box  600  comprises a plurality of LLUs  610 , each adapted to securely store a single UAV  620  in its enclosure. Each UAV  620  is positioned in the LLU in a secure position on the launch/land pad. The LLU  610  is further adapted to move the UAV  620  from a storage position inside the LLU  610  to a launch position by an actuator attached to the launch/landing platform to move the UAV  620  such that it is positioned outside of the LLU housing for launch. In some embodiments, each LLU  610  is adapted to be easily removed and replaced with another LLU  610 , which may include another UAV  620 . 
     The launch platform  630  comprises charging points for charging the UAV  620  while it is in the LLU  610 . The launch platform  630  may further include a release mechanism to hold the UAV  620  on the launch platform  630  while in the storage position, and release the UAV  620  during launch (e.g., when the UAV  620  is positioned in a launch position). The launch platform  630  may also couple the UAV  620  to an operator terminal  660  for communications through a communications link. In various embodiments, the LLU  610  comprises one or more connectors configured to mate with a corresponding connector of the launch box  600  connecting the LLU  610  to a power supply, such as a power supply of the vehicle  650 , the operator terminal  660 , an internal battery, or other power source. When the UAV  620  is positioned on the launch platform  630 , the UAV  620  may be charged. In various embodiments, there may be additional connections enabling communication between the UAV  620  and the operating terminal  660 , including wireless and wired communications links. In some embodiments, the launch box  600  comprises electronics for communicating with and controlling the UAV  620 . For example, the release mechanism may be adapted to close (e.g., hold the UAV  620  on the platform) in response to a “close” instruction or command received from the operator terminal  660  through the launch box  600 , and open (e.g., release the UAV  620 ) in response to an “open” instruction or command received from the operator terminal  660  through the launch box  600 . 
     In various embodiments, the launch box  600  is further adapted to protect the UAV  620  from weather conditions. For example, the launch box  600  may comprise one or more components for cooling the inside of the launch box, such as a cooling fan. The launch box  600  may further comprise components, such as heating wires, for heating the interior and/or exterior walls of the launch box  600  to facilitate the removable of snow and ice. 
     During operation, the UAV  620  is maintained in a storage position, protected from the environment, charged and ready for operation. When the operator provides an instruction from the operator terminal  660 , the actuator  634  activates, moving the UAV  620  from the storage position to the launch position. The UAV  620  starts on instruction from the operator terminal  660 , and provides enough thrust to climb, the release mechanism on the platform  630  opens and the UAV  620  is launched to investigate the area of interest. In various embodiments, the flight path and control of the UAV  620  may be preprogrammed, programmed by the operator terminal  660  (e.g., while the UAV  620  is engaged with the launch platform  630 ), or controlled during flight by flight controls on the operator terminal  660 . In some embodiments, the UAV  620  ends the flight by landing in the extended landing area  640  and returning to the storage position in the LLU  610 . Flight data such as images and video captured during flight may be downloaded from the UAV  620  to the operator terminal  660  through a communications link. 
     Referring to  FIG. 7 , an embodiment of a vehicle launch box will described. In various embodiments, the launch box  700  may be used in civilian settings, military settings and other environments, and may be adapted to fit vehicles including ground vehicles such as consumer automobiles and military vehicles, such as battle tanks, and water vehicles. In one embodiment, the launch box  700  may be mounted (e.g., bolted at connector points designated in the bottom of launch box) to the outside of a vehicle in a position such that actuation of the LLU and launch of the UAV is unobstructed. In one embodiment, the launch box is adapted to fit one or more UAVs, which may include single rotor, quadcopters, and other types of UAV/drones. Although the illustrated embodiment includes four LLUs  710 , other numbers of LLUs may be utilized consistent with the present disclosure. In various embodiments, the LLUs  710  can be inserted and/or removed from one or more launch boxes. The UAVs (not shown) may be loaded or removed from one or more LLUs before or after insertion of the LLU into a launch box. Power to the launch box  700  may be supplied by the vehicle power supply, by an internal battery unit or through another available power source. 
     The launch box  700  may be remotely controlled by the operator positioned in the vehicle, which may facilitate wired communications between an operator terminal and the launch box  700 . An antenna positioned at the back of the box may be provided for wireless transmission to/from the operating UAV and/or operator terminal. Connectors  720  disposed on the back of the launch box connect the electrical components  760  of the launch box  700  to the operator control unit, a power supply, environmental sensors and other communications links. 
     Each LLU  710  comprises a housing  712  having an exterior adapted to fit securly in a cavity (or recess) of a launch box structure  714 , and an interior adapted to house the UAV, launch/land platform  732 , extended platform elements  730  (e.g., articulating arms and flexible fabric in a folded position as illustrated), and components that enable movement of the UAV between the storage position and launch position as described herein. In the storage position, the lid  718  is closed, and the UAV is held on the launch/land platform  732 . In some embodiments, the launch/land platform  732  is a structure adapted to securely hold the UAV, and includes a release mechanism including release arms adapted to hold the UAV when engaged, and release the UAV when the release arms are opened (e.g., using a solenoid, micro actuator, or mechanical release assembly). The launch/land platform  732  is coupled to an actuator assembly that includes a motor  734  and a lead screw  736 . In the illustrated embodiment, the actuator assembly comprises a lead screw step motor (e.g., servo motor  734 ) which is mounted to the housing  712  at a first end. The rotation of the lead screw  736  causes the launch/land platform  732  to traverse the lead screw  736  when activated via the connectors  720  causing the lid  718  to open and the UAV to move into a launch position. As illustrated, the lead screw step motor (DC) causes the screw  736  to open the lid  718  and position the launch/land platform  732 , including the extended platform elements  730  for launch. 
     While in the storage position, the UAV is charged by a power supply coupled to the UAV through the launch/land platform  732  and the connectors  720 . In one embodiment, the bottom of the funnell structure includes charging contacts to engage with corresponding charging contacts on the UAV. In other embodiments, the launch platform may include an inductive charging pad, a connector or other mechanisms to facilitating charging of the UAV. In the launch position the UAV may continue to be charged and is also available for operator control, including instructions to launch the UAV. The actuator assembly (e.g., motor  734  and lead screw  736 ), when operated, opens and/or closes the lid  718  and positions the launch/land platform  732  in the launch position. The actuator assembly may be calibrated/tested to get correct distances between various states. In various embodiments, the launch box  700  may include one or more weather proofing components, such as heating wires and/or a cooling fan. 
     In various embodiments, the operator may instruct the UAV to launch and engage in a flight mission under operator control through the operator terminal or through a preprogrammed flight scenario. The UAV may return to the launch box  700  and land on the extended landing platform. The release arms may close when the UAV is in landing platform securely holding the UAV in place. The motor  734  may then be instructed to lower the platform  732 , which causes the lid  718  to close, and the launch/land platform  732  to move into the storage position until the next flight. While stored in the LLU  710 , the UAV can recharge. In some embodiments, the UAV may communicate with the launch box  700  and/or operator terminal to download flight information, including acquired images, through the connector  720 . 
       FIG. 8  illustrates electrical and processing components for a vehicle launch system in accordance with various embodiments of the present disclosure. A system  800  includes launch box electrical components  810  and an operator terminal  850 . The launch box electrical components  810  facilitate the operation of the launch box, including storing, charging, releasing, launching and communicating with UAVs in the LLUs. In various embodiments, the launch box electrical components  810  includes a controller  812 , power supply  814 , LLUs  816  having electrical components coupled with the launch box electrical components  810 , communications components  822 , optional sensors  818  and optional temperature controls  820 . 
     The controller  812  may be implemented as one or more microprocessors, microcontrollers, application specific integrated circuits (ASICs), programmable logic devices (PLDs) (e.g., field programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), field programmable systems on a chip (FPSCs), or other types of programmable devices), or other processing devices used to control the operations of the launch box. Power supply  814  may be implemented, for example, as one or more batteries and/or power connections to permit use of the launch box and charging of UAVs coupled thereto. In some emboidments, the power supply  814  is coupled to a vehicle power supply, which provides electrical power to the launch box. 
     Communications components may include wired and wireless interfaces. Wired interfaces may include communications links with the operator terminal  850  and the vehicle, and may be implemented as one or more physical network or device connect interfaces. Wireless interfaces may be implemented as one or more WiFi, Bluetooth, cellular, infrared, radio, and/or other types of network interfaces for wireless communications, and may facilitate communications with the operator terminal, vehicle, UAVs and other wireless device. In some embodiments, the communications components  822  include an antenna for communications with a UAV during flights. 
     In various embodiments, the controller  812  is operable to provide control signals to each of a plurality of LLUs  816  of the launch box (e.g., through a connector interface coupling the LLU electrical components to the launch box electrical components  810 ). In various embodiments, the controller  812  provides control signals to a LLU  816  to provide actuator/platform  830  control (e.g., to move to a storage position or launch position; to close or open release arms). LLU communications components  832  provide communications between the controller  812  and connected UAV. In various embodiments, the controller  812  facilitates communications between the operator terminal  850  and UAVs stored in the LLUs. The launch box electrical components  810  may also include optional temperature controls  820  for controlling heating and cooling components if implemented in the launch box. Optional sensors  818  may be provided for additional environmental feedback. 
     The operator terminal  850  is operable to communicate with and control the operation of the launch box. The operator terminal  850  includes a processor  860 , a memory  870 , a display  880 , user input/output components  890  and communications components  892 . The processor  860  may be implemented as one or more microprocessors, microcontrollers, application specific integrated circuits (ASICs), programmable logic devices (PLDs) (e.g., field programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), field programmable systems on a chip (FPSCs), or other types of programmable devices), or other processing devices used to control the operator terminal. In this regard, processor  860  may execute machine readable instructions (e.g., software, firmware, or other instructions) stored in memory  870 . 
     Memory  870  may be implemented as a machine readable medium storing various machine readable instructions and data. For example, in some embodiments, memory  870  may store an operating system and one or more applications as machine readable instructions that may be read and executed by processor  860  to perform various operations described herein. In some embodiments, memory  870  may be implemented as non-volatile memory (e.g., flash memory, hard drive, solid state drive, or other non-transitory machine readable mediums), volatile memory, or combinations thereof. 
     The memory  870  includes a UAV interface  872  and a launch box interface  874 . The launch box interface  874  includes status, configuration and control features which may include all control features disclosed herein. For example, the launch box interface  874  may include identification of LLUs and UAVs coupled to the launch box, storage/launch status and control, UAV charging status and flight planning, control and information. The UAV interface  872  facilitates communications with the UAV before, during and after flight and may include flight controls for controlling the UAV during flight, and an interface for downloading and storing images and other data obtained by the UAV during flight. 
     Communications components  892  may include wired and wireless interfaces. A wired interface may be implemented as one or more physical network or device connection interfaces (e.g., Ethernet, and/or other protocols) configured to connect the operator terminal  850  with the launch box electrical components  810 . Wireless interfaces may be implemented as one or more WiFi, Bluetooth, cellular, infrared, radio, and/or other types of network interfaces for wireless communications. In some embodiments, the operator terminal  850  includes wireless interfaces for communicating with the launch box and for direct communications with one or more UAVs. 
     Display  880  presents information to the user of operator terminal  850 . In various embodiments, display  880  may be implemented as a liquid crystal display (LCD), an organic light emitting diode (OLED) display, and/or any other appropriate display. User input/output components  890  receive user input to operate features of the operator terminal  850 , and may include flight controls for one or more UAVs. 
     Referring to  FIG. 9 , a method  900  for using a vehicle launch device will now be described in accordance with one or more embodiments. In step  902 , a launch box is mounted on an exterior surface of a vehicle, such as the roof of a military vehicle. In some embodiments, the launch box is wired to receive power from the vehicle power supply and for communications with an operator terminal located on the interior of the vehicle. In step  904 , a plurality of LLUs are inserted into the launch box. Each LLU may include a UAV in a stored position. In some embodiments, the launch box may be adapted to hold 4-6 LLUs. When the LLUs are inserted, the UAV is electrically coupled to the launch box and the launch box may provide associted configuration data to the operator terminal in step  906 . The configuration data may include an identification of the LLUs and UAVs loaded into the launch box and a current status of the UAVs such as percentage charged and current flight plan. In step  908 , the operator terminal is used to prepare one or more UAVs for flight, including charging the UAV and configuring the UAV for its next mission. 
     In step  910 , the operator terminal (which is located on the interior of the vehicle) transmits instructions to the launch box to prepare one or more UAVs for launch, and the launch box instructs the launch mechanisms of the corresponding LLUs to move from the storage position to a launch position. In step  912 , one or more UAV(s) are released from the platform and launched for flight as instructed by the operator terminal. During flight, the operator may control and/or monitor the UAV(s) using the operator terminal in step  914 . In step  916 , each UAV returns to the platform and the launch box returns the UAV to the storage position for protection, charging and communication with the operator terminal. In step  918 , the UAV may download flight data and other acquired information to the operator terminal. 
     Where applicable, various embodiments provided by the present disclosure can be implemented using hardware, software, or combinations of hardware and software. Also, where applicable, the various hardware components and/or software components set forth herein can be combined into composite components comprising software, hardware, and/or both without departing from the spirit of the present disclosure. Where applicable, the various hardware components and/or software components set forth herein can be separated into sub-components comprising software, hardware, or both without departing from the spirit of the present disclosure. In addition, where applicable, it is contemplated that software components can be implemented as hardware components, and vice-versa. 
     Software in accordance with the present disclosure, such as non-transitory instructions, program code, and/or data, can be stored on one or more non-transitory machine-readable mediums. It is also contemplated that software identified herein can be implemented using one or more general purpose or specific purpose computers and/or computer systems, networked and/or otherwise. Where applicable, the ordering of various steps described herein can be changed, combined into composite steps, and/or separated into sub-steps to provide features described herein. 
     Embodiments described above illustrate but do not limit the invention. It should also be understood that numerous modifications and variations are possible in accordance with the principles of the invention. Accordingly, the scope of the invention is defined only by the following claims.