Authentication systems and methods for generating flight regulations

• US 11,120,456 B2
• Filed: 09/28/2017
• Issued: 09/14/2021
• Est. Priority Date: 03/31/2015
• Status: Active Grant

• Current Assignee: SZ DJI Technology Co., Ltd. (d/b/a DJI) (iFlight Technology Company Limited)
• Original Assignee: SZ DJI Technology Co., Ltd. (d/b/a DJI) (iFlight Technology Company Limited)
• Inventors: Gong, Ming, Dai, Jin, Cui, Hao, Wang, Xiaodong, Huang, Han, Wu, Jun, Fan, Wei, Ma, Ning, Rong, Xinhua, Lin, Xingsen
• Primary Examiner(s): Shudy, Angelina
• Application Number:
  US15/718,548
• Publication Number:
  US 20180082308A1
• Time in Patent Office: 1,447 Days
• Field of Search: 701 3
• CPC Class Codes: B64C 39/024 of the remote controlled vehicle type, i.e. RPV
• CPC Class Codes: B64U 10/13 Flying platforms
• CPC Class Codes: B64U 2201/102 adapted for flying in formations
• CPC Class Codes: B64U 2201/20 Remote controls
• CPC Class Codes: B64U 30/20 Rotors; Rotor supports
• CPC Class Codes: G05D 1/0022 characterised by the communication link data switching networks in general H04L12/00
• CPC Class Codes: G06F 16/29 Geographical information databases
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 2221/2117 User registration
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06Q 30/018 Certifying business or products
• CPC Class Codes: G08G 5/0008 with other aircraft
• CPC Class Codes: G08G 5/0013 with a ground station
• CPC Class Codes: G08G 5/0026 located on the ground
• CPC Class Codes: G08G 5/0034 Assembly of a flight plan
• CPC Class Codes: G08G 5/0039 Modification of a flight plan
• CPC Class Codes: G08G 5/0043 Traffic management of multiple aircrafts from the ground G08G5/003 takes precedence; data processing specially designed for resource management, e.g. scheduling or allocating time, human or machine resources G06Q10/06
• CPC Class Codes: G08G 5/0052 for cruising combined instruments indicating more than one navigational value G01C23/00
• CPC Class Codes: G08G 5/0056 : in an emergency situation, e.g. hijacking
• CPC Class Codes: G08G 5/006 : in accordance with predefined flight zones, e.g. to avoid prohibited zones
• CPC Class Codes: G08G 5/0069 : specially adapted for an unmanned aircraft
• CPC Class Codes: G08G 5/0078 : for monitoring traffic from the aircraft radar or analogous systems specially adapted for traffic control G01S13/91
• CPC Class Codes: G08G 5/0082 : for monitoring traffic from a ground station radar or analogous systems specially adapted for traffic control G01S13/91
• CPC Class Codes: G08G 5/0086 : for monitoring terrain radar or analogous systems specially adapted for terrain avoidance G01S13/935
• CPC Class Codes: G08G 5/0091 : for monitoring atmospheric conditions radar or analogous systems specially adapted for meteorological use G01S13/95; meteorology G01W
• CPC Class Codes: H04L 63/101 : Access control lists [ACL]
• CPC Class Codes: H04L 67/12 : specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04W 4/021 : Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: Y04S 40/20 : Information technology specific aspects, e.g. CAD, simulation, modelling, system security

Abstract

Systems and methods for UAV safety are provided. An authentication system may be used to confirm UAV and/or user identity and provide secured communications between users and UAVs. The UAVs may operate in accordance with a set of flight regulations. The set of flight regulations may be associated with a geo-fencing device in the vicinity of the UAV.

Claims

1. A method comprising:

determining whether software on an unmanned aerial vehicle (UAV) or on a device associated with the UAV has been updated within a grace period after a user of the UAV is notified to update the software;

determining one or more operational limits on the UAV when the software on the UAV or on the device associated with the UAV has not been updated within the grace period, the one or more operational limits causing at least one of a sensor of the UAV, a payload carried by the UAV, a power supply of the UAV, or a communication unit of the UAV to be inoperable; and

controlling the UAV according to the one or more operational limits.

2. The method of claim 1, wherein an updated version of the software is transmitted to and executed by the UAV or the device associated with the UAV only when the UAV or a user of the UAV has been registered with a control entity.

3. The method of claim 1, wherein controlling the UAV includes preventing the UAV from being operable when the software on the UAV or on the device associated with the UAV has not been updated within the grace period.

4. The method of claim 1, wherein an updated version of the software is used as part of a user authentication process.

5. The method of claim 4, wherein the UAV is operable only after a user is authenticated through the updated version of the software.

6. The method of claim 1, wherein the updated version of the software regulates the operation of the UAV.

7. The method of claim 6, wherein determining the one or more operational limits on the UAV further comprises determining one or more flight restrictions of the UAV.

8. The method of claim 7, wherein determining the one or more flight restrictions of the UAV comprises determining one or more geo-fencing or fly-zone restrictions.

9. The method of claim 7, wherein the one or more flight restrictions of the UAV are in compliance with at least one of statutes, laws, guidelines or protocols.

10. The method of claim 1, further comprising:

receiving an updated version of the software by an application, the application being a smart phone application or a web-based application.

11. The method of claim 1, further comprising:

receiving an updated version of the software transmitted from a server located remotely from the UAV or the device associated with the UAV.

12. The method of claim 1, wherein an updated version of the software is transmitted to the device associated with the UAV, and the device associated with the UAV is configured to re-transmit the updated version of the software to the UAV, and the device associated with the UAV is a remote controller or a user terminal.

13. The method of claim 1, wherein communications are provided between the UAV and a server and between the device associated with the UAV and the server, and wherein the server operates to transmit an updated version of the software to the UAV or the device associated with the UAV.

14. The method of claim 1, further comprising:

receiving an updated version of the software periodically at regular or irregular time intervals.

15. The method of claim 1, further comprising:

receiving an updated version of the software in response to an event or a condition.

16. The method of claim 15, wherein the event comprises a request for software update from a user.

17. The method of claim 15, wherein the event comprises that the UAV or the user are registered with a control entity.

18. The method of claim 15, wherein the condition comprises the UAV or the device associated with the UAV being powered on and connected to a server that transmits the updated version of the software to the UAV or the device associated with the UAV.

19. A system comprising one or more of a sensor, communication unit, payload, or power supply, said system further comprising one or more processors configured to individually or collectively perform steps comprising:

determining whether software on an unmanned aerial vehicle (UAV) or on a device associated with the UAV has been updated within a grace period after a user of the UAV is notified to update the software;

determining one or more operational limits on the UAV when the software on the UAV or on the device associated with the UAV has not been updated within the grace period, the one or more operational limits causing at least one of the sensor, the payload, the power supply, or the communication unit of the UAV to be inoperable; and

controlling the UAV according to the one or more operational limits.

20. A non-transitory computer readable medium containing program instructions that, when executed by one or more processors, cause the one or more processors to perform a method comprising:

determining whether software on an unmanned aerial vehicle (UAV) or on a device associated with the UAV has been updated within a grace period after a user of the UAV is notified to update the software;

determining one or more operational limits on the UAV when the software on the UAV or on the device associated with the UAV has not been updated within the grace period, the one or more operational limits causing at least one of a sensor of the UAV, a payload carried by the UAV, a power supply of the UAV, or a communication unit of the UAV to be inoperable; and

controlling the UAV according to the one or more operational limits.