Low-altitude anti-unmanned system elastic hierarchical command and control architecture and method
By constructing a two-tiered, elastic hierarchical architecture of 'command center + multiple distributed countermeasure nodes', the problem of insufficient coverage and deployment flexibility in existing low-altitude anti-drone systems has been solved, achieving dynamic coverage and rapid response to key protected areas, and effectively countering swarm drone attacks.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-27
- Publication Date
- 2026-04-03
AI Technical Summary
Existing low-altitude anti-drone systems are insufficient in terms of coverage and deployment flexibility, making it difficult to effectively deal with swarm attacks in complex scenarios, and they lack dynamic resource scheduling capabilities.
A two-tiered, resilient hierarchical architecture consisting of a central command and multiple distributed countermeasure nodes is constructed. Cross-level data fusion is achieved through the DDS network, enabling a rapid closed-loop response from perception to decision-making to action, and dynamically covering key protection areas.
It achieves dynamic coverage and precise defense of key protected areas, and can quickly respond to swarm drone attacks in complex scenarios, thus improving the system's response capabilities.
Smart Images
Figure CN121782936A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of low-altitude protection technology, specifically relating to a visible light near-infrared short-wave refraction reflective wavefront-coded calorimetric imaging system. Background Technology
[0002] With the widespread application of unmanned systems in both civilian and military fields, security threats in low-altitude airspace are becoming increasingly prominent. Low-altitude targets such as drones and small aircraft are highly stealthy, maneuverable, and inexpensive, and are widely used in scenarios such as illegal reconnaissance, border incursions, infrastructure sabotage, and even terrorist attacks, posing serious challenges to urban security, airport safety, protection of critical facilities, and battlefield situational awareness.
[0003] Existing low-altitude anti-drone systems typically employ fixed single-node deployments or centralized command and control architectures, which have certain shortcomings in practical applications. On the one hand, the effective radius of a single countermeasure node is limited, making it difficult to cover large key protection areas, and it is prone to creating defense blind spots in complex terrain, urban high-rise building clusters, and other scenarios. On the other hand, traditional systems lack dynamic resource scheduling capabilities and cannot flexibly adjust deployment strategies according to real-time threat situations or temporary security needs, resulting in delayed responses or even failures when dealing with swarm attacks or multi-point intrusions. Summary of the Invention
[0004] The purpose of this invention is to overcome the bottlenecks of existing technologies in terms of limited coverage and insufficient deployment flexibility. By constructing a two-tiered, elastic hierarchical architecture of "command center + multiple distributed countermeasure nodes," dynamic coverage and precise defense of key protected areas can be achieved. Through cross-level data fusion, a rapid closed-loop response of perception, decision-making, and action can be realized, effectively addressing complex scenarios such as swarm drone attacks.
[0005] To achieve the above objectives, the present invention provides the following technical solution: a flexible hierarchical command and control architecture for a low-altitude anti-unmanned system. The architecture is a two-level flexible hierarchical architecture, including a primary command node and multiple secondary countermeasure nodes. The primary command node and the secondary countermeasure nodes communicate with each other via a DDS network. The primary command node is used to collect the status information and detected target information of the secondary countermeasure nodes. The secondary countermeasure nodes are used for the deployment of countermeasure nodes and communicate with the primary command node.
[0006] The flexible hierarchical command and control architecture for low-altitude anti-unmanned systems provided by this invention also has the following technical features: the primary command node includes a service registration center, which communicates with all secondary countermeasure nodes and monitors their status; the service registration center is used to register the addresses of all secondary countermeasure nodes.
[0007] The flexible hierarchical command and control architecture for low-altitude counter-unmanned systems provided by this invention also has the following technical features: the secondary counter-counter node includes a node service registration center, multiple device services, and a service gateway. The node service registry is used to receive device service registrations and monitor their status, and synchronize information to the service gateway when the device status changes; The service gateway receives commands from the primary command node and routes the commands to the corresponding devices based on their registration addresses, thus completing the execution of the disposal commands.
[0008] Another objective of this invention is to provide a resilient hierarchical command and control method for low-altitude anti-unmanned systems, the method being implemented based on the resilient hierarchical command and control architecture for low-altitude anti-unmanned systems described in any of the preceding claims.
[0009] The low-altitude anti-unmanned system elastic layered command and control method provided by the present invention also has the following technical features: the method includes: Register the detection and countermeasure devices in the node service registration center of the secondary countermeasure node; Register countermeasure nodes at the primary command node; It is responsible for reporting target information, issuing disposal commands, and providing feedback on execution results.
[0010] The low-altitude anti-unmanned system elastic layered command and control method provided by this invention also has the following technical feature: the registration of the detection and countermeasure equipment includes: The device service will register the device's own address with the node service registry center; The device service periodically sends its own status information to the node service registry, and the node service registry monitors the service status. If no service status data is received for more than 3 service cycles, the device service will be removed from the device list. The node service registry will receive the service deregistration request and delete the stored registration service information. When the service status received by the node service registry changes, the node service registry will synchronize the changed parts to the service gateway.
[0011] The low-altitude anti-unmanned system elastic hierarchical command and control method provided by this invention also has the following technical feature: the registration of the countermeasure node includes: Secondary countermeasure nodes register their own addresses with the service registry; The secondary countermeasure node periodically sends its own status information to the registration service center through the service gateway, enabling the service registration center to monitor the service status; If no status data for the secondary countermeasure node is received for more than 3 service cycles, the current secondary countermeasure node will be removed from the node list. Upon receiving the node deregistration request, the service registry will delete the stored registration information of the secondary countermeasure node.
[0012] The flexible layered command and control method for low-altitude anti-unmanned systems provided by this invention also has the following technical features: the reporting of detected target information, the issuance of disposal commands, and the feedback of execution results include: The secondary countermeasure node reports the detected target information to the primary command node; After receiving the reported target information, the primary command node selects a target and takes action accordingly. After executing the command, the secondary countermeasure node reports the execution result to the primary command node.
[0013] Beneficial effects: The technical solution provided by this invention constructs a two-level elastic hierarchical architecture of "command center + multiple distributed countermeasure nodes", which realizes dynamic coverage and precise defense of key protection areas. Through cross-level data fusion, it achieves a rapid closed-loop response of perception-decision-action, effectively dealing with complex scenarios such as swarm drone attacks. Attached Figure Description
[0014] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0015] Figure 1 This is a schematic diagram of a two-level flexible hierarchical command and control architecture provided in an embodiment of the present invention. Detailed Implementation
[0016] The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. However, it should be noted that these embodiments are not intended to limit the present invention. Equivalent changes or substitutions in function, method, or structure made by those skilled in the art based on these embodiments are all within the protection scope of the present invention.
[0017] In the description of the embodiments of the present invention, it should be understood that the terms "center", "longitudinal", "lateral", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limiting the invention.
[0018] Furthermore, the terms "first," "second," "third," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature. In the description of this invention, unless otherwise stated, "a plurality of" means two or more.
[0019] The terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to fixed connections, detachable connections, or integral connections; they can refer to mechanical connections or electrical connections; they can refer to direct connections or indirect connections through an intermediate medium; and they can refer to the internal connection between two components. Those skilled in the art will understand the specific meaning of these terms in this invention based on the specific circumstances.
[0020] like Figure 1 As shown, this embodiment of the invention provides a resilient hierarchical command and control architecture for a low-altitude anti-unmanned system. The architecture is a two-level resilient hierarchical architecture, including a primary command node and multiple secondary countermeasure nodes. The primary command node and the secondary countermeasure nodes communicate with each other via a DDS network. The primary command node is used to collect the status information of the secondary countermeasure nodes and the information of detected targets. The secondary countermeasure nodes are used for the deployment of countermeasure nodes and communicate with the primary command node.
[0021] In some embodiments, the primary command node includes a service registry center, which communicates with all secondary countermeasure nodes and monitors their status. The service registry center is used to register the addresses of all secondary countermeasure nodes.
[0022] In some embodiments, the secondary countermeasure node includes a node service registry, multiple device services, and a service gateway. The node service registry is used to receive device service registrations and monitor their status, and synchronize information to the service gateway when the device status changes; The service gateway receives commands from the primary command node and routes them to the appropriate devices based on their registration addresses, thus executing the commands. The node service gateway synchronizes all device services with the registration center and uniformly encapsulates and registers them with the command post service registration center. Simultaneously, it receives instructions from the command post and routes these instructions based on the registration addresses of the device services.
[0023] In some embodiments, a resilient hierarchical command and control method for low-altitude anti-unmanned systems is provided, characterized in that the method is implemented based on the resilient hierarchical command and control architecture for low-altitude anti-unmanned systems as described in any of the preceding embodiments. This includes: Register the detection and countermeasure devices in the node service registration center of the secondary countermeasure node; Register countermeasure nodes at the primary command node; It is responsible for reporting target information, issuing disposal commands, and providing feedback on execution results.
[0024] In some embodiments, the registration of the detection and countermeasures device includes: The device service will register the device's own address with the node service registry center; The device service periodically (e.g., every 10 seconds, which can be changed according to the device characteristics) sends its own status information to the node service registry, and the node service registry monitors the service status. If no service status data is received for more than 3 service cycles, the device service will be removed from the device list. The node service registry will receive the service deregistration request and delete the stored registration service information. When the service status received by the node service registry changes, the node service registry will synchronize the changed parts to the service gateway.
[0025] The device service will register the device's own address with the node service registry. The DDS communication configuration is as follows: Message Subject: DeviceServiceRegistration; QoS policy: Reliability is configured as RELIABLE, and persistence is configured as PERSISTENT; The message data body is shown in the table below.
[0026] Table 1 Equipment Service Registration Information
[0027] The device service periodically (e.g., every 10 seconds, which can be changed according to device characteristics) sends its own status information to the node service registry. The node service registry monitors the service status. The DDS communication configuration is as follows: Message subject: DeviceServiceStatus; QoS policy: Reliability is configured as RELIABLE, and persistence is configured as PERSISTENT; The message data body is shown in the table below.
[0028] Table 2 Service Status Information
[0029] The node service registry receives a service deregistration request and deletes the stored registration service information. The DDS communication configuration is as follows: Message Subject: DeviceServiceDeregistration; QoS policy: Reliability is configured as RELIABLE, and persistence is configured as PERSISTENT; The message data body is shown in the table below.
[0030] Table 3 Service Cancellation Information
[0031] When the service status received by the node service registry changes, the node service registry will synchronize the changed information to the service gateway. The DDS communication configuration is as follows: Message subject: DeviceServiceSync; QoS policy: Reliability is configured as RELIABLE, and persistence is configured as PERSISTENT; The message data body is shown in the table below.
[0032] Table 4 Service Synchronization Information Content
[0033] In some embodiments, the registration of the countermeasure node includes: Secondary countermeasure nodes register their own addresses with the service registry; The secondary countermeasure node periodically sends its own status information to the registration service center through the service gateway, enabling the service registration center to monitor the service status; If no status data for the secondary countermeasure node is received for more than 3 service cycles, the current secondary countermeasure node will be removed from the node list. Upon receiving the node deregistration request, the service registry will delete the stored registration information of the secondary countermeasure node.
[0034] The secondary countermeasure node registers its own address with the service registry center. The DDS communication configuration is as follows: Message Subject: NodeRegistration; QoS policy: Reliability is configured as RELIABLE, and persistence is configured as PERSISTENT; The message data body is shown in the table below.
[0035] Table 5 Node Registration Information
[0036] The secondary countermeasure node periodically sends its own status information to the service registration center through the service gateway, enabling the service registration center to monitor the service status. The DDS communication configuration is as follows: Message subject: NodeStatus; QoS policy: Reliability is configured as RELIABLE, and persistence is configured as PERSISTENT; The message data body is shown in the table below.
[0037] Table 6 Node Status Information
[0038] Upon receiving a node deregistration request, the service registry deletes the stored secondary counter-node registration information. The DDS communication configuration is as follows: Message Subject: NodeDeregistration; QoS policy: Reliability is configured as RELIABLE, and persistence is configured as PERSISTENT; The message data body is shown in the table below.
[0039] Table 7 Node Deregistration Information
[0040] In some embodiments, the reporting of target information, issuance of handling commands, and feedback of execution results include: The secondary countermeasure node reports the detected target information to the primary command node; After receiving the reported target information, the primary command node selects a target and takes action accordingly. After executing the command, the secondary countermeasure node reports the execution result to the primary command node.
[0041] The secondary countermeasure node reports the detected target information to the primary command node. The DDS communication configuration is as follows: Message Subject: TargetReport; QoS policy: Reliability is configured as BEST_EFFORT, and persistence is configured as VOLATILE; The message data body is shown in the table below.
[0042] Table 8 Target Information Content
[0043] After receiving the reported target information, the primary command node selects a target and takes action accordingly. The DDS communication configuration is as follows: Message Subject: DisposalCommand; QoS policy: Reliability is configured as RELIABLE, and persistence is configured as PERSISTENT; The message data body is shown in the table below.
[0044] Table 9. Information on Disposal Orders
[0045] After executing the command, the secondary countermeasure node reports the execution result to the primary command node. The DDS communication configuration is as follows: Message Subject: DisposalCommand; QoS policy: Reliability is configured as RELIABLE, and persistence is configured as PERSISTENT; The message data body is shown in the table below.
[0046] Table 10 Command Feedback Information
[0047] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the protection scope of the present invention. The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the technical principles of the present invention, and these improvements and modifications should also be considered within the protection scope of the present invention.
Claims
1. A resilient hierarchical command and control architecture for a low-altitude anti-unmanned system, characterized in that, The architecture is a two-level elastic layered architecture, including a primary command node and multiple secondary countermeasure nodes. The primary command node and the secondary countermeasure nodes communicate with each other via a DDS network. The primary command node is used to collect the status information of the secondary countermeasure nodes and the detected target information. The secondary countermeasure nodes are used for the deployment of countermeasure nodes and communicate with the primary command node.
2. The flexible hierarchical command and control architecture for low-altitude anti-unmanned systems according to claim 1, characterized in that, The primary command node includes a service registration center, which communicates with all secondary countermeasure nodes and monitors their status. The service registration center is used to register the addresses of all secondary countermeasure nodes.
3. The flexible hierarchical command and control architecture for low-altitude anti-unmanned systems according to claim 1, characterized in that, The secondary countermeasure node includes a node service registry, multiple device services, and a service gateway. The node service registry is used to receive device service registrations and monitor their status, and synchronize information to the service gateway when the device status changes; The service gateway receives commands from the primary command node and routes the commands to the corresponding devices based on their registration addresses, thus completing the execution of the disposal commands.
4. A flexible layered command and control method for a low-altitude anti-unmanned system, characterized in that, The method is implemented based on the resilient hierarchical command and control architecture for low-altitude anti-unmanned systems as described in any one of claims 1-3.
5. The elastic layered command and control method for low-altitude anti-unmanned systems according to claim 4, characterized in that, The method includes: Register the detection and countermeasure devices in the node service registration center of the secondary countermeasure node; Register countermeasure nodes at the primary command node; It is responsible for reporting target information, issuing disposal commands, and providing feedback on execution results.
6. The elastic layered command and control method for low-altitude anti-unmanned systems according to claim 5, characterized in that, The registration of the detection and countermeasures equipment includes: The device service will register the device's own address with the node service registry center; The device service periodically sends its own status information to the node service registry, and the node service registry monitors the service status. If no service status data is received for more than 3 service cycles, the device service will be removed from the device list. The node service registry will receive the service deregistration request and delete the stored registration service information. When the service status received by the node service registry changes, the node service registry will synchronize the changed parts to the service gateway.
7. The elastic layered command and control method for low-altitude anti-unmanned systems according to claim 5, characterized in that, The registration of the countermeasure node includes: Secondary countermeasure nodes register their own addresses with the service registry; The secondary countermeasure node periodically sends its own status information to the registration service center through the service gateway, enabling the service registration center to monitor the service status; If no status data for the secondary countermeasure node is received for more than 3 service cycles, the current secondary countermeasure node will be removed from the node list. Upon receiving the node deregistration request, the service registry will delete the stored registration information of the secondary countermeasure node.
8. The elastic layered command and control method for low-altitude anti-unmanned systems according to claim 5, characterized in that, The reporting of target information, issuance of handling commands, and feedback of execution results include: The secondary countermeasure node reports the detected target information to the primary command node; After receiving the reported target information, the primary command node selects a target and takes action accordingly. After executing the command, the secondary countermeasure node reports the execution result to the primary command node.