Processing information related to one or more monitoring areas.

Abstract

The present disclosure relates to a method for processing information related to one or more monitoring areas, the method comprising: receiving, using a central control unit, a UAV indicator for at least one unmanned aerial vehicle UAV located within the one or more monitoring areas, the UAV indicator being generated by a pre-processing step including extracting information embedded within a detected UAV communication, the detected UAV communication being detected by at least one sensor of a group of sensors; aggregating, by the central control unit, the UAV indicator to provide aggregated information; and corresponding steps of the aggregated information including at least one of I. outputting the aggregated information and ii. storing the aggregated information.

Description

Technical Field

[0001] The popularity of commercial Unmanned Aerial Vehicles (UAVs) is rising rapidly. It is expected that over 100 million UAVs will be in use by 2020. Until a few years ago, UAVs were nothing more than military aircraft. Currently, commercial UAVs are widely available, relatively inexpensive, and equipped with top-tier military-grade capabilities.

[0002] While most UAVs are used for legitimate and meaningful purposes, many UAVs are used irresponsibly or maliciously, such as endangering aircraft at airports, secretly smuggling drugs and weapons into prisons, launching attacks or harassment against politicians, and committing terrorist acts.

[0003] Some anti-UAV systems may have a limited detection range.

[0004] There is a growing need to provide efficient solutions for expanding the detection range.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Means for Solving the Problems

[0006] As set forth herein, systems, methods, and computer-readable media for processing information related to one or more surveillance areas may be provided.

[0007] The embodiments of the present disclosure will be more fully understood and appreciated by using the following details in conjunction with the drawings.

Brief Description of the Drawings

[0008] [Figure 1] This figure shows an example of the method. [Figure 2] This diagram shows an example of a system, other systems, a monitoring area, a UAV, and a UAV remote controller. [Figure 3] This diagram shows the execution of various tasks. [Figure 4] This diagram shows the execution of various tasks. [Figure 5] This figure shows an example of the method. [Figure 6] This figure shows an example of the method. [Figure 7] This figure shows an example of the method. [Modes for carrying out the invention]

[0009] The following detailed description includes many specific details in order to provide a complete understanding of the invention. However, those skilled in the art will understand that the invention can be practiced without these specific details. In some cases, well-known methods, procedures, and components are not described in detail so as not to obscure the invention.

[0010] The subject matter considered to be the present invention is specifically pointed out and clearly claimed in the concluding section of the specification. However, both the configuration and operation of the present invention, along with its objectives, features, and advantages, can be best understood by referring to the following detailed description with reference to the accompanying drawings.

[0011] For the sake of simplicity and clarity in the illustrations, it should be noted that the elements shown in the diagrams are not necessarily drawn to a consistent scale. For example, the dimensions of some elements may be exaggerated compared to others for clarity. Furthermore, where appropriate, reference numbers may be repeated between drawings to indicate corresponding or similar elements.

[0012] Since most of the exemplary embodiments of the present invention can be implemented using electronic components and circuits known to those skilled in the art, no further details beyond what is deemed necessary, as set forth above, will be described, in order to facilitate understanding and recognition of the fundamental concepts of the present invention, and to avoid obscuring or diverting attention from the teachings of the present invention.

[0013] References to methods herein should apply mutatis mutandis to devices or systems capable of performing the methods and / or non-temporary computer-readable media storing instructions for performing the methods.

[0014] References to systems or devices herein should be applied mutatis mutandis to methods that can be performed by a system, and / or to non-temporary computer-readable media that store instructions that can be executed by a system.

[0015] References to non-temporary computer-readable media in this specification should be applied mutatis mutandis to devices or systems capable of executing instructions stored in non-temporary computer-readable media, and / or to methods for executing such instructions.

[0016] Any combination of any figures, any part of the specification, and / or any module or unit listed in any claim may be provided.

[0017] The specification and / or drawings may refer to a processor. The processor may also be a processing circuit. The processing circuit may be implemented as one or more other integrated circuits, such as a central control unit (CPU) and / or an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a fully custom integrated circuit, or a combination of such integrated circuits.

[0018] Any combination of any steps of any method presented in the present specification and / or the drawings may be provided.

[0019] Any combination of any subject matter of any of the claims may be provided.

[0020] Any combination of the system, units, components, processors, and sensors presented in the present specification and / or the drawings may be provided.

[0021] Any reference to a sensor may apply mutatis mutandis to a system, a central control unit, a subsystem, and a UAV disruption unit. The subsystem may include a sensor and / or a UAV disruption unit and / or a preprocessor.

[0022] A disruption task is a task intended to disrupt a UAV, for example, to prevent the UAV from completing its mission, or to delay the UAV from performing its mission, or to take over control of the UAV to prevent the remote controller of the UAV from controlling the UAV for a limited or unlimited period of time.

[0023] A monitoring task is a task for monitoring, and may include monitoring a UAV, its remote controller, or both for one or more reasons. Typically, this task requires dedicated resources for receiving Radio Frequency (RF) signals transmitted by the UAV or by the remote controller. The monitoring result may include extraction of information contained in the received RF communication. The extraction may include, for example, converting the received RF signal into a digital signal and / or an analog signal.

[0024] The term "task" may refer to a disruption task and / or a monitoring task.

[0025] Methods, systems, and computer-readable media for processing information related to one or more monitoring areas may be provided.

[0026] A system may be provided that includes sensors (whether each sensor has local processing logic, such as a preprocessor, but not limited to that) and a central control unit.

[0027] The sensor may include an RF sensing unit for detecting detection information such as RF communication. A sensor with local processing logic, such as a preprocessor, may be configured to preprocess the detection information and extract information embedded in it. Alternatively, the detection information may be preprocessed by a preprocessor that does not belong to the sensor.

[0028] The pre-processed information may be sent to a central control unit, which may perform additional processing and then respond to the results of that processing. The pre-processing may be performed by the sensor or by a preprocessor that does not belong to the sensor.

[0029] The central control unit may receive UAV indicators indicating the presence of one or more UAVs or remote controllers in one or more monitoring areas, and may aggregate (or merge) the UAV indicators so that UAV indicators of the same UAV or remote controller are linked together or identified as originating from the same UAV or remote controller.

[0030] Determining that two or more UAV indicators originate from the same UAV in order to aggregate and use them together may involve using one or more means, which may be done via data transmitted by the UAV, such as UAV identification information, or by the UAV's location (two UAV indicators showing that the originating UAVs are located at approximately the same GPS location and altitude are likely to have originated from the same UAV), or by some communication parameters such as bandwidth frequency or timing (using the same time slot), or by matching some parameters such as model and frequency so that the system can estimate that two such UAV indicators are likely to have originated from the same UAV. Any other method may be used for aggregation.

[0031] This aggregation gives the system a range that is the combined range of all sensors. This effectively extends the range that a single sensor with dedicated local processing would have if it were standalone.

[0032] The system may also include one or more UAV blocking units. These units are capable of initiating and executing blocking tasks (partially or fully) according to parameters that match the target UAV.

[0033] The sensors may be paired or otherwise assigned to the UAV stop unit. The UAV stop unit may receive information from the paired or assigned sensors using direct communication between them. Both sensors may be integrated into a single unit.

[0034] The UAV blocking unit may perform the blocking task by directly receiving information from a sensor paired with the UAV blocking unit, or by independently acquiring information from the sensor if the UAV blocking unit acquires information and / or commands and / or requests and / or suggestions to assist the UAV blocking unit in determining the parameters of the blocking task through other means such as a central control unit.

[0035] When the system determines (through its logic or instructions given by the operator) that it should take over, avoid, or otherwise block a UAV, it may select a UAV blocking unit (or paired sensor and UAV blocking unit) to perform one or more blocking tasks to achieve this objective.

[0036] The system may perform one or more blocking tasks to take over the UAV or to prevent the UAV from operating in any other way.

[0037] The central control unit may control one or more UAV blocking units and one or more sensors. The central control unit may assign blocking tasks to one or more UAV blocking units and / or assign monitoring tasks to one or more sensors.

[0038] The central control unit may determine, in various ways and / or based on different rules and / or parameters, which one or more UAV blocking units to use, and / or which blocking tasks to perform, and / or which UAVs should be target UAVs (which should be the target of one or more blocking tasks).

[0039] For example, the selection of one or more UAV blocking units for use in a blocking task may depend on: (a) the range from the target UAV or its remote controller or both; (b) the quality of reception of target UAV communications by sensors adjacent to or paired with the UAV blocking unit; (c) whether the UAV blocking unit is busy with other tasks; (d) the power source of the UAV blocking unit (e.g., the unit may be battery-powered or connected to a grid); (e) the maximum power that the UAV blocking unit can transmit; (f) the type of antenna connected to the UAV blocking unit; and (g) the system as a whole or adjacent to or paired with the UAV blocking unit. The determination may be based on one or more of the following: (h) the number of transmitted packets received from the UAV or remote controller by the sensor paired with the UAV blocking unit; (i) how recently the target UAV or remote controller was received by the entire system or by sensors adjacent to or paired with the UAV blocking unit; (j) the bandwidth used by the target UAV or remote controller; (k) the type of target UAV; (g) the direction in which the transmitting antenna connected to the UAV blocking unit has the greatest gain (e.g., if the antenna is directional, whether the target UAV is located in that direction); and (l) the elevation of the target UAV.

[0040] If a UAV blocking unit is paired with a sensor, the quality of reception (by the sensor) may affect how successfully the sensor decodes the data being transmitted by the UAV, which can be helpful in the UAV takeover process by the UAV blocking unit.

[0041] The central control unit may select two or more sensors and / or preprocessors for receiving and decoding information from the UAV, and this information will be passed to the UAV blocking unit (either directly if the sensors and the UAV blocking unit are coupled within the same unit, or through communication via the central control unit, or directly from unit to unit).

[0042] UAV blocking units may be powered by a battery pack, a car battery, connected to a power grid, or otherwise. This may affect whether you can instruct a UAV blocking unit to perform one or more blocking tasks, as the power source for the UAV blocking unit may be limited. It may also affect the maximum power that the UAV blocking unit can transmit.

[0043] Multiple UAV deterrent units may work synchronously and collaboratively under the control of a central control unit. This may require clock synchronization, but can result in a more effective attack.

[0044] The system may apply coordinated (or combined) attacks from several UAV interception units, and / or a central control unit may control them.

[0045] U.S. Patent No. 1,0728906, incorporated herein by reference, provides an example of subdividing time slots in a radio time-division duplex communication link. Within a time slot, block signals in multiple frequency bands are transmitted during the time interval of the time slot.

[0046] The attack combination may include using multiple UAV blocking units to transmit multiple blocking signals per time slot. Different UAV blocking units may transmit blocking signals at different frequencies within a given time interval. For example, different UAV blocking units may be assigned different frequencies or frequency bands across the entire time slot. For example, each UAV blocking unit may transmit for longer periods at each of fewer frequencies, or all UAV blocking units may transmit at all frequencies, but each UAV blocking unit will transmit blocking signals at the same frequency at different times.

[0047] The combination of attacks may be used to operate several possible actions simultaneously for an attack (for example, when the system cannot determine at what frequency the UAV expects its remote controller to transmit), and different UAV blocking units may apply these different attacks to cover several possibilities.

[0048] The combination of attacks may include using different UAV blocking units for different roles and / or different types of blocking tasks. For example, one UAV blocking unit could be used to interrupt a target UAV's communications and another UAV blocking unit could be used to transmit alternative communications for the purpose of taking over the target UAV's communications.

[0049] A disruption signal may be transmitted using a UAV blocking unit closer to the target UAV, while alternative communications may be transmitted from a more distant UAV blocking unit. Essentially, the disruption signal is more effective the higher the power at which it is received, and the closer the UAV blocking unit is, the more effectively communications can be disrupted. This is not necessarily true for alternative communications, which may be received at lower power.

[0050] In other cases, the target UAV communication may use noise estimation to determine which alternative frequency band or communication format to use. Noise transmitted in a specific pattern by the first UAV blocking unit can cause the target UAV to decide to communicate in a specific frequency band or communication format that is favorable for takeover. This takeover may be performed by a second UAV blocking unit in cooperation with the first UAV blocking unit.

[0051] The sensor may also assist in the dodging task performed by the UAV dodging unit by, for example, monitoring communication between the target UAV and its remote controller. This monitoring can help determine the status of the target UAV and proceed with the dodging task accordingly.

[0052] Multiple UAVs located within one or more monitoring areas may be attacked during overlapping time periods. Since each UAV blocking unit can perform an independent takeover, several such attacks may occur in parallel within the same time period. Each blocking task may utilize a UAV blocking unit, but if several UAV blocking units are available, two or more attacks may be executed simultaneously. Alternatively, several UAV blocking units may coordinate several attacks in parallel so that all participate in each blocking task.

[0053] Attacks may be prioritized by one or more parameters, for example, threat level, UAV flight range, or other means, and appropriate UAV interceptor units and sensors may be selected by a central control unit according to that priority.

[0054] The central control unit may prioritize attacks (dodging tasks) according to many different parameters, such as the location of the UAV, the weight the UAV can carry (payload), the flight range of such UAVs, prior knowledge of the UAV's identification information (e.g., whether that particular UAV has already attacked or flown nearby without permission but was not intercepted or was intercepted and returned to its owner), the UAV's speed, the UAV's altitude, the UAV's battery charge, the direction the UAV's camera is facing, the UAV operator's location, and the distance between the UAV and its operator. According to this priority, the central control unit may select appropriate UAV dodging units and sensors. Prioritization may be UAV dodging-based or system-based.

[0055] Each subsystem, including the sensors, the UAV blocking unit, and the local processing unit, may function independently, for example, if it is configured to function independently when the subsystem is disconnected from the central control unit. In the event of such disconnection, the subsystem may initiate an attack automatically or by instructions given by a local human operator.

[0056] Sensors, UAV blocking units, and such subsystems may be updated using data useful in future detection or attack, using data of the area (e.g., maps or satellite imagery), or using software versions. This update may be performed through local updates or through central updates via a central processing unit.

[0057] When software versions, maps, databases, etc., need to be updated, each unit, sensor, and UAV blocking unit can be updated individually or together.

[0058] A system including subsystems and / or sensors and / or UAV blocking units and a central control unit may be considered updated only after the central control unit has transferred the new software version to all subsystems and / or sensors and / or UAV blocking units and the new software version has been installed, or only after each of the sensors and / or UAV blocking units has been locally updated.

[0059] The sensor may update the central control unit with the sensor's status, such as its function, range, and availability. This may allow the central control unit to determine how the sensor will be used in the future, or the level of confidence it will place on the information the sensor provides.

[0060] The central control unit may include a distributed array of controllers.

[0061] One or more controllers may be selected (e.g., by a human) to act as a central control unit for one or more time periods. The selection may be made according to a predefined schedule, based on the health of other controllers, etc.

[0062] The central control unit may be physically and / or logically isolated from other subsystems, sensors, and UAV blocking units.

[0063] There may be one or more user interfaces for interfacing with the central control unit. This allows one or more operators to control and / or interact with the central control unit.

[0064] The subsystem can be configured to automatically respond when it detects a UAV threat, take over the UAV according to pre-configured parameters (e.g., the UAV has entered a protected area defined in the system), and, depending on the area where the UAV was detected, cause the UAV to take specific actions (e.g., land at a designated location, execute a flight plan, etc.) (to prevent the UAV from flying across the landing path within the airport).

[0065] The subsystem may also be configured in a manual operation mode, where it only attacks if an operator initiates the attack. In this mode, the subsystem does not perform automated blocking tasks.

[0066] The subsystem may operate under the control of a central control unit, but may also operate in standalone mode, for example, if the subsystem is disconnected from the central control unit and / or other subsystems.

[0067] A subsystem may be programmed not to operate, or at least not to initiate an attack, if it is disconnected from the central control unit and / or other subsystems.

[0068] In standalone mode, a subsystem may automatically attack, completely ignoring the remaining subsystems or the central logical processing unit.

[0069] A central control unit may be provided that can control multiple subsystems (each including one or more sensors and one or more UAV blocking units).

[0070] The central control unit may be contained within a computerized system, such as a single server, which can be located separately from the subsystems. This allows organizations to intuitively defend vast areas of land from rogue UAVs and rapidly scale up to virtually any operational requirement.

[0071] The central control unit may provide a central management solution designed to control multiple subsystems that can detect, identify, and control rogue UAVs. This solution facilitates expanded and uninterrupted response for rogue UAV detection and mitigation without increasing the number of personnel required to operate multiple subsystems, by remotely controlling multiple subsystems from a single server.

[0072] Central control units can be beneficial for organizations that need to secure large areas, including airports, border patrols, major critical infrastructure facilities, and outdoor events such as marathons.

[0073] A central control unit can be beneficial for organizations that need to secure multiple physically separated areas.

[0074] This centralized management solution allows organizations to move from "point protection" with a single sensor to securing vast areas of land using multiple sensors. Because the personnel required to operate the central control unit are comparable to those required for a single subsystem, the centralized management solution can be an efficient solution for defending against rogue UAVs over large areas.

[0075] The central control unit may be seamlessly integrated into a third-party command and control system, for example, using an API or other means.

[0076] Information about UAVs detected by sensors and information about the health of subsystems may be transmitted using an API or other means. Additionally or alternatively, settings (such as protection plans, which may include blocking tasks, selection rules, etc.), system instructions (such as on or off), and attack instructions may be received from the command and control of another system using an API or other means.

[0077] The central control unit may aggregate information from multiple sensors and provide aggregated information, which may be output to various other systems (such as a control command system) via an API or other means.

[0078] The central control unit may receive requests and / or commands from other systems and convert them into blocking tasks and / or monitoring tasks, and / or assign the blocking tasks and / or monitoring tasks to UAV blocking units and / or sensors, respectively, and send them to them.

[0079] The aggregated information may be formatted so that it can be displayed on any platform and / or in any manner, for example, on a map-based command and control platform with an option to trigger mitigation via other systems and / or on a display of any subsystem.

[0080] The central control unit may provide integrated, intuitive operational awareness to support mission-critical decisions by aggregating information from multiple sensors that may be distributed to one or more locations to monitor one or more monitoring areas. This may also include eliminating duplication when multiple sensors detect the same UAV. The central control unit may select (e.g., the best) UAV blocking unit to initiate mitigation after considering interference, radio parameters, range, and other parameters.

[0081] The threats posed by UAVs vary depending on the mission, use case, and environment, and the system may be configured according to various deployment options, providing optimized response range for a wide variety of scenarios, conditions, and terrain types with quick and easy setup.

[0082] The central control unit and / or subsystems and / or sensors and / or UAV interception units may be mounted discreetly on a vehicle or vessel, set up as a stationary deployment in low or high ground, or used tactically in the field, as needed. The hardware of the central control unit may be lightweight and compact, and can be quickly disassembled, moved, and reassembled in minutes.

[0083] Figure 1 shows a method 100 for processing information related to one or more monitoring areas.

[0084] Method 100 may begin with a step 110 in which a central control unit acquires a UAV indicator relating to at least one unmanned aerial vehicle (UAV) located within one or more monitoring areas. Acquisition may include receiving the UAV indicator, for example, from a sensor or from another source. For simplicity of explanation, the following text will refer to sensors.

[0085] The central control unit is central in the sense that it can process the UAV indicators received from the sensor array.

[0086] The central control unit may include one or more processing circuits, which may be distributed or non-distributed.

[0087] The sensor array may include a radio frequency (RF) receiver. The RF receiver may monitor communications associated with one or more UAVs. The RF receiver may be a passive RF receiver, an active RF receiver, may include at least one directional RF receiver, may include any number of antennas, may include any type of antenna, may include at least one omnidirectional receiver, may be spaced far apart from each other, may include at least one sensor that is integrated into and / or included in and / or permanently assigned to a particular UAV blocking unit, or may include at least one standalone sensor that is not integrated into and / or included in and / or permanently assigned to a particular UAV blocking unit. The sensors may be temporarily paired with the UAV blocking unit. The UAV blocking unit may be temporarily or permanently prevented from transmitting blocking signals (for example, based on the location of the UAV blocking unit and / or transmission permission and / or transmission license).

[0088] A UAV blocking unit is a unit configured to transmit one or more transmit UAV blocking signals and / or to generate one or more UAV blocking signals and / or to generate one or more signals that are converted into one or more transmit UAV blocking signals. Conversion may include digital-to-RF conversion, amplification, attenuation, format conversion, and transmission via an antenna.

[0089] The UAV indicator is generated by a preprocessing step which may include extracting information embedded within the detected UAV communication, and the detected UAV communication is detected by at least one sensor from the sensor group.

[0090] Step 110 may include at least one of the following: • Receiving UAV indicators. • Generate a UAV indicator. • Perform a preprocessing step. The preprocessing step may include any processing means that can precede one or more other steps of method 100. • Receive detected UAV communications.

[0091] Method 100 may also include detecting the UAV communication to be detected by one or more sensors.

[0092] A UAV indicator may include one or more UAV indicators associated with the same UAV. One or more UAV indicators associated with the same UAV may be detected by the same sensor or by two or more sensors.

[0093] At least one UAV may include two or more UAVs associated with two or more UAV indicators.

[0094] The UAV indicator may include at least one of the following: (i) a UAV identifier, e.g., a unique UAV ID, MAC address, etc.; (ii) a UAV model identifier; (iii) the location of the UAV, e.g., coordinates and / or direction and / or elevation; (iv) the location of the UAV remote controller; (v) the UAV's "home" location (a location to which the UAV may automatically return, typically in response to a communication loss between the UAV and its remote controller, when the UAV is commanded to return or when an emergency plan is initiated); and (vi) additional telemetry parameters.

[0095] The information embedded within detected UAV communications may be contained within any frame, packet, or communication protocol.

[0096] Extracting embedded information may differ from measuring RF parameters of UAV communications, such as the carrier frequency, modulation, and duty cycle of UAV communications.

[0097] Step 110 may be followed by step 120, in which the central control unit aggregates the UAV indicators and provides aggregated information.

[0098] Information aggregation may include removing redundant information, combining information, merging information, ignoring information, resolving inconsistencies between information on different UAV indicators, merging information, extrapolating information, interpolating information, modifying information, or processing information on different UAV indicators in other ways.

[0099] Information aggregation may include processing two or more UAV indicators related to the same UAV by removing redundant information from two or more UAV indicators related to the same UAV, combining information from two or more UAV indicators related to the same UAV, ignoring information from two or more UAV indicators related to the same UAV, ignoring information from two or more UAV indicators related to the same UAV, resolving inconsistencies between information from two or more UAV indicators related to the same UAV, merging information from two or more UAV indicators related to the same UAV, extrapolating information from two or more UAV indicators related to the same UAV, interpolating information from two or more UAV indicators related to the same UAV, modifying information from two or more UAV indicators related to the same UAV, or processing information from two or more UAV indicators related to the same UAV in other ways.

[0100] Two or more UAV indicators associated with the same UAV may be based on detection information obtained by one or more sensors.

[0101] Step 120 may be followed by Step 130, which corresponds to the aggregated information.

[0102] The corresponding steps can be performed by a central control unit, or by a combination of the central control unit and at least one other entity (human or non-human).

[0103] The corresponding step may include at least one of the following: Determine one or more blocking tasks to be applied to at least one target UAV among the at least one UAV. (Step 131) Propose one or more blocking tasks to be applied to at least one target UAV among at least one UAV. (Step 132) • Receive one or more blocking tasks applied to at least one target UAV among at least one UAV (Step 133). The reception may be from a human or any non-human entity. • Receive the assignment of one or more blocking tasks to one or more UAV blocking units. (Step 134) - Assign a blocking task to the UAV blocking unit. (Step 135). The assignment may include assigning blocking tasks that target the same UAV target or different UAVs. Select at least one target UAV that will be subject to at least one blocking task. (Step 136) • Receive the selection result for at least one target UAV that is subject to at least one blocking task. (Step 137) • Output the aggregated information. (Step 138) • Store the aggregated information. (Step 139). The storage may be performed in volatile memory, non-volatile memory, etc. Assign the monitoring task to one or more sensors. (Step 140) • Decide not to take any blocking steps. (Step 141)

[0104] Any combination of corresponding steps may be provided, provided that the steps do not contradict each other (for example, step 141 cannot be added to step 131 or step 135).

[0105] An example of a combination that includes assigning one or more blocking tasks and one or more monitoring tasks.

[0106] Another example of a combination of Step 134 and one or more of Steps 131-134.

[0107] Steps 131 and / or 132 may include steps 136 and / or 137. For example, the determination of the blocking task may include selecting at least one or more target UAVs and / or depending on the selected at least one or more target UAVs.

[0108] The blocking tasks (described in steps 131-135) may differ from each other in some way, for example, by at least one of the following: • Transmission frequency of block signals associated with different blocking tasks. • Timing of sending block signals associated with different block tasks. • Data transmitted within a block signal associated with a different block task. • A communication protocol used to transmit block signals associated with different blocking tasks.

[0109] The blocking task may include (a) a first blocking task that interrupts a particular UAV from receiving a legitimate signal sent to the UAV by the UAV's remote controller, and (b) a second blocking task that sends a false signal to take over the UAV.

[0110] The blocking task may include (a) a first blocking task that blocks communications transmitted through a first communication channel, and (b) a second blocking task that blocks communications transmitted through a second communication channel.

[0111] The first communication channel may have a different role from the second communication channel. For example, the second communication channel may be (a) an auxiliary communication channel that the UAV and / or remote controller can communicate on when the first communication channel is being interfered with or is of lower quality than desired; (b) an emergency communication channel used when the UAV faces an emergency scenario; (c) a reconnection communication channel used when the UAV is disconnected from the remote controller and decides to reconnect with the remote controller; or (b) a restart communication channel used when the UAV is restarted or when communication should be restarted.

[0112] The dodging task may aim to dodge at least one target UAV. Step 110 refers to a UAV indicator for at least one unmanned aerial vehicle (UAV) (which may be called at least one detected UAV, since communications concerning the UAV are detected), but at least one target UAV is the target of the dodging task. A detected UAV may or may not be a target UAV. For example, assuming there are multiple detected UAVs, one, some, or all of the multiple detected UAVs may be the target UAV.

[0113] Step 131 may include determining a blocking task based on the risks posed by at least one UAV. The risks may be actual risks, potential risks, or estimated risks.

[0114] Step 131 may include prioritizing blocking tasks above unassigned blocking tasks.

[0115] Step 131 may include selecting a UAV blocking unit from a set of UAV blocking units. The set may contain any number of UAV blocking units. The set may communicate with a central control unit.

[0116] The selection may be based on at least one of the following: • The location of the UAV blocking unit within the set of UAV blocking units. • The location of at least one target UAV. • Location of at least one remote controller for at least one target UAV. • At least one home location (the UAV's default landing site when communications are blocked). • Power supply parameters for the UAV blocking units in the set. For example, available power, power consumption of the UAV blocking unit, and type of power supply such as battery, generator, or power grid. • One or more transmission parameters of the UAV blocking units in the set. i. One or more transmission parameters may include the gain of the transmitting antenna. ii. One or more transmission parameters may include the maximum power of the block signal to be transmitted. • Estimation of the success of blocking attempts performed by various UAV blocking units within a set. The strength or quality of the received signal, the time elapsed since the last reception, the total number of receptions received by the sensor, and the spatial relationship between the sensor and the UAV blocking unit. • At least one previous encounter between at least one UAV and one of several other UAVs. • At least one previous encounter with a UAV of a UAV type corresponding to at least one of the UAV types. The UAV type may be the UAV manufacturer, the UAV model, the UAV modem, or the communication protocol used by the UAV.

[0117] Step 136, which selects at least one target UAV, may depend on at least one of the following (any of the parameters may be measured, detected, evaluated, verified, predicted, or estimated): • UAV payload parameters. For example, whether the UAV carries or is suspected of carrying a payload, or whether it has the capability to carry a payload; the size of the payload; the type of payload (e.g., communications payload, jamming payload, explosive payload, disposable payload, non-disposable payload); and the risks of the payload (potential risks, actual risks, estimated risks, etc.). • UAV propagation parameters. For example, speed, altitude, acceleration, direction of travel, and flight pattern. • UAV health parameters. Health parameters may include the status of one or more units, faults, battery status, available battery charge, etc. • At least one spatial relationship between at least one UAV and at least one corresponding remote controller. • At least one previous encounter between at least one UAV and one of several other UAVs. • At least one previous encounter with a UAV of a UAV type corresponding to at least one of the UAV types.

[0118] The sensor is a radio frequency receiver.

[0119] The monitoring task in step 140 may be for the purpose of evaluating the success of one or more blocking tasks, or for any other purpose, such as changing the assignment of sensors per one or more monitoring areas.

[0120] Step 138, which outputs aggregated information, may include at least one of the following: • Send aggregated information to at least one remote system. The remote system may be a remote computer, a remote human-machine interface, or the like. • Output aggregated information to the display. • Display aggregated information. • Generate human-recognizable indicators (sound, touch, etc.) regarding aggregated information.

[0121] Figure 2 shows an example of system 10 and its environment.

[0122] The system includes a central control unit 18 and five subsystems 16(1) to 16(5). The central control unit 18 may perform method 100. Note that the central control unit may be located in one or more subsystems and / or in any of the other systems 20. One or more computerized entities (which may include one or more processing circuits) may be determined in any way, at any frequency, and / or in response to any event.

[0123] The environment includes five detection areas 17(1) to 17(5) (corresponding to the monitoring areas), a third-party system (also called other systems) 20, and a network 22. The central control unit 18, the five subsystems 16(1) to 16(5), and the other systems 20 may communicate using one or more networks, such as network 22.

[0124] Each of the other systems may include several (Q) components 20(1) to 20(Q), such as a processor, a communication unit, and a human-machine interface (which may be a display).

[0125] The five detection areas 17(1) to 17(5) are the detection areas of the five subsystems 16(1) to 16(5). The first to fifth detection areas 17(1) to 17(5) are the detection areas of the first to fifth subsystems 16(1) to 16(5). A monitoring area is an area defined as a target area in any way by any entity, such as an operator. For a monitoring area to be covered by one or more sensors, the monitoring area must be contained within at least one detection area of ​​one or more sensors. For simplicity of explanation, it is assumed that the entirety of the first to fifth detection areas forms a monitoring area.

[0126] In Figure 2, the five detection areas are shown as circular and equal to one another. However, please note that the detection areas may differ from circular detection areas (for example, when using a directional antenna and / or when the terrain of the area creates gaps or other biases within the detection area), and / or the size and / or shape of the detection areas may differ from one another.

[0127] Figure 2 shows the first to fourth UAVs 31-34, each controlled by the first to fourth remote controllers 31'-34', and each having the first to fourth homes 31"-34". The homes are default locations to which the UAVs return and land when communication is lost.

[0128] The first UAV31 is currently located within the fourth detection area 17(4). The second UAV32 is currently located within the first detection area 17(1) and the second detection area 17(2). The third UAV33 is currently located within the second detection area 17(2). The fourth UAV34 is currently located within the second detection area 17(2), the third detection area 17(3), and the fifth detection area 17(5).

[0129] The first subsystem 16(1) generates a first UAV indicator UI1 18(1) (with respect to the second UAV32) and sends it to the central control unit 18.

[0130] The second subsystem 16(2) generates a second UAV indicator UI2 18(2) (for the second UAV32), a third UAV indicator UI3 18(3) (for the third UAV33), and a fourth UAV indicator UI4 18(4) (for the fourth UAV34), and sends all three UAV indicators to the central control unit 18.

[0131] The third subsystem 16(3) generates a fifth UAV indicator UI5 18(5) (with respect to the fourth UAV34) and sends it to the central control unit 18.

[0132] The fourth subsystem 16(4) generates a sixth UAV indicator UI6 18(6) (with respect to the first UAV31) and sends it to the central control unit 18.

[0133] The fifth subsystem 16(5) generates a seventh UAV indicator UI7 18(7) (with respect to the fourth UAV34) and sends it to the central control unit 18.

[0134] It should be noted that UAV indicators may be generated multiple times, such as every second, every few seconds, or every minute. Also, UAVs may move over time and therefore may be associated with different UAV indicators linked to different locations. For simplicity, Figures 2-4 show only a single UAV indicator per UAV / subsystem.

[0135] The central control unit 18 may receive input I1 24 from another system 20 and send output O1 23 to that system.

[0136] Input I1 24 may include a request to obtain information generated by either the central control unit 18 or / or subsystem, which may include information about the UAV, a request to perform a blocking task, a list of possible blocking tasks that may be performed by the system, risk information, software updates, and instructions (such as rules for making any decisions relating to the operation of the central control unit 18, including blocking tasks and / or monitoring tasks to apply, how to assign tasks, how to select UAV blocking units, how sensors operate, and how tasks are determined).

[0137] Output O1 23 may be information generated by the central control unit 18 and / or by either subsystem.

[0138] This information may include aggregated information 82 and / or UAV information 81(1) to 81(4) relating to the first to fourth drones, status information 84 of the central control unit, UAV indicators UI1 18(1) to UI7 18(7), subsystem status 86, and activity logs 88 relating to tasks and / or the impact of task execution.

[0139] Any of the five subsystems may be replaced by the sensor 12 and / or the UAV blocking unit 14. The preprocessor 12(1) is shown as being included with the sensor 12, but may be located outside the sensor. The sensor 12 is shown as including a plurality of (N1) components 12(1) to 12(N1), and the UAV blocking unit 14 is shown as including a plurality of (N2) components 14(1) to 14(N2). In Figure 2, the sensor 12 and the UAV blocking unit 14 are shown as being included in a fifth subsystem 16(5).

[0140] The sensor components 12(1) to 12(N1) may include an antenna, RF circuit, signal analyzer, local controller / preprocessor, memory unit, man-machine interface, communication unit, power supply, etc.

[0141] The components 14(1) to 14(N2) of the UAV blocking unit 14 may include an antenna, RF circuitry, signal generator, transmitter, local controller / processor, memory unit, man-machine interface, communication unit, power source, and the like.

[0142] The sensor and UAV blocking unit may share at least one component (e.g., an antenna, RF circuit, local processor, communication unit, man-machine interface, power source), or they may not share any components.

[0143] The sensor and / or UAV blocking unit may include two or more antennas, or may include multiple other components of the same type.

[0144] The central control unit 18 may include one or more controllers 18(1) to 18(K) and other components, as well as additional components 19(1) to 19(J) such as a communication unit, a memory unit, and a man-machine interface.

[0145] In Figure 2, the central control unit 18 determines that the first drone 31 should not be monitored and blocked, and that the second, third, and fourth drones 32-34 should be blocked, and sends five task assignments TA1 11(1)-TA5 11(5) to the five subsystems. Note that two or more tasks may be assigned to the same subsystem simultaneously, and a subsystem may execute two or more tasks at once. For simplicity of explanation, only a single task is shown for each subsystem.

[0146] In the example related to Figure 3, these task assignments include three blocking tasks and one monitoring task.

[0147] Figure 3 shows that (a) the first subsystem 16(1) performs a first blocking task 41(1) to block the second UAV 32, (b) the second subsystem 16(2) performs a second blocking task 41(2) to block the third UAV 33, (c) the third subsystem 16(3) performs a third blocking task 421(3) to block the fourth UAV 34, (d) the fourth subsystem is commanded not to block any UAVs and can maintain detection of UAVs in any monitoring area within the fourth detection area, and (e) the fifth subsystem 16(3) performs a monitoring task 42(1) to monitor the success of the third blocking task.

[0148] In the example related to Figure 4, these task assignments include five blocking tasks.

[0149] Figure 4 shows that (a) the first subsystem 16(1) performs the first blocking task 41(1) to block the second UAV32, (b) the second subsystem 16(2) performs the second blocking task 41(2) to block the fourth UAV34, (c) the third subsystem 16(3) performs the third blocking task 41(3) to block the fourth UAV34, (d) the fourth subsystem 16(4) performs the fourth blocking task 41(4) to block the first UAV31, and (e) the fifth subsystem 16(3) performs the fifth blocking task 41(5) to block the fourth UAV34.

[0150] In the example shown in Figure 4, the second subsystem 16(2) is closer to the third UAV and the third controller 34' (compared to the fifth subsystem and the third subsystem), so for example, the signals of the third remote controller may be masked, while the fifth subsystem and the third subsystem transmit takeover signals.

[0151] Any task assignment may be provided according to one of the examples sent by the application.

[0152] Figure 5 shows a method 500 for processing information related to one or more monitoring areas.

[0153] Method 500 may be performed by a central control unit.

[0154] Method 500 may include step 510 of receiving a UAV indicator by a central control unit relating to at least one unmanned aerial vehicle (UAV) located within one or more monitoring areas.

[0155] Step 510 may be followed by step 520, in which a central control unit generates UAV information for each of at least one UAV based on UAV indicators, wherein the UAV information for a particular UAV is generated based on two or more UAV indicators associated with that particular UAV.

[0156] UAV information may be generated by fusing or otherwise aggregating information from UAV indicators associated with the same UAV. This determination that two or more UAV indicators originate from the same UAV for use together may be made via data transmitted by the UAV, such as UAV identification information; by the UAV's location (two UAV indicators showing that the originating UAV is located at approximately the same GPS location and elevation are likely to originate from the same UAV); by several communication parameters, such as bandwidth frequency or timing (using the same time slot); or by matching several parameters, such as model and frequency, so that the system can estimate that two such UAV indicators are likely to originate from the same UAV. Any other method may be used for aggregation.

[0157] Step 520 may be followed by step 530, which assigns a blocking task to be applied to at least one of the target UAVs.

[0158] Step 530 may be followed by step 540, which corresponds to UAV information, and the corresponding step includes at least one of (i) outputting UAV information and (ii) storing UAV information.

[0159] Any reference to Method 100 (or one or more steps of Method 100) may be applied mutatis mutandis to Method 500 (or one or more steps of Method 100).

[0160] Figure 6 shows method 600.

[0161] Method 600 may be carried out by subsystems such as subsystems 16(1) to 16(5) shown in Figures 2 to 4, but is not limited to these subsystems.

[0162] Method 600 is for performing tasks related to unmanned aerial vehicles (UAVs).

[0163] Method 600 may begin with step 610, in which a sensor detects UAV communication.

[0164] Step 610 may be followed by step 620, which preprocesses the detected UAV communications to provide a UAV indicator. The preprocessing may include extracting information embedded within the detected UAV communications.

[0165] Step 620 may be followed by step 630, in which the UAV indicator is sent to the central control unit.

[0166] Method 600 may also include step 640 of receiving a request from a central control unit to perform a task, which is either a monitoring task or a blocking task.

[0167] Step 640 may be followed by step 650, which involves performing a task.

[0168] Tasks may be assigned according to the provided UAV indicators. Alternatively, the tasks in steps 640 and / or 650 may be sent to a subsystem according to one or more UAV indicators sent to the central control unit by another subsystem.

[0169] Figure 7 shows method 700.

[0170] Method 700 may be carried out by a system such as system 10 shown in Figures 2 to 4.

[0171] Method 700 may begin with a step 710 in which a central control unit of the system receives a UAV indicator relating to at least one unmanned aerial vehicle (UAV) located within one or more monitoring areas, the UAV indicator being generated by a preprocessing step which includes extracting information embedded in detected UAV communications, the detected UAV communications being detected by at least one sensor of a sensor group.

[0172] Step 710 may be followed by step 720, in which a central control unit aggregates UAV indicators and provides aggregated information.

[0173] Step 720 may be followed by a step 730 corresponding to aggregated information, the corresponding step may include assigning a task based on the aggregated information and performing the task using at least one of (i) one or more UAV blocking units of the system, or (ii) one or more sensors of the system.

[0174] Any of the methods described above may be performed by a system comprising a central control unit and one or more subunits. Such a system may perform any of the methods illustrated above, and may also perform one or more additional steps, such as performing monitoring tasks, performing blocking tasks, detecting UAVs, and generating UAV indicators.

[0175] The above description of the present invention will enable those skilled in the art to create and use what is considered to be the best mode of the present invention at present. However, those skilled in the art will understand and recognize the existence of variations, combinations, and equivalents of specific embodiments, methods, and examples of the present invention. Therefore, the present invention should not be limited by the embodiments, methods, and examples described above, but rather by all embodiments and methods within the scope and spirit of the claimed invention.

[0176] The present invention has been described in the aforementioned specification with reference to specific examples of embodiments of the invention. However, it will be apparent that various modifications and changes may be made without departing from the broader spirit and scope of the invention as described in the appended claims.

[0177] Those skilled in the art will recognize that the boundaries between logic blocks are merely illustrative, and that in alternative embodiments, logic blocks or circuit elements may be merged, or that alternative functional decompositions may be imposed on various logic blocks or circuit elements. Therefore, it should be understood that the architecture described herein is merely illustrative, and in practice, many other architectures can be implemented to achieve the same functionality.

[0178] Any arrangement of components to achieve the same function is effectively “associated” in such a way that the desired function is achieved. Therefore, any two components combined herein to achieve a particular function, regardless of whether they are architectural or intermediate components, can be considered “associated” with each other in such a way that the desired function is achieved. Similarly, any two components thus associated can also be considered “operably connected” or “operably coupled” with each other in such a way that the desired function is achieved.

[0179] Furthermore, those skilled in the art will recognize that the boundaries between the operations described above are merely illustrative. Multiple operations may be combined into a single operation, a single operation may be distributed among additional operations, and operations may be performed with at least partial overlap in time. Moreover, alternative embodiments may include multiple instances of a particular operation, and the order of operations may be modified in various other embodiments.

[0180] Furthermore, for example, in one embodiment, the illustrated examples may be implemented as circuits located on a single integrated circuit or within the same device. Alternatively, these examples may be implemented as any number of separate integrated circuits or separate devices interconnected in a preferred manner.

[0181] However, other modifications, variations, and substitutions are possible. Therefore, the specification and drawings should be considered illustrative and not restrictive.

[0182] In the claims, reference numerals placed in parentheses shall not be construed as limiting the claims. The word “comprising” does not preclude the existence of other elements or steps other than those enumerated in the claims. Furthermore, the terms “a” or “an” as used herein are defined as one or more. Also, even if the same claim contains an introductory phrase such as “one or more” or “at least one,” or an indefinite article such as “a” or “an,” the use of such introductory phrases in the claims, such as “at least one” or “one or more,” should not be construed as meaning that the introduction of another claim element by the indefinite article “a” or “an” limits any particular claim containing such introduced claim element to an invention containing only one such element. The same applies to the use of definite articles. Unless otherwise specified, terms such as “first” and “second” are used to arbitrarily distinguish the elements that the terms describe. Therefore, these terms are not necessarily intended to indicate a temporal or other priority of such elements. The mere fact that certain means are described in different claims does not indicate that a combination of these means cannot be used advantageously.

[0183] While specific features of the present invention have been illustrated and described herein, those skilled in the art will now be able to conceive of numerous modifications, substitutions, alterations, and equivalents. Therefore, it should be understood that the appended claims are intended to cover all such modifications and alterations that fall within the true spirit of the present invention.

[0184] For clarity, various features of the embodiments of this disclosure described in the context of separate embodiments may be provided in combination in a single embodiment. Conversely, for brevity, various features of the embodiments of this disclosure described in the context of a single embodiment may be provided individually or in any preferred partial combination.

[0185] Those skilled in the art will recognize that the embodiments of this disclosure are not limited to those specifically shown and described above. Rather, the scope of the embodiments of this disclosure is defined by the appended claims and equivalents.

Claims

1. A method for processing information related to a monitoring area, A step of receiving a UAV indicator related to at least one unmanned aerial vehicle (UAV) located within the monitoring area by a central control unit, wherein the UAV indicator is generated by a preprocessing step which includes extracting information embedded in the detected UAV communication, and the detected UAV communication is detected by at least one sensor from a group of sensors which are radio frequency receivers configured to receive radio frequency communications; A step of aggregating the UAV indicators and providing aggregated information by a central control unit, wherein the aggregating step includes different UAV indicators associated with the same UAV among the at least one UAV, the aggregating step includes resolving inconsistencies between the information of the different UAV indicators, the different UAV indicators are generated by different sensors of the sensor group, and the different sensors are distributed across different locations to monitor different areas, A step corresponding to the aggregated information, comprising at least one of (i) outputting the aggregated information and (ii) storing the aggregated information. Methods that include...

2. The method according to claim 1, wherein the aggregation step includes removing redundancy of multiple sensors that detect the same UAV.

3. The method according to claim 1, comprising determining the payload type of the UAV and prioritizing blocking tasks based on the payload, wherein the payload type is selected from communications payloads, jamming payloads, explosive payloads, disposable payloads, and non-disposable payloads.

4. The method according to claim 1, wherein the corresponding step includes determining one or more blocking tasks to be applied to at least one target UAV among the at least one UAV.

5. The method according to claim 4, wherein the determination of one or more blocking tasks includes selecting at least one target UAV from the at least one UAV.

6. The method according to claim 1, wherein the corresponding step includes deciding not to perform any blocking task.

7. The method according to claim 1, wherein the corresponding step includes proposing one or more blocking tasks to be applied to at least one target UAV among the at least one UAV.

8. The method according to claim 1, wherein the corresponding step includes receiving one or more blocking tasks applied to at least one target UAV among the at least one UAV.

9. The method according to claim 1, wherein the corresponding step includes receiving the assignment of one or more blocking tasks to one or more UAV blocking units.

10. The method according to claim 1, wherein the corresponding step includes assigning a blocking task related to a specific UAV among the at least one UAV to a UAV blocking unit.

11. The method according to claim 10, wherein the blocking tasks differ from one another by the transmission frequency of the blocking signals associated with different blocking tasks.

12. The method according to claim 10, wherein the blocking tasks differ from one another by the timing of the transmission of blocking signals associated with different blocking tasks.

13. The method according to claim 10, wherein the blocking task includes (a) a first blocking task of interrupting the reception by the UAV of a legitimate signal sent to the UAV by the remote controller of the UAV, and (b) a second blocking task of sending a false signal to take over the UAV.

14. The method according to claim 10, wherein the blocking task includes (a) a first blocking task for blocking communication transmitted through a first communication channel, and (b) a second blocking task for blocking a second communication channel.

15. The method according to claim 14, wherein the second communication channel is at least one of an auxiliary communication channel, an emergency communication channel, a reconnection communication channel, or a restart communication channel.

16. The method according to claim 1, wherein the corresponding step includes assigning one or more blocking tasks to one or more UAV blocking units, the one or more blocking tasks being for blocking at least one target UAV among the at least one UAV.

17. The method according to claim 16, wherein the assignment includes selecting a UAV blocking unit from a set of UAV blocking units.

18. The method according to claim 17, wherein the selection is based on (a) the location of a UAV blocking unit in the set of UAV blocking units, and (b) at least one of (i) the location of at least one target UAV, (ii) the location of at least one remote controller of the at least one target UAV, and (iii) the location of at least one home location of the at least one target UAV.

19. The method according to claim 17, wherein the selection is based on the power supply parameters of the UAV blocking units of the set.

20. The method according to claim 17, wherein the selection is based on one or more transmission parameters of the set of UAV blocking units.

21. The method according to claim 20, wherein the one or more transmission parameters include the gain of the transmitting antenna(s).

22. The method according to claim 20, wherein the one or more transmission parameters include the maximum power of the block signal to be transmitted.

23. The method according to claim 17, wherein the selection is based on an estimate of the success of blocking attempts performed by different UAV blocking units of the set.

24. The method according to claim 17, wherein the selection is based on the intensity or quality of the received signal received from the sensor and the spatial relationship between the sensor and the UAV blocking unit.

25. The method according to claim 1, wherein the corresponding step includes determining a blocking task based on at least one of the actual and potential risks imposed by the at least one UAV.

26. The method according to claim 1, wherein the corresponding step includes prioritizing a blocking task above an unassigned blocking task.

27. The method according to claim 1, wherein the corresponding step includes selecting at least one target UAV from the at least one UAV.

28. The method according to claim 27, wherein the selection of the at least one target UAV is in accordance with the UAV payload parameters.

29. The method according to claim 27, wherein the selection of the at least one target UAV is based on UAV propagation parameters.

30. The method according to claim 27, wherein the selection of the at least one target UAV is based on UAV health parameters.

31. The method according to claim 27, wherein the selection of the at least one target UAV is based on the UAV battery state.

32. The method according to claim 27, wherein the selection of the at least one target UAV corresponds to at least one spatial relationship between the at least one UAV and at least one corresponding remote controller.

33. The method according to claim 27, wherein the selection of the at least one target UAV is based on at least one previous encounter with one or more of the at least one UAVs.

34. The method according to claim 27, wherein the selection of the at least one target UAV is based on at least one prior encounter with a UAV of a UAV type corresponding to one of the at least one UAVs.

35. The method according to claim 1, wherein the corresponding step includes assigning a monitoring task to at least some of the sensors in the group of sensors.

36. The method according to claim 35, wherein the monitoring task is for evaluating the success of one or more blocking tasks.

37. The method according to claim 1, wherein the corresponding step includes determining a blocking task based on a request or instruction to perform a blocking task.

38. The method according to claim 1, wherein the output of the aggregated information includes sending the aggregated information to at least one remote system.

39. The method according to claim 1, wherein the output of the aggregated information includes outputting the aggregated information to a display.

40. The method according to claim 1, wherein the output of the aggregated information includes displaying the aggregated information.

41. The method according to claim 1, further comprising the step of selecting the central control unit from among a plurality of control units.

42. The method according to claim 41, wherein at least one of the plurality of control units belongs to a subsystem.

43. A command for a central control unit to receive a UAV indicator relating to at least one unmanned aerial vehicle (UAV) located within a monitoring area, wherein the UAV indicator is generated by a preprocessing step that includes extracting information embedded in detected UAV communication, and the detected UAV communication is detected by at least one sensor from a group of sensors which are radio frequency receivers configured to receive radio frequency communication, A command for aggregating the UAV indicators and providing aggregated information by a central control unit, wherein the aggregating command includes different UAV indicators associated with the same UAV among the at least one UAV, the aggregating command includes resolving inconsistencies between the information of the different UAV indicators, the different UAV indicators are generated by different sensors of the sensor group, and the different sensors are distributed across different locations to monitor different areas, and An instruction for corresponding to the aggregated information, wherein the correspondence includes at least one of (i) outputting the aggregated information and (ii) storing the aggregated information. A non-temporary, computer-readable medium for storing data.

44. A central control unit for monitoring a monitoring area, Receiving a UAV indicator relating to at least one unmanned aerial vehicle (UAV) located within a monitoring area, wherein the UAV indicator is generated by a preprocessing step including extracting information embedded in the detected UAV communication, and the detected UAV communication is detected by at least one sensor in a group of sensors which is a radio frequency receiver configured to receive radio frequency communications. The aggregation of the UAV indicators and the provision of aggregated information, wherein the aggregation includes different UAV indicators related to the same UAV among the at least one UAV, and the aggregation includes resolving inconsistencies between the information of the different UAV indicators, wherein the different UAV indicators are generated by different sensors of the sensor group, and the different sensors are distributed across different locations to monitor different areas, and the aggregation is provided. Corresponding to the aggregated information, which includes at least one of (i) outputting the aggregated information and (ii) storing the aggregated information. A central control unit configured to perform the following actions.

45. A method for performing one or more tasks related to unmanned aerial vehicles (UAVs), The system's central control unit receives a UAV indicator relating to at least one unmanned aerial vehicle (UAV) located within a monitoring area, wherein the UAV indicator is generated by a preprocessing step which includes extracting information embedded in the detected UAV communication, and the detected UAV communication is detected by at least one sensor from a group of sensors which are radio frequency receivers configured to receive radio frequency communications. A step of aggregating the UAV indicators and providing aggregated information by a central control unit, wherein the aggregating step includes different UAV indicators associated with the same UAV among the at least one UAV, and the aggregating step includes resolving inconsistencies between the information of the different UAV indicators, wherein the different UAV indicators are generated by different sensors of the sensor group, and the different sensors are distributed across different locations to monitor different areas, A step corresponding to the aggregated information, comprising: assigning a task based on the aggregated information; and performing the task using (i) one or more UAV blocking units of the system, and (ii) at least one of one or more sensors of the system. Methods that include...

Images