Method and system for loading, picking up and delivering packages by drones

Abstract

A method for loading, picking up, and delivering a package by a drone, and a system. The method for loading a package by a drone includes: navigating a drone to a serviceable point, the drone including: a drone chassis and a package carrying device selectively coupleable to and removable from the drone chassis, the package carrying device including: an engagement housing at least partially insertable into an internal cavity of a lower portion of the drone chassis to thereby secure to the drone chassis; and a package carrying mechanism coupleable to the engagement housing and positionable thereunder, wherein the package carrying mechanism includes a pair of package carrying arms movable between an engaged position and a disengaged position, wherein at the engaged position the package carrying arms engage a package and at the disengaged position the package carrying arms are spaced apart from the package; detecting a package at the serviceable point; and engaging the package at the engaged position via the package carrying arms such that the package carrying device loads the package.

Description

[0001] This application is a divisional application of PCT patent application PCT / US2017 / 030157, filed on April 28, 2017, with application number 201780026272.0 and entitled "Unmanned Aerial Vehicle Pickup and Delivery System", which entered the Chinese national phase. Technical Field

[0002] The present invention relates to methods and systems for loading, picking up and delivering packages from vehicles by drones, and more particularly to systems including the drone and the vehicle. Background Technology

[0003] Traditionally, parcel transportation between origin and destination is a labor-intensive process. For short-distance, “local” deliveries, items (e.g., parcels) can be transported between origin and destination by delivery personnel. For example, delivery personnel can drive vehicles between origin and destination, ensuring that items are correctly picked up and / or delivered according to delivery instructions. For long-distance deliveries, the transportation of items may involve multiple delivery personnel, who may individually perform one or more steps to pick up items, sort items one or more times, transport items from the final sorting location to the final delivery destination, and / or deliver items from the delivery vehicle to the final destination address (e.g., a point of service). Due to the labor-intensive nature of this process, various attempts have been made to assist carriers by reducing the physical demands required in the transportation and delivery process; however, previous attempts have encountered significant difficulties in ensuring that all aspects of the transportation and delivery process are properly executed. For example, attempts have been made to utilize unmanned vehicles (e.g., unmanned aerial vehicles, UAVs) to transport items from the final sorting location to the intended delivery destination. However, these concepts are often limited by the effective range of UAVs and the number of available UAVs that can be used to deliver items to locations quite far from the final sorting location.

[0004] Therefore, additional systems and methods are needed to assist carriers, thereby reducing the physical requirements of the transportation and delivery process. Summary of the Invention

[0005] In one embodiment, the UAV for delivering packages includes a UAV frame, the UAV frame including an upper portion having a plurality of propulsion members configured to provide lift to the UAV frame. The UAV frame further includes a lower portion vertically positioned below the upper portion, the lower portion defining an inner cavity. A package carrier of the UAV is configured to be selectively coupled to and removed from the UAV frame, the package carrier including an engagement housing configured to be at least partially inserted into the inner cavity of the lower portion of the UAV frame and thus secured to the UAV frame. The package carrier has a package carrying mechanism coupled to and located below the engagement housing, wherein the package carrying mechanism is configured to engage and hold the package.

[0006] In another embodiment, the UAV for delivering packages includes a UAV frame with an upper portion including a plurality of propulsion members configured to provide lift to the UAV frame. The UAV frame further includes a lower portion vertically positioned below the upper portion. A package carrier is selectively coupled to and removable from the UAV frame, the package carrier including an engagement housing configured to be secured to the lower portion of the UAV frame. A package carrying mechanism of the package carrier is coupled to and positioned below the engagement housing, wherein the package carrying mechanism is configured to engage the package.

[0007] In yet another embodiment, the UAV for delivering packages includes a UAV frame comprising: a plurality of propulsion members configured to provide lift to the UAV frame; and a UAV electrical interface electrically coupled to the plurality of propulsion members. The UAV further includes a package carrier selectively coupled to and removable from the UAV frame, the package carrier including an engagement housing configured to be fixed to the UAV frame. The engagement housing includes a carrier electrical interface configured to be electrically coupled to the UAV electrical interface when the package carrier is coupled to the UAV frame. A package carrying mechanism of the package carrier is coupled to the engagement housing, wherein the package carrying mechanism is configured to engage a package, and a power supply for the package carrier is electrically coupled to the carrier electrical interface and configured to supply power to the plurality of propulsion members when the package carrier is coupled to the UAV frame.

[0008] In one embodiment, the enhanced package delivery system includes a UAV with a UAV frame, the UAV frame including an upper portion and a plurality of propulsion members configured to provide lift to the UAV frame. The UAV frame includes a lower portion vertically positioned below the upper portion, the lower portion defining an inner cavity. A first package carrier selectively coupled to and removable from the UAV frame includes a first engagement housing configured to at least partially insert into the inner cavity of the lower portion of the UAV frame. The first package carrier includes a first power source positioned within the first engagement housing and configured to be electrically coupled to the plurality of propulsion members. A first package carrying mechanism of the first package carrier is coupled to and positioned below the first engagement housing, wherein the first package carrying mechanism is configured to engage a first package. The system further includes a second package carrier selectively coupled to and removable from the UAV frame, the second package carrier including a second engagement housing configured to at least partially insert into the inner cavity of the lower portion of the UAV frame. The second package carrier includes a second power source located within a second engagement housing and configured to be electrically coupled to a plurality of propulsion members. A second package carrier mechanism of the second package carrier is coupled to and located below the second engagement housing, wherein the second package carrier mechanism is configured to engage a second package.

[0009] In another embodiment, the UAV for delivering packages includes a UAV frame comprising an upper portion having an upper width evaluated in the lateral direction, wherein the upper portion includes a tapered shape such that the upper width decreases as it moves downward in the vertical direction. The UAV frame includes a plurality of propulsion members and a lower portion, the plurality of propulsion members being configured to provide lift to the UAV frame, the lower portion being vertically positioned below the upper portion. The lower portion of the UAV frame includes a lower width evaluated in the lateral direction, and the UAV frame includes a width-reducing portion positioned between the upper and lower portions, the width-reducing portion having a width evaluated in the lateral direction, wherein the width of the width-reducing portion is less than the width of the upper portion and the width of the lower portion. The UAV further includes a package-carrying mechanism coupled to the lower portion, wherein the package-carrying mechanism is configured to engage a package.

[0010] In yet another embodiment, the UAV for delivering packages includes a UAV frame comprising an upper portion and a plurality of propulsion members having an upper width evaluated in the lateral direction, the plurality of propulsion members being configured to provide lift to the UAV frame. The UAV frame further includes a width-reducing portion located below the upper portion, the width-reducing portion having a width evaluated in the lateral direction, wherein the width of the width-reducing portion is smaller than the width of the upper portion. A package-carrying device of the UAV is selectively coupled to the UAV frame, the package-carrying device including an engagement housing selectively coupled to the width-reducing portion of the UAV frame. A package-carrying mechanism of the package-carrying device is coupled to the engagement housing, wherein the package-carrying mechanism is configured to engage a package.

[0011] In another embodiment, an enhanced package delivery system for delivering packages via a UAV includes a UAV support mechanism having a pair of opposing guide rails extending in a longitudinal direction, wherein the opposing guide rails are spaced apart from each other in a lateral direction transverse to the longitudinal direction. The opposing guide rails define a landing area, a takeoff area positioned opposite to the landing area, and a transfer area positioned between the takeoff area and the landing area. The system further includes at least one UAV including a UAV frame having an upper portion having an upper width evaluated in the lateral direction. A lower portion of the UAV frame is positioned vertically below the upper portion and has a lower width evaluated in the lateral direction. A width-reducing portion of the UAV frame is positioned between the upper and lower portions and has a width evaluated in the lateral direction. The width of the width-reducing portion is smaller than the width of the upper portion and the width of the lower portion, and the width-reducing portion is configured to engage the pair of opposing guide rails of the UAV support mechanism.

[0012] In one embodiment, a primary delivery vehicle configured to deliver packages via a UAV includes an interior compartment and a roof panel defining an entrance, accessible through the entrance. The vehicle includes a UAV support mechanism positioned on the roof panel and configured to provide a landing surface for the UAV. The UAV support mechanism includes a pair of opposing guide rails extending longitudinally and positioned above the entrance, wherein the opposing guide rails are spaced apart from each other in a lateral direction transverse to the longitudinal direction. The opposing guide rails define a landing area, a takeoff area positioned opposite the landing area, and a transfer area positioned between the takeoff area and the landing area.

[0013] In another embodiment, a primary delivery vehicle configured to deliver packages via a UAV includes an interior chamber, a top plate defining a supply inlet and a return inlet spaced apart from the supply inlet, wherein the interior chamber is accessible through the supply inlet and the return inlet. The vehicle further includes a UAV support mechanism comprising a pair of opposing rails extending in a longitudinal direction, wherein the opposing rails are spaced apart from each other in a transverse direction to the longitudinal direction. The opposing rails define a landing area, a supply area positioned above the supply inlet of the top plate, a return area positioned above the return inlet of the top plate, and a transfer area positioned between the supply area and the return area.

[0014] In yet another embodiment, the primary delivery vehicle configured to deliver packages via a UAV includes an interior chamber and a top panel defining a supply entrance, wherein the interior chamber is accessible through the supply entrance, and a loading robot is positioned within the interior chamber. The loading robot includes a robot controller comprising at least one processor and at least one memory, the memory including program code configured to cause the loading robot, via the processor, to at least engage a package carrier, move the package carrier to the supply entrance, and engage the package carrier with a UAV positioned above the supply entrance.

[0015] In yet another embodiment, a primary delivery vehicle configured to deliver packages via a UAV includes an inner chamber and a top panel defining a return entrance, the inner chamber being accessible through the return entrance. A loading robot is positioned within the inner chamber and includes a robot controller comprising at least one processor and at least one memory, the memory including program code configured to, via the processor, at least engage a package carrier coupled to the UAV located above the return entrance, remove the package carrier from the UAV rack of the UAV, move the package carrier from the return entrance to a bracket positioned within the inner chamber, and engage the package carrier with the bracket within the inner chamber.

[0016] In yet another embodiment, a method for loading / unloading a package carrier into a UAV includes: receiving a package to be delivered by the UAV and engaging a package carrier mechanism of the package carrier with the package, the package carrier mechanism being configured to engage the package and secure the package to the package carrier. The method further includes moving the package carrier and the package toward a UAV rack of the UAV, and securing an engagement housing of the package carrier to the UAV rack of the UAV, wherein the engagement housing of the package carrier is coupled to and positioned on the package carrier mechanism of the package carrier.

[0017] In one embodiment, a method for loading / unloading a package carrier into a UAV includes: engaging a package with the package carrier, the package carrier including an engagement housing and a package carrier mechanism coupled to and positioned below the engagement housing, wherein the package engages with the package carrier mechanism. The method further includes moving the package carrier toward a UAV frame positioned on a UAV support mechanism, moving an engagement member of the UAV frame from an extended position to a retracted position, thereby engaging the engagement housing of the package carrier with the UAV frame. The method further includes moving the engagement member of the UAV frame from a retracted position to an extended position, securing the engagement housing to the UAV frame.

[0018] In yet another embodiment, a method for delivering a package via a UAV includes: securing a first package to a first package carrier, and at a loading point, securing the first package carrier to a rack of the UAV for delivery of the first package. The method further includes navigating the UAV from the loading point to a serviceable point, and at the serviceable point, releasing the first package from a package-carrying mechanism of the first package carrier. The method further includes navigating the UAV from the serviceable point to the loading point, and at the loading point, removing the first package carrier from the UAV rack and securing a second package carrier coupled to a second package to the UAV rack for delivery of the second package.

[0019] In another embodiment, a method for accessing a restricted access area via a UAV includes: electronically storing an access code associated with the restricted access area by a computing entity of the UAV, wherein (a) the restricted access area is located at a serviceable point, (b) a user computing entity at the serviceable point is configured to selectively allow access to the restricted access area in response to receiving the access code, and (c) the UAV includes a UAV computing entity. The method further includes, after navigating the UAV near the restricted access area at the serviceable point, transmitting the access code to the user computing entity via the computing entity of the UAV, wherein (a) a UAV rack selectively coupled to the UAV is included, and (b) in response to receiving the access code, the user computing entity allows entry into the restricted access area. After the user computing entity allows entry into the restricted access area, the method further includes navigating the UAV to the restricted access area of ​​the serviceable point via the computing entity of the UAV.

[0020] In yet another embodiment, the UAV computing entity includes at least one processor and at least one memory, the memory including program code configured to cause the UAV computing entity to store, at least electronically, an access code associated with a restricted access area, wherein (a) the restricted access area is at a serviceable point, (b) a user computing entity at the serviceable point is configured to selectively allow access to the restricted access area in response to receiving the access code, and (c) the UAV includes the UAV computing entity. After navigating a UAV near the restricted access area at the serviceable point, the UAV computing entity is configured to transmit the access code to the user computing entity, wherein (a) a UAV rack selectively coupled to the UAV is wrapped, and (b) in response to receiving the access code, the user computing entity allows entry into the restricted access area. After the user computing entity allows entry into the restricted access area, the UAV computing entity is configured to navigate the UAV to the restricted access area of ​​the serviceable point.

[0021] In one embodiment, a method for picking up a package via a UAV includes: navigating the UAV to a serviceable point, the UAV including a UAV frame, a package carrying device coupled to the UAV frame, the package carrying device including an engagement housing selectively coupled to the UAV frame, and a package carrying arm positioned below the engagement housing. The method further includes detecting a package at the serviceable point using a camera of the UAV, navigating the UAV to a position above the package, and reducing the power of the UAV's propulsion components to lower the UAV above the package. The method further includes lowering a ground sensor of the package carrying device to engage the package carrying arm of the package carrying device with the package, and navigating the UAV from the serviceable point to a UAV support mechanism.

[0022] In another embodiment, a method for picking up a package via a UAV includes: navigating the UAV to a serviceable point, the UAV including a UAV rack, a package carrying device coupled to the UAV rack, the package carrying device including an engagement housing selectively coupled to the UAV rack, and a package carrying mechanism positioned below the engagement housing. The method further includes landing the UAV at the serviceable point and deactivating the UAV's propulsion component, receiving notification via a UAV computing entity that the package has engaged with the engagement housing of the package carrying device, and engaging the UAV's propulsion component and navigating the UAV from the serviceable point to the UAV support mechanism.

[0023] In yet another embodiment, an enhanced parcel delivery system for delivering parcels via UAVs includes: a primary delivery vehicle and a UAV support mechanism coupled to the primary delivery vehicle, the UAV support mechanism being configured to support one or more UAVs. Each of the system's multiple UAVs includes a UAV frame and a parcel carrying device. The UAV frame includes multiple propulsion members configured to provide lift to the UAV frame. The parcel carrying device includes an engagement housing configured to be secured to the UAV frame. Each parcel carrying device includes a parcel carrying mechanism coupled to and positioned below the engagement housing, wherein the parcel carrying mechanism is configured to engage and hold the parcel for delivery.

[0024] In yet another embodiment, a method for providing notification regarding package delivery via a UAV includes: after navigating the UAV to a serviceable point, establishing a direct communication link between the UAV computing entity and a user computing entity via the UAV computing entity, wherein (a) the UAV includes the UAV computing entity, a UAV rack, and a package carrier coupled to the UAV rack; (b) the package carrier includes a coupling housing selectively coupled to the UAV rack; (c) the package carrier engages with the coupling housing and secures the package to the coupling housing; and (d) the user computing entity is associated with a serviceable point. The method further includes releasing the package from the package carrier of the package carrier, and after releasing the package from the package carrier of the package carrier, providing notification to the user computing entity via the direct communication link through the UAV computing entity, wherein the notification includes information instructing the release of the package at the serviceable point.

[0025] In one embodiment, the UAV computing entity includes at least one processor and at least one memory, the memory including program code configured to establish a communication link between the UAV computing entity and a user computing entity via the processor, at least after navigating the UAV to a serviceable point, wherein (a) the UAV includes the UAV computing entity, a UAV rack, and a package carrier coupled to the UAV rack, (b) the package carrier includes a engagement housing selectively coupled to the UAV rack, (c) a package carrier mechanism engages with the engagement housing and secures a package to the engagement housing, and (d) the user computing entity, associated with a serviceable point, releases the package from the package carrier mechanism of the package carrier. After releasing the package from the package carrier mechanism of the package carrier, the UAV computing entity is configured to provide a notification to the user computing entity via the communication link, wherein the notification includes information instructing the package to be released at the serviceable point.

[0026] In another embodiment, a method for landing a unmanned aerial vehicle (UAV) on a UAV support structure includes: navigating the UAV toward the UAV support structure, receiving signals from a guidance array of the UAV support structure, and navigating the UAV to a landing area of ​​the UAV support structure. The method further includes guiding a reduced-width portion of the UAV between opposing guide rails of the UAV support structure and engaging the UAV with the UAV support structure, and moving the UAV from the landing area toward a return area of ​​the UAV support structure.

[0027] In one embodiment, a method for initiating package delivery via drone includes: for each of a first plurality of packages to be delivered by a carrier, electronically storing package data, the package data including: (a) a first logical group identifier corresponding to a first logical group, wherein each of the first plurality of packages is associated with the first logical group, and (b) a corresponding package identifier for each of the first plurality of packages. The method further includes: for each of a second plurality of packages to be delivered by the carrier, electronically storing package data, the package data including: (a) a second logical group identifier corresponding to a second logical group, wherein each of the second plurality of packages is associated with the second logical group, and (b) a corresponding package identifier for each of the second plurality of packages. The method further includes: electronically setting a current logical group identifier to the first logical group identifier; in response to receiving an indication from the second plurality of packages that a first package will be delivered by the carrier, determining whether the logical group identifier of the first package is the same as the current logical group identifier; and in response to determining that the logical group identifier of the first package is different from the current logical group identifier, initiating delivery of the second package from the second plurality of packages via drone.

[0028] In another embodiment, the system includes at least one processor and at least one memory, the memory including program code, the at least one memory and the program code being configured by the processor to cause the system to electronically store package data for at least each of a first plurality of packages to be delivered by a carrier, the package data including (a) a first logical group identifier corresponding to a first logical group, wherein each of the first plurality of packages is associated with the first logical group, and (b) a corresponding package identifier for each of the first plurality of packages. For each of a second plurality of packages to be delivered by the carrier, the system is further configured to electronically store package data including (a) a second logical group identifier corresponding to a second logical group, wherein each of the second plurality of packages is associated with the second logical group, and (b) a corresponding package identifier for each of the second plurality of packages. The system is further configured to electronically set a current logical group identifier to the first logical group identifier, and in response to receiving an indication from the second plurality of packages that a first package will be delivered by the carrier, determine whether the logical group identifier of the first package is the same as the current logical group identifier. In response to determining that the logical group identifier of the first package is different from the current logical group identifier, the system is further configured to initiate delivery of the second package from the second plurality of packages via a drone. Attached Figure Description

[0029] Now refer to the accompanying drawings, which are not necessarily drawn to scale, and in which:

[0030] Figure 1 A vehicle and several associated UAVs are schematically depicted according to one embodiment shown and described herein;

[0031] Figure 2 An embodiment according to which this document is shown and described is illustrated schematically. Figure 1 A perspective view of the UAV and its associated package carrier;

[0032] Figure 3 An embodiment according to which this document is shown and described is illustrated schematically. Figure 1 A top view of the UAV;

[0033] Figure 4 An embodiment according to which this document is shown and described is illustrated schematically. Figure 1 A bottom-view perspective view of the UAV rack;

[0034] Figure 5 An embodiment according to which this document is shown and described is illustrated schematically. Figure 2 Exploded perspective view of the UAV and package carrier;

[0035] Figure 6 An embodiment according to which this document is shown and described is illustrated schematically. Figure 2 A bottom perspective view of the UAV and the package carrier;

[0036] Figure 7 An embodiment according to which this document is shown and described is illustrated schematically. Figure 2 A bottom view of the UAV rack and package carrier;

[0037] Figure 8 A cross-sectional view of a retaining member assembly of a UAV rack according to one embodiment shown and described herein is schematically depicted;

[0038] Figure 9 An embodiment according to which this document is shown and described is illustrated schematically. Figure 5 A perspective view of the package carrier and the package;

[0039] Figure 10 An embodiment according to which this document is shown and described is illustrated schematically. Figure 1 A front view of the UAV and various sensors;

[0040] Figure 11 An embodiment according to which this document is shown and described is illustrated schematically. Figure 1 Top-view perspective view of the UAV and ground landing sensors;

[0041] Figure 12 A UAV control system according to one embodiment shown and described herein is schematically depicted;

[0042] Figure 13 A package carrier controller according to one embodiment shown and described herein is schematically depicted;

[0043] Figure 14 An embodiment according to which this document is shown and described is illustrated schematically. Figure 1 Top-view perspective view of the UAV and ground landing sensors;

[0044] Figure 15 An embodiment according to which this document is shown and described is illustrated schematically. Figure 1 Top-view perspective view of the UAV and ground landing sensors;

[0045] Figure 16 A perspective view of a package according to one embodiment shown and described herein is schematically depicted;

[0046] Figure 17 A perspective view of a package carrier and a package according to one embodiment shown and described herein is schematically depicted.

[0047] Figure 18 A perspective view of a package carrier and a package according to one embodiment shown and described herein is schematically depicted.

[0048] Figure 19 A perspective view of a package carrier and a package housing according to one embodiment shown and described herein is schematically depicted.

[0049] Figure 20 A perspective view schematically depicting a package carrier and another package housing according to one embodiment shown and described herein;

[0050] Figure 21A The diagram schematically depicts a closed position according to one embodiment shown and described herein. Figure 20 A side view of the encased shell;

[0051] Figure 21B The diagram schematically depicts a closed position according to one embodiment shown and described herein. Figure 20 A side view of the encased shell;

[0052] Figure 22 A bottom perspective view of a UAV including a landing arm according to one embodiment shown and described herein is schematically depicted.

[0053] Figure 23A A schematic front view of another UAV rack and package carrier according to an embodiment shown and described herein is depicted.

[0054] Figure 23B A schematic front view of another UAV rack and package carrier according to an embodiment shown and described herein is depicted.

[0055] Figure 24 The illustration schematically depicts a UAV support mechanism according to one embodiment shown and described herein. Figure 1 Rear perspective view of the vehicle;

[0056] Figure 25 An embodiment according to which this document is shown and described is illustrated schematically. Figure 24 A perspective view of the UAV support structure;

[0057] Figure 26A An embodiment according to which this document is shown and described is illustrated schematically. Figure 25 A sectional view of the UAV support mechanism along section 26A-26A;

[0058] Figure 26B An embodiment according to which this document is shown and described is illustrated schematically. Figure 26A Enlarged cross-sectional view of the UAV support mechanism;

[0059] Figure 27 A conveyor controller according to one embodiment shown and described herein is schematically depicted;

[0060] Figure 28 An embodiment according to which this document is shown and described is illustrated schematically. Figure 24 A front view of the UAV support mechanism relative to the guide rails;

[0061] Figure 29 The illustration schematically depicts a bracket-included device according to one embodiment shown and described herein. Figure 1 Rear perspective view of the vehicle;

[0062] Figure 30 The illustration schematically depicts a robot-based embodiment according to one of the embodiments shown and described herein. Figure 1 Rear perspective view of the vehicle;

[0063] Figure 31 A robot controller according to one embodiment shown and described herein is schematically depicted;

[0064] Figure 32 A perspective view of an automated parcel carrying device / parcel connection system according to one embodiment shown and described herein is schematically depicted;

[0065] Figure 33 An embodiment according to which this document is shown and described is illustrated schematically. Figure 1 Rear perspective view of vehicles and parcel conveyors;

[0066] Figure 34 An embodiment according to which this document is shown and described is illustrated schematically. Figure 33 Package conveyor and Figure 30 The robot;

[0067] Figure 35A The illustration schematically depicts the loading of a package and a package carrier into a container according to one embodiment shown and described herein. Figure 29 A perspective view of the robot's bracket;

[0068] Figure 35B The illustration schematically depicts the loading of a package and a package carrier into a container according to one embodiment shown and described herein. Figure 29 A perspective view of the robot's bracket;

[0069] Figure 35C The illustration schematically depicts the loading of a package and a package carrier into a container according to one embodiment shown and described herein. Figure 29 A perspective view of the robot's bracket;

[0070] Figure 36 The illustration schematically depicts a UAV-included device according to one embodiment shown and described herein. Figure 25 A perspective view of the UAV support structure;

[0071] Figure 37 An embodiment according to which this document is shown and described is illustrated schematically. Figure 36 A sectional view of the UAV support mechanism along section 37-37;

[0072] Figure 38A The illustration schematically depicts an embodiment utilizing [the technology] shown and described herein. Figure 30 The robot loads the package into the UAV rack;

[0073] Figure 38B The illustration schematically depicts an embodiment utilizing [the technology] shown and described herein. Figure 30 The robot loads the package into the UAV rack;

[0074] Figure 38C The illustration schematically depicts an embodiment utilizing [the technology] shown and described herein. Figure 30 The robot loads the package into the UAV rack;

[0075] Figure 39 An embodiment according to which this document is shown and described is illustrated schematically. Figure 1 means of transportation and Figure 24 Rear perspective view of the UAV support mechanism;

[0076] Figure 40 An embodiment according to which this document is shown and described is illustrated schematically. Figure 24 Side view of the UAV and UAV support mechanism;

[0077] Figure 41 An embodiment according to which this document is shown and described is illustrated schematically. Figure 28 The relative guide rails and the front view of the UAV;

[0078] Figure 42A The illustration schematically depicts the removal of the package carrier from the UAV rack and the movement of the package carrier to a tray according to one embodiment shown and described herein. Figure 30 A perspective view of the robot;

[0079] Figure 42B The illustration schematically depicts the removal of the package carrier from the UAV rack and the movement of the package carrier to a tray according to one embodiment shown and described herein. Figure 30A perspective view of the robot;

[0080] Figure 43 A rear perspective view of another vehicle including a bracket according to one embodiment shown and described herein is schematically depicted.

[0081] Figure 44 The illustration schematically depicts an embodiment according to what is shown and described herein, including... Figure 24 A front perspective view of another vehicle supporting the UAV support mechanism;

[0082] Figure 45A A rear perspective view of a vehicle including a landing pad according to one embodiment shown and described herein is schematically depicted.

[0083] Figure 45B A front perspective view of another vehicle including a landing pad according to one embodiment shown and described herein is schematically depicted;

[0084] Figure 46 The interconnectivity of computing entities according to one embodiment shown and described herein is schematically depicted;

[0085] Figure 47 A central computing entity according to one embodiment shown and described herein is schematically depicted;

[0086] Figure 48 A user computing entity according to one embodiment shown and described herein is illustrated schematically;

[0087] Figure 49 A UAV computing entity according to one embodiment shown and described herein is schematically depicted;

[0088] Figure 50 A flowchart illustrating operations and processes that can be used according to the various embodiments shown and described herein is schematically depicted;

[0089] Figure 51 An area comprising one or more serviceable points is schematically depicted according to one embodiment shown and described herein;

[0090] Figure 52 An area comprising one or more serviceable points is schematically depicted according to one embodiment shown and described herein;

[0091] Figure 53 An area comprising one or more serviceable points is schematically depicted according to one embodiment shown and described herein;

[0092] Figure 54A flowchart illustrating operations and processes that can be used according to the various embodiments shown and described herein is schematically depicted;

[0093] Figure 55 A flowchart illustrating operations and processes that can be used according to the various embodiments shown and described herein is schematically depicted;

[0094] Figure 56 A flowchart illustrating operations and processes that can be used according to the various embodiments shown and described herein is schematically depicted;

[0095] Figure 57 A flowchart illustrating operations and processes that can be used according to the various embodiments shown and described herein is schematically depicted;

[0096] Figure 58 A serviceable point according to one embodiment shown and described herein is schematically depicted;

[0097] Figure 59 A flowchart illustrating operations and processes that can be used according to the various embodiments shown and described herein is schematically depicted;

[0098] Figure 60 A flowchart illustrating operations and processes that can be used according to the various embodiments shown and described herein is schematically depicted;

[0099] Figure 61 A flowchart illustrating operations and processes that can be used according to the various embodiments shown and described herein is schematically depicted;

[0100] Figure 62 A flowchart illustrating operations and processes that can be used according to the various embodiments shown and described herein is schematically depicted;

[0101] Figure 63 A flowchart illustrating operations and processes that can be used according to the various embodiments shown and described herein is schematically depicted;

[0102] Figure 64 A flowchart illustrating operations and processes that can be used according to the various embodiments shown and described herein is schematically depicted;

[0103] Figure 65 A flowchart illustrating operations and processes that can be used according to the various embodiments shown and described herein is schematically depicted;

[0104] Figure 66 A flowchart illustrating operations and processes that can be used according to the various embodiments shown and described herein is depicted schematically; and

[0105] Figure 67An illustration shows a storage device according to one embodiment shown and described herein. Figure 47 Data tables in the central computing entity. Detailed Implementation

[0106] Various embodiments will now be described more fully below with reference to the accompanying drawings, which illustrate some, but not all, of the embodiments. In fact, the inventions described herein can be embodied in many different forms and should not be construed as limited to the embodiments illustrated herein; rather, these embodiments are provided to enable this disclosure to meet applicable legal requirements. Unless otherwise stated, the term “or” is used herein in both alternative and combined senses. The terms “illustrative” and “exemplary” are used for examples without an indication of quality level. Terms may be used interchangeably in singular and plural forms. The same numerals always refer to the same elements.

[0107] Benefiting from the teachings presented in the foregoing description and the accompanying drawings, those skilled in the art will conceive of many modifications and other embodiments of the invention set forth herein. Therefore, it should be understood that the invention is not limited to the specific embodiments disclosed, and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terminology is used herein, it is used only in a general and descriptive sense and not for limiting purposes.

[0108] As used herein, the vertical direction (e.g., the + / -Z direction as shown in the figures) refers to the upward / downward direction of the various components described herein. The longitudinal direction (e.g., the + / -X direction as shown in the figures) refers to the front / backward direction of the components described herein, and is transverse to the vertical direction. The transverse direction (e.g., the + / -Y direction as shown in the figures) refers to the transverse direction of the components described herein, and is transverse to both the vertical and longitudinal directions. Similarly, the terms pick-up and delivery are used interchangeably. That is, while many embodiments are described in the context of delivery, the same or similar features and functions can be applied to the context of pick-up.

[0109] As used herein, the term "package" can include any tangible and / or physical object. In one embodiment, a package can be or be encapsulated in one or more parcels, envelopes, parcels, bags, containers, loads, crates, bundled packages, vehicle parts, pallets, drums, etc., and / or similar terms that may be used interchangeably herein. Such packages can include the ability to communicate with each other (e.g., via chips (e.g., integrated circuit chips), RFID, NFC, Bluetooth, Wi-Fi, and any other suitable communication technology, standard, or protocol) and / or with various computing entities for a variety of purposes. In this regard, in some example embodiments, a package can convey sent "to" address information / data, received "from" address information / data, unique identifier codes, and / or various other information / data.

[0110] 1. Overview

[0111] Various embodiments of the present invention relate to an enhanced parcel delivery system for efficiently delivering parcels in a variety of environments. As described in detail herein, an enhanced parcel delivery system typically includes a primary parcel delivery vehicle (e.g., a conventional parcel delivery truck) and multiple auxiliary delivery vehicles, such as drones (“UAVs” or “unmanned aerial vehicles”). As described with respect to specific embodiments, the parcel delivery vehicle is adapted to act as a mobile hub for a group of UAVs configured to deliver parcels from the delivery vehicle to a delivery point / location (e.g., a home address or business location). In particular, the parcel delivery vehicle is configured to store parcels to be delivered via the UAVs and to provide takeoff (e.g., launch) and landing platforms for the UAVs to depart and return to the delivery vehicle. To facilitate the delivery of parcels from the delivery vehicle via UAVs, numerous novel systems have been developed, including, by way of example only, systems for securing and releasing parcels from the UAV, systems for powering the UAVs, systems for managing parcels within the delivery vehicle for delivery by the UAVs, and systems for guiding, controlling, and managing UAV-based deliveries. Each of these novel systems is described in more detail in this paper, along with various other improvements.

[0112] As will be understood from this disclosure, various embodiments of the enhanced parcel delivery system offer numerous advantages. For example, utilizing UAVs to deliver parcels from mobile hubs in the form of delivery vehicles provides greatly enhanced flexibility in delivering parcels in a variety of environments. In particular, UAVs can traverse diverse geographical areas faster and more efficiently than road-traveling vehicles. Furthermore, the enhanced parcel delivery system enables multiple UAVs to perform multiple deliveries simultaneously.

[0113] Using UAVs launched from shared delivery vehicles also saves fuel, especially in embodiments where the UAVs are battery-powered. Furthermore, UAV-based delivery improves the efficiency of human resources, for example, enabling a single driver or delivery person to manage deliveries or more packages in a shorter time. UAV-based delivery, particularly from mobile hubs in the form of delivery vehicles, allows for greater flexibility in package routing and fleet management.

[0114] Similarly, it enhances convenience for package users (e.g., recipients). As described herein, recipients of packages delivered by UAVs can set specific delivery locations and times and receive up-to-date and interactive information related to the delivery process. Various embodiments of the enhanced package delivery system will now be described in detail with reference to the accompanying drawings provided herein.

[0115] 2. Enhanced parcel delivery system

[0116] Figure 1 An enhanced parcel delivery system 2 according to one embodiment is shown. Figure 1 In one embodiment, the parcel delivery system 2 includes a main parcel delivery vehicle 10 and a plurality of UAVs 100 configured to deliver parcels 300 from the vehicle 10. According to various embodiments, the UAVs 100 are configured to be dispatched from the vehicle 10, deliver parcels 300 to a recipient location, and return to the vehicle 10.

[0117] exist Figure 1In the illustrated embodiment, the primary parcel delivery vehicle 10 is a parcel delivery truck configured to be manually driven by a parcel delivery driver. Alternatively, in some embodiments, the parcel delivery vehicle 10 may be autonomous, as will be described in more detail herein. The delivery vehicle 10 defines an internal parcel compartment for storing multiple parcels to be delivered by the UAV 100. As will be appreciated, although the primary parcel delivery vehicle 10 is described as a land vehicle, it may be a manned or unmanned ground vehicle, aircraft, marine vehicle, etc. For example, such a vehicle may include tractors, trucks, automobiles, motorcycles, mopeds, Segways, bicycles, golf carts, handcarts, trolleys, trailers, tractor and trailer combinations, vans, flatbed trucks, vehicles, drones, airplanes, helicopters, barges, boats, and / or any other form of object used to move or transport people and / or goods (e.g., one or more packages, parcels, bags, containers, loads, crates, bundled items, vehicle parts, pallets, drums, etc., and / or similar terms used interchangeably herein). The primary parcel delivery vehicle 10 may be a hybrid vehicle for standard manual and UAV delivery performed by a driver, assisting the driver in handling deliveries along a route. Alternatively, the primary parcel delivery vehicle 10 may be a manned or unmanned delivery vehicle dedicated to UAV delivery.

[0118] In one embodiment, the top deck of the delivery vehicle includes a UAV support mechanism 400, which serves as a package loading point and is configured to enable the UAV 100 to take off and land on the delivery vehicle 10. As will be explained in further detail, the delivery vehicle 10 is configured such that packages stored in the internal packaging compartments of the delivery vehicle can be automatically secured to one of the UAVs 100, such that the UAV securing the particular package can then take off from the top deck of the vehicle 10, deliver the package to the delivery location, and return to the vehicle 10 to land on the top deck. In this way, the delivery vehicle 10 serves as a mobile hub for UAV-based package delivery. Alternatively, in some embodiments, the UAV 100 can take off from a building or other structure (e.g., a warehouse) and can return and land on the building or other structure.

[0119] The various components and features of the enhanced parcel delivery system 2 will now be described in more detail.

[0120] A. Parcel delivery UAV and parcel carrying device

[0121] Figure 2A perspective view of a package delivery UAV 100 and a package carrier 200 is shown, the package carrier 200 being configured to be coupled to the UAV 100 and engage a package to achieve UAV-based package delivery. As will be discussed in more detail herein, the package carrier 200 is configured to be detachably attached to the UAV 100 for transporting a package 300 ( Figure 1 It may also include a power supply configured to supply power to the UAV 100 when the package carrier 200 is engaged with the UAV 100.

[0122] i. Package delivery UAV

[0123] like Figure 2 As shown, a package delivery UAV 100 typically includes a UAV frame 110 and a plurality of propulsion members 102 extending outward from the UAV frame. The UAV frame 110 typically defines the body of the UAV 100, and the propulsion members 102 are configured for lifting and guiding during flight. The propulsion members 102 can operate between an "on" setting and an "off" setting, wherein in the "on" setting, the propulsion members 102 provide lift to the UAV 100, and in the "off" setting, the propulsion members are stationary and / or do not provide lift to the UAV 100. According to various embodiments, the UAV frame 110 can be formed of any material (including sustainable and reusable materials) having suitable strength and weight, including but not limited to composite materials, aluminum, titanium, polymers, etc., and can be formed by any suitable process.

[0124] exist Figure 2 In the illustrated embodiment, UAV 100 is a hexacopter and includes six separate propulsion components 102, each extending outward from the UAV frame 110. However, as will be understood from the description herein, UAV 100 may include any number of propulsion components adapted to provide lift and guide UAV 100 during flight.

[0125] Figure 3 A top view of UAV 100 is shown, in which the propulsion member 102 is again shown extending outward from the periphery of the UAV frame 110. Figure 3 In the illustrated embodiment, each of the plurality of propulsion components 102 includes a propeller 103 positioned within a propeller housing 108. Each propeller 103 comprises a plurality of blades configured to rotate within the propeller housing 108 to provide lift and facilitate flight of the UAV 100. In the illustrated embodiment, the propeller housing 108 confines the propeller 103 as it rotates, which helps prevent unintentional contact between the propeller 103 and various objects that the UAV 100 may encounter during flight. Figure 3The embodiment shown depicts a propeller 103 comprising three blades configured to rotate within a propeller housing 108. It should be understood that the propeller 103 may include any suitable number of blades configured to rotate within the propeller housing 108 and provide sufficient lift to the UAV 100.

[0126] In the illustrated embodiment, the propulsion member 102 is electrically driven (e.g., by an electric motor controlling the rotational speed of the propeller 103). However, as will be appreciated, the propulsion member 102 can be powered by an internal combustion engine-driven alternator, a hydrogen fuel cell, etc. Each of the propulsion members 102 is pivotally coupled to the UAV frame 110 at an electric joint 104, such that each of the propulsion members 102 is rotatable relative to the UAV frame 110. Specifically, as Figure 3 As shown, each of the electric connectors 104 defines a connector shaft 105, and a corresponding propulsion member 102 of the connector shaft 105 rotates about the connector shaft 105 relative to the UAV frame 110. By rotating about the shaft 105 relative to the UAV frame 110, the propulsion members 102 can direct their respective lift during flight to maneuver the UAV 100. Furthermore, as described in more detail herein, the ability of the propulsion members 102 to pivot relative to the UAV frame 110 enables the propulsion members to maintain a constant or near-constant orientation of the UAV frame 110 relative to the package carrier 200 and the package 300 to prevent undesirable movement of the cargo located within the package 300.

[0127] Figure 4 A bottom-view perspective view of UAV 100 is shown. (As shown) Figure 4 As shown, the UAV rack 110 typically defines an upper portion 114, a lower portion 118 (located below the upper portion 114), and a width-reducing portion 115 (vertically positioned between the upper portion 114 and the lower portion 118). In the illustrated embodiment, a propulsion member 102 is coupled to and extends around the periphery of the upper portion 114 of the UAV rack 110. Additionally, as described in more detail herein, the upper portion 114 of the UAV rack houses the control system 150 of the UAV.

[0128] The lower part 118 of the UAV rack 110 is configured to receive and engage the package carrier 200. Figure 2 Thus, the lower portion 118 can alternatively be referred to herein as the "carrier receiving portion" of the UAV 100. In the illustrated embodiment, the lower portion 118 extends downward from the upper portion 114 of the UAV frame and resembles a hollow, inclined pyramid-shaped member. The lower portion 118 defines an inner cavity 119 that extends upward into the lower portion 118. The inner cavity 119 defines a bottom opening 117 through which access to the inner cavity 119 is made. As will be described in more detail herein, the carrier 200 ( Figure 2At least a portion of the package carrier 200 can be inserted through the opening 117 into the cavity 119 to selectively couple the package carrier 200 to the UAV rack 110.

[0129] like Figure 4 As shown, UAV 100 further includes at least one UAV electrical interface 130 located in a lower cavity 119. The electrical interface 130 includes electrical terminals, electrical contacts, etc., electrically coupled to the propulsion member 102. In the illustrated embodiment, the UAV electrical interface 130 provides an electrical connection to a power source (e.g., located in the package carrier 200) to provide power to the propulsion member 102, as will be described in more detail herein.

[0130] Figure 5 A side view of the UAV 100 and a perspective view of the package carrier 200 are shown. In the illustrated embodiment, the upper portion 114, lower portion 118, and width-reducing portion 115 of the UAV rack define a generally hourglass shape. Specifically, the upper portion 114 and lower portion 118 have a greater width (assessed in the lateral and / or longitudinal directions) compared to the width-reducing portion 115. Figure 5 In the illustrated embodiment, the width of the upper portion 114 gradually tapers downwards, such that the width of the upper portion 114 gradually decreases as it approaches the width-reducing portion 115. Similarly, the width of the lower portion 118 gradually tapers upwards, such that the width of the lower portion 118 gradually increases away from the width-reducing portion 115. As will be described in more detail herein, the hourglass profile of the UAV frame 110 allows it to engage with a UAV support mechanism 400 disposed on the roof of the package delivery vehicle 10, thereby enabling takeoff and landing from the roof. The UAV support mechanism 400 secures the UAV frame 110 to the roof, such that the UAV frame 110 remains fixed to the vehicle 10 as the vehicle 10 moves.

[0131] like Figure 4 and Figure 5 As shown, UAV 100 further includes landing gear 116. In the illustrated embodiment, landing gear 116 is disposed on the underside or downward-facing side of the upper portion 114 of the UAV frame. In the illustrated embodiment, landing gear 116 includes a pair of rollers oriented downward in a vertical direction. In some embodiments, power can be supplied to the rollers of landing gear 116 such that landing gear 116 can advance the UAV frame along UAV support mechanism 400. As will be described in more detail herein, landing gear 116 is configured to engage and be positioned on vehicle 10 when UAV 100 takes off from and lands on vehicle 10. Figure 1 The relative guide rail of the UAV support mechanism 400 on the ).

[0132] In various other embodiments, the landing gear 116 may also be laterally positioned on the opposite side of the width reduction portion 115 of the UAV frame, such that the landing gear 116 spans the width reduction portion 115. Furthermore, in various other embodiments, the landing gear 116 may include other devices, such as bearings, casters, etc., configured to engage relative rails of the UAV support mechanism 400, which rotate relative to the UAV frame 110, potentially facilitating rotation relative to the vehicle 10 ( Figure 1 The UAV frame 110 moves along the relative guide rails of the vehicle 10. Alternatively, in some embodiments, the landing gear 116 may include a slide plate or pad coupled to the UAV frame 110, the slide plate or pad being configured to engage a pair of opposing guide rails of the vehicle 10 and move along the relative guide rails of the vehicle 10. Figure 1 The landing gear 116 slides on a pair of opposing guide rails, as will be described in more detail herein. In an embodiment, the landing gear 116 may be formed of an elastic material that engages with the opposing guide rails of the UAV 100 and the vehicle 10. Figure 1 It can be elastically deformed.

[0133] ii. Package carrying device

[0134] like Figure 5 As shown, the package carrier 200 includes a connecting housing 210 and a package carrier mechanism 229, the package carrier mechanism 229 including a pair of package carrier arms 230 extending outwardly from the connecting housing 210. According to various embodiments, the connecting housing 210 of the package carrier defines a shape generally complementary to and corresponding to the inner cavity 119 of the lower portion 118 of the UAV rack 110. Figure 5 In the illustrated embodiment, the engagement housing 210 defines a generally inclined pyramid shape that complements the cavity 119 of the UAV rack. Therefore, the engagement housing 210 can be inserted into the cavity 119 of the lower portion 118 of the UAV rack 110 to selectively secure the package carrier 200 to the UAV 100 (as described herein). Figure 7 (To be discussed further). For example... Figure 5 As shown, the engagement housing 210 defines a greater width at its bottom (assessed in the lateral direction) compared to the width at its top.

[0135] In the illustrated embodiment, the engagement housing 210 of the package carrier includes a power source 214 configured to supply power to the UAV 100 and the package carrier 200. Specifically, the power source 214 is configured to supply power to the UAV 100 and the package carrier 200 when the engagement housing 210 is engaged in the cavity 119 of the lower portion 118 of the UAV frame. In the illustrated embodiment, the power source 214 includes a battery. However, it will be understood from the description herein that the power source 214 may include any suitable means for supplying power to the UAV 100 and the package carrier 200 (e.g., a hydrogen fuel cell, etc.).

[0136] like Figure 5 As shown, the package carrier 200 includes at least one carrier electrical interface 220 positioned on the upper surface of its engagement housing 210. The carrier electrical interface 220 includes electrical terminals, electrical contacts, etc., electrically coupled to a power supply 214. Specifically, the at least one carrier electrical interface 220 is configured to connect with the UAV electrical interface 130 when the package carrier 200 is fixed to the UAV 100. Figure 4 The power supply 214 is connected to the UAV frame 110 and provides power to the propulsion component 102.

[0137] As explained in more detail herein, the propulsion component 102 provides lift to the UAV 100, consuming electrical energy and depleting the charge and / or power of the power source 214. Since the engagement housing 210 and the corresponding power source 214 are removable from the UAV rack 110, the engagement housing 210 with the depleted power source 214 can be replaced with an engagement housing 210 with the charged power source 214. By periodically replacing the power source 214, a continuous and sufficient power supply can be provided to the UAV 100 to perform repetitive deliveries. According to some embodiments, since the power source 214 is included within the engagement housing 210, the engagement housing 210 is configured to be selectively coupled to the package 300. Figure 9 Each time 300 packages are delivered, power supply 214 can be replaced to UAV 100, as will be described in more detail in this article.

[0138] like Figure 5 As shown, a pair of package-carrying arms 230 of the package-carrying device extend outward from the lateral sides of the engaging housing 210. Specifically, in Figure 5 In the illustrated embodiment, the package support arm 230 extends outward from the lower portion of the engagement housing 210. As discussed in more detail herein, this makes the engagement housing 210 substantially unobstructed to allow engagement with the lower portion 118 of the UAV housing 110.

[0139] In the illustrated embodiment, the package carrier 200 is substantially symmetrical, and the package carrier arms 230 on the opposite side of the engaging housing 210 are substantially identical. Figure 5As shown, each of the package support arms 230 includes an upper portion 232 extending laterally outward from the engagement housing 210, a lower portion 234 extending downward from the upper portion 232, and a package guide 235 positioned on the bottom of the lower portion 234 and oriented laterally to the lower portion 234. A plurality of pins 236 extend laterally from the package guides 235 toward the package 300 and are selectively positioned to engage corresponding holes 312 defined by the package 300. Figure 9 The package support arm 230 and the plurality of pins 236 can be formed from any suitable material (e.g., metal, composite material, etc.) to support the package 300, and can be formed by any suitable manufacturing process, such as casting, forging, etc.

[0140] Each of the package support arms 230 is slidably coupled to the engagement housing 210, such that the package support arm 230 is movable in the lateral direction relative to the engagement housing 210. Specifically, the package support arm 230 can be repositioned between an inwardly engaged position (e.g., where the package support arm 230 engages with the package 300) and an outwardly disengaged position (e.g., where the package support arm moves further outward and disengages from the package 300). Alternatively, in various other embodiments, the package support arm 230 is pivotally coupled to the engagement housing 210, such that the package support arm 230 is movable in the lateral direction relative to the engagement housing 210, for example by pivoting about an axis parallel to the illustrated longitudinal direction.

[0141] In an embodiment, the package support arm 230 may be biased inward in the lateral direction, such that the package support arm 230 is laterally oriented towards the package 300. Figure 9 The package support arm 230 can be biased inward by a biasing member (e.g., a tension spring, a torsion spring, a compression spring, etc.). In this way, the package support arm 230 can be biased to an engaged position where a plurality of pins 236 are positioned in the hole 312 of the package 300. Figure 9 To move the package carrier arm 230 from an engaged position to a disengaged position, the package carrier arm 230 is coupled to a motor 213 configured to overcome an inward bias of the package carrier arm 230, causing the package carrier arm 230 to move outward in the lateral direction to the disengaged position. The motor 213 can be communicatively coupled to a package carrier controller 212 that controls the operation of the motor 213, and can be commanded to move the package carrier arm 230 from the engaged position to the disengaged position. By biasing the package carrier arm 230 in the inward lateral direction, the package carrier arm 230 can engage packages 300 having different widths evaluated in the lateral direction.

[0142] The package carrier 200 further includes a ground detector 250 extending downward from the engagement housing 210. Figure 5In the illustrated embodiment, the ground detector 250 is coupled to the engagement housing 210 via the package support arm 230. Alternatively, the ground detector 250 may be directly coupled to the engagement housing 210 or directly coupled to the package 300.

[0143] iii. Connection between UAV and package carrier

[0144] Figure 6 A perspective view of the package carrier 200 coupled to the UAV 100 is shown. (As shown) Figure 6 As shown, when the package carrier 200 is installed onto the UAV rack 110, the engagement housing 210 is held within the cavity 119 of the lower part 118 of the UAV rack 110. Figure 4 Inside. In the illustrated embodiment, the engaging housing 210 is held within the inner cavity 119 by a retaining member 120. Specifically, Figure 7 A bottom view of the lower part 118 and the inner cavity 119 (in which the engagement housing 210 is inserted) of the UAV is shown. Figure 7 As shown, the retaining member 120 extends inwardly into the cavity 119 of the UAV frame 110 in the transverse and / or longitudinal directions, thereby extending below the lower surface of the engagement housing 210 and retaining the engagement housing 210 within the cavity 119 by mechanical interference. As described above, the engagement housing 210 and the cavity 119 of the UAV frame 110 have complementary shapes. When the engagement housing 210 is mounted into the cavity 119, the engagement housing 210 can be partially or completely fitted within the cavity 119, and once positioned within the cavity 119, it can be retained within the cavity by one or more retaining members 120.

[0145] The retaining member 120 is movable relative to the cavity 119 of the UAV frame 110, such that each of the retaining members 120 moves inward into the cavity 119 and outward from the cavity 119. Figure 8 A cross-sectional side view of one of the retaining members 120 of a UAV rack according to one embodiment is provided. Figure 8 As shown, retaining member 120 is configured as part of a retaining member assembly, which includes retaining member 120, bias spring 125, and solenoid actuator 127. In the illustrated embodiment, retaining member 120 defines an inclined sidewall 121 and an upper wall 122. Retaining member 120 is substantially mounted within the wall of the lower portion 118 of the UAV rack and configured to move laterally relative to that wall. In particular, the ability of retaining member to move laterally allows it to extend inward into the lower cavity 119 (in the extension direction) or recess into the lower wall (in the retraction direction).

[0146] exist Figure 8In the illustrated embodiment, the retaining member 120 is biased in its extending direction by a spring 125. In this direction, the inclined sidewall 121 and top wall 122 of the retaining member each extend into the cavity 119. When the engaging housing 210, which encloses the carrier device, is inserted into the cavity 119 of the UAV, the engaging housing 210 contacts the inclined sidewall 121 of the retaining member and pushes the retaining member 120 laterally into its retraction direction. Once the bottom edge of the engaging housing 210 has penetrated beyond the plane of the top wall 122 of the retaining member, the spring 125 pushes the retaining member 120 back into its extending direction. In this configuration, the retaining member 120 extends back into the cavity 119 such that the bottom edge of the engaging housing rests on the top wall 122 of the retaining member, thereby securing the engaging housing 210 within the cavity 119 of the UAV frame.

[0147] When the engagement housing 210 is to be released from the UAV frame 110, the UAV control system 150 actuates the solenoid 127, which is configured to push the retaining member 120 laterally back to its retracted direction (overcoming the force of the bias spring 125). This movement retracts the top wall 122 of the retaining member into the wall of the lower portion 118 of the UAV frame, leaving an unobstructed path for the engagement housing 210 to disengage from the lower cavity 119. According to various embodiments, a configuration involving [missing information] can be provided around the inner periphery of the lower portion 118 of the UAV frame. Figure 8 Multiple retaining member assemblies of the type shown and described. Furthermore, as can be understood from the description herein, any suitable method can be used to actuate the retaining member 120 between the extension and retraction directions, enabling the engagement housing 210 to be held within the lower portion 118 of the UAV frame.

[0148] iv. Connection between the package carrier and the package

[0149] Figure 9 A package 300 is shown fixed to a package carrier 200. As described above, the package carrier 200 includes a package carrier arm 230 extending outward from the engagement housing 210. Figure 9 The image shows the package-carrying arm 230 in its inwardly engaged position, securing the package 300 to the package-carrying device 200. Meanwhile... Figure 9 In the illustrated embodiment, one of the package-carrying arms 230 is obscured by the package 300. It should be understood that the package-carrying devices 200 are substantially symmetrical and the package-carrying arms 230 on the opposite side of the package 300 are substantially identical.

[0150] exist Figure 9In the illustrated embodiment, a plurality of pins 236 of the package support arm extend laterally from the package guide 235 toward the package 300 and are selectively positioned to engage corresponding holes 312 defined in the package 300. In the illustrated embodiment, holes 312 are pre-formed in the side of the package 300 at locations corresponding to the placement of the pins 236 on the guide 235. However, in an alternative embodiment, the plurality of pins 236 may be configured to pierce the side of the package 300 during engagement to form holes for clamping and securing the package 300 by the plurality of pins 236. In some embodiments, holes 312 are pre-formed in the side of the package 300, and in some embodiments, the holes 312 may be reinforced to support the weight of the package 300 when engaged with the plurality of pins 236. Alternatively, in some embodiments, the plurality of pins 236 may form holes within the package 300 when the package 300 is engaged. In other words, the pins 236 may pierce the package 300 to form holes 312. In other embodiments, package 300 may include a perforated or reduced-thickness area that can be pierced by pin 236 to form hole 312.

[0151] Package carrier arm 230 selectively engages package 300 via engagement between multiple pins 236 and holes 312, such that when package carrier 200 is coupled to UAV rack 110, package 300 can be selectively coupled to UAV 100. Figure 6 Alternatively, in some embodiments, package 300 may include a plurality of pins that can be selectively inserted into holes defined on the guide rail 235 of the package carrier arm.

[0152] Ground probe 250 is configured to extend downwards from the bottom surface 310 of the package, measuring the distance “d” between the end of ground probe 250 and the bottom surface 310. Ground probe 250 is configured to detect when package 300 is placed on the landing surface, for example, when package 300 is launched by UAV 100 ( Figure 5 It can be delivered to the destination and can be communicatively coupled to the package carrier controller 212.

[0153] When package 300 is positioned on the surface, for example when via UAV 100 ( Figure 5When delivering package 300 to its destination, ground detector 250 may contact a surface before the bottom surface 310 of package 300. As package 300 descends toward a surface (e.g., the ground), ground detector 250 may contact the surface and deflect and / or elastically deform in the vertical direction. Alternatively, in some embodiments, ground detector 250 may be a vertically foldable telescopic detector, and ground detector 250 may fold in the vertical direction upon contact with a surface (e.g., the ground). When ground detector 250 contacts the surface, ground detector 250 sends a signal to package carrier controller 212, which then commands motor 213 to reposition package carrier arm 230 from an engaged position to a disengaged position, thereby separating package 300 from package carrier 200. In this way, ground detector 250 can help ensure that package 300 is not released from package carrier 200 until package 300 is positioned on or near a surface, such as the landing surface to which package 300 will be delivered. By ensuring the package is positioned on or near the surface, damage to the package 300 can be minimized compared to when the package is released from the package carrier 200 at a height above the landing surface. While the ground detector 250 is described herein as including a detector extending downwards from the package carrier arm 230, it should be understood that the ground detector 250 may include any suitable sensor for detecting the distance between the bottom surface 310 of the package and the surface, such as, but not limited to, proximity sensors, lidar sensors, sonar sensors, etc.

[0154] v.UAV control system

[0155] In various embodiments, UAV 100 includes a UAV control system 150 that includes a plurality of sensors that aid in navigating UAV 100 during flight. These sensors are configured to detect objects around UAV 100 and provide feedback to UAV computing entity 808 to help guide UAV 100 in performing various operations, such as takeoff, flight navigation, and landing, which will be described in more detail herein.

[0156] Figure 10 and 11 The illustration shows a package carrier 200 secured to a package 300 and further secured to a UAV 100 for delivery. In the illustrated embodiment, the UAV 100 includes multiple sensors, including a ground landing sensor 162, a vehicle landing sensor 164, a flight guidance sensor 166, and one or more cameras 168. The vehicle landing sensor 164 is positioned on the lower part 118 of the UAV frame 110 and assists in landing the UAV 100 on the vehicle 100. Figure 1The vehicle landing sensor 164, which will be described in more detail herein, may include one or more cameras (e.g., video cameras and / or still cameras), one or more altitude sensors (e.g., lidar sensors, laser-based distance sensors, infrared distance sensors, ultrasonic distance sensors, optical sensors, etc.). Located on the lower part 118 of the UAV frame 110, the vehicle landing sensor 164 is positioned below the propulsion member 102 and approaches the vehicle 100 during landing. Figure 1 The guide rail opposite the UAV support mechanism 400 of the delivery vehicle has a line of sight ( Figure 1 This will be described in more detail in this article.

[0157] One or more cameras 168 of the UAV are also positioned on the lower part 118 of the UAV frame 110, on the propeller shield 108, on the ground sensor 250, etc. The one or more cameras 168 may include video cameras and / or stationary cameras, and may capture images and / or videos of the UAV 100 in flight during delivery, and may help verify or confirm that package 300 has been delivered to its destination, as will be described in more detail herein. The one or more cameras 168 located on the lower part 118 of the UAV frame 110 are positioned below the propulsion member 102 and have an unobstructed line of sight to observe the flight of the UAV 100.

[0158] The flight guidance sensor 166 of the UAV is also positioned on the lower part 118 of the UAV frame 110. The flight guidance sensor 166 may include lidar, LiDAR, laser detection and ranging, sonar, magnetic field sensors, radar sensors, etc., and can be configured to "sensor and avoid" objects that the UAV 100 may encounter during flight. For example, the flight guidance sensor 166 can be configured to detect objects located around the UAV 100, allowing the UAV 100 to determine an appropriate flight path to avoid contact with the objects. By positioning the flight guidance sensor 166 on the lower part 118 of the UAV frame 110, the flight guidance sensor 166 is positioned below the propulsion member 102 and has an unobstructed line of sight to observe the flight of the UAV 100.

[0159] Special Reference Figure 11 The UAV's ground landing sensor 162 is coupled to the upper part 114 of the UAV rack 110. Figure 11In the illustrated embodiment, the ground landing sensor 162 is coupled to the propulsion member 102 at the outer periphery of its respective propeller shield 108. According to various embodiments, the ground landing sensor 162 is typically configured to detect the distance between the UAV and a surface positioned within its line of sight 163. For example, during flight, the ground landing sensor 162 may detect the distance between the UAV and a landing surface (e.g., the ground or the top of the package delivery vehicle 10). By detecting the distance between the UAV 100 and the landing surface, the ground landing sensor 162 can assist in the takeoff and landing of the UAV 100. According to various embodiments, the ground landing sensor 162 may include a sonar sensor, a lidar sensor, an IR-lock sensor, an infrared distance sensor, an ultrasonic distance sensor, a magnetic field sensor, a radar sensor, etc.

[0160] In some embodiments, the ground landing sensor 162 may be pivotally coupled to the propeller shield 108, allowing the ground landing sensor 162 to rotate relative to the propeller shield 108. As described above, the propulsion member 102 may pivot relative to the UAV frame 110. Therefore, the ground landing sensor 162 may pivot relative to the propeller shield 108 such that when the propeller shield 108 pivots relative to the UAV frame 110, the ground landing sensor 162 can maintain a line of sight 163 pointing downward toward the landing surface.

[0161] exist Figure 11 In the illustrated embodiment, the ground landing sensor 162 is positioned outside the maximum package envelope 302 where the package 300 is located. Specifically, the maximum package envelope 302 defines the largest area where the package 300 is located when the package is selectively coupled to the UAV 100. When the ground landing sensor 162 is coupled to the propulsion member 102, the ground landing sensor 162 is positioned outside the maximum package envelope 302 defined by the package 300, and each of the ground landing sensors 162 can maintain an unobstructed line of sight 163 to the landing surface. For example, the ground landing sensors 162 are positioned such that they are located outside the maximum package envelope 302 acceptable to the carrier arm 230 of the package carrier.

[0162] Common Reference Figure 3 and Figure 12UAV 100 includes a UAV control system 150. The UAV control system includes a UAV computing entity 808, which is communicatively coupled to one or more sensing elements. Generally, the terms used interchangeably herein—computing entity, computer, entity, device, system, and / or similar terms—may refer to, for example, one or more computers, computing entities, desktop computers, tablet computers, phablets, laptops, distributed systems, servers or server networks, blade servers, gateways, switches, processing devices, processing entities, relays, routers, network access points, base stations, etc., and / or any combination of devices or entities suitable for performing the functions, operations, and / or processes described herein. These functions, operations, and / or processes may include, for example, the terms used interchangeably herein: transmit, receive, operate, process, display, store, determine, create / generate, monitor, evaluate, compare, and / or similar terms. In one embodiment, these functions, operations, and / or processes may be performed on information / data, content, information, and / or similar terms used interchangeably herein.

[0163] like Figure 13 As shown, in one embodiment, the UAV computing entity 808 may include or communicate with one or more processing elements / components 902 (also referred to as processors, processing circuitry, processing devices, and / or similar terms used interchangeably herein), which communicate with other elements / components within the UAV computing entity 808 via, for example, a bus. As will be understood, the processing elements / components 902 may be embodied in a variety of different ways. For example, the processing element / component 902 may be embodied as one or more complex programmable logic devices (CPLDs), “cloud” processors, microprocessors, multi-core processors, coprocessor entities, application-specific instruction set processors (ASIPs), microcontrollers, and / or controllers. Furthermore, the processing element / component 902 may be embodied as one or more other processing devices or circuitry. The term “circuit” can refer to a completely hardware embodiment or a combination of hardware and computer program products. Thus, the processing element / component 902 may be embodied as an integrated circuit, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a programmable logic array (PLA), a hardware accelerator, other circuitry, etc. Therefore, it will be understood that the processing element / component 902 can be configured for a specific purpose or configured to execute instructions stored in or accessible by the processing element / component 902 on a volatile or non-volatile medium. Thus, whether configured as a hardware or computer program product, or by a combination thereof, the processing element / component 902, when configured accordingly, is capable of performing steps or operations according to embodiments of the invention.

[0164] In one embodiment, the UAV computing entity 808 may further include or communicate with a memory component / element (e.g., a non-volatile medium (also referred to as non-volatile memory, memory, storage device, memory circuitry, and / or similar terms used interchangeably herein)). In one embodiment, the non-volatile storage device or memory may include one or more non-volatile memories or storage media 904, including but not limited to hard disks, ROMs, PROMs, EPROMs, EEPROMs, flash memory, MMC, SD memory cards, Memory Sticks, CBRAMs, PRAMs, FeRAMs, NVRAMs, MRAMs, RRAMs, SONOS, FJG RAMs, Millipede memory, track memory, etc. It will be appreciated that non-volatile memories or storage media can store databases, database instances, database management systems, information / data, applications, programs, program modules, scripts, source code, object code, bytecode, compiled code, interpreted code, machine code, executable instructions, etc. The terms database, database instance, database management system, and / or similar terms used interchangeably herein refer to a collection of records or data stored in a computer-readable storage medium, using one or more database models, such as hierarchical database models, network models, relational models, entity-relational models, object models, document models, semantic models, graph models, etc.

[0165] In one embodiment, the memory component / element may further include or communicate with volatile media (also referred to as volatile memory, memory, storage device, memory circuitry and / or similar terms used interchangeably herein). In one embodiment, the volatile storage device or memory may further include one or more volatile memories or storage media 906, including but not limited to random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), fast page mode dynamic random access memory (FPM DRAM), extended data output dynamic random access memory (EDO DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), double data rate type 2 synchronous dynamic random access memory (DDR2 SDRAM), double data rate type 3 synchronous dynamic random access memory (DDR3 SDRAM), Rambus dynamic random access memory (RDRAM), dual transistor RAM (TTRAM), thyristor RAM (T-RAM), zero capacitance (Z-RAM), Rambus through-hole memory module (RIMM), dual in-line memory module (DIMM), single in-line memory module (SIMM), video random access memory (VRAM), cache (including various levels), flash memory, register memory, etc. It will be appreciated that volatile memory or storage media can be used to store at least a portion of databases, database instances, database management systems, information / data, applications, programs, program modules, scripts, source code, object code, bytecode, compiled code, interpreted code, machine code, executable instructions, and / or similar entities executed by, for example, processing element / component 902. Therefore, databases, database instances, database management systems, information / data, applications, programs, program modules, scripts, source code, object code, bytecode, compiled code, interpreted code, machine code, executable instructions, etc., can be used, with the assistance of processing element / component 902 and operating system, to control certain aspects of the operation of UAV computing entity 808.

[0166] As shown, in one embodiment, the central computing entity 802 may further include one or more communication components / elements 908 for communicating with various computing entities, for example by transmitting information / data, content, information, and / or similar terms used interchangeably herein that can be sent, received, manipulated, processed, displayed, stored, etc. Such communication may be performed using wired data transmission protocols such as Fiber Distributed Data Interface (FDDI), Digital Subscriber Line (DSL), Ethernet, Asynchronous Transfer Mode (ATM), Frame Relay, Data Cable Services Interface Specification (DOCSIS), or any other wired transmission protocol. Similarly, the central computing entity 802 can be configured to communicate via a wireless external communication network using any of a variety of protocols, such as General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), CDMA2000 1X (lxRTT), Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications (GSM), GSM Evolution Enhanced Data Rate (EDGE), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Evolved Data Optimized (EVDO), High Speed ​​Packet Access (HSPA), High Speed ​​Downlink Packet Access (HSDPA), IEEE 802.11 (Wi-Fi), Wi-Fi Direct, 802.16 (WiMAX), Ultra Wideband (UWB), Infrared (IR) protocol, Near Field Communication (NFC) protocol, Wibree, Bluetooth protocol, Wireless Universal Serial Bus (USB) protocol, and / or any other wireless protocol.

[0167] In this embodiment, each of the ground landing sensor 162, the vehicle landing sensor 164, the flight guidance sensor 166, and one or more cameras 168 is communicatively coupled to the UAV computing entity 808, and in particular to the processing component 902 of the UAV computing entity 808. The UAV computing entity 808 can send and receive signals from the ground landing sensor 162, the vehicle landing sensor 164, the flight guidance sensor 166, and one or more cameras 168. The UAV computing entity 808 is also communicatively coupled to the propulsion member 102 and can command the propulsion member 102 to rotate, and / or can command the electric connector 104 to pivot the propulsion member 102 about a connector axis 105.

[0168] In addition, UAV 100 may include GPS sensors and / or other satellite system sensors for detecting the current position of the UAV relative to its intended destination (e.g., destination location and / or vehicle). In various embodiments, UAV control system 150 may include communication ports (e.g., 3G, 4G, 5G communication ports) so that UAV control system 150 can communicate with one or more other computing entities.

[0169] Common Reference Figure 9 and 13 The diagram schematically depicts a package carrier controller 212. The package carrier controller 212 typically includes a package carrier computing entity 807, which includes a processing component 902, volatile memory 906, non-volatile memory 904, and a communication component 908, as described above for the UAV computing entity 808. As described above, the package carrier controller 212 is communicatively coupled to, for example, the motor 213 of the package carrier 200 via the communication component 908, and controls the operation of the motor 213 to move the package carrier arm 230 between an engaged position and a disengaged position. The package carrier controller 212 is also communicatively coupled to, for example, the ground probe 250 via the communication component 908, and can receive signals from the ground probe 250 indicating that the ground probe 250 has contacted a surface (e.g., a landing surface). Furthermore, the package carrier computing entity 807 can communicate with the UAV computing entity 808 via the communication component 908, and can exchange data / information with the UAV computing entity 808, such as the charging status of the power supply 214 of the package carrier 200.

[0170] As described above, communication component 908 may include communication with various computing entities, such as by transmitting information / data, content, information, and / or similar terms used interchangeably herein, that can be sent, received, manipulated, processed, displayed, stored, etc. Such communication may be performed using wired data transmission protocols, such as FDDI, DSL, ATM, Frame Relay, DOCSIS, or any other wired transmission protocol. Similarly, central computing entity 802 may be configured to communicate via a wireless external communication network using any of the various protocols, such as GPRS, UMTS, CDMA2000, lxRTT, WCDMA, GSM, EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, UWB, IR protocol, NFC protocol, Wibree, Bluetooth protocol, Wireless USB protocol, and / or any other wireless protocol.

[0171] vi. Other embodiments of UAVs, parcel carriers, and parcels

[0172] As is understandable, consideration has been given to the above. Figure 1-13 Various modifications and changes have been made to the UAV 100, package carrier 200, and package 300 described herein. Various alternative embodiments of the UAV 100, package carrier 200, and package 300 will now be described.

[0173] In some embodiments, UAV 100 may include a separate UAV power supply that powers the propulsion member 102, and package carrier 200 is used to couple package 300 to UAV rack 110. In other words, in some embodiments, package carrier 200 may not include power supply 214 and / or power supply 214 may not power the propulsion member 102, and the propulsion member 102 of UAV 100 may be powered by the UAV power supply. Furthermore, when UAV 100 includes a separate UAV power supply, in some embodiments, power supply 214 of package carrier 200 may power the cooling unit of package 300 and may remain with package 300 during delivery, as will be described in more detail herein.

[0174] Figure 14 An alternative configuration for the ground landing sensor 162 is shown. Similar to that described above and... Figure 11 In the embodiment shown, ground landing sensor 162 is configured to detect the distance between ground landing sensor 162 and a surface positioned within a line of sight 163 of ground landing sensor 162. For example, during flight, ground landing sensor 162 can detect the distance between ground landing sensor 162 (the corresponding UAV 100) and a landing surface (e.g., the ground). By detecting the distance between UAV 100 and the landing surface, ground landing sensor 162 can assist UAV 100 in takeoff and landing. Ground landing sensor 162 may include sonar sensors, lidar sensors, IR-lock sensors, infrared distance sensors, ultrasonic distance sensors, magnetic field sensors, radar sensors, etc.

[0175] exist Figure 14 In the illustrated embodiment, ground landing sensor 162 is coupled to support member 164, which extends to the outside of the maximum enveloping envelope 302 where package 300 is located. Ground landing sensor 162 is coupled to support member 164 such that ground landing sensor 162 is positioned outside the maximum enveloping envelope 302. Similar to the above... Figure 11In the embodiments described herein, by positioning the ground landing sensor 162 outside the maximum envelope 302, the ground landing sensor 162 can maintain an unobstructed line of sight 163 to the landing surface during UAV 100 maneuvering. Furthermore, the ground landing sensor 162 is pivotally coupled to the support member 164 and / or the support member 164 is pivotally coupled to the UAV frame 110, such that the ground landing sensor 162 maintains a line of sight 163 to the landing surface during flight when the UAV 100 is maneuvered.

[0176] Reference Figure 15 This schematically depicts another configuration of the ground landing sensor 162. Similar to that described above and... Figure 14 In the embodiment depicted, UAV 100 includes a support member 164 extending outwardly from UAV frame 110. However, in Figure 15 In the illustrated embodiment, a reflective member 165 is coupled to a support member 164, and a ground landing sensor 162 is coupled to a UAV frame 110. The ground landing sensor 162 has a line of sight 163 initially extending outward from the UAV frame 110 and redirected downward by the reflective member 165. The ground landing sensor 162 is configured to detect the distance between the landing sensor 162 and a surface positioned within its line of sight 163. For example, during flight, the ground landing sensor 162 can detect the distance between the ground landing sensor 162 (the corresponding UAV 100) and a landing surface (e.g., the ground). By detecting the distance between the UAV 100 and the landing surface, the ground landing sensor 162 can assist in the takeoff and landing of the UAV 100. The ground landing sensor 162 may include a sonar sensor, a lidar sensor, an IR-lock sensor, an infrared distance sensor, an ultrasonic distance sensor, a magnetic field sensor, a radar sensor, etc.

[0177] exist Figure 15In the illustrated embodiment, a reflective member 165 is coupled to a support member 164, which extends to the outside of the maximum envelope 302. The reflective member 165 is coupled to the support member 164 such that it is positioned outside the maximum envelope 302. Since the ground landing sensor 162 is coupled to the UAV frame 110 and its line of sight 163 is reflected by the reflective member 165 positioned at the end of the support member 164, the distance the support member 164 extends outward from the UAV frame 110 can be taken into account when estimating the position of the UAV 100 relative to the landing surface. By positioning the reflective member 165 outside the maximum envelope 302, the reflective member 165 can redirect the line of sight 163 of the ground landing sensor 162, causing it to point downwards in the vertical direction and be positioned outside the maximum envelope 302. In addition, the reflector 165 is pivotally coupled to the support member 164 and / or the support member 164 is pivotally coupled to the UAV frame 110, so that the ground landing sensor 162 maintains a line of sight 163 with the landing surface.

[0178] As will be recognized, according to various embodiments, the UAV 100 and the package carrier 200 ( Figure 5 It can be used to carry packages of different sizes and shapes 300.

[0179] Reference Figure 16 Another embodiment of package 300 is schematically depicted. Figure 16 In the illustrated embodiment, package 300 has a generally cylindrical shape. The shape of package 300 can be adapted to the specific specifications of the goods being transported, while Figure 16 The embodiments shown include generally cylindrical shapes. It should be understood that package 300 can include any of a variety of irregular shapes, including but not limited to spherical, triangular prism, conical, etc. For example, in some applications, such as when goods transported within package 300 are refrigerated or cooled, package 300 can be shaped to minimize heat exchange between the interior of package 300 and the surrounding environment. Furthermore, in some embodiments, power source 214 can be configured to remain with package 300 to power refrigeration unit 217. In other embodiments, refrigeration unit 217 can include a separate power source located within refrigeration unit 217 and supplying power to refrigeration unit 217.

[0180] exist Figure 16 In the embodiment shown, package 300 is positioned within rectangular frame 320. Figure 16 Package 300 shown is configured in accordance with the above and in Figure 9 The same package carrier 200 depicted in the image is used together. Figure 16In the illustrated embodiment, a plurality of pins 236 extend laterally from the package guide 235 toward the package frame 320 and are selectively positioned to engage corresponding holes 322 defined by the package frame 320. The package carrier arm 230 selectively engages the package frame 320 via the engagement between the plurality of pins 236 and the holes 322, such that when the package carrier 200 is coupled to the UAV rack 110, the package 300 can be selectively coupled to the UAV 100. Figure 6 Alternatively, in some embodiments, the package frame 320 may include a plurality of pins that can be selectively inserted into holes defined by the package carrier arm.

[0181] As referenced above Figure 9 Each of the package-carrying arms 230 is laterally movable relative to the package 300 and the package frame 320, such that a plurality of pins 236 are selectively positioned within holes 322 defined by the package frame 320. The package-carrying arms 230 are repositionable between an engaged position and a disengaged position, wherein in the engaged position, the plurality of pins 236 are positioned within the holes 322 of the package frame 320, and in the disengaged position, the plurality of pins 236 are spaced apart from the holes 322 of the package frame 320. (Refer to the above...) Figure 9 The package support arm 230 can be biased inward, and the package support arm 230 can move between a disengaged position and an engaged position via a motor 213.

[0182] The package carrier 200 further includes a ground detector 250 extending downward from the engagement housing 210. The ground detector 250 is configured to extend downward from the bottom surface 324 of the package frame 320 at a distance “d” evaluated between the end of the ground detector 250 and the bottom surface 324. (Refer to the above...) Figure 9 The ground detector 250 is configured to detect when the package frame 320 (correspondingly, the package 300) is placed on the surface, for example, when the package 300 is placed by the UAV 100 ( Figure 5 It is delivered to the destination and is communicatively coupled to the package carrier controller 212.

[0183] Reference Figure 17 A perspective view schematically depicting an alternative embodiment of the package carrier 200 is shown. Figure 17 In the illustrated embodiment, the package carrier 200 includes a package carrier arm 230 extending outward from the engagement housing 210. However, in Figure 17 In the illustrated embodiment, the package carrier 200 includes a pair of support flanges 238 extending below the bottom surface 310 of the package. Figure 17In the illustrated embodiment, one of the package-carrying arms 230 is obscured by the package 300. It should be understood that the package-carrying devices 200 are substantially symmetrical, and the package-carrying arms 230 on opposite sides of the package 300 are substantially identical. Figure 17 In the illustrated embodiment, the package support arm 230 includes an upper portion 232 extending laterally outward from the engagement housing 210, a lower portion 234 extending downward from the upper portion 232, and a support flange 238 extending laterally inward from the lower portion 234. The support flange 238 may be coated with a material having a relatively high coefficient of friction (e.g., high-grip rubber), thereby reducing the likelihood that the package 300 may rotate relative to the package support device 200 in the lateral direction. Alternatively, the support flange 238 may extend at least partially in the longitudinal direction to support the package 300, thereby reducing the likelihood that the package 300 may rotate relative to the package support device 200 in the lateral direction.

[0184] exist Figure 17 In the embodiment shown, the housing 210, upper part 232, lower part 234, and ground detector 250 of the packaged carrier are compared with the above reference. Figure 9 The described embodiments are substantially the same. Therefore, each of the package support arms 230 is laterally movable relative to the package 300, such that the support flange 238 is selectively positioned below the bottom surface 310 of the package 300. Specifically, the package support arms 230 may include an inward bias and can be repositioned between an engaged position and a disengaged position, wherein in the engaged position, the support flange 238 is positioned below the bottom surface 310 of the package 300, and in the disengaged position, the support flange 238 is spaced apart from the bottom surface 310 of the package 310.

[0185] refer to Figure 18 Another embodiment of the package carrier 200 and package 300 being fixed to each other is schematically depicted. For example... Figure 18 As shown, package 300 comprises a generally cylindrical shape. Figure 18 In the illustrated embodiment, the package support arm 230 directly engages the package 300. In this embodiment, the package support arm 230 extends around the periphery 301 of the package such that it extends below a centerline 303 to support the package 300, the centerline 303 bisecting the package 300 vertically. In other embodiments, such as those where the package support arm 230 does not extend below the centerline 303, the package support arm 300 may support the package 300, for example, through friction and / or mechanical interference between the package support arm 230 and the periphery 301 of the package 300. Figure 18In the illustrated embodiment, pin 236 of package carrier arm 230 engages with hole 312 defined by package 300. Alternatively, in some embodiments, package 300 may include a plurality of pins that can be selectively inserted into holes defined by package carrier arms.

[0186] As mentioned above, the shape of package 300 can be adapted to the specific specifications of the goods being transported, while Figure 18 The embodiments shown include generally cylindrical shapes. It should be understood that the package 300 may include any of a variety of irregular shapes, including but not limited to spheres, triangular prisms, cones, etc.

[0187] exist Figure 18 In the illustrated embodiment, the package-carrying arm 230 includes a radius of curvature configured to extend at least partially around the periphery 301 of the package 300. Although in Figure 18 In the illustrated embodiment, one of the package-carrying arms 230 is obscured by the package 300. It should be understood that the package-carrying device 200 is substantially symmetrical, and the package-carrying arms 230 on opposite sides of the package 300 are substantially identical. The package-carrying arms 230 may be formed of a material having a relatively high coefficient of friction between the package-carrying arms 230 and the package 300, thereby reducing the likelihood that the package 300 may rotate relative to the package-carrying device 200 in the lateral direction. Alternatively, the package-carrying arms 230 may extend at least partially in the longitudinal direction to support the package 300, thereby reducing the likelihood that the package 300 may rotate relative to the package-carrying device 200 in the lateral direction.

[0188] Each of the package-carrying arms 230 is laterally movable relative to the package 300, allowing the package-carrying arm 230 to be selectively positioned around the perimeter 301 of the package 300. Similar to the above regarding... Figure 9 In the described embodiment, the package support arm 230 can be slidably or pivotally coupled to the package housing 210. The package support arm 230 can be repositioned between an engaged position and a disengaged position, wherein in the engaged position, the package support arm 230 is at least partially positioned around the periphery 301 of the package 300, and in the disengaged position, the package support arm 230 is spaced apart from the periphery 301 of the package in the lateral and / or longitudinal directions. Similar to the above description... Figure 9 In the described embodiment, the wrapping support arm 230 can be biased inward, and the wrapping support arm 230 can be moved between a disengaged position and an engaged position by a motor 213.

[0189] The package carrier 200 includes a ground detector 250, which is coupled to the package carrier arm 230 and extends downwards from the periphery 301 of the package 300 by a distance "d". Similar to the above regarding... Figure 9In the described embodiment, the ground detector 250 communicates with the motor 213 to selectively release the package 300 from the package carrier 200.

[0190] Reference Figure 19 Another embodiment of the package carrier 200 is schematically depicted. Similar to the embodiments described above, the package carrier 200 includes a coupling housing 210 and a power supply 214. However, in Figure 19 In the illustrated embodiment, a package carrier 200 is coupled to a package carrier mechanism 229, which includes a package housing 360 in which a package can be positioned for delivery. The package housing 360 generally defines a closed housing having an opening 361 located on one side of the housing. The opening 361 is selectively covered by a door 362, which is pivotally connected to the housing 360 and adjustable between an open and a closed position, wherein in the open position, the interior of the package housing 360 can be accessed through the opening 361, and in the closed position, the interior of the package housing 360 is closed. In various embodiments, the door 362 is moved between the open and closed positions by a motor 213 of the package carrier, which is controlled by a package carrier controller.

[0191] The enclosure 360 ​​further includes a support rail 364 positioned on the base plate of the enclosure 360, the support rail 364 reducing the enclosure 300 ( Figure 17 The friction between the package 300 and the bottom plate of the package 360 ​​allows the package 300 to easily move into and out of the package 360 ​​through the opening 361.

[0192] The package carrier 200 further includes a ground detector 250 extending downward from the engagement housing 210. Figure 19 In the illustrated embodiment, ground detector 250 is coupled to engagement housing 210 via package housing 360. Alternatively, ground detector 250 may be directly coupled to engagement housing 210. Ground detector 250 is configured to extend downward from bottom surface 365 of package housing 360 by a distance "d", which is evaluated between the end of ground detector 250 and bottom surface 365 of package housing 360. Ground detector 250 is configured to detect when package housing 360 is placed on a surface, e.g., when package housing 360 delivers a package, and ground detector 250 is communicatively coupled to package carrier controller 212.

[0193] When the package housing 360 is positioned on the surface, for example when the package 300 passes through UAV100 ( Figure 5Upon delivery to its destination, ground detector 250 may contact a surface before the bottom surface 365 of the package housing 360. As the package housing 360 descends toward the landing surface (e.g., the ground), ground detector 250 may contact the landing surface and deflect and / or elastically deform in the vertical direction. Alternatively, in some embodiments, ground detector 250 may be a vertically foldable telescopic detector, and ground detector 250 may fold in the vertical direction upon contact with a surface (e.g., the ground). When ground detector 250 contacts the surface, ground detector 250 sends a signal to package carrier controller 212, which then commands a motor to move door 362 from a closed position to an open position. In this way, ground detector 250 helps ensure that package 300 is not released from package housing 360 before package housing 360 is positioned on or near the surface. By ensuring that package housing 360 is positioned on or near the surface, damage to package 300 can be minimized compared to when package is released from package housing 360 from a certain height.

[0194] Once door 362 is in the open position, package 300 ( Figure 17 The package is then manually removed by the recipient from inside the package housing 360 via opening 361. Specifically, in some embodiments, when door 362 is moved to the open position, UAV 100 ( Figure 5 It can be manipulated to tilt the package 360 ​​and move the package 300 along the support rail 364 and away from the package 360.

[0195] Common Reference Figure 20 , 21A Figures 21B and 21B schematically depict another embodiment of the package carrier 200. In the illustrated embodiment, the package housing 360 generally defines and closes the package housing 360, which has an opening 361 located on one side of the package housing 360. The opening 361 is selectively covered by a door 362, and the package housing 360 is repositionable between an open position and a closed position, wherein in the open position, the interior of the package housing 360 can be accessed through the opening 361, and in the closed position, the interior of the package housing 360 is closed by the door 362. Figure 20 , 21A In the embodiment shown in 21B, the housing 360 includes an upper portion 370, which is pivotally coupled to a lower portion 372 at a pivot joint 366.

[0196] Special Reference Figure 21A and 21BThe package housing 360 is shown in both a closed and an open position. In the closed position, the lower portion 372 engages with the upper portion 370 of the package housing 360, such that a door 362 covers the opening 361 of the package housing 360. In the open position, the lower portion 372 pivots relative to the upper portion 370 about a pivot joint 366, such that the opening 361 is spaced vertically from the door 362, and the interior of the package housing 360 can be accessed through the opening 361. Specifically, when the lower portion 372 pivots relative to the upper portion 370, the door 362 can remain stationary relative to the upper portion 370, such that the lower portion 372 and the opening 361 of the package housing 360 move downwards relative to the door 362 in the vertical direction. As the lower portion 372 pivots, the lower portion 372 can tilt relative to a landing surface (e.g., the ground), such that gravity can induce the package 300 to move downwards and away from the package housing 360.

[0197] The package 360 ​​further includes a support rail 364 positioned on the base plate of the package 360, which reduces the friction between the package 300 and the base plate of the package 360, allowing the package 300 to be easily moved into and out of the interior of the package 360 ​​through the opening 361.

[0198] The package carrier 200 further includes a ground detector 250 extending downward from the engagement housing 210. Figure 20 , 21A In the embodiment shown in 21B, the ground detector 250 is coupled to the engagement housing 210 via the packaging housing 360. Alternatively, the ground detector 250 may be directly coupled to the engagement housing 210. The ground detector 250 is configured to extend downward from the bottom surface 365 of the packaging housing 360 by a distance "d", which is evaluated between the end of the ground detector 250 and the bottom surface 365 of the packaging housing 360. The ground detector 250 is configured to detect when the packaging housing 360 is placed on a surface, for example, when the packaging housing 360 delivers a package, and the ground detector 250 is communicatively coupled to the package carrier controller 212.

[0199] When the package housing 360 is positioned on the surface, for example when the package 300 passes through UAV 100 ( Figure 5Upon delivery to its destination, ground detector 250 may contact a surface prior to the bottom surface 365 of the package housing 360. As the package housing 360 descends toward the surface (e.g., the ground), ground detector 250 may contact the surface and deflect and / or elastically deform in the vertical direction. Alternatively, in some embodiments, ground detector 250 may be a vertically foldable telescopic detector, and ground detector 250 may fold in the vertical direction upon contact with a surface (e.g., the ground). When ground detector 250 contacts the surface, ground detector 250 sends a signal to package carrier controller 212. Upon receiving the signal from ground detector 250, package carrier controller 213 may command motor 213 to move lower portion 372 from a closed position to an open position, such that package 300 will slide out of the package carrier housing 360 through opening 361. In some embodiments, motor 213 may rotate lower portion 372 from a closed position to an open position. Alternatively, in some embodiments, the movement of lower portion 372 relative to upper portion 370 about pivot joint 366 may be unpowered and may be caused by gravity. In this way, the ground detector 250 can help ensure that the package 300 is not released from the package housing 360 before the package housing 360 is positioned on or near the surface. By ensuring that the package housing 360 is positioned on or near the surface, damage to the package 300 can be minimized compared to releasing the package from the package housing 360 from a certain height.

[0200] Reference Figure 22 A perspective view of another embodiment of the UAV rack 110 is schematically shown. Figure 22 In the illustrated embodiment, the landing arm 140 is vertically coupled to and extends downward from the UAV frame 110. The landing arm 140 is configured to extend outward from the maximum envelope 312 of the package 300 in both the lateral and longitudinal directions, and is also configured to extend downward below the package 300. When the UAV 100 is positioned on a surface, such as during landing and takeoff, the landing arm 140 can support the UAV frame 110. The landing arm 140 can be relatively flexible, such that it can elastically deform when supporting the weight of the UAV frame 110, which can help slow down the vertical movement of the UAV frame 110 during landing. Alternatively, in some embodiments, the landing arm 140 can be relatively rigid, such that it does not deform when supporting the weight of the UAV frame 110. Figure 3 In the illustrated embodiment, three landing arms 140 are coupled to the UAV frame 110; however, it should be understood that the UAV 100 may include any suitable number of landing arms 140 to support the UAV frame 110 on the surface.

[0201] Reference Figure 23AA perspective view schematically depicting another UAV rack 110 and a package carrier 200 is shown. Figure 23A In the illustrated embodiment, the UAV rack 110 includes an upper portion 114 and a width-reduced portion 115, and the enclosure support 200 includes an enclosure support housing 210. However, in Figure 23A In the illustrated embodiment, the UAV frame 110 does not include a lower portion, and the housing 210 enclosing the carrier device is directly coupled to the width reduction portion 115 of the UAV frame 110. Therefore, the housing 210 enclosing the carrier device 200, as well as the width reduction portion 115 and upper portion 114 of the UAV frame 110, form a conical or hourglass shape, which is configured to engage the vehicle 10 when the UAV 100 takes off and lands on the vehicle 10. Figure 1 A pair of opposing guide rails on the ( ). Specifically, compared to the width-reduced portion 115, the upper portion 114 and the housing 210 enclosing the support device can have a larger width evaluated in the transverse and / or longitudinal directions. Figure 23A In the illustrated embodiment, the width of the upper portion 114, evaluated in the lateral direction, decreases as it moves downward toward the width reduction portion 115. The width of the package carrier housing 210, evaluated in the lateral direction, decreases as it moves downward along the package carrier housing 210, causing the UAV 100 to take on a conical or hourglass shape when the package carrier housing 210 is coupled to the UAV rack 110.

[0202] exist Figure 23A In the illustrated embodiment, the UAV electrical interface 130 is positioned on the width reduction portion 115 and is positioned to align with the carrier electrical interface 220 when the package carrier 200 is coupled to the UAV rack 110. The UAV rack 110 may include a retaining member 120. Figure 7 The retaining member 120 can selectively engage the package carrier housing 210 to couple the package carrier 200 to the UAV rack 110. Alternatively, in some embodiments, the package carrier housing 210 can be coupled to the UAV rack 110 in any suitable manner (e.g., an electromagnet).

[0203] Reference Figure 23B A perspective view schematically depicting another UAV rack 110 and a package carrier 200 is shown. Figure 23BIn the illustrated embodiment, the UAV rack 110 includes an upper portion 114, and the package carrier 200 includes a receiving portion 270 located above the package carrier housing 210. The receiving portion 270 includes an upper portion 271 and a width-reducing portion 274 positioned below the upper portion 271. The upper portion 271, the width-reducing portion 274, and the package carrier housing 210 form a conical or hourglass shape, which is configured to engage the vehicle 10 when the UAV 100 takes off and lands on the vehicle 10. Figure 1 A pair of opposing guide rails on the (). Figure 23B In the illustrated embodiment, the width of the upper portion 271, evaluated in the lateral direction, decreases as it moves downward toward the width reduction portion 274. The width of the package carrier housing 210, evaluated in the lateral direction, increases as it moves downward from the width reduction portion 274, causing the package carrier housing 210 and the receiving portion 270 to be hourglass-shaped or conical.

[0204] The receiving portion 270 includes an upper portion 271 that defines a cavity 272 configured to receive the upper portion 114 of the UAV rack 110. Specifically, when the package carrier 200 is coupled to the UAV rack 110, the upper portion 114 of the UAV rack 110 can be at least partially inserted into the cavity 272 of the upper portion 271 of the receiving portion 270. The UAV rack 110 may include a retaining member 120. Figure 7 The retaining member 120 can selectively engage the receiving portion 270 to couple the package carrier 200 to the UAV rack 110. Figure 23B In the illustrated embodiment, the UAV electrical interface 130 is positioned on the upper portion 114 of the UAV rack 110, and the carrier electrical interface 220 is positioned within the cavity 271 of the receiving portion 270 that encloses the carrier 200. The UAV electrical interface 130 is positioned to align with the carrier electrical interface 220 when the carrier 200 is coupled to the UAV rack 110. Additionally, in Figure 23A In the embodiment shown, the landing gear 116 can be positioned on the upper part 271 of the receiving portion 270, such that the landing gear is positioned on the package carrier 200 compared to the UAV frame 110.

[0205] B. Main parcel delivery vehicles and UAV support facilities

[0206] Figure 24 A perspective view of the primary parcel delivery vehicle 10 is shown. In the illustrated embodiment, the primary parcel delivery vehicle is a stepvan (e.g., a Workhorse Range-Extended E-Gen truck, a Freightliner MT55, etc.). Figure 24 As shown, vehicle 10 includes a roof panel 12 supporting a pair of UAV support mechanisms 400. As explained in more detail herein, the UAV support mechanisms 400 are configured to enable a group of UAVs 100 to be dispatched from and return to vehicle 10 as part of a UAV-based parcel delivery system. Figure 24 In the illustrated embodiment, vehicle 10 includes two UAV support units 400; however, it should be understood that vehicle 10 may include a single UAV support unit 400, or any suitable number of UAV support units 400, to dispatch UAV 100 from vehicle 10. Figure 1 ).

[0207] like Figure 24 As shown, each UAV support structure 400 typically defines a takeoff end 402 and a landing area 404 positioned opposite to the takeoff end 402. Typically, UAV 100 ( Figure 1 It can take off from vehicle 10 from takeoff end 402 and return to and land on vehicle 10 at landing area 404. Figure 24 In the illustrated embodiment, the takeoff end 402 is located at the rear end of the vehicle 10, and the landing area 404 is located at the front end of the vehicle 10. However, it should be understood that the takeoff end 402 may be located at the front end of the vehicle 10, and the landing area 404 may be located at the rear end of the vehicle 10. Additionally, in some embodiments, the takeoff end 402 and the landing area 404 of the support structure may be located at the same end of the vehicle 10. Although the embodiments described herein include one or more UAV support structures 400 positioned on the vehicle 10, it should be understood that the UAV support structure 400 may be mounted on any suitable structure (e.g., a fixed building, structure, movable cargo pod, etc.) and may be used to dispatch UAV 100 from any suitable structure.

[0208] Reference Figure 25 The diagram schematically shows a perspective view of a UAV support mechanism 400 on the top plate 12 of the vehicle 10. Each of the UAV support mechanisms 400 includes a pair of opposing guide rails 410 extending along the top plate 12 of the vehicle 10, and the opposing guide rails 410 are configured to engage a UAV frame 110. Figure 4 This will be described in more detail herein. Opposite guide rails 410 are generally symmetrical to each other and extend longitudinally along the top plate 12. Between the landing area 404 and the takeoff end 402, the UAV support mechanism 400 defines a return area 406, a transfer area 407, and a supply area 408.

[0209] The roof 12 of the vehicle 10 typically defines an entrance or opening through which the interior 18 of the vehicle 10 can be accessed. Specifically, in Figure 25 In the illustrated embodiment, top plate 12 defines a return inlet 14 and a supply inlet 16. The return inlet 14 is located within a return region 406 of the opposing guide rail 410, and the supply inlet 16 is located within a supply region 408 of the opposing guide rail 410. In operation, when UAV 100 ( Figure 1 When engaged with the opposite guide rail 410, the empty package carrier 200 ( Figure 2 ) can be obtained from UAV rack 110 ( Figure 2 The UAV can be released and stored in the interior 18 of the vehicle 10 via return inlet 14. It can be supplied from the interior 18 of the vehicle 10 to the UAV rack 110 via supply inlet 16. Figure 3 The new parcel carrier 200 and parcel 300 are provided. Figure 9 This will be described in more detail in this article.

[0210] refer to Figure 26A This schematically shows along Figure 25 The cross-sectional view of the UAV support mechanism 400 is shown in section 26A-26A. As described above, the UAV support mechanism 400 includes opposing guide rails 410 extending longitudinally along the top plate 12. The opposing guide rails 410 are coupled to a plurality of support arms 416 extending upward from the top plate 12, and the opposing guide rails 410 are positioned vertically above the top plate 12. By positioning the opposing guide rails 410 vertically above the top plate 12, when the package 300 is coupled to the UAV frame 110 ( Figure 2 When the package contains 300 ( Figure 9 It can pass under the opposite guide rail 410, which will be described in more detail in this article.

[0211] Common Reference Figure 25-26B The diagram schematically illustrates perspective and cross-sectional views of the return area 406, transmission area 407, and supply area 408. In the return area 406, transmission area 407, and supply area 408, the UAV support mechanism 400 includes a conveyor 440 configured to move the UAV 100 along opposing guide rails 410 between the return area 406 and the supply area 408. Figure 1Conveyor 440 typically includes a plurality of rollers 442 positioned within a C-shaped profile 410a of opposing guide rails 410. The C-shaped profile 410a typically defines an upper guide surface 412 and a lower guide surface 414, the upper guide surface 412 oriented vertically upwards and the lower guide surface 414 oriented vertically downwards. The upper guide surface 412 and the lower guide surface 414 can engage the upper portion 114 and the lower portion 118 of the UAV frame 110. Figure 2 This restricts the vertical movement of the UAV rack 110, as will be described in more detail herein. In some embodiments, the upper guide rail surface 412 may include a communication connection that can be communicatively coupled to the UAV computing entity 808 when the UAV rack 110 is in the UAV support mechanism 400, allowing notifications / messages to be sent from and received from the UAV computing entity 808 to the vehicle computing entity 810, as will be described in more detail herein.

[0212] Roller 442 rotates relative to the C-shaped profile 410a and can engage with UAV frame 110. Figure 2 This allows the UAV rack 110 to be moved from the supply area 408 to the return area 406. In one embodiment, roller 442 may be operatively coupled to belt 444, which rotates roller 442 about roller shaft 445. Belt 444 may be operatively coupled to conveyor controller 460, which selectively moves belt 444 to rotate a plurality of rollers 442.

[0213] In one embodiment, the conveyor 440 further includes a plurality of position sensors 450 positioned along opposing guide rails 410. The position sensors 450 are configured to detect the UAV rack 110 on the conveyor 440. Figure 2 The position sensor 450 is communicatively coupled to the conveyor controller 460 and can send signals to the conveyor controller 460, such as indicating the location of the UAV rack 110 (and may include multiple proximity sensors, such as capacitive sensors, inductive sensors, Hall effect sensors, etc.). Figure 2 The signal is positioned as if it is approaching one or more position sensors 450. In some embodiments, the position sensors 450 include a supply position sensor 450a located within a supply area 408 and a return position sensor 450b located within a return area 406. The supply position sensor 450a is configured to detect when the UAV rack 110 ( Figure 2 The position sensor 450b is positioned above the supply inlet 16. Similarly, the return position sensor 450b is configured to detect when the UAV rack 110 ( Figure 2 It is positioned above the return entry 14.

[0214] Reference Figure 27 The diagram schematically illustrates a conveyor controller 460. The conveyor controller 460 typically includes one or more processing elements / assemblies 462, a motor 464, and one or more communication elements / assemblies 466. The motor 464 of the conveyor controller 460 can be operatively coupled to a belt 444. Figure 26B This causes motor 464 to drive belt 444. The conveyor controller can also be communicatively coupled to multiple position sensors 450 and can be communicatively coupled to one or more computing entities via communication device 466. In particular, communication device 466 is configured to communicate with various computing entities, for example by transmitting information / data, content, information, and / or similar terms that may be used interchangeably herein, which can be sent, received, manipulated, processed, displayed, stored, etc. Such communication can be performed using wired data transmission protocols such as FDDI, DSL, ATM, Frame Relay, DOCSIS, or any other wired transmission protocol. Similarly, the central computing entity 802 can be configured to communicate via a wireless external communication network using any of the various protocols, such as GPRS, UMTS, CDMA2000, lxRTT, WCDMA, GSM, EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, UWB, IR protocol, NFC protocol, Wibree, Bluetooth protocol, wireless USB protocol, and / or any other wireless protocol.

[0215] Reference Figure 28 The diagram schematically shows a front view of the landing area 404 of the UAV support mechanism 400. Opposing guide rails 410 converge laterally from the landing area 404 to the return area 406, and the width between the opposing guide rails 410 is greater in the landing area 410 compared to the return area 406 and the transport area 407. By converging in the lateral direction, when the UAV 100 ( Figure 1 When landing on vehicle 10, the corresponding guide rail 410 can help guide UAV rack 110. Figure 2 Each of the opposing guide rails 410 includes a damper 410 positioned at a landing area 404 of the opposing guide rail 410. The damper 410 typically includes a flexible brush 422, which, when the flexible brush 422 is in contact with the UAV frame 110 (… Figure 2 Upon contact, the flexible brush 422 elastically deforms. Specifically, when the UAV 100 lands on the vehicle 10 and moves along the land area 404 to the return area 406, the UAV rack 110 ( Figure 2 Contact damper 410. When UAV rack 110 ( Figure 2 When contact damper 410 is engaged, UAV 100 ( Figure 1 The forward motion (e.g., motion in the y direction) will be slowed down by the damper 410.

[0216] Reference Figure 28 and 29 As shown, in this embodiment, the opposing guide rails 410 can move vertically and / or laterally at the landing area 404. Specifically, the opposing guide rails 410 can be operatively coupled to a power source, such as a hydraulic pump, that allows landing and movement in the vertical and / or lateral directions. By moving the opposing guide rails 410 vertically and / or laterally, the opposing guide rails 410 can be moved to match the route / flight path of the UAV 100, allowing the UAV 100 to land on the opposing guide rails 410. In some embodiments, the opposing guide rails 410 at the landing area 404 are hingedly coupled to the vehicle 10 and / or the conveyor 440 at hinge 441.

[0217] Refer again Figure 28 The opposing guide rail 410 includes a guide array 430 positioned in the landing area 404. The guide array 430 typically includes components that aid in guiding the UAV 100 (…). Figure 1 Various devices that land on vehicle 10. Figure 28 In the illustrated embodiment, the guide array 430 includes a visual indicator 432 and a positioning beacon 434. Each of the opposing guide rails 410 includes a visual indicator 432, which may include a light, LED, etc., that emits light (e.g., radiation in the visible spectrum), said light may be emitted by the vehicle landing sensor 164 and / or camera 168. Figure 10 ) detected to help UAV 100 ( Figure 1 The precise positioning of the UAV support mechanism 400 upon landing on vehicle 10 will be described in more detail in this article.

[0218] Positioning beacon 434 can emit signals that can be detected by vehicle landing sensor 164. Figure 10 The detected signal helps UAV 100 ( Figure 1 The UAV support mechanism 400 is accurately positioned upon landing on vehicle 10. In an embodiment, the positioning beacon 434 may include technologies such as iBeacons, gimbal proximity beacons, BLE transmitters, near field communication (NFC) transmitters, etc. Although in Figure 28 The illustrated embodiment includes positioning beacons 434 positioned on each of the opposing guide rails 410. It should be understood that the positioning beacons 434 may include a single beacon or any suitable number of beacons positioned at any suitable location on the opposing guide rails 410 to assist the UAV 100. Figure 1 Accurately position the UAV support mechanism 400.

[0219] i. means of transportation

[0220] Reference Figure 29 The diagram schematically shows a rear perspective view of the vehicle 10, with some panels removed for clarity. As described above, the vehicle 10 includes a pair of UAV support mechanisms 400 positioned on a top plate 12 of the vehicle 10. One or more package carrier support brackets 30 are positioned inside the vehicle 10. The brackets 30 support multiple package carriers 200 (…). Figure 9 This will be described in more detail here. Two loading robots 500 are positioned inside the interior 18 of the vehicle 10. The loading robots 500 assist in moving the package carrier 200 within the interior 18 of the vehicle 10. Figure 9 Each of the loading robots 500 can be associated with one of the UAV support mechanisms 400. The bracket 30 is typically positioned along the side of the vehicle 10; however, the bracket 30 can be positioned at any suitable location within the vehicle 10, and the bracket 30 can be centrally positioned within the vehicle 10.

[0221] refer to Figure 29 and Figure 35A The figures show a rear perspective view of the vehicle 10 and an enlarged perspective view of one of the brackets 30. Each bracket 30 includes an outer extension arm 32 extending outwardly from a base 31 of the bracket 30. The bracket 30 further includes a plurality of flange ends 34 extending upwardly from the outer extension arm 32. The outer extension arm 32 and flange ends 34 of the bracket 30 are configured to engage the engagement housing 210 of the package carrier 200 and restrict movement of the engagement housing 210 in the lateral and longitudinal directions. In some embodiments, the bracket 30 may also include one or more electrical contacts that can provide charge to a power source 214 when the engagement housing 210 is positioned in the bracket 30, such that the power source 214 can be charged or recharged when it is placed in the bracket 30. By charging the power source 214, the bracket 30 can help prepare the package carrier 200 with the consumed power source 214 for reuse.

[0222] Reference Figure 30 A perspective view of the vehicle 10 is shown, with the bracket 30 removed for clarity. The vehicle 10 includes two loading robots 500, each with a UAV support mechanism 400. Figure 29The loading robots 500 are each movable along a horizontal track 502 extending longitudinally along the interior of the vehicle 18. Each loading robot 500 includes an upright member 504 operatively coupled to the horizontal track 502, and an end effector 510 coupled to the upright member 504. The upright member 504 extends vertically upward and is generally defined by a vertical track 506 extending vertically along the upright member 504. The end effector 510 is movable along the upright member 504 in a vertical direction along the vertical track 504. Each of the robots 500 includes a package identification unit 511 configured to scan, read, query, receive, communicate, and / or use similar terms interchangeably herein for package identifiers and / or package carrier identifiers, and the package identification unit 511 may be communicatively coupled to one or more computational entities, which will be described in more detail herein.

[0223] Common Reference Figure 35A , 35B Figure 35C schematically shows a perspective view of end effector 510. End effector 510 includes end effector track 514, platform 512 positioned on and movable along end effector track 514, and clamping member 516 positioned at the opposite end of platform 512. Platform 512 generally supports package 300, and clamping member 516 can be repositioned between an engaged position and a disengaged position, wherein in the engaged position, clamping member 516 contacts the opposite side of package 300, and in the disengaged position, clamping member 516 is spaced apart from the side of package 300. Clamping member 516 can hold the position of package 300 on platform 512 of end effector 510 as loading robot 500 moves package 300 into the interior 18 of vehicle 10. Figure 35A , 35B In the embodiment shown in 35C, the clamping member 516 is positioned longitudinally on the opposite end of the platform 512. However, it should be understood that the clamping member 516 can be positioned at any suitable location on the end effector 510 to maintain the position of the package 300 relative to the platform 512 of the end effector 510. The clamping member 516 can be repositioned between the engaged and disengaged positions in any suitable manner (including but not limited to electric, hydraulic, etc.).

[0224] The platform 512 of the end effector 510 can also move laterally relative to the upright member 504 along the end effector track 514. Therefore, the loading robot 500 can move within the interior 18 of the vehicle 10 in the longitudinal direction (e.g., along the horizontal track 502), the vertical direction (e.g., along the vertical track 504), and the lateral direction (e.g., along the end effector track 514). Although the loading robot 500 is generally described herein as comprising a three-axis robot, it should be understood that the loading robot 500 can include moving the package carrier 200 within the interior 18 of the vehicle. Figure 9 Any suitable robot, such as a six-axis robot, etc.

[0225] Reference Figure 31 A schematic diagram of a loading robot controller 520 is shown. The loading robot controller 520 is communicatively coupled to various components of the loading robot 500 and typically controls the movement and functions of the loading robot 500. The loading robot controller 520 typically includes one or more loading robot processing elements / components 522, one or more storage elements / components 521, and one or more loading robot communication elements / components 524. In embodiments, the loading robot controller 520 may be communicatively coupled to the position sensors 450 of the conveyor controller 460 and / or the UAV support mechanism 400, enabling robot operation to be initiated based on signals received from the conveyor controller 460 and / or the position sensors 450. For example, when a UAV rack 110 is detected above the supply inlet 16 or return inlet 14, the loading robot controller 520 may initiate movement of the robot 500, as will be described in more detail herein. Communication device 524 is configured to communicate with various computing entities, for example, by transmitting information / data, content, information, and / or similar terms that may be used interchangeably herein, which can be sent, received, manipulated, processed, displayed, stored, etc. Such communication may be performed using wired data transmission protocols such as FDDI, DSL, ATM, Frame Relay, DOCSIS, or any other wired transmission protocol. Similarly, central computing entity 802 may be configured to communicate via a wireless external communication network using any of the various protocols, such as GPRS, UMTS, CDMA2000, lxRTT, WCDMA, GSM, EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, UWB, IR protocol, NFC protocol, Wibree, Bluetooth protocol, Wireless USB protocol, and / or any other wireless protocol.

[0226] ii. Loading parcels / parcel carriers onto vehicles

[0227] Reference will now be made to loading a parcel onto vehicle 10. It is understood that a sender can send a parcel to a recipient using a carrier. During the delivery of the parcel to the recipient, the carrier may deliver the parcel to one or more intermediate locations, such as a processing center and / or warehouse. In delivery involving a UAV, the parcel may be attached to the parcel carrier before loading the parcel and the parcel carrier onto the vehicle, as described below.

[0228] Reference Figure 32 The diagram schematically illustrates a perspective view of the operation of loading a package carrier 200 onto a package 300. An automated package / package carrier connection system 600 is positioned within an intermediate location 601. The intermediate location 601 may include a facility, such as a warehouse or distribution center, where packages 300 are sorted and dispatched as part of the delivery process. The connection system 600 includes a tray 610 holding the package carrier 200, a loading robot 612, a transfer rail 620, multiple package carrier grippers 622 positioned on the transfer rail 620, a conveyor belt 630, and an engagement clamping mechanism 634 positioned on the conveyor belt 630. The tray 610 may be substantially similar to the one described above and... Figure 29 The bracket 30 is shown in the image. Figure 32 In the illustrated embodiment, the tray 610 can also supply charge to the package carrier 200, for example, when the package carrier 200 includes a power source 214. By supplying charge to the power source 214, the tray 610 can prepare a separate package carrier 200 for use via UAV 100 ( Figure 1 )Delivered 300 packages.

[0229] The loading robot 612 is basically similar to the robot 500 located in vehicle 10. Figure 30 It is configured to acquire the package carrier 200 from the tray 610 and supply the acquired package carrier 200 to the transfer rail 620. Similar to robot 500 ( Figure 30The loading robot 612 may include a three-axis robot, or may include any suitable robot for moving the package carrier 200, such as a six-axis robot, etc. The loading robot 612 may include a package carrier identification unit 613 configured to scan, read, query, receive, communicate, and / or use similar terms interchangeably herein for package carrier identifiers on each of the package carriers 200, and the package carrier identification unit 613 may be communicatively coupled to one or more computational entities. For example, the package carrier 200 may include package carrier identifiers, such as alphanumeric identifiers or machine-readable identifiers. Such package carrier identifiers may be represented as text, barcodes, labels, strings, Aztec codes, Maxi codes, data matrices, quick response (QR) codes, electronic representations, etc. The carrier may use a unique package identifier (e.g., 123456789), and this unique package identifier may be associated with a package identifier and / or a UAV identifier to identify and track the package carrier as it moves through a carrier's transportation network. In addition, such package carrier identifiers can be attached to the package carrier, for example, by using a sticker (e.g., a label) on which a unique package carrier identifier is printed (in a human- and / or machine-readable form) or by using an RFID tag having a unique package identifier stored thereon.

[0230] Multiple package carrier grippers 622 are operatively coupled to a transfer rail 620, and the transfer rail 620 can move the package carrier grippers 622 along the transfer rail 620 to attach package carriers 200 to packages 300 positioned on a conveyor belt 630. Specifically, a loading robot 612 can insert package carriers 200 into the package carrier grippers 622 on the transfer rail 620. The package carrier grippers 622 can be biased inwards, such that package carriers 200 are held within the package carrier grippers 622. This inward biasing of the package carrier grippers 622 can be caused by biasing members, such as tension springs, torsion springs, compression springs, etc.

[0231] Package carrier clamp 622 and package carrier 200, selectively coupled to package carrier clamp 622, move along transfer guide 620 toward conveyor belt 630. In an embodiment, package carrier clamp 622 is positioned above conveyor belt 630. Package carrier clamp 622 moves downward toward conveyor belt 630, where package carrier 200 engages with package 300 positioned on conveyor belt 630.

[0232] The package carrier clamp 622 moves downward toward the conveyor belt 630 at the engagement clamping mechanism 634. Upon reaching the engagement clamping mechanism 634, the engagement clamping mechanism 634 can mate the package carrier 200 with the package 300, for example, by pressing the package carrier arm 230 inward into the package 300. Once the package carrier 200 is engaged with the package 300, the package carrier clamp 622 can disengage from the package carrier 200 and continue moving along the transport guide 620.

[0233] The parcel / parcel carrier connection system 600 may further include a parcel identification unit 632, which can communicate with a parcel identifier of a parcel 300 positioned on a conveyor belt 630. For example, each parcel 300 may include a parcel identifier, such as an alphanumeric identifier or a machine-readable identifier. Such a parcel identifier can be represented as text, a barcode, a label, a string, an Aztec code, a Maxi code, a data matrix, a QR code, an electronic representation, etc. The carrier can use a unique parcel identifier (e.g., 123456789) to identify and track the parcel as it moves through a carrier's transportation network. Furthermore, such a parcel identifier can be attached to the parcel, for example, using a sticker (e.g., a label) on which the unique parcel identifier is printed (in a human- and / or machine-readable form) or an RFID tag having the unique parcel identifier stored therein.

[0234] Package identification unit 632 may include a barcode scanner, computer vision system, RFID antenna, etc., configured to read package identifiers of packages 300. Package identification unit 632 may be communicatively coupled to one or more computing entities, and the package identification unit may transmit information / data associated with the package identifier of each package 300 to one or more computing entities, which will be described in more detail herein.

[0235] Reference Figure 33 and Figure 34The diagram schematically shows a perspective view of a vehicle 10 loaded with a package 300. In this embodiment, the package 300 and its attached package carrier 200 can be conveyed into the rear opening of the vehicle 10 via a package conveyor 700. The package conveyor 700 may include a conveyor belt, drive rollers, etc., which move the package 300 and its attached package carrier 200 into the vehicle 10. The package conveyor 700 may include a pushing mechanism 702 that moves the package 300 and its attached package carrier 200 from the package conveyor 700 to the end effector 510 of the loading robot 500. Specifically, the pushing mechanism 702 can move the package 300 and its attached package carrier 200 in the lateral direction, conveying the package 300 and its attached package carrier 200 from the package conveyor 700 to the end effector 510 of the loading robot 500. Once the package 300 and the package carrier 200 are positioned on the loading robot 500, the loading robot 500 moves the package 300 and the package carrier 200 to the tray 30 located within the vehicle 10.

[0236] For example and refer to Figure 35A The loading robot 500 can move the package 300 and the package carrier 200 closer to an available outer extension arm 32 of the tray 30 (e.g., an outer extension arm 32 not engaged with the package carrier 200 / package 300). The loading robot 500 can move the package 300 and the attached package carrier 200 in the vertical direction such that the underside of the package carrier 200 is generally aligned in the vertical direction with the outer extension arm 32 of the tray 30.

[0237] Reference Figure 35B As the lower side of the package carrier 200 is aligned with the outer extension arm 32 of the bracket 30, the platform 512 of the loading robot 500 moves laterally toward the outer extension arm 32 along the end effector guide 514. The loading robot 500 moves the platform 512 toward the outer extension arm 32 until the outer extension arm 32 is positioned vertically between the package carrier 200 and the package 300.

[0238] Reference Figure 35COnce the outer extension arm 32 is vertically positioned between the package carrier 200 and the package 300, the clamping member 516 of the end actuator 510 moves from the engaged position to the disengaged position, such that the clamping member 516 is spaced apart from the package 300 in the longitudinal direction. The package 300 and the package carrier 200 can be supported by the outer extension arm 32, and specifically, the bottom surface of the package carrier 200 can be positioned on the outer extension arm 32, with the package 300 vertically positioned below the outer extension arm 32. Movement of the package carrier 200 and the package 300 relative to the outer extension arm 32 can be limited by the flange end 34.

[0239] Once package 300 and package carrier 200 are positioned on the outrigger arm 32, platform 512 moves along end effector track 514 toward the upright member 504 of loading robot 500, making loading robot 500 ready to retrieve another package 300 and package carrier 200 from package conveyor 700. Figure 34 ).

[0240] iii. Loading / unloading into the UAV rack

[0241] Once vehicle 10 is loaded with parcel 300 and parcel carrying device 200 associated with parcel 300, for example as part of a delivery route, vehicle 10 can be dispatched to deliver parcel 300. During the delivery of parcel 300, UAV 100 ( Figure 1 The package 300 and the package carrier 200 associated with the package 300 are loaded as described below.

[0242] Common Reference Figure 36 and 37 The UAV frame 110 is positioned on the UAV support mechanism 400 of the vehicle 10. Within the return area 406, the transfer area 407, and the supply area 408, the UAV support mechanism 400 and the UAV frame 110 engage with the conveyor 440. Specifically, the landing gear 116 contacts and engages with the upper surface 412 of the opposing guide rail 410, and the width reduction portion 115 of the UAV frame 110 is positioned laterally between the opposing guide rails 410. Furthermore, the upper portion 114 of the UAV frame 110 is positioned above the opposing guide rails 410, and the lower portion 118 of the UAV frame 110 is positioned below the opposing guide rails 410. In this embodiment, the width of the upper portion 114 and the width of the lower portion 118, evaluated in the lateral direction, are both greater than the width "w" between the opposing guide rails 410, evaluated in the lateral direction. Because the width of the upper part 114 and the lower part 118 of the UAV rack 110 is greater than the width between the opposing guide rails 410, the UAV rack 110 is restricted in the vertical direction when it is positioned in the conveyor 440.

[0243] Conveyor 440 moves UAV frame 110 longitudinally, for example, via rollers 442 (and / or landing gear 116, when landing gear 116 includes powered rollers), through transport area 407 and into supply area 408 of conveyor 440. Once in supply area 408, and once UAV frame 110 is positioned above supply inlet 16, rollers 442 can stop rotating. Conveyor controller 460 ( Figure 25 It can detect when the UAV rack 110 is positioned above the supply inlet 16, for example, via the supply position sensor 450a. Figure 25 Once the UAV rack 110 is positioned above the supply inlet 16, the package 300 and the attached package carrier 200 can be retrieved from the interior 18 of the vehicle 10 and attached to the UAV rack 110 for loading the UAV rack 110 for flight.

[0244] Reference Figure 38A In order to retrieve the package 300 and the associated package carrier 200 from the interior 18 of the vehicle 10, the loading robot 500 positions its end effector 510 below the package 300 on the carrier 30. Specifically, the platform 512 of the end effector 510 is positioned below the package 300, and the clamping member 516 can engage the side of the package 300.

[0245] Reference Figure 38B With the end effector 510 engaged with the package 300, the loading robot 500 lifts the package 300 and the attached package carrier 200 upward in the vertical direction, causing the package carrier 200 to detach from the carrier 30.

[0246] Reference Figure 38C The loading robot 500 then moves the package 300 and the attached package carrier 200 away from the tray 30 and moves the package 300 and the attached package carrier 200 toward the supply inlet 16. The loading robot 500 positions the package 300 and the package carrier 200 below the UAV rack 110 such that the package carrier 200 can be inserted into the lower part 118 of the UAV rack 110. The loading robot 500 moves upward in the vertical direction and inserts the package carrier 200 into the lower part 118 of the UAV rack 110, and the package carrier 200 can be inserted, for example, by means of the retaining member 120 ( Figure 7 The package carrier 200 is held within the lower part 118. When the package carrier 200 is inserted into the lower part 118 of the UAV frame 110, the clamping member 516 of the end effector 510 moves to the disengaged position, and the end effector 510 can be separated from the package 300.

[0247] Reference Figure 39Once package 300 and package carrier 200 are selectively coupled to UAV rack 110, UAV 100 is ready to deliver package 300 to its destination, and conveyor 440 moves UAV 100 from supply area 408 to takeoff end 402. Once at takeoff end 402, UAV 100's propulsion component 102 can be powered on, and propeller 103 of propulsion component 102 begins to rotate, allowing UAV 100 to take off from takeoff end 402 to deliver package 300 to its destination.

[0248] As will be described in more detail herein, UAV 100 can deliver package 300 to its destination at service point 5901. After successfully delivering package 300 to its destination at service point 5901, UAV 100 returns to vehicle 10 with an empty package carrier 200, where another package 300 and package carrier 200 can be redeployed. As will be appreciated, after delivering one or more packages 300 to one or more service points 5901, UAV 100 can also pick up one or more packages 300 (e.g., multi-station pickup and / or delivery).

[0249] Reference Figure 40 The illustration shows the initiation of a UAV 100 landing on a vehicle 10, for example, when the UAV 100 returns to the vehicle 100 after successfully delivering a package 300. In an embodiment, the vehicle landing sensor 164 of the UAV 100 detects one or more components of the guide array 430, enabling the UAV 100 to locate the relative guide rail 410 of the UAV support system 400. For example, in some embodiments, the vehicle landing sensor 164 may detect the position of the visual indicator 432 and / or the positioning beacon 434 of the UAV support system 400. By detecting the position of the visual indicator 432 and / or the positioning beacon 434, the vehicle landing sensor 164 can provide the UAV 100 with an accurate estimate of the position of the relative guide rail 410, enabling the UAV 100 to navigate toward the landing area 404 of the relative guide rail 410.

[0250] In various embodiments, UAV 100 may be configured to land on vehicle 10 only when vehicle 10 is stationary. For example, for manually operated vehicles, UAV 100 may not be able to predict the movement of vehicle 10, and therefore UAV 100 may land on UAV support 400 only when the movement of vehicle 10 can be accurately predicted (e.g., when vehicle 10 is stationary). In such embodiments, UAV 100 may be configured to follow vehicle 10 at predetermined distances until vehicle 10 stops while UAV 100 is moving.

[0251] In various embodiments, UAV 100 can be configured to land on vehicle 10 while vehicle 10 is in motion. For example, when vehicle 10 includes an autonomous vehicle, vehicle 10 can predictably move along a predetermined / configurable route, making the movement of vehicle 10 accurately predictable. In these embodiments, UAV 100 can land on vehicle 10 while vehicle 10 is in motion.

[0252] Reference Figure 41 The image shows a perspective view of UAV 100 landing on UAV support mechanism 400. When accurately positioning the opposing guide rails 410, for example via guide array 430, UAV 100 is navigated such that, in the vertical direction, the upper portion 114 of UAV frame 110 is positioned above the opposing guide rail 410, and the lower portion 118 of UAV frame 110 is positioned below the opposing guide rail 410. The tapered shape of the upper portion 114 and the lower portion 118 of UAV frame 110 facilitates guiding UAV 100 such that the upper portion 114 is positioned above the opposing guide rail 410, and the lower portion 118 is positioned below the opposing guide rail 410. With the upper portion 114 positioned above the opposing guide rail 410 and the lower portion 118 positioned below the opposing guide rail 410, UAV 100 moves backward in the longitudinal direction as the opposing guide rails 410 converge in the lateral direction. UAV 100 can move backward in the longitudinal direction under the power of propulsion component 102 until UAV 100 reaches conveyor 440 located behind landing area 404.

[0253] Once UAV 100 has landed on UAV support 400 and engaged with conveyor 440, the UAV's propulsion component 102 can be de-energized, causing the propeller 103 to stop rotating. Conveyor 440 can then move UAV 100 to return area 406.

[0254] Reference Figure 42A Conveyor 440 moves UAV 100 to return inlet 14. Conveyor controller 460 ( Figure 25 For example, via the return position sensor 450b ( Figure 25 The system can detect when the UAV rack 110 is positioned above the return inlet 14. At the return inlet 14, the loading robot 500 can engage the currently empty package carrier 200 with the end effector 510, and the package carrier 200 can be selectively decoupled from the UAV rack 110. When the package carrier 200 is decoupled from the UAV rack 110, the loading robot 500 can lower the end effector 510, and thus lower the package carrier from the UAV rack 110.

[0255] Reference Figure 42BThe loading robot 500 can position the empty package carrier 200 from the UAV rack 110 to the tray 30 inside the interior 18 of the vehicle 10. When the empty package carrier 200 is removed from the UAV rack 110, the conveyor 440 moves the UAV rack 110 from the return area 406, through the transfer area 407 to the supply area 408. Figure 36 (This allows for the resupply of new package carriers 200 and packages 300 to the UAV rack 110, as described above.)

[0256] Now refer to Figure 43 A perspective view of an alternative interior 18 of the vehicle 10 is schematically shown. Figure 43 In the illustrated embodiment, the interior 18 of the vehicle 10 includes a bracket 30 and a bracket 41, the bracket 30 being configured to be connected to the UAV 100 ( Figure 1 ) Parcel carrier 200 ( Figure 17 In combination, the tray 41 is used for conventional packages 300 that can be manually delivered by delivery personnel. In particular, in such an embodiment, the vehicle 10 can deliver packages 300 via UAV 100 while simultaneously delivering packages 300 by conventional methods (e.g., by delivery personnel).

[0257] Reference Figure 44 A perspective view of the alternative mode of transportation 10 is schematically shown. Figure 44 In the illustrated embodiment, vehicle 10 includes a trailer, such as a trailer optionally coupled to a semi-truck. Vehicle 10 includes a UAV support structure 400 as described above, from which UAV 100 can take off and land, and may include one or more robots configured to load and unload package carrier 200 from UAV 100. In such an embodiment, when UAV 100 delivers package 300 from vehicle 10, vehicle 10 can be moved to a location to deliver package 300 and vehicle 10 can remain stationary at that location. While UAV 100 is delivering package 300 from vehicle 10, vehicle 10 can remain at that location until all packages 300 have been delivered from vehicle 10, or until every package 300 within vehicle 10 has been attempted for delivery, at which point vehicle 10 can pick up and return to service point 5901. These vehicles can assist in the delivery of package 300 during high-volume periods (e.g., during holiday delivery seasons), supplementing other delivery methods.

[0258] Reference Figure 45A and 45B Another embodiment of the vehicle 10 is illustrated schematically. Figure 45A and 45BIn the illustrated embodiment, the UAV support mechanism 400 includes a landing pad 40 positioned on the top plate 12 of the vehicle 10. In this embodiment, compared to the UAV support mechanism 400 described above, the UAV 100 can land on the landing pad 40. The landing pad 40 is configured to support the UAV 100 and includes an entrance through which access to the interior 180 of the vehicle 10 is possible. The vehicle 10 may include a robot 500. Figure 30 ) and bracket 30 ( Figure 29 It can also be similarly configured to provide the package carrier 200 to the UAV 100 at the landing pad 40, as described above, compared to the supply inlet 16 and the return inlet 14.

[0259] The interconnectivity of the various components of the enhanced parcel delivery system will now be considered.

[0260] 3. Computer program products, methods, and computing entities

[0261] The embodiments described herein can be implemented in various ways, including as a computer program product comprising an article of manufacture. Such a computer program product may include one or more software elements / components, including, for example, software objects, methods, data structures, etc. Software components can be encoded in any of a variety of programming languages. An exemplary programming language may be a low-level programming language, such as assembly language associated with a specific hardware architecture and / or operating system platform. Software components including assembly language instructions may need to be converted into executable machine code by an assembler before execution by the hardware architecture and / or platform. Another example programming language may be a high-level programming language that is portable across multiple architectures. Software components including high-level programming language instructions may need to be converted into an intermediate representation by an interpreter or compiler before execution.

[0262] Other examples of programming languages ​​include, but are not limited to, macro languages, shell or command languages, job control languages, scripting languages, database query or retrieval languages, and / or report writing languages. In one or more example embodiments, a software component including instructions from one of the programming language examples described above can be executed directly by an operating system or other software components without first being converted to another form. Software components can be stored as files or other data storage constructs. Software elements / components of similar type or related functionality can be stored together, for example, in a specific directory, folder, or library. Software elements / components can be static (e.g., pre-built or fixed) or dynamic (e.g., created or modified at runtime).

[0263] Computer program products may include non-transitory computer-readable storage media that store application programs, programs, program modules, scripts, source code, program code, object code, bytecode, compiled code, interpreted code, machine code, executable instructions, etc. (also referred to herein as executable instructions, execution instructions, computer program products, program code, and / or similar terms used interchangeably herein). Such non-transitory computer-readable storage media includes all computer-readable media (including volatile and non-volatile media).

[0264] In one embodiment, a non-volatile computer-readable storage medium may include a floppy disk, a flexible disk, a hard disk, a solid-state storage device (SSS) (e.g., a solid-state drive (SSD), a solid-state card (SSC), a solid-state module (SSM), an enterprise-class flash drive, magnetic tape, or any other non-transitory magnetic medium). Non-volatile computer-readable storage media may also include punched cards, paper tape, optically marked sheets (or any other physical medium with perforated patterns or other optically identifiable markings), optical disc read-only memory (CD-ROM), rewritable optical disc (CD-RW), digital versatile optical disc (DVD), Blu-ray disc (BD), or any other non-transitory optical medium. Such non-volatile computer-readable storage media can also include read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory (e.g., serial, NAND, NOR, etc.), multimedia memory cards (MMC), secure digital storage (SD) cards, SmartMedia cards, compact flash memory (CF) cards, Memory Stick, etc. Furthermore, non-volatile computer-readable storage media can also include conductive bridged random access memory (CBRAM), phase-change random access memory (PRAM), ferroelectric random access memory (FeRAM), non-volatile random access memory (NVRAM), magnetoresistive random access memory (MRAM), resistive random access memory (RRAM), silicon-oxide-nitride-oxide-silicon memory (SONOS), floating junction gate random access memory (FJG RAM), millipede memory, racetrack memory, etc.

[0265] In one embodiment, the volatile computer-readable storage medium may include RAM, DRAM, SRAM, FPMDRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory, register memory, etc. It should be understood that, in the context of describing embodiments using computer-readable storage media, other types of computer-readable storage media may be used instead of those described above.

[0266] It should be understood that various embodiments of the present invention can also be implemented as methods, apparatus, systems, computing devices, computing entities, etc. Thus, embodiments of the present invention can take the form of apparatuses, systems, computing devices, computing entities, etc., that execute instructions stored on a computer-readable storage medium to perform certain steps or operations. Therefore, embodiments of the present invention can also take the form of completely hardware embodiments, completely computer program product embodiments, and / or embodiments including a combination of computer program products and hardware that perform certain steps or operations.

[0267] Embodiments of the present invention are described below with reference to block diagrams and flowcharts. Therefore, it should be understood that each block of the block diagrams and flowcharts can be implemented as a computer program product, a complete hardware embodiment, a combination of hardware and computer program products, and / or an apparatus, system, computing device, computing entity, etc., that executes instructions, operations, steps, and interchangeable terms (e.g., executable instructions, instructions for execution, program code, etc.) on a computer-readable storage medium. For example, code retrieval, loading, and execution can be performed sequentially, such that one instruction is retrieved, loaded, and executed at a time. In some exemplary embodiments, retrieval, loading, and / or execution can be performed in parallel, such that multiple instructions are retrieved, loaded, and / or executed together. Therefore, such embodiments can produce machines with specific configurations that perform the steps or operations specified in the block diagrams and flowcharts. Thus, the block diagrams and flowcharts support various combinations of embodiments for performing specified instructions, operations, or steps.

[0268] 4. Exemplary System Architecture

[0269] Figure 46 Illustrations of exemplary embodiments of the present invention are provided. For example... Figure 46As shown, this particular embodiment may include one or more central computing entities 802, one or more networks 800, one or more user computing entities 804, one or more mobile carrier computing entities 806, one or more UAV computing entities 808, one or more parcel carrier computing entities 212, one or more delivery vehicle computing entities 810, etc. Each of these components, entities, devices, systems, and similar terms used interchangeably herein may communicate directly or indirectly with each other, for example, via the same or different wired or wireless networks. Furthermore, although... Figure 43 Various system entities are shown as separate, independent entities, but various embodiments are not limited to this particular architecture.

[0270] A. Exemplary Central Computing Entity

[0271] Figure 47 A schematic diagram of a central computing entity 802 according to an embodiment of the present invention is provided. The central computing entity 802 can be operated by various entities, including carriers. As will be appreciated, carriers can be traditional carriers such as UPS, FedEx, DHL, express delivery services, the United States Postal Service (USPS), Canada Post, freight companies (e.g., trucking, less-than-truckload (LTL), rail carriers, air carriers, ocean carriers, etc.). However, carriers can also be non-traditional carriers such as Coyote, Amazon, Google, Airbus, Uber, ride-sharing services, crowdsourcing services, retailers, etc.

[0272] As shown, in one embodiment, the central computing entity 802 may also include one or more communication elements / components 908 for communicating with various computing entities, such as by transmitting information / data, content, information and / or similar terms that may be used interchangeably herein, which can be sent, received, manipulated, processed, displayed, stored, etc.

[0273] like Figure 47As shown, in one embodiment, the central computing entity 802 may include or communicate with one or more processing elements / components 902 (also referred to as processors, processing circuitry, processing devices, and / or similar terms used interchangeably herein) via, for example, a bus, or other elements / components within the central computing entity 802. As will be understood, the processing element / component 902 may be embodied in a variety of different ways. For example, the processing element / component 902 may be embodied as one or more CPLDs, “cloud” processors, microprocessors, multi-core processors, coprocessor entities, ASIPs, microcontrollers, and / or controllers. Furthermore, the processing element / component 902 may be embodied as one or more other processing devices or circuitry. The term “circuit” can refer to a completely hardware embodiment or a combination of hardware and computer program products. Thus, the processing element / component 902 may be embodied as an integrated circuit, ASIC, FPGA, PLA, hardware accelerator, other circuitry, etc. Thus, as will be understood, the processing element / component 902 may be configured for a particular purpose or configured to execute instructions stored in volatile or non-volatile media or accessible to the processing element / component 902. Thus, whether configured by hardware or computer program products, or by a combination thereof, the processing element / component 902 can perform the steps or operations according to embodiments of the present invention when configured accordingly.

[0274] In one embodiment, the central computing entity 802 may also include or communicate with memory components / elements (e.g., non-volatile media (also referred to as non-volatile memory, memory, storage device, memory circuitry, and / or similar terms used interchangeably herein)). In one embodiment, the non-volatile storage device or memory may include one or more non-volatile memories or storage media 904, including but not limited to hard disks, ROMs, PROMs, EPROMs, EEPROMs, flash memory, MMC, SD memory cards, memory sticks, CBRAMs, PRAMs, FeRAMs, NVRAMs, MRAMs, RRAMs, SONOS, FJGRAMs, millipede memory, racetrack memory, etc. As will be appreciated, non-volatile memories or storage media may store databases, database instances, database management systems, information / data, applications, programs, program modules, scripts, source code, object code, bytecode, compiled code, interpreted code, machine code, executable instructions, etc. The terms database, database instance, database management system, and / or similar terms that may be used interchangeably herein may refer to a collection of records or data stored in a computer-readable storage medium, using one or more database models, such as hierarchical database models, network models, relational models, entity-relational models, object models, document models, semantic models, graph models, etc.

[0275] In one embodiment, the memory component / element may further include or communicate with volatile media (also referred to as volatile memory, memory, storage device, memory circuitry, and / or similar terms used interchangeably herein). In one embodiment, the volatile storage device or memory may also include one or more volatile memories or storage media 906, including but not limited to RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory, register memory, etc. As will be appreciated, the volatile memory or storage media may be used to store at least a portion of databases, database instances, database management systems, information / data, applications, programs, program modules, scripts, source code, object code, bytecode, compiled code, interpreted code, machine code, executable instructions, etc., executed by, for example, processing element / component 902. Therefore, databases, database instances, database management systems, information / data, applications, programs, program modules, scripts, source code, object code, bytecode, compiled code, interpreted code, machine code, executable instructions, etc., can be used to control certain aspects of the operation of the central computing entity 802 with the help of the processing element / component 902 and the operating system.

[0276] As shown, in one embodiment, the central computing entity 802 may further include one or more communication components / elements 908 for communicating with various computing entities, for example by transmitting information / data, content, information, and / or similar terms that may be sent, received, manipulated, processed, displayed, stored, etc., and / or used interchangeably herein. Such communication may be performed using wired data transmission protocols such as FDDI, DSL, ATM, Frame Relay, DOCSIS, or any other wired transmission protocol. Similarly, the central computing entity 802 may be configured to communicate via a wireless external communication network using any of the various protocols, such as GPRS, UMTS, CDMA2000, lxRTT, WCDMA, GSM, EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, UWB, IR protocol, NFC protocol, Wibree, Bluetooth protocol, Wireless USB protocol, and / or any other wireless protocol.

[0277] Although not shown, the central computing entity 802 may include or communicate with one or more input components / elements (e.g., keyboard input, mouse input, touchscreen / display input, motion input, movement input, audio input, indicator device input, joystick input, keyboard input, etc.). The central computing entity 802 may also include or communicate with one or more output components / elements (e.g., audio output, video output, screen / display output, motion output, movement output, etc.).

[0278] As will be understood, for example in a distributed system, one or more central computing entity 802 elements / components may be located remotely from other central computing entity 802 elements / components. That is, the term "central" is used in a general sense and is not intended to necessarily indicate a central location. Furthermore, one or more elements / components may be combined, and additional elements / components that perform the functions described herein may be included in the central computing entity 802. Thus, the central computing entity 802 can be adapted to various needs and environments. As will be appreciated, these architectures and descriptions are provided for illustrative purposes only and are not intended to limit the various embodiments.

[0279] B. Exemplary User Computing Entity

[0280] Users can be individuals, families, companies, organizations, entities, departments within an organization, representatives of organizations and / or individuals, etc. Therefore, as will be appreciated, in some embodiments, the user can be a shipper and / or consignee. For this purpose, the user can operate user computing entity 804, which includes one or more elements / components that are functionally similar to the central computing entity 802.

[0281] Figure 48An exemplary schematic diagram is provided to represent a user computing entity 804 that can be used in conjunction with embodiments of the present invention. Generally, the terms apparatus, system, computing entity, entity, and / or similar terms that are used interchangeably herein may refer to, for example, one or more computers, computing entities, desktop computers, mobile phones, tablets, phablets, laptops, laptops, distributed systems, smart home entities, kitchen appliances, Google Home, Amazon Echo, garage door openers, cameras, imaging devices, thermostats, security systems, networks, game consoles (such as Xbox, PlayStation, Wii), watches, glasses, iBeacon, proximity beacons, remote keys, RFID tags, headphones, scanners, televisions, dongles, cameras, wristbands, wearable items / devices, items / devices, vehicles, telephone booths, input terminals, servers or server networks, blade servers, gateways, switches, processing devices, processing entities, set-top boxes, relays, routers, network access points, base stations, etc., and / or any combination of apparatus or entities suitable for performing the functions, operations, and / or processes described herein. As shown in Figure 45, user computing entity 804 may include communication components / elements, such as antenna 912, transmitter 914 (e.g., radio), and receiver 916 (e.g., radio). Similarly, user computing entity 804 may include processing elements / elements 918 (e.g., CPLD, microprocessor, multi-core processor, cloud processor, coprocessor entity, ASIP, microcontroller, and / or controller) that provide signals to and receive signals from the communication elements / elements.

[0282] The signals provided to and received from transmitter 914 and receiver 916 may include signaling information / data conforming to the air interface standard of the applicable wireless system. In this regard, user computing entity 804 may be able to operate using one or more air interface standards, communication protocols, modulation types, and access types. More specifically, user computing entity 804 may operate according to any of a plurality of wireless communication standards and protocols, such as those described above with respect to central computing entity 802. In certain embodiments, user computing entity 804 may operate according to a variety of wireless communication standards and protocols, such as UMTS, CDMA2000, lxRTT, WCDMA, GSM, EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, UWB, IR, NFC, Bluetooth, USB, etc. Similarly, user computing entity 804 may operate according to a plurality of wired communication standards and protocols, such as those described above with respect to central computing entity 802 via network interface 908.

[0283] Through these communication standards and protocols, user computing entity 804 can communicate with various other entities using concepts such as Unstructured Supplemental Service Data (USSD), Short Message Service (SMS), Multimedia Messaging Service (MMS), Dual-Tone Multi-Frequency Signaling (DTMF), and / or Subscriber Identity Module Dialer (SIM Dialer). User computing entity 804 can also download changes, plugins, and updates to, for example, its firmware, software (e.g., including executable instructions, applications, program modules), and operating system.

[0284] According to one embodiment, user computing entity 804 may include location determining elements / components, aspects, devices, modules, functions, and / or similar terms used interchangeably herein. For example, user computing entity 804 may include an outdoor positioning aspect, such as a location module adapted to acquire, for example, latitude, longitude, altitude, geocoding, route, direction, heading, speed, Universal Time (UTC), date, and / or various other information / data. In one embodiment, the location module may acquire information / data, sometimes referred to as ephemeris information / data, by identifying the number of satellites in a view and the relative positions of those satellites (e.g., using a Global Positioning System (GPS)). Satellites may be a variety of different satellite systems, including Low Earth Orbit (LEO) satellite systems, Department of Defense (DOD) satellite systems, the European Union Galileo positioning system, the Chinese BeiDou Navigation Satellite System, the Global Navigation Satellite System (GLONASS), the Indian Regional Navigation Satellite System, etc. This information / data can be collected using various coordinate systems, such as decimal degrees (DD); degrees, minutes, and seconds (DMS); Universal Transverse Mercator (UTM); Universal Polar Spherical (UPS) coordinate system, etc. Alternatively, location information / data can be determined by triangulation of the user computing entity 804's location in conjunction with various other systems, including cell towers, Wi-Fi access points, etc. Similarly, the user computing entity 804 may include indoor positioning aspects, such as location modules adapted to acquire, for example, latitude, longitude, altitude, geocoding, route, direction, heading, speed, time, date, and / or various other information / data. Some indoor systems may use a variety of location or positioning technologies, including RFID tags, indoor beacons or transmitters, Wi-Fi access points, cell towers, nearby computing devices (e.g., smartphones, laptops), etc. These technologies may include, for example, iBeacon, gimbal proximity beacons, Bluetooth Low Energy (BLE) transmitters, Bluetooth Smart, NFC transmitters, etc. These indoor positioning aspects can be used in various setups to determine the location of a person or object within inches or centimeters.

[0285] User computing entity 804 may also include a user interface (which may include a display 919 coupled to processing element / component 918) and / or a user input interface (coupled to processing element / component 918). For example, the user interface may be a user application, browser, user interface, interface, and / or similar terms used interchangeably herein that execute on and / or are accessible via user computing entity 804 to interact with and / or cause the display of information / data from central computing entity 802, as described herein. The user input interface may include any of a plurality of means or interfaces that allow user computing entity 804 to receive information / data, such as a keyboard 920 (hard or soft), a touch display, a voice / speech or motion interface, or other input means. In embodiments including keyboard 920, keyboard 920 may include (or cause the display of) conventional numbers (0-9) and related keys (#, *), as well as other keys for operating user computing entity 804, and may include a full set of alphanumeric keys or a set of keys that can be activated to provide a full set of alphanumeric keys. In addition to providing input, the user input interface can also be used to activate or deactivate certain functions, such as screen savers and / or sleep modes.

[0286] User computing entity 804 may also include memory elements / components that may be embedded and / or removable, such as volatile memory devices or memories 922 and / or non-volatile memory devices or memories 924. For example, non-volatile memory may be ROM, PROM, EPROM, EEPROM, flash memory, MMC, SD memory card, Memory Stick, CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, millipede memory, racetrack memory, etc. Volatile memory may be RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory, register memory, etc. Volatile and non-volatile storage devices or memories can store databases, database instances, database management systems, information / data, applications, programs, program modules, scripts, source code, object code, bytecode, compiled code, interpreted code, machine code, executable instructions, etc., to implement the functions of user computing entity 804. As shown, this can include user applications residing on the entity or accessible through a browser or other user interface for communicating with central computing entity 802, mobile carrier computing entity 806, UAV computing entity 808, delivery vehicle computing entity 810, and / or various other computing entities.

[0287] In another embodiment, user computing entity 804 may include one or more elements / components or functions that are the same as or similar to those of central computing entity 802, as described in more detail above. As will be appreciated, these architectures and descriptions are provided for illustrative purposes only and are not intended to limit the various embodiments.

[0288] C. Exemplary UAV computing entity

[0289] Figure 49 Illustrative schematics are provided of a UAV computing entity 808 that can be used in conjunction with embodiments of the present invention. As described above, the elements / components of the UAV computing entity 808 may be similar to those described with respect to the central computing entity 802, the user computing entity 804, and / or the mobile carrier computing entity 806. In one embodiment, the UAV computing entity 808 may also include one or more control elements / components (not shown) and / or be associated with one or more control elements / components (not shown) for controlling and operating the UAV 100 as described herein. Figure 49 As shown, the UAV computing entity 808 may include communication elements / components 908, such as those described above with respect to the central computing entity 802 and / or the user computing entity 804. For example, the UAV computing entity 808 can operate according to any of a plurality of wireless communication standards, such as UMTS, CDMA2000, lxRTT, WCDMA, GSM, EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, UWB, IR, NFC, Bluetooth, BLE, Wibree, USB, etc. Similarly, the UAV computing entity 808 can operate according to a plurality of wired communication standards and protocols, such as those described with respect to the central computing entity 802, user computing entity 804, etc., via the communication elements / components. Therefore, UAV 100 (e.g., UAV computing entity 808) may be able to communicate with various computing entities (including user computing entity 804 (e.g., smart home entity)) to, for example, provide instructions to open a garage door, provide notifications / messages, etc. UAV computing entity 808 may also include one or more processing elements / components 405, including the processing elements / components described with respect to central computing entity 802 and / or user computing entity 804.

[0290] As shown, UAV 100 (e.g., UAV computing entity 808) may have the ability to operate according to multiple long-range and short-range communication standards and protocols and use multiple wireless operators (e.g., China Mobile, Vodafone, Telefónica, T-Mobile, Verizon, AT&T, and Qtel). For example, multiple wireless operators providing wireless services may exist within a single geographic area (e.g., country, region, state, county, city, or town). Similarly, when communicating with the primary package delivery vehicle 10 (or various other computing entities), UAV computing entity 808 may have the ability to use long-range and short-range communication standards and protocols, depending on the proximity of UAV 100 to the primary package delivery vehicle 10 and / or the operational status of UAV 100 (e.g., whether propulsion component 102 is active or inactive).

[0291] In one embodiment, a central computing entity 802 may manage the access of UAV computing entities 808 to multiple wireless operators and / or the use of long-range and short-range communication standards and protocols in one or more geographic areas. For example, various wireless operators may be used to activate UAV 100s associated with various geographic areas. Activating a UAV computing entity 808 with a wireless operator may include registering each UAV computing entity 808 with the wireless operator from which it is expected to serve (e.g., based on the operating area of ​​UAV 100). In cases where many UAV 100s need to be managed, the central computing entity 802 may provide an automated activation process. In some embodiments, configuring UAV 100s in a given geographic area to operate through more than a few wireless operators may be impractical. For example, in one embodiment, activating UAV 100s on two wireless operators may be sufficient: a primary wireless operator and a secondary wireless operator. In other embodiments, a third or fourth activation may be justified based on the available wireless services and actual coverage patterns in the geographic areas where UAV 100s will be used.

[0292] In addition to activating the UAV computing entity 808, the central computing entity 802 can also be used to configure the UAV computing entity 808 to use the wireless services of wireless operators and / or various long-range and short-range communication standards and protocols. To this end, the central computing entity 802 can create and provide configurations (e.g., profiles) for all UAVs 100 operating within a specific geographic area (e.g., country, region, state, county, city, town, or other area). This configuration can also provide the order in which wireless operators should be accessed and / or the status or proximity of the primary package delivery vehicle 10 that should use long-range and short-range communication standards and protocols.

[0293] In one embodiment, the central computing entity 802 can create and provide UAV type configurations for each type of UAV computing entity 808 used by the enterprise. For example, the enterprise may have different types of UAV computing entities 808, each using different hardware, firmware, and software. Therefore, the different configurations can be quite extensive and can be customized, for example, to individual UAV computing entities 808. In one embodiment, the UAV type configuration can be used to provide the UAV computing entity 808 with optimization parameters, such as default values ​​embedded at build time, for example, the number of times a failed carrier dialing is allowed before changing the current wireless carrier (e.g., from a primary wireless carrier to a secondary wireless carrier).

[0294] As shown, the configuration can identify a primary wireless operator and one or more secondary wireless operators for wireless service. In one embodiment, the primary wireless operator can be the wireless operator that the UAV computing entity 808 should use under normal conditions. One or more secondary wireless operators can be the wireless operators that the UAV computing entity 808 can use in the event of, for example, a communication problem with the primary wireless operator. For example, when something fails and cannot be restored by establishing a new session with the primary wireless operator, the UAV computing entity 808 can switch from the primary wireless operator to a secondary wireless operator. Identifying the appropriate secondary wireless operator to use can be based on a variety of factors, including location, coverage availability, signal strength, etc.

[0295] Similarly, the configuration can identify the primary long-range standard / protocol and the secondary short-range standard / protocol. In one embodiment, the primary long-range standard / protocol (e.g., LTE, GSM) can be the radio standard / protocol that the UAV computing entity 808 should use when its operating state is on or active (e.g., when the propulsion component 102 of the UAV 100 is active). The secondary short-range standard / protocol (e.g., BLE, UWB) can be the radio standard / protocol that the UAV 100 should use when its operating state is off or inactive (e.g., when its propulsion component 102 is inactive). The use of the secondary radio standard / protocol can also be determined based on the proximity of the UAV 100 to the primary package delivery vehicle 10. For example, when the UAV 100 is within 100 feet of the primary package delivery vehicle 10, the UAV can use either the short-range standard / protocol or a dual-band approach until its operating state changes.

[0296] In one embodiment, by using various technologies and common control mechanisms (e.g., software), the UAV computing entity 808 can use various standards / protocols to manage communication with multiple wireless operators and drive network connectivity. This can include path switching (e.g., software path switching) implemented at runtime when it makes sense to act differently based on identified practical conditions, depending on the different hardware builds to be used. Typically, path switching can refer to software branching, for example, to meet the needs of a particular UAV computing entity 808. Furthermore, to accommodate different UAV computing entities 808, conditional compile-time switches can be used to make code blocks adaptable to a specific UAV computing entity 808.

[0297] According to one embodiment, UAV computing entity 808 may include location determination elements / components, aspects, devices, modules, functions, and / or similar terms used interchangeably herein. As previously described, such outdoor positioning aspects may include location modules adapted to acquire, for example, latitude, longitude, altitude, geocoding, route, direction, heading, speed, UTC, date, and / or various other information / data. In one embodiment, the location module may acquire information / data, sometimes referred to as ephemeris information / data, by identifying the number of satellites in a view and the relative positions of those satellites (e.g., GPS). Satellites may be a variety of different satellite systems, including the LEO satellite system, GLONASS satellite system, DOD satellite system, EU Galileo positioning system, China's BeiDou Navigation Satellite System, India's Regional Navigation Satellite System, etc. This information / data may be collected using various coordinate systems (e.g., DD; DMS; UTM; UPS coordinate systems, etc.). Alternatively, location information / data may be determined by triangulation of the location of user computing entity 804 in conjunction with various other systems (including cell towers, Wi-Fi access points, etc.). Similarly, the UAV computing entity 808 may include indoor positioning aspects, such as a location module adapted to acquire information / data such as latitude, longitude, altitude, geocoding, route, direction, heading, speed, time, date, and / or various other information / data. Some indoor systems may use a variety of location or positioning technologies, including RFID tags, indoor beacons or transmitters, Wi-Fi access points, cellular towers, nearby computing devices (e.g., smartphones, laptops), etc. These technologies may include, for example, iBeacon, gimbal proximity beacons, BLE transmitters, Bluetooth Smart, NFC transmitters, etc. These indoor positioning aspects can be used in various setups to determine the location of a person or object within inches or centimeters.

[0298] UAV computing entity 808 may also include one or more memory elements / components 915, which may be embedded and / or removable. For example, non-volatile memory may be ROM, PROM, EPROM, EEPROM, flash memory, MMC, SD memory card, Memory Stick, CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, worm memory, track memory, etc. Volatile memory may be RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, TTRAM, T-RAM, Z-RAM, RIMM, DIMM, SIMM, VRAM, cache memory, register memory, etc. Volatile and non-volatile storage devices or memories can store databases, database instances, database management systems, information / data, applications, programs, program modules, scripts, source code, object code, bytecode, compiled code, interpreted code, machine code, executable instructions, etc., to implement the functionality of UAV computing entity 808.

[0299] As shown, UAV computing entity 808 may include one or more sensing elements / components, modules, and / or similar terms used interchangeably herein and / or be associated with one or more sensing elements / components, modules, and / or similar terms used interchangeably herein. In an embodiment, the one or more sensing elements / components include a ground landing sensor 162, a vehicle landing sensor 164, a route / flight guidance sensor 166, and a camera 168. UAV computing entity 808 may include sensing elements / components such as motor / engine sensors, fuel sensors, battery sensors, speed sensors, route / flight time sensors, altitude sensors, barometer sensors, airborne telemetry sensors, ground telemetry sensors, gyroscope sensors, pressure sensors, position sensors, weight sensors, emission sensors, temperature sensors, magnetic sensors, current sensors, tilt sensors, motor / engine intake sensors, motor / engine output sensors, and / or carrier sensors. The sensed information / data may include, but is not limited to, air velocity information / data, ground velocity information / data, emission information / data, RPM information / data, acceleration information / data, tilt information / data, oil pressure information / data, pressure information / data, rotation information / data, distance information / data, fuel information / data, idle information / data, weight information / data, etc. (which can be referred to as telematics information / data). Sensing elements / components may include environmental sensors, such as air quality sensors, chemical sensors, precipitation sensors, temperature sensors, etc. Therefore, the sensed information / data may also include carbon monoxide (CO), nitrogen oxides (NOx), sulfur oxides (SOx), ethylene oxide (EtO), ozone (O3), hydrogen sulfide (H2S) and / or ammonium (NH4) information / data, temperature information / data, pressure information / data, and / or meteorological information / data (which can be referred to as weather or atmospheric information / data).

[0300] As described above, the ground landing sensor 162 and the vehicle landing sensor 164 may include one or more sonar sensors / optical sensors (e.g., lidar, LiDAR, and laser detection and ranging (LADAR)), magnetic field sensors, radio wave sensors (e.g., radar (RADAR)), thermal sensors, infrared sensors, image sensors, etc. Furthermore, the vehicle landing sensor 164 and the camera 168 may include one or more image sensors for capturing, collecting, and / or recording image information / data (e.g., sensed information / data). Image information / data can be captured and stored in various formats. For example, image information / data (including 360° video) can be captured in various formats or converted into various formats, such as Joint Image Experts Group (JPEG), Motion JPEG (MJPEG), Moving Picture Experts Group (MPEG), Graphics Interchange Format (GIF), Portable Web Graphics (PNG), Tagged Image File Format (TIFF), Bitmap (BMP), H.264, H.263, Flash Video (FLV), Hypertext Markup Language 5 (HTML5), VP6, VP8, 4K, etc. Such sensor information / data can be captured, collected, and / or recorded using various technologies and methods for various purposes (e.g., takeoff, landing, delivery, collision avoidance, routing, etc.).

[0301] D. Exemplary Delivery Vehicle Computing Entity

[0302] Refer again Figure 46 One or more delivery vehicle computing entities 810 may be attached, fixed, or arranged on the main parcel delivery vehicle 10, or integrated into or part of the main parcel delivery vehicle 10. The delivery vehicle computing entity 810 may collect telematics information / data (including location information / data) and transmit / send the information / data to various other computing entities via one of several communication methods.

[0303] In one embodiment, the delivery vehicle computing entity 810 may include, or be associated with, or wirelessly communicate with, one or more processing elements / components, location determination elements / components, one or more communication elements / components, one or more sensing elements / components, one or more memory location determination elements / components, one or more power supplies, etc. These elements / components may be similar to those described with respect to the central computing entity 802, the user computing entity 804, the mobile carrier computing entity 806, and / or the UAV computing entity 808.

[0304] In one embodiment, the one or more location-determining elements / components may be one of several components that communicate with or are compatible with the delivery vehicle computing entity 810 via wired or wireless communication. Furthermore, the one or more location-determining elements / components may be compatible with various satellite or navigation systems, coordinate systems, etc. Therefore, the one or more location-determining elements / components may be used to receive latitude, longitude, altitude, heading or direction, geocoding, route, location, time, and / or speed information / data (e.g., referred to herein as telematics information / data and further described below). The one or more location-determining elements / components may also communicate with the central computing entity 802, the delivery vehicle computing entity 810, the mobile carrier computing entity 806, and / or similar computing entities.

[0305] As shown, in addition to one or more elements / components, the delivery vehicle computing entity 810 may include one or more sensing elements / components, modules, and / or similar terms used interchangeably herein, and / or associated with them. For example, sensing elements / components may include vehicle sensors such as electric motor / engine sensors, fuel sensors, odometer sensors, wheel hub sensors, tire pressure sensors, position sensors, weight sensors, emission sensors, door sensors, and speed sensors. Sensed information / data may include, but is not limited to, speed information / data, emission information / data, RPM information / data, tire pressure information / data, oil pressure information / data, seatbelt usage information / data, distance information / data, fuel information / data, idle information / data, etc. (which may be referred to as telematics information / data). Sensing elements / components may include environmental sensors, such as air quality sensors, temperature sensors, etc. Therefore, sensed information / data may also include CO, NO... X SO X Information / data on EtO, O3, H2S and / or NH4, and / or meteorological information / data (which may be referred to as weather, environmental and / or atmospheric information / data).

[0306] In one embodiment, the delivery vehicle computing entity 810 may also communicate with a vehicle control module or system. The vehicle control module or system (which may be an scalable and subordinate device to the delivery vehicle computing entity 810) may have information / data processing capabilities to decode and store analog and digital inputs from the vehicle system and sensors. The vehicle control module or system may further have information / data processing capabilities to collect and provide telematics information / data to the J-Bus (which may allow transmission to the delivery vehicle computing entity 810), and output standard vehicle diagnostic codes when received from the vehicle's J-Bus-compatible onboard controllers and / or sensors.

[0307] As will be appreciated, the delivery vehicle computing entity 810 may include communication elements / components, such as those described with respect to the central computing entity 802, the UAV computing entity 808, and / or the user computing entity 804. Furthermore, the delivery vehicle computing entity 810 may be communicatively coupled to the robot processor 522 and the conveyor controller 460, and may control the operation of the robot 500 and the conveyor 440, as will be described in more detail herein.

[0308] E. Exemplary Package Carrying Device Computing Entity

[0309] In one embodiment, the package carrier computing entity 212 may include one or more elements / components that are functionally similar to those of the central computing entity 802, user computing entity 804, UAV computing entity 808, and / or delivery vehicle computing entity 810. For example, in one embodiment, each package carrier computing entity 212 may include one or more processing elements / components (e.g., CPLD, microprocessor, multi-core processor, cloud processor, coprocessor entity, ASIP, microcontroller, and / or controller), one or more display / input devices (e.g., including a user interface), volatile and non-volatile storage devices or storage elements / components, and / or one or more communication elements / components. For example, a user interface may be a user application, browser, user interface, interface, and / or similar terms used interchangeably herein that execute on and / or are accessible via the package carrier computing entity 212 to interact with and / or cause the display of information / data from the central computing entity 802, as described herein. This also enables the package carrier computing entity 212 to communicate with various other computing entities (such as UAV computing entity 808) and / or various other computing entities. As will be appreciated, these architectures and descriptions are provided for illustrative purposes only and are not intended to limit the various embodiments.

[0310] F. Exemplary Mobile Carrier Computing Entity

[0311] In one embodiment, mobile carrier computing entity 806 may include one or more elements / components that are functionally similar to those of central computing entity 802, user computing entity 804, UAV computing entity 808, and / or delivery vehicle computing entity 810. For example, in one embodiment, each mobile carrier computing entity 806 may include one or more processing elements / components (e.g., CPLD, microprocessor, multi-core processor, cloud processor, coprocessor entity, ASIP, microcontroller, and / or controller), one or more display devices / input devices (e.g., including a user interface), volatile and non-volatile storage devices or storage elements / components, and / or one or more communication elements / components. For example, a user interface may be a user application, browser, user interface, interface, and / or similar terms used interchangeably herein, that executes on and / or is accessible via mobile carrier computing entity 806 to interact with and / or cause the display of information / data from central computing entity 802, as described herein. This also enables the mobile carrier computing entity 806 to communicate with various other computing entities, such as the user computing entity 804 and / or various other computing entities. As will be appreciated, these architectures and descriptions are provided for illustrative purposes only and are not intended to limit the various embodiments.

[0312] Reference will now be made to a delivery method for delivering package 300 via UAV 100. In various embodiments, UAV 100 may be assigned based on logical grouping, geofencing, etc.

[0313] G. Geographic Information / Data Database

[0314] In one embodiment, each computing entity may include or communicate with one or more geographic information / data databases (not shown) configured to access, process, provide, manipulate, store, etc., map information / data. For example, a geographic information / data database may include or be able to access a map information / data database containing various data (e.g., map information / data) for displaying maps, constructing routes / flights, or navigation paths, and / or other map-related functions for land, sea, and / or air vehicles. For example, a geographic information / data database may communicate with or include a geographic information / data database that includes map information / data provided by a map provider computing entity. For example, a geographic information / data database may include node data, waypoint records, street / flight / route segment records, point of interest (POI) data records, event of interest data records, serviceable point 5901 data records, and other data records. In one embodiment, other data records include cartographic (“carto”) data records, routing data records (e.g., for routing and navigating vehicles to specific points), etc. For example, a geographic information / data database may include map information / data, which includes boundary, location, and attribute information / data corresponding to various serviceable points, points of interest, events of interest, etc.

[0315] One or more portions, components, areas, layers, features, text, and / or symbols of POI or event data may be stored in one or more of these data records, linked to one or more of these data records, and / or associated with one or more of these data records. For example, one or more portions of POI, event data, or recorded route / flight information may be matched with a corresponding map or geographic record by, for example, location or GNSS and / or GPS data (e.g., using known or future map matching, geocoding, and / or reverse geocoding techniques). As will be appreciated, map information / data can be stored using various formats, layers, etc. (including shapefiles, ArcMap, geodatabases, coverage, imaging, raster, computer-aided drawing (CAD) files, other storage formats, etc.). For example, a geographic information / data database may appropriately store / record map information / data as part of a digital map, for example, as part of a feature layer, raster layer, service layer, geoprocessing layer, base map layer, service area layer, constitutive area layer, etc.

[0316] In the example embodiment, street / flight / route segment data records are segments representing roads, streets, flight paths, routes, etc. Node data records are endpoints of corresponding links or segments corresponding to street / flight / route segment data records. Street / flight / route segment data records and node data records represent road networks or flight paths used by various types of vehicles. Alternatively, for example, in addition to or in lieu of street / flight / route segment data records, a geographic information / data database may contain path segments and node data records or other data representing pedestrian paths or areas. The objects or data structures of street / flight / route segments and other records may include various information / data associated with each map element. In some examples, this information / data may include the recipient's name, pick-up or delivery identifier, primary delivery point (e.g., first expected delivery point / location 5902), secondary delivery point, street name, street number, street prefix, street suffix, street type, city, state, province, territory, country, postal code, residential or commercial sign, street classification, direction (e.g., one-way <whichever way> or both ways), longitude and latitude, geocoding, location identifier, etc. For example, in one embodiment, map elements may be represented and / or associated with longitude and latitude, geocoding, nearest street / airline / route segment, address, etc. Similarly, streets / airlines / route segments may be represented or associated with a name defining the overall shape and location of the street / airline / route segment, segment identifier, connecting node, address or address range, a series of longitude and latitude coordinates, etc. As will be appreciated, various other methods and techniques can be used to adapt to various needs and environments.

[0317] Street / route / flight segments and nodes can be associated with attributes such as geographic coordinates (e.g., latitude and longitude), names or identifiers, street names, address ranges, speed limits, turning restrictions at intersections, and other navigation-related attributes, as well as service points, events of interest, and / or points of interest (POIs), such as gas stations, hotels, restaurants, museums, stadiums, offices, waypoints, car dealerships, auto repair shops, buildings, shops, parks, etc. For example, service point 5901, event of interest, and / or POI can be represented in a digital map as accessible by one or more street networks or street segments of a street network. Service point 5901, event of interest, POI, street networks, etc., can be represented in a digital map as navigable / traversable / drivable segments or points for driving to and / or from service point 5901, waypoint, event of interest, and / or POI.

[0318] The geographic information / data database may include data about serviceable points 5901, events of interest, and / or POIs, and their corresponding locations within the data records of serviceable points 5901, events of interest, and / or POIs. The geographic information / data database may also include data about locations (e.g., cities, towns, or other communities) and other geographic features (e.g., bodies of water, mountains, etc.). Such location or feature data may be part of the POI data or may be associated with POIs or POI data records (e.g., data points used to display or represent city locations). Furthermore, the geographic information / data database may include and / or be associated with event information / data (e.g., traffic events, buildings, scheduled events, unscheduled events, etc.) associated with POI data records or other records in the geographic information / data database. For example, in one embodiment, serviceable points 5901, events of interest, and / or POIs may be represented and / or associated with longitude and latitude, geocoding, nearest street / flight / route segment, address, etc. As will be appreciated, various other methods and techniques can be used to adapt to various needs and environments.

[0319] In one embodiment, the geographic information / data database may store digital maps. In another embodiment, the geographic information / data database may be linked to one or more map or content provider entities (e.g., mapping websites / servers / providers / databases, including, for example, maps.google.com, bing.com / maps, mapquest.com, Tele...). This involves communicating or associating with one or more map or content provider computing entities that provide map information / data (or other content) of digital maps to various users and / or entities. Using digital maps, appropriate computing entities can provide, for example, map information / data about serviceable points of interest (POIs) (e.g., their location, attributes, etc.), and / or their corresponding street networks based on the map information / data.

[0320] A geographic information / data database can be maintained by a map or content provider (e.g., a map developer) associated with a service platform. For example, a map developer can collect geographic data to generate and enhance the geographic information / data database. Map developers can use various methods to collect data. These methods can include acquiring data from other sources, such as municipalities or their respective geographic authorities. The geographic information / data database can be a master geographic information / data database stored in a format that facilitates updating, maintenance, and development. For example, the master geographic information / data database or the data within it can be in Oracle spatial format, .kml, SQL, PostGIS, or other spatial formats, for example, for development or production purposes. Oracle spatial format or development / production databases can be compiled into delivery formats, such as Geographic Data File (GDF) format. Data in production and / or delivery formats can be compiled or further compiled to form geographic information / data database products or databases that can be used in end-user computing entities or systems.

[0321] 5. Additional features, functions, and operation

[0322] A. Package Information / Data

[0323] In one embodiment, the process may be initiated by a central computing entity 802 generating and / or receiving package information / data for one or more packages 300. For example, a user may initiate the transportation process by inputting identification information / data into the central computing entity 802. In various embodiments, a user (e.g., a user or user representative operating a user computing entity 804) may access the carrier's webpage, application, control panel, browser, or portal. After identifying the user (e.g., based on his or her profile), the user may initiate package 300. In various embodiments, the central computing entity 802 may then provide the user with a user interface (e.g., a browser, control panel, application) or communicate with the user interface to provide package information / data including certain details about package 300. In various embodiments, package information / data may include the sender's and recipient's names, street addresses, cities, states, postal codes, countries, telephone numbers, etc. In various embodiments, the user interface may include a fillable form with fields including shipping information / data and receiving information / data. In various embodiments, some information / data fields may be pre-filled. For example, if a user logs into a registered account / profile, they can pre-fill address information / data entered during registration in certain information / data fields. In some embodiments, the user may also have a digital address book associated with the account, which includes address information / data for possible delivery information / data and / or shipping information / data. The user can be able to select certain delivery information / data and / or shipping information / data for the associated package 300 from the address book.

[0324] In one embodiment, after the central computing entity 802 receives receipt information / data and / or shipment information / data from the user, the central computing entity 802 may perform one or more verification operations. For example, the central computing entity 802 may determine whether a primary address (and / or other address) in a specified country or postal code is eligible for pickup or delivery. The central computing entity 802 may also determine the validity of a primary address (and / or other secondary address) by, for example, passing the primary address through one or more address cleanup or standardization systems. The central computing entity 802 may also perform various anti-fraud measures, such as determining whether the user (or one of the delivery addresses) has been "blacklisted" from the user's pickup and / or delivery. As will be appreciated, various other methods and techniques can be used to adapt to various needs and environments.

[0325] In addition to receiving information / data and / or shipping information / data, package information / data may also include service level information / data. This service level option may be, for example, Same Day UAV, Same Day Ground, Next Day UAV, Next Day Ground, Overnight, Express, Next Day Air Early AM, Next Day Air Saver, Jetline, Sprintline, Secureline, 2nd Day Air, Priority, 2nd Day Air Early AM, 3Day Select, Ground, Standard, First Class, MediaMail, SurePost, Freight, etc.

[0326] In one embodiment, the central computing entity 802 (a) may be provided with characteristics and attributes of package 300 from package information / data, and / or (b) may determine characteristics and attributes of package 300 from package information / data. Characteristics and attributes may include various dimensions, weight, transport classification, planned movement within a carrier's transport and logistics network, planned time, etc., of package 300. For example, length, width, height, base, radius, and weight may be received as input information / data by various carrier systems and / or determined or collected by various carrier systems. For example, sensors or cameras may be positioned to capture or determine the length, width, height, and weight (including volumetric weight) of package 300 as it moves along a conveyor, enters or exits a loading bay, is loaded by a lift truck, or is transported through a carrier's transport and logistics network.

[0327] In one embodiment, using such information / data, the central computing entity 802 can determine / identify the cubic / volume of each package 300. The units of measurement for the equations can be established such that the dimensions resulting from the determination are in cubic feet, cubic inches, or any other volume measurement. In one embodiment, after determining the cubic / volume of the package 300 (and / or making various other determinations), the central computing entity 802 can apply a classification to the package 300 based at least in part on that cubic / volume. The classification can include (1) one package 300 size category, (2) two package 300 size categories, (3) three package 300 size categories, and / or (4) four package 300 size categories. For example, (1) a package size 300 can be defined as being between >0 and ≤2 cubic feet, (2) two packages size 300 can be defined as being between >2 and ≤4 cubic feet, (3) three packages size 300 can be defined as being between >4 and ≤6 cubic feet, and / or (4) four packages size 300 can be defined as being greater than >6 cubic feet. As will be appreciated, a variety of other methods and techniques can be used to accommodate a variety of needs and environments. This can help determine the type of delivery options available for the package, such as UAV delivery or primary package size 300 delivery vehicle 10.

[0328] In one embodiment, the central computing entity 802 may assign or associate one or more planned times with each package 300, as well as planned times for specific activities, routes / routes, etc., related to the package 300. Planned time may be the time spent processing the package 300 (e.g., sorting, repackaging, loading, unloading, inspecting, picking, delivering, marking, over-marking, joining, unjoining, etc.). In one embodiment, each package 300, each activity, each route / route stop, each route / route, etc., may have an overall planned time or associated with additional planned times. Planned times may be based on historical information / data, such as average planned times.

[0329] As shown, the planned time can include the total planned time for package 300, activities, route / flight stops, routes / flights, etc. The total planned time can include various additional planned times (both are interchangeably referred to as planned time herein). The planned time can be based on various factors or parameters. For example, the planned time can be based on the cubic / volume and / or weight of package 300; for instance, moving a package 300 weighing 11.52 pounds from a conveyor belt may take longer than moving a package 300 weighing 32 pounds from the same conveyor belt. Furthermore, the planned time factors and / or parameters can also consider or include the type of package 300, such as whether package 300 requires special handling. The planned time factors and / or parameters can also consider the service level and / or activities to be performed on package 300. For example, based on factors and parameters, the central computing entity 802 can store, access, and / or predict / estimate the planned time for various packages 300 for sorting, processing, conveying, scanning, picking, delivery, etc. For illustrative and not limiting purposes, in order to sort package 300 from the belt conveyor to a location in a full-length trailer, (1) a package size may be assigned an additional planned time of 1 second or a package size category may be associated with an additional planned time of 1 second, (2) two package size categories may be assigned an additional planned time of 1.5 seconds, and so on. Similarly, for loading operations from the warehouse to the vehicle, for example, (1) a planned time of 5 seconds may be assigned to each package size category or a package size category may be associated with a planned time of 5 seconds, (2) a planned time of 7 seconds may be assigned to each two package size categories or a package size category may be associated with a planned time of 7 seconds, (3) a planned time of 10 seconds may be assigned to each three package size categories or a package size category may be associated with a planned time of 10 seconds, and (4) a planned time of 20 seconds may be assigned to each four package size categories or a package size category may be associated with a planned time of 20 seconds. In addition, (1) an additional planned time of 25 seconds is allocated to each special handling category of parcels or each special handling category of parcels is associated with an additional planned time of 25 seconds; (2) an additional planned time of 45 seconds is allocated to every two special handling categories of parcels or each two special handling categories of parcels is associated with an additional planned time of 45 seconds; and (3) an additional planned time of 33 seconds is allocated to every three special handling categories of parcels or each three special handling categories of parcels is associated with an additional planned time of 33 seconds. The additional planned time may also be specific to carrier equipment: unloading systems, loading systems, sorting systems, vehicles, repackaging systems, weighing systems, inspection systems, tools, and / or any other suitable systems. Therefore, the additional planned time can vary for different types of systems (e.g., unloading conveyor A, unloading conveyor B) because the time available for handling specific tasks associated with different systems can vary.Additionally, some additional planned times can vary based on different types of vehicles, as the storage area of ​​a vehicle can vary based on its size. For example, it may take longer or shorter to travel to or near the storage area, as well as to the walls, shelves, etc., near the storage area. In this example, the central computing entity 802 can determine / identify additional planned times associated with the setup of the conveyor (e.g., unloading the conveyor). Furthermore, there may be additional planned times for loading parcel 300 onto the main parcel 300 vehicle 10 or conveyor, sorting parcel 300 at a hub or other center, rewrapping and over-marking parcel 300, scanning parcel 300, and traveling parcel 300 from the main parcel 300 vehicle 10 to its final delivery destination, etc.

[0330] Additional scheduled times can also be specific to the vehicles (also referred to herein as equipment) used in the loading, unloading, picking, and / or delivery operations of package 300 and one or more bundles / containers. For example, central computing entity 802 can determine the number of packages 300 that can be loaded or unloaded from a trailer or truck within a given time period based on the size of the truck / trailer, etc. (e.g., 40-foot trailer, 50-foot trailer). Thus, in response to identifying the selected primary package 300 vehicle 10 (from which packages 300 are unloaded and / or loaded), central computing entity 802 can determine / identify additional scheduled times (e.g., unloading system, loading system) in part based on the size of the trailer / truck and / or equipment used. As will be appreciated, longer trailers / trucks may require more additional scheduled time than shorter trailers, for example, transporting packages 300 (e.g., package 300), and may, but does not necessarily, require longer conveyors, which may require more setup time than shorter conveyors. Additionally, in some embodiments, a package 300 of various size categories may be stored in one or more bundles / containers (e.g., bags, boxes, etc.). Thus, when the central computing entity 802 determines that a bundle / container includes an instance of a package 300 size category, the central computing entity 802 may allocate additional scheduled time to the bundle / container, which may reduce or increase the processing time for a given load of a package 300 size category.

[0331] In one embodiment, the central computing entity 802 can determine / identify the total planned time for handling, transporting, warehousing, sorting, loading, unloading, repackaging, inspecting, picking, and delivering parcel 300 from entry into the carrier's transportation and logistics network until delivery to its final delivery destination. Additionally, the central computing entity 802 can determine the planned time for different branches or activities of a given parcel 300 (e.g., the planned time for picking or delivering parcel 300). In one embodiment, the total planned time can be an estimated time that does not take into account various potential additional planned times.

[0332] Continuing the example above, for four package size categories with cubes of 2.315 cubic feet and weighing 15 pounds, the central computing entity 802 can allocate the total planned time for picking up package 300 from the ABC distribution warehouse in Orlando, Florida, and delivering it to 123 Springfield Road, Norcross, Georgia 30092. The total planned time can be estimated based on historical information / data about similar packages 300, and / or the sum of various activities to be performed on the package (including picking up and delivering package 300). For example, the total planned time for a package might be 0.0352778 hours (127 seconds). This can represent the total allowed time for picking up, processing, transferring, inspecting, unloading, loading, repackaging, and delivering package 300 as it travels through the carrier's transportation and logistics network. In this example, 0.0007869 hours (2.83284 seconds) are allowed or allocated to the driver to pick up package 300. As will be appreciated, the total planned time and additional planned time can be stored in association with various package information / data. Using this information / data, the central computing entity 802 can determine and allocate the total planned time and additional planned time for scheduling plans, routes / routes, logical grouping, stops on routes / routes, package 300, etc.

[0333] In one embodiment, package information / data may also include tracking information / data (various "tracking events") corresponding to the location of package 300 within a transportation and logistics network. To determine and reflect the movement of the package, for example, when package 300 is transported through a carrier's transportation and logistics network, a package 300 identifier associated with package 300 may be scanned or otherwise electronically read at various points. As noted, these events may be referred to as tracking events. In one embodiment, the most recent or most recent tracking event (e.g., tracking information / data) may associate package 300 with a specific shipping entity, destination entity, bundle / container, vehicle, employee, location, facility, etc.

[0334] B. User Profile

[0335] In one embodiment, one or more users (e.g., shippers and / or consignees) may register / sign up accounts, subscriptions, programs, and / or similar terms used interchangeably herein. In another embodiment, users may automatically register / sign up accounts, subscriptions, programs, and / or similar terms used interchangeably herein. As previously stated, users may be individuals, families, family members, companies, organizations, entities, departments within an organization, representatives of organizations and / or individuals, etc. In one embodiment, for registration, a user (e.g., a user operating user computing entity 804) may access the webpage, mobile application, application, control panel, browser, or portal of the entity providing notification / message services.

[0336] In one embodiment, as part of the registration / registration process, a user (e.g., a user operating user computing entity 804) may be requested to provide information / data (e.g., including user information / data, biographical information / data, biometric information / data, geographic information / data, entity / entity information / data, payment information / data, etc.) through central computing entity 802 (e.g., via the registration module). The information / data may be manually entered by the user; automatically provided by allowing access to other accounts such as Amazon.com, Facebook, Gmail, Twitter, PayPal, etc.; automatically collected by various computing entities (including automatic entity recognition); combinations of the foregoing methods; and / or other technologies and methods. For example, biographical information / data may include the user's name, such as first name, last name, company name, entity name, organization name, etc. Geographic information / data may also include one or more physical addresses or locations associated with the user (e.g., street address, city, state, postal code, and / or country). Physical addresses or locations may be residential addresses, commercial addresses, geocodes, latitude and longitude points, virtual addresses, etc. In one embodiment, user information / data may include one or more electronic signatures and signature formats for electronically signing documents, versions, etc.

[0337] Users (e.g., shippers or consignees) may also provide central computing entity 802 with one or more physical addresses (e.g., street address, city, state, zip code, and / or country) and / or one or more geocodes associated with the user. For example, Joseph Brown's primary residential address, 105 Main Street, Atlanta, Georgia 30309, USA, may be provided to central computing entity 802. Additionally, one or more secondary residential addresses (e.g., 71 Lanier Islands, Buford, Georgia 30518, USA) may be provided to central computing entity 802 for association with Mr. Brown's account and profile. As will be appreciated, residential addresses may include weekend residences, family member residences visited by the user, etc. Additionally, users (e.g., shippers or consignees) may provide one or more business addresses (e.g., street address, city, state, zip code, and / or country) associated with the user to the central computing entity 802. For example, Mr. Brown might have a primary business address of 1201 West Peachtree Street, Atlanta, Georgia 30309, USA. One or more secondary business addresses may also be provided to the central computing entity 802, such as 101 South Tryon Street, Charlotte, North Carolina 28280, USA; 950 F Street, NW, Washington, DC 20004, USA; and 90 Park Avenue, New York, NY 10016, USA, to be associated with Mr. Brown's account and profile. As will be appreciated, business addresses may include various office locations for a single business, multiple office locations for various businesses, etc. As will be appreciated, users (e.g., shippers or consignees) may provide additional biographical and / or geographic information / data (e.g., geocoding) to suit various needs and environments.

[0338] In one embodiment, in addition to a physical address, a user (e.g., operating user computing entity 804) may also enter, request, or automatically generate and assign a "virtual address." A virtual address may be a combination of alphanumeric characters to identify a user or user profile. The virtual address may be stored in association with the user's profile by the central computing entity 802. For example, Joseph Brown (e.g., operating user computing entity 804) may enter a request for a unique virtual address such as BigBrown8675309 or any other unique virtual address. In another embodiment, the central computing entity 802 may automatically generate and assign a unique virtual address to a user, such as assigning the virtual address 1XR457RS7 to Joseph Brown. Users who do not wish to (a) provide their physical address to a merchant or other third party, (b) print their physical address on a label placed on the outside of package 300, (c) use geocoding points for delivery, (d) etc., may use such a virtual address. For example, this could allow a user (e.g., a shipper) to use an appropriate carrier to ship package 300 using only BigBrown8675309; 1XR457RS7; or 33.7869128, -84.3875602 as the destination address (e.g., a virtual address). When package 300 is retrieved into the carrier's transportation and logistics network, carrier personnel can read (e.g., manually or physically) the virtual address (e.g., BigBrown8675309 or 1XR457RS7) on package 300, locate the appropriate physical delivery address for package 300 based on the recipient's profile (e.g., searching a user profile associated with the virtual address), and accordingly send package 300 along a route / flight (including using an automated service schedule). In some embodiments, package 300 may be routed using only the virtual address. That is, each package 300 is handled by carrier personnel, and the mobile station 105 operated by the carrier personnel (communicating with the central computing entity 802) can cause appropriate processing or routing instructions to be displayed when the actual physical delivery address is masked. However, in other embodiments, once the package 300 with a virtual address is introduced into the carrier's transportation and logistics network, carrier personnel can place a label on the package 300 indicating the physical delivery address (e.g., based on an address associated with a profile and / or automated service schedule).

[0339] In addition to virtual addresses, the central computing entity 802 can also generate and store internal user identifiers associated with a user profile, such as globally unique identifiers (GUIDs) or universally unique identifiers (UUIDs). For example, in one embodiment, the user identifier can be a 128-bit value, which can be displayed as hexadecimal numbers grouped by hyphens. For instance, Joseph Brown's user identifier could be 21EC2020-3AEA-4069-A2DD-08002B30309D. In one embodiment, the user identifier can be used to uniquely identify a user profile. In another embodiment, the user identifier can be used to uniquely identify a given address (e.g., a physical address or a virtual address) associated with a user profile. In such an embodiment, if a user profile is associated with four addresses, the central computing entity 802 can generate and store four user identifiers associated with the user profile (or use one user identifier for all of the user's addresses). User identifiers can also be stored in association with package information / data of package 300 to associate package 300 (and its package information / data) with (a) the correct user (e.g., user profile) and / or (b) the correct address of the user. For example, package information / data for all packages 300 corresponding to Joseph Brown's user profile can be appended with a user identifier created for Joseph Brown. In various embodiments, this method allows packages 300 (and their package information / data) to be linked to the appropriate user profile. Thus, when Joseph Brown accesses his account, he can view all his packages 300 (e.g., those packages 300 whose package information / data is appended with their user identifier (or other identifier)). Similarly, any action of package 300 or user can be passed to the package information / data of package 300 (including executing automated service schedules). In other words, the user identifier appended to the package information / data resolves to the corresponding user profile / account and / or address. Package information / data can have multiple appended user identifiers—one or more user identifiers for the shipper and one or more user identifiers for the consignee.

[0340] In one embodiment, user information / data may include one or more communication formats for communicating with the user as part of his or her notification / message preferences. Communication formats may include text notifications / messages (e.g., SMS, MMS), email notifications / messages, voice notifications / messages, video notifications / messages (e.g., YouTube, Vine), image notifications / messages (e.g., Instagram), social media notifications / messages (e.g., private social media created for the entity's internal use), commercial social media (e.g., Yammer, SocialCast), or public social media (e.g., Facebook, Instagram, Twitter) and / or various other notifications / messages taking various communication formats. In addition to one or more communication formats, the user (e.g., the user computing entity 804) may provide a corresponding electronic destination address for providing the user with information / data associated with the notification / message service (e.g., email address, online handle, phone number, username, etc.). For example, for text notifications / messages, the user may provide one or more cellular phone numbers. For email notifications / messages, the user may provide one or more email addresses (to receive emails or notifications through a specific account). Furthermore, for voice notifications / messages, users can provide one or more cellular or landline phone numbers or other electronic destination addresses, to which audio files can be delivered. Additionally, in one embodiment, a verification operation can be performed on each entered electronic destination address to ensure accuracy. As will be appreciated, various other types of electronic destination addresses can be used to accommodate diverse needs and environments.

[0341] In one embodiment, entities / entity information / data, user information / data, physical address or location information / data, etc., may be received, provided, obtained, detected, allocated, collected, requested, and / or similar terms used interchangeably herein, as part of a registration / registration process. As will be appreciated, entity / entity information / data may be collected for any number of entities or entities to be associated with a user's account, subscription, program, and / or similar terms used interchangeably herein. Entity / entity information / data may include one or more entities or entity identifiers—telephone number, Subscriber Identity Module (SIM) number, Media Access Control (MAC) address, International Mobile Subscriber Identity (IMSI) number, Internet Protocol (IP) address, Mobile Equipment Identifier (MEID), Unit Identifier (e.g., GPS Unit Identifier, UDiD, Mobile Identifier (MIN), IMSI_S (short IMSI), email address, username, GUID, Integrated Circuit Card Identifier (ICCID), Electronic Serial Number (ESN), International Mobile Equipment Identity (IMEI), Wi-Fi ID, RFID tag, etc. Entity / entity information / data may include the entity's supplier, model, specifications, version, components, software specifications and / or versions, the person associated with the entity, etc. Entity / entity information / data can be used to track, monitor, connect to, and communicate with the corresponding entity or entity.

[0342] In one embodiment, using appropriate information / data, the central computing entity 802 can create user profiles for users through a registration / registration process. Therefore, the central computing entity 802 can create, store, and / or access various user profiles and / or information / data associated with the user profiles. In addition to at least the aforementioned information / data, the user profile may also include one or more corresponding usernames, passwords, images, tokens, challenge phrases, reminders, etc. (referred to herein as credentials) for accessing accounts, applications, services, entities, etc. As will be appreciated, various other methods and techniques can be used to adapt to various needs and environments.

[0343] In one embodiment, a user profile identifier may be used to uniquely identify a user profile. In another embodiment, a user profile identifier may be used to uniquely identify a given address associated with a user profile. In such an embodiment, if a user profile is associated with four addresses, the central computing entity 802 may create and store four user profile identifiers associated with the user profile. The user profile identifiers may also be stored in association with package information / data of package 300 to associate package 300 (and its package information / data) with (a) the correct user (e.g., user profile) and / or (b) the correct address of the user. Furthermore, the central computing entity 802 may associate the package information / data of package 300 with the corresponding user profile. This may include appending the package information / data with an appropriate user profile identifier (or other identifier corresponding to the user profile). For example, the package information / data of all packages 300 corresponding to a user profile of Smith Co. Automotive may be appended with a user profile identifier (or other identifier) ​​created for Smith Co. Automotive. In various embodiments, this method allows package 300 (and its package information / data) to be linked to the appropriate user profile. Thus, when a user at Smith Motors accesses their account, he or she can view all their packages 300 (e.g., those packages 300 whose package information / data is accompanied by their user profile identifier (or other identifier)). Similarly, any action selected by the user for package 300 can be passed to the package information / data of package 300.

[0344] C. Pick-up and delivery points

[0345] In one embodiment, a pickup and / or delivery point can be a location from which a package can be picked up and / or delivered to a given serviceable point 5901. These locations can be stored in a user profile and / or as package information / data. See reference. Figure 58 Delivery points can be identified as locations associated with serviceable points, such as those on driveways, porches, garages, yards, and building rooftops. In one embodiment, UAV 100 may use a primary delivery point (e.g., first desired delivery point / location 5902) as the default for all deliveries. Similarly, if the primary delivery point (e.g., first desired delivery point / location 5902) is obstructed, inaccessible, or not preferred for a particular delivery or type of delivery, UAV 100 may use one or more secondary delivery points (e.g., second desired delivery point / location 5904).

[0346] In addition to delivery points, UAV landing points can be, for example, locations where UAV 100 can land for package pickup by a recipient. In one embodiment, a UAV landing point can be used, for example, if a single address is associated with multiple primary / secondary delivery points 5902, 5904 accessed through a single landing location (e.g., a shopping mall delivering to multiple stores or an apartment building delivering to multiple apartments). Therefore, in one example, a UAV landing point can be a location where UAV 100 can land for multiple recipients to pick up packages (e.g., landing at a shopping mall or apartment building). In another embodiment, a landing point can be used when automatic package release is unavailable, for example, due to size or configuration.

[0347] In one embodiment, different types of information / datasets can be used to identify various types of points at serviceable point 5901. For example, in one embodiment, the information / data associated with serviceable point 5901 may include primary / secondary delivery point 5902, 5904 information / data and / or landing point information / data. As will be appreciated, various techniques and methods can be used to collect or determine such information / data associated with different points. For example, in one embodiment, whenever UAV 100 visits primary / secondary delivery points 5902, 5904 associated with serviceable point 5901, the geographic coordinates of the primary / secondary delivery points are collected or determined for the primary / secondary delivery points. The term primary / secondary delivery point geographic coordinates can refer to, for example, information / data that may include, longitude and latitude coordinates, geocoding, altitude, route, speed, distance, UTC, date information, etc. For example, this information / data can be collected via UAV computing entity 808 (with or without the assistance of a driver of UAV 100). Similar information / data can be collected from physical access by carrier personnel to, for example, serviceable point 5901.

[0348] In one embodiment, the UAV computing entity 808 is operably provided with the function of maintaining and processing location information / data (e.g., latitude and longitude information / data) for locations, such as delivering or picking up packages at the location. Therefore, in one embodiment, the UAV computing entity 808 is adapted to collect geographic coordinate samples (e.g., geocoding, latitude and longitude points, GPS readings, etc.) each time a package lands, is delivered, or is picked up at the serviceable point 5901 over a period of time. More specifically, the UAV computing entity 808 can be configured to collect geographic coordinate samples continuously or upon determination that one or more configurable triggering events have occurred. Such configurable triggering events may include, but are not limited to: landing events, obstacle detection events, package release events, failure events, scan or other read events, communication or acknowledgment events, notification events, delivery events, etc. Therefore, for each delivery point and landing point at the serviceable point 5901, the UAV computing entity 808 can acquire one or more geographic coordinate samples (e.g., GPS readings) in response to various triggering events.

[0349] As shown, in one embodiment, the UAV computing entity 808 is configured to continuously and / or periodically store geographic coordinate samples, regardless of whether a triggering event has occurred. This can be advantageous because geographic coordinates may not always be available at any given time, as GPS signals may be temporarily blocked by nearby obstacles, for example. Therefore, if a triggering event occurs when geographic coordinates are not immediately available, the last known geographic coordinates (or, in some embodiments, the next geographic coordinates) can be used. In such an embodiment, the UAV computing entity 808 can store information / data regarding the time of the geographic coordinate samples and the time of the associated triggering events, allowing geographic information / data database providers to use this information / data to determine the accuracy of the geographic coordinate samples.

[0350] Geographic coordinate samples can be provided to a geographic information / data database. After an appropriate number of geographic coordinate samples are associated with primary / secondary delivery points, the geographic information / data database processes the sample geographic coordinates and creates or updates the primary / secondary delivery point geographic coordinates of serviceable point 5901. For example, the geographic information / data database can be configured to require two, three, and / or more consistent sample geographic coordinates associated with primary / secondary delivery points 5902 and 5904 before creating or updating the primary / secondary delivery point geographic coordinates of serviceable point 5901.

[0351] In various embodiments, it is necessary to store and access information / datasets for points for route / path determination and optimization. In various embodiments, information / data for primary / secondary delivery points 5902, 5904 may be stored in various ways—including as part of user profiles, package information / data, and / or the profile of serviceable point 5901. For example, the serviceable point 5901 object (e.g., a data structure) can be used to store (a) the address of the serviceable point 5901, (b) the latitude and longitude of the primary / secondary delivery points 5902 and 5904 associated with the serviceable point 5901 (e.g., geographic coordinates of the primary / secondary delivery points), (c) the latitude and longitude types of the primary / secondary delivery points 5902 and 5904 associated with the serviceable point 5901 (e.g., latitude and longitude of the primary / secondary delivery points 5902 and 5904 or the latitude and longitude of the UAV landing point), (d) the latitude and longitude of the street network connection point 400 associated with the serviceable point 5901 (e.g., geographic coordinates of the street network connection point), (e) obstacles at the serviceable point 5901, and (f) the delivery history at the serviceable point 5901, etc.

[0352] D. Group-based loading and takeoff operations

[0353] In one embodiment, the central computing entity 802 can create / generate scheduling plans for executing pickup and / or delivery from the UAV computing entity 808 to one or more serviceable points 5901 at pickup and / or delivery points. Scheduling plans are well-known and used daily by various carriers. Generally, a scheduling plan is a group of routes / routes scheduled together with its associated delivery and pickup tasks. Scheduling plans can also indicate how each primary parcel delivery vehicle 10 should be loaded and / or how each route / routes should be executed. Figure 51 , 5253 includes various regions, routes / routes, service points 5901 associated with regions (e.g., geographic areas) or routes / routes, and pickup and delivery assignments for service points 5901. Routes / routes are typically one or more address ranges of service points 5901, with associated service levels assigned to a single service provider (e.g., a carrier delivery person). Each route / route typically includes a track, which is a predefined path used to perform one or more deliveries. The delivery order list is then a list of address ranges, addresses, and / or packages 300 for service points 5901 that follows the route / route access to perform the assigned pickup and / or delivery tracks for service points 5901. Through appropriate interfaces, scheduling plans can be compared with alternative scheduling plans for load balancing and various scheduling plans can be adjusted for a given geographic area, service center, route / routes, etc. U.S. Patent No. 7,624,024, filed April 18, 2005, entitled "System and Method for Dynamically Updating Scheduling Plans," provides a general description of scheduling plans and how to generate and update such plans. This may include dynamically updating scheduling plans to add, remove, or update pick-up and / or delivery for serviceable point 5901. U.S. Patent No. 7,624,024 is incorporated herein by reference in its entirety.

[0354] Therefore, packages can be easily accessed for loading into UAV 100 based on the delivery order list, and a loading / storage location can be assigned to each package in the main package delivery vehicle 10. In one embodiment, each loading / storage location can be associated with a unique loading / storage location. For example, each package can be assigned a serial number between 0001 and 9999 (a number within a sequence range) based on its loading / storage location. In another example, grid locations A1-Z99 can be assigned to each package. As will be appreciated, various other methods and techniques can be used to adapt to various needs and environments.

[0355] In one embodiment, loading / storage locations may be stored in association with corresponding package information / data. Loading / storage locations may be provided via an interface, printed on pre-loading labels to aid in loading vehicles, and / or implemented through various other technologies and methods. In one embodiment, loading / storage locations (e.g., 0001-0050 or A1-A30) may be logical groups. Logical groups may include multiple packages to be delivered within a planned timeframe (e.g., estimated time periods / frames relative to each other, such as 15 minutes, 1 hour, 2 hours, 4 hours, days, etc.). For example, logical groups may be based on routes / lines, route / line portions, neighborhood names, postal codes, postal code +4, geographic regions, longitude and latitude ranges, geocodes, geographic descriptors, confidence areas, geofences, etc. As will be appreciated, in one embodiment, each route / line may include one or more logical groups and / or logical group identifiers. Each logical group may correspond to a specific planned time (e.g., an estimated pick-up / delivery time or window). For example, a logical group may be associated with a planned time for delivering all packages within the logical group: 15 minutes, 30 minutes, 1 hour, 2 hours, etc. An estimated pick-up / delivery window can indicate the estimated timeframe for delivering all packages in a logical group. For example, if the planned time for a logical group is 1 hour, this could indicate that package 300 in the logical group will be delivered within the next hour from that point. In other words, the estimated pick-up / delivery window or time can be used to indicate when or within what time frame the corresponding package will be delivered. If the current time is 1:00 PM Eastern Time (EST) and the planned time is 1 hour, the estimated pick-up / delivery window for all packages would be from 1:00 PM EST to 2:00 PM EST. Logical groups can also be stored in association with package information / data. In another embodiment, a specific information / data field or portion of an information / data field in the package information / data may have been designated as a logical group identifier. For example, a logical group identifier could be a portion of a freight identifier, all or part of a postal code field, loading / storage location, route / flight path, portion of a route / flight path, all or part of a serial number, a geographic descriptor, etc. By using such logical groups, the grouped takeoff of UAV 100 can be coordinated within a specific planned time and / or pick-up / delivery window.

[0356] In one embodiment, various computing entities (e.g., delivery vehicle computing entity 810, central computing entity 802, mobile carrier computing entity 806, etc.) can determine or receive input indicating that a package is about to be delivered, a package is being delivered, or a package has just been delivered. Figure 50(Box 4700). For example, in one embodiment, the mobile carrier computing entity 806 is configured (e.g., via a user interface) to receive input indicating various service dynamics (e.g., activities or events related to delivery or transportation). For example, in various embodiments, the user interface is configured to allow the driver to indicate the following service dynamics: (a) a delivery stop has begun (e.g., by pressing a button indicating that the driver has arrived at the delivery point / location and started the delivery process, scanning or inquiring about a package), (b) a delivery stop has ended (e.g., by pressing a button indicating that the driver has completed the delivery and is now leaving the delivery location), (c) a specific bill of lading and its associated goods or packages have been picked up or delivered (e.g., by entering or scanning a tracking number or code, or otherwise identifying one or more bills of lading associated with the goods or packages that have been picked up or delivered), (d) the number of units picked up or delivered at the station (e.g., by manually entering a value), (e) the weight of the packages or goods picked up or delivered at the station (e.g., by manually entering a value), (f) a lunch or rest period has begun or ended (e.g., by manually entering a value). For example, (g) a specific delay encountered by the driver has begun or ended (e.g., by entering a code or otherwise identifying the type of delay the driver has encountered (e.g., waiting for goods, traffic jam, refueling the vehicle, waiting on the train tracks, waiting in a safe area, waiting for a bill of lading), and pressing a button indicating that the identified delay has begun or ended), (h) the driver has started a workday and is at work (e.g., at a transport hub and before starting the delivery vehicle calculation entity 810), (i) the driver has finished a workday and is off duty, (j) the driver and vehicle have entered a specific area (e.g., property of a transport hub, designated delivery area or other work area) and / or (k) the driver and vehicle have left a specific area (e.g., property of a transport hub, designated delivery area or other work area).

[0357] In one embodiment, in response to receiving input indicating an impending or already occurred delivery, the mobile carrier computing entity 806 may capture service information / data and / or package information / data in a computer-readable format. Figure 50 (Box 4700). Upon receiving input of capture service information / data and / or package information / data, the appropriate computational entity can determine whether the package information / data is part of the current logical group ( Figure 50(4702). For the first delivery of the day (or other time period, such as after a shift or break), the appropriate computing entity will determine that the package is not part of the current logical group because it is the first logical group delivered on the day or time period / frame (e.g., the current logical group value is empty until it is set by the first delivery of the day or time period). Once the current logical group value is set for the day (or time period), the appropriate computing entity can store the indicator of the current logical group based on the last package delivered. Accordingly, whenever the mobile carrier computing entity 806 (or other appropriate computing entity) records that the stop has been completed (e.g., the package has been delivered), the mobile carrier computing entity 806 can store the logical group of that package (e.g., the most recently delivered package) as the current logical group. For subsequent packages, the appropriate computing entity (e.g., delivery vehicle computing entity 810, central computing entity 802, mobile carrier computing entity 806, etc.) can compare the logical group of the package to be delivered or already delivered with the logical group indicated as the current logical group. To this end, appropriate computational entities identify the current logical grouping and the logical grouping of packages that are to be delivered or have already been delivered.

[0358] In response to determining that a package is part of the current logical grouping, the appropriate computing entity does not take any action. Instead, the appropriate computing entity (e.g., delivery vehicle computing entity 810, central computing entity 802, mobile carrier computing entity 806, etc.) waits for input indicating whether a different package will be delivered or has already been delivered (e.g., the process returns to...). Figure 50 (Frame 4700).

[0359] In response to determining that the package is not part of the current logical grouping, in one embodiment, the mobile carrier computing entity 806 may present a customized interactive interface to carrier personnel. Figure 50 (Blocks 4704, 4706, and 4708). In one embodiment, a customized interactive interface can provide carrier personnel with the ability to confirm whether a package is part of a new logical packet. In response to input received via the customized interactive interface indicating that the package is not part of a new logical packet, an appropriate computing entity (e.g., delivery vehicle computing entity 810, central computing entity 802, mobile carrier computing entity 806, etc.) can automatically start a timer for a configurable time period / frame (e.g., 30 seconds, 2 minutes, 5 minutes, 10 minutes, etc.) to bypass [the restrictions]. Figure 50 The operations in boxes 4700-4708. An automatic timer provides a mechanism to limit the burden on carrier personnel by repeating requests (e.g., for each delivered package) to confirm logical groups (e.g., for each package delivered within a short period). Once the time period / frame ends ( Figure 50(Box 4712), the process can then return to Figure 50 Box 4700. The use of automatic timers also reduces processing by not checking each package used for picking or delivery, but allows processing elements to be used for other processing and / or tasks.

[0360] In response to an input received via a customized interactive interface indicating that the package is part of a new logical group, the appropriate computing entity (e.g., delivery vehicle computing entity 810, central computing entity 802, mobile carrier computing entity 806, etc.) can automatically initiate the loading of package 300 for the new logical group via one or more UAVs 100 for takeoff and delivery. Figure 50 (Frame 4708).

[0361] In embodiments using timers, if a package is delivered during the timer's time period / frame, a next delivery from a logical group outside the time period / frame will be detected at box 4700 because the corresponding operation has been bypassed, and therefore the current logical group indication will not be updated. Therefore, if a package is delivered during the timer's time period / frame, other packages in the logical group will be detected to generate and send corresponding notifications / messages.

[0362] E. Geofencing-based loading and takeoff operations

[0363] In one embodiment, a suitable computing entity can identify or define one or more geofences, such as geofences defining the area around a geographic region. A geofence can be defined to surround a defined geographic region, such as a surrounding country, region, state, county, city, town, interstate highway, road, street, avenue, toll road, zip code, area code, mode of transport, exit and entrance ramps, delivery routes, route / flight patterns, community, shopping mall, off-road area (e.g., an area without paved roads), private land area, parking lot (e.g., in a shopping mall or other location), driveway, etc. A geofence can be defined, for example, by latitude and longitude coordinates associated with various points along the perimeter of the geographic region. Alternatively, a geofence can be defined based on the latitude and longitude coordinates of the center of the geographic region and a radius. A geofence may be as large as (or larger than) an entire country, region, state, county, city, or town. The geographic region, and therefore the geofence, can be of any shape, including but not limited to circular, square, rectangular, irregular shapes, etc. Moreover, geofence areas do not need to have the same shape or size. Therefore, any combination of shape and size can be used according to embodiments of the invention. Similarly, geofences can overlap or be entirely located within another geofence.

[0364] In one embodiment, once at least one geofence is defined, the coordinates (or a similar method for defining the geofence area) and the corresponding geofence identifier can be stored in a map / geographic information / data database accessible to various computing entities. Therefore, when the primary package delivery vehicle 10 and / or UAV 100 enters and leaves one or more defined geofences, appropriate computing entities can monitor the location of the primary package delivery vehicle 10 and / or UAV 100 and trigger / initiate certain events based on the location.

[0365] To facilitate easy access to packages for geofence-based loading into the UAV 100, each package 300 and / or package carrier 200 may be assigned a geofence identifier (indicating the geofence within which delivery should take place) and stored in the primary package delivery vehicle 10, near other packages associated with the same geofence identifier. In one embodiment, each geofence may be associated with a scheduled time for delivery of all packages within that geofence: 15 minutes, 30 minutes, 1 hour, 2 hours, etc. An estimated pick-up / delivery window may indicate the estimated amount of time required to deliver all packages within a geofence. For example, if the scheduled time for a geofence is 1 hour, this might indicate that once a package enters the geofence, the package associated with that geofence will be delivered within the next hour. That is, the estimated pick-up / delivery window or time can be used to indicate when or within what time frame the corresponding package will be delivered. If the current time is 1:00 PM Eastern Time (EST) and the scheduled time is 1 hour, the estimated pick-up / delivery window for all packages would be from 1:00 PM EST to 2:00 PM EST. The geofence identifier may also be stored in association with package information / data. In another embodiment, a specific information / data field or a portion of an information / data field in the package information / data may have been designated as a geofence identifier. For example, a geofence identifier may be a portion of a freight identifier, all or part of a postal code field, loading / storage location, route / flight path, portion of a route / flight path, all or part of a serial number, a geographic descriptor, etc. By using such a geofence, the group loading and takeoff of UAV 100s can be coordinated within a specific planned time and / or pick-up / delivery window.

[0366] In one embodiment, the location of the primary package delivery vehicle 10 and / or UAV 100 can be monitored when one or more geofenced areas (e.g., geofences) are defined. Typically, the location of the primary package delivery vehicle 10 and / or UAV 100 can be monitored by any of various computing entities, including delivery vehicle computing entity 810, UAV computing entity 808, mobile carrier computing entity 806, central computing entity 802, etc. For example, as described above, the location at a specific time can be determined by means of location determination elements / components. By using the location of the primary package delivery vehicle 10 and / or UAV 100, appropriate computing entities can determine, for example, when the primary package delivery vehicle 10 and / or UAV 100 enters the defined geofence.

[0367] In one embodiment, in response to (e.g., after) determining that the primary parcel delivery vehicle 10 and / or UAV 100 has entered a defined geofenced area, an appropriate computing entity can initiate the pickup / delivery of the parcel associated with the geofence identifier of the geofence entered. That is, the corresponding computing entity can identify all parcels in the scheduling plan associated with the geofence identifier for loading and takeoff by UAV 100. Specifically, once vehicle 10 and / or UAV 100 has entered the defined geofenced area, UAV 100 can be dispatched from vehicle 10 to deliver parcel 300 to a delivery / pickup point / location located within the geofenced area.

[0368] In one embodiment, after the primary package delivery vehicle 10 and / or UAV 100 has entered the geofenced area, the location of the primary package delivery vehicle 10 and / or UAV 100 can continue to be monitored by any of various computing entities. By using the location of the primary package delivery vehicle 10 and / or UAV 100, the computing entities can determine, for example, when the primary package delivery vehicle 10 and / or UAV 100 leaves the defined geofenced area. As described, this can include using various location determination elements / components. In another embodiment, in response to (e.g., after) determining that the primary package delivery vehicle 10 and / or UAV 100 has exited the defined geofenced area, the appropriate computing entity can stop delivering packages to the exited geofence (e.g., based on a geofence identifier) ​​and / or provide notifications / messages to the mobile carrier computing entity 806 and / or the central computing entity 802 regarding the status of each package to be delivered using UAV 100 within the geofence.

[0369] F. Loading and takeoff operations based on route / flight path

[0370] In embodiments, in conjunction with or independently of the above-described logical group-based and geofence-based loading and takeoff methods, UAV 100 can be loaded into and take off from vehicle 10 according to a route / line (e.g., track) based scheduling plan or a predetermined / configurable path for performing one or more deliveries / pickups. As mentioned above, each route / line typically includes a track, which is a predefined path for performing one or more pickups and / or deliveries. The delivery order list is a list of address ranges, addresses, and / or packages 300 for service point 5901 that follow the track to perform specified pickups and / or deliveries for service point 5901. Through appropriate interfaces, scheduling plans can be compared with alternative scheduling plans for load balancing and various scheduling plans can be adjusted for a given geographic area, service center, route / line, etc. In such embodiments, takeoff can be triggered based on completion time, location, pickup and / or delivery, position in the track, etc.

[0371] Furthermore, in such embodiments, messages / notifications can be provided to the user computing entity 804 based on the progress of the vehicle 10 and / or UAV 100 along a predetermined / configurable route / flight. The message / notification criteria can be based on the estimated time of the carrier's arrival at the service point 5901. For example, the shipper / consignee may seek to receive a message when the vehicle 10 and / or UAV 100 is approximately 1 hour, 30 minutes, 15 minutes, and / or 5 minutes away. In this case, the central computing entity (and / or user computing entity 804) can identify the number of stops required before reaching the service point 5901 for a particular shipper / consignee and apply a predetermined / configurable stop time estimate to calculate the estimated time of arrival at the shipper / consignee's service point 5901 (e.g., number of stops * standard stop duration). In some embodiments, the estimate may also include the estimated travel time between remaining stops (e.g., ETA calculated by navigation software, distance of the expected route * average speed, etc.). In other embodiments, the central computing entity 802 may use historical information / data regarding service time and / or travel time between stops to arrive at the user's serviceable point at the estimated arrival time. This process may be repeated, with messages sent, when the vehicle 10 or UAV 100 is 30 minutes, 15 minutes, and / or 5 minutes away, depending on the user's preferences in the corresponding user profile. The central computing entity 802 (and / or the user computing entity 804) may also send an arrival message to the shipper / consignee when the vehicle 10 and / or UAV 100 approaches and / or arrives at the shipper / consignee's serviceable point 5901. Individual messages may be sent via the same protocol or under different protocols, depending on the user and / or carrier's preferences (e.g., via countdown messages in text). As will be appreciated, various other methods and techniques can be used to adapt to various needs and environments.

[0372] G. Pre-flight condition operations

[0373] Reference Figure 54 This schematically illustrates one embodiment of the operation used to determine whether package 300 is suitable for delivery via UAV 100. For example, at intermediate position 601 ( Figure 32Before attaching the package carrier 200 to the package 300, the central computing entity 802 or another suitable computing entity may determine whether conditions are suitable for delivery of the package 300 via UAV. In a first step 5402, the central computing entity 802 detects wind speed associated with a predetermined / configurable area. In embodiments, the predetermined / configurable area includes a geographic region where the package 300 can be delivered and / or picked up via UAV 100, and may include one or more geofenced areas. The central computing entity 802 may detect wind speed conditions, for example, by accessing weather forecasts from the Internet via network 800 (e.g., wind speed at the current time and / or the expected delivery time). Alternatively, the vehicle 10 may be equipped with one or more wind speed detection devices, such as an anemometer communicatively coupled to the associated delivery vehicle computing entity 810, and the central computing entity 802 may receive the detected wind speed conditions for the predetermined / configurable area from the delivery vehicle computing entity 810 of the vehicle 10.

[0374] In the second step 5404, the central computing entity 802 determines whether the wind speed is below a predetermined / settable wind speed threshold. If the detected wind speed condition is not below the predetermined / settable wind speed threshold, the central computing entity 802 proceeds to step 5412 and provides instructions to prepare package 300 for routine delivery (e.g., without using UAV 100) within intermediate location 601. In one embodiment, the predetermined / settable wind speed threshold may be 30 miles per hour (mph). In other embodiments, the predetermined / settable wind speed threshold may be 25 mph. In still other embodiments, the predetermined / settable wind speed threshold may be 15 mph.

[0375] If, in step 5404, the detected wind speed is lower than a predetermined / settable wind speed threshold, then the central computing entity 802 proceeds to step 5406 and detects precipitation conditions for a predetermined / settable area. In an embodiment, the central computing entity 802 can detect precipitation conditions within a predetermined / settable area. For example, the central computing entity 802 can detect current and predicted precipitation conditions within the predetermined / settable area, for instance, by accessing weather forecasts from the Internet via network 800.

[0376] Then, the central computing entity 802 proceeds to step 5408 and determines whether the precipitation conditions within the predetermined / configurable area are below a predetermined / configurable precipitation threshold. If the detected precipitation conditions are not below the predetermined / configurable precipitation threshold, the central computing entity 802 proceeds to step 5412 and provides instructions to prepare package 300 for routine delivery within intermediate location 610. If the detected precipitation conditions are below the predetermined / configurable precipitation threshold, the central computing entity 802 proceeds to step 5410 and provides instructions to prepare package 300 for delivery via UAV 100 within intermediate location. The predetermined / configurable precipitation threshold may be based on a percentage probability of precipitation within the predetermined / configurable area (e.g., a percentage probability of precipitation within the predetermined / configurable area on a specific date), or the predetermined / configurable precipitation threshold may include precipitation events (e.g., rain, sleet, snow, etc.) detected within a predetermined / configurable distance of the predetermined / configurable area. For example, a predetermined / settable precipitation threshold may be a prediction indicating a 10% probability of precipitation within a predetermined / settable area. In other embodiments, a predetermined / settable precipitation threshold may be a prediction indicating a 20% probability of precipitation within a predetermined / settable area. In other embodiments, a predetermined / settable precipitation threshold may include an indication of precipitation events detected within 20 miles of a predetermined / settable area. In other embodiments, a predetermined / settable precipitation threshold may include an indication of precipitation events detected within 40 miles of a predetermined / settable area.

[0377] Therefore, the central computing entity 802 can provide instructions based on the above and / or various other weather / environmental conditions to prepare package 300 within intermediate location 601 for regular delivery or delivery via UAV 100. As can be understood, operating UAV 100 under adverse weather / environmental conditions can be difficult, such as in strong winds, precipitation, and / or low or high temperatures. Operating UAV 100 under such conditions may increase the chance of unsuccessful delivery of package 300 and may result in damage to package 300 and / or UAV 100, which typically reduces user satisfaction and may increase operating costs. Therefore, by providing instructions to prepare package 300 for conventional delivery based on the detection of adverse weather / environmental conditions, the central computing entity 802 can help reduce operating costs and ensure successful delivery of package 300.

[0378] H. Wrapping and Joining Operation

[0379] Common Reference Figure 32 and Figure 55The diagram schematically illustrates a perspective view of intermediate position 601 and an embodiment of the operation for associating package 300 with package carrier 200. In the first step 5502, package identification unit 632 scans / reads / receives package 300, and package identification unit 632 can read the package identifier of package 300. In the second step 5504, package identification unit 632 can send the package identifier to central computing entity 802. In the third step 5506, when robot 612 mounts package carrier 200 onto package carrier fixture 622, package carrier identification unit 613 scans package carrier 200 positioned on robot 612. In the fourth step 5508, package carrier identification unit 613 transmits the scanned / read / received package carrier 200 to central computing entity 802. In the fifth step 5508, central computing entity 802 associates the scanned / read / received package identifier with the scanned / read / received package carrier identifier. As can be understood, the package carrier 200 and the associated package 300 can be connected to each other at an engagement clamping mechanism 634, which is spaced apart from the package identification unit 632 and the package carrier identification unit 613 of the robot 612. Therefore, when the package carrier identifier is associated with the package identifier, the central computing entity 802 can consider and accommodate the package carrier 200 located between the package carrier identification unit 613 and the engagement clamping mechanism 634, and the package 300 located between the package identification unit 632 and the engagement clamping mechanism 634.

[0380] By associating package 300 with package carrier 200 attached to package 300, central computing entity 802 can track and monitor the location and progress of package 300 and associated package carrier 200 throughout the delivery process.

[0381] Reference will now be made to a method for supplying a parcel carrier 200 within a vehicle 10 to a UAV 100, and to operations for delivering and picking up parcels 300 via the UAV 100.

[0382] I. Remote User Authorization and Takeoff Operation

[0383] Reference Figure 56This schematically illustrates one embodiment of the operation for loading the package carrier 200 into the UAV 100. As described above, the delivery vehicle computing entity 810 is communicatively coupled to the central computing entity 802 and may also be communicatively coupled to the robot processor 522 and the conveyor controller 460 of the vehicle 10. In a first step 5601, the delivery vehicle computing entity 810 determines whether the supply position sensor 450a indicates that the UAV 100 is positioned within the supply area 408. If the delivery vehicle computing entity 810 does not receive a signal from the supply position sensor 450a indicating that the UAV 100 is positioned within the supply area 408, the delivery vehicle computing entity 810 remains at step 5602. If the delivery vehicle computing entity 810 receives a signal from the supply position sensor 450a indicating that the UAV 100 is positioned within the supply area 408, the delivery vehicle computing entity 810 proceeds to step 5604 and commands the robot 500 to retrieve the package carrier 200 from the tray 30 within the vehicle 10.

[0384] In an optional second step 5602, the delivery vehicle computing entity 810 determines the package carrier 200 for delivery. As described above, the package carrier 200 (and associated package 300) can be dispatched from the vehicle 10 based on logical grouping and / or the location of the vehicle 10, for example, when the vehicle 10 is located within a geofenced area. Upon selecting the package carrier 200 for delivery, the delivery vehicle computing entity 801 proceeds to step 5603. In step 5603, the delivery vehicle computing entity 810 determines whether an acknowledgment has been received from the user computing entity 804, indicating that the sender / recipient wishes to perform delivery / pickup via the UAV 100. For example, in some embodiments, the delivery vehicle computing entity 804 may send a notification to the user computing entity 804 before dispatching the package carrier 200 (and associated package 300 at the time of delivery) from the vehicle 10. The notification may invite the sender / receiver to provide input through user computing entity 804, confirming that the sender / receiver wishes to perform delivery / pickup via UAV. If delivery vehicle computing entity 810 does not receive confirmation from user computing entity 808, delivery vehicle computing entity 810 may return to step 5602 and determine another parcel carrier 200 for delivery. In this way, delivery vehicle computing entity 810 can receive confirmation from the sender / receiver that the sender / receiver wishes to perform delivery / pickup via UAV 100 before dispatching UAV 100 from vehicle 10. If delivery vehicle computing entity 810 receives confirmation from user computing entity 808, delivery vehicle computing entity 810 proceeds to step 5604 and commands the robot to retrieve parcel carrier 200 from pallet 30.

[0385] Then, the delivery vehicle computing entity 810 proceeds to step 5606 and commands the robot 500 to install the package carrier 200 onto the UAV rack 110. While installing the package carrier 200 onto the UAV rack 110, the delivery vehicle computing entity 810 may additionally provide information / data to the UAV computing entity 804, indicating the destination of the package carrier 200 (e.g., the coordinates of the delivery / pickup point / location to which the package carrier 200 will be transported).

[0386] Once the package carrier 200 is installed on the UAV rack 110, the delivery vehicle computing entity 810 proceeds to step 5608 and moves the UAV to the takeoff end 402. Once moved to the takeoff end 402, the propulsion component 102 of the UAV 100 can be engaged, and the UAV 100 can leave the vehicle 10.

[0387] The above can be executed. Figure 56 The operation can be performed to prepare UAV 100 for two types of delivery, in which the package carrier 200 installed to UAV 100 is coupled to package 300. It can also be performed to prepare UAV 100 for pickup, in which the package carrier 200 installed to UAV 100 is not coupled to package 300, but is configured to pick up package 300 from a serviceable point.

[0388] J. Navigation for UAVs used for pickup / delivery

[0389] In various embodiments, UAV 100 can operate autonomously. In autonomous embodiments, UAV 100 can navigate between vehicle 10 and service point 5901 along a predetermined / configurable flight route / path. The predetermined / configurable flight route can include a straight flight path between vehicle 10 and service point 5901. UAV 100 can travel in a straight line between vehicle 10 and service point 5901, and in response to receiving indications of objects or obstacles in the flight path from flight guidance sensor 166, UAV 100 can deviate from the predetermined / configurable flight path. In some embodiments, the predetermined / configurable flight path can include one or more waypoints (e.g., geocoding or geographic coordinates), or one or more geographic locations that UAV 100 will travel to between vehicle 10 and service point 5901. Waypoints can be determined to provide an efficient flight path between vehicle 10 and service point 5901 (e.g., minimizing flight time), and waypoints are determined based on known obstacles (e.g., buildings, power lines, etc.) that would obstruct a direct flight path between vehicle 10 and service point 5901.

[0390] Alternatively, in some embodiments, the flight and operation of the UAV 100 can be controlled remotely and manually, for example through mobile carrier computing entity 806, central computing entity 802, and / or delivery vehicle computing entity 810. As will be appreciated, a variety of other methods and techniques can be used to adapt to various needs and environments.

[0391] Reference Figure 57 This schematically illustrates one embodiment of the operation of UAV 100 after it leaves vehicle 10. In a first step 5702, UAV 100 navigates from takeoff end 402 of vehicle 10 to a desired serviceable point 5901. In this embodiment, UAV 100 navigates to the desired serviceable point based on information / data associated with package carrier 200.

[0392] In some embodiments, the delivery vehicle computing entity 810 and / or the UAV computing entity 808 may provide the user computing entity 804 with a notification / message indicating that the UAV 100 has left the vehicle 10. The UAV computing entity 808 may also provide the user computing entity 804 with an indication of the estimated time of arrival of the UAV 100 at the available service point, based on the location of the UAV 100 relative to the available service point. Furthermore, in some embodiments, the UAV computing entity 808 may transmit live feedback / streaming of the route / flight path of the UAV 100 (e.g., which may be captured by one or more cameras 168) for display on the user computing entity 804.

[0393] In step 5704, if the package carrier 200 is scheduled for pickup, the UAV computing entity 808 proceeds to step 5706 and initiates the pickup sequence. If the package carrier 200 is not scheduled for pickup, the UAV computing entity 808 proceeds to step 5708 and initiates the delivery sequence. The operational steps of the delivery sequence (e.g., step 5708) and the pickup sequence (e.g., step 5706) are described in more detail herein.

[0394] Reference Figure 58The diagram schematically illustrates a front view of UAV 100 at a serviceable point 5901. In an embodiment, a recipient or user can request delivery to or pickup of package 300 at serviceable point 5901, which may include residential, business, or other locations where the recipient wishes package 300 to be delivered. The sender / recipient can further request delivery of package 300 to one or more preferred delivery / pickup points / locations at serviceable point 5901. As an example, the recipient can request delivery of the package to a first desired delivery point / location 5902 or an alternative second desired delivery point / location 5904 at serviceable point 5901, wherein the first desired delivery point / location 5902 and the second desired delivery point / location 5904 are spaced apart. Figure 58 In the illustrated embodiment, the first desired delivery point / location 5902 is located in the front area of ​​the serviceable point 5901 (e.g., in the front yard, etc.), while the second desired delivery point / location 5904 is located in the rear area of ​​the serviceable point 5901 (e.g., in the backyard, etc.). Alternatively, the first desired delivery point / location 5902 and the second desired delivery point / location 5904 can be located at any location of the serviceable point 5901 suitable for receiving the package 300, such as the top of a structure, a porch, a driveway, etc. In some embodiments, the first desired delivery point / location 5902 and / or the second desired delivery point / location 5904 can be located within a portion of the serviceable point 5901 with restricted access. For example, the first desired delivery point / location 5902 and / or the second desired delivery point / location 5904 can be located within the garage 5906 of the serviceable point 5901, wherein the garage 5906 is selectively accessible via a garage door 5908. In an embodiment, the location of the desired delivery point / location at serviceable point 5901 can be associated with a user profile, so that the desired delivery point / location can be reused for subsequent delivery to serviceable point 5901.

[0395] In this embodiment, UAV computing entity 808 can communicate with user computing entity 802, enabling UAV 100 to gain access to garage 5906 (or access garage 5906 via user profile). For example, UAV computing entity 808 can receive a delivery instruction from the recipient via user computing entity 804 and central computing entity 802, indicating that package 300 will be delivered to a restricted access area of ​​service point 5901. Upon receiving a request to deliver the package to the restricted access area of ​​service point 5901, UAV computing entity 804 can receive an access code from the recipient via user computing entity 804 and / or central computing entity 802 (or access the access code via user profile). The access code can provide selective access to the restricted access area of ​​service point 5901 (if valid).

[0396] In one embodiment, upon receiving communication of an access code from UAV computing entity 808 (e.g., stored in a user profile), user computing entity 804 can verify the access code and, if valid, can command garage door 5908 ( Figure 58 The door was opened to allow UAV 100 to enter and deliver package 300 to garage 5906. Figure 58 The access code may include a unique, one-time use or temporary access code that provides access to a restricted access area of ​​service point 5901 once. For example, upon receiving a unique, one-time use access code from UAV computing entity 808, user computing entity 804 may verify the access code and, if valid, command garage door 5908 ( Figure 58 ) Open. In a single-use implementation, user computation entity 804 may not command garage door 5908 upon subsequently receiving the unique single-use access code. Figure 58 Open. By utilizing a unique one-time access code, access can be granted for a specific package delivery without providing data / information to UAV computing entity 808 or any other computing entity that might facilitate general access to the restricted access area of ​​service point 5901.

[0397] Furthermore, in some configurations, the access code may include a unique access code that, when transmitted to the user computing entity 804, causes the user computing entity 804 to partially open the garage door 5908. Figure 58 This allows the UAV100 to navigate to the interior of garage 5906. Figure 58 By partially opening garage door 5908, the access code allows access to garage 5908 for delivery of package 300, without fully opening garage door 5908 and provides unrestricted access to garage 5906. Figure 58 Although user computing entity 804 is described as commanding garage door 5908 to selectively open to allow access to garage 5906, it should be understood that user computing entity 804 may selectively provide access to any suitable restricted access area of ​​service point 5901.

[0398] Alternatively, or in addition to receiving and subsequently providing an access code to obtain access to a restricted area of ​​serviceable point 5901, UAV computing entity 802 may interact directly with the recipient via user computing entity 804 to obtain access to the restricted area of ​​serviceable point 5901. For example, upon arrival at serviceable point 5901, UAV computing entity 802 may establish communication with user computing entity 804 (e.g., a gate or garage door controller, smart home entity, etc.) and may send a request to access the restricted area of ​​serviceable point 5901. The recipient may then provide input to user computing entity 804 that provides access to the restricted area of ​​serviceable point 5901 (e.g., by opening garage door 5908). UAV computing entity 802 may also close the door or garage door in a similar manner. Alternatively, access to the restricted area may be based on a timer (e.g., the door or gate is open for 30 seconds or 1 minute).

[0399] Central computing entity 802 may receive location coordinates (e.g., latitude and longitude) of a first desired delivery point / location 5902 and a second desired delivery point / location 5904 from a recipient via user computing entity 804 (or access these location coordinates via a corresponding user profile). Alternatively, in some embodiments, upon receiving a request from user computing entity 804 for package delivery to a serviceable point 5901, central computing entity 802 may send information / data to user computing entity 804, including markings configured to be printed on a medium. As a specific example, central computing entity 802 may send to the recipient via user computing entity 804 a QR code, barcode, MaxiCode, symbol, etc., configured to be printed on a medium and placed at the first desired delivery point / location 5902 and / or the second desired delivery point / location 5904. Camera 168 of UAV 100 may be configured to read the markings and may utilize the markings to navigate to the first desired delivery point / location 5902 and / or the second desired delivery point / location 5904.

[0400] Similarly, the central computing entity 802 may receive the location coordinates (e.g., latitude and longitude) of the desired pickup point / location from the recipient via the user computing entity 8...

Claims

1. A method for loading packages via drone, comprising: Navigate the drone to a service point, the drone comprising: The drone rack includes: The upper part includes multiple propulsion components that provide lift to the UAV frame; The lower portion, positioned vertically below the upper portion, defines an inner cavity; and A package carrier, selectively coupling to and removable from the drone frame, the package carrier comprising: The engaging housing is at least partially insertable into the lower cavity of the drone frame, thereby securing it to the drone frame; and A package carrying mechanism is coupled to and positioned below the engagement housing, wherein the package carrying mechanism includes a package carrying arm that is movable between an engagement position and a disengagement position, wherein in the engagement position the package carrying arm engages the package and in the disengagement position the package carrying arm is spaced apart from the package; Detect the package at the service point; The package is engaged at the engagement position via the package-carrying arm, thereby loading the package onto the package-carrying device; Move the package carrier toward the drone frame positioned on the drone support mechanism; The connecting member of the drone frame is moved from the extended position to the retracted position, bringing the connecting housing of the packaged carrier into contact with the drone frame; and the connecting member of the drone frame is moved from the retracted position to the extended position, securing the connecting housing to the drone frame. The drone is launched from a shared vehicle, which is used by multiple drones. The width reduction portion and upper portion of the drone frame are formed into a conical or hourglass shape, which is configured to engage a pair of opposing guide rails on the shared vehicle when the drone takes off from and lands on the shared vehicle.

2. The method according to claim 1, further comprising: The package support arm is actuated by an electric motor; as well as The package carrier controller commands the motor to move the package carrier arm between the engaged position and the disengaged position, wherein the package carrier controller is communicatively coupled to the motor.

3. The method according to claim 2, further comprising: When the bottom surface of the package contacts the landing surface is detected by a ground probe, wherein the ground probe is communicatively coupled to the package carrier controller.

4. The method of claim 1, wherein each of the packaged support arms includes an upper portion extending outwardly from the engagement housing and a lower portion extending downwardly from the upper portion.

5. The method of claim 4, wherein each of the package-carrying arms further comprises a plurality of pins extending inwardly from the lower portion of the package-carrying arm toward the package.

6. The method of claim 4, wherein each of the package carrier arms includes a support flange extending inwardly from a lower portion of the package carrier arm, wherein the support flange is configured to extend below the bottom surface of the package.

7. The method of claim 1, wherein the engagement member of the drone frame is a retaining member in the lower part of the drone frame, the retaining member being configured to engage the engagement housing of the package carrier and secure the package carrier in the cavity of the drone frame.

8. The method of claim 7, wherein the retaining member is positioned around the periphery of an opening in the inner cavity of the UAV frame, and The retaining member is capable of being repositioned between the extended position and the retracted position. At the extended position, the retaining member extends inward into the inner cavity, and the method further includes securing the engaging housing of the enclosing support device within the inner cavity via the retaining member. In the retracted position, the retaining member is withdrawn from the cavity, and the method further includes allowing the engaging housing to be removed from the cavity via the retaining member.

9. The method of claim 1, wherein the UAV further includes a ground landing sensor coupled to the UAV frame and positioned outside the maximum envelope.

10. The method of claim 1, wherein the drone further comprises landing gear coupled to a downward-facing surface of the upper portion of the drone frame.

11. The method of claim 1, wherein the drone further comprises a camera positioned on the lower part of the drone frame.

12. A method for retrieving a package from a shared vehicle using a drone, the shared vehicle being used by multiple drones, the method comprising: Navigate the drone to the pickup point of the shared vehicle, the drone comprising: The drone rack includes: The upper part includes multiple propulsion components that provide lift to the UAV frame; The lower portion, positioned vertically below the upper portion, defines an inner cavity; and A package carrier, selectively coupling to and removable from the drone frame, the package carrier comprising: The engaging housing is at least partially insertable into the lower cavity of the drone frame, thereby securing it to the drone frame; and A package carrying mechanism is coupled to and positioned below the engagement housing, wherein the package carrying mechanism includes a package carrying arm that is movable between an engagement position and a disengagement position, wherein in the engagement position the package carrying arm engages the package and in the disengagement position the package carrying arm is spaced apart from the package; Detect the package at the pickup point; The package is engaged at the engagement position via the package carrying arm, so that the package carrying device picks up the package from the shared vehicle; Move the package carrier toward the drone frame positioned on the drone support mechanism; Move the connecting member of the drone frame from the extended position to the retracted position, so that the connecting housing of the packaged carrier contacts the drone frame; and The connecting member of the drone frame is moved from the retracted position to the extended position, and the connecting housing is secured to the drone frame. The width reduction portion and upper portion of the drone frame are formed into a conical or hourglass shape, which is configured to engage a pair of opposing guide rails on the shared vehicle when the drone takes off from and lands on the shared vehicle.

13. A method for delivering a package via drone, comprising: Navigate the drone to the first available service point, the drone comprising: The drone rack includes: The upper part includes multiple propulsion components that provide lift to the UAV frame; The lower portion, positioned vertically below the upper portion, defines an inner cavity; and A package carrier, selectively coupling to and removable from the drone frame, the package carrier comprising: The engaging housing can be inserted at least partially into the inner cavity of the lower part of the drone frame, thereby securing it to the drone frame; A package carrier mechanism is coupled to and positioned below the engagement housing, wherein the package carrier mechanism includes a package carrier arm that is movable between an engagement position and a disengagement position; The package at the first serviceable point is detected, and the package is engaged at the engagement position via the package carrying arm, such that the package carrying mechanism engages and holds the package; the drone is navigated to the second serviceable point, and the drone is separated from the package at the disengagement position via the package carrying arm, such that the package carrying mechanism releases the package; Move the package carrier toward the drone frame positioned on the drone support mechanism; Move the connecting member of the drone frame from the extended position to the retracted position, so that the connecting housing of the packaged carrier contacts the drone frame; and The connecting member of the drone frame is moved from the retracted position to the extended position, and the connecting housing is secured to the drone frame. The drone is launched from a shared vehicle, which is used by multiple drones. The width reduction portion and upper portion of the drone frame are formed into a conical or hourglass shape, which is configured to engage a pair of opposing guide rails on the shared vehicle when the drone takes off from and lands on the shared vehicle.

14. A drone pickup and delivery system comprising using a drone according to any one of claims 1 to 11 and a shared vehicle.

Images