Parcel delivery using drones integrated into a vehicle lift unit

Abstract

A delivery vehicle is disclosed. The delivery vehicle may include a vehicle lift unit configured to move a container to a container pickup zone in an internal vehicle section. The delivery vehicle may also include a vehicle drone unit mounted on an upper section of the vehicle lift unit. The vehicle drone unit may be detachably coupled to the vehicle lift unit. The vehicle drone unit may include a landing platform for a drone. The landing platform may include an opening to allow the drone to engage the container for last-mile delivery. The opening may be located near the container pickup zone.

Description

AREA

[0001] The present disclosure relates to parcel delivery using drones and in particular parcel delivery using a drone unit integrated into a vehicle lift unit. GENERAL STATE OF THE ART

[0002] E-commerce companies and their delivery partners are delivering an ever-increasing number of packages per day while striving to limit resource expenditures (e.g., labor) and reduce delivery times. Currently, various approaches are being used to optimize the loading and unloading process of delivery packages into and out of delivery vehicles. For example, e-commerce companies load packages with similar delivery addresses into vehicles close to each other to improve unloading efficiency. Furthermore, e-commerce companies are optimizing delivery routes for their vehicles to reduce energy consumption and package delivery time.

[0003] While traditional procedures implemented by e-commerce companies are effective in achieving efficiency, challenges remain that cause inconvenience for drivers and / or the e-commerce companies themselves. For example, unloading delivery packages from a delivery vehicle for last-mile delivery is still a manual process and requires resources that may be unavailable or expensive. SUMMARY

[0004] The present disclosure describes a delivery vehicle configured to perform container (or package) deliveries. The delivery vehicle may include a vehicle lift unit configured to move a container / package vertically along a vehicle height and position the container / package in a pick-up zone located near an upper vehicle section. The delivery vehicle may further include a vehicle drone unit, which may be enclosed in the upper vehicle section (e.g., in a recess or depression in the upper vehicle section). The vehicle drone unit may enclose a drone configured to perform last-mile container delivery. The vehicle drone unit may be positioned above the vehicle lift unit and may be aligned with the vehicle lift unit.

[0005] In some aspects, the vehicle drone unit can be connected to the vehicle lift unit via a mechanical interface, a data interface, and a power interface. The mechanical interface allows the vehicle drone unit to be plugged directly into an upper section of the vehicle lift unit. The data interface allows the delivery vehicle to provide delivery instructions to the drone (e.g., instructions to engage the container and perform the last-mile container delivery). The power interface allows the drone to receive power from a power source, such as a vehicle battery.

[0006] In one aspect, the vehicle-based drone unit can include a vehicle landing platform for the drone. The landing platform can have an opening to allow the drone to pick up the container for last-mile delivery. The opening can be located near the pickup zone and aligned with it.

[0007] In addition, the vehicle drone unit may include a sliding flap on its upper section, configured to cover or expose the top. The drone can then move out of the unit when the upper section is exposed. Furthermore, the vehicle drone unit may include a drone resting platform configured to move up and down along the unit's height, allowing the drone to enter or exit.

[0008] In some aspects, the container may include recesses that allow the drone to interact with it. For example, the drone may be equipped with a gripping mechanism to grasp or manipulate the container.

[0009] In other aspects, the landing platform may include one or more recesses (e.g., conical recesses) to facilitate alignment of the drone and vehicle lift unit (e.g., to allow the drone to grasp the container from the pick-up zone in the vehicle lift unit). The conical recesses may be configured to accommodate drone legs. In some aspects, the conical recesses may incorporate a primary magnetic material, enabling magnetic coupling between the landing platform and the drone, which may have a secondary magnetic material. In other aspects, the landing platform may have a shape that corresponds to the shape of the drone's landing gear, allowing the landing gear to engage with the landing platform to facilitate alignment of the drone and vehicle lift unit.

[0010] The present disclosure discloses a delivery system and method that enables last-mile container delivery using drones and a vehicle-mounted lift unit, thereby increasing the efficiency of package delivery and reducing manual effort. The system further facilitates effective integration of the vehicle-mounted drone unit with the vehicle-mounted lift unit, allowing the drone to conveniently pick up the container / package and perform the last-mile delivery.

[0011] These and other benefits of the present revelation are provided in detail in this document. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The detailed description is set forth with reference to the accompanying drawings. The use of the same reference numerals may indicate similar or identical elements. Different embodiments may use different elements and / or components than those illustrated in the drawings, and some elements and / or components may not be present in different embodiments. The elements and / or components in the figures are not necessarily drawn to scale. Throughout this disclosure, singular and plural expressions may be used interchangeably depending on the context. Fig. 1 represents an exemplary environment in which techniques and structures for providing the systems and procedures disclosed in this document may be implemented. Fig. 2 represents an exemplary vehicle drone unit and vehicle lift unit according to the present disclosure. Fig. Figure 3 represents an exemplary sliding flap that is part of the vehicle drone unit. Fig. 2 is assigned according to the present disclosure. Fig. 4 represents an exemplary drone resting platform, which is part of the vehicle drone unit. Fig. 2 is assigned according to the present disclosure. Fig. Figure 5 represents a first exemplary container gripping mechanism according to the present disclosure. Fig. 6A and Fig. 6B represents a second exemplary container gripping mechanism according to the present disclosure. Fig. Figure 7 represents a third exemplary container gripping mechanism according to the present disclosure. Fig. Figure 8 represents a first exemplary alignment of the drone and vehicle lift unit according to the present disclosure. Fig. Figure 9 represents a second exemplary orientation of the drone and vehicle lift unit according to the present disclosure. Fig. Figure 10 represents a third exemplary orientation of the drone and vehicle lift unit according to the present disclosure. Fig. Figure 11 presents a flowchart of an exemplary procedure for facilitating container / package delivery according to the present disclosure. DETAILED DESCRIPTION

[0013] The disclosure is described in more detail below with reference to the accompanying drawings, which show exemplary embodiments of the disclosure, and is not intended to be restrictive.

[0014] Fig. Figure 1 represents an exemplary environment 100 in which techniques and structures for providing the systems and procedures disclosed in this document may be implemented. The environment 100 may include a delivery vehicle 102 (or vehicle 102), which may be a truck, a van (including walk-in vans), a truck trailer, and / or the like. In some aspects, the vehicle 102 may be an autonomous vehicle. In other aspects, a driver (not shown) may operate the vehicle 102. Furthermore, the vehicle 102 may include any powertrain, such as a gasoline engine, one or more electrically driven motors, a hybrid system, etc.

[0015] The vehicle 102 can include one or more layers / arrangements of a plurality of motorized plates 104a, 104b, 104c (collectively referred to as a plurality of motorized plates 104) on which a plurality of containers 106a, 106b, 106c, etc. (collectively referred to as a plurality of containers 106) can be mounted. Each container 106 can be configured to hold one or more packages. In an exemplary aspect, the location of each container 106 within the vehicle 102 and the allocation of each package within each container 106 can be optimally pre-planned or pre-set so that unloading each package / container from the vehicle 102 can be convenient (e.g., when the vehicle 102 arrives at a package delivery location).

[0016] The environment 100 may further include a vehicle lift 108, which may be located in an inner vehicle section near a rear vehicle section. In one exemplary aspect, the vehicle lift 108 may be located beneath an upper sliding section (not shown) of the vehicle 102. The vehicle lift 108 may be configured to move a container 106 (or a package) to a container pick-up zone (e.g., a first pick-up zone) in the inner vehicle section. In particular, the vehicle lift 108 may be configured to pick up the container 106 from one or more motorized plates of the plurality of motorized plates 104 and move the container 106 along a vehicle height to place the container 106 in the first pick-up zone. The first pick-up zone may be located near an upper vehicle section.In other aspects, the vehicle lift 108 can be configured to move the container 106 (or any other container) to a second container pick-up zone (e.g., near a vehicle loading platform) in response to the container 106 being picked up from the motorized plates, enabling a driver to perform a last-mile container delivery. The second pick-up zone can be located near a lower vehicle section.

[0017] Environment 100 may also include a drone 110, which may be communicatively linked to vehicle 102 via one or more networks. The drone 110 may be configured to pick up container 106 from the first pickup zone and perform the last-mile container delivery (e.g., moving container 106 from the first pickup zone to a delivery address assigned to container 106).

[0018] The network(s) described above illustrate(s) an exemplary communication infrastructure in which the connected devices discussed in various embodiments of this disclosure can communicate. The network(s) may be the Internet, a private network, a public network, or another configuration and / or include, and / or operate using any one or more known communication protocols, such as Transmission Control Protocol / Internet Protocol (TCP / IP), Bluetooth, or similar technologies. ® BLE ®, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) standard 802.11, ultrawideband (UWB) and mobile communication technologies such as Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), High-Speed ​​Packet Access (HSPDA), Long-Term Evolution (LTE), Global System for Mobile Communications (GSM) and Fifth Generation (5G), to name just a few examples.

[0019] The vehicle 102 may further include one or more units, including, among others, a vehicle transceiver 112, a vehicle memory 114, and a vehicle processor 116. The vehicle transceiver 112 may be configured to exchange information / data / signals with external devices or vehicle components (such as the drone 110). The vehicle memory 114 may store programs in code and / or data for performing various operations in accordance with this disclosure. In particular, the vehicle processor 116 may be configured and / or programmed to execute computer-executable instructions stored in the vehicle memory 114 for performing various functions in accordance with this disclosure.Consequently, the vehicle memory 114 can be used to store code and / or data code and / or data for carrying out operations in accordance with the present disclosure.

[0020] In some aspects, the vehicle processor 116 can communicate with one or more storage devices (e.g., the vehicle memory 114 and / or one or more external databases (in Fig. (1 not shown)) may be arranged. The vehicle memory 114 may include any one or a combination of volatile memory elements (e.g., dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), etc.) and any one or more non-volatile memory elements (e.g., erasable programmable read-only memory (EPROM), flash memory, electronically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), etc.).

[0021] The vehicle memory 114 can be an example of a non-transient computer-readable storage medium or a non-transient computer-readable memory and can be used to store programs / instructions in code and / or to store data for performing various operations in accordance with the disclosure. The instructions in the vehicle memory 114 can include one or more separate programs, each of which can contain an ordered list of computer-executable instructions for implementing logical functions.

[0022] In some aspects, the vehicle memory 114 can store information associated with the inventory loaded into the vehicle 102. This inventory information (e.g., real-time information) can include, for example, package size / dimensions, package weight, package shape, and / or similar data assigned to each delivery package in the vehicle 102. The information can also include the container size in which the packages / items can be placed, the mapping of the multiple packages to the multiple containers 106 (e.g., which package is placed in which container), and / or similar data. Additionally, the vehicle memory 114 can store delivery information. This delivery information can include the delivery location, delivery route, sequence of package deliveries, date and time of delivery, customer information (such as contact details, delivery address, etc.), and / or similar data.

[0023] The vehicle processor 116 can retrieve information from the vehicle memory 114, including inventory and delivery information. Based on this information, the vehicle processor 116 can determine a container 106 (e.g., the container 106 itself or a package located within the container 106) that can be scheduled for delivery to the next delivery location along the delivery route. In some cases, for last-mile container deliveries, the container may only contain orders / items that are assigned to a specific delivery location / address.

[0024] In response to the identification of container 106, the vehicle processor 116 can cause container 106 to move from its storage location on the multitude of motorized plates 104 (determined based on inventory information obtained from vehicle memory 114) across one or more motorized plates to the vehicle lift 108. Once container 106 is positioned on the vehicle lift 108, the vehicle processor 116 can instruct the vehicle lift 108 to move container 106 to the first pickup zone. Specifically, the vehicle processor 116 can generate instructions for the vehicle lift 108 to move container 106 to the first pickup zone and transmit these instructions to the vehicle lift 108. The vehicle lift 108 can receive the instructions from the vehicle processor 116 and move container 106 to the first pickup zone based on the received instructions.

[0025] In some aspects, the vehicle processor 116 can further be configured to determine that container 106 can be placed in the first pickup zone (e.g., via vehicle sensors, vehicle cameras, and / or the like). In response to a determination that container 106 can be placed in the first pickup zone, the vehicle processor 116 can be configured to generate an instruction(s) for drone 110 to perform a last-mile container delivery and transmit the instruction(s) to drone 110. In some aspects, the instructions may include delivery information, which may contain the delivery or destination location assigned to container 106. Drone 110 can receive the instructions and engage container 106 to move it to the delivery / destination location.

[0026] In some aspects, the drone 110 can include one or more units, including, but not limited to, a drone transceiver 118, a drone memory 120, a drone processor 122, and a drone sensor 124. The drone transceiver 118 can be configured to exchange information, data, notifications, signals, etc., with the vehicle transceiver 112. For example, the drone transceiver 118 can be configured to receive the instruction to perform the last-mile container delivery and can store the received instructions in the drone memory 120. The drone processor 122 can be configured to receive the instructions from the drone transceiver 118 and / or the drone memory 120 and can cause the drone 110 to perform the last-mile container delivery based on the received instructions.

[0027] As an example, upon receiving instructions, drone 110 can first engage container 106 in the first pickup zone and then fly to deliver container 106 to the delivery / destination location. Once drone 110 has completed the container delivery, it can return to vehicle 102 for the next container delivery, and then the process described above can be repeated. In some aspects, the structure / features / functionality of drone memory 120 and drone processor 122 may be the same as the structure / features / functionality of vehicle memory 114 and vehicle processor 116, respectively. Furthermore, in some aspects, drone 110 may include sensor(s) 124 configured to facilitate drone operation. For example, the sensor(s) 124 can include proximity sensors to determine whether the container 106 is located in the first collection zone.Additionally, the sensor(s) can include 124 pressure sensors to confirm a drone landing.

[0028] The drone 110 can be either autonomous or remotely controlled by an operator or a server. In the case of autonomous remote navigation and operation, the drone 110 can maintain communication with the vehicle 102 either via a visual system (e.g., line of sight) or via the network(s) described above. Although the present disclosure describes the use of a drone (e.g., the drone 110) to enable last-mile container delivery from the vehicle 102, the present disclosure is furthermore not limited to the use of a single drone. In other aspects, the vehicle 102 can use multiple drones to perform several deliveries simultaneously to improve unloading or operational efficiency.

[0029] In other aspects, the vehicle processor 116 can instruct the vehicle lift 108 to move another container to the second pickup zone (e.g., near the vehicle's loading platform). In response to the other container being moved to the second pickup zone, the vehicle processor 116 can transmit an instruction / notification to a user device assigned to the driver or to a vehicle infotainment system (not shown) to perform the last-mile container delivery. Thus, the vehicle processor 116 can enable last-mile container delivery via the drone 110 as well as the driver at each delivery stop.

[0030] The vehicle 102, the operator and the drone 110 implement and / or carry out operations in accordance with the user manual and the safety guidelines, as described herein in this disclosure.

[0031] Fig. 2 represents a vehicle drone unit 202 and a vehicle lift unit 204 according to the present disclosure. The vehicle lift unit 204 can be the same as the vehicle lift 108 or a section of the vehicle lift 108 described above in conjunction with Fig. 1 is described. As described above, the vehicle lift unit 204 can be configured to move a container (e.g. the container 106) to the first pick-up zone in the inner vehicle section.

[0032] The vehicle drone unit 202 can be located on an upper vehicle section. In some aspects, the upper vehicle section can include a recess or indentation configured to accommodate / enclose the vehicle drone unit 202. The vehicle drone unit 202 can be configured to enclose the drone 110 inside the vehicle 102. In some aspects, the vehicle drone unit 202 can include a landing platform 206 for the drone 110. The landing platform 206 can include an opening 208 (e.g., a first opening 208) to allow the drone 110 to engage the container 106 for last-mile container delivery. If the vehicle drone unit 202 can be mounted on the upper vehicle section, the first opening 208 can be located near and aligned with the first pickup zone.

[0033] In some aspects, the vehicle drone unit 202 can be arranged on an upper section of the vehicle lift unit 204, as shown in Fig. Figure 2 shows the vehicle drone unit 202 being aligned with the vehicle lift unit 204 to allow the drone 110 to perform the container delivery on the last mile. In some aspects, the vehicle lift unit 204 may include an opening 210 (e.g., a second opening 210) on an upper section of the vehicle lift unit, which may be aligned with the first opening 208 to allow the drone 110 to pick up the container / package from the first pickup zone.

[0034] The vehicle drone unit 202 can be attached to the vehicle lift unit 204. In some aspects, the vehicle drone unit 202 can be removably attached to the vehicle lift unit 204 via a first mechanical attachment interface 212a and a second mechanical attachment interface 212b (collectively referred to as mechanical interface 212). The vehicle drone unit 202 (e.g., a lower section of the vehicle drone unit) can be inserted (or slid) into an upper section of the vehicle lift unit via the mechanical interface 212. In some aspects, the first mechanical structure 212a can be located on the lower section of the vehicle drone unit, and the second mechanical structure 212b can be located on the upper section of the vehicle lift unit.The first mechanical structure 212a can be configured to engage the second mechanical structure 212b to couple the vehicle drone unit 202 with the vehicle lift unit 204.

[0035] In additional aspects, the vehicle drone unit 202 can be coupled to the vehicle lift unit 204 via a data and power interface 214. In some aspects, the data and power interface 214 can be located on the first mechanical structure 212a and the second mechanical structure 212b. In some aspects, the drone 110 (e.g., the drone transceiver 118) can be configured to exchange information with the vehicle 102 (e.g., the vehicle transceiver 112) via the data interface. For example, the vehicle transceiver 112 can be configured to transmit delivery information (such as the delivery location) associated with the container and / or instructions to the drone 110 (e.g., the drone transceiver 118) via the data interface. Additionally, the drone 110 can be configured to receive power from a power source via the power interface.For example, the drone 110 can receive power from the vehicle 102 (e.g., vehicle batteries) or an external power source via the power interface. This allows the drone 110 to be charged via the power interface when it is inside the vehicle drone unit 202. In other words, the drone 110 can charge when it is in a rest or idle position inside the vehicle drone unit 202. Furthermore, the drone 110 can have a built-in small, fast-charging battery to reduce its weight. The drone 110 can be charged between delivery runs.

[0036] Fig. Figure 3 represents an exemplary sliding flap 302 associated with the vehicle drone unit 202 according to the present disclosure. The sliding flap 302 can be arranged on the upper section of the vehicle drone unit. The sliding flap 302 can be configured to slide and open / close the upper section of the vehicle drone unit. In some aspects, the sliding flap 302 can be configured to cover the upper section of the drone unit (e.g., in a closed position) to protect the drone 110 from its environment, for example. The sliding flap 302 can slide and move into an open position to expose the drone 110 (or the vehicle drone unit 202) to allow the drone 110 to take off vertically and perform last-mile container delivery.Additionally, the sliding flap 302 can move into the open position to allow the drone 110 to land directly in the vehicle drone unit 202 (e.g. after completion of delivery).

[0037] Fig. Figure 3 shows various exemplary positions of the sliding flap 302 in views 304, 306, and 308. In view 304, the sliding flap 302 is in the closed position. In this position, the sliding flap 302 can completely cover the upper section of the vehicle drone unit and may prevent the drone 110 from moving into or out of the vehicle drone unit 202. In view 306, the sliding flap 302 is partially open, and in view 308, the sliding flap 302 is fully open (i.e., the sliding flap 302 is in the open position in view 308). If the sliding flap 302 can be in the open position, the drone 110 may be able to move into or out of the vehicle drone unit 202.

[0038] In some aspects, the sliding flap 302 can be configured to open or close based on instructions / command signals transmitted by the vehicle processor 116 or user input. In other aspects, the sliding flap 302 can allow the drone 110 (e.g., a drone vision system) to identify a landing zone within the inner vehicle section. In some aspects, the drone wings can remain extended even when the drone 110 is at rest in the vehicle drone unit 202 or when the drone 110 is in flight mode.

[0039] Fig. Figure 4 presents an exemplary drone resting platform 402 associated with the vehicle drone unit 202 according to the present disclosure. The drone resting platform 402 can be arranged in an inner section of the vehicle drone unit. The drone resting platform 402 can be configured to move vertically up and down along a height of the vehicle drone unit to enable drone movement within the vehicle drone unit 202. In other words, the drone resting platform 402 can be actuated up or down to raise the drone 110 up or down and move the drone 110 into or out of the vehicle drone unit 202. In some aspects, the drone resting platform 402 can include a telescopic / linear actuator 404 to move the drone resting platform 402 up or down within the vehicle drone unit 202. The telescopic / linear actuator 404 can include a variety of telescopic legs (e.g.,(two legs on opposite sides). If the vehicle drone unit 202 can accommodate the drone resting platform 402, the drone 110 can retract its drone wings so that it can be stowed in a compact / narrow space.

[0040] Fig. Figure 4 shows various exemplary views of the drone resting platform 402 in views 406, 408, and 410. In view 406, the drone resting platform 402 can be in a lower / downward-facing position. In this position, the drone wings can be retracted and located within the vehicle drone unit 202. When the vehicle processor 116 generates the instruction for the drone 110 to perform the last-mile container delivery, the drone processor 122 can receive the instruction and enable the drone 110 to grasp the container 106 (or package) located in the first pickup zone. In response to the drone 110 grasping the container 106, the drone resting platform 402 can begin to move upwards (an intermediate position is shown in view 408) until the drone resting platform 402 moves to an upper / upward-facing position, as shown in view 410.In this position, the drone 110 can be fully lifted out of the vehicle drone unit 202 and the drone wings can be in an extended / unfolded position to perform the vertical takeoff (as shown in view 410).

[0041] Fig. Figure 5 represents a first exemplary container gripping mechanism according to the present disclosure. The container gripping mechanism can enable a drone (e.g., the drone 110) to engage a container 502 according to the present disclosure. The container 502 can be a hollow cube or cuboid and can include a lower container section 504 and a plurality of container side walls 506. In some aspects, the container 502 can additionally include a cover 508 on an upper container section. One or more container side walls 506 can include a recess 510 on an upper section of the container side wall. In some aspects, the recesses 510 can be arranged on a section (e.g., 50-80%) of a side wall length. The recesses 510 can enable the drone 110 to engage or grip the container 502 (e.g., via hooks 512 attached to the drone 110).In some aspects, the recesses 510 and the hooks 512 can form the container gripping mechanism.

[0042] In some aspects, the container 502 can be arranged on a base 514 located in the vehicle 102. The container 502 can be detachably attached to the base 514. The base 514 can include locating pins 516, for example, at the corners of the base. The locating pins 516 can be configured to engage with the lower container section 504 (e.g., with the locating holes 518 in the lower container section 504) to prevent unwanted movement of the container within the vehicle 102 (e.g., due to vehicle movement). In other aspects, the base 514 can be an air-filled cushion (e.g., for fall protection). In additional aspects, the lower container section 504 can also be an air-filled cushion. The container 502 can be made of a lightweight and disposable material (e.g., cardboard).

[0043] Fig. Figures 6A-6B represent a second exemplary container gripping mechanism according to the present disclosure. The container gripping mechanism can enable a drone (e.g., the drone 110) to engage a container 602 according to the present disclosure. In some aspects, the container 602 may have recesses in an upper container section, as described above in conjunction with Fig. 5 described. The container gripping mechanism can include a structural element 608 which can be attached to the drone 110 (e.g. a lower drone section). Fig. Figures 6A-6B specifically depict a top view 604 and a side view 606 of the container 602 and the structural element 608 at different stages. The structural element 608 can be a sheet metal plate that may be attached to the lower drone section. The structural element 608 can have any shape and size that corresponds to the shape and size of the container / package. For example, the structural element 608 can have a square shape if the container 602 is cube-shaped.

[0044] In other aspects, the structural element 608 can include hooks 610 for engaging (or gripping) the container 602 (e.g., container recesses). The hooks 610 can be arranged eccentrically around the circumference of the structural element. For example, the hooks 610 can be arranged at the corners of structural elements. In some aspects, the hooks 610 can be mounted on spring-loaded hinges with mechanical stops 612, as shown in side view 606 (from Fig. 6A-6B) shown so that the hooks 610 engage the container 602 (e.g., the container recesses). Alternatively, the hooks 610 can include counterweights (not shown) to cause the hooks 610 to engage the container 602.

[0045] In some aspects, the hooks 610 may be located at the ends of long, slender elements 614 of the structural element 608, which may be made of materials such as plastic or thin spring steel. In other aspects, the hooks 610 may include a chamfered surface 616 on a lower hook section, which allows the hooks 610 to be pushed outwards when they come into contact with the top of the container walls. The container 602 may be raised to a sufficient height so that the hooks 610 can fully engage the container recesses.

[0046] In some aspects, to grasp the container 602, the vehicle lift unit 204 can move the container 602 upwards until the container 602 and the hooks 610 engage (e.g., until a vertical alignment is achieved between the hooks 610 and recesses in the container walls). If the container 602 can move upwards, a container side wall can push the hooks 610 outwards (e.g., via the chamfered surface 616 and using the spring-loaded hinges with mechanical stops 612, as shown in phase 618 of side view 606 in Figure 1). Fig. (shown in Figure 6A). As the container 602 moves further upwards, the container recesses in the container side walls can align with the hooks 610. Once the container recesses are aligned with the hooks 610, the hooks 610 can move inwards (e.g., due to the weight of the hooks) and can move inside the container recesses, as shown in phase 620 of side view 606 in Figure 6A. Fig. 6A shown.

[0047] The drone 110 can then energize all its propellers in the same direction (e.g., counterclockwise), causing the drone 110 to rotate in the opposite direction (e.g., clockwise) due to the conservation of angular momentum. As the drone 110 rotates in the opposite direction, the hooks 610 can be "locked" or engaged with the container recesses, as shown in phase 622 of side view 606. Fig. 6A shown. In response to the fact that the hooks 610 are locked / engaged with the container recesses, the drone 110 lifts off vertically to carry out the last mile container delivery.

[0048] To release the container 602 from the hooks 610 (e.g., at the time of delivery), the drone 110 can begin to land on a surface (e.g., the ground). Once the container 602 has landed on the surface and the drone 110 continues its downward movement, the container recesses in the container side walls can be aligned with the hooks 610, as shown in stage 624 of side view 606. Fig. 6B shown. The drone 110 can then release the hooks 610 from the container recesses by activating all propellers in the same direction (e.g., clockwise), which causes the drone 110 to rotate in the opposite direction (e.g., counterclockwise) due to the conservation of angular momentum. The drone 110 thus releases the hooks 610 from the container recesses, as shown in phase 626 of the top view 604 and the side view 606 in Fig. Figure 6B shows that drone 110 then lifts off vertically until all components have passed the upper container section. Drone 110 can then fly sideways and return to vehicle 102 (and repeat the process).

[0049] Fig. Figure 7 presents a third exemplary container gripping mechanism 702 according to the present disclosure. The container gripping mechanism 702 can enable a drone (e.g., the drone 110) to engage a package 704 (or a container). In some aspects, the drone 110 can couple with (or be equipped with) the container gripping mechanism 702 (e.g., from the lower drone section). The container gripping mechanism 702 can be attached to the lower drone section using a mounting mechanism, such as a bolt-and-screw connector. The container gripping mechanism 702 can be made of lightweight material to reduce the overall weight of the drone, which can reduce the drone's power consumption.

[0050] The container gripping mechanism 702 can include a telescopic arm 706 and a gripping structure / gripping arms 708. The gripping arms 708 can be arranged perpendicular to the telescopic arm 706, and in one exemplary aspect, two gripping arms 708 can be arranged opposite each other. In some aspects, the gripping arms 708 can be detachably connected to the telescopic arm 706 and can be replaced when worn. The gripping arms 708 can include gripping surfaces that can contact the walls of the package 704. In some aspects, the gripping surfaces can be made of a light rubber padding to facilitate gripping the package 704. In other aspects, the container gripping mechanism 702 can include an arm support / arm supports 710 for the drone landing pad. The arm support(s) 710 can be arranged on two opposite sides of the telescopic arm 706.In some aspects, the drone processor 122 can control the movement of the gripper arms 708 to enable the gripping and release of the package 704 when the drone 110 performs the package delivery on the last mile.

[0051] Fig. Figure 8 represents a first exemplary alignment of the drone and vehicle lift unit according to the present disclosure. As described above, the drone 110 can be aligned with the vehicle lift unit 204 to enable the drone 110 to grasp a container (e.g., the container 106) to perform a last-mile container delivery. In some aspects, the vehicle drone unit 202, in order to align the drone 110 with the vehicle lift unit 204, may include mechanical alignment features described below (in addition to the drone detection, planning, and motion control schemes).

[0052] Specifically, it states Fig. Figure 8 represents the vehicle lift unit 204, which can move a container 802 to the container pickup zone / first pickup zone (e.g., in the direction of the vehicle drone unit 202, in which the drone 110 may be located). The drone 110 may be equipped with a package / container gripper 804 configured to grasp the container 802. The vehicle drone unit 202 may include a landing platform 806 on which the drone 110 can land. The landing platform 806 may have one or more recesses 808 (e.g., conical recesses) to receive or engage drone legs 810. The recesses 808 may facilitate precise alignment of the drone and the vehicle lift unit.

[0053] In some aspects, the recesses 808 can contain a first magnetic material (e.g., embedded magnets or electromagnets) that can interact with a second magnetic material (e.g., magnets or ferromagnetic materials) arranged in the drone legs 810. Thus, the landing platform 806 can be configured to be magnetically coupled to the drone 110 via the first and second magnetic materials. In some aspects, the first and second magnetic materials can provide sufficient attraction to prevent unwanted drone movement, but not so much force as to prevent the drone 110 from flying. In one exemplary aspect, if the recesses 808 contain electromagnets, the holding force can be made large and then switched off just before the drone takes off.

[0054] Fig. Figure 9 represents a second exemplary orientation of the drone and vehicle lift unit according to the present disclosure. Specifically, Figure 9 represents Fig. Figure 9 represents the vehicle lift unit 204, which can move a container 902 to the container pickup zone (e.g., towards the vehicle drone unit 202, in which the drone 110 may be located). The drone 110 may be equipped with a package / container gripper 904 configured to grasp the container 902. The vehicle drone unit 202 may include a landing platform / landing pad 906 on which the drone 110 can land. The landing platform 906 may include a base 908 and side walls 910. The side walls 910 may be arranged at a predefined non-zero angle relative to the base 908. The landing platform 906 may have any size and shape and may be configured to accommodate a landing gear 912 of the drone 110. The landing platform shape can correspond to the landing gear shape, so that the landing platform 906 and the landing gear 912 can lock into each other, thus enabling alignment of the drone and vehicle lift unit.In other words, the landing platform 906 can be configured to be mechanically attached to the landing gear 912 to allow alignment of the drone and vehicle lift unit.

[0055] Fig. Figure 10 represents a third exemplary orientation of the drone and vehicle lift unit according to the present disclosure. Specifically, Figure 10 represents Fig. Figure 10 represents the vehicle lift unit 204, which can move a container 1002 to the container pickup zone (e.g., towards the vehicle drone unit 202, in which the drone 110 may be located). The drone 110 may be equipped with a package / container gripper 1004 configured to grip the container 1002. The vehicle drone unit 202 may include a landing platform / landing pad 1006 on which the drone 110 can land. The landing platform 1006 may include rest pads 1008, which may be arranged at two opposite ends of the upper surface of the landing platform. The rest pads 1008 may be configured to accommodate the package / container gripper 1004. The rest pads 1008 may have a conical recess to accommodate a package gripper section (e.g., gripper legs) to facilitate alignment of the drone and vehicle lift unit. In some aspects, the vehicle drone unit 202 may include a sliding flap 1010, which is located in Fig. 5 is described.

[0056] Fig. Figure 11 presents a flowchart of an exemplary procedure for facilitating container / package delivery according to the present disclosure. Fig. Figure 11 may be described with continued reference to earlier figures. The following process is exemplary and is not limited to the steps described below. Moreover, alternative embodiments may include more or fewer steps than are shown or described in this document, and these steps may be in a sequence that differs from the sequence described in the following exemplary embodiments.

[0057] Procedure 1100 begins at step 1102. At step 1104, procedure 1100 may involve the vehicle processor 116 obtaining delivery information assigned to a container (e.g., container 106). The delivery information may include a delivery location.

[0058] In step 1106, the procedure 1100 may cause the vehicle processor 116 to move a vehicle lift unit (e.g., the vehicle lift unit 204) to the container 106 in response to receiving delivery information to a container pick-up zone in the inner vehicle section.

[0059] In step 1108, the procedure 1100 can involve generating, by the vehicle processor 116, an instruction for the drone 110 to engage the container 106 in the container pickup zone and carry out the container delivery on the last mile. In step 1110, the procedure 1100 can involve transmitting, by the vehicle processor 116, the generated instructions to the drone 110.

[0060] Procedure 1100 ends at step 1112.

[0061] The preceding disclosure refers to the accompanying drawings, which form part thereof and illustrate specific implementations in which the present disclosure can be practically implemented. It is understood that other implementations may be used and structural modifications made without deviating from the scope of the present disclosure. References in the description to "an embodiment," "an exemplary embodiment," etc., indicate that the described embodiment may include a specific feature, structure, or property, but not every embodiment necessarily includes that specific feature, structure, or property. Furthermore, such formulations do not necessarily refer to the same embodiment.Furthermore, if a feature, structure or property is described in connection with an embodiment, the person skilled in the art will recognize such a feature, structure or property in connection with other embodiments, whether this is expressly described or not.

[0062] Furthermore, the functions described in this document may be performed in one or more hardware, software, firmware, digital components, or analog components. For example, one or more application-specific integrated circuits (ASICs) may be programmed to execute one or more of the systems and procedures described in this document. Certain terms are used throughout the description, and patent claims refer to specific system components. It is obvious to those skilled in the art that the components may be designated by other names. This document does not distinguish between components that differ in name but not in function.

[0063] It is also understood that the word "example," as used in this document, is not intended to be exclusive or restrictive. In particular, the word "example," as used in this document, indicates one of several examples, and it is understood that no undue emphasis or preference is placed on the specific example described.

[0064] A computer-readable medium (also called a processor-readable medium) comprises any non-volatile (e.g., physical) medium involved in providing data (e.g., instructions) that can be read by a computer (e.g., by a computer's processor). Such a medium can take many forms, including, without limitation, both non-volatile and volatile media. Computing devices can contain computer-executable instructions, the instructions being executable by one or more computing devices, such as those listed above, and being stored on a computer-readable medium.

[0065] With regard to the processes, systems, procedures, heuristics, etc., described in this document, it is understood that, although the steps of such processes, etc., have been described as following a certain orderly sequence, such processes could be implemented in practice in such a way that the described steps are carried out in a sequence that differs from the sequence described in this document. Furthermore, it is understood that certain steps could be carried out simultaneously, that other steps could be added, or that certain steps described in this document could be omitted. In other words, the descriptions of processes in this document serve the purpose of illustrating various embodiments and should in no way be interpreted as limiting the patent claims.

[0066] Accordingly, it is understood that the foregoing description is intended to be illustrative and not limiting. Many other embodiments and applications beyond the examples provided will become apparent from reading the preceding description. The scope should not be determined by reference to the foregoing description, but instead by reference to the attached claims, together with the full scope of equivalents to which these claims entitle. It is anticipated and intended that there will be future developments in the prior art discussed in this document and that the disclosed systems and methods will be incorporated into such future embodiments. Overall, it is understood that the application may be modified and varied.

[0067] All terms used in the patent claims shall have their general meaning as known to a person skilled in the art in the field of the technologies described in this document, unless expressly stated otherwise herein. In particular, the use of singular articles such as "a", "an", "the", "the", etc., shall be understood to refer to one or more of the elements indicated, unless a patent claim expressly limits this to the contrary.Phrases expressing conditional relationships, such as "may," "could," "can," or "may possibly," are generally intended to convey that certain embodiments might include certain features, elements, and / or steps, whereas other embodiments might not include them, unless specifically stated otherwise or the context makes it clear. Thus, such conditional phrases generally do not imply that features, elements, and / or steps are required in any way for one or more embodiments.

[0068] In one aspect of the invention, the vehicle drone unit is detachably coupled to the vehicle lift unit via a mechanical interface.

[0069] In one aspect of the invention, the vehicle drone unit is coupled to the vehicle lift unit via a data interface, and the vehicle is configured to transmit delivery information associated with the container to the drone via the data interface.

[0070] In one aspect of the invention, the vehicle drone unit is coupled to the vehicle lift unit via a power interface, and the drone is configured to receive power from a power source via the power interface.

[0071] In one aspect of the invention, the opening is located near the container collection zone.

[0072] According to the present invention, a non-transient computer-readable storage medium is provided on which instructions are stored which, when executed by a processor, cause the processor to: obtain delivery information associated with a container, wherein the delivery information includes a delivery location; cause a vehicle lift unit of a vehicle to move the container to a container pick-up zone in an inner vehicle section in response to obtaining the delivery information;Generating an instruction for a drone to engage the container in the container pickup zone and perform a last-mile container delivery, wherein the drone is located in a vehicle drone unit mounted on an upper section of the vehicle lift unit, the vehicle drone unit comprising a landing platform for the drone, and the landing platform comprising an opening to enable the drone to engage the container for last-mile container delivery; and transmitting the instruction to the drone, wherein the drone is configured to receive the instruction and engage the container to perform the last-mile container delivery.

Claims

[1] Vehicle comprising: a vehicle lift unit configured to move a container to a container pickup zone in an interior vehicle section; and a vehicle drone unit disposed at an upper portion of the vehicle lift unit, the vehicle drone unit including a landing platform for a drone, the landing platform including an opening to allow the drone to engage the container for a last-mile container delivery, and the opening being located near the container pickup zone. [2] The vehicle of claim 1, further comprising an upper vehicle portion having a recess, the recess configured to enclose the vehicle drone unit. [3] The vehicle of claim 1, wherein the vehicle drone unit is removably coupled to the vehicle lift unit via a mechanical interface. [4] The vehicle of claim 1, wherein the vehicle drone unit is coupled to the vehicle lift unit via a data interface, and wherein the vehicle is configured to transmit delivery information associated with the container to the drone via the data interface. [5] The vehicle of claim 1, wherein the vehicle drone unit is coupled to the vehicle hoist unit via a power interface, and wherein the drone is configured to receive power from a power source via the power interface. [6] The vehicle of claim 1, wherein the vehicle drone unit comprises a sliding door on an upper portion of the vehicle drone unit, and wherein the sliding door is configured to open or close the upper portion of the vehicle drone unit to enable drone movement for last mile container delivery. [7] The vehicle of claim 6, wherein the vehicle drone unit further comprises a drone rest platform in an interior portion of the vehicle drone unit, and wherein the drone rest platform is configured to move up and down along a height of the vehicle drone unit to enable drone movement within the vehicle drone unit. [8] The vehicle of claim 1, wherein the container comprises a container sidewall, wherein the container sidewall comprises one or more recesses, and wherein the drone is configured to engage the container via the one or more recesses. [9] The vehicle of claim 1, wherein the landing platform includes a recess configured to receive drone legs. [10] The vehicle of claim 9, wherein the recess comprises a first magnetic material and the drone legs comprise a second magnetic material, and wherein the landing platform is configured to be magnetically coupled to the drone via the first magnetic material and the second magnetic material. [11] The vehicle of claim 1, wherein a shape of the landing platform corresponds to a shape of a drone landing gear, and wherein the landing platform is configured to be mechanically attached to the drone landing gear. [12] The vehicle of claim 1, further comprising a processor configured to: Obtaining delivery information associated with the container, wherein the delivery information includes a delivery location; and Causing the vehicle lift unit to move the container to the container pickup zone in response to obtaining the delivery information. [13] The vehicle of claim 12, wherein the processor is further configured to: Determine that the container is placed in the container pickup zone; generating an instruction for the drone to perform the last-mile container delivery in response to a determination that the container is placed in the container pickup zone, the instruction comprising the delivery information; and Transmitting the instruction to the drone, wherein the drone is configured to receive the instruction and engage the container to perform the last mile container delivery in response to receiving the instruction from the processor. [14] Method comprising: Obtaining, by a processor, delivery information associated with a container, the delivery information including a delivery location; causing, by the processor, a vehicle lift unit of a vehicle to move the container to a container pickup zone in an interior vehicle compartment in response to obtaining the delivery information; Generating, by the processor, an instruction for a drone to engage the container in the container pickup zone and perform a last-mile container delivery, wherein the drone is disposed in a vehicle drone unit disposed at an upper portion of the vehicle hoist unit, wherein the vehicle drone unit includes a landing platform for the drone, and wherein the landing platform includes an opening to enable the drone to engage the container for the last-mile container delivery; and Transmitting, by the processor, the instruction to the drone, wherein the drone is configured to receive the instruction and engage the container to perform the last mile container delivery in response to receiving the instruction. [15] The method of claim 14, further comprising: Determining that the container is placed in the container pickup zone; and Generating the instruction for the drone in response to a determination that the container is placed in the container pickup zone.

Images