A multi-station multi-machine wide-area cooperative unmanned aerial vehicle command and control system

Abstract

The application discloses a kind of unmanned plane command systems for multi-station multi-machine wide-area cooperation, the system includes N unmanned plane group, front desk command subsystem and background management subsystem;The unmanned plane group includes unmanned plane ground station and several unmanned planes;The front desk command subsystem is connected with the background management subsystem and the unmanned plane data, for task monitoring, task planning and situation monitoring;The background management subsystem is connected with the unmanned plane and the unmanned plane ground station data, for basic data management and communication network management.The method can realize the real-time overall scheduling of unmanned plane in multi-station multi-airport scene.

Description

Technical Field

[0001] The present invention belongs to the field of command and control, and specifically relates to an unmanned aerial vehicle (UAV) command and control system for multi-station and multi-machine wide-area collaboration. Background Art

[0002] With the continuous development of unmanned intelligent technology, unmanned combat, especially drone warfare, has become an indispensable component of modern warfare. Currently, medium-altitude, long-endurance drone operations are typically deployed in units of drone ground stations, typically consisting of two to three drones per station. This model, where drone ground stations serve as the basic unit for mission execution, is generally positioned to assist specific manned units and often limits the combat radius and mission capabilities of drones assigned to a single station within a fixed area. On the other hand, the inherent mobility and flexibility of drones as military equipment, since their inception, have given them the potential for deployment and coordinated operations on a wider scale.

[0003] Due to the highly information-based nature of drone combat systems, the primary bottleneck in aggregating drone swarms lies in the command and control system. Existing command and control systems are primarily designed for single-ground station combat scenarios. However, for multi-ground station, multi-aircraft collaborative combat scenarios, they lack the ability to coordinate combat resources and integrate intelligence and situational information. Consequently, it is difficult to aggregate as many drones as possible and maximize combat effectiveness to meet increasingly complex and changing operational requirements. Summary of the Invention

[0004] The technical problem to be solved by the present invention is to provide a drone command and control system for multi-station and multi-machine wide-area collaboration, which can realize real-time coordinated scheduling of drones in multi-station and multi-machine scenarios.

[0005] In order to solve the above technical problems, an embodiment of the present invention discloses a drone command and control system for multi-station and multi-machine wide-area collaboration, the system comprising N drone groups, a front-end command and control subsystem, and a back-end management subsystem; N is an integer greater than 1;

[0006] The drone group includes a drone ground station and several drones;

[0007] The front-end command subsystem communicates with the back-end management subsystem and the drone data for mission monitoring, mission planning and situation monitoring;

[0008] The background management subsystem is in data communication with the UAV and the UAV ground station, and is used for basic data management and communication network management.

[0009] As an optional implementation, in an embodiment of the present invention, the front-end charge subsystem includes a task monitoring module, a task planning module and a situation monitoring module;

[0010] The task monitoring module includes a task end queue maintenance unit, a task new queue maintenance unit, a task cancellation queue maintenance unit and a task display unit;

[0011] The end task queue maintenance unit is in data communication with the task planning module and the background management subsystem, and is used to construct an end task queue; the end task queue includes a plurality of end task numbers;

[0012] The newly added task queue maintenance unit is in data communication with the task planning module and is used to construct a newly added task queue; the newly added task queue includes a plurality of task tuples;

[0013] The task tuple includes task instructions, release time, execution status, target information, and task requirement information; the execution status value is executing, ended, or canceled; the target information includes target number, target name, and target coordinates;

[0014] The revocation task queue maintenance unit is in data communication with the task planning module and is used to construct a revocation task queue; the revocation task queue includes a plurality of task numbers to be revoked;

[0015] The task display unit is in data communication with the task planning module and is used to display the task tuple sequence and execution resource tree sequence output by the task planning module in a linked manner; the task tuple sequence includes a plurality of task tuples;

[0016] The execution resource tree sequence includes a plurality of available resource trees; the available resource tree includes a root node, N intermediate nodes, and a plurality of leaf nodes; the N intermediate nodes correspond to N UAV ground stations respectively; each leaf node corresponds to one UAV; the leaf nodes are all marked as busy, occupied, unavailable, or idle;

[0017] The task planning module is in data communication with the UAV and the background management subsystem, and is used to perform task planning processing on the available resource tree, the newly added task queue, the revoked task queue, and the ended task queue to obtain the task tuple sequence and the execution resource tree sequence;

[0018] The situation monitoring module is in data communication with the background management subsystem and is used to display the situation using the combat environment information and force and equipment information set stored in the background management subsystem.

[0019] As an optional implementation, in an embodiment of the present invention, the background management subsystem includes a basic data management module and a communication network management module;

[0020] The basic data management module includes a basic data storage unit and an equipment information updating unit;

[0021] The basic data storage unit is in data communication with the equipment information update unit and the front-end command and control subsystem, and is used to store a collection of troop equipment information and combat environment information;

[0022] The force and equipment information set includes N pieces of force and equipment information; the force and equipment information includes ground station information and a plurality of pieces of equipment information; the ground station information includes a ground station number, a ground station communication address, ground station coordinates, and commander information; the equipment information includes UAV status information and a UAV communication address;

[0023] The drone status information includes the drone number, real-time coordinates, mission number, mission status, mission objective, and capability information; the mission status value is in progress, completed, or canceled;

[0024] The equipment information updating unit is in data communication with the communication management module for updating information;

[0025] The communication management module includes a state information forwarding unit and an available resource tree generating unit;

[0026] The status information forwarding unit is in data communication with the UAV ground station, the UAV, the front-end command and control subsystem, and the equipment information updating unit, and is used to forward UAV status information and ground station status information; the ground station status information includes the ground station number, ground station communication address, ground station coordinates, and commander information;

[0027] The available resource tree generating unit is in data communication with the basic data storage unit and the front-end command and control subsystem, and is used to process the force and equipment information set to obtain an available resource tree.

[0028] As an optional implementation manner, in an embodiment of the present invention, the end task queue maintenance unit constructs the end task queue, including:

[0029] A1. Initialize the end task queue to an empty queue;

[0030] A2. In response to receiving the drone status information forwarded by the status information forwarding unit, determining whether the mission status value in the drone status information is ended, and obtaining a first status determination result;

[0031] When the first state judgment result is yes, the current ended task number is set as the task number T of the drone state information;

[0032] When the result of the first state judgment is no, execute A5;

[0033] A3. Determine whether the execution status of the Tth task tuple in the task tuple sequence is ended, and obtain a second status determination result;

[0034] When the second state determination result is yes, execute A5;

[0035] When the result of the second state judgment is no, the end task queue is updated to obtain the updated end task queue;

[0036] A4. Setting the execution status of the T-th task tuple in the task tuple sequence to end;

[0037] A5. Repeat A2 to A4 until the end signal from external input is received.

[0038] As an optional implementation manner, in an embodiment of the present invention, the available resource tree generation unit processes the force and equipment information set to obtain the available resource tree, including:

[0039] B1. Create a force organization tree with only one root node; initialize the first loop number mm to 1;

[0040] B2. Create the mmth intermediate node Node 1, mm ; Set the current force and equipment information to the mth force and equipment information in the force and equipment information set; set the communication address of the ground station to be connected to the ground station communication address of the ground station information in the current force and equipment information; use the ground station address to be connected to obtain the ground station communication status; the value of the ground station communication status is connected or not connected;

[0041] B3, using the ground station communication status, the intermediate node Node 1, mm Perform the first marking process to obtain the intermediate node Node after the first marking 1, mm ;Use the intermediate node Node 1, mm , performing a first update process on the force organization tree to obtain the force organization tree after the first update process;

[0042] B4. Determine the total number of current equipment NN, which is the number of equipment information in the current force equipment information; initialize the second loop number nn to 1;

[0043] B5. Create the nth leaf node 2,nn; Determine the communication address of the drone to be connected, which is the communication address of the drone of the nth equipment information in the current force equipment information; use the communication address of the drone to be connected to obtain the current drone communication status; the value of the drone communication status is connected or not connected;

[0044] B6, using the UAV communication status, the leaf node Node 2,nn Perform the second marking process to obtain the leaf node after the second marking 2,nn ; Using leaf nodes 2,nn , performing a second update process on the force organization tree to obtain the force organization tree after the second update process; adding 1 to the value of nn;

[0045] B7. Repeat B5-B6 until nn is greater than NN.

[0046] B8. Repeat B2 to B7 until mm is greater than N;

[0047] B9. Determine the available resource tree as the force organization tree;

[0048] B10. Repeat B1 to B9 until the end signal from external input is received.

[0049] As an optional implementation manner, in an embodiment of the present invention, performing task planning processing on the available resource tree, the newly added task queue, the revoked task queue, and the ended task queue to obtain the task tuple sequence and the execution resource tree sequence includes:

[0050] S1. Initialize the task tuple sequence to an empty sequence; initialize the execution resource tree sequence to include only the available resource tree;

[0051] S2, performing resource allocation processing on the newly added task queue, the task tuple sequence, and the execution resource tree sequence to obtain a first task tuple sequence and a first resource tree sequence;

[0052] S3, performing resource recovery processing on the revoked task queue, the first task tuple sequence, and the first resource tree sequence to obtain a second task tuple sequence and a second resource tree sequence;

[0053] S4, performing resource reallocation processing on the finished task queue, the second task tuple sequence, and the second resource tree sequence to obtain a third task tuple sequence and a third resource tree sequence;

[0054] S5. Setting the task tuple sequence and the execution resource tree sequence as the third task tuple sequence and the third resource tree sequence, respectively;

[0055] S6. Repeat S2 to S5 until the end signal from external input is received.

[0056] As an optional implementation manner, in an embodiment of the present invention, the resource allocation processing is performed on the newly added task queue, the task tuple sequence, and the execution resource tree sequence to obtain the first task tuple sequence and the first resource tree sequence, including:

[0057] S21, determining whether the newly added task queue is empty to obtain a first determination result;

[0058] When the first judgment result is yes, execute S25;

[0059] When the first judgment result is no, setting the current newly added task tuple as the task tuple at the head of the newly added task queue; performing a dequeue update on the newly added task queue to obtain the newly added task queue after the dequeue update;

[0060] S22, using the current newly added task tuple, performing task allocation update on the execution resource tree sequence to obtain the execution resource tree sequence after task allocation update;

[0061] S23, using the current newly added task tuple to expand and update the task tuple sequence to obtain the expanded and updated task tuple sequence;

[0062] S24, repeat S21 to S23;

[0063] S25 . Determine the first task tuple sequence and the first resource tree sequence, which are the task tuple sequence and the execution resource tree sequence respectively.

[0064] As an optional implementation manner, in an embodiment of the present invention, the use of the current newly added task tuple to update the execution resource tree sequence to obtain the execution resource tree sequence after the task allocation is updated includes:

[0065] S221, obtaining the last available resource tree in the execution resource tree sequence to obtain the current resource tree;

[0066] S222, using the newly added task tuple to filter the current resource tree to obtain a filtered resource tree;

[0067] S223. In response to a user operation, perform a third marking process on the screening resource tree to obtain a marked resource tree;

[0068] S224: Send the task instruction in the current newly added task tuple to the UAV corresponding to the leaf node marked as occupied in the marked resource tree;

[0069] S225: Insert the marked resource tree into the end of the execution resource tree sequence to obtain the execution resource tree sequence after the task allocation is updated.

[0070] As an optional implementation manner, in an embodiment of the present invention, performing resource recovery processing on the revoked task queue, the first task tuple sequence, and the first resource tree sequence to obtain a second task tuple sequence and a second resource tree sequence includes:

[0071] S31, determining whether the cancellation task queue is empty to obtain a second determination result;

[0072] When the second judgment result is yes, execute S35;

[0073] When the second judgment result is no, the current to-be-revoked number is set as the to-be-revoked task number q1 at the head of the revoked task queue; the revoked task queue is dequeued and updated to obtain the revoked task queue after dequeuing and updating;

[0074] S32, determining whether the execution status of the q1th task tuple in the first task tuple sequence is ended or in progress, and obtaining a third determination result;

[0075] When the third judgment result is yes, execute S31;

[0076] When the third judgment result is no, setting the execution state of the q1th task tuple in the first task tuple sequence to cancel;

[0077] S33: Using the to-be-revoked resource tree, revoking and updating the first resource tree sequence to obtain the first resource tree sequence after revoking and updating;

[0078] S34, repeat S31 to S33;

[0079] S35 . Determine the second task tuple sequence and the second resource tree sequence, which are the first task tuple sequence and the first resource tree sequence respectively.

[0080] As an optional implementation manner, in an embodiment of the present invention, performing resource reallocation processing on the finished task queue, the second task tuple sequence, and the second resource tree sequence to obtain a third task tuple sequence and a third resource tree sequence includes:

[0081] S41, determining whether the finished task queue is empty to obtain a fourth determination result;

[0082] When the fourth judgment result is yes, execute S45;

[0083] When the fourth judgment result is no, the current completion number is set as the to-be-revoked task number q2 at the head of the finished task queue; the finished task queue is dequeued and updated to obtain the finished task queue after dequeuing and updating;

[0084] S42: Reallocate and update the second resource tree sequence to obtain a reallocated and updated second resource tree sequence;

[0085] S43, setting the execution status of the q2th task tuple in the second task tuple sequence to end;

[0086] S44, repeat S41 to S43;

[0087] S45 . Determine a third task tuple sequence and a third resource tree sequence, which are the second task tuple sequence and the second resource tree sequence respectively.

[0088] Compared with the prior art, the embodiments of the present invention have the following beneficial effects:

[0089] By abstracting drones as resources and further uniformly representing and allocating multiple drone ground stations and their assigned drones through the available resource tree, real-time coordinated scheduling of drones in multi-station and multi-machine scenarios can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0090] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0091] Figure 1 This is a structural diagram of a UAV command and control system for multi-station and multi-machine wide-area collaboration disclosed in an embodiment of the present invention.

[0092] Figure 2 This is a structural diagram of a front-end control subsystem of a multi-station and multi-machine wide-area collaborative UAV command and control system disclosed in an embodiment of the present invention.

[0093] Figure 3 This is a structural diagram of a background management subsystem of a multi-station and multi-machine wide-area collaborative UAV command and control system disclosed in an embodiment of the present invention. DETAILED DESCRIPTION

[0094] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0095] In the description of the present invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings and are intended solely to facilitate and simplify the description of the present invention. They are not intended to indicate or imply that the devices or components referred to must have, be constructed, or operate in a specific orientation, and therefore should not be construed as limitations on the present invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0096] In the description of the present invention, it should be noted that, unless otherwise expressly specified or limited, the terms "mounted," "connected," and "connected" should be understood in a broad sense. For example, they may refer to fixed, detachable, or integral connections; mechanical or electrical connections; direct or indirect connections through an intermediate medium; and internal communication between two components. Those skilled in the art will understand the specific meanings of the above terms in the present invention based on the specific circumstances.

[0097] Example 1

[0098] See also Figure 1-3 , Figure 1 This is a structural diagram of a UAV command and control system for multi-station and multi-machine wide-area collaboration disclosed in an embodiment of the present invention. Figure 2 This is a structural diagram of a front-end control subsystem of a multi-station and multi-machine wide-area collaborative UAV command and control system disclosed in an embodiment of the present invention. Figure 3 This is a schematic diagram of the structure of a background management subsystem of a multi-station multi-machine wide-area collaborative UAV command and control system disclosed in an embodiment of the present invention. Figure 1-3 The described command and control system for multi-station and multi-machine wide-area collaboration of UAVs is applied to the command and control field, such as the command and control of UAVs, and is not limited in the embodiments of the present invention.

[0099] like Figure 1 As shown, the system includes N drone groups, a front-end command and control subsystem, and a back-end management subsystem; N is an integer greater than 1;

[0100] The above-mentioned drone group includes a drone ground station and several drones.

[0101] It should be noted that the UAV ground station is an important part of the UAV system. It is responsible for communicating with the UAV in the air, executing flight route planning, monitoring flight status, processing flight data, controlling the takeoff and landing of the UAV, and intervening and taking over control in emergency situations to ensure the smooth execution of the UAV mission and flight safety.

[0102] The above-mentioned front-end command and control subsystem is connected with the back-end management subsystem and drone data for mission monitoring, mission planning and situation monitoring.

[0103] The above-mentioned front-end command and control subsystem is connected with the back-end management subsystem and drone data for mission monitoring, mission planning and situation monitoring.

[0104] It can be seen that through the front-end command and control subsystem and the back-end management subsystem, the unified scheduling of multiple UAV ground stations and their assigned UAVs can be achieved.

[0105] In an optional embodiment, if Figure 2 As shown, the foreground control subsystem includes a task monitoring module, a task planning module and a situation monitoring module.

[0106] The task monitoring module includes a task end queue maintenance unit, a task new queue maintenance unit, a task cancel queue maintenance unit and a task display unit.

[0107] The above-mentioned end task queue maintenance unit is in data communication with the task planning module and the background management subsystem to construct an end task queue; the above-mentioned end task queue includes several end task numbers.

[0108] The newly added task queue maintenance unit is in data communication with the task planning module and is used to construct a newly added task queue; the newly added task queue includes several task tuples.

[0109] The above-mentioned task tuple includes task instructions, release time, execution status, target information, and task requirement information; the value of the above-mentioned execution status is executing, ended, or canceled; the above-mentioned target information includes target number, target name, and target coordinates.

[0110] It should be noted that these mission commands are sent to drones to control them to execute corresponding actions. These include reconnaissance, strike, jamming, or communication commands, corresponding to the four types of actions: reconnaissance, strike, jamming, and communication. The user fills in these mission commands based on pre-set action templates. For example, the corresponding action template for reconnaissance is shown in Table 1.

[0111] It should be noted that the above mission requirement information includes flight time requirement value, range requirement value, take-off weight requirement value, ceiling requirement value, payload configuration requirement list, and weapon configuration requirement list.

[0112] Table 1 Reconnaissance Operation Template

[0113]

[0114] It should be noted that the target coordinates include target accuracy and target latitude. The target information may also include target type, target height, target structure, target material, target area, number of targets, importance level and target introduction, which are not limited in the embodiment of the present invention.

[0115] The cancellation task queue maintenance unit is in data communication with the task planning module and is used to construct a cancellation task queue; the cancellation task queue includes a number of task numbers to be cancelled.

[0116] The above-mentioned task display unit is in data communication with the task planning module, and is used to jointly display the task tuple sequence and execution resource tree sequence output by the task planning module; the above-mentioned task tuple sequence includes several task tuples.

[0117] The execution resource tree sequence includes a plurality of available resource trees; the child nodes of the available resource trees are all marked as busy, occupied, unavailable or idle.

[0118] The above-mentioned execution resource tree sequence includes several available resource trees; the above-mentioned available resource tree includes a root node, N intermediate nodes and several leaf nodes; the above-mentioned N intermediate nodes correspond to N UAV ground stations respectively; each leaf node corresponds to 1 UAV; the above-mentioned leaf nodes are all marked as busy, occupied, unavailable or idle.

[0119] It should be noted that the above-mentioned intermediate nodes are direct child nodes of the root node; the above-mentioned leaf nodes are direct child nodes of the intermediate nodes; the direct parent node is the leaf node of the same intermediate node, and the corresponding drones are assigned to the same drone ground station.

[0120] The above-mentioned task planning module communicates with the drone and the background management subsystem data, and is used to perform task planning processing on the available resource tree, the new task queue, the canceled task queue and the ended task queue to obtain the task tuple sequence and the execution resource tree sequence.

[0121] The above situation monitoring module is connected to the background management subsystem data, and is used to display the situation using the combat environment information and force and equipment information set stored in the background management subsystem.

[0122] As can be seen, the independent maintenance units for the ended task queue, the added task queue, and the canceled task queue maintain the ended task queue, the added task queue, and the canceled task queue, respectively, allowing UAV resource scheduling to take into account the three scenarios of task ending, task adding, and task canceling. These three queues, along with the available resource tree, are processed by the mission planning module to coordinate the scheduling of UAV resources under these three scenarios.

[0123] In another optional embodiment, the above-mentioned front-end control subsystem further includes an intelligence monitoring module.

[0124] The above-mentioned intelligence monitoring module includes an intelligence aggregation unit and an intelligence display unit.

[0125] The above-mentioned intelligence aggregation unit is used to receive intelligence information input from the outside and sort it in the order of reception time to obtain an intelligence information sequence.

[0126] The above intelligence information includes batch number, receipt time, intelligence source, intelligence type, identification, longitude, latitude, altitude, length, width, direction, speed, threat level, annotations and annotator.

[0127] The above-mentioned intelligence display unit is connected to the intelligence aggregation unit data and is used to display the intelligence information sequence.

[0128] In another optional embodiment, Figure 3 As shown, the above-mentioned background management subsystem includes a basic data management module and a communication network management module.

[0129] The above basic data management module includes a basic data storage unit and an equipment information updating unit.

[0130] The above-mentioned basic data storage unit is connected to the equipment information update unit and the front-end command and control subsystem data, and is used to store force and equipment information sets and combat environment information.

[0131] It should be noted that the aforementioned operational environment information includes geographic information system vector data, satellite imagery data, feature identification data, and information about areas requiring routine maintenance. This information includes the area number, area name, area point list, rasterization type, and number of blocks.

[0132] The above-mentioned force and equipment information set includes N force and equipment information; the above-mentioned force and equipment information includes ground station information and several equipment information; the above-mentioned ground station information includes ground station number, ground station communication address, ground station coordinates and commander information; the above-mentioned equipment information includes UAV status information and UAV communication address.

[0133] It should be noted that the above-mentioned commander information includes the commander number, commander name, commander rank, commander contact number and the name of the superior commander.

[0134] It should be noted that the above-mentioned UAV strength information includes UAV model, UAV name, assigned ground station number, flight time, range, maximum take-off weight, ceiling, payload configuration list, and weapon configuration list.

[0135] It should be noted that the above-mentioned N force and equipment information correspond to N UAV ground stations respectively; the number of equipment information in each force and equipment information is equal to the number of UAVs assigned to the corresponding UAV ground station, and each assigned UAV corresponds to one piece of equipment information.

[0136] The above-mentioned drone status information includes drone number, real-time coordinates, mission number, mission status, mission target and strength information; the value of the above-mentioned mission status is executing, completed or canceled.

[0137] It should be noted that the above real-time coordinates include the real-time longitude and latitude of the drone.

[0138] It should be noted that the above-mentioned task number is the sequence number of the task tuple corresponding to the task performed by the drone in the task tuple sequence.

[0139] It should be noted that the above strength information includes remaining flight time, remaining range, maximum take-off weight, ceiling, payload configuration list, and weapon configuration list.

[0140] It should be noted that the aforementioned missions fall under the responsibility of either the leader or the wingman. The leader is responsible for planning the flight path and speed of the entire formation based on mission requirements and environmental conditions. The wingman, in turn, adjusts its flight state based on the leader's position and speed information to maintain its relative position and formation with the leader. When encountering obstacles or requiring a change in flight state, the leader is responsible for making decisions and directing the wingman to make appropriate adjustments.

[0141] The equipment information updating unit is in data communication with the communication management module for updating information.

[0142] It should be noted that the above-mentioned information update includes: in response to receiving the drone status information forwarded by the status information forwarding unit, using the drone number therein to search for the corresponding drone status information in the force and equipment information set, and using the received drone status information to replace the corresponding drone status information in the force and equipment information set; in response to receiving the ground station status information forwarded by the status information forwarding unit, using the ground station number therein to search for the corresponding ground station information in the force and equipment information set, and using the received ground station status information to replace the corresponding ground station information in the force and equipment information set;

[0143] The above-mentioned communication management module includes a state information forwarding unit and an available resource tree generating unit.

[0144] The above-mentioned status information forwarding unit communicates data with the UAV ground station, UAV, front-end command and control subsystem and equipment information update unit, and is used to forward UAV status information and ground station status information; the above-mentioned ground station status information includes the ground station number, ground station communication address, ground station coordinates and commander information.

[0145] It should be noted that the aforementioned status information forwarding unit, upon receiving ground station status information from the UAV ground station, forwards it in real time to the equipment information updating unit. Furthermore, upon receiving drone status information from the drone, the unit forwards it in real time to the equipment information updating unit and the end-task queue maintenance unit of the front-end command and control subsystem. This real-time forwarding can be performed at intervals of a predetermined waiting time, which can be 1 second, and is not limited in this embodiment of the present invention.

[0146] It can be seen that through the status information forwarding unit and the equipment information update unit, it can be ensured that the ground station information and UAV status information in the force and equipment information set are kept updated in real time, thereby reflecting the battlefield situation in a timely manner, thereby assisting users to reasonably schedule resources.

[0147] The above-mentioned available resource tree generation unit is in data communication with the basic data storage unit and the front-end command and control subsystem, and is used to process the force and equipment information set to obtain the available resource tree.

[0148] It can be seen that through the available resource tree, the available status of drone resources can be perceived in real time from a global perspective, avoiding the inability to execute tasks due to communication failures and other reasons after some resources are scheduled.

[0149] In another optional embodiment, the above-mentioned end task queue maintenance unit constructs the end task queue, including:

[0150] A1. Initialize the end task queue to an empty queue.

[0151] A2. In response to receiving the drone status information forwarded by the status information forwarding unit, determining whether the mission status value in the drone status information is ended, and obtaining a first status determination result;

[0152] When the result of the first status judgment is yes, the current ended task number is set as the task number T of the drone status information;

[0153] When the first state judgment result is no, execute A5.

[0154] It should be noted that when each drone finishes its ongoing mission, it sets the mission status in the drone status information to ended and sends it to the background management subsystem. The status information forwarding unit of the background management subsystem forwards it to the end mission queue maintenance unit of the foreground command and control subsystem to ensure that the mission tuple sequence can be updated in a timely manner and further coordinate the scheduling of the corresponding drones.

[0155] A3. Determine whether the execution status of the Tth task tuple in the task tuple sequence is "Ended," and obtain a second status determination result.

[0156] When the second state judgment result is yes, execute A5;

[0157] When the second state judgment result is no, the end task queue is updated by enqueuing to obtain an updated end task queue.

[0158] It should be noted that the above task tuple sequence is read from the basic data management module.

[0159] A4. Set the execution status of the Tth task tuple in the task tuple sequence to finished.

[0160] It should be noted that the above-mentioned use of T to enqueue the completed task queue is to insert T at the end of the newly added task queue.

[0161] A5. Repeat A2 to A4 until the end signal from external input is received.

[0162] It should be noted that the above-mentioned end signal can be a combat stop signal input by the user or received by the superior, and the embodiment of the present invention does not limit this.

[0163] This double check prevents the same UAV status information from being received multiple times due to communication or other reasons, which could result in the same completed task number being placed multiple times in the completed task queue. This could lead to duplicate processing and reduced system efficiency. Furthermore, if the execution status of a task tuple in the task tuple sequence is already completed, even if the execution status of the UAV status information corresponding to the task tuple is still completed when it is received again, the corresponding task number will not be inserted into the end of the completed task queue.

[0164] In another optional embodiment, the newly added task queue maintenance unit constructs the newly added task queue, including:

[0165] A6. Initialize the newly added task queue as an empty queue.

[0166] A7. In response to receiving the task tuple input by the user, insert the task tuple into the end of the newly added task queue to obtain an updated newly added task queue.

[0167] It should be noted that in the task tuple input by the user, the value of the task status is fixed as "Executing".

[0168] A8. Repeat A6 to A7 until the end signal from external input is received.

[0169] In another optional embodiment, the cancellation task queue maintenance unit constructs the cancellation task queue, including:

[0170] A9. Initialize the cancel task queue to an empty queue.

[0171] A10. In response to receiving the to-be-revoked task number input by the user, insert the to-be-revoked task number into the end of the revoked task queue to obtain an updated revoked task queue.

[0172] A11. Repeat A9 to A10 until the end signal from external input is received.

[0173] In yet another optional embodiment, the task display unit links and displays the task tuple sequence and the resource tree sequence output by the background management subsystem, including:

[0174] A12. Display the task tuple sequence as a task list in a preset first display area; each row of the task list corresponds to a task tuple, and the row number of each row corresponds to the sequence number of the task tuple in the task tuple sequence.

[0175] A13. In response to the user selecting the Lth row in the task list, display the Lth resource tree in the resource tree sequence as a tree diagram in a preset second display area.

[0176] It should be noted that the first display area and the second display area may be rectangular areas on a graphical interface, which is not limited in the embodiment of the present invention.

[0177] Preferably, in the above tree diagram, nodes marked as busy, occupied, unavailable or idle are displayed in different colors.

[0178] In another optional embodiment, the situation monitoring module uses combat environment information and force and equipment information to display the situation, including:

[0179] C1. In the preset third display area, a combat area map is displayed using combat environment information.

[0180] C2. Obtain the ground station coordinates and ground station number of each ground station information in the force and equipment information set in sequence; display the preset ground station icon and the corresponding ground station number at the corresponding position of each ground station coordinate on the combat area map.

[0181] C3. Sequentially obtain the drone number of each piece of equipment information in the force and equipment information set, as well as the drone coordinates in the corresponding drone status information; display the preset drone icon and the corresponding drone number at the corresponding position of the drone coordinates on the combat area map.

[0182] C4. Repeat C1 to C3 until the end signal from external input is received.

[0183] It should be noted that the above-mentioned target icons, ground station icons and drone icons are all preset two-dimensional graphics.

[0184] Preferably, in response to the user's selection operation of the ground station icon on the combat area map, the corresponding ground station information or equipment information is displayed in text form in the preset fourth display area.

[0185] Preferably, in response to the user's selection operation of the drone icon on the combat area map, the corresponding equipment information is displayed in text form in the preset fifth display area, and the target icon and the corresponding target number are displayed at the position corresponding to the target coordinates in the corresponding equipment information on the combat area map.

[0186] Preferably, each UAV ground station and UAV sends real-time environmental video to the UAV command and control system for multi-station and multi-machine wide-area collaboration; in response to the user's selection operation of the ground station icon or the UAV icon on the combat area map, the corresponding environmental video is displayed in the preset sixth display area.

[0187] It should be noted that the third display area, the fourth display area, the fifth display area and the sixth display area may be rectangular areas on the graphical interface, which is not limited in the embodiment of the present invention.

[0188] It can be seen that through the situation monitoring module, the locations of N drone ground stations and their assigned drones, related text information and environmental videos can be presented in real time, helping users to reasonably determine the drone resources that need to be dispatched.

[0189] In yet another optional embodiment, the available resource tree generating unit processes the force and equipment information set to obtain the available resource tree, including:

[0190] B1. Create a force organization tree with only one root node; initialize the first loop number mm to 1.

[0191] B2. Create the mmth intermediate node Node 1, mm ; Set the current force and equipment information to the mmth force and equipment information in the force and equipment information set; set the communication address of the ground station to be connected to the ground station communication address of the ground station information in the current force and equipment information; use the address of the ground station to be connected to obtain the communication status of the ground station; the value of the ground station communication status is connected or not connected.

[0192] B3, using the ground station communication status, the intermediate node Node 1, mm Perform the first marking process to obtain the intermediate node Node after the first marking 1, mm ;Use the intermediate node Node 1, mm , perform a first update process on the force organization tree to obtain the force organization tree after the first update process.

[0193] It should be noted that the first update process mentioned above is to mark the intermediate node Node 1, mm , set as the direct child node of the root node of the troop organization tree.

[0194] B4. Determine the current total number of equipment NN, which is the number of equipment information in the current force equipment information; and initialize the second loop number nn to 1.

[0195] B5. Create the nth leaf node 2,nn ; Determine the communication address of the drone to be connected, which is the communication address of the drone of the nth equipment information in the current force equipment information; use the communication address of the drone to be connected to obtain the current drone communication status; the value of the drone communication status is connected or not connected.

[0196] B6. Using the drone communication status, the leaf node 2,nnPerform the second marking process to obtain the leaf node after the second marking 2,nn ; Using leaf nodes 2,nn , perform a second update on the force organization tree to obtain the force organization tree after the second update; add 1 to the value of nn.

[0197] It should be noted that the second update process is to mark the leaf node Node 2,nn , set as the middle node of the troop organization tree 1, mm The direct child nodes of .

[0198] B7. Repeat B5-B6 until nn is greater than NN.

[0199] B8. Repeat B2 to B7 until mm is greater than N.

[0200] B9. Determine the available resource tree as the troop organization tree.

[0201] B10. Repeat B1 to B9 until the end signal from external input is received.

[0202] In yet another optional embodiment, the method of obtaining the connection status of the ground station by using the address of the ground station to be connected includes:

[0203] B21. Preset request data packet and response data packet.

[0204] It should be noted that the above request data packet and response data packet are a string of binary sequences, which is not limited in the embodiment of the present invention.

[0205] B22. Send a request data packet to the address of the ground station to be connected.

[0206] B23. Wait for the preset response time.

[0207] If a response data packet is received from the address of the ground station to be connected within the response time, the ground station communication status will be set to connected.

[0208] If no response data packet is received from the address of the ground station to be connected within the response time, the ground station communication status will be set to disconnected.

[0209] Preferably, the above response time is 1s.

[0210] In yet another optional embodiment, the first marking process includes:

[0211] The value of the ground station communication status is judged to obtain a third status judgment result.

[0212] When the third state judgment result is connected, the intermediate node Node 1, mmMark as free.

[0213] When the third state judgment result is not connected, the intermediate node Node 1, mm Marked as unavailable.

[0214] In another optional embodiment, the above-mentioned method of obtaining the current communication status of the drone using the communication address of the drone to be connected includes:

[0215] B51. Send a request data packet to the communication address of the drone to be connected.

[0216] B52. Wait for the preset response time.

[0217] If a response data packet is received from the communication address of the drone to be connected within the response time, the current drone communication status will be set to connected.

[0218] If no response data packet is received from the communication address of the drone to be connected within the response time, the current drone communication status will be set to disconnected.

[0219] In yet another optional embodiment, the second marking process includes:

[0220] The current drone communication status is judged to obtain the fourth status judgment result:

[0221] When the fourth state judgment result is connected, the leaf node Node 2,nn Mark as free;

[0222] When the fourth state judgment result is not connected, the leaf node Node 2,nn Marked as unavailable.

[0223] In another optional embodiment, the above-mentioned task planning processing is performed on the available resource tree, the newly added task queue, the cancelled task queue, and the ended task queue to obtain the task tuple sequence and the execution resource tree sequence, including:

[0224] S1. Initialize the task tuple sequence to an empty sequence; initialize the execution resource tree sequence to contain only available resource trees.

[0225] S2. Perform resource allocation processing on the newly added task queue, the task tuple sequence, and the execution resource tree sequence to obtain a first task tuple sequence and a first resource tree sequence.

[0226] S3. Perform resource recovery processing on the revoked task queue, the first task tuple sequence, and the first resource tree sequence to obtain a second task tuple sequence and a second resource tree sequence.

[0227] S4. Perform resource reallocation processing on the finished task queue, the second task tuple sequence, and the second resource tree sequence to obtain a third task tuple sequence and a third resource tree sequence.

[0228] S5. Set the task tuple sequence and the execution resource tree sequence as a third task tuple sequence and a third resource tree sequence, respectively.

[0229] S6. Repeat S2 to S5 until the end signal from external input is received.

[0230] In yet another optional embodiment, the resource allocation process is performed on the newly added task queue, the task tuple sequence, and the execution resource tree sequence to obtain the first task tuple sequence and the first resource tree sequence, including:

[0231] S21, determining whether the newly added task queue is empty, and obtaining a first determination result;

[0232] When the first judgment result is yes, execute S25;

[0233] When the first judgment result is no, the current newly added task tuple is set as the task tuple at the head of the newly added task queue; the newly added task queue is dequeued and updated to obtain the newly added task queue after dequeuing and updating.

[0234] It should be noted that the above dequeue update removes an element from the front of the queue.

[0235] S22: Using the current newly added task tuple, perform task allocation update on the execution resource tree sequence to obtain the execution resource tree sequence after task allocation update.

[0236] S23. Using the currently added task tuple, the task tuple sequence is expanded and updated to obtain an expanded and updated task tuple sequence.

[0237] It should be noted that the above expansion and update of the task tuple sequence is to insert the current newly added task tuple into the end of the task tuple sequence.

[0238] S24. Repeat S21 to S23.

[0239] S25 . Determine a first task tuple sequence and a first resource tree sequence, which are a task tuple sequence and an execution resource tree sequence respectively.

[0240] It can be seen that with the help of the newly added task queue, after the user analyzes the content displayed by the situation monitoring module, when a new task is needed, the allocation and scheduling of drone resources can be carried out.

[0241] In another optional embodiment, the above-mentioned task allocation update of the execution resource tree sequence using the current newly added task tuple to obtain the execution resource tree sequence after the task allocation update includes:

[0242] S221. Acquire the last available resource tree in the execution resource tree sequence to obtain the current resource tree.

[0243] S222: Filter the current resource tree using the newly added task tuple to obtain a filtered resource tree.

[0244] S223 . In response to the user operation, perform a third marking process on the filtered resource tree to obtain a marked resource tree.

[0245] S224: Send the task instructions in the current newly added task tuple to the UAV corresponding to the leaf node marked as occupied in the marked resource tree.

[0246] S225: Insert the marked resource tree into the end of the execution resource tree sequence to obtain the execution resource tree sequence after task allocation is updated.

[0247] In another optional embodiment, the above-mentioned filtering process of the current resource tree using the newly added task tuple to obtain the filtered resource tree includes:

[0248] S2221. Re-mark the leaf nodes marked as occupied in the current resource tree as busy, to obtain a first resource tree.

[0249] It should be noted that after S2221 is executed, the leaf nodes in the first resource tree only contain three marking indicators: unavailable, idle, and busy.

[0250] S2222: Using the newly added task tuple, sequentially perform instance demand judgment on all leaf nodes marked as idle in the first resource tree to obtain instance demand judgment results;

[0251] When the instance requirement judgment result is yes, the first resource tree remains unchanged;

[0252] When the instance demand judgment result is negative, the leaf node marked as idle is re-marked as unavailable.

[0253] S2223: Determine that the filtered resource tree is the first resource tree.

[0254] Optionally, the above-mentioned strength requirement determination for the leaf node marked as idle includes:

[0255] Find the UAV corresponding to the leaf node marked as idle, and obtain the idle strength information from the UAV status information in the force and equipment information set; compare the idle strength information with the task requirement information in the newly added task tuple to obtain the instance requirement judgment result.

[0256] It should be noted that a yes result in the above instance requirement judgment means that the remaining flight time, remaining range, maximum takeoff weight, and ceiling in the idle strength information are respectively greater than the flight time requirement value, range requirement value, takeoff weight requirement value, and ceiling requirement value of the mission requirement information in the mission tuple, and the payload configuration list and weapon configuration list in the idle strength information respectively include the payload configuration requirement list and weapon configuration requirement list of the mission requirement information in the mission tuple. A no result in the instance requirement judgment means that the remaining flight time, remaining range, maximum takeoff weight, or ceiling in the idle strength information is not greater than the flight time requirement value, range requirement value, takeoff weight requirement value, or ceiling requirement value of the mission requirement information in the mission tuple, or the payload configuration list or weapon configuration list in the idle strength information respectively includes the payload configuration requirement list or weapon configuration requirement list of the mission requirement information in the mission tuple.

[0257] It should be noted that after S2222 is executed, the nodes in the first resource tree include three tags: idle, busy, and unavailable.

[0258] In yet another optional embodiment, in response to a user operation, performing a third marking process on the filtered resource tree to obtain a marked resource tree includes:

[0259] S2231. Display the filtered resource tree in a graphical interface, wherein leaf nodes marked as busy, idle, and unavailable are displayed in three different colors.

[0260] S2232. In response to the user operation, the leaf nodes marked as idle in the filtered resource tree are selected, and the selected leaf nodes are re-marked as occupied, thereby obtaining a marked resource tree to complete the force allocation for this mission.

[0261] It should be noted that the nodes in the marked resource tree include four tags: idle, busy, unavailable and occupied.

[0262] In yet another optional embodiment, the above-mentioned resource recovery process is performed on the revoked task queue, the first task tuple sequence, and the first resource tree sequence to obtain the second task tuple sequence and the second resource tree sequence, including:

[0263] S31, determining whether the cancellation task queue is empty to obtain a second determination result;

[0264] When the second judgment result is yes, execute S35;

[0265] When the second judgment result is no, the current to-be-revoked number is set as the to-be-revoked task number q1 at the head of the revocation task queue; the revocation task queue is dequeued and updated to obtain the revocation task queue after dequeuing and updating.

[0266] S32, determining whether the execution status of the q1th task tuple in the first task tuple sequence is ended or in progress, and obtaining a third determination result;

[0267] When the third judgment result is yes, it indicates that no cancellation is required, and S31 is executed;

[0268] When the third judgment result is no, the execution state of the q1th task tuple in the first task tuple sequence is set to cancel.

[0269] S33: Use the resource tree to be revoked to perform a revocation update on the first resource tree sequence to obtain a revocation-updated first resource tree sequence.

[0270] S34. Repeat S31 to S33.

[0271] S35 . Determine a second task tuple sequence and a second resource tree sequence, which are the first task tuple sequence and the first resource tree sequence respectively.

[0272] It can be seen that with the help of the task cancellation queue, when the user analyzes the content displayed by the situation monitoring module, or receives a task cancellation instruction sent by the superior, when a task needs to be canceled, the executing task can be canceled and the drone resources therein can be recovered. It can also be reflected in time to the cancellation of the task and its subsequent tasks, all corresponding task tuples and available resource trees, so that the recovered drone resources can be used by the subsequent newly added task scheduling.

[0273] In yet another optional embodiment, the above-mentioned undoing and updating of the first resource tree sequence includes:

[0274] S331. Set the revocation update number L1 to q1.

[0275] S332, judging the value of q1;

[0276] When q1 is not less than the length of the first resource tree sequence, execute S336;

[0277] When q1 is less than the length of the first resource tree sequence, S333 is executed.

[0278] S333: traverse the leaf nodes of the q1th available resource tree in the first resource tree sequence, and judge the visited leaf nodes during each traversal;

[0279] When the accessed leaf node is marked as occupied, and the leaf node corresponding to the accessed leaf node in the q1+1th available resource tree of the first resource tree sequence is not marked as occupied, the corresponding node in the q1+1th available resource tree of the first resource tree sequence is marked as free;

[0280] When the visited leaf node is not marked as occupied, or the leaf node corresponding to the visited leaf node in the q1+1th available resource tree of the first resource tree sequence is marked as occupied, the q1+1th available resource tree of the first resource tree sequence remains unchanged.

[0281] S334. Add 1 to the value of q1.

[0282] S335. Repeat S332 to S334.

[0283] S336 : Mark all leaf nodes marked as occupied in the L1 th available resource tree of the first resource tree sequence as idle.

[0284] In yet another optional embodiment, the resource reallocation process is performed on the finished task queue, the second task tuple sequence, and the second resource tree sequence to obtain a third task tuple sequence and a third resource tree sequence, including:

[0285] S41, determining whether the completed task queue is empty to obtain a fourth determination result;

[0286] When the fourth judgment result is yes, execute S45;

[0287] When the fourth judgment result is no, the current completion number is set as the to-be-cancelled task number q2 at the head of the end task queue; the end task queue is dequeued and updated to obtain the end task queue after dequeuing and updating.

[0288] S42: Reallocate and update the second resource tree sequence to obtain a reallocated and updated second resource tree sequence.

[0289] S43: Set the execution status of the q2th task tuple in the second task tuple sequence to end.

[0290] S44. Repeat S41 to S43.

[0291] S45 . Determine a third task tuple sequence and a third resource tree sequence, which are the second task tuple sequence and the second resource tree sequence respectively.

[0292] In yet another optional embodiment, the above-mentioned reallocation update includes:

[0293] S431, judging the value of q2;

[0294] When q2 is not less than the length of the second resource tree sequence, executing S44;

[0295] When q2 is less than the length of the second resource tree sequence, S432 is executed.

[0296] S432: traverse the leaf nodes of the q2th available resource tree in the second resource tree sequence, and judge the visited leaf nodes during each traversal.

[0297] When the accessed leaf node is marked as busy, and the leaf node corresponding to the accessed leaf node in the q2+1th available resource tree of the second resource tree sequence is not marked as occupied, marking the corresponding node of the q2+1th available resource tree of the second resource tree sequence as free;

[0298] When the visited leaf node is not marked as busy, or the leaf node corresponding to the visited leaf node in the q2+1th available resource tree of the second resource tree sequence is marked as occupied, the q2+1th available resource tree of the second resource tree sequence remains unchanged.

[0299] S433. Add 1 to the value of q2.

[0300] S434. Repeat S431 to S433.

[0301] It can be seen that the drone command and control system for multi-station and multi-machine wide-area collaboration described in the embodiment of the present invention can realize the coordinated scheduling of drones in multi-station and multi-machine scenarios by uniformly abstracting drones into resources and further uniformly representing and allocating the use of multiple drone ground stations and their assigned drones through the available resource tree.

[0302] Example 2

[0303] An embodiment of the present invention discloses a computer-readable storage medium, which includes a drone command and control system for multi-station, multi-machine wide-area collaboration, as described in Example 1. It should be noted that for a detailed description of the drone command and control system for multi-station, multi-machine wide-area collaboration, please refer to the specific description of the relevant content in Example 1, and this embodiment will not be repeated here.

[0304] Example 3

[0305] An embodiment of the present invention discloses an electronic device, comprising the drone command and control system for multi-station, multi-machine wide-area collaboration as described in Example 1. It should be noted that for a detailed description of the drone command and control system for multi-station, multi-machine wide-area collaboration, please refer to the specific description of the relevant content in Example 1, and this embodiment will not be repeated here.

[0306] The device embodiments described above are merely illustrative. Modules described as separate components may or may not be physically separate, and components shown as modules may or may not be physical modules, i.e., they may be located in one place or distributed across multiple network modules. Some or all of the modules may be selected based on actual needs to achieve the objectives of the present embodiment. Persons of ordinary skill in the art will be able to understand and implement the present invention without inventive effort.

[0307] Through the detailed description of the above embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, or of course, by means of hardware. Based on this understanding, the above technical solution, in essence, or the portion that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a read-only memory (ROM), a random access memory (RAM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), a one-time programmable read-only memory (OTPROM), an electronically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disk storage, magnetic disk storage, magnetic tape storage, or any other computer-readable medium capable of carrying or storing data.

[0308] Finally, it should be noted that the embodiment of the present invention discloses a drone command and control system for multi-station and multi-machine wide-area collaboration, which only discloses a preferred embodiment of the present invention and is only used to illustrate the technical solution of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, ordinary technicians in this field should understand that it is still possible to modify the technical solutions recorded in the aforementioned embodiments, or to replace some of the technical features therein with equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims

1. A UAV command and control system for multi-station and multi-machine wide-area collaboration, characterized by: It includes N drone groups, a front-end command and control subsystem, and a back-end management subsystem; N is an integer greater than 1; A drone group, including a drone ground station and several drones; Front-end command and control subsystem, including task monitoring module, task planning module and situation monitoring module; Task monitoring module, including end task queue maintenance unit, new task queue maintenance unit, cancel task queue maintenance unit and task display unit; The end task queue maintenance unit is in data communication with the task planning module and the background management subsystem to construct an end task queue; the end task queue includes a number of end task numbers; The newly added task queue maintenance unit is in data communication with the task planning module and is used to construct a newly added task queue; the newly added task queue includes a plurality of task tuples; The task tuple includes task instructions, release time, execution status, target information, and task requirement information; the execution status value is executing, ended, or canceled; the target information includes target number, target name, and target coordinates; The revocation task queue maintenance unit is in data communication with the task planning module and is used to construct a revocation task queue; the revocation task queue includes a number of task numbers to be revoked; The task display unit is in data communication with the task planning module and is used to display the task tuple sequence and execution resource tree sequence output by the task planning module in a linked manner; the task tuple sequence includes a plurality of task tuples; The execution resource tree sequence includes several available resource trees; the available resource tree includes a root node, N intermediate nodes and several leaf nodes; the N intermediate nodes correspond to N UAV ground stations respectively; each leaf node corresponds to one UAV; the leaf nodes are all marked as busy, occupied, unavailable or idle; A task planning module, communicating with the drone and the background management subsystem, is used to perform task planning processing on the available resource tree, the newly added task queue, the canceled task queue, and the ended task queue to obtain the task tuple sequence and the execution resource tree sequence; The situation monitoring module is connected to the background management subsystem data and is used to display the situation using the combat environment information and force and equipment information stored in the background management subsystem; The background management subsystem communicates with the drone and the drone ground station data, and is used for basic data management and communication network management.

2. The UAV command and control system for multi-station and multi-machine wide-area collaboration according to claim 1 is characterized in that: The background management subsystem includes a basic data management module and a communication network management module; The basic data management module includes a basic data storage unit and an equipment information updating unit; The basic data storage unit is in data communication with the equipment information update unit and the front-end command and control subsystem, and is used to store a collection of troop equipment information and combat environment information; The force and equipment information set includes N pieces of force and equipment information; the force and equipment information includes ground station information and a plurality of pieces of equipment information; the ground station information includes a ground station number, a ground station communication address, ground station coordinates, and commander information; the equipment information includes UAV status information and a UAV communication address; The drone status information includes the drone number, real-time coordinates, mission number, mission status, mission objective, and capability information; the mission status value is in progress, completed, or canceled; The equipment information updating unit is in data communication with the communication network management module for updating information; The communication network management module includes a state information forwarding unit and an available resource tree generating unit; The status information forwarding unit is in data communication with the UAV ground station, the UAV, the front-end command and control subsystem, and the equipment information updating unit, and is used to forward UAV status information and ground station status information; The ground station status information includes the ground station number, ground station communication address, ground station coordinates and commander information; The available resource tree generating unit is in data communication with the basic data storage unit and the front-end command and control subsystem, and is used to process the force and equipment information set to obtain an available resource tree.

3. The UAV command and control system for multi-station and multi-machine wide-area collaboration according to claim 1 is characterized in that: The construction end task queue includes: A1. Initialize the end task queue to an empty queue; A2. In response to receiving the drone status information forwarded by the status information forwarding unit, determining whether the mission status value in the drone status information is ended, and obtaining a first status determination result; When the first state judgment result is yes, the current ended task number is set as the task number T of the drone state information; When the result of the first state judgment is no, execute A5; A3. Determine whether the execution status of the Tth task tuple in the task tuple sequence is ended, and obtain a second status determination result; When the second state determination result is yes, execute A5; When the result of the second state judgment is no, the end task queue is updated to obtain the updated end task queue; A4. Setting the execution status of the T-th task tuple in the task tuple sequence to end; A5. Repeat A2 to A4 until the end signal from external input is received.

4. The UAV command and control system for multi-station and multi-machine wide-area collaboration according to claim 2 is characterized in that: The processing of the military force and equipment information set to obtain an available resource tree includes: B1. Create a force organization tree with only one root node; initialize the first loop number mm to 1; B2. Create the mmth intermediate node Node 1, mm ; Set the current force and equipment information to the mth force and equipment information in the force and equipment information set; set the communication address of the ground station to be connected to the ground station communication address of the ground station information in the current force and equipment information; use the communication address of the ground station to be connected to obtain the communication status of the ground station; the value of the communication status of the ground station is connected or not connected; B3, using the ground station communication status, the intermediate node Node 1, mm Perform the first marking process to obtain the intermediate node Node after the first marking 1, mm ;Use the intermediate node Node 1, mm , performing a first update process on the force organization tree to obtain the force organization tree after the first update process; B4. Determine the total number of current equipment NN, which is the number of equipment information in the current force equipment information; initialize the second loop number nn to 1; B5. Create the nth leaf node 2,nn ; Determine the communication address of the drone to be connected, which is the communication address of the drone of the nth equipment information in the current force equipment information; use the communication address of the drone to be connected to obtain the current drone communication status; the value of the drone communication status is connected or not connected; B6, using the UAV communication status, the leaf node Node 2,nn Perform the second marking process to obtain the leaf node after the second marking 2,nn ; Using leaf nodes 2,nn , performing a second update process on the force organization tree to obtain the force organization tree after the second update process; adding 1 to the value of nn; B7. Repeat B5-B6 until nn is greater than NN. B8. Repeat B2 to B7 until mm is greater than N; B9. Determine the available resource tree as the force organization tree; B10. Repeat B1 to B9 until the end signal from external input is received.

5. The UAV command and control system for multi-station and multi-machine wide-area collaboration according to claim 1 is characterized in that: The step of performing task planning processing on the available resource tree, the newly added task queue, the canceled task queue, and the ended task queue to obtain the task tuple sequence and the execution resource tree sequence includes: S1. Initialize the task tuple sequence to an empty sequence; initialize the execution resource tree sequence to include only the available resource tree; S2, performing resource allocation processing on the newly added task queue, the task tuple sequence, and the execution resource tree sequence to obtain a first task tuple sequence and a first resource tree sequence; S3, performing resource recovery processing on the revoked task queue, the first task tuple sequence, and the first resource tree sequence to obtain a second task tuple sequence and a second resource tree sequence; S4, performing resource reallocation processing on the finished task queue, the second task tuple sequence, and the second resource tree sequence to obtain a third task tuple sequence and a third resource tree sequence; S5. Setting the task tuple sequence and the execution resource tree sequence as the third task tuple sequence and the third resource tree sequence, respectively; S6. Repeat S2 to S5 until the end signal from external input is received.

6. The UAV command and control system for multi-station and multi-machine wide-area collaboration according to claim 5 is characterized in that: The performing resource allocation processing on the newly added task queue, the task tuple sequence, and the execution resource tree sequence to obtain a first task tuple sequence and a first resource tree sequence includes: S21, determining whether the newly added task queue is empty to obtain a first determination result; When the first judgment result is yes, execute S25; When the first judgment result is no, setting the current newly added task tuple as the task tuple at the head of the newly added task queue; performing a dequeue update on the newly added task queue to obtain the newly added task queue after the dequeue update; S22, using the current newly added task tuple, performing task allocation update on the execution resource tree sequence to obtain the execution resource tree sequence after task allocation update; S23, using the current newly added task tuple to expand and update the task tuple sequence to obtain the expanded and updated task tuple sequence; S24, repeat S21 to S23; S25 . Determine the first task tuple sequence and the first resource tree sequence, which are the task tuple sequence and the execution resource tree sequence respectively.

7. The UAV command and control system for multi-station and multi-machine wide-area collaboration according to claim 6 is characterized in that: The step of performing task allocation update on the execution resource tree sequence by using the current newly added task tuple to obtain the execution resource tree sequence after task allocation update includes: S221, obtaining the last available resource tree in the execution resource tree sequence to obtain the current resource tree; S222, using the newly added task tuple to filter the current resource tree to obtain a filtered resource tree; S223. In response to a user operation, perform a third marking process on the screening resource tree to obtain a marked resource tree; S224: Send the task instruction in the current newly added task tuple to the UAV corresponding to the leaf node marked as occupied in the marked resource tree; S225: Insert the marked resource tree into the end of the execution resource tree sequence to obtain the execution resource tree sequence after the task allocation is updated.

8. The UAV command and control system for multi-station and multi-machine wide-area collaboration according to claim 5 is characterized in that: The performing resource recycling processing on the revoked task queue, the first task tuple sequence, and the first resource tree sequence to obtain a second task tuple sequence and a second resource tree sequence includes: S31, determining whether the cancellation task queue is empty to obtain a second determination result; When the second judgment result is yes, execute S35; When the second judgment result is no, the current to-be-revoked number is set as the to-be-revoked task number q1 at the head of the revoked task queue; the revoked task queue is dequeued and updated to obtain the revoked task queue after dequeuing and updating; S32, determining whether the execution status of the q1th task tuple in the first task tuple sequence is ended or in progress, and obtaining a third determination result; When the third judgment result is yes, execute S31; When the third judgment result is no, setting the execution state of the q1th task tuple in the first task tuple sequence to cancel; S33: Using the resource tree to be revoked, perform a revocation update on the first resource tree sequence to obtain the first resource tree sequence after revocation and update; S34, repeat S31 to S33; S35 . Determine the second task tuple sequence and the second resource tree sequence, which are the first task tuple sequence and the first resource tree sequence respectively.

9. The UAV command and control system for multi-station and multi-machine wide-area collaboration according to claim 5 is characterized in that: The performing resource reallocation processing on the finished task queue, the second task tuple sequence, and the second resource tree sequence to obtain a third task tuple sequence and a third resource tree sequence includes: S41, determining whether the finished task queue is empty to obtain a fourth determination result; When the fourth judgment result is yes, execute S45; When the fourth judgment result is no, the current completion number is set as the to-be-revoked task number q2 at the head of the finished task queue; the finished task queue is dequeued and updated to obtain the finished task queue after dequeuing and updating; S42: Reallocate and update the second resource tree sequence to obtain a reallocated and updated second resource tree sequence; S43, setting the execution status of the q2th task tuple in the second task tuple sequence to end; S44, repeat S41 to S43; S45 . Determine a third task tuple sequence and a third resource tree sequence, which are the second task tuple sequence and the second resource tree sequence respectively.

Images