IOT DRONE FLEET

• US 20190332974A1
• Filed: 04/27/2018
• Published: 10/31/2019
• Est. Priority Date: 04/27/2018
• Status: Active Grant

• Current Assignee: Dish Technologies LLC (Echostar Corporation)
• Original Assignee: Dish Technologies LLC (Echostar Corporation)
• Inventors: Karatekeli, Kayhan, Raghavan, Srinath, Tilaye, Swapnil
• Granted Patent: US 10,860,953 B2
• Time in Patent Office: Days
• CPC Class Codes: B64U 2101/20 for use as communications relays, e.g. high-altitude platforms
• CPC Class Codes: B64U 2101/30 for imaging, photography or videography
• CPC Class Codes: B64U 2201/00 UAVs characterised by their flight controls
• CPC Class Codes: B64U 30/20 Rotors; Rotor supports
• CPC Class Codes: G05D 1/0027 involving a plurality of vehicles, e.g. fleet or convoy travelling fleet control of land vehicles from a control room G05D1/0297; traffic control systems for road vehicles G08G1/00; for marine craft G08G3/00; for aircraft G08G5/00
• CPC Class Codes: G05D 1/0094 involving pointing a payload, e.g. camera, weapon, sensor, towards a fixed or moving target
• CPC Class Codes: G05D 1/689 Pointing payloads towards fixed or moving targets positioning towed, pushed or suspended implements G05D1/672
• CPC Class Codes: G05D 1/692 involving a plurality of disparate vehicles
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 30/0645 Rental transactions; Leasing transactions
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04W 12/08 Access security

Abstract

Apparatus, systems, processes, and computer-readable mediums for facilitating the use of drones are described. For one embodiment, such a system includes a user element having a user application computer program configured to instruct a user interface device to facilitate use of user data and use of mission parameter(s) for a proposed drone mission. An owner element includes an owner application computer program configured to facilitate use of owner data and use of at least one drone parameter. A fleet system element is communicatively coupled to the user element and to the owner element and includes a computer system processor configured to facilitate use of a fleet record and use of at least one fleet parameter.

Claims

1. A system for facilitating drone usage, comprising:

a user element, comprising;

a user application program including non-transient first computer executable instructions configured to instruct a user interface device to perform one or more user operations including;

a first user operation facilitating use of user data;

a second user operation facilitating use of at least one mission parameter for a proposed mission;

an owner element, comprising;

an owner application program including non-transient second computer executable instructions configured to instruct an owner interface device to perform one or more owner operations including;

a first owner operation facilitating use of owner data;

a second owner operation facilitating use of at least one drone parameter; and

a fleet system element, communicatively coupled to each of the user element and the owner element, comprising;

a system processor configured to execute non-transient third computer executable instructions configured to perform one or more system operations including;

a first system operation facilitating use of a fleet record; and

a second system operation facilitating use of at least one fleet parameter.

2. The system of claim 1, wherein the user operations include:

a third user operation facilitating use of at least one flight control.

3. The system of claim 2, wherein the user operations include:

a fourth user operation facilitating use of at least one payload control.

4. The system of claim 3, wherein the owner operations include:

a third owner operation facilitating use of at least one drone control.

5. The system of claim 4, wherein the owner operations include:

a fourth owner operation facilitating use of at least one payload parameter.

6. The system of claim 5, wherein the owner operations include:

a fifth owner operation facilitating use of at least one flight control; and

a sixth owner operation facilitating use of at least one payload control.

7. The system of claim 6,

wherein the system operations include at least one of:

a third system operation facilitating use of at least one fleet control;

a fourth system operation facilitating use of at least one fleet payload parameter;

a fifth system operation facilitating use of one or more of the first owner operation, the second owner operation, the third owner operation, the fourth owner operation, the fifth owner operation, and the sixth owner operation.

8. The system of claim 1,

wherein the first computer executable instructions are configured to instruct the user interface device to perform one or more user operations including:

a fifth user operation for verifying whether a user element identified for the proposed mission is permitted to execute the proposed mission; and

for a verified user element, communicating the proposed mission to the system element.

9. The system of claim 8,

wherein the third computer executable instructions are configured to instruct the system processor to perform one or more system operations including:

determining whether at least one drone is available for release to perform the proposed mission;

determining whether release of the at least one available drone is approved by the owner element associated with the at least one available drone; and

releasing at least one of the user element, the owner element, and the system element to perform the proposed mission.

10. The system of claim 9,

wherein the first computer executable instructions are configured to instruct the user interface device to perform one or more user operations including:

determining whether a revised mission parameter is available for a non-verified user element; and

when a revised mission parameter is available,

determining whether the revised mission parameter is acceptable to the user element;

updating the proposed mission with the revised mission parameter; and

communicating the proposed mission with the revised mission parameter to the system element.

11. The system of claim 1, wherein the at least one mission parameter includes information provided by the user element, for the proposed mission including at least one of:

an identifier,

a date;

a time;

a location; and

an intended use.

12. The system of claim 1, wherein the at least one drone parameter includes information provided by the owner element, with respect to a given drone, including at least one of:

a usage window;

a home base identification;

at least one acceptable use; and

at least one operational constraint.

13. The system of claim 1, wherein the fleet record includes information provided by the fleet system element, with respect to the proposed mission, including for at least one drone identified for use in the proposed mission, at least one of:

a reservation requirement;

a rental term;

insurance;

certification requirements; and

usage restrictions.

14. The system of claim 1, wherein the at least one fleet parameter includes information provided by the fleet system element, with respect to the proposed mission, including for at least one drone identified for use in the proposed mission, at least one of:

a usage window;

a home base identification;

at least one acceptable use; and

at least one operational constraint.

15. The system of claim, comprising:

a government system element, communicatively coupled to the fleet system element, including non-transient first computer executable instructions configured to facilitate operations including at least one of;

drone control;

air traffic control;

permitting of at least one of users, owners, and operators;

certifying drones; and

emergency response.

16. A process for facilitating usage of a drone, via a user interface device configured to execute a user application program, comprising:

receiving a first input identifying at least one user record associated with a first user;

receiving a second input including mission parameters for a proposed drone mission;

in response to the first input and the second input, first determining whether the proposed drone mission is acceptable;

when the first determining is positive, communicating the proposed drone mission to a fleet system element;

when the first determining is negative, presenting at least one of;

a first option for revising at least one revised mission parameter;

a second option for use of an alternative user for the proposed mission;

a third option for the first user to qualify for the proposed mission; and

based on a selection of one or more of the first option, the second option and the third option;

revising the proposed mission;

second determining whether the revised proposed mission is acceptable; and

when the second determining is positive, communicating the revised proposed mission to the fleet system element.

17. The process of claim 16,

wherein the fleet system element is configured to communicate at least one of the proposed drone mission and the revised proposed mission to at least one drone owner;

and

upon receiving approval from the at least one drone owner for at least one of the proposed drone mission and the revised proposed mission, the process further comprising;

enabling use, via the user interface device, of a least one flight control for an approved drone;

wherein the at least one flight control is configured based on at least one drone characteristic for the approved drone and based on at least one capability of the user interface device.

18. The process of claim 17, wherein the at least one drone characteristic is identified in at least one drone parameter record provided by a drone owner element for the approved drone.

19. The process of claim 16, comprising:

enabling use, via the user interface device, of at least one payload control for a payload of the approved drone.

20. The process of claim 19, wherein the payload is at least one of a camera, a basket, and an interpretative guide.