Abstract: A system and method for multi-level breach detection of UAV, is disclosed. A sensing device is configured to generate a first breach signal upon detecting a first event of interest. A flight controller is configured to generate a second breach signal upon detecting a second event of interest. A controller is configured to detect the first and second breach signal with low latency. A GPS module is configured to provide time and geolocation information to the controller. A storage device is configured to store first event of interest and the second event of interest with tags of time and geolocation information. A communication module is configured to connect the controller to pre-destined servers. The controller is configured to periodically check network availability over the communication module at a pre-defined time interval, and synchronize the first and second event of interest with tags to the pre-destined servers. Fig 1.
Claims:We Claim:
1. A system for multi-level breach detection of Unmanned Aerial Vehicle (UAV), comprising:
a sensing device configured to generate a first breach signal upon detecting a first event of interest;
a flight controller configured to generate a second breach signal upon detecting a second event of interest;
a controller in communication with the flight controller configured to detect the first and second breach signal from the sensing device and the flight controller, respectively, with low latency;
a GPS module in communication with the controller configured to provide time and geolocation information;
a storage device in communication with the controller configured to store first event of interest and the second event of interest with tags of time and geolocation information, and
a communication module in communication with the controller configured to connect the controller to one or more pre-destined servers,
wherein the controller is configured to:
periodically check network availability over the communication module at a pre-defined time interval, and
synchronize the first event of interest and the second event of interest with tags to one or more pre-destined servers.
2. The system of claim 1, wherein the sensing device is an electromechanical switch.
3. The system of claim 1, wherein the sensing device is disposed at an interior periphery of disassembly junction of the UAV.
4. The system of claim 1, further comprises a main power source and an auxiliary power source in communication with the flight controller, controller, sensing device, GPS module and communication module.
5. The system of claim 1, wherein the first event of interest represents a breach in the housing and the second event of interest represents a breach in flight controller and controller of the UAV.
6. The system of claim 1, wherein the controller is configured to autonomously execute one or more responsive actions based on at least one of the first breach signal or second breach signal.
7. The system of claim 1, wherein the flight controller is configured to detect switching of main power source to the auxiliary power source.
8. The system of claim 1, wherein the flight controller is configured to maintain a communication line between the controller and the flight controller in known state on receiving power from the auxiliary power source.
9. The system of claim 1, wherein the flight controller attempts to detach from the controller, thereby resulting in change of state of communication lines between the flight controller and the controller, indicating the occurrence of the second event of interest.
10. The system of claim 1, wherein the controller is configured to identify the change of state of communication lines between the flight controller and controller as the second event of interest. , Description:BACKGROUND OF THE INVENTION
A. Technical field
[0001] The present invention generally relates to detection of breach in Unmanned Aerial Vehicle (UAV), and more specifically relates to a system and method for detecting various level of hardware breaches in UAV.
B. Description of related art
[0002] With UAV operations getting ratified at many parts of the world, the regulatory authorities in those parts laid down certain kind of guidelines to which the UAV should adhere. An On-board computer (OBC) on the UAV technically facilitates adhering to such guidelines with much feasibility. However, drones operating outside a trusted environment are vulnerable to two level of breach, which includes breach at the periphery of drone and breach of the critical components that are Flight Controller (FC) and On-Board Computer (OBC). Few cases/scenarios of unauthorized hardware tampering of the drones outside the trusted environments like manufacturers' facilities are discussed as follows. In one case, unscrupulous parties often take legitimate electronic products and replace components to illegally upgrade or otherwise modify those products. In another case, the control of the UAV is intercepted in-flight such as by intercepting, jamming and/or imitating global positioning or Global Navigation Satellite System signals (e.g. pirate signals) and directing the drone to a surrogate landing zone. In these kinds of tampering, all trust on the hardware, which met certain compliance during its manufacturing cycle, is lost.
[0003] . Conventional method utilizes a warranty-void sticker, which just reflects the breach by visual inspection of torn sticker, with no aspects of latency and qualitative responses respected. Few existing patents attempted to address the aforesaid problem are explained in detail as follows.
[0004] US8928471 of Gerald A. Morgan et al. entitled “Methods and Systems Related to Remote Tamper Detection” discloses a tamper detection unit connected to an onboard device receiving backup power from an asset battery. The onboard device losses power upon tampering, and utilizes energy from the backup power to send an alert related to tampering to a remote location.
[0005] WO2018227477 of Liu Lijian et al. entitled “Control Method for Unmanned Aerial Vehicle After the Unmanned Aerial Vehicle has been Disassembled and Assembled and Unmanned Aerial Vehicle” discloses a mechanical sensing unit disposed within the unmanned aerial vehicle for detection of unauthorized replacement or tampering of devices within the unmanned aerial vehicle. After performing disassembling and assembling operation, the sensing unit determines whether the performed operation is unauthorized for prohibiting the unmanned aerial vehicle from taking off or moving.
[0006] US9266610 of Jeffrey H. Knapp et al. entitled “Controlled Range and Payload for Unmanned Vehicles, and Associated Systems and Methods” discloses an unmanned vehicle system to prevent and/or detect tampering and provide security to the system. A Trusted Platform Module (TPM) technology used in the unmanned vehicle system is controlled by the commerce department. The unmanned vehicle is configured to send communication signal to a ground control station or satellite in response to detecting tampering activities. An Avionics Module containing: a) the commercial GPS receiver b) an auto pilot computer; and c) a regulated power conditioning system are factory sealed to prevent tampering. Data communication to and from the Avionics Module requires matching encryption keys to function. The avionics module is factory programmed using specific compiled code and trusted platform module encryption techniques.
[0007] However, the existing prior arts lack to provide an effective, real-time sensing systems to detect damage events of interest immediately or as the event happens, such as an impact from a ballistic object, a tamper event, a physical impact, or other damage events which may affect structural integrity or cause failure of the UAV. Further, the existing prior arts lack to differentiate the level or severity of breach. The undifferentiation could result in transmitting high level alert even for minor level of breach.
[0008] Therefore, there is a need for a system and method for detecting various level of breach in UAV immediately or as the event happens.
SUMMARY OF THE INVENTION
[0009] The present invention provides a system for multi-level hardware breach detection of unmanned aerial vehicle (UAV). The system is configured to detect various level or severity of breach in the UAV and implement an appropriate action based on the level of breach. The system is configured to autonomously report breach event in UAV utilizing remote cellular communication. In case of critical tampering in the UAV, the system is configured to automatically prevent flight of UAV, while also reporting the breach event with remote cellular technology.
[0010] The system comprises a sensing device, a flight controller (FC), a controller or on-board controller (OBC), a GPS module, a storage device and a communication module. The OBC is in communication with the flight controller and one or more pre-destined servers. The communication module is configured to connect the controller to one or more pre-defined servers.
[0011] The sensing device is configured to generate a first breach signal upon detecting a first event of interest or secondary breach. In one embodiment, the sensing device is an electromechanical switch. The flight controller is configured to generate a second breach signal upon detecting a second event of interest or primary breach. The first event of interest represents a periphery level breach and the second event of interest represents critical level breach.
[0012] The controller in communication with the flight controller is configured to detect the first and second breach signal from the sensing device and the flight controller, respectively, with low latency. The GPS module in communication with the controller is configured to provide time and geolocation information. The storage device in communication with the controller is configured to store first event of interest and the second event of interest with tags of time and geolocation information. The system further comprises a main power source and an auxiliary power source in communication with the flight controller, controller, sensing device, GPS module and communication module.
[0013] The secondary breach or periphery level breach is detected using the sensing device placed at the interior, periphery of the disassembly junction of the UAV housing. The sensing device is activated when the disassembly junction of the drone periphery housing is moved apart. Upon activation, the switch sends an electronic signal to the on-board controller (OBC), which detects this signal change with extremely low latency, in the order of milliseconds. Upon detecting the change, the OBC logs this event onto the storage device. The log includes data such as severity of breach, GPS location of breach, time of breach etc.
[0014] During primary breach, the main power source is disconnected from the system. The FC and OBC are powered by the auxiliary power source. As soon as the auxiliary power source is connected to the system, the FC that normally consumes more power makes an electronic signal to OBC and switch to power-saving sleep mode, while holding the state of communication lines between FC and OBC to known states. In this condition, the OBC and FC are attempted to be detached. The state of the said communication lines would change and is detected by the OBC. This change represents the second event of interest. Thereafter, the OBC logs the event with necessary data such as severity of breach, GPS location and time of the event.
[0015] Additionally, in cases of breach between FC and OBC, the OBC on next main power cycle checks the integrity of FC based upon its identity checks, and autonomously decides if the UAV should continue its normal mode of operation, or completely prevent any more flights.
[0016] Other objects, features and advantages of the present invention will become apparent from the following detailed description. It should be understood, however, that the detailed description and the specific examples, while indicating specific embodiments of the invention, are given by way of illustration only, since various changes and modifications within the spirit and scope of the invention will become apparent to those skilled in the art from this detailed description.
BRIEF DESCRIPTION OF DRAWINGS
[0017] The embodiments herein will be better understood from the following detailed description with reference to the drawings, in which:
[0018] FIG. 1 exemplarily illustrates a system for multi-level breach detection of unmanned aerial vehicle (UAV), according to an embodiment of the present invention.
[0019] FIG. 2 exemplarily illustrates a multi-level breach detection method for UAV, according to an embodiment of the present invention.
[0020] FIG. 3 exemplarily illustrates a method for checking the network availability and synching breach logs to servers, according to an embodiment of the present invention.
[0021] FIG. 4 exemplarily illustrates the unmanned aerial vehicle (UAV) incorporated with the multi-level breach detection system, according to an embodiment of the present invention.
DETAILED DESCRIPTION OF EMBODIMENTS
[0023] A description of embodiments of the present invention will now be given with reference to the Figures. It is expected that the present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.
[0024] Referring to FIG. 1, the present invention provides a system 100 for multi-level hardware breach detection of unmanned aerial vehicle (UAV) 400. The system 100 is configured to autonomously report breach events in UAV 400 utilizing remote cellular communication. The system 100 is configured to autonomously report hardware breach events in UAV 400 utilizing remote cellular communication. The system 100 is configured to detect breach and provide appropriate responses with lowest latency by a combination of electronic and mechanical means. The system 100 is configured to detect various level or severity of breach in the UAV 400 and implement an appropriate action autonomously, based on the level of breach. In case of critical tampering in the UAV 400, the system 100 is configured to automatically prevent flight of UAV 400.
[0025] The system 100 comprises a sensing device, a flight controller (FC) 112, a controller or on-board controller (OBC) 118, a GPS module 108, a storage device 106 and a communication module 110. The controller 118 is in communication with the flight controller 112 and one or more pre-destined servers 102. The communication module 110 is configured to connect the controller 118 to one or more pre-defined servers 102. The flight controller 112 and OBC 118 comprises software routines.
[0026] The communication module 110 is a communication network such as the Internet, a local area network (LAN), and a wide area network (WAN), and includes various communication lines such as a telephone network, an Integrated Services Digital Network (ISDN) line, a broad communication network, a leased line network, a mobile communication network, a communication satellite circuit, a community antenna television (CATV) network, and a wireless communication line, and includes internet service providers connecting those various communication lines.
[0027] The system 100 includes a power supply assembly in communication with the sensing device, the flight controller 112, the controller 118, the GPS module 108, the storage device 106 and the communication module 110. The power supply assembly includes a main power source and an auxiliary power source 116. The auxiliary power source 116 could be a built-in battery, and supplies power to the system 100 when the main power source is in “OFF” state.
[0028] The sensing device is configured to detect and generate a first breach signal upon detecting a first event of interest. The sensing device sends the first breach signal to the OBC 118. In one embodiment, the sensing device is an electromechanical switch 114. The sensing device is disposed at an interior portion of the UAV 400. Particularly, the sensing device is disposed at a disassembly junction of a housing of the UAV 400. The first event of interest, includes, for example, physically opening/ opening the housing the UAV 400. In one embodiment, the first event of interest also includes addition or replacement of hardware constituting the UAV 400. In another embodiment, the first event of interest includes breach of hardware constituting the UAV 400.
[0029] The flight controller (FC) 112 is configured to control the flight dynamics of the UAV 400. The flight controller 112 is configured to generate a second breach signal upon detecting a second event of interest. The flight controller 112 is configured to facilitate detection of breach by setting the state of communication lines between the FC 112 and OBC 118 to a known state.
[0030] The second event of interest, includes, for example, a breach in flight controller 112 and controller 118 of the UAV 400. The second event of interest also includes manipulation of software constituting the system 100. The GPS module 108 in communication with the controller 118 is configured to provide time and geolocation information. The storage device or internal storage device 106 in communication with the controller 118 is configured to store first event of interest and the second event of interest with tags of time and geolocation information.
[0031] The controller 118 comprises a network module, a detection module and a log module. The controller 118 is configured to periodically check network availability over the communication module 110 at a pre-defined time interval, and synchronize the first event of interest and the second event of interest with tags to one or more pre-destined servers 102. In particular, the detection module is configured to detect breach signals, the network module is configured to check network availability and the log module is configured to check for new breach logs or events.
[0032] In one embodiment, the detection of first event of interest is disclosed. When the main power source is in “ON” state, electric power is supplied to the system 100 from the main power source. When the main power source is in “OFF” state, electric power is supplied to the system 100 from the auxiliary power source 116. The system 100 is configured to detect the change of a predetermined state of a specific part of the plurality of parts constituting the system 100, and check for any breach in the housing of the UAV 400. If there is any breach in housing, the sensing device detects and sends the first breach signal to the controller 118. The controller 118 comprising the detection module detects the breach signal with very low latency. The detection module comprises Low Latency Software Interrupt Service Routines (ISRs) in OBC 118 for capturing the breach detection signals generated at extremely low latency.
[0033] The controller 118 identifies the first breach signal as secondary breach. Thereafter, the controller 118 is configured to fetch the time and location data from the GPS module 108. The controller 118 stores the data regarding the secondary breach in the storage device 106. The data includes, but not limited to, severity of breach, time and location tags.
[0034] In one embodiment, the detection of second event of interest is disclosed in detail. when the main power source is in the “ON” state, the electric power is supplied to the system 100 from the main power source. When the main power source is in the “OFF” state, the electric power is supplied to the system 100 from the auxiliary power source 116.
[0035] The system 100 is configured to detect the change of a predetermined state of a specific part of the plurality of parts constituting the system 100, and check if the flight controller 112 is disconnected from the controller 118. The flight controller 112 is configured to detect switching of power supply to the auxiliary power source 116 and switches into power saving mode. The FC 112 comprises software routines to detect removal of main power supply, hold the states of communication lines between FC 112 and OBC 118 to known states.
[0036] During breach, the flight controller 112 is disconnected from the controller 118. The system 100 is configured to determine if the flight controller 112 is detached from the controller 118. If the flight controller 112 is detached from the controller 118, state of the communication lines between the controller 118 and the flight controller 112 also changes. The detection module in the controller 118 detects the change of state of communication lines and identifies the change as a primary breach or second event of interest. Thereafter, the controller 118 is configured to fetch the time and location data from the GPS module 108. The controller 118 stores the data regarding the primary breach in the storage device 106. The data includes, but not limited to, severity of breach, time and location tags.
[0037] The OBC 118 on next main power cycle checks the integrity of FC 112 based upon its identity checks, and autonomously decides if the UAV 400 should continue its normal mode of operation, or completely prevent any more flights.
[0038] Referring to FIG. 2, a multi-level breach detection method 200 for UAV 400, according to an embodiment of the present invention, is disclosed. At step 202, the controller 118 checks whether the main power source in “ON” state or “OFF” state. When the controller 118 confirms the main power source is in “OFF” state, the controller 118 moves to step 204. At step 204, the electric power is supplied to the system 100 from the auxiliary power source 116. At step 206, the flight controller 112 is configured to detect switching of power supply to the auxiliary power source 116 and maintains the communication line between the controller 118 and the flight controller 112 in known state. At step 208, the flight controller 112 switches into power saving mode, while detaching flight controller 112 from the controller 118.
[0039] At step 212, the system 100 is configured to determine if the flight controller 112 is detached from the controller 118. At step 224, if the flight controller 112 is detached from the controller 118, state of the communication lines between the controller 118 and the flight controller 112 also changes. At step 226, the detection module in the controller detects the change of state of communication lines. At step 228, the detection module identifies the change a primary breach or second event of interest. At step 230, the controller 118 is configured to fetch the time and location data from the GPS module 108. At step 232, the controller 118 stores the data regarding the primary breach in the storage device 106. The data includes, but not limited to, severity of breach, time and location tags.
[0040] When the flight controller 112 switches into power saving mode, the system 100 is also configured to check for breach in the housing of the drone, at step 210. At step 214, if there is any breach in housing, the sensing device detects and sends the first breach signal to the controller 118. At step 216, the detection module comprising set of instruction is configured to detect the breach signal with very low latency. At step 218, the controller 118 identifies the first breach signal as secondary breach or first event of interest. At step 220, the controller 118 is configured to fetch the time and location data from the GPS module 108. At step 222, the controller 118 stores the data or logs regarding the secondary breach in the storage device 106. The data includes, but not limited to, severity of breach, time and location tags. The controller 118 is configured to autonomously execute one or more responsive actions based on at least one of the first breach signal or second breach signal. The actions include, but not limited to, preventing flight of UAV 400.
[0041] FIG. 3 exemplarily illustrates a method 300 for checking the network availability and synching breach logs to servers 102, according to an embodiment of the present invention. At step 302, the network module of the controller 118 periodically checks for network availability over the communication module 110. At step 304, the network module detects if network is available. If network is not available, the method goes back to step 302. If the network is available, the method proceeds to step 306. At step 306, the log module is configured to periodically check the storage device 106 for new breach logs or data. At step 308, the log module checks for new breach logs. If new breach logs are not available, the method goes back to step 302. If new breach logs are available, the method proceeds to step 310. At step 310, the controller 118 sends the logs to the pre-destined servers 102 and goes to step 302. FIG. 4, exemplarily illustrates the unmanned aerial vehicle (UAV) 400 incorporated with the multi-level breach detection system 100, according to an embodiment of the present invention.
[0042] The principle advantages of the implementation of invention are disclosed as follows. The breach detection system 100 comprises very low latency. This highly sensitive breach detection removes room for working around the breach detection mechanism. Multiple level breach detection provides insights on the severity of breach. Low latency reporting of breaches gives head-ups time for taking appropriate manual actions against the breach. Use of cellular radio technology for reporting breaches enables breach reporting even at remote places.
[0043] Although a single embodiment of the invention has been illustrated in the accompanying drawings and described in the above detailed description, it will be understood that the invention is not limited to the embodiment developed herein, but is capable of numerous rearrangements, modifications, substitutions of parts and elements without departing from the spirit and scope of the invention.
[0044] The foregoing description comprises illustrative embodiments of the present invention. Having thus described exemplary embodiments of the present invention, it should be noted by those skilled in the art that the within disclosures are exemplary only, and that various other alternatives, adaptations, and modifications may be made within the scope of the present invention. Merely listing or numbering the steps of a method in a certain order does not constitute any limitation on the order of the steps of that method. Many modifications and other embodiments of the invention will come to mind to one skilled in the art to which this invention pertains having the benefit of the teachings presented in the foregoing descriptions. Although specific terms may be employed herein, they are used only in generic and descriptive sense and not for purposes of limitation. Accordingly, the present invention is not limited to the specific embodiments illustrated herein.
| # | Name | Date |
|---|---|---|
| 1 | 201941050483-STATEMENT OF UNDERTAKING (FORM 3) [06-12-2019(online)].pdf | 2019-12-06 |
| 2 | 201941050483-STARTUP [06-12-2019(online)].pdf | 2019-12-06 |
| 3 | 201941050483-REQUEST FOR EXAMINATION (FORM-18) [06-12-2019(online)].pdf | 2019-12-06 |
| 4 | 201941050483-REQUEST FOR EARLY PUBLICATION(FORM-9) [06-12-2019(online)].pdf | 2019-12-06 |
| 5 | 201941050483-POWER OF AUTHORITY [06-12-2019(online)].pdf | 2019-12-06 |
| 6 | 201941050483-FORM28 [06-12-2019(online)].pdf | 2019-12-06 |
| 7 | 201941050483-FORM-9 [06-12-2019(online)].pdf | 2019-12-06 |
| 8 | 201941050483-FORM FOR STARTUP [06-12-2019(online)].pdf | 2019-12-06 |
| 9 | 201941050483-FORM FOR SMALL ENTITY(FORM-28) [06-12-2019(online)].pdf | 2019-12-06 |
| 10 | 201941050483-FORM 18A [06-12-2019(online)].pdf | 2019-12-06 |
| 11 | 201941050483-FORM 18 [06-12-2019(online)].pdf | 2019-12-06 |
| 12 | 201941050483-FORM 1 [06-12-2019(online)].pdf | 2019-12-06 |
| 13 | 201941050483-FIGURE OF ABSTRACT [06-12-2019(online)].jpg | 2019-12-06 |
| 14 | 201941050483-EVIDENCE FOR REGISTRATION UNDER SSI(FORM-28) [06-12-2019(online)].pdf | 2019-12-06 |
| 15 | 201941050483-DRAWINGS [06-12-2019(online)].pdf | 2019-12-06 |
| 16 | 201941050483-DECLARATION OF INVENTORSHIP (FORM 5) [06-12-2019(online)].pdf | 2019-12-06 |
| 17 | 201941050483-COMPLETE SPECIFICATION [06-12-2019(online)].pdf | 2019-12-06 |
| 18 | Correspondence by Agent_Power of Attorney_23-12-2019.pdf | 2019-12-23 |
| 19 | Form 1_After Filing_30-12-2019.pdf | 2019-12-30 |
| 20 | 201941050483-Correspondence by Office_Defence_22-01-2020.pdf | 2020-01-22 |
| 21 | 201941050483-OTHERS [09-07-2021(online)].pdf | 2021-07-09 |
| 22 | 201941050483-FER_SER_REPLY [09-07-2021(online)].pdf | 2021-07-09 |
| 23 | 201941050483-DRAWING [09-07-2021(online)].pdf | 2021-07-09 |
| 24 | 201941050483-CORRESPONDENCE [09-07-2021(online)].pdf | 2021-07-09 |
| 25 | 201941050483-COMPLETE SPECIFICATION [09-07-2021(online)].pdf | 2021-07-09 |
| 26 | 201941050483-CLAIMS [09-07-2021(online)].pdf | 2021-07-09 |
| 27 | 201941050483-ABSTRACT [09-07-2021(online)].pdf | 2021-07-09 |
| 28 | 201941050483-FER REPLY AND SUPPORTING DOCUMENT_15-07-2021.pdf | 2021-07-15 |
| 29 | 201941050483-Reply from defence.pdf | 2021-10-17 |
| 30 | 201941050483-FER.pdf | 2021-10-17 |
| 31 | 201941050483-POA [07-06-2022(online)].pdf | 2022-06-07 |
| 32 | 201941050483-MARKED COPIES OF AMENDEMENTS [07-06-2022(online)].pdf | 2022-06-07 |
| 33 | 201941050483-FORM 13 [07-06-2022(online)].pdf | 2022-06-07 |
| 34 | 201941050483-AMENDED DOCUMENTS [07-06-2022(online)].pdf | 2022-06-07 |
| 35 | 201941050483-PatentCertificate10-03-2023.pdf | 2023-03-10 |
| 36 | 201941050483-IntimationOfGrant10-03-2023.pdf | 2023-03-10 |
| 37 | 201941050483-OTHERS [06-06-2023(online)].pdf | 2023-06-06 |
| 38 | 201941050483-FORM FOR STARTUP [06-06-2023(online)].pdf | 2023-06-06 |
| 39 | 201941050483-OTHERS [09-06-2023(online)].pdf | 2023-06-09 |
| 40 | 201941050483-FORM FOR SMALL ENTITY [09-06-2023(online)].pdf | 2023-06-09 |
| 41 | 201941050483-FORM FOR SMALL ENTITY [13-12-2024(online)].pdf | 2024-12-13 |
| 1 | 201941050483searchstrategyE_07-04-2021.pdf |