Unified access and instruction generation method and system for multiple unmanned aerial vehicle defense devices

Abstract

This application discloses a unified access and command generation method and system for various drone defense devices, relating to the field of drone defense system technology. The method includes: matching dedicated protocol description models and control protocol models to different types of drone defense devices, driving communication data frame parsing and control command generation, thereby achieving unified access and collaborative management of at least two heterogeneous drone defense devices, meeting the needs of multi-device collaborative defense in complex scenarios.

Description

Technical Field

[0001] This application relates to the field of unmanned aerial vehicle (UAV) defense system technology, and more specifically, to a method and system for unified access and command generation of various UAV defense devices. Background Technology

[0002] Unmanned aerial vehicle (UAV) defense systems are primarily used to prevent the security risks posed by UAVs. Existing UAV defense systems integrate various defense devices such as UAV detection radar, radio spectrum detection equipment, optoelectronic reconnaissance equipment, and optoelectronic tracking equipment to achieve the detection, identification, tracking, and countermeasures against UAV targets.

[0003] In practical applications, the defense equipment connected to the drone defense system is usually designed and manufactured by different manufacturers. Due to the lack of a unified industry communication protocol and control standard, there are significant differences in communication methods, data protocol formats and control command specifications between different types and manufacturers of defense equipment.

[0004] Related technologies for accessing and controlling UAV defense equipment include: dedicated access and control solutions: for each type of defense equipment, dedicated communication access programs, data parsing logic, and equipment control logic are developed separately, usually implemented using hard coding; access solutions categorized by communication protocols: general communication modules are implemented according to communication methods such as TCP, UDP, HTTP, and MQTT, but customized programs still need to be written for different devices during the equipment data parsing and control command generation stages; and semi-general communication and control framework solutions: by abstracting the communication framework or middleware, the development complexity of the communication layer is reduced, but the equipment protocol structure and control command format are still implemented using embedded code or fixed templates, making it difficult to expand flexibly.

[0005] However, device access requires customized development, control command generation relies on hard coding, and data parsing and command generation logic are highly coupled. The commands generated by existing technologies are difficult to meet the needs of multi-device collaborative defense in complex scenarios. Summary of the Invention

[0006] The main purpose of this application is to provide a unified access and command generation method for multiple drone defense devices, so as to solve the problem that the existing drone defense system cannot meet the needs of multi-device collaborative defense in complex scenarios.

[0007] To achieve the above objectives, the first aspect of this application proposes a method for unified access and command generation of multiple unmanned aerial vehicle (UAV) defense devices, including: Receive a first communication data frame and a second communication data frame, wherein the first communication data frame is a communication data frame of a first drone defense device, and the second communication data frame is a communication data frame of a second drone defense device, and the first drone defense device and the second drone defense device are two different types of drone defense devices; Based on the device identification information of the first UAV defense device, a first protocol description model and a first control protocol model are determined in the protocol description model library. Similarly, based on the device identification information of the second UAV defense device, a second protocol description model is determined in the same library. The first protocol description model and the first control protocol model are the protocol description model and control protocol model corresponding to the first UAV defense device, respectively, and the second protocol description model is the protocol description model corresponding to the second UAV defense device. The first and second protocol description models are used to define the complete structure of the uplink data frames for the first and second UAV defense devices, respectively. The first control protocol model is used to define the generation rules for the downlink control commands of the first UAV defense device. The first communication data frame is parsed based on the first protocol description model to obtain the first UAV defense data, and the second communication data frame is parsed based on the second protocol description model to obtain the second UAV defense data; Based on the first control protocol model, the first UAV defense data, and the second UAV defense data, control commands for the first UAV defense device are generated.

[0008] Secondly, a unified access and command generation system for multiple UAV defense devices is proposed, including: A unified access module is used to receive a first communication data frame and a second communication data frame, wherein the first communication data frame is a communication data frame of a first UAV defense device, and the second communication data frame is a communication data frame of a second UAV defense device, and the first UAV defense device and the second UAV defense device are two different types of UAV defense devices. The model matching module is used to determine a first protocol description model and a first control protocol model in the protocol description model library based on the device identification information of the first UAV defense device, and to determine a second protocol description model in the protocol description model library based on the device identification information of the second UAV defense device. The first protocol description model and the first control protocol model are the protocol description model and control protocol model corresponding to the first UAV defense device, and the second protocol description model is the protocol description model corresponding to the second UAV defense device. The first and second protocol description models are used to define the complete structure of the uplink data frames of the first and second UAV defense devices, respectively; the first control protocol model is used to define the generation rules for the downlink control commands of the first UAV defense device. The protocol parsing module is used to parse the first communication data frame based on the first protocol description model to obtain the first UAV defense data, and to parse the second communication data frame based on the second protocol description model to obtain the second UAV defense data; The instruction generation module is used to generate control instructions for the first drone defense device based on the first control protocol model, the first drone defense data, and the second drone defense data.

[0009] Thirdly, an electronic device is proposed, comprising: At least one processor; and The memory is communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform any of the methods described in the present disclosure.

[0010] The technical solutions provided by the embodiments of this application may include the following beneficial effects: In this application, by matching exclusive protocol description models and control protocol models to different types of UAV defense devices, the communication data frame parsing and control command generation are driven, realizing unified access and collaborative management of at least two heterogeneous UAV defense devices, and meeting the needs of multi-device collaborative defense in complex scenarios. Attached Figure Description

[0011] The accompanying drawings, which form part of this application, are used to provide a further understanding of the application and to make other features, objects, and advantages of the application more apparent. The illustrative embodiments and descriptions of this application are used to explain the application and do not constitute an undue limitation of the application. In the drawings: Figure 1 A flowchart illustrating a method for unified access and command generation of multiple UAV defense devices provided in this application; Figure 2A flowchart illustrating a data receiving method provided in this application; Figure 3 A flowchart illustrating a control command issuance method provided in this application; Figure 4 A schematic diagram of a unified access and command generation system for multiple UAV defense devices provided in this application; Figure 5 This is a schematic diagram of the structure of an electronic device provided in this application. Detailed Implementation

[0012] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0013] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of this application described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0014] In this application, the terms "upper," "lower," "left," "right," "front," "rear," "top," "bottom," "inner," "outer," "middle," "vertical," "horizontal," "lateral," and "longitudinal" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. These terms are primarily for the purpose of better describing this application and its embodiments, and are not intended to limit the indicated device, element, or component to having a specific orientation, or to be constructed and operated in a specific orientation.

[0015] Furthermore, in addition to indicating location or positional relationship, some of the aforementioned terms may also have other meanings. For example, the term "above" may also be used in some cases to indicate a certain dependency or connection relationship. Those skilled in the art can understand the specific meaning of these terms in this application based on the specific circumstances.

[0016] Furthermore, the terms "installation," "setup," "equipped with," "connection," "linked," and "socketing" should be interpreted broadly. For example, "connection" can be a fixed connection, a detachable connection, or an integral structure; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, or an internal connection between two devices, components, or parts. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0017] Figure 1 This application provides a flowchart illustrating a method for unified access and command generation for multiple UAV defense devices. The method may include: S110. Receive a first communication data frame and a second communication data frame, wherein the first communication data frame is a communication data frame of a first drone defense device, and the second communication data frame is a communication data frame of a second drone defense device, and the first drone defense device and the second drone defense device are two different types of drone defense devices. In this step, communication data frames from various drone defense devices are received. In this embodiment, the drone defense devices are used for drone detection, identification, or tracking, including radar, radio spectrum detection equipment, and optoelectronic devices. The communication data frames can be structured data units transmitted by the drone defense devices through a communication network, and the communication method can employ network communication protocols such as TCP, UDP, MQTT, and HTTP.

[0018] The platform system can receive communication data frames from different types of drone defense equipment, such as data frames transmitted by drone detection radar via TCP protocol, data frames transmitted by radio spectrum detection equipment via MQTT protocol, and data frames transmitted by electro-optical tracking equipment via UDP protocol.

[0019] S120. Based on the device identification information of the first UAV defense device, determine the first protocol description model and the first control protocol model in the protocol description model library, and based on the device identification information of the second UAV defense device, determine the second protocol description model in the protocol description model library. The first protocol description model and the first control protocol model are the protocol description model and control protocol model corresponding to the first UAV defense device, and the second protocol description model is the protocol description model corresponding to the second UAV defense device. The first protocol description model and the second protocol description model are respectively used to define the complete structure of the uplink data frames of the first UAV defense device and the second UAV defense device; the first control protocol model is used to define the generation rules of the downlink control commands of the first UAV defense device. In this step, based on the device identification information of the drone defense device, the protocol description model and control protocol model corresponding to the drone defense device are matched in the protocol description model library. The protocol description model can be used to define the complete structure of the uplink data frame of the drone defense device, and the control protocol model can be used to define the generation rules of the downlink control commands of the drone defense device. In this embodiment, the device identification information can be a set of feature information that uniquely identifies the drone defense device, which may include device type identifier, manufacturer code, device model, access channel identifier, protocol version number, etc.

[0020] The protocol description model and control protocol model are bound and stored in the protocol description model library through device identifiers, ensuring a one-to-one correspondence between the "parsing model" and "control model" for the same device. The protocol description model is a purely configurable, structured data protocol definition model used to describe the complete structure of uplink data frames from UAV defense equipment. Its essence is not an executable program, parsing module, or binary template, but rather a protocol metadata model interpreted and executed by the parsing engine. The control protocol model describes the generation rules for downlink control commands from the UAV defense equipment, and its structure also adopts a configurable modeling approach.

[0021] By decoupling the data and control protocols of defense devices from the program code, unified access, dynamic parsing, and unified control of UAV defense devices are achieved. It supports unified access and control of multiple types of UAV defense devices, allowing management of devices from different manufacturers and of different types under a unified architecture. This solves the problems of difficult unified management of multiple types of defense devices, significant differences in data access and control methods for radar, spectrum, and optoelectronic devices, and complex system architectures in related UAV defense device access and control solutions.

[0022] When adding new drone defense equipment or changing the drone defense equipment protocol, it is only necessary to add or modify the corresponding protocol description model and control protocol model in the protocol description model library. There is no need to modify the core code. This solves the problems of poor equipment access and control flexibility in related technologies for drone defense equipment access and control. When adding new equipment or when the equipment protocol or control command changes, it is usually necessary to modify the program code and recompile and deploy. It also solves the problems of high coupling between protocol parsing logic and device control logic, with data parsing rules and device control command generation logic being fixed in the program and difficult to adjust flexibly through configuration. When equipment models are upgraded, protocols are adjusted, and control commands are frequently extended, it can be dealt with at low cost and low risk.

[0023] S130. Based on the first protocol description model, the first communication data frame is parsed to obtain the first UAV defense data, and based on the second protocol description model, the second communication data frame is parsed to obtain the second UAV defense data; In this step, communication data frames are parsed using a protocol description model to obtain the first UAV defense data. In this embodiment, the UAV defense data is the core data supporting UAV target detection, identification, tracking, and equipment collaborative control, reflecting the UAV target's operational status and the working status of the defense equipment. The corresponding UAV defense data is obtained by parsing the communication data frames of the UAV defense equipment based on their respective protocol description models.

[0024] S140. Based on the first control protocol model, the first UAV defense data, and the second UAV defense data, generate control commands for the first UAV defense device.

[0025] In this step, control commands are generated based on the control protocol model and drone defense data from at least two drone defense devices. In this embodiment, the control commands for the drone defense device are generated by collaboratively analyzing drone defense data from multiple devices, based on the protocol description model corresponding to the drone defense device. For example, control commands for the radar can be generated based on the protocol description model corresponding to the radar, combined with drone defense data from the radar and drone defense data from a radio spectrum detection device. Alternatively, control commands for the radar can be generated based on the protocol description model corresponding to the radar, combined with drone defense data from the radar and drone defense data from all other drone defense devices besides the radar.

[0026] According to the embodiments of this application, by matching exclusive protocol description models and control protocol models for different types of UAV defense devices, driving the parsing of communication data frames and the generation of control commands, unified access and collaborative management of at least two heterogeneous UAV defense devices can be achieved, meeting the needs of multi-device collaborative defense in complex scenarios.

[0027] In one implementation, it may further include: The protocol description model includes field description units, variable-length and loop structure definition units, and validation rule definition units; The control protocol model includes instruction structure definition units and parameter field mapping rule units.

[0028] In this embodiment, the protocol basic information unit in the protocol description model may include a protocol identifier ID, a device type identifier, a protocol version number, and a data frame direction identifier (e.g., uplink); the overall frame structure definition unit may include a frame header definition (e.g., a fixed byte sequence or feature field), a frame body structure definition, a frame tail or check field definition, and an identifier indicating whether a multi-target loop structure is supported; the field description unit (Field Descriptor) defines each field item by item, and may include a field name, field type (e.g., integer, floating-point, enumeration, bit field), field length (e.g., byte level or bit level), byte order rule (big-endian, little-endian), bit mask and bit offset rule, whether it is a variable-length field, and field dependencies; the variable-length and loop structure definition unit may include a target quantity field, loop parsing start position, single-target structure template, and loop termination condition; the check rule definition unit may include a check algorithm type (e.g., CRC, checksum), check field position, and check participation range.

[0029] The basic information unit of the control protocol in the control protocol model may include the protocol identifier ID, device type identifier, and control command category (such as configuration, control, and query). The command structure definition unit may include the command frame header, operation code, parameter area structure, and verification field definition. The parameter field mapping rule unit may include the mapping relationship between business parameters and protocol fields, parameter type conversion rules, and parameter value range and default value. The command assembly rule unit may include the field assembly order, fixed and reserved field filling rules, and dynamic field filling rules.

[0030] According to the embodiments of this application, by splitting into independent structural units, complex protocol rules are decomposed into configurable and easy-to-understand modules, avoiding the problems of chaotic and difficult-to-maintain protocol rules in traditional hard coding, and reducing the configuration and management difficulty of protocol description models and control protocol models.

[0031] In one implementation, parsing the first communication data frame based on the first protocol description model to obtain the first UAV defense data may include: The data is parsed field by field, starting from the beginning of the header of the first communication data frame. This field describes the unit for performing byte reading, byte order conversion, and bitwise operation parsing. Through this variable-length and loop structure definition unit, the variable-length field and loop structure in the first communication data frame are recursively or iteratively parsed respectively. According to the verification rules defined by the verification rule definition unit, the first communication data frame is verified to obtain the first UAV defense data.

[0032] In this embodiment, the parsing starting point is determined by the frame header, and the field order is sorted according to the structure defined by the protocol description model. Basic information is extracted for fixed-length fields to resolve differences in underlying device data formats. For fields with dynamic lengths or repetitive structures, all valid data is covered recursively or iteratively to avoid omissions. Invalid data is filtered through validation rules to ensure the accuracy and usability of the final output drone defense data. The process of obtaining the second drone defense data is the same as that of obtaining the first drone defense data.

[0033] According to the embodiments of this application, by field-by-field positioning, byte order conversion, bitwise operation parsing, and recursive or iterative parsing of variable-length fields and loop structures, combined with verification rules, the accurate and complete parsing of complex data frames of various UAV defense devices can be achieved, ensuring the validity of UAV defense data, while supporting the reusability of parsing logic and flexible expansion of devices.

[0034] In one implementation, the generation of control commands for the first drone defense device based on the first control protocol model, the first drone defense data, and the second drone defense data may include: The target status information and equipment status information are extracted from the first UAV defense data and the second UAV defense data respectively. The target status information includes at least one of the number, position, speed and heading of UAVs. The equipment status information includes at least one of the operating status, working parameters and fault alarms of the UAV defense equipment. Based on the target status information and the device status information, trigger control operations on the first UAV defense device; Based on the first control protocol model and the control parameters corresponding to the control operation, control commands for the first UAV defense device are generated.

[0035] In this embodiment, target status information reflects the objective operational status of the UAV target, including the number of UAVs, their location (e.g., latitude, longitude, altitude), speed, heading, and signal characteristics (e.g., frequency band, signal strength), used to determine whether the target needs to be tracked or countered. Device status information reflects the operational status of the UAV defense equipment itself, including device operating status (e.g., powered on, powered off, standby), operating parameters (e.g., radar scanning frequency, optoelectronic device focal length), and fault alarms (e.g., low battery, hardware failure), used to determine whether the device has the conditions to execute control operations. Control operations may include device start / stop, mode switching, and parameter configuration. Control parameters may be specific values ​​or configuration items that support the implementation of control operations, corresponding one-to-one with the control operations.

[0036] The system extracts target and device status information from drone defense data. Based on the drone and device status, it triggers control operations on the drone defense equipment. Using a control protocol model and corresponding control parameters, it generates control commands for the drone defense equipment. For example, when a target location is detected to be outside a safe range, it triggers device start / stop control; when abnormal device status data is detected, it triggers device parameter configuration control.

[0037] According to the embodiments of this application, precise control operations are triggered by integrating target status and device status information of multiple devices, and adaptive instructions are generated based on the target device's dedicated control protocol model, thereby achieving precise and compatible device control driven by multi-source data collaboration.

[0038] In one embodiment, before triggering the control operation on the first UAV defense device based on the target status information and the device status information, the method may further include: Obtain the preset field mapping rules. The field mapping rules are used to define the correspondence between the original fields of the device and the target fields in the unified defense data object model, as well as the data type conversion rules and value range constraints. According to the preset field mapping rules, the target status information is converted into standardized target status information and the device status information is converted into standardized device status information in the unified defense data object model.

[0039] In this embodiment, the original device fields can be the raw data fields directly output by various UAV defense devices after protocol parsing, without format adjustment. Field mapping rules are stored in a structured configuration file, including field name mapping tables, data conversion formulas, and value range constraints. A unified defense data object model is used to unify the defense data format of various UAV defense devices, including a unified target object structure, a unified coordinate system, a unified timestamp format, and a unified device source identifier.

[0040] The system acquires the raw status information output by different UAV defense devices after protocol parsing, and transforms it in the unified defense data object model according to preset field mapping rules to obtain standardized target status information and standardized device status information, which can be used by subsequent target fusion, situation display, alarm judgment or countermeasure decision modules.

[0041] According to the embodiments of this application, by obtaining preset field mapping rules, the standardized conversion of target status information and device status information is completed in the unified defense data object model, so as to realize the unification of the format, type and value of heterogeneous defense data, and provide a consistent and reliable data foundation for subsequent accurate triggering of device control operations.

[0042] In one implementation, generating control commands for the first UAV defense device based on the first control protocol model and the control parameters corresponding to the control operation may include: An empty instruction template is generated based on the instruction structure definition unit; According to the mapping rules of the parameter field mapping rule unit, the control parameter is filled into the corresponding field of the empty instruction template; Integrity verification is performed according to the verification rules of the first control protocol model, and control commands for the first UAV defense device are generated.

[0043] In this embodiment, the empty instruction template is a parameterless instruction frame generated according to the frame structure, field length, and field order preset by the instruction structure definition unit in the control protocol model.

[0044] By defining a unified device-identifiable framework for control commands through instruction structure definition units, the problem of inconsistent instruction structures is solved; by implementing parameter field mapping rules, the conversion of business layer control parameters to device protocol layer parameters is realized, ensuring that the parameters can be accurately parsed by the device; and by completing the calculation and filling of verification values ​​through verification rules, the integrity of the generated control command data is ensured.

[0045] According to the embodiments of this application, the process of generating templates through instruction structures, filling parameters with mapping rules, and completing verification through verification rules enables the accurate conversion of control parameters into device-specific executable control instructions.

[0046] In one implementation, determining the first protocol description model and the first control protocol model in the protocol description model library based on the device identification information of the first unmanned aerial vehicle (UAV) defense device may include: In the protocol description model library, a first mapping relationship between the device identification information and the protocol description model is constructed, and a second mapping relationship between the device identification information and the control protocol model is constructed. The device identification information includes at least one of the following: device type identifier, manufacturer code, device model, access channel identifier, and protocol version number. The first protocol description model is determined by the device identification information of the first drone defense device and the first mapping relationship, and the first control protocol model is determined by the device identification information of the first drone defense device and the second mapping relationship.

[0047] In this embodiment, a unique correspondence between device identification information and protocol description model and control protocol model is constructed in the protocol description model library. When the UAV defense device accesses the platform system and uploads communication data frames, the device identification information is extracted from the device network access information, and the corresponding protocol description model and control protocol model are matched through the first mapping relationship and the second mapping relationship.

[0048] According to the embodiments of this application, by constructing a unique mapping relationship between device identification information and protocol description model and control protocol model, accurate matching of protocol model based on device identification is achieved, ensuring the unique adaptability of parsing rules and control rules for heterogeneous UAV defense equipment.

[0049] In one implementation, after generating the control command for the first unmanned aerial vehicle (UAV) defense device, the method may further include: The control command was sent to the first drone defense device; Determine whether the first drone defense device supports control acknowledgments; If the first UAV defense device supports control acknowledgments, then according to the protocol description model corresponding to the first UAV defense device, the execution result data frame returned by the first UAV defense device is parsed, and a unified format control command response result is returned.

[0050] In this embodiment of the application, the control receipt is response data returned to the platform system by the UAV defense device after receiving and executing the control command issued by the platform system, which includes the command execution status and execution result.

[0051] The system determines whether acknowledgment processing is needed based on the inherent attributes of the device. If the drone defense device supports receiving device acknowledgments, the response data is parsed based on the protocol description model of the same device to confirm the command execution result, and a unified format control command response result is generated and returned. If the drone defense device does not support control acknowledgments, the parsing operation is not performed. The accuracy of acknowledgment parsing is ensured by the protocol description model corresponding to the drone defense device, and the unified format conversion enables the platform system to uniformly manage the command execution results.

[0052] According to the embodiments of this application, a complete control command execution closed loop is formed by sending control commands in a targeted manner, judging the device's acknowledgment capability, parsing the acknowledgment data in a model and standardizing the results, thereby achieving accurate confirmation of the command execution results and improving the system's unified management capability of heterogeneous device control results.

[0053] Figure 2 This is a flowchart illustrating a data receiving method provided in this application.

[0054] In this embodiment, the access device includes a drone detection radar, a radio spectrum detection device, an optoelectronic tracking device, and a countermeasure device.

[0055] The unified access module receives communication data frames from various devices and is compatible with multiple communication protocols (such as TCP, UDP, MQTT, and HTTP).

[0056] Each drone defense device is certified and verified to determine whether the certification is successful. If the certification is successful, the process proceeds to the next data processing stage; if the certification fails, the process ends.

[0057] The protocol parsing engine relies on a protocol description model library. It matches the corresponding protocol model based on the device identifier and performs structured parsing on the original data frames to obtain drone defense data.

[0058] The data standardization module converts the raw data from heterogeneous drone defense equipment into standardized data with a unified format, coordinates, and time system. Target status information includes the number, location, speed, and heading of drones, while equipment status information includes the operating status, working parameters, and fault alarms of the aforementioned drone defense equipment.

[0059] The unified event processing engine, based on standardized data, executes device status alarms, device online reminders, and device offline reminders, enabling unified event identification, alarming, and response.

[0060] The standardized data is then distributed to downstream systems such as the business layer, control layer, and visualization platform.

[0061] According to the embodiments of this application, a data foundation is provided for the collaborative control of the drone defense system through the entire process of multi-source drone defense equipment, from access, parsing, standardization to event processing and data distribution.

[0062] Figure 3 This is a flowchart illustrating a control command issuance method provided in this application.

[0063] In this embodiment, the platform system is a control decision center that generates control commands based on the communication data frames of the multi-source drone defense equipment.

[0064] The control device acts as a relay node for issuing commands, receiving control commands and passing them to the command packaging engine.

[0065] The instruction packaging engine relies on a protocol description model library to encapsulate control instructions into structured instruction frames that can be recognized by the device, based on the control protocol model.

[0066] The instruction state machine in the instruction delivery engine manages the instruction lifecycle (e.g., pending, sent, acknowledged, failed) and tracks the instruction execution status. The receipt parsing and result determination are used to receive the execution receipts returned by the UAV defense equipment, parse them according to the protocol description model, and determine whether the control instruction was executed successfully. The timeout check and retry strategy is used to determine if the UAV defense equipment fails to return a receipt within the specified time, triggering a timeout mechanism and re-issuing the instruction according to a preset strategy (e.g., number of retries, interval).

[0067] The drone detection radar, radio spectrum detection equipment, electro-optical tracking equipment, and countermeasure equipment receive control commands issued by the command delivery engine and execute corresponding operations (such as adjusting radar parameters, starting countermeasure equipment, and tracking electro-optical equipment). If the above-mentioned drone defense equipment supports control feedback, it returns the execution result data frame to the command delivery engine after execution.

[0068] According to the embodiments of this application, the entire process from the platform system issuing instructions to encapsulation according to the device protocol, engine delivery and execution, and then to receipt parsing, enables precise, reliable, and closed-loop control of various drone defense devices.

[0069] In practice, both the protocol description model and the control protocol model are pre-configured sets of structured rules, rather than hard-coded logic. Data parsing and control command generation rely on these pre-configured models, not fixed code logic. Protocol parsing and device control are fully configurable; both data and control protocols are described through models, avoiding hard coding. The uplink data protocol and downlink control protocol of the device are uniformly described through configuration, and a unified parsing and control engine dynamically completes data parsing and control command generation. The control generation and distribution process is entirely driven by the configuration model, eliminating the need to write separate command generation code for different UAV defense devices.

[0070] By using a protocol description model and a control protocol model, the data protocol and control protocol of the UAV defense equipment are decoupled from the program code, enabling unified access, dynamic parsing, and unified control of the UAV defense equipment. This reduces maintenance costs and system complexity, unifies access and control logic, and standardizes the parsing process, which is conducive to the long-term stable operation of the UAV defense system.

[0071] Figure 4 This application provides a schematic diagram of a unified access and command generation system for multiple UAV defense devices. The system may include: The unified access module 410 is used to receive a first communication data frame and a second communication data frame, wherein the first communication data frame is a communication data frame of a first UAV defense device, and the second communication data frame is a communication data frame of a second UAV defense device, and the first UAV defense device and the second UAV defense device are two different types of UAV defense devices. The model matching module 420 is used to determine a first protocol description model and a first control protocol model in the protocol description model library based on the device identification information of the first UAV defense device, and to determine a second protocol description model in the protocol description model library based on the device identification information of the second UAV defense device. The first protocol description model and the first control protocol model are the protocol description model and control protocol model corresponding to the first UAV defense device, and the second protocol description model is the protocol description model corresponding to the second UAV defense device. The first and second protocol description models are used to define the complete structure of the uplink data frames of the first and second UAV defense devices, respectively; the first control protocol model is used to define the generation rules for the downlink control commands of the first UAV defense device. The protocol parsing module 430 is used to parse the first communication data frame based on the first protocol description model to obtain the first UAV defense data, and to parse the second communication data frame based on the second protocol description model to obtain the second UAV defense data; The instruction generation module 440 is used to generate control instructions for the first drone defense device based on the first control protocol model, the first drone defense data, and the second drone defense data.

[0072] In one implementation, the system may further include: The data standardization module is used to obtain preset field mapping rules. The field mapping rules are used to define the correspondence between the original fields of the device and the target fields in the unified defense data object model, the data type conversion rules, and the value range constraints. According to the preset field mapping rules, the drone defense data is converted into standardized drone defense data in the unified defense data object model.

[0073] In one implementation, the unified access module 410 can also be used to send control commands to the target drone defense equipment.

[0074] In practical applications, the unified access module is an access component used to receive data from devices using different communication protocols. Uplink, the unified access module receives raw data from the devices, providing input for the parsing process; downlink, it sends control commands, providing an output channel for the control process.

[0075] Based on the same idea, this application also provides a device corresponding to the above method.

[0076] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 5As shown in the embodiment of this application, a unified access and command generation device 500 for multiple drone defense devices is provided, including a memory 530, a processor 510 and a computer program 520 stored in the memory. The processor 510 executes the computer program 520 to implement the unified access and command generation method for multiple drone defense devices described in any of the above embodiments.

[0077] This application provides a unified access and command generation device for multiple drone defense devices, which may include a memory, a processor, and a computer program stored in the memory. The processor executes the computer program to implement the unified access and command generation method for multiple drone defense devices described in any of the above embodiments.

[0078] It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.

[0079] Obviously, those skilled in the art should understand that the various units or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computing device, or fabricating them separately as individual integrated circuit modules, or fabricating multiple modules or steps into a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0080] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for unified access and command generation for multiple UAV defense equipment, characterized in that, include: Receive a first communication data frame and a second communication data frame, wherein the first communication data frame is a communication data frame of a first drone defense device, and the second communication data frame is a communication data frame of a second drone defense device, and the first drone defense device and the second drone defense device are two different types of drone defense devices; Based on the device identification information of the first UAV defense device, a first protocol description model and a first control protocol model are determined in the protocol description model library. Based on the device identification information of the second UAV defense device, a second protocol description model is determined in the same library. The first protocol description model and the first control protocol model are the protocol description model and control protocol model corresponding to the first UAV defense device, respectively, and the second protocol description model is the protocol description model corresponding to the second UAV defense device. The first protocol description model and the second protocol description model are used to define the complete structure of the uplink data frames of the first UAV defense device and the second UAV defense device, respectively. The first control protocol model is used to define the generation rules for the downlink control commands of the first UAV defense device. First UAV defense data is obtained by parsing the first communication data frame based on the first protocol description model, and second UAV defense data is obtained by parsing the second communication data frame based on the second protocol description model. Based on the first control protocol model, the first UAV defense data, and the second UAV defense data, control commands for the first UAV defense device are generated.

2. The method of claim 1, wherein, The protocol description model includes a field description unit, a variable-length and loop structure definition unit, and a verification rule definition unit; The control protocol model includes an instruction structure definition unit and a parameter field mapping rule unit.

3. The method of claim 2, wherein, The step of parsing the first communication data frame based on the first protocol description model to obtain the first UAV defense data includes: Parse field by field, starting from the beginning of the header of the first communication data frame; The field description unit performs byte reading, byte order conversion, and bitwise operation parsing operations. The variable-length and loop structure definition unit is used to recursively or iteratively parse the variable-length field and loop structure in the first communication data frame, respectively. According to the verification rules defined by the verification rule definition unit, the first communication data frame is verified to obtain the first UAV defense data.

4. The method of claim 2, wherein, The step of generating control commands for the first drone defense device based on the first control protocol model, the first drone defense data, and the second drone defense data includes: Target status information and device status information are extracted from the first UAV defense data and the second UAV defense data respectively. The target status information includes at least one of the number, location, speed and heading of UAVs. The device status information includes at least one of the operating status, working parameters and fault alarms of the UAV defense device. Based on the target status information and the device status information, a control operation on the first UAV defense device is triggered. Based on the first control protocol model and the control parameters corresponding to the control operation, control commands for the first UAV defense device are generated.

5. The method according to claim 4, characterized in that, Before triggering control operations on the first UAV defense device based on the target status information and the device status information, the method further includes: Obtain the preset field mapping rules. The field mapping rules are used to define the correspondence between the original fields of the device and the target fields in the unified defense data object model, as well as the data type conversion rules and value range constraints. According to the preset field mapping rules, the target status information is converted into standardized target status information and the device status information is converted into standardized device status information in the unified defense data object model.

6. The method according to claim 4, characterized in that, The step of generating control commands for the first UAV defense device based on the first control protocol model and the control parameters corresponding to the control operation includes: An empty instruction template is generated based on the instruction structure definition unit; According to the mapping rules of the parameter field mapping rule unit, the control parameters are filled into the corresponding fields of the empty instruction template; Integrity verification is performed according to the verification rules of the first control protocol model, and control commands for the first UAV defense device are generated.

7. The method according to claim 1, characterized in that, The step of determining the first protocol description model and the first control protocol model in the protocol description model library based on the device identification information of the first UAV defense device includes: In the protocol description model library, a first mapping relationship between the device identification information and the protocol description model, and a second mapping relationship between the device identification information and the control protocol model are constructed, wherein the device identification information includes at least one of device type identifier, manufacturer code, device model, access channel identifier, and protocol version number; The first protocol description model is determined by the device identification information of the first UAV defense device and the first mapping relationship, and the first control protocol model is determined by the device identification information of the first UAV defense device and the second mapping relationship.

8. The method according to claim 1, characterized in that, After generating the control commands for the first drone defense device, the method further includes: The control command is sent to the first UAV defense device; Determine whether the first UAV defense device supports control receipts; If the first UAV defense device supports control receipts, then according to the first protocol description model, the execution result data frame returned by the first UAV defense device is parsed, and a unified format control command response result is returned.

9. A unified access and command generation system for multiple unmanned aerial vehicle (UAV) defense devices, characterized in that, include: A unified access module is used to receive a first communication data frame and a second communication data frame, wherein the first communication data frame is a communication data frame of a first UAV defense device, and the second communication data frame is a communication data frame of a second UAV defense device, and the first UAV defense device and the second UAV defense device are two different types of UAV defense devices; The model matching module is used to determine a first protocol description model and a first control protocol model in the protocol description model library based on the device identification information of the first UAV defense device, and to determine a second protocol description model in the protocol description model library based on the device identification information of the second UAV defense device. The first protocol description model and the first control protocol model are the protocol description model and control protocol model corresponding to the first UAV defense device, and the second protocol description model is the protocol description model corresponding to the second UAV defense device. The first protocol description model and the second protocol description model are respectively used to define the complete structure of the uplink data frames of the first UAV defense device and the second UAV defense device; the first control protocol model is used to define the generation rules of the downlink control commands of the first UAV defense device. The protocol parsing module is used to parse the first communication data frame based on the first protocol description model to obtain the first UAV defense data, and to parse the second communication data frame based on the second protocol description model to obtain the second UAV defense data; The instruction generation module is used to generate control instructions for the first drone defense device based on the first control protocol model, the first drone defense data, and the second drone defense data.

10. An electronic device, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-8.

Images