Movable mounting structure for a drone

Abstract

Example movable mounting structures and methods are described. In one embodiment, an unmanned aerial vehicle (UAV) includes a body and a movable mounting structure coupled to the body. The movable mounting structure is movable between a stowed position and a deployed position without interfering with a payload carried by the UAV. A camera is mounted to the movable mounting structure.

Description

Technical Field

[0001] This disclosure relates to a movable mounting structure for an unmanned aerial vehicle (UAV) and a system for controlling the movement of said mounting structure. Background Technology

[0002] Landing an unmanned aerial vehicle (UAV) in a specific location can be difficult. A precise landing site can be hampered by turbulence generated by the air expelled from the UAV's propellers and reflected off the landing surface. Cameras mounted on the UAV can assist in landing by capturing images of the landing location. These images are used to maneuver the UAV and keep it aligned with the desired landing position. For optimal image capture, cameras are typically positioned on the bottom of the UAV, with their field of view directly below the UAV. However, this can compromise the camera's ability to capture images of the landing area, as objects carried by the UAV may obstruct the view. Additionally, cameras mounted below the UAV can interfere with the loading and unloading of objects carried by the UAV. Summary of the Invention

[0003] An unmanned aerial vehicle (UAV) includes a fuselage and a movable mounting structure attached to the fuselage. The movable mounting structure is movable between a stowed position and an extended position. Moving the movable mounting structure between the stowed and extended positions does not interfere with the payload carried by the UAV. Additionally, a camera is mounted to the movable mounting structure. Attached Figure Description

[0004] Non-limiting and non-exhaustive embodiments of this disclosure are described with reference to the following accompanying drawings, wherein, unless otherwise specified, the same reference numerals refer to the same parts in the various drawings.

[0005] Figure 1 It is a block diagram depicting an environment in which exemplary embodiments may be implemented.

[0006] Figure 2 An embodiment of a UAV is shown, in which the movable mounting structure is in the deployed position.

[0007] Figure 3 An embodiment of a UAV is shown, wherein the movable mounting structure is in a stowed position.

[0008] Figure 4 An embodiment of a UAV is shown, wherein the movable mounting structure is located between the unfolded position and the retracted position.

[0009] Figure 5 This is a block diagram illustrating an embodiment of a drone.

[0010] Figure 6This is a block diagram illustrating an embodiment of a UAV management system.

[0011] Figure 7 This is a flowchart illustrating an embodiment of a method for operating a UAV and adjusting a movable mounting structure associated with the UAV.

[0012] Figure 8 This is a flowchart illustrating an embodiment of a method for controlling the position of a movable mounting structure associated with the UAV to monitor a specific area. Detailed Implementation

[0013] In the following disclosure, reference is made to the accompanying drawings, which form part of this disclosure and illustrate specific embodiments through which the disclosure can be practiced. It should be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of this disclosure. Embodiments described by reference to "an embodiment," "an example embodiment," etc., in the specification may include specific features, structures, or characteristics, but each embodiment may not necessarily include said specific features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a specific feature, structure, or characteristic is described in connection with an embodiment, whether or not it is explicitly described, it is believed that implementing such a feature, structure, or characteristic in conjunction with other embodiments is still within the knowledge of those skilled in the art.

[0014] Embodiments of the systems, apparatus, and methods disclosed herein may include or utilize dedicated or general-purpose computers, including computer hardware such as, for example, one or more processors and system memories, as discussed herein. Embodiments within the scope of this disclosure may also include physical and other computer-readable media for carrying or storing computer-executable instructions and / or data structures. Such computer-readable media may be any available media accessible by a general-purpose or dedicated computer system. A computer-readable medium storing computer-executable instructions is a computer storage medium (device). A computer-readable medium carrying computer-executable instructions is a transmission medium. Therefore, by way of example and not limitation, embodiments of this disclosure may include at least two distinct types of computer-readable media: a computer storage medium (device) and a transmission medium.

[0015] Computer storage media (devices) include: RAM, ROM, EEPROM, CD-ROM, solid-state drive (“SSD”) (e.g., RAM-based), flash memory, phase-change memory (“PCM”), other types of memory, other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of computer-executable instructions or data structures and that can be accessed by a general-purpose or special-purpose computer.

[0016] Implementations of the apparatus, systems, and methods disclosed herein can communicate via computer networks. A “network” is defined as one or more data links capable of transmitting electronic data between computer systems and / or modules and / or other electronic devices. When information is transmitted or provided to a computer via a network or another communication connection (hardwired, wireless, or a combination of hardwired and wireless), the computer appropriately considers the connection as a transmission medium. The transmission medium may include networks and / or data links, which can be used to carry desired program code in the form of computer-executable instructions or data structures and are accessible by general-purpose or special-purpose computers. Combinations of the above should also be included within the scope of computer-readable media.

[0017] For example, computer-executable instructions include instructions and data that, when executed at a processor, cause a general-purpose computer, special-purpose computer, or special-purpose processing device to perform a function or a set of functions. For example, computer-executable instructions can be binary files, intermediate format instructions such as assembly language, or even source code. Although the subject matter is described in language specific to structural features and / or methodological behavior, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or actions. Rather, the described features and actions are disclosed as exemplary forms for implementing the claims.

[0018] Those skilled in the art will understand that this disclosure can be practiced in networked computing environments using many types of computer system configurations, including personal computers, desktop computers, laptop computers, message processors, handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframes, mobile phones, PDAs, tablets, pagers, routers, switches, various storage devices, etc. This disclosure can also be practiced in distributed system environments where both local and remote computer systems perform tasks, linked by a network (via a hardwired data link, a wireless data link, or a combination of hardwired and wireless data links). In a distributed computing environment, program modules can reside on both local and remote memory storage devices.

[0019] Furthermore, where appropriate, the functions described herein can be performed using one or more of the following: hardware, software, firmware, digital components, or analog components. For example, one or more application-specific integrated circuits (ASICs) can be programmed to perform one or more of the systems and programs described herein. Certain terms are used throughout the specification and claims to refer to specific system components. As those skilled in the art will understand, different names may be used to refer to components. This document is not intended to distinguish between components with different names rather than different functions.

[0020] It should be noted that the sensor embodiments discussed herein may include computer hardware, software, firmware, or any combination thereof to perform at least a portion of their functions. For example, a sensor may include computer code configured to execute in one or more processors and may include hardware logic / circuit controlled by the computer code. These example devices are provided herein for illustrative purposes and are not intended to be limiting. As those skilled in the art will appreciate, embodiments of this disclosure may be implemented in other types of devices.

[0021] At least some embodiments of this disclosure relate to computer program products that include such logic (e.g., in software form) stored on any computer-usable medium. When such software is executed in one or more data processing devices, it causes the devices to operate as described herein.

[0022] Figure 1 This is a block diagram depicting an environment 100 in which exemplary embodiments may be implemented. An unmanned aerial vehicle (UAV) 102 may land on and take off from a landing platform 104 or any other landing surface, landing area, landing location, etc. In some embodiments, the landing platform 104 is mounted to a vehicle (e.g., mounted on top of a vehicle), a building, a loading dock, a loading platform, or any other device or structure. The UAV 102 may be any type of unmanned aerial vehicle capable of being maneuvered to land on and take off from any type of landing platform or landing area. In some embodiments, the UAV 102 is a multi-rotor helicopter with two or more rotors (e.g., motors) and associated propellers. In a particular embodiment, the UAV 102 has a single rotor and associated propeller. The UAV 102 may also be referred to as an unmanned aerial vehicle or a remotely piloted aircraft. In some embodiments, the landing platform 104 provides a temporary location for the UAV 102 to land and receive payloads, deliver payloads, recharge, "carry" on a vehicle, etc.

[0023] like Figure 1As shown, the UAV management system 108 is capable of wireless communication with the UAV 102. Communication between the UAV management system 108 and the UAV 102 can be performed using any communication protocol, such as 3G, 4G LTE, WiFi, etc. In some embodiments, the UAV management system 108 provides flight guidance to the UAV 102 when landing on or taking off from the landing platform 104. In some embodiments, the UAV management system 108 communicates with the server 110 via a data communication network 112. For example, the UAV management system 108 can transmit data associated with the UAV 102, payload, etc., to the server 110. Additionally, the UAV management system 108 can receive data associated with the UAV 102, payload delivery instructions, etc., from the server 110. Other types of data received by the UAV management system 108 may include calculated flight paths of the UAV 102, temporary flight restrictions, airspace flight restrictions, and local models of obstacles near or along the delivery path of the UAV 102. The data communication network 112 includes any type of network topology using any communication protocol. Additionally, the data communication network 112 may include a combination of two or more communication networks. In some embodiments, the data communication network 112 includes a cellular communication network, the Internet, a local area network, a wide area network, or any other communication network.

[0024] It should be understood that Figure 1 The embodiments shown are given by way of example only. Other embodiments may include fewer or additional components without departing from the scope of this disclosure. Furthermore, the components shown may be combined with or included within other components without limitation.

[0025] Figure 2 An embodiment of UAV 102 is shown, wherein the movable mounting structure 208 is in the deployed position. Figure 2 The example shown only shows a portion of UAV 102. Now in Figure 2 Some parts of UAV 102 are shown to improve the illustration and explanation of specific components or structures associated with the movable mounting structure 208. For example, Figure 2 Certain housing components and other structures are not shown because they may obstruct the visibility of the movable mounting structure 208 and its mounting and moving parts. As discussed herein, the movable mounting structure 208 can be deployed in an extended position (e.g., Figure 2 (as shown) and the collapsible position (as shown) Figure 3The movable mounting structure 208 can be moved (e.g., rotated) between the extended and retracted positions. The extended position may also be referred to as the "stretched position," and the retracted position may also be referred to as the "retracted position." In some embodiments, the rotation difference between the extended and retracted positions is approximately 90 degrees. In other embodiments, the movable mounting structure 208 can be configured to rotate through any range, including rotations greater than 90 degrees or less than 90 degrees. In some embodiments, the mounting structure 208 is made of any stable plastic (e.g., ABS or PVA) or of a fiber / resin material (such as glass fiber or carbon fiber). In other embodiments, a metal such as aluminum can be used to manufacture the mounting structure 208.

[0026] UAV 102 includes multiple outriggers 202 supporting UAV 102 on a landing platform or other landing surface. One or more fuselage components (also referred to as “structural components”) (such as mounting plates 204 and 206) support various components, devices, and / or systems associated with UAV 102. In other embodiments, mounting plates 204, 206 may be replaced with different types of fuselage components or support structures (such as chassis, fuselage structural components, etc.). Specific embodiments of UAV 102 may include any number of mounting plates 204, 206 and other mounting structures, mounting platforms, support structures, housings, etc. As described above, a movable mounting structure 208 is mounted to UAV 102 such that the movable mounting structure 208 can be in an deployed position (e.g., Figure 2 (as shown) and the collapsible position (as shown) Figure 3 The movable mounting structure 208 is mounted to the UAV 102 at a pivot point 212 adjacent to the motor 216. Corresponding pivot points are located on opposite sides of the UAV 102, where the opposite side of the movable mounting structure 208 is pivotally attached to the mounting plate 206. Operation of the motor 216 causes rotation of a motor drive shaft connected to the movable mounting structure 208 at pivot point 212. Rotation of the motor drive shaft causes movement (e.g., rotation) of the movable mounting structure 208. In some embodiments, the motor 216 may include a servo motor, a stepper motor, a geared DC motor with an encoder, etc.

[0027] Camera 210 is attached to movable mounting structure 208, such as Figure 2 As shown. Camera 210 includes any type of camera, such as an RGB (red, green, blue) camera, an IR (infrared) camera, etc. When the movable mounting structure 208 is in Figure 2 When in the deployed position, camera 210 faces downwards and captures images of the area beneath UAV 102. This orientation is particularly useful during UAV 102 landing or takeoff, as it provides images of the landing area and allows UAV 102 to land in the desired location. As the movable mounting structure 208 moves from the deployed position to the retracted position... Figure 3 The field of view of camera 210 changes based on the varying rotation angle of movable mounting structure 208. In some embodiments, the legs 202 of UAV 102 are long enough that camera 210 does not contact the landing surface (or landing platform) when movable mounting structure 208 is in the deployed position.

[0028] like Figure 2 As shown, UAV 102 includes multiple payload support structures 214 (e.g., rack and pinion grippers) that can be attached to and / or grip a payload object (not shown), allowing UAV 102 to transport the payload object to another location. The area where the payload object is secured by UAV 102 can be referred to as the "payload area". A movable mounting structure 208 moves between an extended position and a retracted position without entering or interfering with the payload area associated with UAV 102. Figure 2 As shown, the movable mounting structure 208 partially surrounds the payload area associated with the UAV 102. Therefore, the movable mounting structure 208 can move between an extended position and a retracted position without contacting the payload carried by the UAV 102.

[0029] In some embodiments, when the UAV 102 lands, the movable mounting structure 208 is in the position as follows: Figure 2 The image shows the deployed position. In this position, camera 210 provides an image of the landing area, which allows UAV 102 to successfully maneuver and land at the desired location. After UAV 102 lands in the landing area, the movable mounting structure 208 is moved to the retracted position, which allows access to the bottom of UAV 102 for loading / unloading payloads, connecting to the charging system, etc. Since UAV 102 has landed, camera 210 is no longer needed, and the movable mounting structure 208 is moved to the retracted position to avoid interfering with UAV activities. After servicing UAV 102 (loading / unloading payloads, connecting to the charging system, etc.) is completed, the movable mounting structure 208 is moved back to the deployed position so that camera 210 is in place to capture images when UAV 102 takes off from the landing area. As described herein, the movable mounting structure 208 has a shape and position that does not contact any payload mounted to UAV 102 when the movable mounting structure 208 moves between the deployed and retracted positions.

[0030] Figure 3An embodiment of UAV 102 is shown, wherein the removable mounting structure 208 is in a retracted position. As discussed herein, with the removable mounting structure 208 in the retracted position, the bottom of UAV 102 can be accessed for loading payloads, unloading payloads, connecting a charging system to charge one or more batteries in UAV 102, etc.

[0031] Figure 4 An embodiment of UAV 102 is shown, wherein the movable mounting structure 208 is rotated between an deployed position and a retracted position. The movable mounting structure 208 can be moved to any point between the deployed and retracted positions (e.g., any rotation angle). This is achieved by stopping the operation of motor 216 at the desired point. Additionally, the position of the movable mounting structure 208 can be adjusted during the flight of UAV 102, for example, to adjust the image captured by camera 210. In some embodiments, UAV 102 can capture images of a specific area while in flight. As the position of UAV 102 changes (e.g., lateral position, altitude, etc.), the position of the movable mounting structure 208 is adjusted to keep camera 210 focused on the specific area. Additionally, the axis of UAV 102 can be changed to adjust the orientation (or field of view) of camera 210. In certain embodiments, UAV management system 108 and / or control systems within UAV 102 can operate independently or jointly to position UAV 102 and movable mounting structure 208 such that camera 210 remains focused on the specific area.

[0032] Figures 2 to 4 The UAV 102 shown is one example including a movable mounting structure 208. In other embodiments, the movable mounting structure 208 can have any shape, be mounted at any location on the UAV 102, move in any direction using any number of pivot points, etc. For example, the movable mounting structure 208 can have an "L" shape instead of... Figures 2 to 4 The “U” shape is shown. In some embodiments, the movable mounting structure 208 may have two separate “L”-shaped structures, each pivoting independently and driven by a separate motor 216. In other examples, the movable mounting structure 208 may swing outward from the payload region rather than rotating around it. In some embodiments, the orientation of the payload support structure 214 may be rotated from the position shown, such as by 90 degrees. In a particular embodiment, the camera 210 may be integrated into a portion of the payload support structure 214 (e.g., one of the claws or arms of the payload support structure 214).

[0033] exist Figures 2 to 4In the example, camera 210 is mounted to movable mounting structure 208. However, in alternative embodiments, any type of sensor or other device may be attached to movable mounting structure 208. For example, a lidar (light detection and ranging) sensor, a radar (radio detection and ranging) sensor, an ultrasonic sensor, or an IR (infrared) array may be mounted to movable mounting structure 208. In some embodiments, any number of devices (such as camera 210 and one or more other sensors) may be attached to movable mounting structure 208. In certain embodiments, one or more of a microphone, microphone array, RFID (radio frequency identification) scanner, NFC (near field communication) scanner, etc., may be attached to movable mounting structure 208.

[0034] Figure 5 This is a block diagram illustrating an embodiment of UAV 102. (As shown) Figure 5 As shown, UAV 102 includes a communication manager 502, a processor 504, and a memory 506. The communication manager 502 allows UAV 102 to communicate with other systems such as UAV management system 108, server 110, data communication network 112, etc. The processor 504 executes various instructions to implement the functions provided by UAV 102, as discussed herein. The memory 506 stores these instructions, as well as other data used by the processor 504 and other modules and components included in UAV 102.

[0035] UAV 102 also includes a camera 508 that captures images of an area near UAV 102. In some embodiments, camera 508 is the same as camera 210 discussed above. In other embodiments, camera 508 differs from camera 210. In some embodiments, image processing module 510 analyzes the images captured by camera 508 (or camera 210) to locate the landing platform, delivery area, obstacles, etc. Additionally, image processing module 510 can assist UAV 102 landing by identifying the location of the landing platform (or other landing area) and determining the flight adjustments required for UAV 102 to successfully land on the landing platform. Flight path module 512 generates and maintains information related to the flight path that UAV 102 attempts to follow. In some embodiments, flight path information is received from UAV management system 108 or server 110. Rotor control module 514 controls the operation of a plurality of rotors 516 associated with UAV 102. In some embodiments, the UAV 102 has three or four rotors 516 that assist the UAV 102 in flying between multiple locations. For example, the rotor control module 514 can control the rotational speed of each rotor 516 to steer and maneuver the UAV 102 to a destination, such as a landing platform or delivery location. Thus, the rotor control module 514 can assist in maneuvering the UAV 102 along a specific flight path, avoiding obstacles, etc. In certain embodiments, one or more of the functions performed by the rotor control module 514 are alternatively performed by the UAV management system 108 or server 110, which sends appropriate rotor control commands to the rotor control module 514 for implementation.

[0036] UAV 102 also includes a movable mounting structure controller 518, which controls the movement and positioning of the movable mounting structure 208. For example, the movable mounting structure controller 518 can instruct the motor 216 to change the position of the movable mounting structure 208 from a retracted position to an extended position (or vice versa) based on the current activity, status, or position of UAV 102. Additionally, the movable mounting structure controller 518 can instruct the motor 216 to change the position of the movable mounting structure 208 to maintain a specific field of view for camera 210. Sensor processing module 520 receives data from one or more sensors and processes the data based on pre-programmed instructions, instructions received from UAV management system 108, instructions received from server 110, etc. In some embodiments, sensor processing module 520 provides the received sensor data or analyzed / processed sensor data to communication manager 502 for communication with another system or device, such as UAV management system 108 or server 110.

[0037] Figure 6This is a block diagram illustrating an embodiment of the UAV management system 108. Figure 6 As shown, the UAV management system 108 includes a communication module 602, a processor 604, and a memory 606. The communication module 602 allows the UAV management system 108 to communicate with other systems and devices, such as UAV 102, server 110, data communication network 112, etc. The processor 604 executes various instructions to implement the functions provided by the UAV management system 108, as discussed herein. The memory 606 stores these instructions, as well as other data used by the processor 604 and other modules and components included in the UAV management system 108.

[0038] The UAV management system 108 also includes an image processing module 608, which analyzes images, for example, captured by camera 508 or camera 210. The image processing module 608 assists the UAV 102 in landing by identifying the position and trajectory of the UAV 102 relative to the landing location and determining the flight adjustments required for a successful landing at the landing location. The flight path module 610 generates and maintains information related to the flight path that the UAV 102 attempts to follow.

[0039] UAV camera manager 612 manages cameras 508 and / or 210 to capture appropriate images from either or both of cameras 508, 210. UAV load and unload manager 614 assists in the loading and unloading of the payload carried by UAV 102. Removable installation structure manager 616 controls the movement and positioning of removable installation structure 208. In some embodiments, removable installation structure manager 616 receives commands from server 110 or other systems external to UAV management system 108. In certain embodiments, removable installation structure manager 616 receives movement commands from processor 604, image processing module 608, UAV camera manager 612, or any other component or system within UAV management system 108.

[0040] Figure 7This is a flowchart illustrating an embodiment of a method 700 for operating a UAV and adjusting a movable mounting structure associated with the UAV. Initially, the UAV approaches a landing area 702 and maneuvers to land there. The movable mounting structure on the UAV is moved 704 to an deployed position, allowing a camera on the movable mounting structure to capture 706 an image of the landing area to assist the landing process. Based on the captured image, the UAV is maneuvered 708 to land at the desired location within the landing area. After the UAV has landed in the landing area, the movable mounting structure is moved 710 to a stowed position, providing easy access to the underside of the UAV for loading / unloading payloads at 712, attaching a charging system to the UAV, and performing other activities. When the activities are complete, the movable mounting structure is moved 714 to an deployed position in preparation for takeoff. The UAV then takes off 716 from the landing area and proceeds toward its destination.

[0041] Figure 8 This is a flowchart illustrating an embodiment of a method 800 for controlling the position of a movable mounting structure associated with a UAV to monitor a specific area. Initially, the UAV takes off from the landing area 802. The UAV management system uses the UAV's camera or other sensors to determine 804 the area to be monitored. Then, the UAV management system transmits the information identifying the area to be monitored 806 to the UAV. The UAV moves 808 to the position of the movable mounting structure such that a camera mounted on the movable mounting structure captures an image of the identified area. Additionally, the orientation of the UAV can be adjusted to provide an appropriate field of view for the camera. As the UAV travels through the air, the position of the movable mounting structure is adjusted 810 as needed to keep the camera pointed at the identified area.

[0042] Although various embodiments of this disclosure are described herein, it should be understood that they are presented by way of example only and not as limiting. It will be apparent to those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of this disclosure. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described, but should be defined only by the following claims and their equivalents. This description is presented for purposes of illustration and description. It is not intended to be exhaustive or to limit this disclosure to the precise forms disclosed. Many modifications and variations are possible in light of the teachings disclosed. Furthermore, it should be noted that any or all of the alternative embodiments discussed herein may be used in any desired combination to form additional hybrid embodiments of this disclosure.

Claims

1. A drone comprising: a body component; a movable mounting structure coupled to the body component, wherein the movable mounting structure includes a first end and a second end defining a U-shape, the first end and the second end each being pivotally attached to the body component to form a first pivot point and a second pivot point, the movable mounting structure being configured to move between a stowed position and a deployed position when pivoted about the first pivot point and the second pivot point, the movable mounting structure at least partially surrounding a payload area associated with the drone and extending below the payload area when in the deployed position, a bottom of the drone being accessible when the movable mounting structure is in the stowed position, and wherein movement of the movable mounting structure between the stowed position and the deployed position does not interfere with a payload carried by the drone; a plurality of legs configured to support the drone on a landing surface, wherein the plurality of legs cause a separation between the movable mounting structure and the landing surface when the movable mounting structure is in the deployed position; and a camera mounted to the movable mounting structure, wherein the movable mounting structure is in the deployed position when the drone is landed on the landing surface, and the camera faces downward toward a landing position when the movable mounting structure is in the deployed position.

2. The drone of claim 1, wherein the movable mounting structure moves in an area outside of a payload area associated with the drone.

3. The drone of claim 2, wherein the payload area associated with the drone is accessible from below the drone when the movable mounting structure is in the stowed position.

4. The drone of claim 1, wherein a difference in rotation between the stowed position and the deployed position is 90 degrees.

5. The drone of claim 1, further comprising an image processing module configured to receive and process images captured by the camera.

6. The drone of claim 1, further comprising a movable mounting structure controller configured to manage movement of the movable mounting structure between the stowed position and the deployed position.

7. The drone of claim 6, wherein the movable mounting structure controller is further configured to position the movable mounting structure at a particular position that produces a desired orientation of the camera.

8. The drone of claim 1, further comprising a communication manager configured to communicate with a drone management system to control operation of the drone.

9. The drone of claim 8, wherein the communication manager receives control instructions from the drone management system, and wherein the control instructions define a desired position of the movable mounting structure.

10. The drone of claim 1, wherein the body component is a mounting plate.

11. A drone comprising: a body component; and A movable mounting structure is attached to the fuselage component, wherein the movable mounting structure includes a first end and a second end defining a U-shape, the first end and the second end being pivotally attached to the fuselage component to form a first pivot point and a second pivot point, the movable mounting structure being configured to move between a stowed position and an extended position when pivoting about the first pivot point and the second pivot point, the movable mounting structure extending at least partially around and below a payload area associated with the UAV when in the extended position, the bottom of the UAV being accessible when the movable mounting structure is in the stowed position, and wherein the movement of the movable mounting structure between the stowed position and the extended position does not interfere with the payload carried by the UAV; A plurality of legs configured to support the drone on a landing surface, wherein when the movable mounting structure is in the deployed position, the plurality of legs create a separation between the movable mounting structure and the landing surface; and at least one of a camera, a microphone, a microphone array, an RFID scanner, and an NFC scanner mounted on the movable mounting structure.

12. The drone of claim 11, wherein when the movable mounting structure is in the retracted position, the payload area associated with the drone can be accessed from below the drone.

13. The drone of claim 11, further comprising a movable mounting structure controller configured to manage movement of the movable mounting structure between the stowed position and the deployed position.

14. The drone of claim 11, further comprising a communication manager configured to receive control commands from a drone management system, wherein the control commands define a desired location of the movable mounting structure.

15. A method for an unmanned aerial vehicle, comprising: The movable mounting structure of the UAV is moved from a stowed position to an deployed position without interfering with the payload carried by the UAV. The movable mounting structure includes a first end and a second end defining a U-shape, each end being pivotally attached to a fuselage component of the UAV to form a first pivot point and a second pivot point. When in the deployed position, the movable mounting structure at least partially surrounds and extends below a payload area associated with the UAV. When the movable mounting structure is in the stowed position, the bottom of the UAV is accessible. The UAV includes a plurality of legs configured to support the UAV on a landing surface, wherein when the movable mounting structure is in the deployed position, the plurality of legs create a separation between the movable mounting structure and the landing surface. Images of the landing area are captured using a camera mounted on the movable mounting structure, wherein the movable mounting structure is in the deployed position when the UAV lands on the landing surface, and the camera faces downwards toward the landing position when the movable mounting structure is in the deployed position. Based on the captured images, the drone is manipulated to the landing area; and The movable mounting structure of the UAV is moved from the deployed position to the stowed position by pivoting around the first pivot point and the second pivot point.

16. The method of claim 15, wherein when the movable mounting structure is in the retracted position, it can be accessed from below the drone to the payload area associated with the drone.

17. The method of claim 15, further comprising moving the movable mounting structure of the UAV from the stowed position to the deployed position prior to takeoff from the landing area.

Images