Secure payload deliveries via unmanned aerial vehicles

A device receives a request for a flight path for a UAV to travel from a first location to a second location, and determines capability information for the UAV based on component information of the UAV. The device calculates the flight path based on the capability information, and generates flight path instructions that include delivery confirmation instructions. The device provides the flight path instructions to the UAV to permit the UAV to travel from the first location to the second location to deliver a payload, and obtains, based on the delivery confirmation instructions, user credentials associated with a user at the second location. The device determines whether the user is an authorized recipient of the payload, based on the user credentials, and causes the UAV to selectively deliver the payload to the user based on whether the user is the authorized recipient of the payload.

BACKGROUND

An unmanned aerial vehicle (UAV) is an aircraft without a human pilot aboard. A UAV's flight may be controlled either autonomously by onboard computers or by remote control of a pilot on the ground or in another vehicle. A UAV is typically launched and recovered via an automatic system or an external operator on the ground. There are a wide variety of UAV shapes, sizes, configurations, characteristics, etc. UAVs may be used for a growing number of civilian applications, such as police surveillance, firefighting, security work (e.g., surveillance of pipelines), surveillance of farms, commercial purposes, etc.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Some private companies propose using UAVs for rapid delivery of lightweight commercial products (e.g., packages), food, medicine, etc. Such proposals for UAVs may need to meet various requirements, such as federal and state regulatory approval, public safety, reliability, individual privacy, operator training and certification, security (e.g., hacking), payload thievery, logistical challenges, etc.

FIGS. 1A and 1Bare diagrams of an overview of an example implementation100described herein. In example implementation100, assume that a first user device (e.g., user device A) is associated with a first user (e.g., user A) that is located at an origination location (e.g., location A), as shown inFIG. 1A. Further, assume that user A wants to fly a UAV from location A to a destination location (e.g., location B) in order to deliver a payload (e.g., a package) to a second user (e.g., user B) associated with a second user device (e.g., user device B). As further shown inFIG. 1A, a UAV platform or system may be associated with data storage, and the UAV platform and the data storage may communicate with networks, such as a wireless network, a satellite network, and/or other networks. The networks may provide information to the data storage, such as capability information associated with UAVs (e.g., thrust, battery life, etc. associated with UAVs); weather information associated with a geographical region that includes geographical locations of location A, location B, and locations between location A and location B; air traffic information associated with the geographical region; obstacle information (e.g., buildings, mountains, etc.) associated with the geographical region; regulatory information (e.g., no fly zones, government buildings, etc.) associated with the geographical region; historical information (e.g., former flight paths, former weather, etc.) associated with the geographical region; etc.

As further shown inFIG. 1A, user A may instruct user device A (or the UAV) to generate a request for a flight path (e.g., from location A to location B) for the UAV, and to provide the request to the UAV platform. The request may include credentials (e.g., a serial number, an identifier of a universal integrated circuit card (UICC), etc.) associated with the UAV. The UAV platform may utilize the UAV credentials to determine whether the UAV is authenticated for utilizing the UAV platform and/or one or more of the networks, and is registered with an appropriate authority (e.g., a government agency) for use. For example, the UAV platform may compare the UAV credentials with UAV account information (e.g., information associated with authenticated and registered UAVs) provided in the data storage to determine whether the UAV is authenticated. Assume that the UAV is authenticated for the UAV platform, and that the UAV platform provides, to the networks, a message indicating that the UAV is authenticated and/or authorized. The UAV may connect with the networks based on the authentication/authorization of the UAV.

The UAV platform may utilize information associated with the UAV (e.g., components of the UAV, the requested flight path, etc.) to identify capabilities of the UAV and other information in the data storage. For example, the UAV platform may retrieve capability information associated with the UAV and/or other information (e.g., the weather information, the obstacle information, the regulatory information, the historical information, etc. associated with the geographical region) from the data storage. The UAV platform may calculate the flight path from location A to location B based on the capability information and/or the other information, and may generate flight path instructions for the flight path. For example, the flight path instructions may indicate that the UAV is to fly at an altitude of two-thousand (2,000) meters, for fifty (50) kilometers and fifty-five (55) minutes, and then is to fly at an altitude of one-thousand (1,000) meters, for seventy (70) kilometers and one (1) hour in order to arrive at location B. The flight path instructions may also indicate that the UAV is to verify that user B is the appropriate recipient of the package before delivering the package to user B.

As shown inFIG. 1B, the UAV platform may provide, to the UAV, the flight path instructions. The UAV may take off from location A, and may travel the flight path based on the flight path instructions. When the UAV arrives at location B, the UAV may request user device B and/or user B to verify (e.g., via facial recognition, audio recognition, detection of the presence of user device B, etc.) that user B is the appropriate recipient of the package, and may receive user credentials (e.g., an image of user B, audio provided by user B, information identifying the presence of user device B, etc.) based on the request. The UAV may provide an arrival confirmation (e.g., confirming that the UAV arrived at location B) and the user credentials to the UAV platform, via the networks, as further shown inFIG. 1B.

The UAV platform may determine whether user B is the appropriate recipient of the package based on the user credentials. If the UAV platform determines that user B is not the appropriate recipient of the package (e.g., that user B is not verified), the UAV platform may instruct the UAV to not deliver the package to user B and to leave location B. As further shown inFIG. 1B, if the UAV platform determines that user B is the appropriate recipient of the package (e.g., that user B is verified), the UAV platform may instruct the UAV to deliver the package to user B. The UAV may provide the package to user B, and may leave location B via a return flight path (e.g., back to location A). After the UAV provides the package to user B, the UAV and/or user device B may generate a notification confirming that the package was received by user B, and may provide the notification to the UAV platform.

Systems and/or methods described herein may provide a platform that enables UAVs to safely traverse flight paths from origination locations to destination locations. The systems and/or methods may ensure that the UAVs and/or payloads of the UAVs are not stolen and/or damaged by unauthorized parties, and that the payloads are securely delivered to appropriate parties. The systems and/or methods may also ensure that the payloads are not left unattended for extended periods of time by verifying that authorized recipients are present to accept the payloads.

FIG. 2is a diagram of an example environment200in which systems and/or methods described herein may be implemented. As illustrated, environment200may include user devices210, UAVs220, a UAV platform230, data storage235, a wireless network240, a satellite network250, and other networks260. Devices/networks of environment200may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections.

User device210may include a device that is capable of communicating over wireless network240with UAV220, UAV platform230, and/or data storage235. In some implementations, user device210may include a radiotelephone; a personal communications services (PCS) terminal that may combine, for example, a cellular radiotelephone with data processing and data communications capabilities; a smart phone; a personal digital assistant (PDA) that can include a radiotelephone, a pager, Internet/intranet access, etc.; a laptop computer; a tablet computer; a global positioning system (GPS) device; a gaming device; or another type of computation and communication device.

UAV220may include an aircraft without a human pilot aboard, and may also be referred to as an unmanned aircraft (UA), a drone, a remotely piloted vehicle (RPV), a remotely piloted aircraft (RPA), or a remotely operated aircraft (ROA). In some implementations, UAV220may include a variety of shapes, sizes, configurations, characteristics, etc. for a variety of purposes and applications. In some implementations, UAV220may include one or more sensors, such as electromagnetic spectrum sensors (e.g., visual spectrum, infrared, or near infrared cameras, radar systems, etc.); biological sensors; chemical sensors; etc. In some implementations, UAV220may utilize one or more of the aforementioned sensors to sense (or detect) and avoid an obstacle in or near a flight path of UAV220.

In some implementations, UAV220may include a particular degree of autonomy based on computational resources provided in UAV220. For example, UAV220may include a low degree of autonomy when UAV220has few computational resources. In another example, UAV220may include a high degree of autonomy when UAV220has more computational resources (e.g., built-in control and/or guidance systems to perform low-level human pilot duties, such as speed and flight-path stabilization, scripted navigation functions, waypoint following, etc.). The computational resources of UAV220may combine information from different sensors to detect obstacles on the ground or in the air; communicate with one or more of networks240-260and/or other UAVs220; determine an optimal flight path for UAV220based on constraints, such as obstacles or fuel requirements; determine an optimal control maneuver in order to follow a given path or go from one location to another location; regulate a trajectory of UAV220; etc. In some implementations, UAV220may include a variety of components, such as a power source (e.g., an internal combustion engine, an electric battery, a solar-powered battery, etc.); a component that generates aerodynamic lift force (e.g., a rotor, a propeller, a rocket engine, a jet engine, etc.); computational resources; sensors; etc.

UAV platform230may include one or more personal computers, one or more workstation computers, one or more server devices, one or more virtual machines (VMs) provided in a cloud computing network, or one or more other types of computation and communication devices. In some implementations, UAV platform230may be associated with a service provider that manages and/or operates wireless network240, satellite network250, and/or other networks260, such as, for example, a telecommunication service provider, a television service provider, an Internet service provider, etc.

In some implementations, UAV platform230may receive a request for a flight path from an origination location to a destination location, and credentials associated with UAV220. UAV platform230may authenticate UAV220for use of UAV platform230and/or networks240-260based on the credentials, and may determine capability information for UAV220based on the request and/or component information associated with UAV220. UAV platform230may calculate the flight path from the origination location to the destination location based on the capability information and/or other information (e.g., weather information, air traffic information, etc.), and may generate flight path instructions, for the flight path, that include delivery confirmation and/or safety instructions. UAV platform230may provide the flight path instructions to UAV220, and UAV220may traverse the flight path until UAV220arrives at the destination location.

When UAV220arrives at the destination location, UAV platform230may receive, from UAV220, a confirmation that UAV220arrived at the destination location and/or credentials associated with a user located at the destination location. UAV platform230may determine whether the user is an appropriate recipient of a payload carried by UAV220based on the credentials. If UAV platform230determines that the user is the appropriate recipient of the payload, UAV platform230may instruct UAV220to deliver the payload to the user. If UAV platform230determines that the user is not the appropriate recipient of the payload, UAV platform230may instruct UAV220to not deliver the payload to the user and to leave the destination location.

In some implementations, UAV platform230may authenticate one or more users, associated with user device210and/or UAV220, for utilizing UAV platform230, and may securely store authentication information associated with the one or more users. In some implementations, UAV platform230may adhere to requirements to ensure that UAVs220safely traverse flight paths, and may limit the flight paths of UAVs220to particular safe zones (e.g., particular altitudes, particular geographical locations, particular geo-fencing, etc.) to further ensure safety.

Data storage235may include one or more storage devices that store information in one or more data structures, such as databases, tables, lists, trees, etc. In some implementations, data storage235may store information, such as UAV account information (e.g., serial numbers, model numbers, user names, etc. associated with UAVs220); capability information associated with UAVs220(e.g., thrust, battery life, etc. associated with UAVs220); weather information associated with a geographical region (e.g., precipitation amounts, wind conditions, etc.); air traffic information associated with the geographical region (e.g., commercial air traffic, other UAVs220, etc.); obstacle information (e.g., buildings, mountains, towers etc.) associated with the geographical region; regulatory information (e.g., no fly zones, government buildings, etc.) associated with the geographical region; historical information (e.g., former flight paths, former weather conditions, etc.) associated with the geographical region; etc. In some implementations, data storage235may be included within UAV platform230.

Wireless network240may include a fourth generation (4G) cellular network that includes an evolved packet system (EPS). The EPS may include a radio access network (e.g., referred to as a long term evolution (LTE) network), a wireless core network (e.g., referred to as an evolved packet core (EPC) network), an Internet protocol (IP) multimedia subsystem (IMS) network, and a packet data network (PDN). The LTE network may be referred to as an evolved universal terrestrial radio access network (E-UTRAN), and may include one or more base stations (e.g., cell towers). The EPC network may include an all-Internet protocol (IP) packet-switched core network that supports high-speed wireless and wireline broadband access technologies. The EPC network may allow user devices210and/or UAVs220to access various services by connecting to the LTE network, an evolved high rate packet data (eHRPD) radio access network (RAN), and/or a wireless local area network (WLAN) RAN. The IMS network may include an architectural framework or network (e.g., a telecommunications network) for delivering IP multimedia services. The PDN may include a communications network that is based on packet switching. In some implementations, wireless network240may provide location information (e.g., latitude and longitude coordinates) associated with user devices210and/or UAVs220. For example, wireless network240may determine a location of user device210and/or UAV220based on triangulation of signals, generated by user device210and/or UAV220and received by multiple cell towers, with prior knowledge of the cell tower locations.

Satellite network250may include a space-based satellite navigation system (e.g., a global positioning system (GPS)) that provides location and/or time information in all weather conditions, anywhere on or near the Earth where there is an unobstructed line of sight to four or more satellites (e.g., GPS satellites). In some implementations, satellite network250may provide location information (e.g., GPS coordinates) associated with user devices210and/or UAVs220, enable communication with user devices210and/or UAVs220, etc.

Each of other networks260may include a network, such as a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network, such as the Public Switched Telephone Network (PSTN) or a cellular network, an intranet, the Internet, a fiber optic network, a cloud computing network, or a combination of networks.

The number of devices and/or networks shown inFIG. 2is provided as an example. In practice, there may be additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those shown inFIG. 2. Furthermore, two or more devices shown inFIG. 2may be implemented within a single device, or a single device shown inFIG. 2may be implemented as multiple, distributed devices. Additionally, one or more of the devices of environment200may perform one or more functions described as being performed by another one or more devices of environment200.

FIG. 3is a diagram of example components of a device300that may correspond to one or more of the devices of environment200. In some implementations, one or more of the devices of environment200may include one or more devices300or one or more components of device300. As shown inFIG. 3, device300may include a bus310, a processor320, a memory330, a storage component340, an input component350, an output component360, and a communication interface370.

FIGS. 4A and 4Bdepict a flow chart of an example process400for ensuring that a payload is securely delivered by a UAV. In some implementations, one or more process blocks ofFIGS. 4A and 4Bmay be performed by UAV platform230. In some implementations, one or more process blocks ofFIGS. 4A and 4Bmay be performed by another device or a group of devices separate from or including UAV platform230, such as user device210and/or UAV220.

As shown inFIG. 4A, process400may include receiving a request for a flight path from a first location to a second location in a particular region, and credentials of a UAV (block405). For example, UAV platform230may receive a request for a flight path from a first location to a second location in a particular region, and credentials associated with UAV220. In some implementations, user device210may provide information associated with the flight path to UAV220, and UAV220may provide the request for the flight path to UAV platform230. In some implementations, the request for the flight path may be provided by user device210to UAV platform230. In some implementations, the request for the flight path may include a request for flight path instructions from an origination location (e.g., a current location of UAV220) to a destination location (e.g., a location in the particular region). The origination location and the destination location may be provided in the particular region. In some implementations, the credentials of UAV220may include an identification number, a model number, a serial number, an identifier of a UICC (or another type of smart card), a government registration number, a private encryption key, a public encryption key, a certificate, etc. associated with UAV220. In some implementations, the credentials of UAV220may include information identifying components of UAV220(e.g., serial numbers, model numbers, part numbers, etc. of the components).

As further shown inFIG. 4A, process400may include determining whether the UAV is authenticated for network(s) and is registered with an appropriate authority based on the UAV credentials (block410). For example, UAV platform230may determine whether UAV220is authenticated for using UAV platform230and/or one or more of networks240-260based on the credentials of UAV220. In some implementations, UAV platform230may compare the credentials of UAV220with UAV account information stored in data storage235(e.g., information associated with authenticated and registered UAVs220, such as identification numbers of UAVs220, public and/or private encryption keys of UAVs220, account status information, etc.) in order to determine whether UAV220is authenticated for using UAV platform230and/or one or more of networks240-260. For example, if the credentials of UAV220include a serial number of UAV220, UAV platform230may compare the serial number to the UAV account information in data storage235to determine whether UAV220is registered with UAV platform230, whether an account of UAV220is in good standing (e.g., paid for), etc. In some implementations, UAV platform230may determine whether UAV220is authenticated for using UAV platform230and/or one or more of networks240-260based on a UICC associated with UAV220.

In some implementations, UAV platform230may determine whether UAV220is registered with an appropriate authority (e.g., a government agency) based on the credentials of UAV220. For example, if the credentials of UAV220include a government registration number of UAV220, UAV platform230may compare the government registration number to the UAV account information in data storage235to determine whether UAV220is registered with a government agency to legally fly in airspace regulated by the government agency. In some implementations, UAV220may include a common protocol with other UAVs220. The common protocol may enable UAV220to be authenticated for using UAV platform230and/or one or more of networks240-260, to communicate with the other UAVs220, and/or to be verified as being registered with an appropriate authority. For example, if a particular UAV220is flying in an area where the particular UAV220loses communication with wireless network240, UAV220may establish communications with other UAVs220located near the particular UAV220(e.g., via the common protocol). The other UAVs220may share information (e.g., received from wireless network240) with the particular UAV220via the communications.

As further shown inFIG. 4A, if the UAV is not authenticated for the network(s) and/or is not registered with an appropriate authority (block410—NO), process400may include denying the request for the flight path (block415). For example, if UAV platform230determines that UAV220is not authenticated for using UAV platform230and/or one or more of networks240-260based on the credentials of UAV220, UAV platform230may deny the request for the flight path. In some implementations, UAV platform230may provide, to UAV220, a notification indicating that the request for the flight path is denied due to UAV220not being authenticated for using UAV platform230and/or one or more of networks240-260. In some implementations, UAV platform230may determine that UAV220is not authenticated for using UAV platform230and/or one or more of networks240-260when UAV220is not registered with UAV platform230, an account of UAV220is not in good standing, etc.

Additionally, or alternatively, if UAV platform230determines that UAV220is not registered with an appropriate authority based on the credentials of UAV220, UAV platform230may deny the request for the flight path. In some implementations, UAV platform230may provide, to UAV220, a notification indicating that the request for the flight path is denied due to UAV220not being registered with an appropriate authority. In some implementations, UAV platform230may determine that UAV220is not registered with an appropriate authority when UAV220fails to provide a government registration number via the credentials of UAV220.

As further shown inFIG. 4A, if the UAV is authenticated for the network(s) and is registered with an appropriate authority (block410—YES), process400may include determining capability information for the UAV based on the request and component information of the UAV (block420). For example, if UAV platform230determines, based on the credentials of UAV220, that UAV220is authenticated for using UAV platform230and/or one or more of networks240-260, and is registered with an appropriate authority, UAV platform230may approve the request for the flight path. In some implementations, UAV platform230may determine that UAV220is authenticated for using UAV platform230and/or one or more of networks240-260when UAV220is registered with UAV platform230, an account of UAV220is in good standing (e.g., paid for), etc. In some implementations, UAV platform230may determine that UAV220is registered with an appropriate authority when UAV220provides a government registration number that matches a government registration number provided in data storage235.

In some implementations, if UAV platform230approves the request for the flight path, UAV platform230may determine capability information for UAV220based on the request for the flight path and component information of UAV220(e.g., provided with the request for the flight path). For example, data storage235may include capability information associated with different components of UAVs220, such as battery life, thrusts provided by rotors, flight times associated with amounts of fuel, etc. In some implementations, UAV platform230may utilize the component information of UAV220(e.g., UAV220has a particular type of battery, engine, rotors, etc.) to retrieve the capability information for components of UAV220from data storage235. For example, if UAV220has a particular type of battery and a particular type of rotor, UAV platform230may determine that the particular type of battery of UAV220may provide two hours of flight time and that the particular type of rotor may enable UAV220to reach an altitude of one-thousand meters.

In some implementations, UAVs220may be required to follow a maintenance schedule (e.g., for safety purposes), and may need to be certified (e.g., by a government agency) that the maintenance schedule is followed. Such information may be provided in data storage235(e.g., with the capability information). In some implementations, if UAV platform230determines that UAV220is authenticated for using UAV platform230and/or one or more of networks240-260, and is registered with an appropriate authority, UAV platform230may still deny the request for the flight path if UAV platform230determines that UAV220has not properly followed the maintenance schedule. This may enable UAV platform230to ensure that only properly maintained UAVs220are permitted to fly, which may increase safety associated with UAVs220utilizing airspace.

As further shown inFIG. 4A, process400may include calculating the flight path from the first location to the second location based on the capability information and other information (block425). For example, UAV platform230may calculate the flight path from the origination location to the destination location based on the capability information and/or other information (e.g., the weather information, the air traffic information, the obstacle information, the regulatory information, and/or the historical information) stored in UAV platform230and/or data storage235. In some implementations, UAV platform230may determine whether the capability information indicates that UAV220may safely complete the flight path from the origination location to the destination location without stopping. If UAV platform230determines that UAV220cannot safely complete the flight path from the origination location to the destination location without stopping (e.g., to recharge or refuel), UAV platform230may determine one or more waypoints along the flight path where UAV220may stop and recharge or refuel.

In some implementations, UAV platform230may calculate the flight path based on the capability information associated with UAV220and the weather information. For example, UAV platform230may determine that, without weather issues, the flight path may take UAV220two hours to complete at an altitude of five-hundred meters. UAV platform230may further determine that wind conditions at five-hundred meters may create a headwind of fifty kilometers per hour on UAV220, but that wind conditions at one-thousand meters may create a tailwind of fifty kilometers per hour on UAV220. In such an example, UAV platform230may alter the flight path from an altitude of five-hundred meters to an altitude of one-thousand meters (e.g., if UAV220is capable of reaching the altitude of one-thousand meters). Assume that the tailwind at the altitude of one-thousand meters decreases the flight time from two hours to one hour and thirty minutes. Alternatively, UAV platform230may not alter the flight path, but the headwind at the altitude of five-hundred meters may increase the flight time from two hours to two hours and thirty minutes.

Additionally, or alternatively, UAV platform230may calculate the flight path based on the capability information associated with UAV220and the air traffic information. For example, UAV platform230may determine that, without air traffic issues, the flight path may take UAV220two hours to complete at an altitude of five-hundred meters. UAV platform230may further determine that other UAVs220are flying at the altitude of five-hundred meters based on the air traffic information, but that no other UAVs220are flying at an altitude of one-thousand meters. In such an example, UAV platform230may alter the flight path from an altitude of five-hundred meters to an altitude of one-thousand meters. The altitude of one-thousand meters may enable UAV220to safely arrive at the location without the possibility of colliding with other UAVs220. Alternatively, UAV platform230may not alter the flight path, but the other UAVs220flying at the altitude of five-hundred meters may increase possibility that UAV220may collide with another UAV220. UAV platform230may then determine whether UAV220is capable of safely flying at the altitude of five-hundred meters without colliding with another UAV220.

Additionally, or alternatively, UAV platform230may calculate the flight path based on the capability information associated with UAV220and the obstacle information. For example, UAV platform230may determine that, without obstacle issues, the flight path may take UAV220one hour to complete at an altitude of two-hundred meters. UAV platform230may further determine that one or more buildings are two-hundred meters in height based on the obstacle information, but that no other obstacles are greater than two-hundred meters in height. In such an example, UAV platform230may alter the flight path from an altitude of two-hundred meters to an altitude of three-hundred meters. The altitude of three-hundred meters may enable UAV220to safely arrive at the location without the possibility of colliding with the one or more buildings. Alternatively, UAV platform230may not alter the altitude of the flight path, but may change the flight path to avoid the one or more buildings, which may increase the flight time from one hour to one hour and thirty minutes.

Additionally, or alternatively, UAV platform230may calculate the flight path based on the capability information associated with UAV220and the regulatory information. For example, UAV platform230may determine that, without regulatory issues, the flight path may take UAV220one hour to complete at an altitude of five-hundred meters. UAV platform230may further determine that the flight path travels over a restricted facility based on the regulatory information. In such an example, UAV platform230may change the flight path to avoid flying over the restricted facility, which may increase the flight time from one hour to one hour and thirty minutes.

Additionally, or alternatively, UAV platform230may calculate the flight path based on the capability information associated with UAV220and the historical information. For example, UAV platform230may identify prior flight paths to the location from the historical information, and may select one of the prior flight paths, as the flight path, based on the capability information associated with UAV220. For example, assume that UAV platform230identifies three prior flight paths that include flight times of two hours, three hours, and four hours, respectively, and may determine that UAV220may safely fly for two hours and thirty minutes (e.g., based on the capability information). In such an example, UAV platform230may select, as the flight path, the prior flight path with the flight time of two hours.

In some implementations, UAV platform230may calculate the flight path from the origination location to the destination location based on the capability information, the weather information, the air traffic information, the obstacle information, the regulatory information, and/or the historical information.

As further shown inFIG. 4A, process400may include generating flight path instructions, for the flight path, that include delivery confirmation and/or safety instructions (block430). For example, UAV platform230may generate flight path instructions for the flight path. In some implementations, the flight path instructions may include specific altitudes for UAV220between fixed geographic coordinates (e.g., a first location and a second location); navigational information (e.g., travel east for three kilometers, then north for two kilometers, etc.); expected weather conditions (e.g., headwinds, tailwinds, temperatures, etc.); network information (e.g., locations of base stations of wireless network240); timing information (e.g., when to take off, when to perform certain navigational maneuvers, etc.); waypoint information (e.g., locations where UAV220may stop and recharge or refuel); etc. For example, the flight path instructions may include information that instructs UAV220to fly forty-five degrees northeast for ten kilometers at an altitude of five-hundred meters, fly three-hundred and fifteen degrees northwest for ten kilometers at an altitude of four-hundred meters, etc.

In some implementations, the flight path instructions may include delivery confirmation and/or safety instructions associated with delivering a payload of UAV220to an appropriate recipient. In some implementations, the delivery confirmation/safety instructions may include information instructing UAV220to drop off a payload carried by UAV220at the destination location and leave the destination location. In such implementations, UAV220may not require confirmation that the payload is received by an appropriate user at the destination location. In some implementations, a recipient of the payload may pay more for sensitive payloads (e.g., controlled substances, such as medicine or drugs, electronics, jewelry, etc.) so that UAV220and UAV platform230confirms that the sensitive payloads are received by the appropriate users at destination locations.

In some implementations, the delivery confirmation/safety instructions may include information instructing UAV220to drop the payload at the destination location without landing (e.g., hovering and releasing the payload). In such implementations, a height at which UAV220drops the payload may depend on the contents of the payload (e.g., unbreakable objects, such as medicine pills may be dropped from a greater height than breakable objects, such as electronics). In such implementations, UAV220may confirm that user device210, associated with an appropriate user, is within a particular proximity of UAV220before UAV220drops the payload at the destination location. Such implementations may prevent damage or theft of UAV220at the destination location by malicious parties (e.g., potential thieves).

In some implementations, the delivery confirmation/safety instructions may include information instructing UAV220to not land at the destination location if UAV220detects (e.g., via cameras, heat detection sensors, or other sensors) the presence of humans and/or animals within a particular distance of UAV220. In such implementations, UAV220may wait until the detected humans and/or animals are no longer within the particular distance before delivering the payload at the destination location. Such implementations may prevent damage or theft of UAV220and/or the payload, and may ensure that UAV220does not injure the detected humans and/or animals.

In some implementations, the delivery confirmation/safety instructions may include information instructing UAV220to deliver the payload at the destination location when a particular wireless local area network (WLAN) (e.g., an IEEE 802.15 (e.g., Bluetooth) network, an IEEE 802.11 (e.g., Wi-Fi) network, a near field communication (NFC) network, etc.) is detected by UAV220at the destination location. For example, user device210may generate the particular WLAN and/or a device at the destination location may generate the particular WLAN. If UAV220detects the particular WLAN, UAV220may determine that it is safe to deliver the payload and may deliver the payload.

In some implementations, the delivery confirmation/safety instructions may include information instructing UAV220to request verification of a user at the destination location. For example, UAV220may request that the user look at a camera of UAV220and smile or blink (e.g., to ensure that the user is not utilizing a picture). The camera of UAV220may capture the image of the user so that UAV platform230may perform facial recognition of the image in order to confirm an identity of the user. In such implementations, UAV platform230may include images, of appropriate users, that are provided by the users when establishing an account with UAV platform230, that are retrieved from social media web sites associated with the users (e.g., the users may provide, to UAV platform230, access to social media profiles of the users), etc.

In another example, UAV220may request that the user at the destination location speak into a microphone of UAV220. The microphone of UAV220may capture the voice of the user so that UAV platform230may perform audio recognition of the voice in order to confirm an identity of the user. In such implementations, UAV platform230may include audio files, of voices of appropriate users, that are provided by the users when establishing an account with UAV platform230, that are retrieved from social media web sites associated with the users, etc.

In still another example, UAV platform230may provide (e.g., via an email message, a text message, an instant message, etc.) a confirmation code (e.g., a bar code, a quick response (QR) code, a word, a numeric code, an alphabetical code, an alphanumeric code, etc.) and/or an authentication mechanism (e.g., a private and/or public encryption key, a certificate, a password, etc.) to user device210at the destination location. UAV platform230may request that the user provide the confirmation code and/or the authentication mechanism to UAV220when UAV220arrives at the destination location. For example, the user may speak the confirmation code and/or the authentication mechanism or may cause user device210to provide the confirmation code and/or the authentication mechanism to UAV220(e.g., UAV220may scan a bar code or a QR code displayed by user device210). UAV platform230may utilize the confirmation code and/or the authentication mechanism in order to confirm an identity of the user.

As shown inFIG. 4B, process400may include providing the flight path instructions to the UAV (block435). For example, UAV platform230may provide the flight path instructions to UAV220. In some implementations, UAV220may utilize the flight path instructions to travel via the flight path. For example, UAV220may take off at a time specified by the flight path instructions, may travel a route and at altitudes specified by the flight path instructions, may detect and avoid any obstacles encountered in the flight path, etc. until UAV220arrives at the destination location. In some implementations, when UAV220arrives at the destination location, UAV220may execute the delivery confirmation/safety instructions before delivering the payload at the destination location.

In some implementations, if UAV220includes sufficient computational resources (e.g., a sufficient degree of autonomy), UAV220may utilize information provided by the flight path instructions to calculate a flight path for UAV220and to generate flight path instructions. In such implementations, the flight path instructions provided by UAV platform230may include less detailed information, and UAV220may determine more detailed flight path instructions via the computational resources of UAV220.

As further shown inFIG. 4B, process400may include receiving, from the UAV, confirmation that the UAV arrived at the second location and user credentials (block440). For example, when UAV220arrives at the destination location, UAV220may generate a message confirming that UAV220has arrived at a geographical location associated with the destination location, and may provide the message to UAV platform230. UAV platform230may receive the message. In some implementations, UAV platform230may continuously monitor the location of UAV220(e.g., via satellite network250), and may determine that UAV220is at the destination location when a location (e.g., GPS coordinates) associated with UAV220is within a particular distance of the destination location (e.g., GPS coordinates of the destination location). In such implementations, UAV220need not generate the message confirming that UAV220has arrived at the destination location.

In some implementations, when UAV220arrives at the destination location, UAV220may request (e.g., based on the delivery confirmation/safety instructions) that a user at the destination location (e.g., a recipient of the payload) verify their identity by providing user credentials to UAV220. In some implementations, UAV220may drop off the payload at the destination location without requiring confirmation that the payload is received by an appropriate user at the destination location. In such implementations, UAV220may not request user credentials from the user at the destination location.

In some implementations, when UAV220arrives at the destination location, UAV220may determine (e.g., based on the delivery confirmation/safety instructions) whether a particular WLAN is detected by UAV220at the destination location. If UAV220detects the particular WLAN, UAV220may utilize the detected WLAN as the user credentials, and may provide the user credentials to UAV platform230.

In some implementations, when UAV220arrives at the destination location, UAV220may request (e.g., based on the delivery confirmation/safety instructions) that the user look at a camera of UAV220and make a gestures (e.g., smile or blink to ensure that the user is not utilizing a picture). The camera of UAV220may capture the image of the user, and UAV220may provide (e.g., as the user credentials) the image of the user to UAV platform230.

In some implementations, when UAV220arrives at the destination location, UAV220may request (e.g., based on the delivery confirmation/safety instructions) that the user speak into a microphone of UAV220. The microphone of UAV220may capture the voice of the user, and UAV220may provide (e.g., as the user credentials) the voice of the user to UAV platform230.

In some implementations, UAV platform230may provide (e.g., via an email message, a text message, an instant message, etc.) a confirmation code and/or an authentication mechanism to user device210at the destination location. When UAV220arrives at the destination location, UAV220may request that the user provide the confirmation code and/or the authentication mechanism to UAV220. For example, the user may speak the confirmation code and/or the authentication mechanism or may cause user device210to provide the confirmation code and/or the authentication mechanism to UAV220. UAV220may provide (e.g., as the user credentials) the confirmation code and/or the authentication mechanism, received from the user and/or user device210, to UAV platform230.

In some implementations, for increased security, UAV220may request two or more forms of user credentials (e.g., a bar code and a password, an encryption key and a QR code, an encryption key and facial recognition, etc.) from the user at the destination location so that UAV platform230may verify and/or authenticate an identity of the user.

As further shown inFIG. 4B, process400may include determining whether the user is an appropriate recipient of a payload based on the user credentials (block445). For example, UAV platform230may determine whether the user at the destination location is an appropriate recipient of the payload based on the user credentials received from UAV220. In some implementations, UAV platform230may compare the user credentials with user account information stored in data storage235(e.g., information associated with authenticated and registered users of UAV platform230, such as confirmation codes, authentication mechanisms, etc. provided by UAV platform230to user devices210) in order to determine whether the user at the destination location is the appropriate recipient of the payload.

In some implementations, if UAV220captures an image of the user at the destination location, UAV platform230may perform facial recognition of the image in order to confirm an identity of the user. In such implementations, UAV platform230and/or data storage235may store images of appropriate users. UAV platform230, via the facial recognition, may compare the image received from UAV220with the stored images in order to determine whether the user at the destination location is the appropriate recipient of the payload. For example, if the image matches a stored image, UAV platform230may determine that the user is the appropriate recipient of the payload.

In some implementations, if UAV220captures the voice of the user, UAV platform230may perform audio recognition of the voice in order to confirm an identity of the user. In such implementations, UAV platform230and/or data storage235may store audio files of voices of appropriate users. UAV platform230, via the audio recognition, may compare the voice received from UAV220with the stored audio files in order to determine whether the user at the destination location is the appropriate recipient of the payload. For example, if the voice matches a stored audio file, UAV platform230may determine that the user is the appropriate recipient of the payload.

In some implementations, if UAV platform230provides a confirmation code and/or an authentication mechanism to user device210at the destination location, UAV platform230may determine whether UAV220receives the same confirmation code and/or authentication mechanism from the user or user device210at the destination location. For example, if the user or user device210provides the confirmation code and/or the authentication mechanism to UAV220, UAV220may provide the received confirmation code/authentication mechanism to UAV platform230. UAV platform230may determine whether the received confirmation code/authentication mechanism is correct in order to confirm that the user is the appropriate recipient of the payload.

As further shown inFIG. 4B, if the user is the appropriate recipient of the payload (block445—YES), process400may include providing, to the UAV, an instruction to deliver the payload to the user (block450). For example, if UAV platform230determines that the user is the appropriate recipient of the payload, UAV platform230may provide, to UAV220, information instructing UAV220to deliver the payload to the user. In some implementations, the information provided to UAV220may include information indicating that the user's identity is verified and that the user is the appropriate recipient of the payload. In some implementations, UAV220may provide the payload to the user at the destination location, based on the information received from UAV platform230. After UAV220provides the payload to the user, user device210and/or UAV220may provide a notification to UAV platform230, via one or more of networks240-260. In some implementations, the notification may indicate that the payload has been received by the user at the destination location. In some implementations, after UAV220provides the payload to the user, UAV220may return to the origination location or to another location (e.g., a storage location associated with a delivery company).

As further shown inFIG. 4B, if the user is not the appropriate recipient of the payload (block445—NO), process400may include providing, to the UAV, an instruction to not deliver the payload to the user and to leave the second location (block455). For example, if UAV platform230determines that the user is not the appropriate recipient of the payload, UAV platform230may provide, to UAV220, information instructing UAV220to not deliver the payload to the user and to leave the destination location. In some implementations, the information provided to UAV220may include information indicating that the user's identity is not verified and that the user is not the appropriate recipient of the payload. In some implementations, based on the information received from UAV platform230, UAV220may not provide the payload to the user at the destination location, and may return to the origination location or to another location (e.g., a payload facility associated with a package facility).

AlthoughFIGS. 4A and 4Bshows example blocks of process400, in some implementations, process400may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted inFIGS. 4A and 4B. Additionally, or alternatively, two or more of the blocks of process400may be performed in parallel.

FIGS. 5A-5Fare diagrams of an example500relating to example process400shown inFIGS. 4A and 4B. Assume that a first user device210(e.g., a tablet210) is associated with a first user (e.g., an employee at a delivery company) that is located at an origination location (e.g., Washington, D.C.), as shown inFIG. 5A. Further, assume that a second user device210(e.g., a computer210) is associated with a second user (e.g., a doctor) that is located at a destination location (e.g., a hospital in Fairfax, Va.), and that the doctor has instructed computer210to request delivery of a package of medicine to Fairfax, Va. For example, computer210may inform tablet210(e.g., via one or more servers associated with the delivery company) and the employee that the medicine is to be delivered to the doctor as soon as possible. Further, assume that the employee wants to utilize UAV220to fly the medicine from Washington, D.C. to Fairfax, Va. in order to deliver the medicine to the doctor.

As further shown inFIG. 5A, UAV platform230and data storage235may communicate with wireless network240, satellite network250, and/or other networks260. Wireless network240, satellite network250, and/or other networks260may provide, to data storage235, information505, such as capability information associated with UAV220, weather information associated with a geographical region (e.g., that includes a geographical location of Washington, D.C., a geographical location of Fairfax, Va., and geographical locations between Washington and Fairfax), air traffic information associated with the geographical region, obstacle information associated with the geographical region, regulatory information associated with the geographical region, historical information associated with the geographical region, etc.

As further shown inFIG. 5A, the employee may instruct tablet210(or UAV220) to generate a request510for a flight path (e.g., from Washington, D.C. to Fairfax, Va.) for UAV220, and to provide request510to UAV platform230. Request510may include credentials515(e.g., a serial number, an identifier of a UICC, etc. of UAV220) associated with UAV220, or credentials515may be provided separately from request510to UAV platform230. UAV platform230may utilize credentials515to determine whether UAV220is authenticated for utilizing UAV platform230and/or one or more of networks240-260, and is registered with an appropriate authority for use. For example, UAV platform230may compare credentials515with information provided in data storage235in order to determine whether UAV220is authenticated for utilizing UAV platform230and/or one or more of networks240-260, and is registered with an appropriate authority.

Assume that UAV platform230determines that UAV220is authenticated for utilizing UAV platform230and/or one or more of networks240-260, and is registered with an appropriate authority, as indicated by reference number520inFIG. 5B. Further, assume that UAV platform230provides, to networks240-260, a message525indicating that UAV220is authenticated to use one or more of networks240-260. UAV220may connect with one or more of networks240-260based on the authentication of UAV220, as indicated by reference number530. As further shown inFIG. 5B, when UAV platform230determines that UAV220is authenticated, UAV platform230may retrieve capability information535associated with UAV220and other information540(e.g., weather information, air traffic information, obstacle information, regulatory information, and/or historical information) from data storage235based on component information of UAV220(e.g., provided with request510).

As shown inFIG. 5C, UAV platform230may calculate a flight path545from Washington, D.C. to Fairfax, Va. based on capability information535and/or other information540. UAV platform230may generate flight path instructions550for flight path545, and may provide flight path instructions550to UAV220via one or more of networks240-260. Flight path instructions550may include information instructing UAV220to fly north at zero degrees for ten kilometers, fly northeast at forty degrees for three kilometers, at an altitude of one-thousand meters, etc. Flight path instructions550may also include delivery confirmation and/or safety instructions associated with delivering the medicine to the doctor in Fairfax, Va. Assume that the delivery confirmation/safety instructions instruct UAV220to acquire an image of the doctor's face before providing the medicine to the doctor. UAV220may take off from Washington, D.C., and may travel flight path545based on flight path instructions550.

As shown inFIG. 5D, when UAV220arrives at the hospital in Fairfax, Va., UAV220(e.g., based on flight path instructions550) may provide, to computer210, a request555to verify an identity of the doctor. For example, request555may instruct the doctor to look at UAV220and smile so that a camera of UAV220may capture an image of the doctor's face. The doctor may look at the camera of UAV220and smile so that the doctor may provide the image of the doctor's face (e.g., doctor credentials560) to UAV220. After receiving doctor credentials560, UAV220may provide an arrival confirmation565, indicating that UAV220arrived at the hospital in Fairfax, Va., and doctor credentials560, to UAV platform230(e.g., via one or more of networks240-260), as further shown inFIG. 5D.

UAV platform230may receive doctor credentials560and arrival confirmation565, and may determine whether the doctor is the appropriate recipient of the medicine based on doctor credentials560. As shown inFIG. 5E, assume that UAV platform230determines that the doctor is the appropriate recipient of the medicine since the image of the doctor's face matches at least one image of the doctor stored in UAV platform230and/or data storage235. UAV platform230may provide, to UAV220(e.g., via one or more of networks240-260), a message570indicating that the doctor is verified as the appropriate recipient of the medicine and instructing UAV220to deliver the medicine to the doctor. UAV220may receive message570, and may provide the medicine to the doctor based on message570. After providing the medicine to the doctor, UAV220may return to Washington, D.C. via a return flight path575specified by UAV platform230(e.g., via message570). As further shown inFIG. 5E, UAV220and/or computer210(e.g., via the doctor's input) may generate a notification580confirming that the medicine was received by the doctor, and may provide notification580to UAV platform230.

In some implementations, the hospital may include a particular number of employees that are authorized to accept delivery of the medicine from UAV220. In such implementations, UAV220may capture an image of a face of a hospital employee attempting to accept delivery of the medicine, and may provide the captured image to UAV platform230. UAV platform230may compare the captured image to facial images of hospital employees authorized to accept delivery of the medicine to determine if the captured image matches one of the facial images. If UAV platform230determines a match for the captured image, UAV platform230may instruct UAV220to provide the medicine to the hospital employee attempting to accept delivery of the medicine.

In some implementations, the hospital may include a particular number of employees that are waiting for delivery of different medicines from different UAVs220. In such implementations, UAV220may attempt to authenticate the particular number of employees or may request that the authorized employee (e.g., the doctor) for the medicine step forward to be authenticated by UAV220and UAV platform230.

As shown inFIG. 5F, now assume that UAV platform230determines that the doctor is not the appropriate recipient of the medicine since the image of the doctor's face failed to match at least one image of the doctor stored in UAV platform230and/or data storage235. UAV platform230may provide, to UAV220(e.g., via one or more of networks240-260), a message585indicating that the doctor is not verified as the appropriate recipient of the medicine and instructing UAV220to return the medicine to the employee in Washington, D.C. UAV220may receive message585, and may return, with the medicine, to Washington, D.C. via a return flight path590specified by UAV platform230(e.g., in message585).

As indicated above,FIGS. 5A-5Fare provided merely as an example. Other examples are possible and may differ from what was described with regard toFIGS. 5A-5F.

Systems and/or methods described herein may provide a platform that enables UAVs to safely traverse flight paths from origination locations to destination locations. The systems and/or methods may ensure that the UAVs and/or payloads of the UAVs are not stolen and/or damaged, and that the payloads are securely delivered to appropriate recipients. The systems and/or methods may also ensure that the payloads are not left unattended for extended periods of time by verifying that authorized recipients are present to accept the payloads.

A component is intended to be broadly construed as hardware, firmware, or a combination of hardware and software.

User interfaces may include graphical user interfaces (GUIs) and/or non-graphical user interfaces, such as text-based interfaces. The user interfaces may provide information to users via customized interfaces (e.g., proprietary interfaces) and/or other types of interfaces (e.g., browser-based interfaces, etc.). The user interfaces may receive user inputs via one or more input devices, may be user-configurable (e.g., a user may change the sizes of the user interfaces, information displayed in the user interfaces, color schemes used by the user interfaces, positions of text, images, icons, windows, etc., in the user interfaces, etc.), and/or may not be user-configurable. Information associated with the user interfaces may be selected and/or manipulated by a user (e.g., via a touch screen display, a mouse, a keyboard, a keypad, voice commands, etc.).

It will be apparent that systems and/or methods, as described herein, may be implemented in many different forms of software, firmware, and hardware in the implementations illustrated in the figures. The actual software code or specialized control hardware used to implement these systems and/or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and/or methods were described without reference to the specific software code—it being understood that software and control hardware can be designed to implement the systems and/or methods based on the description herein.