Package Transport by Unmanned Aerial Vehicles

Referring now to Figure 1, a high level view of a system 100 for performing package transport services is generally shown in accordance with an embodiment. The system 100 includes a plurality of unmanned aerial vehicles (UAV(s) 102) and a plurality of package docking device(s) 104, each of which is communicatively coupled to one or more network(s) 108. A UAV(s) 102 refers to an unmanned aircraft whose flight is autonomously controlled through onboard computer systems. In an embodiment, a portion of the flight control may be implemented remotely through interaction with a ground station (not shown). The UAV(s) 102 include physical components and related circuitry configured to pick up, carry, and drop off packages. 

The package docking device(s) 104 refer to structures used in assisting UAVs in implementing corresponding docking functions. A package docking device(s) 104 may be assigned to or otherwise controlled by an end user of the package transport services. A package docking device(s) 104 can be identified by the UAVs based on a unique identifier that is assigned to the package docking device(s) 104 and which identifier is communicatively conveyed to the UAV(s) 102 over a network at the time of a package transfer operation, as will be described further herein. As indicated above, the package docking devices may be permanent or semi-permanent fixed structures or may be portable structures that are lightweight and can be carried by a human.

The network(s) 108 may be any type of known networks including, but not limited to, a wide area network (WAN), a local area network (LAN), a global network (e.g. Internet), a virtual private network (VPN), and an intranet. The network(s) 108 may be implemented using wireless networks or any kind of physical network implementation known in the art, e.g., using cellular, satellite, and/or terrestrial network technologies. The network(s) 108 may also include short rangewireless networks utilizing, e.g., BLUETOOTH.TM. and WI-FI.TM. technologies and protocols. In one embodiment, the UAV(s) 102 communicate with the package docking device(s) 104 over a short-range wireless network, while the UAV(s) 102 communicate with other network entities, such as the package transport services provider, over a long-range network (e.g., satellite or cellular). 

The system 100 also includes a host system computer 106, a personal computer 112, and a mobile device 114, each of which is communicatively coupled to one or more of the network(s) 108. The host system computer 106 may be implemented as one or more high-speed computer processing devices, such as one or more mainframe computers capable of handling a high volume of activities conducted on behalf of end users of the package transport services. The host system computer 106 implements an application 116 to centrally manage the package transport services described herein. The application 116 includes a user interface 118 that is presented to end users via the personal computer 112 and the mobile device 114. The user interface 118 is described further in Figure 6. 

In one embodiment, the host system computer 106 may be implemented by an entity that sells goods to consumers. Alternatively, the host system computer 106 may be implemented by a third-party service provider that provides the package transport services as an intermediary between the seller entity and the consumers. In another embodiment, the host system computer 106 may be implemented by a non-commercial entity, e.g., for situations in which packages (such as food or medical supplies) need to be transferred between locations as part of an emergency condition where first responders are unable to gain access to various roads or locations. For purposes of illustration, the package transport services are described herein with respect to a commerce application. 

The personal computer 112 may be implemented as a general-purpose desktop or laptop computer. An end user consumer may access the user interface 118 of the host system computer 106 via a web browser operating on the personal computer 112. The end user may ordergoods from the host system computer 106, as well as schedule delivery of the goods, as will be described further herein. 

The mobile device 114 refers to a portable, wireless communications device, such as a smart phone, personal digital assistant, or tablet PC. Similar to the personal computer 112, the end user may access the user interface 118 of the host system computer 106 via a web browser operating on the mobile device 114 to ordergoods and schedule deliveries. In an embodiment, the mobile device 114 includes a global positioning system (GPS) that enables a UAV(s) 102 to locate a package docking device(s) 104 associated with the mobile device 114, as will be described further herein. 

A storage device 110 is coupled to the host system computer 106 and may be alternatively coupled to the host system computer 106 via one or more of the network(s) 108. The storage device 110stores a variety of data used by the host system computer 106 in implementing the package transport services described herein. As shown in Figure 1, the storage device 110storesorders generated for end users, as well as transaction records. The transaction records provide information about completed orders. It is understood that the storage device 110 may be implemented using memory contained in the host system computer 106 or may be a separate physical device. The storage device 110 is logically addressable as a consolidated data source across a distributed environment that includes the network(s) 108. 

The host system computer 106 operates as a database server and coordinates access to application data including data stored in the storage device 110. The host system computer 106 may be implemented using one or more servers operating in response to a computer program stored in a storage medium accessible by the server. The host system computer 106 may operate as a network server (e.g., a web server) to communicate with the personal computer 112 and the mobile device 114 and other network entities. 

As indicated above, the package docking device(s) 104 may be a secured structure that is permanently or semi-permanently installed at a fixed location, such as an area of a real estate, an apartment building rooftop, etc., and is described in figure 2. In an alternative embodiment, the package docking device(s) 104 is implemented as a portable device, which is described in Figure 3. Turning now to Figure 2 and Figure 3, perspective views of package docking device A 200 and portable package docking device 300, respectively, will now be described. 

The package docking device A 200 of Figure 2 includes a housing 208, an opening 204 for receiving a package, and a door 206 for securing the package in the housing 208. An upper wall 202, or roof, of the housing 208 may be used as a landing site for the UAV. The package docking device A 200 may be constructed of a durable material, such as metal, and may be mounted or fixed to another permanent structure (e.g., a building or concrete base) to prevent theft or tampering. The door 206 is closed and locked to secure delivered packages, and may be opened by the UAV(s) 102 using a security key. It will be understood that the configuration shown in Figure 2 is not limited thereto. For example, in other configurations, the package docking device A 200 may have various shapes, sizes, and dimensions. Further, an additional panel or structure may be installed near the opening 204 such that the UAV lands on the panel within a close proximity of the opening 204 to facilitate hand off of the package. 

The portable package docking device 300 of Figure 3 is constructed of a lightweight and flexible material to provide ease of portability. The portable package docking device 300 may be implemented as a substantially flat structure with a thickness that is narrow enough to enable the portable package docking device 300 to be rolled up for portability and storage. Dimensions of the portable package docking device 300 may vary based on applications of its use. In one non-limiting embodiment, the length and width of the portable package docking device 300 is sized substantially similar to the length and width of a beach towel. Details of the various components of the package docking device A 200 and portable package docking device 300 are described further in Figure 5. 

Turning now to Figure 4, a UAV 102 (102) will now be described in an embodiment. The UAV 102 includes communication components 404, a control processor 406, and memory 408. The memory 408stores a transaction packet 410, a transaction record 412, and an application 414. The application 414 is executable by the control processor 406 to coordinate the functions of the UAV 102 as described herein. The control processor 406 is communicatively coupled to the circuitry of the UAV 102 to receive operational data from components of the UAV 102, such as data indicating the activation of landing gear or the physical engagement of the landing gear at a package docking device. 

The communication components 404 include an antenna configured to receive communications from the host system computer 106 over one or more of the network(s) 108. The communications may include instructions associated with a package transfer operation. The package transfer operation refers to the pickup and delivery of a package to a target package docking device as defined by GPS coordinates (and vertical scale information that provides altitude data corresponding to the delivery point) and a device identifier of the package docking device(s) 104. The instructions include the GPS coordinates, vertical scale data, and the identifier of the package docking device(s) 104 to which the package will be delivered. The instructions may also include an identification of an order corresponding to the package that differentiates between orders placed for two or more items by the same consumer. In an embodiment, the instructions may further include individual identification of items within an order. For example, a package may contain a partial order due to weight restrictions placed on the UAV, or because an item is not available at the precise time of transport, or because the items are picked up from multiple geographically-dispersed locations for transport. If a package contains a partial order, the UAV may contain instructions that identify those items of the order that are being transported by the UAV. The instructions may also indicate that the partial order reflects `x` of `y` items in an order being delivered. If the package docking system is a secure device, the instructions may also include a security key, as described further herein. 

These instructions are conveyed to the UAV(s) 102 from the host system computer 106 as a transaction packet 410. In addition, the communications enabled by the antenna include communications from the UAV(s) 102 to the host system computer 106. For example, upon completing a package transfer operation, the UAV(s) 102 may send associated information (e.g., transaction recording, time/date stamp, etc.) to the host system computer 106, which is stored in the storage device 110 as a transaction record. Alternatively, the information may be stored as the transaction record 412 in the memory 408 of the UAV 102. 

The communications components 404 also include an antenna configured to send short-range wireless communications to the package docking device(s) 104. In an embodiment, when the UAV 102 reaches its destination defined by the GPS coordinates, it may send a communication to discover the presence of the package docking device(s) 104. Alternatively, the package docking device(s) 104 may be configured to periodically send out signals to enable its discovery. Once the UAV 102 has discovered the presence of a package docking device(s) 104, the UAV 102 requests the device identifier of the discovered device 104. The device identifier received from the package docking device(s) 104 is compared against the device identifier in the transaction packet 410 to ensure that the package is delivered to the correct package docking device. The communications components 404 may further include an adapter configured to translate radio signals from the package docking device(s) 104 to data that is stored in the memory 408 of the UAV 102. 

In an embodiment, the communications components 404 may include WI-FI components that are initiated when no package docking device is discovered, or alternatively, if the device identifier received by the UAV 102 is different than the device identifier in the transaction packet 410. The first scenario may occur if the package docking device has been moved to a new location. The latter scenario may occur if the package docking device has been moved from its location and another package docking device is subsequently placed in that location. The latter scenario may otherwise occur when two package docking devices are located in very close proximity to each other (e.g., within a few feet), such that the GPS coordinates span the physical locations of both package docking devices and the UAV 102 receives the device identifier from the wrong package docking device. In any of these scenarios, the UAV 102 may utilize the WI-FI components to send a signal searching for the package docking device. 

Optionally, the UAV 102 may include a video recording device 402 to record package transfer operations. The video recording device 402 may be configured through prompts from the application 414 to begin recording, e.g., when the application 414 receives an indication that the landing apparatus of the UAV 102 has been triggered. The video recording device 402 may be prompted through the application 414 to discontinue recording, when the application 414 received an indication that the package transfer operation (i.e., successful delivery of the package to the package docking device(s) 104) is complete. The recording may be stored as a transaction record 412 in the memory 408 of the UAV 102. In addition, the recording may be transmitted through the communication components 404 to the package docking device(s) 104 if the package docking device(s) 104 is equipped to receive the recording. The transaction record 412 may include other information including a time/date stamp of the delivery, as well as transaction details (e.g., invoicing information, billing and payment information, etc.). In addition, the transaction record 412 may be supplemented with electronic coupons or advertisements for goods offered by the seller or through affiliates of the seller, if desired. 

Turning now to Figure 5, a package docking device 104 (104,  package docking device A 200, portable package docking device 300) will now be described. The package docking device 104, whether portable or fixed, includes communication component(s) 404, a processor 508, and memory 512. If the package docking device 104 is a portable device, the communications components 404 may include a GPS device that is used by the UAV 102 to track the location of the package docking device 104. Alternatively, a GPS system on mobile device 114 associated with the package docking device 104 may be used to enable the UAV 102 to track the location of the package docking device 104, assuming that the mobile device 114 is in close proximity with the package docking device 104. 

The communication components 404 include an antenna configured to receive communications from the UAV 102 over a short-range network (e.g., BLUETOOTH). For example, the package docking device 104 may receive prompts from the UAV 102 to discover its presence at a GPS location. The package docking device 104 may receive requests for the device identifier 510 of the package docking device 104. Further, upon completing a package transfer operation, the UAV 102 may send associated information (e.g., transaction recording, time/date stamp, etc.) to the package docking device 104, which may be stored in the memory 512 as a transaction record 412. 

The memory 512stores a device identifier 510, a transaction record 412, and an application 414. The application 414 is executable by the processor 508 to coordinate the functions of the package docking device 104 described herein. The device identifier 510 may be a network address of the package docking device 104. 

The package docking device 104 may optionally include a video recording device 402 for recording package transfer operations. The video recording device 402 may be disposed at a location on the package docking device 104 suitable for capturing the hand off of the package to the package docking device 104. 

If the package docking device 104 is a secured device (e.g., the  package docking device A 200 of Figure 2), the package docking device 104 may include a locking system 502 and a security key 506. The locking system 502 may be implemented as an electronic lock (e.g., using electro-magnetics) using the security key 506 as an authentication means to unlock the package docking device 104. The security key 506 may be provided to the host system computer 106 as part of the order process. 

In an embodiment, the package docking device 104 may include a detection sensor 504 that is configured to detect a landing function of the UAV 102. For example, the detection sensor 504 may be a weight sensor that is disposed on the landing panel (e.g., upper wall 202 or roof of package docking device A 200 in Figure 2). The detection of weight may indicate to the package docking device that the UAV 102 has landed, and the subsequent absence of weight may indicate the departure of the UAV 102. This information may be stored in the package docking device 104 as part of the transaction record 412.

As indicated above, the package transport services are managed by the host system computer 106. In an embodiment, an end user of the services may access a website of the host system computer 106 and is presented with a user interface 118 for initiating an order for goods offered by the entity associated with the host system computer 106. A sample user interface screen 600 is shown in Figure 6. An area 602 of the user interface screen 600 is used by the end user to enter order information, and an area 604 of the user interface screen 600 is used by the end user to view the order. 

In placing an order, the user is prompted to enter GPS coordinates606 of the delivery point in which the package is to be delivered. The end user may also enter vertical scale information 608 in the form of the sea level corresponding to the delivery point. In an embodiment, if the order is placed through a mobile device 114, the GPS coordinates of the mobile device 114 may be transmitted to the host system computer 102 and automatically entered in the corresponding fields of area 602. The user further enters a device identifier 510 of the package docking device to which the package will be delivered. The end user then selects an option “Ship to this destination” 610. The user interface screen 600 also includes an option that allows the end user to select a mailing address for the delivery if desired. The review order information 604 provides a summary of the order details including payment and billing information, as well as discounts. The order information 604 may also include an order identifier 612 assigned to the order. Once the order has been placed, the package transport services include providing order details to a designated UAV for implementing a package transfer operation. 

Turning now to Figure 7, a flow diagram of a process 700 for implementing the package transfer operations will now be described in an embodiment. The process described in Figure 7 assumes that the UAV 102 has picked up the package subject to an order placed, e.g., via the user interface screen 600 of Figure 6. 

At block 702, the UAV 102 receives a transaction packet (e.g., packet 410 of Figure 4) for the package transfer operation. The transaction packet includes the GPS coordinates and the device identifier of the package docking device associated with the package transfer request. The transaction packet may be stored in the memory 408 of the UAV 102. 

At block 704, upon arrival at the delivery point as defined by the GPS coordinates and vertical scale information, the application 414 receives a device identifier from a package docking device located at the delivery point and compares the device identifier for the package docking device located at the delivery point with the device identifier stored in the transaction packet 410. 

At block 706, the application 414 determines whether the device identifier of the package docking device located at the delivery point matches the device identifier stored in the transaction packet 410. If so, the application 414 directs the UAV 102 to initiate the package transfer operation. The package transfer operation includes a hand off of the package between the UAV and the package docking device. The package transfer operation may also include recording the details of the hand off including the date and time of delivery and/or videorecording the hand off. 

At block 710, once the operation is completed, the application 414 transmits confirmation of the operation to the end user. This may be implemented using various techniques. For example, the confirmation may be directly transmitted to the package docking device over the wireless network. Alternatively, the confirmation may be transmitted by the UAV 102 over satellite, cellular, or other long-range network to the host system computer 106, which then provides the end user with access to the confirmation. In another embodiment, the UAV 102 may store the confirmation along with other confirmations in its memorymemory 408 and upload the confirmations in a batch process to the host system computer 106 at a designated time. 

If, however, the device identifier of the package docking device at the delivery location does not match the device identifier in the transaction packet 410, at block 712, the application 414 directs the communication components 404 to transmit a request over a short-range (e.g., BLUETOOTH or WI-FI) network. The request may include the device identifier, or network address, of the package docking device. Assuming that the package docking device has not moved outside of the range of communication of the UAV, the package docking device having the network address sends a signal indicating its presence at a new location. The package docking device, or alternatively the mobile device associated with the package docking device, may then send updated GPS location information to the UAV at block 714. The UAV is re-routed to the new location based on the updated GPS coordinates at block 716, and process reverts back to block 704. 

As indicated above, the package docking device may be a secured system in which a locking system and security key (e.g., locking system 502and security keysecurity key 506, respectively, of Figure 5) is used to gain access to the device. In this embodiment, the process 700 may include additional functions. The control processor 406 may be configured to store the security key associated with the package docking device. In an embodiment, the control processor 406 may be configured to receive an acknowledgement communication from the package docking device upon completion of the package transfer operation indicating the package docking device received the package. In a further embodiment, the control processor 406 may be configured to transmit, upon reaching a pre-defined clearance after departure of the UAV, a request to the package docking device to secure the package by locking the door. In this embodiment, a confirmation of the transaction may be transmitted by the UAV to the package docking device when the UAV receives an acknowledgement that the package is secured.