US20210304626A1 - Selection of networks for communicating with unmanned aerial vehicles - Google Patents
Selection of networks for communicating with unmanned aerial vehicles Download PDFInfo
- Publication number
- US20210304626A1 US20210304626A1 US17/227,604 US202117227604A US2021304626A1 US 20210304626 A1 US20210304626 A1 US 20210304626A1 US 202117227604 A US202117227604 A US 202117227604A US 2021304626 A1 US2021304626 A1 US 2021304626A1
- Authority
- US
- United States
- Prior art keywords
- flight path
- network
- networks
- uav
- unmanned aerial
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 claims description 47
- 230000008569 process Effects 0.000 description 27
- 238000004891 communication Methods 0.000 description 21
- 238000013500 data storage Methods 0.000 description 21
- 230000001413 cellular effect Effects 0.000 description 19
- 230000001105 regulatory effect Effects 0.000 description 11
- 238000010586 diagram Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 5
- 230000001174 ascending effect Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000001419 dependent effect Effects 0.000 description 2
- 238000001228 spectrum Methods 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 238000002485 combustion reaction Methods 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 239000003814 drug Substances 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000001556 precipitation Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000006641 stabilisation Effects 0.000 description 1
- 238000011105 stabilization Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0047—Navigation or guidance aids for a single aircraft
- G08G5/0069—Navigation or guidance aids for a single aircraft specially adapted for an unmanned aircraft
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/003—Flight plan management
- G08G5/0034—Assembly of a flight plan
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B64—AIRCRAFT; AVIATION; COSMONAUTICS
- B64C—AEROPLANES; HELICOPTERS
- B64C39/00—Aircraft not otherwise provided for
- B64C39/02—Aircraft not otherwise provided for characterised by special use
- B64C39/024—Aircraft not otherwise provided for characterised by special use of the remote controlled vehicle type, i.e. RPV
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/083—Shipping
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0004—Transmission of traffic-related information to or from an aircraft
- G08G5/0013—Transmission of traffic-related information to or from an aircraft with a ground station
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0017—Arrangements for implementing traffic-related aircraft activities, e.g. arrangements for generating, displaying, acquiring or managing traffic information
- G08G5/0026—Arrangements for implementing traffic-related aircraft activities, e.g. arrangements for generating, displaying, acquiring or managing traffic information located on the ground
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/003—Flight plan management
- G08G5/0039—Modification of a flight plan
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0043—Traffic management of multiple aircrafts from the ground
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0047—Navigation or guidance aids for a single aircraft
- G08G5/0056—Navigation or guidance aids for a single aircraft in an emergency situation, e.g. hijacking
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0047—Navigation or guidance aids for a single aircraft
- G08G5/006—Navigation or guidance aids for a single aircraft in accordance with predefined flight zones, e.g. to avoid prohibited zones
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0073—Surveillance aids
- G08G5/0082—Surveillance aids for monitoring traffic from a ground station
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0073—Surveillance aids
- G08G5/0086—Surveillance aids for monitoring terrain
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0073—Surveillance aids
- G08G5/0091—Surveillance aids for monitoring atmospheric conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B17/00—Monitoring; Testing
- H04B17/30—Monitoring; Testing of propagation channels
- H04B17/309—Measuring or estimating channel quality parameters
- H04B17/318—Received signal strength
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/185—Space-based or airborne stations; Stations for satellite systems
- H04B7/18502—Airborne stations
- H04B7/18504—Aircraft used as relay or high altitude atmospheric platform
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B64—AIRCRAFT; AVIATION; COSMONAUTICS
- B64U—UNMANNED AERIAL VEHICLES [UAV]; EQUIPMENT THEREFOR
- B64U2101/00—UAVs specially adapted for particular uses or applications
- B64U2101/60—UAVs specially adapted for particular uses or applications for transporting passengers; for transporting goods other than weapons
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B64—AIRCRAFT; AVIATION; COSMONAUTICS
- B64U—UNMANNED AERIAL VEHICLES [UAV]; EQUIPMENT THEREFOR
- B64U2201/00—UAVs characterised by their flight controls
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B64—AIRCRAFT; AVIATION; COSMONAUTICS
- B64U—UNMANNED AERIAL VEHICLES [UAV]; EQUIPMENT THEREFOR
- B64U2201/00—UAVs characterised by their flight controls
- B64U2201/10—UAVs characterised by their flight controls autonomous, i.e. by navigating independently from ground or air stations, e.g. by using inertial navigation systems [INS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/29—Geographical information databases
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
- H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
- H04W36/1446—Reselecting a network or an air interface over a different radio air interface technology wherein at least one of the networks is unlicensed
Definitions
- UAV unmanned aerial vehicle
- 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.
- UAV shapes, sizes, configurations, characteristics, etc. 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.
- FIGS. 1A and 1B are diagrams of an overview of an example implementation described herein;
- FIG. 2 is a diagram of an example environment in which systems and/or methods described herein may be implemented
- FIG. 3 is a diagram of example components of one or more devices of FIG. 2 ;
- FIGS. 4A and 4B depict a flow chart of an example process for selecting a network for communicating with a UAV during traversal of a flight path
- FIGS. 5A-5E are diagrams of an example relating to the example process shown in FIGS. 4A and 4B .
- 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 1B are diagrams of an overview of an example implementation 100 described herein.
- a first user device e.g., user device A
- a first user e.g., user A
- an origination location e.g., location A
- user A wants to fly a UAV from location A to a destination location (e.g., location B) in order to deliver a package to a second user (e.g., user B) associated with a second user device (e.g., user device B).
- a destination location e.g., location B
- a second user e.g., user device B
- 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 the UAV (e.g., a thrust, a battery life, etc.
- 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.
- obstacle information e.g., buildings, mountains, etc.
- regulatory information e.g., no-fly zones, government buildings, etc.
- historical information e.g., former flight paths, former weather, etc.
- user A may instruct user device A 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., serial numbers, identifiers of universal integrated circuit cards (UICCs), 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.
- an appropriate authority e.g., a government agency
- 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. In example implementation 100 , assume that the UAV is authenticated by the UAV platform.
- UAV account information e.g., information associated with authenticated and registered UAVs
- the UAV platform may calculate a flight path from location A to location B based on aviation information (e.g., the weather information, the air traffic information, etc.) associated with the geographical region.
- the UAV platform may track the flight path of the UAV based on the UAV's continuous connectivity to a network (e.g., the wireless network, the satellite network, etc.), but may lose connectivity with the UAV when the UAV travels outside a range of the network.
- the UAV platform may determine network requirements for the flight path based on the request for the flight path. For example, the UAV platform may determine that the UAV is to connect to a cheapest network, a network with the greatest security, a network with the most bandwidth, etc. during traversal of the flight path.
- the UAV platform may assign different weights to different available networks (e.g., the wireless network, the satellite network, etc.), and may calculate a score for each of the available networks based on the network requirements and the assigned weights.
- the UAV platform may rank the available networks based on the scores (e.g., in ascending order, descending order, etc.), and may store the scores and the rankings for the available networks in the data storage.
- the UAV platform may retrieve the scores and the rankings for the available networks from the data storage, as further shown in FIG. 1A .
- the UAV platform may select a particular network based on the scores and the rankings for the available networks. For example, the UAV platform may select the wireless network as the network to which the UAV is to connect based on the scores and the rankings for the available networks since the wireless network may be less expensive to utilize than the satellite network and the other networks. As further shown in FIG. 1A the UAV may connect to the wireless network based on the selection of the wireless network (e.g., as the particular network).
- the UAV platform may generate flight path instructions for the flight path, as shown in FIG. 1B .
- 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, in order to arrive at location B.
- the UAV platform may provide the flight path instructions to the UAV (e.g., via the wireless network), as further shown in FIG. 1B .
- the UAV may take off from location A, and may travel the flight path based on the flight path instructions. While the UAV is traversing the flight path, the wireless network may receive and/or generate network connectivity information associated with the UAV (e.g., about changing conditions, such as the UAV flying out of range of the wireless network, etc.). The wireless network may provide the network connectivity information to the UAV platform, and the UAV platform may select a new network, to which the UAV is to connect, based on the network connectivity information. For example, the UAV platform may select the satellite network as the new network, and may instruct the UAV to connect to the satellite network based on the selection. As further shown in FIG.
- the UAV may connect to the satellite network, and may continue to traverse the flight path (e.g., while connected to the satellite network) until the UAV arrives at location B.
- the UAV and/or user device B may generate a notification indicating that the UAV arrived safely at location 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 enable UAVs to seamlessly connect with the platform via various networks, which may ensure that the platform continuously communicates with the UAVs.
- the systems and/or methods may enable the platform to select a network for communicating with the UAV, and the selected network may reduce connectivity costs, increase security of communications, reduce the need for handoffs to other networks, offer the best connectivity, or the like.
- FIG. 2 is a diagram of an example environment 200 in which systems and/or methods described herein may be implemented.
- environment 200 may include user devices 210 , UAVs 220 , a UAV platform 230 , data storage 235 , a wireless network 240 , a satellite network 250 , and other networks 260 .
- Devices/networks of environment 200 may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections.
- User device 210 may include a device that is capable of communicating over wireless network 240 with UAV 220 , UAV platform 230 , and/or data storage 235 .
- user device 210 may 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.
- PCS personal communications services
- PDA personal digital assistant
- UAV 220 may 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).
- UAV 220 may include a variety of shapes, sizes, configurations, characteristics, etc. for a variety of purposes and applications.
- UAV 220 may 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.
- UAV 220 may utilize one or more of the aforementioned sensors to sense (or detect) and avoid an obstacle in or near a flight path of UAV 220 .
- UAV 220 may include a particular degree of autonomy based on computational resources provided in UAV 220 .
- UAV 220 may include a low degree of autonomy when UAV 220 has few computational resources.
- UAV 220 may include a high degree of autonomy when UAV 220 has 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 UAV 220 may combine information from different sensors to detect obstacles on the ground or in the air; communicate with one or more of networks 240 - 260 and/or other UAVs 220 ; determine an optimal flight path for UAV 220 based 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 UAV 220 ; etc.
- UAV 220 may 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.
- 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 e.g., a rotor, a propeller, a rocket engine, a jet engine, etc.
- UAV platform 230 may 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.
- UAV platform 230 may be associated with a service provider that manages and/or operates wireless network 240 , satellite network 250 , and/or other networks 260 , such as, for example, a telecommunication service provider, a television service provider, an Internet service provider, etc.
- UAV platform 230 may receive, from user device 210 , a request for a flight path from an origination location to a destination location.
- UAV platform 230 may calculate the flight path from the origination location to the destination location based on aviation information (e.g., weather information, air traffic information, etc.), and may determine network requirements for the flight path based on the request for the flight path.
- UAV platform 230 may assign different weights to different networks (e.g., wireless network 240 , satellite network 250 , etc.) available to UAV 220 , and may calculate a score for each network based on the network requirements and/or the assigned weights.
- networks e.g., wireless network 240 , satellite network 250 , etc.
- UAV platform 230 may rank the available networks based on the scores (e.g., in ascending order, descending order, etc.), and may select a particular network, from the available networks, based on the ranks and/or based on the network requirements for the flight path. After selecting the network, UAV platform 230 may generate flight path instructions that identify the selected network, and may provide the flight path instructions to UAV 220 . UAV 220 may connect to the selected network, based on the flight path instructions, so that UAV 220 may communicate with UAV platform 230 . UAV platform 230 may receive network connectivity information from UAV 220 during traversal of the flight path by UAV 220 .
- the scores e.g., in ascending order, descending order, etc.
- UAV platform 230 may select a new network based on the network connectivity information, and may provide information associated with the new network to UAV 220 (e.g., so that UAV 220 may connect with the new network). UAV platform 230 may receive a notification that UAV 220 arrived at the destination location when UAV 220 lands at the destination location.
- UAV platform 230 may authenticate one or more users, associated with user device 210 and/or UAV 220 , for utilizing UAV platform 230 , and may securely store authentication information associated with the one or more users.
- UAV platform 230 may adhere to requirements to ensure that UAVs 220 safely traverse flight paths, and may limit the flight paths of UAVs 220 to particular safe zones (e.g., particular altitudes, particular geographical locations, particular geo-fencing, etc.) to further ensure safety.
- Data storage 235 may include one or more storage devices that store information in one or more data structures, such as databases, tables, lists, trees, etc.
- data storage 235 may store information, such as UAV account information (e.g., serial numbers, model numbers, user names, etc. associated with UAVs 220 ); capability information associated with UAVs 220 (e.g., thrust, battery life, etc.
- UAVs 220 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 UAVs 220 , 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.
- data storage 235 may be included within UAV platform 230 .
- Wireless network 240 may 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).
- LTE long term evolution
- EPC evolved packet core
- IP Internet protocol
- PDN packet data network
- 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).
- EPC network may include an all-Internet protocol (IP) packet-switched core network that supports high-speed wireless and wireline broadband access technologies.
- IP Internet protocol
- the EPC network may allow user devices 210 and/or UAVs 220 to 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.
- wireless network 240 may provide location information (e.g., latitude and longitude coordinates) associated with user devices 210 and/or UAVs 220 .
- wireless network 240 may determine a location of user device 210 and/or UAV 220 based on triangulation of signals, generated by user device 210 and/or UAV 220 and received by multiple cell towers, with prior knowledge of the cell tower locations.
- Satellite network 250 may 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).
- satellite network 250 may provide location information (e.g., GPS coordinates) associated with user devices 210 and/or UAVs 220 , enable communication with user devices 210 and/or UAVs 220 , etc.
- GPS global positioning system
- Each of other networks 260 may 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.
- LAN local area network
- WAN wide area network
- MAN metropolitan area network
- PSTN Public Switched Telephone Network
- the number of devices and/or networks shown in FIG. 2 is 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 in FIG. 2 . Furthermore, two or more devices shown in FIG. 2 may be implemented within a single device, or a single device shown in FIG. 2 may be implemented as multiple, distributed devices. Additionally, one or more of the devices of environment 200 may perform one or more functions described as being performed by another one or more devices of environment 200 .
- FIG. 3 is a diagram of example components of a device 300 that may correspond to one or more of the devices of environment 200 .
- one or more of the devices of environment 200 may include one or more devices 300 or one or more components of device 300 .
- device 300 may include a bus 310 , a processor 320 , a memory 330 , a storage component 340 , an input component 350 , an output component 360 , and a communication interface 370 .
- Bus 310 may include a component that permits communication among the components of device 300 .
- Processor 320 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), etc.), a microprocessor, and/or any processing component (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.) that interprets and/or executes instructions.
- Memory 330 may include a random access memory (RAM), a read only memory (ROM), and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, an optical memory, etc.) that stores information and/or instructions for use by processor 320 .
- RAM random access memory
- ROM read only memory
- static storage device e.g., a flash memory, a magnetic memory, an optical memory, etc.
- Storage component 340 may store information and/or software related to the operation and use of device 300 .
- storage component 340 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, etc.), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of computer-readable medium, along with a corresponding drive.
- Input component 350 may include a component that permits device 300 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, a microphone, etc.). Additionally, or alternatively, input component 350 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.). Output component 360 may include a component that provides output information from device 300 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.).
- GPS global positioning system
- LEDs light-emitting diodes
- Communication interface 370 may include a transceiver-like component (e.g., a transceiver, a separate receiver and transmitter, etc.) that enables device 300 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface 370 may permit device 300 to receive information from another device and/or provide information to another device.
- communication interface 370 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, or the like.
- RF radio frequency
- USB universal serial bus
- Device 300 may perform one or more processes described herein. Device 300 may perform these processes in response to processor 320 executing software instructions stored by a computer-readable medium, such as memory 330 and/or storage component 340 .
- a computer-readable medium is defined herein as a non-transitory memory device.
- a memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.
- Software instructions may be read into memory 330 and/or storage component 340 from another computer-readable medium or from another device via communication interface 370 .
- software instructions stored in memory 330 and/or storage component 340 may cause processor 320 to perform one or more processes described herein.
- hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein.
- implementations described herein are not limited to any specific combination of hardware circuitry and software.
- device 300 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 3 . Additionally, or alternatively, a set of components (e.g., one or more components) of device 300 may perform one or more functions described as being performed by another set of components of device 300 .
- FIGS. 4A and 4B depict a flow chart of an example process 400 for selecting a network for communicating with a UAV during traversal of a flight path.
- one or more process blocks of FIGS. 4A and 4B may be performed by UAV platform 230 .
- one or more process blocks of FIGS. 4A and 4B may be performed by another device or a group of devices separate from or including UAV platform 230 , such as user device 210 and/or UAV 220 .
- process 400 may include receiving a request for a flight path from a first location to a second location in a region (block 405 ).
- UAV platform 230 may receive, from user device 210 , a request for a flight path from a first location to a second location in a particular region.
- the request for the flight path may include a request for flight path instructions from an origination location (e.g., a current location of UAV 220 ) 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.
- UAV 220 may be associated with UAV platform 230 and/or user(s) associated with user device 210 .
- user device 210 and UAV 220 may be owned and/or operated by a delivery company, a telecommunication service provider, a television service provider, an Internet service provider, etc.
- process 400 may include calculating the flight path from the first location to the second location based on aviation information (block 410 ).
- UAV platform 230 may calculate the flight path from the origination location to the destination location based on aviation information.
- UAV platform 230 may calculate the flight path from the origination location to the destination location based on aviation information associated with the particular region, such as the weather information, the air traffic information, the obstacle information, the regulatory information, the historical information, etc. stored in UAV platform 230 and/or data storage 235 .
- UAV platform 230 may determine whether the aviation information indicates that UAV 220 may safely complete the flight path from the origination location to the destination location without stopping.
- UAV platform 230 may determine one or more waypoints along the flight path for stopping and recharging or refueling.
- UAV platform 230 may calculate the flight path based on the weather information. For example, UAV platform 230 may determine that, without weather issues, the flight path may take UAV 220 two hours to complete at an altitude of five-hundred meters. UAV platform 230 may further determine that wind conditions at five-hundred meters may create a headwind of fifty kilometers per hour on UAV 220 , but that wind conditions at one-thousand meters may create a tailwind of fifty kilometers per hour on UAV 220 . In such an example, UAV platform 230 may alter the flight path from an altitude of five-hundred meters to an altitude of one-thousand meters (e.g., if UAV 220 is capable of reaching the altitude of one-thousand meters).
- UAV platform 230 may 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.
- UAV platform 230 may calculate the flight path based on the air traffic information. For example, UAV platform 230 may determine that, without air traffic issues, the flight path may take UAV 220 two hours to complete at an altitude of five-hundred meters. UAV platform 230 may further determine that other UAVs 220 are flying at the altitude of five-hundred meters based on the air traffic information, but that no other UAVs 220 are flying at an altitude of one-thousand meters. In such an example, UAV platform 230 may 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 UAV 220 to safely arrive at the location without the possibility of colliding with the other UAVs 220 .
- UAV platform 230 may not alter the flight path, but the other UAVs 220 flying at the altitude of five-hundred meters may increase the possibility that UAV 220 may collide with another UAV 220 .
- UAV platform 230 may then determine whether UAV 220 is capable of safely flying at the altitude of five-hundred meters without colliding with another UAV 220 .
- UAV platform 230 may calculate the flight path based on the obstacle information. For example, UAV platform 230 may determine that, without obstacle issues, the flight path may take UAV 220 one hour to complete at an altitude of two-hundred meters. UAV platform 230 may 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 platform 230 may 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 UAV 220 to safely arrive at the location without the possibility of colliding with the one or more buildings. Alternatively. UAV platform 230 may 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.
- UAV platform 230 may calculate the flight path based on the regulatory information. For example, UAV platform 230 may determine that, without regulatory issues, the flight path may take UAV 220 one hour to complete at an altitude of five-hundred meters. UAV platform 230 may further determine that the flight path travels over a restricted facility based on the regulatory information. In such an example, UAV platform 230 may 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.
- UAV platform 230 may calculate the flight path based on the historical information. For example, UAV platform 230 may identify prior flight paths from the origination location to the destination location from the historical information, and may select one of the prior flight paths, as the flight path. For example, assume that UAV platform 230 identifies three prior flight paths that include flight times of two hours, three hours, and four hours, respectively. In such an example, UAV platform 230 may select, as the flight path, the prior flight path with the flight time of two hours.
- process 400 may include determining network requirements for the flight path based on the request for the flight path (block 415 ).
- UAV platform 230 may determine network requirements for the flight path based on the request for the flight path.
- UAV platform 230 may determine the network requirements based on the origination location, the destination location, and/or the particular region associated with the flight path.
- UAV platform 230 may determine that the flight path requires one or more of networks 240 - 260 at or near the origination location, the destination location, the particular region, etc. so that UAV 220 may communicate with UAV platform 230 .
- UAV platform 230 may determine that UAV 220 may communicate with UAV platform 230 , via wireless network 240 , during traversal of the flight path by UAV 220 . In another example, UAV platform 230 may determine that UAV 220 may communicate with UAV platform 230 via wireless network 240 during a portion of the flight path, may communicate with UAV platform 230 via satellite network 250 during another portion of the flight path, etc.
- UAV platform 230 may determine that the flight path requires utilization of a most reliable network or networks for communication with UAV 220 . For example, UAV platform 230 may determine that the flight path requires wireless network 240 (e.g., a cellular network), if wireless network 240 is available, since wireless network 240 may be more reliable than satellite network 250 and/or other networks 260 . If wireless network 240 is not available, UAV platform 230 may determine that the flight path requires satellite network 250 (e.g., a GPS network), if satellite network 250 is available, since satellite network 250 may be more reliable than other networks 260 .
- wireless network 240 e.g., a cellular network
- satellite network 250 e.g., a GPS network
- UAV platform 230 may determine that the flight path requires other networks 260 , such as a Wi-Fi network, a cellular network generated by a dedicated UAV 220 (e.g., a stationary UAV 220 , with a constant power source, that provides cellular coverage), a wireless network hotspot (e.g., a mobile hotspot), etc.
- networks 260 such as a Wi-Fi network, a cellular network generated by a dedicated UAV 220 (e.g., a stationary UAV 220 , with a constant power source, that provides cellular coverage), a wireless network hotspot (e.g., a mobile hotspot), etc.
- UAV platform 230 may determine that UAV 220 is to traverse flight path (e.g., without communicating with UAV platform 230 ) until UAV 220 enters an area covered by one of networks 240 - 260 . In some implementations, if multiple wireless networks 240 , satellite networks 250 , and/or other networks 260 are available, UAV platform 230 may determine that the flight path requires a most reliable of wireless networks 240 , satellite networks 250 , and/or other networks 260 .
- UAV platform 230 may determine that the flight path requires utilization of a least expensive network or networks for communication with UAV 220 . For example, UAV platform 230 may determine that the flight path requires other networks 260 (e.g., a Wi-Fi network), if other networks 260 are available, since other networks 260 may be less expensive to utilize than wireless network 240 and/or satellite network 250 . If other networks 260 are not available, UAV platform 230 may determine that the flight path requires satellite network 250 (e.g., a GPS network), if satellite network 250 is available, since satellite network 250 may be less expensive to utilize than wireless network 240 .
- networks 260 e.g., a Wi-Fi network
- satellite network 250 e.g., a GPS network
- UAV platform 230 may determine that the flight path requires wireless network 240 , such as a cellular network. In some implementations, if multiple wireless networks 240 , satellite networks 250 , and/or other networks 260 are available, UAV platform 230 may determine that the flight path requires a least expensive of wireless networks 240 , satellite networks 250 , and/or other networks 260 .
- UAV platform 230 may determine that the flight path requires utilization of a most secure network or networks for communication with UAV 220 . For example, UAV platform 230 may determine that the flight path requires wireless network 240 (e.g., a cellular network), if wireless network 240 is available, since wireless network 240 may be more secure than satellite network 250 and/or other networks 260 . If wireless network 240 is not available, UAV platform 230 may determine that the flight path requires satellite network 250 (e.g., a GPS network), if satellite network 250 is available, since satellite network 250 may be more secure than other networks 260 .
- wireless network 240 e.g., a cellular network
- satellite network 250 e.g., a GPS network
- UAV platform 230 may determine that the flight path requires other networks 260 (e.g., a Wi-Fi network, a cellular network generated by a dedicated UAV 220 , a mobile hotspot, etc.). In some implementations, if multiple wireless networks 240 , satellite networks 250 , and/or other networks 260 are available, UAV platform 230 may determine that the flight path requires a most secure of wireless networks 240 , satellite networks 250 , and/or other networks 260 .
- networks 260 e.g., a Wi-Fi network, a cellular network generated by a dedicated UAV 220 , a mobile hotspot, etc.
- UAV platform 230 may determine that the flight path requires utilization of a network or networks with a greatest bandwidth. For example, UAV platform 230 may determine that the flight path requires wireless network 240 (e.g., a cellular network), if wireless network 240 is available, since wireless network 240 may have a greater bandwidth than satellite network 250 and/or other networks 260 . If wireless network 240 is not available, UAV platform 230 may determine that the flight path requires satellite network 250 (e.g., a GPS network), if satellite network 250 is available, since satellite network 250 may have a greater bandwidth than other networks 260 .
- wireless network 240 e.g., a cellular network
- satellite network 250 e.g., a GPS network
- UAV platform 230 may determine that the flight path requires other networks 260 (e.g., a Wi-Fi network, a cellular network generated by a dedicated UAV 220 , a mobile hotspot, etc.). In some implementations, if multiple wireless networks 240 , satellite networks 250 , and/or other networks 260 are available, UAV platform 230 may determine that the flight path requires one of wireless networks 240 , satellite networks 250 , and/or other networks 260 with a greatest bandwidth.
- networks 260 e.g., a Wi-Fi network, a cellular network generated by a dedicated UAV 220 , a mobile hotspot, etc.
- UAV platform 230 may determine the network requirements based on components (e.g., sensors, network generating components, etc. of UAV 220 ) associated with UAV 220 . For example, UAV platform 230 may determine that UAV 220 is capable of communicating with wireless network 240 but not with satellite network 250 and/or other networks 260 (e.g., since UAV 220 only includes a component to communicate with wireless network 240 ). In such an example, UAV platform 230 may determine that satellite network 250 and/or other networks 260 do not satisfy the network requirements, but that wireless network 240 satisfies the network requirements. In another example, UAV platform 230 may determine that UAV 220 includes a GPS component that can communicate with satellite network 250 . In such an example, UAV platform 230 may determine that wireless network 240 and/or other networks 260 do not satisfy the network requirements, but that satellite network 250 satisfies the network requirements.
- components e.g., sensors, network generating components, etc. of UAV 220 .
- UAV platform 230 may determine the network requirements based on the aviation information associated with the particular region, such as the weather information, the air traffic information, the obstacle information, the regulatory information, the historical information, etc. associated with the particular region. For example, assume that the obstacle information indicates that the flight path requires UAV 220 to travel at an altitude of one kilometer. In such an example, UAV platform 230 may determine that the flight path requires a network (e.g., satellite network 250 ) that is capable of providing coverage at the one kilometer altitude. In another example, assume that the weather information indicates that the flight path requires UAV 220 to travel at an altitude of one-hundred meters to avoid strong headwinds. In such an example, UAV platform 230 may determine that the flight path requires a network (e.g., a Wi-Fi network) that is capable of providing coverage at the one-hundred meter altitude.
- a network e.g., a Wi-Fi network
- process 400 may include scoring available networks based on the network requirements (block 420 ).
- UAV platform 230 may retrieve, from data storage 235 , information associated with wireless network 240 , satellite network 250 , other networks 260 , etc.
- data storage 235 may include information associated with networks 240 - 260 , such as availability information, security information, cost information, bandwidth information, network resources information, etc. associated with networks 240 - 260 .
- UAV platform 230 may assign different weights to different information associated with networks 240 - 260 .
- UAV platform 230 may calculate a score for each of networks 240 - 260 based on the information associated with networks 240 - 260 and/or based on the assigned weights. For example, assume that UAV platform 230 assigns a weight of 0.1 to costs associated with networks 240 - 260 , a weight of 0.2 to security associated with networks 240 - 260 , and a weight of 0.5 to bandwidths associated with networks 240 - 260 . Further, assume that UAV platform 230 calculates a score of 0.4 for other networks 260 , a score of 0.7 for wireless network 240 , and a score of 0.5 for satellite network 250 based on the assigned weights.
- UAV platform 230 may select one or more networks to utilize for the flight path, and may identify a greatest or lowest score for the selected network(s) utilized during the flight path (e.g., an end-to-end flight path score). Each of the selected network(s) may include certain coverage area(s) which may (or may not) cover part of or all the flight path. In some implementations, UAV platform 230 may select a network or a combination of networks to cover as much of the flight path as possible, with a greatest (or lowest) score(s) for the selected network(s). In some implementations, the score(s) of the selected network(s) may be relative to different parts of the flight path.
- wireless network 240 might be the best network for one part of the flight path, but may be the worst network for another part of the flight path (e.g., even though wireless network 240 has coverage in both parts of the flight path).
- UAV platform 230 may select an initial network to utilize for the flight path, and may select one or more additional networks, to utilize for communications with UAV 220 , as UAV 220 traverses the flight path.
- process 400 may include ranking the available networks, based on the scores (block 425 ).
- UAV platform 230 may rank each of networks 240 - 260 based on a score calculated for each of networks 240 - 260 .
- UAV platform 230 may rank networks 240 - 260 based on the scores in ascending order, descending order, etc. For example, assume that UAV platform 230 calculates a score of 0.4 for other networks 260 , a score of 0.7 for wireless network 240 , and a score of 0.5 for satellite network 250 . In such an example, UAV platform 230 may rank networks 240 - 260 based on the scores, for example, as: (1) wireless network 240 , (2) satellite network 250 , and (3) other networks 260 .
- process 400 may include selecting a particular network, from the available networks, based on the rank (block 430 ).
- UAV platform 230 may select a particular network, from networks 240 - 260 , based on the rank associated with networks 240 - 260 .
- UAV platform 230 may select, as the particular network, a network with a greatest ranking. For example, assume that UAV platform 230 calculates a score of 0.4 for other networks 260 , a score of 0.7 for wireless network 240 , and a score of 0.5 for satellite network 250 .
- UAV platform 230 may rank networks 240 - 260 based on the scores (e.g., as (1) wireless network 240 , (2) satellite network 250 , and (3) other networks 260 ), and may select wireless network 240 as the particular network (e.g., via which to communicate with UAV 220 ) based on the ranking, since wireless network 240 has the greatest score.
- the scores e.g., as (1) wireless network 240 , (2) satellite network 250 , and (3) other networks 260
- wireless network 240 may select wireless network 240 as the particular network (e.g., via which to communicate with UAV 220 ) based on the ranking, since wireless network 240 has the greatest score.
- UAV platform 230 may not utilize the ranking of networks 240 - 260 , and may select the particular network, from networks 240 - 260 , based on the scores associated with networks 240 - 260 . For example, assume that UAV platform 230 calculates a score of 0.4 for other networks 260 , a score of 0.7 for wireless network 240 , and a score of 0.5 for satellite network 250 . In such an example, UAV platform 230 may select other networks 260 as the particular network (e.g., via which to communicate with UAV 220 ) since other networks 260 has the lowest score.
- process 400 may include generating flight path instructions that identify the selected network (block 435 ).
- UAV platform 230 may generate flight path instructions that identify the selected network (e.g., wireless network 240 ).
- the flight path instructions may include specific altitudes for UAV 220 between 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 network 240 via which UAV 220 may communicate with UAV platform 230 ); timing information (e.g., when to take off, when to perform certain navigational maneuvers, etc.); waypoint information (e.g., locations where UAV 220 may stop and recharge or refuel); etc.
- the flight path instructions may include information that instructs UAV 220 to fly forty-five degrees northeast for ten kilometers and at an altitude of five-hundred meters, then fly three-hundred and fifteen degrees northwest for ten kilometers and at an altitude of four-hundred meters, etc.
- the flight path instructions may include information instructing UAV 220 to connect to network X until UAV 220 reaches point A of the flight path, then connect to network Y until UAV 220 reaches point B of the flight path, and then connect back to network X for the remainder of the flight path.
- the flight path instructions may include information instructing UAV 220 to connect to network X until UAV 220 loses connectivity, and then connect to network Y for the remainder of the flight path.
- the flight path instructions may include information instructing UAV 220 to connect to network X until UAV 220 reaches point A of the flight path, and then keep trying to connect to network Y until successful.
- process 400 may include providing the flight path instructions to the UAV (block 440 ).
- UAV platform 230 may provide the flight path instructions to UAV 220 .
- UAV 220 may utilize the flight path instructions to travel via the flight path. For example, UAV 220 may 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 UAV 220 arrives at the destination location.
- UAV 220 may utilize information provided by the flight path instructions to calculate a flight path for UAV 220 and to generate flight path instructions.
- the flight path instructions provided by UAV platform 230 may include less detailed information, and UAV 220 may determine more detailed flight path instructions via the computational resources of UAV 220 .
- process 400 may include receiving network connectivity information from the UAV during traversal of the flight path by the UAV (block 445 ).
- UAV 220 and/or the selected network e.g., one or more of networks 240 - 260
- UAV platform 230 may receive the network connectivity information.
- the network connectivity information may include information associated with a connection between UAV 220 and the selected network.
- the network connectivity information may include information associated with signal strength between UAV 220 and the selected network, a bandwidth provided by the selected network to UAV 220 , etc.
- process 400 may include determining whether to select a new network based on the network connectivity information (block 450 ).
- UAV platform 230 may determine whether to select a new network for communicating with UAV 220 based on the network connectivity information.
- UAV platform 230 may determine to not select a new network if the network connectivity information indicates that UAV 220 will continue to communicate with UAV platform 230 via the selected network.
- UAV platform 230 may determine to select a new network if the network connectivity information indicates that UAV 220 is losing or will lose a signal received from the selected network (e.g., UAV 220 will not be able to communicate with UAV platform 230 ).
- UAV platform 230 may select a new network so that UAV 220 may continue to communicate with UAV platform 230 via the new network. For example, assume that UAV 220 is communicating with UAV platform 230 via wireless network 240 , but is about to fly out of a range of wireless network 240 . Further, assume that UAV 220 is flying in a range of satellite network 250 . In such an example, UAV platform 230 may instruct UAV 220 to disconnect from wireless network 240 and to connect with satellite network 250 so that UAV 220 may communicate with UAV platform 230 via satellite network 250 .
- process 400 may include selecting the new network based on the network connectivity information (block 455 ). For example, if UAV platform 230 determines that a new network is to be selected, UAV platform 230 may select a new network based on the network connectivity information (e.g., as described above). In some implementations, if the selected network is wireless network 240 , the new network may include another wireless network 240 , satellite network 250 , and/or one or more of other networks 260 . In some implementations, the new network may enable UAV 220 to communicate with UAV platform 230 . In some implementations.
- UAV platform 230 may generate modified flight path instructions, which include information associated with the new network, based on the network connectivity information.
- the modified flight path instructions may include the features of flight path instructions, but may be modified based on the network connectivity information.
- the flight path instructions may be modified to instruct UAV 220 to disconnect from wireless network 240 and connect with satellite network 250 .
- process 400 may include providing information associated with the new network to the UAV (block 460 ).
- UAV platform 230 may provide, to UAV 220 , information associated with the new network, such as a system identification code (SID), security information, bandwidth information, etc. associated with the new network.
- SID system identification code
- UAV platform 230 may provide the information associated with the new network via the modified flight path instructions.
- UAV 220 may utilize the information associated with the new network to connect with the new network and to communicate with UAV platform 230 .
- UAV 220 may instruct the selected network to handover communication to the new network (e.g., so that UAV 220 may continuously communicate with UAV platform 230 ) until UAV 220 arrives at the destination location.
- UAV 220 may continue to provide further network connectivity information to UAV platform 230 during traversal of the flight path, and UAV platform 230 may or may not select another new network based on the further network connectivity information.
- process 400 may include receiving a notification that the UAV arrived at the second location (block 465 ). For example, if the network connectivity information indicates that UAV 220 may still communicate with UAV platform 230 via the selected network. UAV platform 230 may determine that the new network need not be selected. In some implementations, UAV 220 may continue to communicate with UAV platform 230 , via the selected network, if a new network is not selected. In some implementations, UAV 220 may continue along the flight path based on the flight path instructions until UAV 220 arrives at the destination location.
- UAV 220 may provide a notification to UAV platform 230 , via one or more of networks 240 - 260 .
- the notification may indicate that UAV 220 has safely arrived at the destination location.
- process 400 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIGS. 4A and 4B . Additionally, or alternatively, two or more of the blocks of process 400 may be performed in parallel.
- FIGS. 5A-5E are diagrams of an example 500 relating to example process 400 shown in FIGS. 4A and 4B .
- a first user device 210 e.g., a tablet 210
- a first user e.g., an employee at a delivery company
- an origination location e.g., Washington, D.C.
- a second user device 210 e.g., a computer 210
- a second user e.g., Bob
- a destination location e.g., Fairfax, Va.
- computer 210 may inform tablet 210 (e.g., via one or more servers associated with the delivery company) and the employee that the package is to be delivered to Bob as soon as possible. Further, assume that the employee wants to utilize UAV 220 to fly the package from Washington, D.C. to Fairfax, Va. in order to deliver the package to Bob.
- UAV platform 230 and data storage 235 may communicate with wireless network 240 , satellite network 250 , and/or other networks 260 .
- networks 240 - 260 may provide, to data storage 235 , information 505 , such as capability information associated with UAV 220 , 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.
- information 505 such as capability information associated with UAV 220 , 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.
- the employee may instruct tablet 210 to generate a request 510 for a flight path (e.g., from Washington, D.C. to Fairfax, Va.) for UAV 220 , and to provide request 510 to UAV platform 230 .
- Request 510 may include credentials (e.g., a serial number, an identifier of a UICC, etc.) associated with UAV 220 , or the credentials may be provided separately from request 510 to UAV platform 230 .
- UAV platform 230 may utilize the credentials to determine whether UAV 220 is authenticated for utilizing UAV platform 230 and/or one or more of networks 240 - 260 , and is registered with an appropriate authority for use.
- UAV platform 230 may compare the credentials with information provided in data storage 235 in order to determine whether UAV 220 is authenticated for utilizing UAV platform 230 and/or one or more of networks 240 - 260 , and is registered with an appropriate authority. Assume that UAV 220 is authenticated and/or registered.
- UAV platform 230 may calculate a flight path from Washington, D.C. to Fairfax, Va. based on information 505 (e.g., weather information, air traffic information, obstacle information, regulatory information, historical information, etc.) provided in data storage 235 .
- information 505 e.g., weather information, air traffic information, obstacle information, regulatory information, historical information, etc.
- the weather information indicates that the wind is ten kilometers per hour from the west and that it is raining
- the air traffic information indicates that a jet is at an altitude of ten-thousand meters and another UAV 220 is at an altitude of five-hundred meters
- the obstacle information indicates that a mountain is two kilometers in height and a building is five-hundred meters in height
- the regulatory information indicates that there is a no-fly zone over a government building
- the historical information indicates that a historical flight path had a duration of thirty minutes and an altitude of one-thousand meters.
- UAV platform 230 may calculate the flight path from Washington, D
- UAV platform 230 may determine network requirements 515 for the requested flight path based on request 510 . For example, UAV platform 230 may determine that network requirements 515 include UAV 220 utilizing one or more of networks 240 - 260 to communicate with UAV platform 230 during the flight path. UAV platform 230 may provide network requirements 515 to data storage 235 (e.g., for storage).
- data storage 235 e.g., for storage
- UAV platform 230 may assign different weights to different information associated with available networks (e.g., networks 240 - 260 ), and may calculate a score for each network based on the assigned weights and/or based on network requirements 515 .
- UAV platform 230 may rank the networks based on the scores, and may provide the ranking and the scores of the networks to data storage 235 (e.g., for storage). Assume that UAV platform 230 ranks wireless network 240 the highest based on the calculated scores.
- UAV platform 230 may retrieve the ranking and the scores of the networks from data storage 235 , as indicated by reference number 520 in FIG. 5B .
- UAV platform 230 may select a particular network (e.g., wireless network 240 ), from the networks, based on the ranking and/or based on network requirements 515 , as indicated by reference number 525 .
- a particular network e.g., wireless network 240
- UAV 220 may connect 530 with wireless network 240 based on the selection of wireless network 240 as the particular network.
- UAV 220 may communicate with UAV platform 230 via wireless network 240 .
- the calculated flight path from Washington, D.C. to Fairfax, Va. may be depicted by reference number 535 in FIG. 5C .
- UAV platform 230 may generate flight path instructions 540 for flight path 535 .
- Flight path instructions 540 may include, for example, information instructing UAV 220 to fly north at zero degrees for ten kilometers, then northeast at forty degrees for three kilometers, at an altitude of one-thousand meters, etc.
- UAV platform 230 may provide flight path instructions 540 to UAV 220 via wireless network 240 .
- the package may be attached to or provided in UAV 220 (e.g., by the employee).
- UAV 220 may take off from Washington, D.C. with the package, and may travel flight path 535 based on flight path instructions 540 .
- UAV 220 and/or wireless network 240 may provide network connectivity information 545 to UAV platform 230 , as shown in FIG. 5D .
- UAV 220 is flying out of range of wireless network 240 , and provides, to UAV platform 230 , information indicating that UAV 220 is losing connectivity with wireless network 240 (e.g., via network connectivity information 545 ).
- UAV platform 230 may select a new network 550 that enables UAV 220 to communicate with UAV platform 230 .
- UAV platform 230 selects satellite network 250 as new network 550 , and instructs wireless network 250 to handover 555 communications with UAV 220 to satellite network 250 .
- UAV 220 may connect 560 with satellite network 250 , based on the selection of satellite network 250 , and may communicate with UAV platform 230 via satellite network 250 . While communications are being switched from wireless network 240 to satellite network 250 , UAV 220 may continue to travel along flight path 535 until UAV 220 arrives at Fairfax, Va.
- UAV 220 may leave the package at a location where Bob may retrieve the package.
- UAV 220 and/or computer 210 e.g., via Bob's input or detection of the presence of UAV 220 ) may generate a notification 565 indicating that UAV 220 and the package arrived safely at a particular location in Fairfax, Va., and may provide notification 565 to UAV platform 230 .
- UAV 220 receives flight path instructions 540 , for flight path 535 , from UAV platform 230 . Further, assume that flight path instructions 540 instruct UAV 220 to connect to a cellular network 240 - 1 , and that UAV 220 connects 570 with cellular network 240 - 1 based on flight path instructions 540 . UAV 220 may take off from Washington, D.C. with the package, and may travel flight path 535 based on flight path instructions 540 . UAV 220 may communicate with UAV platform 230 , via cellular network 240 - 1 , for a portion of flight path 535 . As further shown in FIG.
- UAV 220 may disconnect from cellular network 240 - 1 at a particular point of flight path 535 , and may connect 575 with a UAV-generated cellular network 240 - 2 .
- UAV 220 may communicate with UAV platform 230 , via UAV-generated cellular network 240 - 2 , for another portion of flight path 535 .
- UAV 220 may disconnect from UAV-generated cellular network 240 - 2 at another particular point of flight path 535 , and may connect 580 with a Wi-Fi network 260 .
- UAV 220 may communicate with UAV platform 230 , via Wi-Fi network 260 , for a final portion of flight path 535 .
- FIGS. 5A-5E are provided merely as an example. Other examples are possible and may differ from what was described with regard to FIGS. 5A-5E .
- 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 enable UAVs to seamlessly connect with the platform via various networks, which may ensure that the platform continuously communicates with the UAVs.
- the systems and/or methods may enable the platform to select a network for communicating with the UAV, and the selected network may reduce connectivity costs, increase security of communications, reduce the need for handoffs to other networks, offer the best connectivity, or the like.
- 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.
- GUIs graphical user 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.).
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Aviation & Aerospace Engineering (AREA)
- Remote Sensing (AREA)
- Radar, Positioning & Navigation (AREA)
- Business, Economics & Management (AREA)
- Computer Networks & Wireless Communication (AREA)
- Economics (AREA)
- Quality & Reliability (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Operations Research (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Development Economics (AREA)
- Atmospheric Sciences (AREA)
- Emergency Management (AREA)
- Astronomy & Astrophysics (AREA)
- Life Sciences & Earth Sciences (AREA)
- Electromagnetism (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Traffic Control Systems (AREA)
- Automation & Control Theory (AREA)
- Navigation (AREA)
Abstract
Description
- This application is a continuation of pending U.S. patent application Ser. No. 15/657,668, filed Jul. 24, 2017, which is a continuation of U.S. patent application Ser. No. 14/282,378, filed May 20, 2014, now U.S. Pat. No. 9,881,022, issued Jan. 30, 2018, all of which are hereby incorporated by reference in their entirety.
- 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.
-
FIGS. 1A and 1B are diagrams of an overview of an example implementation described herein; -
FIG. 2 is a diagram of an example environment in which systems and/or methods described herein may be implemented; -
FIG. 3 is a diagram of example components of one or more devices ofFIG. 2 ; -
FIGS. 4A and 4B depict a flow chart of an example process for selecting a network for communicating with a UAV during traversal of a flight path; and -
FIGS. 5A-5E are diagrams of an example relating to the example process shown inFIGS. 4A and 4B . - The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements.
- 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 1B are diagrams of an overview of anexample implementation 100 described herein. Inexample implementation 100, 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 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 the UAV (e.g., a thrust, a battery life, etc. associated with the UAV); 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 in
FIG. 1A , user A may instruct user device A 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., serial numbers, identifiers of universal integrated circuit cards (UICCs), 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. Inexample implementation 100, assume that the UAV is authenticated by the UAV platform. - The UAV platform may calculate a flight path from location A to location B based on aviation information (e.g., the weather information, the air traffic information, etc.) associated with the geographical region. The UAV platform may track the flight path of the UAV based on the UAV's continuous connectivity to a network (e.g., the wireless network, the satellite network, etc.), but may lose connectivity with the UAV when the UAV travels outside a range of the network. As further shown in
FIG. 1A , the UAV platform may determine network requirements for the flight path based on the request for the flight path. For example, the UAV platform may determine that the UAV is to connect to a cheapest network, a network with the greatest security, a network with the most bandwidth, etc. during traversal of the flight path. The UAV platform may assign different weights to different available networks (e.g., the wireless network, the satellite network, etc.), and may calculate a score for each of the available networks based on the network requirements and the assigned weights. The UAV platform may rank the available networks based on the scores (e.g., in ascending order, descending order, etc.), and may store the scores and the rankings for the available networks in the data storage. The UAV platform may retrieve the scores and the rankings for the available networks from the data storage, as further shown inFIG. 1A . - The UAV platform may select a particular network based on the scores and the rankings for the available networks. For example, the UAV platform may select the wireless network as the network to which the UAV is to connect based on the scores and the rankings for the available networks since the wireless network may be less expensive to utilize than the satellite network and the other networks. As further shown in
FIG. 1A the UAV may connect to the wireless network based on the selection of the wireless network (e.g., as the particular network). - After selecting the wireless network, the UAV platform may generate flight path instructions for the flight path, as shown in
FIG. 1B . 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, in order to arrive at location B. The UAV platform may provide the flight path instructions to the UAV (e.g., via the wireless network), as further shown inFIG. 1B . - The UAV may take off from location A, and may travel the flight path based on the flight path instructions. While the UAV is traversing the flight path, the wireless network may receive and/or generate network connectivity information associated with the UAV (e.g., about changing conditions, such as the UAV flying out of range of the wireless network, etc.). The wireless network may provide the network connectivity information to the UAV platform, and the UAV platform may select a new network, to which the UAV is to connect, based on the network connectivity information. For example, the UAV platform may select the satellite network as the new network, and may instruct the UAV to connect to the satellite network based on the selection. As further shown in
FIG. 1B , the UAV may connect to the satellite network, and may continue to traverse the flight path (e.g., while connected to the satellite network) until the UAV arrives at location B. When the UAV arrives at location B, the UAV and/or user device B may generate a notification indicating that the UAV arrived safely at location 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 enable UAVs to seamlessly connect with the platform via various networks, which may ensure that the platform continuously communicates with the UAVs. The systems and/or methods may enable the platform to select a network for communicating with the UAV, and the selected network may reduce connectivity costs, increase security of communications, reduce the need for handoffs to other networks, offer the best connectivity, or the like.
-
FIG. 2 is a diagram of anexample environment 200 in which systems and/or methods described herein may be implemented. As illustrated,environment 200 may includeuser devices 210,UAVs 220, aUAV platform 230,data storage 235, awireless network 240, asatellite network 250, andother networks 260. Devices/networks ofenvironment 200 may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections. -
User device 210 may include a device that is capable of communicating overwireless network 240 withUAV 220,UAV platform 230, and/ordata storage 235. In some implementations,user device 210 may 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. -
UAV 220 may 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,UAV 220 may include a variety of shapes, sizes, configurations, characteristics, etc. for a variety of purposes and applications. In some implementations,UAV 220 may 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,UAV 220 may utilize one or more of the aforementioned sensors to sense (or detect) and avoid an obstacle in or near a flight path ofUAV 220. - In some implementations,
UAV 220 may include a particular degree of autonomy based on computational resources provided inUAV 220. For example,UAV 220 may include a low degree of autonomy whenUAV 220 has few computational resources. In another example,UAV 220 may include a high degree of autonomy whenUAV 220 has 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 ofUAV 220 may combine information from different sensors to detect obstacles on the ground or in the air; communicate with one or more of networks 240-260 and/orother UAVs 220; determine an optimal flight path forUAV 220 based 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 ofUAV 220; etc. In some implementations,UAV 220 may 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 platform 230 may 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 platform 230 may be associated with a service provider that manages and/or operateswireless network 240,satellite network 250, and/orother networks 260, such as, for example, a telecommunication service provider, a television service provider, an Internet service provider, etc. - In some implementations,
UAV platform 230 may receive, fromuser device 210, a request for a flight path from an origination location to a destination location.UAV platform 230 may calculate the flight path from the origination location to the destination location based on aviation information (e.g., weather information, air traffic information, etc.), and may determine network requirements for the flight path based on the request for the flight path.UAV platform 230 may assign different weights to different networks (e.g.,wireless network 240,satellite network 250, etc.) available toUAV 220, and may calculate a score for each network based on the network requirements and/or the assigned weights.UAV platform 230 may rank the available networks based on the scores (e.g., in ascending order, descending order, etc.), and may select a particular network, from the available networks, based on the ranks and/or based on the network requirements for the flight path. After selecting the network,UAV platform 230 may generate flight path instructions that identify the selected network, and may provide the flight path instructions toUAV 220.UAV 220 may connect to the selected network, based on the flight path instructions, so thatUAV 220 may communicate withUAV platform 230.UAV platform 230 may receive network connectivity information fromUAV 220 during traversal of the flight path byUAV 220.UAV platform 230 may select a new network based on the network connectivity information, and may provide information associated with the new network to UAV 220 (e.g., so thatUAV 220 may connect with the new network).UAV platform 230 may receive a notification thatUAV 220 arrived at the destination location whenUAV 220 lands at the destination location. - In some implementations,
UAV platform 230 may authenticate one or more users, associated withuser device 210 and/orUAV 220, for utilizingUAV platform 230, and may securely store authentication information associated with the one or more users. In some implementations,UAV platform 230 may adhere to requirements to ensure thatUAVs 220 safely traverse flight paths, and may limit the flight paths ofUAVs 220 to particular safe zones (e.g., particular altitudes, particular geographical locations, particular geo-fencing, etc.) to further ensure safety. -
Data storage 235 may 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 storage 235 may store information, such as UAV account information (e.g., serial numbers, model numbers, user names, etc. associated with UAVs 220); capability information associated with UAVs 220 (e.g., thrust, battery life, etc. associated with UAVs 220); 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 UAVs 220, 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 storage 235 may be included withinUAV platform 230. -
Wireless network 240 may 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 allowuser devices 210 and/orUAVs 220 to 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 network 240 may provide location information (e.g., latitude and longitude coordinates) associated withuser devices 210 and/orUAVs 220. For example,wireless network 240 may determine a location ofuser device 210 and/orUAV 220 based on triangulation of signals, generated byuser device 210 and/orUAV 220 and received by multiple cell towers, with prior knowledge of the cell tower locations. -
Satellite network 250 may 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 network 250 may provide location information (e.g., GPS coordinates) associated withuser devices 210 and/orUAVs 220, enable communication withuser devices 210 and/orUAVs 220, etc. - Each of
other networks 260 may 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 in
FIG. 2 is 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. 2 may be implemented within a single device, or a single device shown inFIG. 2 may be implemented as multiple, distributed devices. Additionally, one or more of the devices ofenvironment 200 may perform one or more functions described as being performed by another one or more devices ofenvironment 200. -
FIG. 3 is a diagram of example components of adevice 300 that may correspond to one or more of the devices ofenvironment 200. In some implementations, one or more of the devices ofenvironment 200 may include one ormore devices 300 or one or more components ofdevice 300. As shown inFIG. 3 ,device 300 may include a bus 310, aprocessor 320, amemory 330, astorage component 340, aninput component 350, anoutput component 360, and acommunication interface 370. - Bus 310 may include a component that permits communication among the components of
device 300.Processor 320 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), etc.), a microprocessor, and/or any processing component (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.) that interprets and/or executes instructions.Memory 330 may include a random access memory (RAM), a read only memory (ROM), and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, an optical memory, etc.) that stores information and/or instructions for use byprocessor 320. -
Storage component 340 may store information and/or software related to the operation and use ofdevice 300. For example,storage component 340 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, etc.), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of computer-readable medium, along with a corresponding drive. -
Input component 350 may include a component that permitsdevice 300 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, a microphone, etc.). Additionally, or alternatively,input component 350 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.).Output component 360 may include a component that provides output information from device 300 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.). -
Communication interface 370 may include a transceiver-like component (e.g., a transceiver, a separate receiver and transmitter, etc.) that enablesdevice 300 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections.Communication interface 370 may permitdevice 300 to receive information from another device and/or provide information to another device. For example,communication interface 370 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, or the like. -
Device 300 may perform one or more processes described herein.Device 300 may perform these processes in response toprocessor 320 executing software instructions stored by a computer-readable medium, such asmemory 330 and/orstorage component 340. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices. - Software instructions may be read into
memory 330 and/orstorage component 340 from another computer-readable medium or from another device viacommunication interface 370. When executed, software instructions stored inmemory 330 and/orstorage component 340 may causeprocessor 320 to perform one or more processes described herein. Additionally, or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software. - The number and arrangement of components shown in
FIG. 3 is provided as an example. In practice,device 300 may include additional components, fewer components, different components, or differently arranged components than those shown inFIG. 3 . Additionally, or alternatively, a set of components (e.g., one or more components) ofdevice 300 may perform one or more functions described as being performed by another set of components ofdevice 300. -
FIGS. 4A and 4B depict a flow chart of anexample process 400 for selecting a network for communicating with a UAV during traversal of a flight path. In some implementations, one or more process blocks ofFIGS. 4A and 4B may be performed byUAV platform 230. In some implementations, one or more process blocks ofFIGS. 4A and 4B may be performed by another device or a group of devices separate from or includingUAV platform 230, such asuser device 210 and/orUAV 220. - As shown in
FIG. 4A ,process 400 may include receiving a request for a flight path from a first location to a second location in a region (block 405). For example,UAV platform 230 may receive, fromuser device 210, a request for a flight path from a first location to a second location in a particular region. 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 UAV 220) 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,UAV 220 may be associated withUAV platform 230 and/or user(s) associated withuser device 210. For example,user device 210 andUAV 220 may be owned and/or operated by a delivery company, a telecommunication service provider, a television service provider, an Internet service provider, etc. - As further shown in
FIG. 4A ,process 400 may include calculating the flight path from the first location to the second location based on aviation information (block 410). For example,UAV platform 230 may calculate the flight path from the origination location to the destination location based on aviation information. In some implementations,UAV platform 230 may calculate the flight path from the origination location to the destination location based on aviation information associated with the particular region, such as the weather information, the air traffic information, the obstacle information, the regulatory information, the historical information, etc. stored inUAV platform 230 and/ordata storage 235. In some implementations,UAV platform 230 may determine whether the aviation information indicates thatUAV 220 may safely complete the flight path from the origination location to the destination location without stopping. IfUAV platform 230 determines thatUAV 220 cannot safely complete the flight path from the origination location to the destination location without stopping (e.g., to recharge or refuel),UAV platform 230 may determine one or more waypoints along the flight path for stopping and recharging or refueling. - In some implementations,
UAV platform 230 may calculate the flight path based on the weather information. For example,UAV platform 230 may determine that, without weather issues, the flight path may takeUAV 220 two hours to complete at an altitude of five-hundred meters.UAV platform 230 may further determine that wind conditions at five-hundred meters may create a headwind of fifty kilometers per hour onUAV 220, but that wind conditions at one-thousand meters may create a tailwind of fifty kilometers per hour onUAV 220. In such an example,UAV platform 230 may alter the flight path from an altitude of five-hundred meters to an altitude of one-thousand meters (e.g., ifUAV 220 is 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 platform 230 may 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 platform 230 may calculate the flight path based on the air traffic information. For example,UAV platform 230 may determine that, without air traffic issues, the flight path may takeUAV 220 two hours to complete at an altitude of five-hundred meters.UAV platform 230 may further determine thatother UAVs 220 are flying at the altitude of five-hundred meters based on the air traffic information, but that noother UAVs 220 are flying at an altitude of one-thousand meters. In such an example,UAV platform 230 may 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 enableUAV 220 to safely arrive at the location without the possibility of colliding with theother UAVs 220. Alternatively,UAV platform 230 may not alter the flight path, but theother UAVs 220 flying at the altitude of five-hundred meters may increase the possibility thatUAV 220 may collide with anotherUAV 220.UAV platform 230 may then determine whetherUAV 220 is capable of safely flying at the altitude of five-hundred meters without colliding with anotherUAV 220. - Additionally, or alternatively.
UAV platform 230 may calculate the flight path based on the obstacle information. For example,UAV platform 230 may determine that, without obstacle issues, the flight path may takeUAV 220 one hour to complete at an altitude of two-hundred meters.UAV platform 230 may 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 platform 230 may 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 enableUAV 220 to safely arrive at the location without the possibility of colliding with the one or more buildings. Alternatively.UAV platform 230 may 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 platform 230 may calculate the flight path based on the regulatory information. For example,UAV platform 230 may determine that, without regulatory issues, the flight path may takeUAV 220 one hour to complete at an altitude of five-hundred meters.UAV platform 230 may further determine that the flight path travels over a restricted facility based on the regulatory information. In such an example,UAV platform 230 may 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 platform 230 may calculate the flight path based on the historical information. For example,UAV platform 230 may identify prior flight paths from the origination location to the destination location from the historical information, and may select one of the prior flight paths, as the flight path. For example, assume thatUAV platform 230 identifies three prior flight paths that include flight times of two hours, three hours, and four hours, respectively. In such an example,UAV platform 230 may select, as the flight path, the prior flight path with the flight time of two hours. - As further shown in
FIG. 4A ,process 400 may include determining network requirements for the flight path based on the request for the flight path (block 415). For example,UAV platform 230 may determine network requirements for the flight path based on the request for the flight path. In some implementations,UAV platform 230 may determine the network requirements based on the origination location, the destination location, and/or the particular region associated with the flight path. For example,UAV platform 230 may determine that the flight path requires one or more of networks 240-260 at or near the origination location, the destination location, the particular region, etc. so thatUAV 220 may communicate withUAV platform 230. In such an example,UAV platform 230 may determine thatUAV 220 may communicate withUAV platform 230, viawireless network 240, during traversal of the flight path byUAV 220. In another example,UAV platform 230 may determine thatUAV 220 may communicate withUAV platform 230 viawireless network 240 during a portion of the flight path, may communicate withUAV platform 230 viasatellite network 250 during another portion of the flight path, etc. - In some implementations,
UAV platform 230 may determine that the flight path requires utilization of a most reliable network or networks for communication withUAV 220. For example,UAV platform 230 may determine that the flight path requires wireless network 240 (e.g., a cellular network), ifwireless network 240 is available, sincewireless network 240 may be more reliable thansatellite network 250 and/orother networks 260. Ifwireless network 240 is not available,UAV platform 230 may determine that the flight path requires satellite network 250 (e.g., a GPS network), ifsatellite network 250 is available, sincesatellite network 250 may be more reliable thanother networks 260. Ifwireless network 240 andsatellite network 250 are not available,UAV platform 230 may determine that the flight path requiresother networks 260, such as a Wi-Fi network, a cellular network generated by a dedicated UAV 220 (e.g., astationary UAV 220, with a constant power source, that provides cellular coverage), a wireless network hotspot (e.g., a mobile hotspot), etc. - In some implementations, if none of networks 240-260 are available,
UAV platform 230 may determine thatUAV 220 is to traverse flight path (e.g., without communicating with UAV platform 230) untilUAV 220 enters an area covered by one of networks 240-260. In some implementations, ifmultiple wireless networks 240,satellite networks 250, and/orother networks 260 are available,UAV platform 230 may determine that the flight path requires a most reliable ofwireless networks 240,satellite networks 250, and/orother networks 260. - In some implementations,
UAV platform 230 may determine that the flight path requires utilization of a least expensive network or networks for communication withUAV 220. For example,UAV platform 230 may determine that the flight path requires other networks 260 (e.g., a Wi-Fi network), ifother networks 260 are available, sinceother networks 260 may be less expensive to utilize thanwireless network 240 and/orsatellite network 250. Ifother networks 260 are not available,UAV platform 230 may determine that the flight path requires satellite network 250 (e.g., a GPS network), ifsatellite network 250 is available, sincesatellite network 250 may be less expensive to utilize thanwireless network 240. Ifsatellite network 250 andother networks 260 are not available,UAV platform 230 may determine that the flight path requireswireless network 240, such as a cellular network. In some implementations, ifmultiple wireless networks 240,satellite networks 250, and/orother networks 260 are available,UAV platform 230 may determine that the flight path requires a least expensive ofwireless networks 240,satellite networks 250, and/orother networks 260. - In some implementations,
UAV platform 230 may determine that the flight path requires utilization of a most secure network or networks for communication withUAV 220. For example,UAV platform 230 may determine that the flight path requires wireless network 240 (e.g., a cellular network), ifwireless network 240 is available, sincewireless network 240 may be more secure thansatellite network 250 and/orother networks 260. Ifwireless network 240 is not available,UAV platform 230 may determine that the flight path requires satellite network 250 (e.g., a GPS network), ifsatellite network 250 is available, sincesatellite network 250 may be more secure thanother networks 260. Ifwireless network 240 andsatellite network 250 are not available,UAV platform 230 may determine that the flight path requires other networks 260 (e.g., a Wi-Fi network, a cellular network generated by adedicated UAV 220, a mobile hotspot, etc.). In some implementations, ifmultiple wireless networks 240,satellite networks 250, and/orother networks 260 are available,UAV platform 230 may determine that the flight path requires a most secure ofwireless networks 240,satellite networks 250, and/orother networks 260. - In some implementations,
UAV platform 230 may determine that the flight path requires utilization of a network or networks with a greatest bandwidth. For example,UAV platform 230 may determine that the flight path requires wireless network 240 (e.g., a cellular network), ifwireless network 240 is available, sincewireless network 240 may have a greater bandwidth thansatellite network 250 and/orother networks 260. Ifwireless network 240 is not available,UAV platform 230 may determine that the flight path requires satellite network 250 (e.g., a GPS network), ifsatellite network 250 is available, sincesatellite network 250 may have a greater bandwidth thanother networks 260. Ifwireless network 240 andsatellite network 250 are not available,UAV platform 230 may determine that the flight path requires other networks 260 (e.g., a Wi-Fi network, a cellular network generated by adedicated UAV 220, a mobile hotspot, etc.). In some implementations, ifmultiple wireless networks 240,satellite networks 250, and/orother networks 260 are available,UAV platform 230 may determine that the flight path requires one ofwireless networks 240,satellite networks 250, and/orother networks 260 with a greatest bandwidth. - In some implementations,
UAV platform 230 may determine the network requirements based on components (e.g., sensors, network generating components, etc. of UAV 220) associated withUAV 220. For example,UAV platform 230 may determine thatUAV 220 is capable of communicating withwireless network 240 but not withsatellite network 250 and/or other networks 260 (e.g., sinceUAV 220 only includes a component to communicate with wireless network 240). In such an example,UAV platform 230 may determine thatsatellite network 250 and/orother networks 260 do not satisfy the network requirements, but thatwireless network 240 satisfies the network requirements. In another example,UAV platform 230 may determine thatUAV 220 includes a GPS component that can communicate withsatellite network 250. In such an example,UAV platform 230 may determine thatwireless network 240 and/orother networks 260 do not satisfy the network requirements, but thatsatellite network 250 satisfies the network requirements. - In some implementations,
UAV platform 230 may determine the network requirements based on the aviation information associated with the particular region, such as the weather information, the air traffic information, the obstacle information, the regulatory information, the historical information, etc. associated with the particular region. For example, assume that the obstacle information indicates that the flight path requiresUAV 220 to travel at an altitude of one kilometer. In such an example,UAV platform 230 may determine that the flight path requires a network (e.g., satellite network 250) that is capable of providing coverage at the one kilometer altitude. In another example, assume that the weather information indicates that the flight path requiresUAV 220 to travel at an altitude of one-hundred meters to avoid strong headwinds. In such an example,UAV platform 230 may determine that the flight path requires a network (e.g., a Wi-Fi network) that is capable of providing coverage at the one-hundred meter altitude. - As further shown in
FIG. 4A ,process 400 may include scoring available networks based on the network requirements (block 420). For example,UAV platform 230 may retrieve, fromdata storage 235, information associated withwireless network 240,satellite network 250,other networks 260, etc. In some implementations,data storage 235 may include information associated with networks 240-260, such as availability information, security information, cost information, bandwidth information, network resources information, etc. associated with networks 240-260. In some implementations,UAV platform 230 may assign different weights to different information associated with networks 240-260. In some implementations,UAV platform 230 may calculate a score for each of networks 240-260 based on the information associated with networks 240-260 and/or based on the assigned weights. For example, assume thatUAV platform 230 assigns a weight of 0.1 to costs associated with networks 240-260, a weight of 0.2 to security associated with networks 240-260, and a weight of 0.5 to bandwidths associated with networks 240-260. Further, assume thatUAV platform 230 calculates a score of 0.4 forother networks 260, a score of 0.7 forwireless network 240, and a score of 0.5 forsatellite network 250 based on the assigned weights. - In some implementations,
UAV platform 230 may select one or more networks to utilize for the flight path, and may identify a greatest or lowest score for the selected network(s) utilized during the flight path (e.g., an end-to-end flight path score). Each of the selected network(s) may include certain coverage area(s) which may (or may not) cover part of or all the flight path. In some implementations,UAV platform 230 may select a network or a combination of networks to cover as much of the flight path as possible, with a greatest (or lowest) score(s) for the selected network(s). In some implementations, the score(s) of the selected network(s) may be relative to different parts of the flight path. For example,wireless network 240 might be the best network for one part of the flight path, but may be the worst network for another part of the flight path (e.g., even thoughwireless network 240 has coverage in both parts of the flight path). In some implementations,UAV platform 230 may select an initial network to utilize for the flight path, and may select one or more additional networks, to utilize for communications withUAV 220, asUAV 220 traverses the flight path. - As further shown in
FIG. 4A ,process 400 may include ranking the available networks, based on the scores (block 425). For example,UAV platform 230 may rank each of networks 240-260 based on a score calculated for each of networks 240-260. In some implementations,UAV platform 230 may rank networks 240-260 based on the scores in ascending order, descending order, etc. For example, assume thatUAV platform 230 calculates a score of 0.4 forother networks 260, a score of 0.7 forwireless network 240, and a score of 0.5 forsatellite network 250. In such an example,UAV platform 230 may rank networks 240-260 based on the scores, for example, as: (1)wireless network 240, (2)satellite network 250, and (3)other networks 260. - As further shown in
FIG. 4A ,process 400 may include selecting a particular network, from the available networks, based on the rank (block 430). For example,UAV platform 230 may select a particular network, from networks 240-260, based on the rank associated with networks 240-260. In some implementations,UAV platform 230 may select, as the particular network, a network with a greatest ranking. For example, assume thatUAV platform 230 calculates a score of 0.4 forother networks 260, a score of 0.7 forwireless network 240, and a score of 0.5 forsatellite network 250. In such an example,UAV platform 230 may rank networks 240-260 based on the scores (e.g., as (1)wireless network 240, (2)satellite network 250, and (3) other networks 260), and may selectwireless network 240 as the particular network (e.g., via which to communicate with UAV 220) based on the ranking, sincewireless network 240 has the greatest score. - In some implementations,
UAV platform 230 may not utilize the ranking of networks 240-260, and may select the particular network, from networks 240-260, based on the scores associated with networks 240-260. For example, assume thatUAV platform 230 calculates a score of 0.4 forother networks 260, a score of 0.7 forwireless network 240, and a score of 0.5 forsatellite network 250. In such an example,UAV platform 230 may selectother networks 260 as the particular network (e.g., via which to communicate with UAV 220) sinceother networks 260 has the lowest score. - As further shown in
FIG. 4A ,process 400 may include generating flight path instructions that identify the selected network (block 435). For example,UAV platform 230 may generate flight path instructions that identify the selected network (e.g., wireless network 240). In some implementations, the flight path instructions may include specific altitudes forUAV 220 between 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 ofwireless network 240 via whichUAV 220 may communicate with UAV platform 230); timing information (e.g., when to take off, when to perform certain navigational maneuvers, etc.); waypoint information (e.g., locations whereUAV 220 may stop and recharge or refuel); etc. For example, the flight path instructions may include information that instructsUAV 220 to fly forty-five degrees northeast for ten kilometers and at an altitude of five-hundred meters, then fly three-hundred and fifteen degrees northwest for ten kilometers and at an altitude of four-hundred meters, etc. - In some implementations, the flight path instructions may include
information instructing UAV 220 to connect to network X untilUAV 220 reaches point A of the flight path, then connect to network Y untilUAV 220 reaches point B of the flight path, and then connect back to network X for the remainder of the flight path. In some implementations, the flight path instructions may includeinformation instructing UAV 220 to connect to network X untilUAV 220 loses connectivity, and then connect to network Y for the remainder of the flight path. In some implementations, the flight path instructions may includeinformation instructing UAV 220 to connect to network X untilUAV 220 reaches point A of the flight path, and then keep trying to connect to network Y until successful. - As shown in
FIG. 4B ,process 400 may include providing the flight path instructions to the UAV (block 440). For example,UAV platform 230 may provide the flight path instructions toUAV 220. In some implementations,UAV 220 may utilize the flight path instructions to travel via the flight path. For example,UAV 220 may 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. untilUAV 220 arrives at the destination location. - In some implementations, if
UAV 220 includes sufficient computational resources (e.g., a sufficient degree of autonomy),UAV 220 may utilize information provided by the flight path instructions to calculate a flight path forUAV 220 and to generate flight path instructions. In such implementations, the flight path instructions provided byUAV platform 230 may include less detailed information, andUAV 220 may determine more detailed flight path instructions via the computational resources ofUAV 220. - As further shown in
FIG. 4B ,process 400 may include receiving network connectivity information from the UAV during traversal of the flight path by the UAV (block 445). For example, whileUAV 220 is traveling along the flight path in accordance with the flight path instructions,UAV 220 and/or the selected network (e.g., one or more of networks 240-260) may provide network connectivity information toUAV platform 230, andUAV platform 230 may receive the network connectivity information. In some implementations, the network connectivity information may include information associated with a connection betweenUAV 220 and the selected network. For example, the network connectivity information may include information associated with signal strength betweenUAV 220 and the selected network, a bandwidth provided by the selected network toUAV 220, etc. - As further shown in
FIG. 4B ,process 400 may include determining whether to select a new network based on the network connectivity information (block 450). For example,UAV platform 230 may determine whether to select a new network for communicating withUAV 220 based on the network connectivity information. In some implementations,UAV platform 230 may determine to not select a new network if the network connectivity information indicates thatUAV 220 will continue to communicate withUAV platform 230 via the selected network. In some implementations,UAV platform 230 may determine to select a new network if the network connectivity information indicates thatUAV 220 is losing or will lose a signal received from the selected network (e.g.,UAV 220 will not be able to communicate with UAV platform 230). In such implementations,UAV platform 230 may select a new network so thatUAV 220 may continue to communicate withUAV platform 230 via the new network. For example, assume thatUAV 220 is communicating withUAV platform 230 viawireless network 240, but is about to fly out of a range ofwireless network 240. Further, assume thatUAV 220 is flying in a range ofsatellite network 250. In such an example,UAV platform 230 may instructUAV 220 to disconnect fromwireless network 240 and to connect withsatellite network 250 so thatUAV 220 may communicate withUAV platform 230 viasatellite network 250. - As further shown in
FIG. 4B , if the new network is to be selected (block 450—YES),process 400 may include selecting the new network based on the network connectivity information (block 455). For example, ifUAV platform 230 determines that a new network is to be selected,UAV platform 230 may select a new network based on the network connectivity information (e.g., as described above). In some implementations, if the selected network iswireless network 240, the new network may include anotherwireless network 240,satellite network 250, and/or one or more ofother networks 260. In some implementations, the new network may enableUAV 220 to communicate withUAV platform 230. In some implementations.UAV platform 230 may generate modified flight path instructions, which include information associated with the new network, based on the network connectivity information. In some implementations, the modified flight path instructions may include the features of flight path instructions, but may be modified based on the network connectivity information. For example, the flight path instructions may be modified to instructUAV 220 to disconnect fromwireless network 240 and connect withsatellite network 250. - As further shown in
FIG. 4B ,process 400 may include providing information associated with the new network to the UAV (block 460). For example,UAV platform 230 may provide, toUAV 220, information associated with the new network, such as a system identification code (SID), security information, bandwidth information, etc. associated with the new network. In some implementations,UAV platform 230 may provide the information associated with the new network via the modified flight path instructions. In some implementations,UAV 220 may utilize the information associated with the new network to connect with the new network and to communicate withUAV platform 230. For example,UAV 220 may instruct the selected network to handover communication to the new network (e.g., so thatUAV 220 may continuously communicate with UAV platform 230) untilUAV 220 arrives at the destination location. In some implementations,UAV 220 may continue to provide further network connectivity information toUAV platform 230 during traversal of the flight path, andUAV platform 230 may or may not select another new network based on the further network connectivity information. - As further shown in
FIG. 4B , if the new network is not selected (block 450—NO),process 400 may include receiving a notification that the UAV arrived at the second location (block 465). For example, if the network connectivity information indicates thatUAV 220 may still communicate withUAV platform 230 via the selected network.UAV platform 230 may determine that the new network need not be selected. In some implementations,UAV 220 may continue to communicate withUAV platform 230, via the selected network, if a new network is not selected. In some implementations,UAV 220 may continue along the flight path based on the flight path instructions untilUAV 220 arrives at the destination location. WhenUAV 220 arrives at the destination location,UAV 220 may provide a notification toUAV platform 230, via one or more of networks 240-260. In some implementations, the notification may indicate thatUAV 220 has safely arrived at the destination location. - Although
FIGS. 4A and 4B shows example blocks ofprocess 400, in some implementations,process 400 may 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 ofprocess 400 may be performed in parallel. -
FIGS. 5A-5E are diagrams of an example 500 relating toexample process 400 shown inFIGS. 4A and 4B . Assume that a first user device 210 (e.g., a tablet 210) 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 device 210 (e.g., a computer 210) is associated with a second user (e.g., Bob) that is located at a destination location (e.g., Fairfax, Va.), and that Bob has instructedcomputer 210 to request delivery of a package to Fairfax, Va. For example,computer 210 may inform tablet 210 (e.g., via one or more servers associated with the delivery company) and the employee that the package is to be delivered to Bob as soon as possible. Further, assume that the employee wants to utilizeUAV 220 to fly the package from Washington, D.C. to Fairfax, Va. in order to deliver the package to Bob. - As further shown in
FIG. 5A ,UAV platform 230 anddata storage 235 may communicate withwireless network 240,satellite network 250, and/orother networks 260. One or more of networks 240-260 may provide, todata storage 235,information 505, such as capability information associated withUAV 220, 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 in
FIG. 5A , the employee may instructtablet 210 to generate arequest 510 for a flight path (e.g., from Washington, D.C. to Fairfax, Va.) forUAV 220, and to providerequest 510 toUAV platform 230.Request 510 may include credentials (e.g., a serial number, an identifier of a UICC, etc.) associated withUAV 220, or the credentials may be provided separately fromrequest 510 toUAV platform 230.UAV platform 230 may utilize the credentials to determine whetherUAV 220 is authenticated for utilizingUAV platform 230 and/or one or more of networks 240-260, and is registered with an appropriate authority for use. For example,UAV platform 230 may compare the credentials with information provided indata storage 235 in order to determine whetherUAV 220 is authenticated for utilizingUAV platform 230 and/or one or more of networks 240-260, and is registered with an appropriate authority. Assume thatUAV 220 is authenticated and/or registered. -
UAV platform 230 may calculate a flight path from Washington, D.C. to Fairfax, Va. based on information 505 (e.g., weather information, air traffic information, obstacle information, regulatory information, historical information, etc.) provided indata storage 235. For example, assume that the weather information indicates that the wind is ten kilometers per hour from the west and that it is raining; the air traffic information indicates that a jet is at an altitude of ten-thousand meters and anotherUAV 220 is at an altitude of five-hundred meters; the obstacle information indicates that a mountain is two kilometers in height and a building is five-hundred meters in height; the regulatory information indicates that there is a no-fly zone over a government building; and the historical information indicates that a historical flight path had a duration of thirty minutes and an altitude of one-thousand meters.UAV platform 230 may calculate the flight path from Washington, D.C. to Fairfax, Va. based on such information. - As further shown in
FIG. 5A ,UAV platform 230 may determinenetwork requirements 515 for the requested flight path based onrequest 510. For example,UAV platform 230 may determine thatnetwork requirements 515 includeUAV 220 utilizing one or more of networks 240-260 to communicate withUAV platform 230 during the flight path.UAV platform 230 may providenetwork requirements 515 to data storage 235 (e.g., for storage). -
UAV platform 230 may assign different weights to different information associated with available networks (e.g., networks 240-260), and may calculate a score for each network based on the assigned weights and/or based onnetwork requirements 515.UAV platform 230 may rank the networks based on the scores, and may provide the ranking and the scores of the networks to data storage 235 (e.g., for storage). Assume thatUAV platform 230 rankswireless network 240 the highest based on the calculated scores.UAV platform 230 may retrieve the ranking and the scores of the networks fromdata storage 235, as indicated byreference number 520 inFIG. 5B .UAV platform 230 may select a particular network (e.g., wireless network 240), from the networks, based on the ranking and/or based onnetwork requirements 515, as indicated byreference number 525. As further shown inFIG. 5B ,UAV 220 may connect 530 withwireless network 240 based on the selection ofwireless network 240 as the particular network. Once connected towireless network 240,UAV 220 may communicate withUAV platform 230 viawireless network 240. - The calculated flight path from Washington, D.C. to Fairfax, Va. may be depicted by
reference number 535 inFIG. 5C . As further shown inFIG. 5C .UAV platform 230 may generateflight path instructions 540 forflight path 535.Flight path instructions 540 may include, for example,information instructing UAV 220 to fly north at zero degrees for ten kilometers, then northeast at forty degrees for three kilometers, at an altitude of one-thousand meters, etc.UAV platform 230 may provideflight path instructions 540 toUAV 220 viawireless network 240. The package may be attached to or provided in UAV 220 (e.g., by the employee).UAV 220 may take off from Washington, D.C. with the package, and may travelflight path 535 based onflight path instructions 540. - While
UAV 220 is traveling alongflight path 535,UAV 220 and/orwireless network 240 may providenetwork connectivity information 545 toUAV platform 230, as shown inFIG. 5D . Assume thatUAV 220 is flying out of range ofwireless network 240, and provides, toUAV platform 230, information indicating thatUAV 220 is losing connectivity with wireless network 240 (e.g., via network connectivity information 545). Based onnetwork connectivity information 545,UAV platform 230 may select anew network 550 that enablesUAV 220 to communicate withUAV platform 230. Assume thatUAV platform 230 selectssatellite network 250 asnew network 550, and instructswireless network 250 tohandover 555 communications withUAV 220 tosatellite network 250. As further shown inFIG. 5D ,UAV 220 may connect 560 withsatellite network 250, based on the selection ofsatellite network 250, and may communicate withUAV platform 230 viasatellite network 250. While communications are being switched fromwireless network 240 tosatellite network 250,UAV 220 may continue to travel alongflight path 535 untilUAV 220 arrives at Fairfax, Va. - As further shown in
FIG. 5D , whenUAV 220 arrives at Fairfax, Va.,UAV 220 may leave the package at a location where Bob may retrieve the package.UAV 220 and/or computer 210 (e.g., via Bob's input or detection of the presence of UAV 220) may generate anotification 565 indicating thatUAV 220 and the package arrived safely at a particular location in Fairfax, Va., and may providenotification 565 toUAV platform 230. - As shown in
FIG. 5E , now assume thatUAV 220 receivesflight path instructions 540, forflight path 535, fromUAV platform 230. Further, assume thatflight path instructions 540 instructUAV 220 to connect to a cellular network 240-1, and thatUAV 220 connects 570 with cellular network 240-1 based onflight path instructions 540.UAV 220 may take off from Washington, D.C. with the package, and may travelflight path 535 based onflight path instructions 540.UAV 220 may communicate withUAV platform 230, via cellular network 240-1, for a portion offlight path 535. As further shown inFIG. 5E ,UAV 220 may disconnect from cellular network 240-1 at a particular point offlight path 535, and may connect 575 with a UAV-generated cellular network 240-2.UAV 220 may communicate withUAV platform 230, via UAV-generated cellular network 240-2, for another portion offlight path 535. As further shown inFIG. 5E ,UAV 220 may disconnect from UAV-generated cellular network 240-2 at another particular point offlight path 535, and may connect 580 with a Wi-Fi network 260.UAV 220 may communicate withUAV platform 230, via Wi-Fi network 260, for a final portion offlight path 535. - As indicated above,
FIGS. 5A-5E are provided merely as an example. Other examples are possible and may differ from what was described with regard toFIGS. 5A-5E . - 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 enable UAVs to seamlessly connect with the platform via various networks, which may ensure that the platform continuously communicates with the UAVs. The systems and/or methods may enable the platform to select a network for communicating with the UAV, and the selected network may reduce connectivity costs, increase security of communications, reduce the need for handoffs to other networks, offer the best connectivity, or the like.
- To the extent the aforementioned implementations collect, store, or employ personal information provided by individuals, it should be understood that such information shall be used in accordance with all applicable laws concerning protection of personal information. Additionally, the collection, storage, and use of such information may be subject to consent of the individual to such activity, for example, through “opt-in” or “opt-out” processes as may be appropriate for the situation and type of information. Storage and use of personal information may be in an appropriately secure manner reflective of the type of information, for example, through various encryption and anonymization techniques for particularly sensitive information.
- The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.
- 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.
- Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of possible implementations includes each dependent claim in combination with every other claim in the claim set.
- No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Furthermore, as used herein, the term “set” is intended to include one or more items, and may be used interchangeably with “one or more.” Where only one item is intended, the term “one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/227,604 US20210304626A1 (en) | 2014-05-20 | 2021-04-12 | Selection of networks for communicating with unmanned aerial vehicles |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/282,378 US9881022B2 (en) | 2014-05-20 | 2014-05-20 | Selection of networks for communicating with unmanned aerial vehicles |
US15/657,668 US10977949B2 (en) | 2014-05-20 | 2017-07-24 | Selection of networks for communicating with unmanned aerial vehicles |
US17/227,604 US20210304626A1 (en) | 2014-05-20 | 2021-04-12 | Selection of networks for communicating with unmanned aerial vehicles |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/657,668 Continuation US10977949B2 (en) | 2014-05-20 | 2017-07-24 | Selection of networks for communicating with unmanned aerial vehicles |
Publications (1)
Publication Number | Publication Date |
---|---|
US20210304626A1 true US20210304626A1 (en) | 2021-09-30 |
Family
ID=57112773
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/282,378 Active 2035-12-26 US9881022B2 (en) | 2014-05-20 | 2014-05-20 | Selection of networks for communicating with unmanned aerial vehicles |
US15/657,668 Active 2035-01-24 US10977949B2 (en) | 2014-05-20 | 2017-07-24 | Selection of networks for communicating with unmanned aerial vehicles |
US17/227,604 Pending US20210304626A1 (en) | 2014-05-20 | 2021-04-12 | Selection of networks for communicating with unmanned aerial vehicles |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/282,378 Active 2035-12-26 US9881022B2 (en) | 2014-05-20 | 2014-05-20 | Selection of networks for communicating with unmanned aerial vehicles |
US15/657,668 Active 2035-01-24 US10977949B2 (en) | 2014-05-20 | 2017-07-24 | Selection of networks for communicating with unmanned aerial vehicles |
Country Status (1)
Country | Link |
---|---|
US (3) | US9881022B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220070253A1 (en) * | 2020-08-28 | 2022-03-03 | Tencent America LLC | Systems and methods for unmanned aerial system communication |
Families Citing this family (60)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140330456A1 (en) * | 2006-03-17 | 2014-11-06 | Manuel R. Lopez Morales | Landing site designation in an autonomous delivery network |
EP3926433A1 (en) * | 2014-06-13 | 2021-12-22 | Twitter, Inc. | Messaging-enabled unmanned aerial vehicle |
JP6210522B2 (en) * | 2014-09-15 | 2017-10-11 | エスゼット ディージェイアイ テクノロジー カンパニー リミテッドSz Dji Technology Co.,Ltd | Unmanned aircraft flight control method, flight data processing method, unmanned aircraft, and server |
US10163164B1 (en) * | 2014-09-22 | 2018-12-25 | State Farm Mutual Automobile Insurance Company | Unmanned aerial vehicle (UAV) data collection and claim pre-generation for insured approval |
US9715009B1 (en) | 2014-12-19 | 2017-07-25 | Xidrone Systems, Inc. | Deterent for unmanned aerial systems |
US9689976B2 (en) | 2014-12-19 | 2017-06-27 | Xidrone Systems, Inc. | Deterent for unmanned aerial systems |
US10039114B2 (en) * | 2015-04-14 | 2018-07-31 | Verizon Patent And Licensing Inc. | Radio access network for unmanned aerial vehicles |
US9858824B1 (en) * | 2015-07-14 | 2018-01-02 | Rockwell Collins, Inc. | Flight plan optimization for maintaining internet connectivity |
EP3341925B1 (en) * | 2015-08-27 | 2023-09-13 | Dronsystems Limited | A highly automated system of air traffic control (atm) for at least one unmanned aerial vehicle (unmanned aerial vehicles uav) |
US10051475B2 (en) | 2015-09-28 | 2018-08-14 | Department 13, Inc. | Unmanned aerial vehicle intrusion detection and countermeasures |
US10730626B2 (en) | 2016-04-29 | 2020-08-04 | United Parcel Service Of America, Inc. | Methods of photo matching and photo confirmation for parcel pickup and delivery |
CA3022379C (en) | 2016-04-29 | 2021-03-23 | United Parcel Service Of America, Inc. | Unmanned aerial vehicle pick-up and delivery systems |
US10446043B2 (en) * | 2016-07-28 | 2019-10-15 | At&T Mobility Ii Llc | Radio frequency-based obstacle avoidance |
AU2017318799A1 (en) * | 2016-09-02 | 2018-09-20 | Sony Corporation | Circuit, terminal device, base station device and method |
US9866313B1 (en) * | 2016-12-14 | 2018-01-09 | T-Mobile Usa, Inc. | UAV cellular communication service delivery |
US10168695B2 (en) * | 2016-12-07 | 2019-01-01 | At&T Intellectual Property I, L.P. | Method and apparatus for controlling an unmanned aircraft |
JP6895657B2 (en) * | 2017-01-31 | 2021-06-30 | サイレックス・テクノロジー株式会社 | Unmanned vehicle, driving system, and control method of unmanned vehicle |
US11217105B2 (en) | 2017-03-31 | 2022-01-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Enhanced flight plan for unmanned traffic aircraft systems |
US11218840B2 (en) | 2017-03-31 | 2022-01-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and systems for using network location services in a unmanned aircraft systems traffic management framework |
RU2731942C1 (en) | 2017-03-31 | 2020-09-09 | Телефонактиеболагет Лм Эрикссон (Пабл) | Broadcasting transmission of geolocation information in radio frame transmitted from unmanned aerial vehicle |
US11023283B2 (en) | 2017-04-13 | 2021-06-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and resource manager for scheduling of instances in a data centre |
EP3610346A1 (en) | 2017-04-14 | 2020-02-19 | Telefonaktiebolaget LM Ericsson (Publ) | Optimal unmanned aerial vehicle flight route planning based on quality-of-service requirements for data, telemetry, and command and control requirements in 3gpp networks |
EP3619832B1 (en) | 2017-05-05 | 2021-04-07 | Telefonaktiebolaget LM Ericsson (PUBL) | Methods and systems for using an unmanned aerial vehicle (uav) flight path to coordinate an enhanced handover in 3rd generation partnership project (3gpp) networks |
US10775792B2 (en) | 2017-06-13 | 2020-09-15 | United Parcel Service Of America, Inc. | Autonomously delivering items to corresponding delivery locations proximate a delivery route |
US11445510B2 (en) | 2017-07-10 | 2022-09-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Optimization of radio resource allocation based on unmanned aerial vehicle flight path information |
EP3665950A4 (en) * | 2017-08-11 | 2021-03-31 | Nokia Technologies Oy | Information exchange for an unmanned aerial vehicle |
US10952113B2 (en) | 2017-09-05 | 2021-03-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Planned continuity of unmanned aerial vehicle (UAV) link connectivity in UAV traffic management systems |
US11032022B1 (en) | 2017-10-11 | 2021-06-08 | Genghiscomm Holdings, LLC | Detection, analysis, and countermeasures for automated and remote-controlled devices |
US10998960B2 (en) * | 2017-11-17 | 2021-05-04 | Nokia Technologies Oy | Providing reference altitude information to unmanned aerial vehicles for configuration differentiation |
WO2019113733A1 (en) * | 2017-12-11 | 2019-06-20 | 深圳市大疆创新科技有限公司 | Handover control method, control terminal, and unmanned aerial vehicle |
US10907940B1 (en) | 2017-12-12 | 2021-02-02 | Xidrone Systems, Inc. | Deterrent for unmanned aerial systems using data mining and/or machine learning for improved target detection and classification |
US10691142B2 (en) | 2017-12-21 | 2020-06-23 | Wing Aviation Llc | Anticipatory dispatch of UAVs to pre-staging locations |
US11010851B2 (en) * | 2017-12-22 | 2021-05-18 | Wing Aviation Llc | Distribution of aerial vehicle transport capacity based on item-provider performance metrics |
EP3732927B1 (en) | 2017-12-29 | 2022-05-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Managing connections between an unmanned aerial vehicle and on or more associated devices. |
WO2019139511A1 (en) | 2018-01-12 | 2019-07-18 | Telefonaktiebolaget Lm Ericsson (Publ) | Method, device and system for programming a uav to be controlled based on communication via at least two mobile communication networks |
EP3747000B1 (en) * | 2018-01-29 | 2024-07-10 | Israel Aerospace Industries Ltd. | Proximity navigation of unmanned vehicles |
US11693400B2 (en) * | 2018-02-13 | 2023-07-04 | Rakuten Group, Inc. | Unmanned aerial vehicle control system, unmanned aerial vehicle control method, and program |
CN108492060A (en) * | 2018-03-04 | 2018-09-04 | 南京大翼航空科技有限公司 | A kind of unmanned plane real name monitoring and managing method and monitoring system |
WO2019186245A1 (en) | 2018-03-30 | 2019-10-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Network coverage and policy information generation and distribution for unmanned aerial vehicle flight planning |
WO2019204997A1 (en) * | 2018-04-24 | 2019-10-31 | 深圳市大疆创新科技有限公司 | Autonomous mobile platform, control end and autonomous mobile platform system |
WO2020006559A1 (en) * | 2018-06-29 | 2020-01-02 | Satcom Direct, Inc. | System and method for forecasting availability of network services during flight |
US11398158B2 (en) | 2018-06-29 | 2022-07-26 | Satcom Direct, Inc. | System and method for forecasting availability of network services during flight |
US11601825B2 (en) * | 2018-08-08 | 2023-03-07 | Faraday&Future Inc. | Connected vehicle network data transfer optimization |
DE102018120013A1 (en) * | 2018-08-16 | 2020-02-20 | Autel Robotics Europe Gmbh | METHOD, DEVICE AND SYSTEM FOR TRANSMITTING TRAVEL INFORMATION, UNMANNED AIRCRAFT, GROUND STATION AND COMPUTER READABLE STORAGE MEDIUM |
US11567513B2 (en) * | 2018-08-16 | 2023-01-31 | Rakuten Group, Inc. | Unmanned aerial vehicle control system, unmanned aerial vehicle control method, and program |
US10594872B1 (en) | 2018-09-27 | 2020-03-17 | Honeywell International Inc. | Systems and methods for wireless network service provider selection |
CN110972127B (en) * | 2018-09-29 | 2021-07-09 | 华为技术有限公司 | Unmanned aerial vehicle supervision method and device |
US20200130510A1 (en) * | 2018-10-30 | 2020-04-30 | Brandon Eck | System and method for autonomous shipping |
CN111385811B (en) * | 2018-12-27 | 2023-04-07 | 华为技术有限公司 | Unmanned aerial vehicle communication method, device and system |
US20220400398A1 (en) * | 2019-02-21 | 2022-12-15 | Aveopt, Inc. | Vehicle connectivity and communication device |
US11288970B2 (en) * | 2019-02-21 | 2022-03-29 | Aveopt, Inc. | System and methods for monitoring unmanned traffic management infrastructure |
WO2020230511A1 (en) * | 2019-05-15 | 2020-11-19 | ソニー株式会社 | Wireless communication device, wireless communication method, program, and wireless communication system |
EP3751756A1 (en) | 2019-06-14 | 2020-12-16 | Dimetor GmbH | Apparatus and method for guiding unmanned aerial vehicles |
DK3751897T3 (en) * | 2019-06-14 | 2022-08-15 | Dimetor Gmbh | Apparatus and method for determining network coverage data for connecting a mobile terminal |
EP3751901B1 (en) | 2019-06-14 | 2023-06-07 | Dimetor GmbH | Apparatus and method for guiding unmanned aerial vehicles |
EP4014525A4 (en) * | 2019-10-02 | 2022-09-14 | Samsung Electronics Co., Ltd. | Apparatus and method for mobility management of unmanned aerial vehicle using flight mission and route in mobile communication system |
US11498701B2 (en) | 2020-04-06 | 2022-11-15 | Workhorse Group Inc. | Flying vehicle systems and methods |
CN113676936B (en) * | 2020-05-15 | 2024-04-09 | 华为技术有限公司 | Processing method, network element, system and storage medium of abnormal behavior unmanned aerial vehicle |
US11440679B2 (en) * | 2020-10-27 | 2022-09-13 | Cowden Technologies, Inc. | Drone docking station and docking module |
US11681301B2 (en) | 2021-06-29 | 2023-06-20 | Beta Air, Llc | System for a guidance interface for a vertical take-off and landing aircraft |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060178141A1 (en) * | 2005-02-09 | 2006-08-10 | Honeywell International Inc. | Adaptive communications system and method |
US20090210109A1 (en) * | 2008-01-14 | 2009-08-20 | Donald Lewis Ravenscroft | Computing Flight Plans for UAVs While Routing Around Obstacles Having Spatial and Temporal Dimensions |
US8639265B1 (en) * | 2012-02-14 | 2014-01-28 | Sprint Spectrum L.P. | Advertising wireless coverage areas based on device altitude |
US20150120094A1 (en) * | 2013-10-26 | 2015-04-30 | Amazon Technologies, Inc. | Unmanned aerial vehicle delivery system |
US20160328980A1 (en) * | 2014-01-31 | 2016-11-10 | Tata Consultancy Services Limited | A computer implemented system and method for providing robust communication links to unmanned aerial vehicles |
US20160363447A1 (en) * | 2013-08-30 | 2016-12-15 | Insitu, Inc. | Aerial vehicle awareness display |
US20180026708A1 (en) * | 2016-06-10 | 2018-01-25 | ETAK Systems, LLC | Drone network switchover between wireless networks |
US10431103B2 (en) * | 2017-04-11 | 2019-10-01 | T-Mobile Usa, Inc. | Three-dimensional network coverage modeling for UAVs |
US20220148434A1 (en) * | 2020-11-11 | 2022-05-12 | AT&T Technical Services Company, Inc. | System and method for selecting long-lasting anchor base stations for unmanned aerial vehicles |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6400690B1 (en) * | 1998-10-15 | 2002-06-04 | International Business Machines Corporation | Dual map system for navigation and wireless communication |
US8060102B2 (en) * | 2004-12-14 | 2011-11-15 | Bce Inc. | System and method for coverage analysis in a wireless network |
US9654200B2 (en) * | 2005-07-18 | 2017-05-16 | Mutualink, Inc. | System and method for dynamic wireless aerial mesh network |
DE102007032084A1 (en) * | 2007-07-09 | 2009-01-22 | Eads Deutschland Gmbh | Collision and Conflict Prevention System for autonomous unmanned aerial vehicles (UAV) |
US8948932B2 (en) * | 2007-10-30 | 2015-02-03 | Raytheon Company | Unmanned vehicle route management system |
US8626361B2 (en) * | 2008-11-25 | 2014-01-07 | Honeywell International Inc. | System and methods for unmanned aerial vehicle navigation |
US8706131B2 (en) * | 2009-06-18 | 2014-04-22 | Empire Technology Development Llc | Device location prediction for mobile service optimization |
US8594932B2 (en) * | 2010-09-14 | 2013-11-26 | The Boeing Company | Management system for unmanned aerial vehicles |
GB2484085B (en) * | 2010-09-28 | 2014-05-07 | Cassidian Ltd | Telecommunications network routing |
US8606266B1 (en) * | 2011-05-20 | 2013-12-10 | Rockwell Collins, Inc. | Airborne communications network routing |
US10206164B2 (en) * | 2011-05-31 | 2019-02-12 | Blackberry Limited | Collaborative scheme for selection of optimal accesses and seamless transition between accesses |
DE102011118706B4 (en) * | 2011-11-16 | 2014-03-20 | Audi Ag | Method for transmitting data between a mobile terminal and at least one fixed data network, mobile terminal and motor vehicle with a mobile terminal |
US8938544B2 (en) * | 2012-03-09 | 2015-01-20 | Toyota Jidosha Kabushiki Kaisha | Vehicle network connectivity management |
US9384668B2 (en) * | 2012-05-09 | 2016-07-05 | Singularity University | Transportation using network of unmanned aerial vehicles |
US8798922B2 (en) * | 2012-11-16 | 2014-08-05 | The Boeing Company | Determination of flight path for unmanned aircraft in event of in-flight contingency |
EP2733560A1 (en) * | 2012-11-19 | 2014-05-21 | The Boeing Company | Autonomous mission management |
US8818719B1 (en) * | 2013-02-22 | 2014-08-26 | GM Global Technology Operations LLC | Method of controlling data communication between a vehicle and heterogeneous wireless networks |
US9046370B2 (en) * | 2013-03-06 | 2015-06-02 | Qualcomm Incorporated | Methods for providing a navigation route based on network availability and device attributes |
US9167417B2 (en) * | 2013-05-17 | 2015-10-20 | Nokia Solutions And Networks Oy | Application based network information maintenance |
US9654965B2 (en) * | 2013-09-09 | 2017-05-16 | Blackberry Limited | Regulatory compliance for wireless devices |
US9859972B2 (en) * | 2014-02-17 | 2018-01-02 | Ubiqomm Llc | Broadband access to mobile platforms using drone/UAV background |
US9256225B2 (en) * | 2014-05-12 | 2016-02-09 | Unmanned Innovation, Inc. | Unmanned aerial vehicle authorization and geofence envelope determination |
-
2014
- 2014-05-20 US US14/282,378 patent/US9881022B2/en active Active
-
2017
- 2017-07-24 US US15/657,668 patent/US10977949B2/en active Active
-
2021
- 2021-04-12 US US17/227,604 patent/US20210304626A1/en active Pending
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060178141A1 (en) * | 2005-02-09 | 2006-08-10 | Honeywell International Inc. | Adaptive communications system and method |
US20090210109A1 (en) * | 2008-01-14 | 2009-08-20 | Donald Lewis Ravenscroft | Computing Flight Plans for UAVs While Routing Around Obstacles Having Spatial and Temporal Dimensions |
US8639265B1 (en) * | 2012-02-14 | 2014-01-28 | Sprint Spectrum L.P. | Advertising wireless coverage areas based on device altitude |
US20160363447A1 (en) * | 2013-08-30 | 2016-12-15 | Insitu, Inc. | Aerial vehicle awareness display |
US20150120094A1 (en) * | 2013-10-26 | 2015-04-30 | Amazon Technologies, Inc. | Unmanned aerial vehicle delivery system |
US20160328980A1 (en) * | 2014-01-31 | 2016-11-10 | Tata Consultancy Services Limited | A computer implemented system and method for providing robust communication links to unmanned aerial vehicles |
US20180026708A1 (en) * | 2016-06-10 | 2018-01-25 | ETAK Systems, LLC | Drone network switchover between wireless networks |
US10431103B2 (en) * | 2017-04-11 | 2019-10-01 | T-Mobile Usa, Inc. | Three-dimensional network coverage modeling for UAVs |
US20220148434A1 (en) * | 2020-11-11 | 2022-05-12 | AT&T Technical Services Company, Inc. | System and method for selecting long-lasting anchor base stations for unmanned aerial vehicles |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220070253A1 (en) * | 2020-08-28 | 2022-03-03 | Tencent America LLC | Systems and methods for unmanned aerial system communication |
US11522950B2 (en) * | 2020-08-28 | 2022-12-06 | Tencent America LLC | Systems and methods for unmanned aerial system communication |
US11729261B2 (en) | 2020-08-28 | 2023-08-15 | Tencent America LLC | Systems and methods for unmanned aerial system communication |
Also Published As
Publication number | Publication date |
---|---|
US10977949B2 (en) | 2021-04-13 |
US20170337219A1 (en) | 2017-11-23 |
US20160300493A1 (en) | 2016-10-13 |
US9881022B2 (en) | 2018-01-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210304626A1 (en) | Selection of networks for communicating with unmanned aerial vehicles | |
US10394858B2 (en) | Utilization of third party networks and third party unmanned aerial vehicle platforms | |
US10089890B2 (en) | Dynamic selection of unmanned aerial vehicles | |
US11230377B2 (en) | Unmanned aerial vehicle platform | |
US9334052B2 (en) | Unmanned aerial vehicle flight path determination, optimization, and management | |
US9454151B2 (en) | User interfaces for selecting unmanned aerial vehicles and mission plans for unmanned aerial vehicles | |
US9412279B2 (en) | Unmanned aerial vehicle network-based recharging | |
US9875454B2 (en) | Accommodating mobile destinations for unmanned aerial vehicles | |
US9569972B2 (en) | Unmanned aerial vehicle identity and capability verification | |
US9811084B2 (en) | Identifying unmanned aerial vehicles for mission performance | |
US10380900B2 (en) | Information collection and component/software upgrades for unmanned aerial vehicles | |
US9311820B2 (en) | Configurability options for information, airspace, and property utilized by an unmanned aerial vehicle platform | |
US9671790B2 (en) | Scheduling of unmanned aerial vehicles for mission performance | |
US9542850B2 (en) | Secure communications with unmanned aerial vehicles | |
US11316581B2 (en) | Network capacity management | |
US9646283B2 (en) | Secure payload deliveries via unmanned aerial vehicles | |
US9262929B1 (en) | Ground-sensitive trajectory generation for UAVs |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: VERIZON PATENT AND LICENSING INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:UBHI, GURPREET;SRIVASTAVA, ASHOK N.;PASKO, DOUGLAS M.;AND OTHERS;SIGNING DATES FROM 20140515 TO 20140519;REEL/FRAME:055890/0041 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: ADVISORY ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |