EP4014216A1 - Détermination de l'opportunité d'entretenir un véhicule aérien sans pilote - Google Patents

Détermination de l'opportunité d'entretenir un véhicule aérien sans pilote

Info

Publication number
EP4014216A1
EP4014216A1 EP20771733.1A EP20771733A EP4014216A1 EP 4014216 A1 EP4014216 A1 EP 4014216A1 EP 20771733 A EP20771733 A EP 20771733A EP 4014216 A1 EP4014216 A1 EP 4014216A1
Authority
EP
European Patent Office
Prior art keywords
uav
smart contract
determining
service operation
receive
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
Application number
EP20771733.1A
Other languages
German (de)
English (en)
Inventor
Syed Mohammad Ali
Lowell L. Duke
Zehra Akbar
Syed Mohammad Amir Husain
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Skygrid LLC
Original Assignee
Skygrid LLC
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Skygrid LLC filed Critical Skygrid LLC
Publication of EP4014216A1 publication Critical patent/EP4014216A1/fr
Pending legal-status Critical Current

Links

Classifications

    • 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
    • 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/02—Reservations, e.g. for tickets, services or events
    • 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/04—Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
    • G06Q10/047—Optimisation of routes or paths, e.g. travelling salesman problem
    • 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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • 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
    • 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/20—Administration of product repair or maintenance
    • 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
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40—Business processes related to the transportation industry
    • 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/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/04—Anti-collision systems
    • G08G5/045—Navigation or guidance aids, e.g. determination of anti-collision manoeuvers

Definitions

  • UAV Unmanned Aerial Vehicle
  • the Unmanned Aircraft System Traffic Management is an initiative sponsored by the Federal Aviation Administration (FAA) to enable multiple beyond visual line-of-sight drone operations at low altitudes (under 400 feet above ground level (AGL)) in airspace where FAA air traffic services are not provided.
  • FAM Federal Aviation Administration
  • AGL ground level
  • a framework that extends beyond the 400 feet AGL limit is needed.
  • unmanned aircraft that would be used by package delivery services and air taxis may need to travel at altitudes above 400 feet.
  • Such a framework requires technology that will allow the FAA to safely regulate unmanned aircraft.
  • a method of determining whether to service an unmanned aerial vehicle includes accessing, by a smart contract controller executing on a device of a UAV transportation ecosystem, one or more parameters associated with a UAV.
  • the smart contract determines whether the one or more parameters satisfies one or more conditions for fulfillment of the smart contract.
  • the smart contract indicates a requirement for the UAV to receive a service operation.
  • a method of determining whether to service an unmanned aerial vehicle includes determining, by a smart contract controller executing on a device of a UAV transportation ecosystem, whether a UAV has a particular requirement to receive a particular service operation. In response to determining that the UAV has the particular requirement to receive the particular service operation, the smart contract directs the UAV to receive the particular service operation.
  • UAV unmanned aerial vehicle
  • FIG. 1 is a block diagram illustrating a particular implementation of a system for determining whether to sendee an unmanned aerial vehicle
  • FIG. 2 is a block diagram illustrating another implementation of a system for determining whether to sendee an unmanned aerial vehicle
  • FIG. 3 A a block diagram illustrating a particular implementation of the blockchain used by the systems of FIGS. 1-2 to record data associated with an unmanned aerial vehicle;
  • FIG. 3B is an additional view of the blockchain of FIG. 3 A;
  • FIG. 3C is an additional view of the blockchain of FIG. 3 A;
  • FIG. 4 is a block diagram illustrating a particular implementation of a system for determining whether to sendee an unmanned aerial vehicle
  • FIG. 5 is a flowchart to illustrate a particular implementation of a method for determining whether to sendee an unmanned aerial vehicle
  • FIG. 6 is a flowchart to illustrate another implementation of a method for determining whether to service an unmanned aerial vehicle
  • FIG. 7 is a flowchart to illustrate yet another implementation of a method for determining whether to sendee an unmanned aerial vehicle
  • FIG. 8 is a flowchart to illustrate yet another implementation of a method for determining whether to sendee an unmanned aerial vehicle
  • FIG. 9 is a flowchart to illustrate yet another implementation of a method for determining whether to sendee an unmanned aerial vehicle
  • FIG. 10 is a flowchart to illustrate yet another implementation of a method for determining whether to service an unmanned aerial vehicle
  • FIG. 11 is a flowchart to illustrate yet another implementation of a method for determining whether to service an unmanned aerial vehicle.
  • FIG. 12 is a flowchart to illustrate yet another implementation of a method for determining whether to sendee an unmanned aerial vehicle.
  • FIG. 13 is a flowchart to illustrate yet another implementation of a method for determining whether to sendee an unmanned aerial vehicle.
  • FIG. 14 is a flowchart to illustrate yet another implementation of a method for determining whether to sendee an unmanned aerial vehicle.
  • FIG. 15 is a flowchart to illustrate yet another implementation of a method for determining whether to sendee an unmanned aerial vehicle.
  • FIG. 16 is a flowchart to illustrate yet another implementation of a method for determining whether to sendee an unmanned aerial vehicle.
  • an ordinal term e g., “first,” “second,” “third,” etc.
  • an element such as a structure, a component, an operation, etc.
  • an ordinal term does not by itself indicate any priority or order of the element with respect to another element, but rather merely distinguishes the element from another element having a same name (but for use of the ordinal term).
  • the term “set” refers to a grouping of one or more elements, and the term “plurality” refers to multiple elements.
  • determining may be used to describe how one or more operations are performed. It should be noted that such terms are not to be construed as limiting and other techniques may be utilized to perform similar operations. Additionally, as referred to herein, “generating,” “calculating,” “estimating,” “using,” “selecting,” “accessing,” and “determining” may be used interchangeably. For example, “generating,” “calculating,” “estimating,” or “determining” a parameter (or a signal) may refer to actively generating, estimating, calculating, or determining the parameter (or the signal) or may refer to using, selecting, or accessing the parameter (or signal) that is already generated, such as by another component or device.
  • Coupled may include “communicatively coupled,” “electrically coupled,” or “physically coupled,” and may also (or alternatively) include any combinations thereof.
  • Two devices (or components) may be coupled (e.g., communicatively coupled, electrically coupled, or physically coupled) directly or indirectly via one or more other devices, components, wires, buses, networks (e.g., a wired network, a wireless network, or a combination thereof), etc.
  • Two devices (or components) that are electrically coupled may be included in the same device or in different devices and may be connected via electronics, one or more connectors, or inductive coupling, as illustrative, non-limiting examples.
  • two devices may send and receive electrical signals (digital signals or analog signals) directly or indirectly, such as via one or more wires, buses, networks, etc.
  • electrical signals digital signals or analog signals
  • directly coupled may include two devices that are coupled (e.g., communicatively coupled, electrically coupled, or physically coupled) without intervening components.
  • FIG. 1 sets forth a diagram of a system (100) configured for regarding data associated with an UAV according to embodiments of the present disclosure.
  • the system (100) of FIG. 1 includes an unmanned aerial vehicle (UAV) (102), a control device (120), a server (140), a distributed computing network (151), an air traffic data server (160), a weather data server (170), a regulatory data server (180), and a topographical data server (190).
  • UAV unmanned aerial vehicle
  • control device 120
  • server 140
  • a distributed computing network 151
  • an air traffic data server 160
  • a weather data server (170
  • regulatory data server 180
  • a topographical data server 190
  • a UAV commonly known as a drone, is a type of powered aerial vehicle that does not carry a human operator and uses aerodynamic forces to provide vehicle lift.
  • UAVs are a component of an unmanned aircraft system (UAS), which typically include at least a UAV, a control device, and a system of communications between the two.
  • UAS unmanned aircraft system
  • the flight of a UAV may operate with various levels of autonomy including under remote control by a human operator or autonomously by onboard or ground computers.
  • a UAV may not include a human operator pilot, some UAVs, such as passenger drones (drone taxi, flying taxi, or pilotless helicopter) cany human passengers.
  • the UAV (102) is illustrated as one type of drone.
  • any type of UAV may be used in accordance with embodiments of the present disclosure and unless otherwise noted, any reference to a UAV in this application is meant to encompass all types of UAVs. Readers of skill in the art will realize that the type of drone that is selected for a particular mission or excursion may depend on many factors, including but not limited to the type of payload that the UAV is required to carry, the distance that the UAV must travel to complete its assignment, and the types of terrain and obstacles that are anticipated during the assignment.
  • the UAV (102) includes a processor (104) coupled to a memory (106), a camera (112), positioning circuitry (114), and communication circuitry (116).
  • the communication circuitry (116) includes a transmitter and a receiver or a combination thereof (e.g., a transceiver).
  • the communication circuitry (116) (or the processor (104)) is configured to encrypt outgoing message(s) using a private key associated with the UAV (102) and to decrypt incoming message(s) using a public key of a device (e.g., the control device (120) or the server (140)) that sent the incoming message(s).
  • the outgoing and incoming messages may be transaction messages that include information associated with the UAV.
  • communications between the UAV (102), the control device (120), and the server (140) are secure and trustworthy (e.g., authenticated).
  • the camera (112) is configured to capture image(s), video, or both, and can be used as part of a computer vision system.
  • the camera (112) may capture images or video and provide the video or images to a pilot of the UAV (102) to aid with navigation.
  • the camera (112) may be configured to capture images or video to be used by the processor (104) during performance of one or more operations, such as a landing operation, a takeoff operation, or object/collision avoidance, as non-limiting examples.
  • a single camera (112) is shown in FIG. 1, in alternative implementations more and/or different sensors may be used (e.g., infrared, LIDAR, SONAR, etc.).
  • the positioning circuitry (114) is configured to determine a position of the UAV (102) before, during, and/or after flight.
  • the positioning circuitry (114) may include a global positioning system (GPS) interface or sensor that determines GPS coordinates of the UAV (102).
  • GPS global positioning system
  • the positioning circuitry (114) may also include gyroscope(s), accelerometer(s), pressure sensor(s), other sensors, or a combination thereof, that may be used to determine the position of the UAV (102).
  • the processor (104) is configured to execute instructions stored in and retrieved from the memory (106) to perform various operations.
  • the instructions include operation instructions (108) that include instructions or code that cause the UAV (102) to perform flight control operations.
  • the flight control operations may include any operations associated with causing the UAV to fly from an origin to a destination.
  • the flight control operations may include operations to cause the UAV to fly along a designated route (e.g., based on route information (110), as further described herein), to perform operations based on control data received from one or more control devices, to take off, land, hover, change altitude, change pitch/yaw/roll angles, or any other flight-related operations.
  • the UAV (102) may include one or more actuators, such as one or more flight control actuators, one or more thrust actuators, etc., and execution of the operation instructions (108) may cause the processor (104) to control the one or more actuators to perform the flight control operations.
  • the one or more actuators may include one or more electrical actuators, one or more magnetic actuators, one or more hydraulic actuators, one or more pneumatic actuators, one or more other actuators, or a combination thereof.
  • the route information (110) may indicate a flight path for the UAV (102) to follow.
  • the route information (110) may specify a starting point (e.g., an origin) and an ending point (e.g., a destination) for the UAV (102).
  • the route information may also indicate a plurality of waypoints, zones, areas, regions between the starting point and the ending point.
  • the route information (110) may also indicate a corresponding set of control devices for various points, zones, regions, areas of the flight path.
  • the indicated sets of control devices may be associated with a pilot (and optionally one or more backup pilots) assigned to have control over the UAV (102) while the UAV (102) is in each zone.
  • the route information (110) may also indicate time periods during which the UAV is scheduled to be in each of the zones (and thus time periods assigned to each pilot or set of pilots).
  • the memor (106) of the UAV (102) also includes communication instructions (111) that when executed by the processor (104) cause the processor (104) to transmit to the distributed computing network (151), transaction messages that include telemetry data (107).
  • Telemetry data may include any information that could be useful to identifying the location of the UAV, the operating parameters of the UAV, or the status of the UAV. Examples of telemetry data include but are not limited to GPS coordinates, instrument readings (e.g., airspeed, altitude, altimeter, turn, heading, vertical speed, attitude, turn and slip), and operational readings (e.g., pressure gauge, fuel gauge, battery level).
  • the control device (120) includes a processor (122) coupled to a memory (124), a display device (132), and communication circuitry (134).
  • the display device (132) may be a liquid crystal display (LCD) screen, a touch screen, another type of display device, or a combination thereof.
  • the communication circuitry (134) includes a transmitter and a receiver or a combination thereof (e.g., a transceiver).
  • the communication circuitry (134) (or the processor (122)) is configured to encrypt outgoing message(s) using a private key associated with the control device (120) and to decrypt incoming message(s) using a public key of a device (e.g., the UAV (102) or the server (140)) that sent the incoming message(s).
  • a device e.g., the UAV (102) or the server (140)
  • communication between the UAV (102), the control device (120), and the server (140) are secure and trustworthy (e.g., authenticated).
  • the processor (122) is configured to execute instructions from the memory (124) to perform various operations.
  • the instructions also include control instructions (130) that include instmctions or code that cause the control device (120) to generate control data to transmit to the UAV (102) to enable the control device (120) to control one or more operations of the UAV (102) during a particular time period, as further described herein.
  • the instmctions also include deconfliction instmctions (139) that include receiving flight path data for a first unmanned aerial vehicle (UAV), wherein the flight path data indicates a first flight path that traverses a geographic cell assigned to the deconfliction controller; determining, by a deconfliction module, whether the first flight path conflicts with at least one second flight path of at least one second UAV, wherein the at least one second flight path also traverses the geographic cell; and providing, in dependence upon the determination, first navigation instmctions for one or more UAVs.
  • UAV unmanned aerial vehicle
  • the deconfliction instructions (139) are further configured for determining that the first flight path conflicts with the at least one of second flight path and providing, to at least one of the first UAV and the second UAV, rerouting instmctions for a rerouted flight path that avoids the conflict.
  • the first UAV and the at least one second UAV are coordinated by a server and the method further comprises transmitting one or more rerouted flight paths to a server.
  • the deconfliction instmctions (139) are further configured for receiving a flight path approval request and providing a flight path approval response to the first UAV.
  • the memor (124) of the control device (102) also includes communication instmctions (131) that when executed by the processor (122) cause the processor (122) to transmit to the distributed computing network (151), transaction messages that include control instructions (130) or deconfliction instructions (139) that are directed to the UAV (102).
  • the transaction messages are also transmitted to the UAV and the UAV takes action (e.g., adjusting flight operations), based on the information (e.g., control data) in the message.
  • the server (140) includes a processor (142) coupled to a memory (146), and communication circuitry (144).
  • the communication circuitry (144) includes a transmitter and a receiver or a combination thereof (e.g., a transceiver).
  • the communication circuitry (144) (or the processor (142)) is configured to encrypt outgoing message(s) using a private key associated with the server (140) and to decrypt incoming message(s) using a public key of a device (e.g., the UAV (102) or the control device (120)) that sent the incoming message(s).
  • the outgoing and incoming messages may be transaction messages that include information associated with the UAV.
  • communication between the UAV (102), the control device (120), and the server (140) are secure and trustworthy (e.g., authenticated).
  • the processor (142) is configured to execute instructions from the memory (146) to perform various operations.
  • the instructions include route instructions (148) comprising computer program instructions for aggregating data from disparate data servers, virtualizing the data in a map, generating a cost model for paths traversed in the map, and autonomously selecting the optimal route for the UAV based on the cost model.
  • the route instructions (148) are configure to partition a map of a region into geographic cells, calculate a cost for each geographic cell, wherein the cost is a sum of a plurality of weighted factors, determine a plurality of flight paths for the UAV from a first location on the map to a second location on the map, wherein each flight path traverses a set of geographic cells, determine a cost for each flight path based on the total cost of the set of geographic cells traversed, and select, in dependence upon the total cost of each flight path, an optimal flight path from the plurality of flight paths.
  • the route instructions (148) are further configured to obtain data from one or more data servers regarding one or more geographic cells, calculate, in dependence upon the received data, an updated cost for each geographic cell traversed by a current flight path, calculate a cost for each geographic cell traversed by at least one alternative flight path from the first location to the second location, determine that at least one alternative flight path has a total cost that is less than the total cost of the current flight path, and select a new optimal flight path from the at least one alternative flight paths.
  • the route instructions (148) may also include instructions for storing the parameters of the selected optimal flight path as route information (110).
  • the route information may include waypoints marked by GPS coordinates, arrival times for waypoints, pilot assignments.
  • the server (140) may be configured to transmit the route information (110) to the UAV (102).
  • the instructions may also include control instructions (150) that include instructions or code that cause the server (140) to generate control data to transmit to the UAV (102) to enable the server (140) to control one or more operations of the UAV (102) during a particular time period, as further described herein.
  • the memory (146) of the server (140) also includes communication instructions (147) that when executed by the processor (142) cause the processor (142) to transmit to the distributed computing network (151), transaction messages that include control instructions (150) or route instructions (148) that are directed to the UAV (102).
  • the distributed computing network (151) of FIG. 1 includes a plurality of computers (157).
  • An example computer (158) of the plurality of computers (157) is show n and includes a processor (152) coupled to a memory (154), and communication circuitry (153).
  • the communication circuitry (153) includes a transmitter and a receiver or a combination thereof (e.g., a transceiver).
  • the communication circuitry (153) (or the processor (152)) is configured to encrypt outgoing message(s) using a private key associated with the computer (158) and to decrypt incoming message(s) using a public key of a device (e.g., the UAV (102), the control device (120), or the server (140)) that sent the incoming message(s).
  • a device e.g., the UAV (102), the control device (120), or the server (140)
  • the outgoing and incoming messages may be transaction messages that include information associated with the UAV.
  • communication between the UAV (102), the control device (120), the server (140), and the distributed computing network (151) are secure and trustworthy (e.g., authenticated).
  • the processor (145) is configured to execute instructions from the memory (154) to perform various operations.
  • the memory (154) includes a blockchain manager (155) that includes computer program instructions for recording data associated with the UAV (102).
  • the blockchain manager (155) includes computer program instructions that when executed by the processor (152) cause the processor (152) to receive a transaction message associated with a UAV.
  • the blockchain manager may receive transaction messages from the UAV (102), the control device (120), or the server (140).
  • other entities e.g., a service repair technician
  • the blockchain manager (155) also includes computer program instructions that when executed by the processor (152) cause the processor (152) to use the information within the transaction message to create a block of data; and store the created block of data in a blockchain data stmcture (156) associated with the UAV.
  • the blockchain manager may also include instructions for determining whether to service an unmanned aerial vehicle (UAV).
  • the blockchain manager (155) also includes computer program instructions that when executed by the processor (152) cause the processor to receive from a user, a request for information regarding the UAV; in response to receiving the request, retrieve from a blockchain data structure associated with the UAV, data associated with the information requested; and based on the retrieved data, respond to the user.
  • the memory (154) includes a smart contract controller (161) that includes computer program instructions for determining whether to sendee the UAV (102).
  • the smart contract controller (161) includes computer program instructions that when executed by the processor (152) cause the processor (152) to access one or more parameters associated with a UAV.
  • the smart contract controller (161) determines whether the one or more parameters satisfies one or more conditions for fulfillment of a smart contract.
  • the smart contract controller (161) indicates a requirement for the UAV to receive a service operation.
  • the smart contract controller (161) determines whether a UAV has a particular requirement to receive a particular service operation. In response to determining that the UAV has the particular requirement to receive the particular service operation, the smart contract controller (161) directs the UAV to receive the particular service operation.
  • the UAV (102), the control device (120), and server (140) are communicatively coupled via a network (118).
  • the network (118) may include a satellite network or another type of network that enables wireless communication between the UAV (102), the control device (120), the server (140), and the distributed computing network (151).
  • the control device (120), the server (140) communicate with the UAV (102) via separate networks (e.g., separate short range networks.
  • minimal (or no) manual control of the UAV (102) may be performed, and the UAV (102) may travel from the origin to the destination without incident.
  • one or more pilots may control the UAV (102) during a time period, such as to perform object avoidance or to compensate for an improper UAV operation.
  • the UAV (102) may be temporarily stopped, such as during an emergency condition, for recharging, for refueling, to avoid adverse weather conditions, responsive to one or more status indicators from the UAV (102), etc.
  • the route information (110) may be updated (e.g., via a subsequent blockchain entry, as further described herein) by route instructions (148) executing on the UAV (102), the control device (120), or the server (140)).
  • the updated route information may include updated waypoints, updated time periods, and updated pilot assignments.
  • the route information is exchanged using a blockchain data structure.
  • the blockchain data structure may be shared in a distributed manner across a plurality of devices of the system (100), such as the UAV (102), the control device (120), the server (140), and any other control devices or UAVs in the system (100).
  • each of the devices of the system (100) stores an instance of the blockchain data structure in a local memory of the respective device.
  • each of the devices of the system (100) stores a portion of the shared blockchain data structure and each portion is replicated across multiple of the devices of the system (100) in a manner that maintains security of the shared blockchain data structure as a public (i.e., available to other devices) and incorruptible (or tamper evident) ledger.
  • the blockchain (156) is stored in a distributed manner in the distributed computing network (151).
  • the blockchain data structure may include, among other things, route information associated with the UAV (102), the telemetry data (107), the control instructions (130), the deconfliction instructions (139), and the route instructions (148).
  • the route information (110) may be used to generate blocks of the blockchain data structure (156).
  • a sample blockchain data structure (300) is illustrated in FIGs. 3A-3C. Each block of the blockchain data structure (300) includes block data and other data, such as availability data, route data, telemetry data, service information, incident reports, etc.
  • the block data of each block includes information that identifies the block (e.g., a block ID) and enables the devices of the system (100) to confirm the integrity of the blockchain data structure (300).
  • the block data also includes a timestamp and a previous block hash.
  • the timestamp indicates a time that the block was created.
  • the block ID may include or correspond to a result of a hash function (e.g., a SHA256 hash function, a RIPEMD hash function, etc.) based on the other information (e.g., the availability data or the route data) in the block and the previous block hash (e.g., the block ID of the previous block). For example, in FIG.
  • the blockchain data structure (300) includes an initial block (Bk_0) (302) and several subsequent blocks, including a block Bk_l (304), a block Bk_2 (306), a block BK_3 (307), a block BK_4 (308), a block BK_5 (309), and a block Bk_n (310)
  • the initial block Bk_0 (302) includes an initial set of availability data or route data, a timestamp, and a hash value (e.g., a block ID) based on the initial set of availability data or route data.
  • the block Bk_l (304) also may include a hash value based on the other data of the block Bk_l (304) and the previous hash value from the initial block Bk_0 (302).
  • the block Bk_2 (306) other data and a hash value based on the other data of the block Bk_2 (306) and the previous hash value from the block Bk_l (304).
  • the block Bk_n (310) includes other data and a hash value based on the other data of the block Bk_n (310) and the hash value from the immediately prior block (e.g., a block Bk_n-1).
  • This chained arrangement of hash values enables each block to be validated with respect to the entire blockchain; thus, tampering with or modifying values in any block of the blockchain is evident by calculating and verifying the hash value of the final block in the block chain. Accordingly, the blockchain acts as a tamper-evident public ledger of availability data and route data for the system (100).
  • each block of the blockchain data structure (300) includes some information associated with aUAV (e.g., availability data, route information, telemetry data, incident reports, updated route information, maintenance records, etc.).
  • the block Bk_l (304) includes availability data that includes a user ID (e.g., an identifier of the mobile device, or the pilot, that generated the availability data), a zone (e.g., a zone at which the pilot will be available), and an availability time (e.g., a time period the pilot is available at the zone to pilot a UAV).
  • the block Bk_2 (306) includes route information that includes a UAV ID, a start point, an end point, waypoints, GPS coordinates, zone markings, time periods, primary pilot assignments, and backup pilot assignments for each zone associated with the route.
  • the block BK_3 (307) includes telemetry data, such as a user ID (e.g., an identifier of the UAV that generated the telemetry data), a battery level of the UAV; a GPS position of the UAV; and an altimeter reading.
  • a UAV may include many types of information within the telemetry data that is transmitted to the blockchain managers of the computers within the distributed computing network (151).
  • the UAV is configured to periodically broadcast to the network (118), a transaction message that includes the UAV’s current telemetry data.
  • the blockchain managers of the distributed computing network receive the transaction message containing the telemetry data and store the telemetry data within the blockchain (156).
  • FIG. 3B also depicts the block BK_4 (308) as including updated route information having a start point, an endpoint, and a plurality of zone times and backups, along with a UAV ID.
  • the control device (120) or the server (140) may determine that the route of the UAV should be changed. For example, the control device or the server may detect that the route of the UAV conflicts with a route of another UAV or a developing weather pattern. As another example, the control device or the server many determine that the priority level or concerns of the user have changed and thus the route needs to be changed. In such instances, the control device or the server may transmit to the UAV, updated route information, control data, or navigation information.
  • Transmitting the updated route information, control data, or navigation information to the UAV may include broadcasting a transaction message that includes the updated route information, control data, or navigation information to the network (118).
  • the blockchain manager (155) in the distributed computing network (151), retrieves the transaction message from the network (118) and stores the information within the transaction message in the blockchain (156).
  • FIG. 3C depicts the block BK 5 (309) as including data describing an incident report.
  • the incident report includes a user ID; a warning message; a GPS position; and an altimeter reading.
  • a UAV may transmit a transaction message that includes an incident report in response to the UAV experiencing an incident. For example, if during a flight mission, one of the UAV s propellers failed, a warning message describing the problem may be generated and transmitted as a transaction message.
  • FIG. 3C also depicts the block BK_n (310) that includes a maintenance record having a user ID of the service provider that serviced the UAV; flight hours that the UAV had flown when the service was performed; the service ID that indicates the type of service that was performed; and the location that the service was performed.
  • UAV must be serviced periodically.
  • the service provider may broadcast to the blockchain managers in the distributed computing network, a transaction message that includes service information, such as a maintenance record.
  • Blockchain managers may receive the messages that include the maintenance record and store the information in the blockchain data structure.
  • a digital and immutable record or logbook of the UAV may be created. This type of record or logbook may be particularly useful to a regulatory agency and an owner/operator of the UAV.
  • the server (140) includes software that is configured to receive telemetry information from an airborne UAV and track the UAV’s progress and status.
  • the server (140) is also configured to transmit in-flight commands to the UAV. Operation of the control device and the server may be carried out by some combination of a human operator and autonomous software (e.g., artificial intelligence (AI) softw are that is able to perform some or all of the operational functions of a typical human operator pilot).
  • AI artificial intelligence
  • the route instructions (148) cause the server (140) to plan a flight path, generate route information, dynamically reroute the flight path and update the route information based on data aggregated from a plurality of data servers.
  • the server (140) may receive air traffic data (167) over the network (119) from the air traffic data server (160), weather data (177) from the weather data server (170), regulatory data (187) from the regulatory data server (180), and topographical data (197) from the topographic data server (190).
  • air traffic data (167) over the network (119) from the air traffic data server (160)
  • weather data (177) from the weather data server (170
  • regulatory data from the regulatory data server (180)
  • topographical data (197) from the topographic data server (190).
  • other data servers useful in flight path planning of a UAV may also provide data to the server (140) over the network (101) or through direct communication with the server (140).
  • the air traffic data server (160) may include a processor (162), memory (164), and communication circuitry (168).
  • the memory (164) of the air traffic data server (160) may include operating instructions (166) that when executed by the processor (162) cause the processor to provide the air traffic data (167) about the flight paths of other aircraft in a region, including those of other UAVs.
  • the air traffic data may also include real-time radar data indicating the positions of other aircraft, including other UAVs, in the immediate vicinity or in the flight path of a particular UAV.
  • Air traffic data servers may be, for example, radar stations, airport air traffic control systems, the FAA, UAV control systems, and so on.
  • the weather data server (170) may include a processor (172), memory (174), and communication circuitry (178).
  • the memory (174) of the weather data server (170) may include operating instructions (176) that when executed by the processor (172) cause the processor to provide the weather data (177) that indicates information about atmospheric conditions along the UAV’s flight path, such as temperature, wind, precipitation, lightening, humidity, atmospheric pressure, and so on.
  • Weather data servers may be, for example, the National Weather Service (NWS), the National Oceanic and Atmospheric Administration (NOAA), local meteorologists, radar stations, other aircraft, and so on.
  • the regulatory data server (180) may include a processor (182), memor (184), and communication circuitry (188).
  • the memory (184) of the weather data server (180) may include operating instructions (186) that when executed by the processor (182) cause the processor provide the regulatory data (187) that indicates information about laws and regulations governing a particular region of airspace, such as airspace restrictions, municipal and state laws and regulations, permanent and temporary no-fly zones, and so on.
  • Regulatory- data servers may include, for example, the FAA, state and local governments, the Department of Defense, and so on.
  • the topographical data server (190) may include a processor (192), memory (194), and communication circuitry (198).
  • the memory (194) of the topographical data server (190) may include operating instructions (196) that when executed by the processor (192) cause the processor to provide the topographical data that indicates information about terrain, places, structures, transportation, boundaries, hydrography, orthoimagery, land cover, elevation, and so on.
  • Topographic data may be embodied in, for example, digital elevation model data, digital line graphs, and digital raster graphics.
  • Topographic data servers may include, for example, the United States Geological Survey or other geographic information systems (GISs).
  • the server (140) may aggregate data from the data servers (160, 170, 180, 190) using application program interfaces (APIs), syndicated feeds and extensible Markup Language (XML), natural language processing, JavaScript Object Notation (JSON) servers, or combinations thereof. Updated data may be pushed to the server (140) or may be pulled on-demand by the server (140).
  • the FAA may be an important data server for both airspace data concerning flight paths and congestion as well as an important data server for regulatory data such as permanent and temporary airspace restrictions.
  • the FAA provides the Aeronautical Data Delivery Service (ADDS), the Aeronautical Product Release API (APRA), System Wide Information Management (SWIM), Special Use Airspace information, and Temporary Flight Restrictions (TFR) information, among other data.
  • the National Weather Service (NWS) API allows access to forecasts, alerts, and observations, along with other weather data.
  • NWS National Weather Service
  • the USGS Seamless Server provides geospatial data layers regarding places, structures, transportation, boundaries, hydrography, orthoimagery, land cover, and elevation. Readers of skill in the art will appreciate that various governmental and non-govemmental entities may act as data servers and provide access to that data using APIs, JSON, XML, and other data formats.
  • the server (140) can communicate with a UAV (102) using a variety of methods.
  • the UAV (102) may transmit and receive data using Cellular, 5G, SublGHz, SigFox, WiFi networks, or any other communication means that would occur to one of skill in the art.
  • the network (119) may comprise one or more Local Area Networks (LANs), Wide Area Networks (WANs), cellular networks, satellite networks, internets, intranets, or other networks and combinations thereof.
  • the network (119) may comprise one or more wired connections, wireless connections, or combinations thereof.
  • the arrangement of servers and other devices making up the exemplary system illustrated in FIG. 1 are for explanation, not for limitation. Data processing systems useful according to various embodiments of the present invention may include additional servers, routers, other devices, and peer-to-peer architectures, not shown in FIG. 1, as will occur to those of skill in the art.
  • Networks in such data processing systems may support many data communications protocols, including for example TCP (Transmission Control Protocol), IP (Internet Protocol), HTTP (HyperText Transfer Protocol), and others as will occur to those of skill in the art.
  • TCP Transmission Control Protocol
  • IP Internet Protocol
  • HTTP HyperText Transfer Protocol
  • Various embodiments of the present invention may be implemented on a variety of hardware platforms in addition to those illustrated in FIG. 1.
  • FIG. 2 sets forth a block diagram illustrating another implementation of a system (200) for accessing data associated with an unmanned aerial vehicle.
  • the system (200) of FIG. 2 shows an alternative configuration in which one or both of the UAV (102) and the server (140) may include route instructions (148) for generating route information.
  • the UAV (102) and the control device (120) may retrieve and aggregate the information from the various data sources (e.g., the air traffic data server (160), the weather data server (170), the regulatory data server (180), and the topographical data server (190)).
  • the route instructions may be configured to use the aggregated information from the various source to plan and select a flight path for the UAV (102).
  • the network (418) may include a satellite network or another type of network that enables wireless communication between the UAVs (102, 103, 105), the provider participant device (450), and the distributed computing network (151).
  • the UAVs (102, 103, 105), the provider participant device (450), and the distributed computing network (151) communicated with each other via separate networks (e.g., separate short range networks.
  • FIG. 4 is a block diagram illustrating a particular implementation of a system (400) for determining whether to service an unmanned aerial vehicle.
  • the system (400) includes the first UAV (102) of FIGs. 1-2, a second UAV (103), athird UAV (105), the distributed computing network (151) of FIGs. 1-2, and a provider participant device (450) coupled for communication to a network (418).
  • the provider participant device (450) includes a processor (442) coupled to communication circuitry (444) and a memory (446).
  • the memory (446) includes operating instructions (448) which are configured to generate service information (449) and transmit via the communication circuitry (444), a transaction message that includes the service information (449).
  • a provider participant device may be a device that is used by a provider participant to log and transmit a record of the service that is performed and associated with a UAV. Examples of provider participants include but are not limited to maintenance technicians and repair shops; infrastructure providers (e.g., providers of UAV storage facilities and parking spots); and insurance providers (e.g., insurance companies that provide insurance for flight missions).
  • the technician at the service repair shop may enter the UAV’s information into the provider participant device along with a selection of “replaced battery” as a description of the service that was performed.
  • the provider participant device may encapsulate this information along with additional information, such as the flight hours of the UAV, within the service information (449).
  • the provider participant device may broadcast a transaction message that includes the service information (449) to the distributed computing network.
  • the blockchain managers of the distributed computing network may create a block that includes the service information and store the block in the blockchain (156).
  • FIG. 5 sets forth a flow chart illustrating an exemplary method for determining whether to service an unmanned aerial vehicle (UAV).
  • the method of FIG. 5 includes accessing (502), by a smart contract controller (501) executing on a device (503) of a UAV transportation ecosystem, one or more parameters (550) associated with a UAV (505).
  • a smart contract controller is a series of computer program instructions that are executable by a processor to facilitate performance of a smart contract.
  • a smart contract is a computerized transaction protocol that defines one or more conditions and specifies the operations that are performed in response to one or more parameters satisfying the one or more conditions.
  • one or more parameters (550) associated with a UAV (505) may be carried out by acquiring data indicating the one or more parameters associated with the UAV.
  • Parameters associated with a UAV may define, represent, or measure the state of one or more components of the UAV or the use of one or more components of the UAV.
  • parameters associated with a UAV may include but are not limited to a total flight time; amount of operation time of a particular component since last service of the particular component; wear estimate for a component; replacement interval count for a component; use count for a component; date and time of last software updated; version of software or firmware; etc. Readers of skill in the art that a variety of data associated with a UAV may be measured, calculated, determined, and detected. As explained above, this data may be stored in various devices in the UAV transportation ecosystem in a variety of formats including within a blockchain data structure.
  • the smart contract controller (501) may access this data by requesting and receiving the data from one or more devices in the UAV transportation ecosystem.
  • the smart contract controller is executing on a device that has direct access to the data that indicates the one or more parameters associated with the UAV.
  • the smart contract controller may execute on a computer that also stores a copy of the blockchain data structure associated with the UAV that is the subject of the smart contract being facilitated by the smart contract controller.
  • the smart contract controller of the present disclosure may execute on a variety of devices of the UAV transportation ecosystem including but not limited to a UAV (e.g., the UAV (102) of FIG. 1); computers (e.g., the computers (158) of FIG.
  • a distributed computing network e.g., the distributed computing network (151) of FIG. 1
  • a server e.g., the server (140) of FIG. 1
  • a control device e.g., the control device (120) of FIG. 1
  • the method of FIG. 5 also includes determining (504), by the smart contract controller (501), whether the one or more parameters (550) satisfies one or more conditions (552) for fulfillment of the smart contract (501).
  • a condition may specify what action, event, or value must happen for another action or event to happen.
  • a smart contract may specify the conditions for requiring a UAV to receive a particular service operation. Examples of service operations include but are not limited to replacing or servicing operational components of a UAV (e.g., batteries, rotors, actuators, electrical components, etc.); recharging or refueling; performing a check or examination of a component; and upgrading software or firmware within the UAV.
  • a condition may involve preventative maintenance (e.g., replacing a component before it breaks).
  • a condition of a smart contract may specify terms, values, events, or actions that define a component failure.
  • one or more devices of the UAV transportation may detect that a rotor of a UAV is not operating properly during a flight mission.
  • the one or more devices may generate an alert, an event, or a message that includes data indicating one or more parameters associated with the rotor component.
  • the smart contract controller may access this data and determine, based on the accessed data, that the conditions for replacing the rotor have been fulfilled.
  • Determining (504), by the smart contract controller (501), whether the one or more parameters (550) satisfies one or more conditions (552) for fulfillment of the smart contract (501) may be carried out by comparing values of a parameter with a threshold indicated by a condition of the smart contract; and determining if the value exceeds the threshold indicated by the condition. For example, if the operational time since the replacement of a battery exceeds one hundred hours, the smart contract may specify that the battery must be replaced.
  • determining (504), by the smart contract controller (501), whether the one or more parameters (550) satisfies one or more conditions (552) for fulfillment of the smart contract (501) may be carried out by determining that a specific event indicated by a parameter has occurred; and that event satisfies the condition of the smart contract.
  • a smart contract may require a service operation on the UAV’s communication circuitry if the UAV loses communication with a control device during a flight.
  • the smart contract may require a UAV to receive a software update at the next available service opportunity after a software update has been released.
  • the smart contract controller may determine that a new version of firmware is available and determine that a parameter indicates that the UAV has an out-of-date firmware version.
  • the method of FIG. 5 also includes in response to determining that the one or more parameters (550) satisfies the one or more conditions (552) for fulfillment of the smart contract (501), indicating (506) a requirement (554) for the UAV (505) to receive a service operation. Indicating (506) a requirement (554) for the UAV (505) to receive a service operation may be carried out by generating or creating an alert, an alarm, a data value, or message to represent the requirement. For example, the smart contract controller may transmit a transaction message to other devices in the UAV transportation ecosystem or store the message in the blockchain data structure associated with the UAV.
  • other devices in the UAV transportation ecosystem may receive this transaction message or access the transaction message on the blockchain data structure and determine that the UAV has a requirement to receive a service operation.
  • another smart contract controller may determine that the UAV has a requirement to receive the service operation.
  • a UAV that has a requirement to receive a service operation may be prevented from flying non-maintenance missions until the UAV has received the required service operation.
  • FIG. 6 sets forth a flow chart illustrating an exemplary method for determining whether to service an unmanned aerial vehicle (UAV), according to embodiments of the present disclosure.
  • the exemplary method of FIG. 6 also includes accessing (502), by a smart contract controller (501) executing on a device (503) of a UAV transportation ecosystem, one or more parameters (550) associated with a UAV (505); determining (504), by the smart contract controller (501), whether the one or more parameters (550) satisfies one or more conditions (552) for fulfillment of the smart contract (501); and in response to determining that the one or more parameters (550) satisfies the one or more conditions (552) for fulfillment of the smart contract (501), indicating (506) a requirement (554) for the UAV (505) to receive a sendee operation.
  • a smart contract controller 501
  • the exemplary method of FIG. 6 also includes accessing (502), by a smart contract controller (501) executing on a device (503) of a UAV
  • the exemplary method of FIG. 6 differs from the method of FIG. 5 in that in the method of FIG. 6, accessing (502), by a smart contract controller (501) executing on a device (503) of a UAV transportation ecosystem, one or more parameters (550) associated with a UAV (505) includes receiving (602), from another device (601) of the UAV transportation ecosystem, data (650) indicating the one or more parameters (550). Receiving (602), from another device (601) of the UAV transportation ecosystem, data (650) indicating the one or more parameters (550) may be carried out by the smart contract controller transmitting a request for data indicating the one or more parameters; and receiving in response to the request, the data indicating the one or more parameters.
  • the smart contract controller may be executing on a device that does not have access to the blockchain data structure.
  • the smart contract controller may identify another device (e.g., one of the computers of the distributed computing network (151) of FIG. 1) that possibly has access to the data indicating the one or more parameters; transmit a request for the identified device to access the data; and receive in response to the request, the requested data.
  • FIG. 7 sets forth a flow chart illustrating an exemplary method for determining whether to service an unmanned aerial vehicle (UAV), according to embodiments of the present disclosure.
  • the exemplary method of FIG. 7 also includes accessing (502), by a smart contract controller (501) executing on a device (503) of a UAV transportation ecosystem, one or more parameters (550) associated with a UAV (505); determining (504), by the smart contract controller (501), whether the one or more parameters (550) satisfies one or more conditions (552) for fulfillment of the smart contract (501); and in response to determining that the one or more parameters (550) satisfies the one or more conditions (552) for fulfillment of the smart contract (501), indicating (506) a requirement (554) for the UAV (505) to receive a sendee operation.
  • a smart contract controller 501
  • the exemplary method of FIG. 7 also includes accessing (502), by a smart contract controller (501) executing on a device (503) of a UAV
  • the exemplary method of FIG. 7 differs from the method of FIG. 5 in that in the method of FIG. 7, accessing (502), by a smart contract controller (501) executing on a device (503) of a UAV transportation ecosystem, one or more parameters (550) associated with a UAV (505) includes examining (702) one or more transactions (752) on a blockcham data structure (750) associated with the UAV.
  • the one or more transactions (752) indicate the one or more parameters (550).
  • Examining (702) one or more transactions (752) on a blockchain data structure (750) associated with the UAV may be carried out by directly or indirectly searching the blockchain data structure for transaction that indicate the one or more parameters.
  • FIG. 8 sets forth a flow chart illustrating an exemplary method for determining whether to service an unmanned aerial vehicle (UAV), according to embodiments of the present disclosure.
  • the exemplary method of FIG. 8 also includes accessing (502), by a smart contract controller (501) executing on a device (503) of a UAV transportation ecosystem, one or more parameters (550) associated with a UAV (505); determining (504), by the smart contract controller (501), whether the one or more parameters (550) satisfies one or more conditions (552) for fulfillment of the smart contract (501); and in response to determining that the one or more parameters (550) satisfies the one or more conditions (552) for fulfillment of the smart contract (501), indicating (506) a requirement (554) for the UAV (505) to receive a sendee operation.
  • the exemplary method of FIG. 8 differs from the method of FIG. 5 in that in the method of FIG. 8 also includes selecting (802), by the smart contract controller (501), a service provider to perform the service operation. Selecting (802), by the smart contract controller (501), a service provider to perform the service operation may be carried out by using terms within the smart contract to identify from a plurality of service providers, a particular service to perform the required service operation. For example, the smart contract may specify a maximum price to be paid for the service operation or a minimum turn-around time for the sendee provider to provide the service operation. The smart contract may also specify a bidding process in which the smart contract controller requests the location, rates, and availability of service providers to perform the service operation.
  • the smart contract controller may select the optimal service provider that satisfies the requirements according to a selection algorithm (e.g., fastest turn-around time; nearest location; lowest cost; or some combination of turn-around time, location, and cost) for selecting a service provider.
  • a selection algorithm e.g., fastest turn-around time; nearest location; lowest cost; or some combination of turn-around time, location, and cost
  • FIG. 9 sets forth a flow chart illustrating an exemplary method for determining whether to service an unmanned aerial vehicle (UAV), according to embodiments of the present disclosure.
  • the exemplary method of FIG. 9 also includes accessing (502), by a smart contract controller (501) executing on a device (503) of a UAV transportation ecosystem, one or more parameters (550) associated with a UAV (505); determining (504), by the smart contract controller (501), whether the one or more parameters (550) satisfies one or more conditions (552) for fulfillment of the smart contract (501); and in response to determining that the one or more parameters (550) satisfies the one or more conditions (552) for fulfillment of the smart contract (501), indicating (506) a requirement (554) for the UAV (505) to receive a sendee operation.
  • the exemplary method of FIG. 9 differs from the method of FIG. 5 in that in the method of FIG. 9, in response to determining that the one or more parameters (550) satisfies the one or more conditions (552) for fulfillment of the smart contract (501), indicating (506) a requirement (554) for the UAV (505) to receive a service operation includes storing (902) a transaction message (950) to a blockchain data structure (952) associated with the UAV. Storing (902) a transaction message (950) to a blockchain data structure (952) associated with the UAV may be carried out by directly storing the transaction message as a block on the blockchain data structure.
  • FIG. 10 sets forth a flow chart illustrating an exemplary method for determining whether to service an unmanned aerial vehicle (UAV), according to embodiments of the present disclosure. Like the exemplary method of FIG. 5, the exemplary method of FIG.
  • UAV unmanned aerial vehicle
  • 10 also includes accessing (502), by a smart contract controller (501) executing on a device (503) of a UAV transportation ecosystem, one or more parameters (550) associated with a UAV (505); determining (504), by the smart contract controller (501), whether the one or more parameters (550) satisfies one or more conditions (552) for fulfillment of the smart contract (501); and in response to determining that the one or more parameters (550) satisfies the one or more conditions (552) for fulfillment of the smart contract (501), indicating (506) a requirement (554) for the UAV (505) to receive a sendee operation.
  • the exemplary method of FIG. 10 differs from the method of FIG. 5 in that in the method of FIG. 10 includes determining (1002), by the smart contract controller (501), whether the UAV has a particular requirement (1050) to receive a particular service operation. Determining (1002), by the smart contract controller (501), whether the UAV has a particular requirement (1050) to receive a particular service operation may be carried out by accessing a storage location (e.g., the blockchain data structure) that indicates the service operation requirements for a UAV.
  • a storage location e.g., the blockchain data structure
  • the exemplary method of FIG. 10 further differs from the method of FIG. 5 in that in the method of FIG. 10 also includes in response to determining that the UAV has the particular requirement (1050) to receive the particular service operation directing (1004) the UAV to receive the particular service operation. Directing (1004) the UAV to receive the particular service operation may be carried out by instructing the UAV to fly to a service provider to receive the required service operation.
  • FIG. 11 sets forth a flow chart illustrating an exemplary method for determining whether to service an unmanned aerial vehicle (UAV), according to embodiments of the present disclosure.
  • the exemplary method of FIG. 11 also includes accessing (502), by a smart conlracl controller (501) executing on a device (503) of a UAV transportation ecosystem, one or more parameters (550) associated with a UAV (505); determining (504), by the smart contract controller (501), whether the one or more parameters (550) satisfies one or more conditions (552) for fulfillment of the smart contract (501); in response to determining that the one or more parameters (550) satisfies the one or more conditions (552) for fulfillment of the smart contract (501), indicating (506) a requirement (554) for the UAV (505) to receive a sendee operation; determining (1002), by the smart contract controller (501), whether the UAV has a particular requirement (1050) to receive a particular service operation;
  • the exemplary method of FIG. 11 differs from the method of FIG. 10 in that in the method of FIG. 11, in response to determining that the UAV has the particular requirement (1050) to receive the particular service operation, directing (1004) the UAV to receive the particular service operation includes creating (1102) a flight plan (1150) for the UAV to fly to a service provider. Creating (1102) a flight plan (1150) for the UAV to fly to a service provider may be carried out by identifying possible routes for the UAV to fly to a service provider; selecting a route; and specifying the route in the form of a flight plan.
  • the exemplary method of FIG. 11 differs from the method of FIG. 10 in that in the method of FIG. 11, in response to determining that the UAV has the particular requirement (1050) to receive the particular service operation, directing (1004) the UAV to receive the particular service operation includes getting (1104) an approval (1152) for the flight plan (1150). Getting (1104) an approval (1152) for the flight plan (1150) may be carried out by transmitting to an approval organization or agency (e.g., the FAA), the flight plan with a request for approval; and receiving a response from the approval organization or agency that approves the flight plan.
  • an approval organization or agency e.g., the FAA
  • the exemplary method of FIG. 11 differs from the method of FIG. 10 in that in the method of FIG. 11, in response to determining that the UAV has the particular requirement (1050) to receive the particular service operation, directing (1004) the UAV to receive the particular service operation includes directing (1106) the UAV to perform the flight plan (1150). Directing (1106) the UAV to perform the flight plan (1150) may be carried out by authorizing the UAV to fly a maintenance flight mission in accordance with the flight plan; and instructing the UAV to perform the maintenance flight mission.
  • FIG. 12 sets forth a flow chart illustrating an exemplary method for determining whether to service an unmanned aerial vehicle (UAV), according to embodiments of the present disclosure.
  • the exemplary method of FIG. 12 also includes accessing (502), by a smart contract controller (501) executing on a device (503) of a UAV transportation ecosystem, one or more parameters (550) associated with a UAV (505); determining (504), by the smart contract controller (501), whether the one or more parameters (550) satisfies one or more conditions (552) for fulfillment of the smart contract (501); and in response to determining that the one or more parameters (550) satisfies the one or more conditions (552) for fulfillment of the smart contract (501), indicating (506) a requirement (554) for the UAV (505) to receive a sendee operation.
  • a smart contract controller 501
  • the exemplary method of FIG. 12 also includes accessing (502), by a smart contract controller (501) executing on a device (503) of a UAV
  • the exemplary method of FIG. 12 differs from the method of FIG. 5 in that in the method of FIG. 12 further includes in response to determining that the one or more parameters (550) satisfies the one or more conditions (552) for fulfillment of the smart contract (501), indicating (1202) within a blockchain data structure (1250) that the UAV is not clear for flights associated with non-maintenance missions until the UAV has received the service operation. Indicating (1202) within a blockchain data structure (1250) that the UAV is not clear for flights associated with non-maintenance missions until the UAV has received the service operation may be carried out by storing a value, flag, indicator that the UAV is not clear for flights associated with non-maintenance missions.
  • FIG. 13 sets forth a flow chart illustrating an exemplary method for determining whether to service an unmanned aerial vehicle (UAV), according to embodiments of the present disclosure.
  • the exemplary method of FIG. 13 also includes accessing (502), by a smart contract controller (501) executing on a device (503) of a UAV transportation ecosystem, one or more parameters (550) associated with a UAV (505); determining (504), by the smart contract controller (501), whether the one or more parameters (550) satisfies one or more conditions (552) for fulfillment of the smart contract (501); and in response to determining that the one or more parameters (550) satisfies the one or more conditions (552) for fulfillment of the smart contract (501), indicating (506) a requirement (554) for the UAV (505) to receive a sendee operation.
  • a smart contract controller 501
  • the exemplary method of FIG. 13 also includes accessing (502), by a smart contract controller (501) executing on a device (503) of a UAV
  • the exemplary method of FIG. 13 differs from the method of FIG. 5 in that in the method of FIG. 13 further includes determining (1302) whether the UAV has received the service operation. Determining (1302) whether the UAV has received the service operation may be carried out by examining transaction messages on a blockchain data structure; and determining whether an authorized sendee provider has verified that the required service operation was performed.
  • the exemplary method of FIG. 13 differs from the method of FIG. 5 in that in the method of FIG. 13 further also includes in response to determining that the UAV has received the service operation, clearing (1304) the UAV for flights associated with non-maintenance missions. Clearing (1304) the UAV for flights associated with non-maintenance missions may be carried out by storing a value, flag, indicator that the UAV is clear for flights associated with non-maintenance missions.
  • FIG. 14 sets forth a flow chart illustrating an exemplary method for determining whether to service an unmanned aerial vehicle (UAV).
  • the method of FIG. 14 includes determining (1402), by a smart contract controller (1401) executing on a device (1403) of a UAV transportation ecosystem, whether a UAV (1405) has a particular requirement (1450) to receive a particular service operation. Determining (1402), by a smart contract controller (1401) executing on a device (1403) of a UAV transportation ecosystem, whether a UAV (1405) has a particular requirement (1450) to receive a particular service operation may be carried out by accessing a storage location (e.g., the blockchain data structure) that indicates the service operation requirements for a UAV.
  • a storage location e.g., the blockchain data structure
  • the method of FIG. 14 also includes in response to determining that the UAV (1405) has the particular requirement (1450) to receive the particular service operation, directing (1404) the UAV (1405) to receive the particular service operation.
  • directing (1404) the UAV (1405) to receive the particular service operation may be carried out by instructing the UAV to fly to a service provider to receive the required service operation.
  • FIG. 15 sets forth a flow chart illustrating an exemplary method for determining whether to service an unmanned aerial vehicle (UAV), according to embodiments of the present disclosure.
  • the exemplary method of FIG. 15 also includes determining (1402), by a smart contract controller (1401) executing on a device (1403) of a UAV transportation ecosystem, whether a UAV (1405) has a particular requirement (1450) to receive a particular service operation; and includes in response to determining that the UAV (1405) has the particular requirement (1450) to receive the particular service operation, directing (1404) the UAV (1405) to receive the particular service operation.
  • the exemplary method of FIG. 15 differs from the method of FIG. 14 in that in the method of FIG. 15, directing (1404) the UAV (1405) to receive the particular service operation includes creating (1502) a flight plan (1550) for the UAV (1505) to a service provider.
  • Creating (1502) a flight plan (1550) for the UAV (1505) to a service provider may be carried out by identifying possible routes for the UAV to fly to a service provider; selecting a route; and specifying the route in the form of a flight plan.
  • the exemplary method of FIG. 15 differs from the method of FIG. 14 in that in the method of FIG. 15, directing (1404) the UAV (1405) to receive the particular service operation includes getting (1504) an approval (1552) for the flight plan (1550). Getting (1504) an approval (1552) for the flight plan (1550) may be carried out by transmitting to an approval organization or agency (e.g., the FAA), the flight plan with a request for approval; and receiving a response from the approval organization or agency that approves the flight plan.
  • an approval organization or agency e.g., the FAA
  • the exemplary method of FIG. 15 differs from the method of FIG. 14 in that in the method of FIG. 15, directing (1404) the UAV (1405) to receive the particular service operation includes directing (1506) the UAV (1405) to perform the flight plan (1550). Directing (1506) the UAV (1405) to perform the flight plan (1550) may be carried out by authorizing the UAV to fly a maintenance flight mission in accordance with the flight plan; and instructing the UAV to perform the maintenance flight mission.
  • FIG. 16 sets forth a flow chart illustrating an exemplary method for determining whether to service an unmanned aerial vehicle (UAV), according to embodiments of the present disclosure.
  • the exemplary method of FIG. 16 also includes determining (1402), by a smart contract controller (1401) executing on a device (1403) of a UAV transportation ecosystem, whether a UAV (1405) has a particular requirement (1450) to receive a particular service operation; and includes in response to determining that the UAV (1405) has the particular requirement (1450) to receive the particular service operation, directing (1404) the UAV (1405) to receive the particular service operation.
  • the exemplary method of FIG. 16 differs from the method of FIG. 14 in that in the method of FIG. 16 further includes determining (1602) whether the UAV (1405) has received the particular service operation. Determining (1602) whether the UAV (1405) has received the particular service operation may be carried out by examining transaction messages on a blockchain data structure; and determining whether an authorized service provider has verified that the required service operation was performed.
  • the exemplary method of FIG. 16 differs from the method of FIG. 14 in that in the method of FIG. 16 further includes in response to determining that the UAV (1405) has received the particular service operation, clearing (1604) the UAV (1405) for flights associated with non-maintenance missions.
  • clearing (1604) the UAV (1405) for flights associated with non-maintenance missions may be carried out by storing a value, flag, indicator that the UAV is clear for flights associated with non-maintenance missions.
  • Exemplary embodiments of the present invention are described largely in the context of a fully functional computer system for determining whether to service a UAV. Readers of skill in the art will recognize, however, that the present invention also may be embodied in a computer program product disposed upon computer readable storage media for use with any suitable data processing system.
  • Such computer readable storage media may be any storage medium for machine-readable information, including magnetic media, optical media, or other suitable media. Examples of such media include magnetic disks in hard drives or diskettes, compact disks for optical drives, magnetic tape, and others as will occur to those of skill in the art. Persons skilled in the art will immediately recognize that any computer system having suitable programming means will be capable of executing the steps of the method of the invention as embodied in a computer program product.
  • the present invention may be a system, a method, and/or a computer program product.
  • the computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
  • the computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device.
  • the computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing.
  • a non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD- ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing.
  • a computer readable storage medium, as used herein, is not to be construed as being transitory signals per se. such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber optic cable), or electrical signals transmitted through a wire.
  • Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network.
  • the network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers.
  • a network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
  • Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages.
  • the computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
  • Hardware logic including programmable logic for use with a programmable logic device (PLD) implementing all or part of the functionality previously described herein, may be designed using traditional manual methods or may be designed, captured, simulated, or documented electronically using various tools, such as Computer Aided Design (CAD) programs, a hardware description language (e.g., VHDL or Verilog), or a PLD programming language. Hardware logic may also be generated by a non-transitory computer readable medium storing instructions that, when executed by a processor, manage parameters of a semiconductor component, a cell, a library of components, or a library of cells in electronic design automation (EDA) software to generate a manufacturable design for an integrated circuit.
  • CAD Computer Aided Design
  • EDA electronic design automation
  • These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instmctions stored therein comprises an article of manufacture including instmctions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • each block in the flowchart or block diagrams may represent a module, segment, or portion of instmctions, which comprises one or more executable instructions for implementing the specified logical function(s).
  • the functions noted in the block may occur out of the order noted in the figures.
  • two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Theoretical Computer Science (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Development Economics (AREA)
  • Remote Sensing (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Game Theory and Decision Science (AREA)
  • Educational Administration (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Traffic Control Systems (AREA)

Abstract

Selon un mode de réalisation particulier, l'invention concerne la détermination de l'opportunité d'entretenir un véhicule aérien sans pilote qui comprend l'accès, par un contrôleur de contrat intelligent s'exécutant sur un dispositif d'un écosystème de transport de véhicule aérien sans pilote, à un ou plusieurs paramètres associés à un véhicule aérien sans pilote. Selon ce mode de réalisation, le contrat intelligent détermine si le ou les paramètres satisfont une ou plusieurs conditions pour l'exécution du contrat intelligent. En réponse à la détermination du fait que le ou les paramètres satisfont la ou les conditions pour l'exécution du contrat intelligent, le contrat intelligent indique une exigence pour que le véhicule aérien sans pilote reçoive une opération d'entretien.
EP20771733.1A 2019-09-02 2020-09-01 Détermination de l'opportunité d'entretenir un véhicule aérien sans pilote Pending EP4014216A1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201962894887P 2019-09-02 2019-09-02
US202062961052P 2020-01-14 2020-01-14
PCT/US2020/048888 WO2021046021A1 (fr) 2019-09-02 2020-09-01 Détermination de l'opportunité d'entretenir un véhicule aérien sans pilote

Publications (1)

Publication Number Publication Date
EP4014216A1 true EP4014216A1 (fr) 2022-06-22

Family

ID=72474022

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20771733.1A Pending EP4014216A1 (fr) 2019-09-02 2020-09-01 Détermination de l'opportunité d'entretenir un véhicule aérien sans pilote

Country Status (2)

Country Link
EP (1) EP4014216A1 (fr)
WO (1) WO2021046021A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023235639A2 (fr) * 2022-03-03 2023-12-07 Skygrid, Llc Satisfaction d'une demande associée à des aspects opérationnels d'une mission de véhicule aérien sans pilote
TW202348668A (zh) 2022-06-10 2023-12-16 美商陶氏全球科技有限責任公司 剛性聚胺甲酸酯發泡體配方及製造適用於低溫應用之纖維強化聚胺甲酸酯發泡體之方法
WO2024049936A1 (fr) 2022-08-31 2024-03-07 Dow Global Technologies Llc Procédé de préparation d'une mousse polymère moulée
US20240118689A1 (en) * 2022-10-05 2024-04-11 Skydio, Inc. Task Management For Unmanned Aerial Vehicles

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9489852B1 (en) * 2015-01-22 2016-11-08 Zipline International Inc. Unmanned aerial vehicle management system
CA3035771A1 (fr) * 2016-09-09 2018-03-15 Walmart Apollo, Llc Systemes et procedes de surveillance de zone geographique par echange de systemes d'outils entre vehicules sans pilote
US10547454B2 (en) * 2017-12-27 2020-01-28 International Business Machines Corporation Managing in-flight transfer of parcels using blockchain authentication

Also Published As

Publication number Publication date
WO2021046021A1 (fr) 2021-03-11

Similar Documents

Publication Publication Date Title
US20220351628A1 (en) Automated mission planning and execution for an unmanned aerial vehicle
US20210065560A1 (en) Utilizing visualization for managing an unmanned aerial vehicle
US11436930B2 (en) Recording data associated with an unmanned aerial vehicle
US20210304621A1 (en) Utilizing unmanned aerial vehicles for emergency response
US11945582B2 (en) Coordinating an aerial search among unmanned aerial vehicles
WO2021046021A1 (fr) Détermination de l'opportunité d'entretenir un véhicule aérien sans pilote
US20210304625A1 (en) Monotonic partitioning in unmanned aerial vehicle search and surveillance
US20240078913A1 (en) Automated preflight evaluation of an unmanned aerial vehicle configuration
US20220392352A1 (en) Unmanned aerial vehicle module management
US20220383762A1 (en) Increasing awareness of an environmental condition for an unmanned aerial vehicle
US20220351631A1 (en) Unmanned aerial vehicle response to object detection
US20220351626A1 (en) Multi-objective mission planning and execution for an unmanned aerial vehicle
US11875690B2 (en) Decentralized oracles in an unmanned aerial vehicle (UAV) transportation ecosystem
US20240233559A1 (en) Accessing information regarding an unmanned aerial vehicle
US20220011784A1 (en) Making a determination regarding consensus using proofs of altitude of unmanned aerial vehicles
US20230017922A1 (en) Incentivizing unmanned aerial vehicle use
US20220382272A1 (en) Predictive maintenance of an unmanned aerial vehicle
WO2024081451A2 (fr) Affichage d'informations relatives au spectre électromagnétique pour la navigation d'un aéronef sans pilote (uav)

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20220314

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)