METHOD AND SYSTEM FOR IMPLEMENTING AND ENFORCING A NO-FLY ZONE OR PROHIBITIVE ZONE FOR DRONES AND UNMANNED VEHICLES
20170103659 ยท 2017-04-13
Inventors
Cpc classification
B64U2201/00
PERFORMING OPERATIONS; TRANSPORTING
B64U2201/104
PERFORMING OPERATIONS; TRANSPORTING
G05D1/106
PHYSICS
G01S1/68
PHYSICS
International classification
G05D1/00
PHYSICS
Abstract
In certain areas, if a drone flies into them, may cause danger to people or facilities within the area. In such areas no-fly zones need to be implemented and enforced. A no-fly zone can be indicated or identified by specially transmitted radio signals in or around the no-fly zone. No-fly zones can also be defined using geo-fence data that is provided to a drone. Once a drone detects itself within a no-fly zone, will disable the control from its original operator or from its pre-programmed flying plan at least in part, and be made harmless.
Claims
1. A method of enforcing a no-fly zone for drones, comprising the steps of: determining, by a drone while flying under control of an operator or a pre-programmed flying plan, an entry to a no-fly zone; and performing, by the drone, take-over mode operations; wherein the take-over mode operations ignore the control from the operator or the pre-programmed flying plan at least in part.
2. The method of claim 1, wherein the determining an entry to a no-fly zone comprises at least one of receiving, by an on-board wireless receiver, a no-fly-zone indication signal; calculating, by an on-board wireless receiver, the drone position relative to the no-fly zone based on a plurality of no-fly-zone identification signals received; and detecting, by an on-board controller, that a current location of said drone is within a no-fly zone.
3. The method of claim 2, wherein said detecting a current location within a no-fly zone includes checking the current location against a no-fly-zone definition data.
4. The method of claim 3, wherein the no-fly-zone definition data is represented by geo-fence parameters.
5. The method of claim 3, wherein the no-fly-zone definition data is obtained by the drone through at least one of: receiving, by an on-board wireless receiver, a message that contains the definition data; reading from a hardware module coupled with the drone that pre-stores the definition data; and downloading the definition data onto a storage device on-board of the drone through a network connection.
6. The method of claim 3, wherein the current location is calculated based on parameters from at least one of: an on-board global or regional positioning satellite system receiver; at least one on-board gyro sensor; at least one on-board accelerating sensor; at least one on-board barometer or pressure or pressure difference sensors for obtaining at least one of altitude, airspeed, air velocity, angular airspeed, angular air velocity; a means obtaining wind velocity around said drone; at least one of on-board earth magnetic field sensor; at least one on-board wireless receiver to be able to determine at least one of angle, time, time difference of received wireless signals; an on-board transmitter to be able to transmit a signal for measuring propagation parameters of said signal by at least one off-board receiver; at least one on-board image or light sensors to detect on-sky position of at least one of sun, moon and stars; a means to provide time; and a radar.
7. The method of claim 1, wherein said take-over mode operations include at least one of: the drone is flying according to a de-risk procedure; the drone is flying under the control of a super operator other than the original operator; and the drone is flying under control by a combination of sources but under a final arbitration of a super arbitrator.
8. The method of claim 7, wherein said de-risk procedure includes at least one of stopping an engine; attempting a soft landing; flying away; hovering at current position; and warning.
9. The method of claim 7, wherein said de-risk procedure is obtained by the drone through at least one of over-the-air signals received by an on-board wireless receiver; a hardware module coupled with the drone controller that pre-stores the procedure; and downloading onto an on-board storage device coupled with the drone controller.
10. The method of claim 7, wherein the drone is flying under the control of a super operator further includes an hand-over and control protocol comprising: detecting that the no-fly zone has a super operator on duty; sending a notification message indicating that the drone is ready to be taken over by the super operator; performing default flying procedure while waiting for the super operator's response; if within a predetermined timer period, the super operator did not respond: starting performing automated de-risk procedures; and if, at any time, the super operator responded: stopping performing current operation instructions from other than the super operator; receiving and acknowledging reception of each of control instructions from the super operator; and performing and acknowledging completion of each of control instructions from the super operator.
11. The method of claim 7, wherein the drone is flying under control by a combination of sources but under a final arbitration of a super arbitrator, further includes an hand-over and arbitration protocol comprising: detecting that the no-fly zone has a super arbitration on duty; sending a notification message indicating that the drone control is ready to be arbitrated by the super arbitrator; performing default flying procedure while waiting for super arbitrator's response; if, within a predetermined timer period, the super arbitrator did not respond: starting performing automated de-risk procedures; and if, at any time after the sending step, the super arbitrator responded: forwarding control signals from all sources to the super arbitrator; receiving and acknowledging reception of each of arbitration instructions from the super arbitrator; and performing each of fly instructions selected by the super arbitrator.
12. The method of claim 8, wherein the procedure of flying away is away from a reference point, and the reference point position data is obtained from at least one of: over-the-air signal message, received by an on-board wireless receiver; a hardware module coupled with the drone controller that pre-stores the reference point position data; downloading onto a storage device coupled with the drone controller; and calculating based on a footprint shape of the no-fly zone.
13. The method of claim 8, wherein performing at least one of the procedures of stopping an engine and attempting a soft landing further includes releasing at least one of a parachute and an air bag by the drone.
14. A hardware module for being coupled with a drone controller comprising a data storage device which stores at least one of: permitted fly zone definition data; and no-fly zone definition data.
15. The hardware module of claim 14, wherein the at least one of permitted fly zone definition data and no-fly zone definition data is represented by geo-fence parameters.
16. The hardware module of claim 14, wherein the data storage device further stores at least one of: fly authorization ID; fly authorization valid time; fly authorization expiring time; security digital signature; drone types authorized for use of the hardware module; at least one drone IDs authorized for use of the hardware module; valid time for each of the drone IDs authorized for flying with the hardware module; expiring time for each of the drone IDs authorized for flying with the hardware module; ID of each of the stored at least one of permitted fly zones and no-fly zones; effective time for each of the stored at least one of permitted fly zones and no-fly zones; valid time for each of the stored at least one of permitted fly zones and no-fly zones; expiring time for each of the stored at least one of permitted fly zones and no-fly zones; a type indication for each of the no-fly zones; issuing organization for each of the stored at least one of permitted fly zones and no-fly zones; owner contact information for each of the stored at least one of permitted fly zones and no-fly zones; detour route information around each of the stored no-fly zones; automated de-risk procedure for each of the stored no-fly zones; at least one reference point associated with each of the stored no-fly zones for deriving direction to fly away from the zone; an indicator for availability of a super operator associated with each of the stored no-fly zones; a handover and control protocol for handover by a super operator, associated with each of the stored no-fly zones having a super operator; an expiring time duration for handover by a super operator, associated with each of the stored no-fly zones having a super operator; an indicator for availability of a super arbitrator associated with each of the stored no-fly zones; a hand-over and arbitration protocol for handover by a super arbitrator, associated with each of the stored no-fly zones having a super arbitrator; an expiring time duration for handover by a super arbitrator, associated with each of the stored no-fly zones having a super arbitrator; a special permission to fly into at least one of no-fly zone; a valid time for a special permission to fly into a no-fly zone; a expiring time for a special permission to fly into a no-fly zone; a password to allow activation of a special permission to fly into a no-fly zone; flying limitations to fly into a no-fly zone under a special permission; speed limitations for each of the stored permitted fly zones.
17. An unmanned vehicle, comprising: a controller; a storage medium; computer instructions stored in the storage medium; and the computer instructions being executable by the controller for: detecting whether or not the unmanned vehicle is within at least one of a no-fly zone, no-drive zone, no-sail zone and a prohibitive zone; and if detected positive, causing the unmanned vehicle to enter a special mode of operation that disables the control from at least one of an original operator and an originally programmed traveling plan at least in part.
18. The unmanned vehicle of claim 17 further includes: at least one wireless receiver that is coupled with the controller, for receiving at least one of no-fly-zone indication signals, no-fly-zone identification signals, no-drive-zone indication signals, no-drive-zone identification signals, no-sail-zone indication signals, no-sail-zone identification signals, prohibitive zone indication signals, prohibitive zone identification signals, global positioning satellite signals, regional positioning satellite signals; and whereby the controller is operable to determine whether or not the unmanned vehicle is within at least one of a no-fly zone, no-drive zone, no-sail zone and a prohibitive zone based at least in part on the at least one of signals, messages and parameters that the wireless receiver provides to the controller.
19. The unmanned vehicle of claim 17 further includes: a hardware module coupled to the controller, for providing at least geo-fence data that defines at least one of no-fly zones, no-drive zones, no-sail zones and a prohibitive zones; a navigation subsystems, coupled to the controller, for determining the position of the unmanned vehicle; and whereby the controller is operable to detect whether the unmanned vehicle is within at least one of a no-fly zone, no-drive zone, no-sail zone and a prohibitive zone based at least in part on the unmanned vehicle position reported by the navigation subsystem and the geo-fence data provided by the hardware module.
20. The unmanned vehicle of claim 17 further includes: a wireless receiver coupled with the controller, for receiving signals from least one of a super operator and a super arbitrator during the special mode of operation; and a wireless transmitter coupled with the controller, for transmitting signals to at least one of a super operator and a super arbitrator during the special mode of operation.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0013] For a better understanding of the invention and to show more clearly how it may be carried into effect, reference will now be made, by way of example only, to the accompanying drawings which show at least one exemplary embodiment of the invention and in which:
[0014]
[0015]
[0016]
[0017]
DETAILED DESCRIPTION OF THE INVENTION
[0018] It will be appreciated that in the description herein, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those of ordinary skill in the art that the invention may be practiced without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to obscure the invention. Furthermore, this description is not to be considered as limiting the scope of the invention, but rather as merely providing a particular preferred working embodiment thereof.
[0019] In the specification and claims, the terminology drone is used to refer to an unmanned aerial vehicle (UAV), including a remotely piloted aircraft (RPA), or an autonomous aircraft. Furthermore, a drone in this specification also broadly refers to any unmanned vehicles, including unmanned automobiles, boats, submarines, and robots, as well as unmanned all-in-one vehicles (a vehicle that is able to travel in more than one of the spacesair, land, overwater and underwater). Similarly, the terminology of no-fly zone also broadly refers to as no-drive zone on land, no-sail zone over and/or under water, generally, a prohibitive zone.
[0020]
[0021] In another preferred embodiment, the no-fly-zone indication signal further include broadcasting an embedded message that defines the boundary of the no-fly zone using geo-fence parameters such as those based on or in terms of longitude, latitude and altitude; the regulation requires drones that comply to this grade of regulation to support decoding the geo-fence message, and using its on-board global positioning system or regional positioning system receiver (such as GPS/GLONASS/Beidou/Galileo) or other compliant navigation/positioning means to check its location continuously or periodically against the received geo-fence. Once an entry to the no-fly zone is found, the drone must immediately take procedures to leave the no-fly zone in a safe way no matter what its operator or its on-board computer instructs or originally programmed it to do; alternatively, once its position is approaching a no-fly zone, it shall take procedures to avoid entering the no-fly zone no matter what its operator or its on-board computer instructs or originally programmed it to do.
[0022] The no-fly-zone indication signal may be radiated by dedicated transmitter and antenna, it may also be radiated by other types of transmitter and antenna, such as a commercial TV and radio stations, radar, instrument landing system, etc, such as through adding a subcarrier, adding an embedded message, or directly define the signal originally for other purpose as one type of no-fly-zone indication signal. For example, the airport instrument landing system signals may be borrowed and defined as one type of no-fly-zone indication signal.
[0023] In yet another preferred embodiment, instead of using the radiation pattern of an indication signal to specify the boundary of a no-fly zone, the no-fly zone is identified by a plurality of no-fly-zone identification signals transmitted each from a separate antenna, and using the antenna positions to mark the footprint boundary shape of the no-fly zone.
[0024] In an alternative embodiment, instead of using a receiver on-board of a drone to receive the no-fly-zone definition, the no-fly-zone definition is transferred to the drone through other means, including through a hardware module, referred to herein as flying authorization module. A regulation compliant drone is required to detect the presence of a flying authorization module in order to fly, i.e., without a valid flying authorization module a regulation compliant drone shall not be able to fly. The flying authorization module may be physically provided by a regulation authority, or its contents be provided by a regulation authority. Either way, digital signature or other security means may be used to guarantee that the contents are truly from the regulation authority. The flying authorization module may contain an authorization identification of the drone user, so that no matter which physical drone is flying, as long as the particular flying authorization identification is used, its identification owner takes the legal responsibility. The flying authorization module may further contain permitted fly-zone definition data or otherwise contain no-fly-zone definition data such as in the form of geo-fences. During flying, a regulation compliant drone shall, through its navigation means such as GPS, check its current position against permitted fly-zone or no-fly-zone definitions stored in its flying authorization module, and once its position is within a no-fly zone, it shall immediately take procedures to leave the no-fly zone in a safe way no matter what its operator or its on-board computer instructs or originally programmed it to do; alternatively, once its position is approaching a no-fly zone, it shall take procedures to avoid entering the no-fly zone no matter what its operator or its on-board computer instructs or originally programmed it to do. The flying authorization identification as well as the permitted fly-zone or no-fly-zone definition data each may be associated with an expiring date and time, a regulation compliant drone shall check the expiring status and once found expired, it shall not able to fly with it. The permitted fly-zone or no-fly-zone definition data including their expiring time contained in a flying authorization module may be renewed or updated through network or storage media from regulation authorities, and the expiring time of the flying authorization identification may also be renewed through network or storage media from regulation authorities. The flying authorization module may be a plug-in module that can be replaced in field by drone user, such as through a socket installed on a drone, or may be built-in on a drone during manufacturing that cannot be replaced without engineering work.
[0025] In another alternative embodiment, the permitted fly-zone definition data or no-fly-zone definition data such as in the form of geo-fences are stored in memory or data storage device associated with the on-board controller of the drone without a physically separable hardware module. The fly-zone or no-fly-zone definition data are either pre-stored in the controller during manufacturing, or downloaded and/or updated through network or data media onto the controller after manufacturing. The definition data are either from regulation authority or indirectly from the manufacturer that is authorized by the regulation authority. The on-board controller of a drone may also be further loaded with an identification that uniquely identifies the authorized user. All the functions of the fly-zone or no-fly-zone definition data, including their expiring time if available, as well as the identification, including its expiring time if available, are identical to what are described hereinabove, except without a separate hardware module.
[0026] In general several types of no-fly zones are needed. One type is long-term no-fly zones, such as those set up around nuclear plants, which are set up all time over fixed locations; another type of no-fly zones have fixed location but have fixed on-off schedule, such as one that is set up over a single runway of a small airport that is closed every night; the third type is ad-hoc and mostly short-term no-fly zones such as those set up at sites of wildfires to allow firefighting aircrafts to operate. The embodiment hereinabove that uses a no-fly-zone indication signal or identification signal to define is suitable for enforcing all these types of no-fly zones since the indication/identification signal may change over time, a drone supporting such indication/identification signals is able to receive the change right away. In the embodiments hereinabove that use a flying authorization module or built-in storage to store the definition data of no-fly zones, in order to fully support ad-hoc no-fly zones, the drone must include a receiver that supports receiving and updating the definitions of ad-hoc no-fly zones wirelessly. Preferably a drone supports both pre-downloaded definitions as well as instantaneous indication and identification or real-time updating.
[0027] The no-fly-zone definition, no matter it is broadcasted as definition messages, pre-stored or downloaded as definition data, may further include such attributes as effective time duration or time of day and week, issuing organization and owner contact information; in addition, it may be desirable to further include detour route information to fly around the zone, especially when multiple no-fly zones are close to each other. A no-fly-zone issuer (i.e., owner) is responsible to report the setup of the zone to the regulating authority, and update the no-fly-zone database at the authority for drone users to download. A drone shall record and report to the regulating authority the no-fly zones that it had encountered once the drone has a chance to connect to the network (e.g., after retrieval) so that illegal no-fly zones can be found and corrected. Drones have wireless transmitters may also report it wirelessly.
[0028] For drones with pre-programmed flying plan, it is desirable while programming the plan or at least before the drone is lunched and the flying plan starts to run, the flying plan programming tool, the flying plan loading tool, or the drone controller would provide warnings to the operator if the plan has violated any no-fly-zone requirements.
[0029] When a regulation compliant drone detects itself within a no-fly zone, the drone shall immediately enter a special mode, herein referred to as take-over mode, in which the original operator no longer has control to the drone (at least in part), and the drone is either controlled by an automated de-risk procedure or by a super operator who represents the owner of the no-fly zone. In one preferred embodiment the automated de-risk procedure is broadcasted through the no-fly-zone indication/identification signal as a message, and is decoded by an on-board wireless receiver of the drone. In another embodiment, the automated de-risk procedure is pre-stored in association with the zone definition data, e.g., pre-stored in a flying authorization module, or pre-stored with the built-in controller of the drone. The pre-stored automated de-risk procedure may be on a zone-by-zone basis, i.e., different zones may be stored with different instructions, or otherwise, be stored uniformly identical for all zones. The de-risk procedure may instruct the drone to perform at least one of the operations: 1) stop the engine(s) and crash the drone at current locationif supported, the drone may release a parachute and/or an air bag for safer touching to the ground; 2) attempt to land at current location as soft as possible; 3) fly away from a reference point as provided in terms of latitude and longitude; 4) hover at current location and attitude if supported, and wait for being captured by a capturing net or otherwise being made harmless. Among these options, option 1) usually is used in a guard zone of a protected core zone, where crashing would not cause danger to the protected targets; option 2) implements a relatively soft landing for purpose to reduce risks of damages to facilities on ground, and usually not for avoiding damages to the drone; option 3) can be used for drones that are equipped with navigation means such as GPS, so that the drone is able to find the direction away from the provided reference point; if option 3 is given in the procedure but a reference point data is not provided, a default reference point can be used, which is the geometry center of the footprint shape of the entire no-fly zone; option 4 is for drones that support hovering, the no-fly zone owner may dispatch a manned or unmanned craft to retrieve the drone using a capturing net, or use other means to make the drone harmless. The de-risk procedure may further include an indication whether to allow the drone to resume normal operation mode after leaving the no-fly-zone.
[0030] Preferably, the no-fly zones may be divided into multiple tiers, for example, in addition to the core area to enforce highest degree of protection, the core zone may be surrounded by zones of lower degree of protections, such as guard zone and warning zone, etc. Associated with each zone or subzone, a type indication data may be provided together with the zone definition data, to indicate that it is a core zone, guard zone, or a warning zone, etc. In some zones, such as a warning zone, the de-risk procedure can be less tough than higher degree of zones, for example, it may just provide a warning to the operator and let the operator take actions to avoid the no-fly zone. The warning may be triggered by detection of its location against pre-stored or received geo-fence definition of the zone, and its contents retrieved from the de-risk procedure pre-stored or broadcasted in association with the zone definition. Once the warning message is triggered and retrieved, the message would be indicated through a user interface to the operator, such as in the form of one or multiple types of visible and/or audible indication signals. In some zones, the de-risk procedure may still allow the user to retrieve the drone after completed the de-risk procedure, however, in some higher degree zones, the drone may have to be confiscated after completing the de-risk procedure, depending on the de-risk procedure associated with the zone or sub-zone definition.
[0031]
[0032] When a regulation compliant drone detects itself within a no-fly zone, and enters a take-over mode, the drone should support accepting remote control instructions from a super operator through an on-board wireless receiver, and support standardized handover and control protocols for the super operator control, if the drone supports such grade of regulation. Preferably such drones should also be equipped with a wireless transmitter, when the no-fly-zone indication/identification signal or the no-fly-zone definition message indicates that the no-fly zone has a super operator on duty, the on-board controller should automatically send a notification message through the transmitter to indicate that the drone is ready to be taken over by the super operator, if desired by the super operator. The super operator thus may take over the control of the drone, and then, for example, control the drone to land or crash itself at desired safe location, or fly away along a safe route. The on-board controller and transmitter should acknowledge to the super operator for each of the control instructions received and performed. Under the discretion of the super operator, the drone may be granted its normal operation mode again and get control back to the original operator after leaving the no-fly zone. If the drone is not taken over by the super operator in response to the notification message, after a pre-determined period of time, the drone shall execute the automated de-risk procedures received or pre-stored. A timer can be used to control the execution of this fall-back action. If the super operator does take over after the automated de-risk procedures have started, the procedures shall stop immediately and gives the control to the super operator.
[0033] In an alternative embodiment, when entering a take-over mode, the drone is flying under control by a combination of sources but under a final arbitration of a super arbitrator. For example, the original operator may continue to send fly instructions if the drone was remotely controlled, the automated de-risk procedures also is sending pre-determined fly instructions, and eventually which of these instructions takes effect is determined by the super arbitrator. The arbitrator may accept the original operator's fly instruction if it does not conflict with the arbitrator's intention. Otherwise, the arbitrator may deny the original operator's instruction, the control then may be given to the pre-determined automated de-risk procedure, or be given to the super operator. The super arbitrator and the super operator may also be the same person or same group of persons.
[0034] While drones are banned to fly over a no-fly zone, some drones may be a part of the mission and given exceptions to allow them fly over. For example, when most drones are banned over firefighting site of wildfire, some drones might be on their firefighting mission. In order to allow authorized drones to fly into the no-fly zones, special electronic pass may be given to the drones. The electronic pass may be implemented by a special flying authorization module attached to the drone in question that is coded to ignore the specific zone, or by a standalone permit module attached thereto. It may also be implemented by broadcasting a message in the no-fly-zone indication/identification signal to identity certain drone ID as permitted. Alternatively, the special permission can be given as a pass-code provided by the regulation authority or by the no-fly-zone owner that can be input into the drone controller so that the drone controller can verify and accept the permission. A no-fly zone can also be partitioned into multiple grades of sub-zones to selectively give permissions to certain drones.
[0035]
[0036] Certain terms are used to refer to particular components. As one skilled in the art will appreciate, people may refer to a component by different names. It is not intended to distinguish between components that differ in name but not in function.
[0037] The terms including and comprising are used in an open-ended fashion, and thus should be interpreted to mean including, but not limited to. The terms example and exemplary are used simply to identify instances for illustrative purposes and should not be interpreted as limiting the scope of the invention to the stated instances.
[0038] Also, the term couple in any form is intended to mean either a direct or indirect connection through other devices and connections.
[0039] It should be understood that various modifications can be made to the embodiments described and illustrated herein, without departing from the invention, the scope of which is defined in the appended claims.