CN112187717B - Rescue scene-based data link message processing method - Google Patents

Rescue scene-based data link message processing method Download PDF

Info

Publication number
CN112187717B
CN112187717B CN202010874451.3A CN202010874451A CN112187717B CN 112187717 B CN112187717 B CN 112187717B CN 202010874451 A CN202010874451 A CN 202010874451A CN 112187717 B CN112187717 B CN 112187717B
Authority
CN
China
Prior art keywords
message
messages
word
information
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010874451.3A
Other languages
Chinese (zh)
Other versions
CN112187717A (en
Inventor
张周
桑玮
王彤彤
许左宏
谢佳
闫野
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tianjin (binhai) Intelligence Military-Civil Integration Innovation Center
National Defense Technology Innovation Institute PLA Academy of Military Science
Original Assignee
Tianjin (binhai) Intelligence Military-Civil Integration Innovation Center
National Defense Technology Innovation Institute PLA Academy of Military Science
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tianjin (binhai) Intelligence Military-Civil Integration Innovation Center, National Defense Technology Innovation Institute PLA Academy of Military Science filed Critical Tianjin (binhai) Intelligence Military-Civil Integration Innovation Center
Priority to CN202010874451.3A priority Critical patent/CN112187717B/en
Publication of CN112187717A publication Critical patent/CN112187717A/en
Application granted granted Critical
Publication of CN112187717B publication Critical patent/CN112187717B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/06Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

The invention discloses a data chain message processing device and method based on a rescue scene. The device comprises a plurality of node devices connected through a LAN, wherein each node device respectively adopts a PCB (printed Circuit Board), and a basic unit required by a data link system is integrated in the PCB. The method comprises the following steps: classifying the messages to be transmitted in the rescue scene based on the analysis of the cooperative fighting process among the nodes in the rescue scene; formulating a standard format of the message; setting a message database structure, storing message contents into a database to form a data element dictionary; visually describing the message by adopting XML: all nodes and links form a network together, and each node encodes or decodes information received from the network or information to be transmitted; and each execution node completes tasks in cooperation with other execution nodes in the network according to the issued instruction. The invention realizes the information sharing and communication of the multi-party nodes, enlarges the perception of battlefield situation and improves the cooperative fighting capability of the system.

Description

Rescue scene-based data link message processing method
Technical Field
The invention relates to a message processing technology in the field of communication, in particular to a rescue scene-based data link message processing device and method.
Background
With the continuous development of science and technology and the increasingly complex application environment, the data link is used as the key for realizing interconnection of weapon platforms, situation information sharing, collaborative accurate striking and automation of battle command, the status in the military and civil collaborative work becomes more and more important, the data link message is the soul of running through the data link, and the efficiency of data link message processing directly influences the performance and efficiency of the whole data link system. And the formatted message standard is one of three basic elements of a data chain, the standardization process of the formatted message standard is an important guarantee of interoperability of the data chain, and the establishment of the formatted message standard is decisive for realizing autonomous collection, processing, transmission and exchange of real-time information and enhancing situation awareness.
Since the beginning of the 60 s of the last century, various data Link systems such as Link4A, Link11, Link11B, Link16 and Link22 have been developed in the countries in the north, and various message standards such as M series, J series and F series have been established. (1) The M-series messages are composed of data messages for transmitting targets, situational information and command commands, and control messages for network calibration and management, each message directly containing multiple data elements. The length of an M series message in Link11 is 60bits, one message comprises two 30-bit frames, each frame is 30bits long and comprises an information bit and an error detection code, wherein the information bit occupies 24bits, and the error detection code occupies 6 bits. The length of the M series message in Link11B is 72bits, wherein the initial group occupies 9bits, the data group occupies 6 x 9bits, and the check group occupies 9 bits. (2) The J series messages are composed of tactical messages, RTT messages and free text messages, the tactical messages are used for realizing transmission and exchange of tactical messages, the RTT messages are used for synchronous timing of a network, and the free text messages are used for array transmission of text messages and voice messages. The J series message consists of a plurality of message words, including an initial word, an extended word and a continuation word, each message word being 75bits in length, the data bits occupying 70bits, and the parity bits occupying 5 bits. (3) The F series messages consist of 1-8 message words, and the message words have three different message coding formats: f0m.n-p, Fm-p, and Fm, each message word length being 72 bits. For the F0m.n-p message format, the indicator occupies 4bits, the series identifier occupies 5bits, and the information field occupies 61 bits. For the Fm-p message format, the indicator takes 4bits, the word size takes 1bit, and the information field takes 67 bits. For the Fm message format, the series indicator takes 1bit, the marker indicator takes 3bits, and the information field takes 68 bits.
Throughout the development process of the domestic data chain, the research on the data chain information in China starts late, most of resources of the domestic data chain information come from foreign partial decrypted documents, the content is loose, systematic research is lacked, the development of the domestic data chain is still in the primary stage, the data chain information processing technology is not mature, only individual military-specific data chains are put into use, the data chain with wide application, stable performance and good compatibility is not developed successfully on the whole, and the research and development of the domestic data chain information technology is slow.
In foreign countries, army in the north bound countries has studied data links for many years, but early data links have single purposes, for example, V/R sequence messages of Link4A are mainly used for automatic control of airplanes, Link11 is mainly used for exchanging electronic warfare data and flight paths between mobile units and transmitting commands, warnings and instruction information, so that the range of covered functional domains is small, the types of messages are few and independent, and the problem of gradually diversified application requirements is difficult to meet. The data chains such as Link16 and Link22 are in line with the development of the era, cover various battle requirements of sea, land, air and sky, have more message types and relatively complete functions, but are difficult to put into practical application because the technical contents are not disclosed to the outside and have opacity and complexity.
Disclosure of Invention
The invention aims to provide a data chain message processing device and method based on a rescue scene, so that information sharing and communication of multiple nodes are realized, the perception of battlefield situation is expanded, and the cooperative combat capability of a system is improved.
The technical solution for realizing the purpose of the invention is as follows: a data link message processing device based on a rescue scene comprises a plurality of node devices connected through a LAN, each node device adopts a PCB (printed Circuit Board) respectively, a basic unit required by a data link system is integrated in the PCB, and the basic unit comprises a signal transceiving unit, a decoding unit, a storage unit, a control unit and a communication protocol.
Further, the rescue scene is composed of 50 nodes, the nodes are divided into a command platform, an unmanned aerial vehicle, an unmanned vehicle and rescuers, the nodes corresponding to the command platform are command nodes, the nodes corresponding to the unmanned aerial vehicle, the unmanned aerial vehicle and the rescuers are execution nodes, and rescue goods and materials are reserved in each execution node and are used for rescuing when a rescue target is searched; each node corresponds to a node device.
Further, the command nodes issue command messages to the execution nodes according to task needs, each execution node cooperatively executes the task according to requirements after receiving the command messages, and sends self states and self monitoring information to the command nodes to wait for decision at regular time or directly to other execution nodes, and the other execution nodes perform route obstacle avoidance or cooperative rescue according to target types after receiving the command messages.
A rescue scene-based data chain message processing method comprises the following steps:
step 1, classifying messages needing to be transmitted in a rescue scene based on analysis of a collaborative combat process among nodes in the rescue scene;
step 2, formulating a standard format of the message;
step 3, setting a message database structure, storing the message content in a database to form a data element dictionary;
and 4, visually describing the message by adopting XML:
step 5, all nodes and links form a network together, and each node encodes or decodes information received from the network or information to be sent;
and 6, each execution node cooperates with other execution nodes in the network to complete tasks according to the instructions issued by the command nodes.
Further, in step 1, based on the analysis of the collaborative combat process among the nodes in the rescue scene, the messages to be transmitted in the rescue scene are classified into the following five categories:
(1) aerial platform positioning and system state class messages
The aerial platform comprises an unmanned aerial vehicle; the information is used for reporting the participation state, the identity recognition, the geographic position, the motion state and the positioning navigation content of the air platform network on one hand, and is used for reporting the current state of the air platform on the other hand, each air platform periodically sends the current state information, so that the control center masters the node dynamics and issues a corresponding command;
(2) ground platform positioning and system status type messages
The ground platform comprises an unmanned vehicle and rescue workers; the information reports the platform geographic position, the motion state and the relative navigation information of the unmanned vehicle and the rescue workers on one hand, and reports the current states of the unmanned vehicle and the rescue workers including load, electric quantity, working state, platform system state and medicine allowance on the other hand; each ground platform also needs to periodically send current state information, but the sending period is longer than that of the air platform;
(3) formation of teamed homogeneous messages
The message comprises a command node for distributing tasks in a team and providing target information for the aerial unmanned aerial vehicle; the command platform also receives the command, plans the multilateral flight path information of different unmanned aerial vehicles in the formation and interacts the command with the unmanned aerial vehicles;
(4) monitoring class messages
The messages comprise monitoring messages of special areas or fixed points and tracks, and also comprise track management messages, data updating request messages, pointer messages and filter management messages;
(5) command control type messages
The messages refer to control and cooperative commands issued by the command nodes to the execution nodes, or state information of battles, control right of the platform, pairing messages and track management messages, and are used for leading the situation of a battlefield.
Further, step 2, formulating a standard format of the message, specifically as follows:
the formulated message is named as Q message, the naming format of the Q message is Qn.m, wherein n represents a message identifier, the number is 0-31, 32 numbers are provided in total, m represents a message sub-identifier, the number is 0-7, eight numbers are provided in total, and 256 messages can be formed in total; each message defines three word formats: an initial word, an extended word and a continuation word, each word containing 72 bits;
the initial word structure is shown in table 1, with words labeled "00", with and without one initial word per message, and must start with the initial word:
TABLE 1
Character mark Message identification Message sub-identity Message length Information segment Error detection section
The extension word is shown in table 2, and its word is labeled "10", when the data length of the message that the node needs to send exceeds the payload of the initial word, the extension word is added to extend the message, each message has at most one extension word, and the extension word can only be sent after the initial word:
TABLE 2
Character mark Information segment Error detection section
As shown in table 3, the continuation word is labeled "01" and is a supplement to information based on the initial word and the extended word, each message can contain 0 to a plurality of extended words, but one message contains 8 words at most, each time the message is sent, a part of the extended words can be selected to be sent, and the sending sequence of the extended words is arbitrary:
TABLE 3
Character mark Continuation word mark Information segment Error detection section
Further, the step 3 of setting a message database structure, storing the message content in the database to form a data element dictionary, specifically:
the established message standard architecture is divided into five layers, namely a function group, a message category, a message word, a DFI and a DUI, wherein a data field identifier DFI represents a data element of each word, and a data use identifier DUI is a data item corresponding to the data element; each function group comprises a plurality of messages, each message consists of one to a plurality of words, and each word consists of DFI and DUI items; and storing the DFI and the DUI into a database to form a data element dictionary library, and forming a complete message by combining the DFI and the DUI.
Further, in step 4, the message is visually described by using XML, which specifically includes the following steps:
each node receives messages sent by other node devices from the network, converts binary code stream messages into visual XML files through JAVA language, and analyzes the messages according to the mapping relation in the database; when the information is transmitted to other node devices, the information to be transmitted is visually described by using an XML file, and the file is converted into a binary code stream by using a JAVA language and is transmitted into a network.
Further, each node encodes or decodes information received from within the network or information to be transmitted, step 5, wherein:
the message encoding process is as follows:
(1.1) loading a structured file, acquiring a message identifier (MessageID) and a Version number Version from a file header, and determining a corresponding template configuration file according to the message identifier and the Version number;
(1.2) loading a corresponding Q message configuration XML template from a template configuration file library, acquiring the number ElementCnt of message body elements and Reserve field, and splicing the message identifier, the version number, the number of the message body elements and the Reserve field into a message header of the Q message in sequence according to the definition of the Q message header;
(1.3) sequentially acquiring element configuration information in an XML template according to an XML template configured by Q messages and SN serial numbers, searching a corresponding attribute identifier ZBS and an attribute name, namely a word identifier, from a data element dictionary library according to the DFI and DUI serial numbers for the element with the SN being 1, searching the value of the element in the structured data according to the path/Message/Body/ZBS according to the attribute identifier, converting the value into a Bit value, supplementing the Bit value according to the length information in the XML template, completing the coding of the Message element, and splicing the coded Bit value to a Message Body;
(1.4) coding the elements in sequence according to the sequence of the SN to complete the splicing of the Q message body;
(1.5) splicing the Q message header and the Q message body into a complete Q message for outputting, and finishing coding;
the message decoding process is as follows:
(2.1) intercepting a Message header of the Q Message according to bits, namely the first 24Bit bits, analyzing a Message identifier and a Version number of the Q Message according to the bits, respectively outputting the Message identifier and the Version number to corresponding nodes/Message/Head/Message ID and/Message/Head/Version in the structured data, and determining a configuration XML template of the Q Message according to the Message identifier and the Version number;
(2.2) loading the determined Q Message configuration XML template, acquiring the element quantity ElementCnt of the Message Body, sequentially acquiring element configuration information in the XML template according to the SN serial number according to the XML template configured by the Q Message, searching a corresponding attribute identifier ZBS and an attribute name, namely a word identifier, in an element data dictionary library according to DFI/DUI for the element with the SN of 1, intercepting the offset length Bit value of the Message Body according to length, converting the Bit value into the value of structured data, and outputting the value to a corresponding node/Message/Body/QZGZBS in the structured data;
(2.3) decoding corresponding elements according to the SN sequence number sequence and outputting the elements to corresponding nodes in the structured data;
and (2.4) outputting the structured data as a whole, and finishing decoding.
Compared with the prior art, the invention has the following remarkable advantages: (1) the rescue scene based on the method is more practical due to the fact that the rescue scene is close to public service, a set of complete message processing technology is designed for information intercommunication among all nodes in the scene, the message processing technology has good performance aiming at the rescue scene, and the real-time performance and uncertainty of the scene deduction are fully considered; (2) original data such as a state of a party, cooperative control, a command, network management signaling, a sensor and the like related in a scene are regularly formatted to realize information sharing and communication of multiple nodes, so that the perception of battlefield situation is enlarged, the transparency of the scene to the party is enhanced, and the system cooperative combat capability of task allocation, traversal reconnaissance, rescue development and the like is improved; (3) the message processing technology is implanted into the board card, the implementation is simple, the cost is low, and the method can be widely applied to the research of other similar scenes.
Drawings
Fig. 1 is a schematic structural diagram of a data chain message processing device based on a rescue scenario.
Fig. 2 is a schematic diagram of a message standard architecture.
Fig. 3 is a schematic diagram of an XML template for associating initial words of a message.
Fig. 4 is a schematic diagram of XML description of the initial word of the association message.
Fig. 5 is a schematic diagram of message encoding.
Fig. 6 is a schematic diagram of message decoding.
Detailed Description
Because disasters frequently occur due to severe climate environments in recent years, and rescue work is difficult to rapidly and accurately carry out after disasters in emergency rescue, particularly in remote areas, due to communication interference, the message processing considered by the invention is applied to the emergency rescue scene of the remote special areas far away from cities, and aims to establish a set of flexible and normative message processing flow and realize various functions such as real-time situation sharing, accurate command control, efficient task cooperation and the like of information among nodes in a network.
The invention relates to a rescue scene-based data link message processing device which comprises a plurality of node devices connected through a LAN (local area network), wherein each node device adopts a PCB (printed circuit board) respectively, a basic unit required by a data link system is integrated in the PCB, and the basic unit comprises a signal transceiving unit, a decoding unit, a storage unit, a control unit and a communication protocol.
Further, the rescue scene is composed of 50 nodes, the nodes are divided into a command platform, an unmanned aerial vehicle, an unmanned vehicle and rescuers, the nodes corresponding to the command platform are command nodes, the nodes corresponding to the unmanned aerial vehicle, the unmanned aerial vehicle and the rescuers are execution nodes, and rescue goods and materials are reserved in each execution node and are used for rescuing when a rescue target is searched; each node corresponds to a node device.
Further, the command nodes issue command messages to the execution nodes according to task needs, each execution node cooperatively executes the task according to requirements after receiving the command messages, and sends self states and self monitoring information to the command nodes to wait for decision at regular time or directly to other execution nodes, and the other execution nodes perform route obstacle avoidance or cooperative rescue according to target types after receiving the command messages.
A rescue scene-based data chain message processing method comprises the following steps:
step 1, classifying messages needing to be transmitted in a rescue scene based on analysis of a collaborative combat process among nodes in the rescue scene;
step 2, formulating a standard format of the message;
step 3, setting a message database structure, storing the message content in a database to form a data element dictionary;
and 4, visually describing the message by adopting XML:
step 5, all nodes and links form a network together, and each node encodes or decodes information received from the network or information to be sent;
and 6, each execution node cooperates with other execution nodes in the network to complete tasks according to the instructions issued by the command nodes.
Further, in step 1, based on the analysis of the collaborative combat process among the nodes in the rescue scene, the messages to be transmitted in the rescue scene are classified into the following five categories:
(1) aerial platform positioning and system state class messages
The aerial platform comprises an unmanned aerial vehicle; the information is used for reporting the participation state, the identity recognition, the geographic position, the motion state and the positioning navigation content of the air platform network on one hand, and is used for reporting the current state of the air platform on the other hand, each air platform periodically sends the current state information, so that the control center masters the node dynamics and issues a corresponding command;
(2) ground platform positioning and system status type messages
The ground platform comprises an unmanned vehicle and rescue workers; the information reports the platform geographic position, the motion state and the relative navigation information of the unmanned vehicle and the rescue workers on one hand, and reports the current states of the unmanned vehicle and the rescue workers including load, electric quantity, working state, platform system state and medicine allowance on the other hand; each ground platform also needs to periodically send current state information, but the sending period is longer than that of the air platform;
(3) formation of teamed homogeneous messages
The message comprises a command node for distributing tasks in a team and providing target information for the aerial unmanned aerial vehicle; the command platform also receives the command, plans the multilateral flight path information of different unmanned aerial vehicles in the formation and interacts the command with the unmanned aerial vehicles;
(4) monitoring class messages
The messages comprise monitoring messages of special areas or fixed points and tracks, and also comprise track management messages, data updating request messages, pointer messages and filter management messages;
(5) command control type messages
The messages refer to control and cooperative commands issued by the command nodes to the execution nodes, or state information of battles, control right of the platform, pairing messages and track management messages, and are used for leading the situation of a battlefield.
Further, step 2, formulating a standard format of the message, specifically as follows:
the formulated message is named as Q message, the naming format of the Q message is Qn.m, wherein n represents a message identifier, the number is 0-31, 32 numbers are provided in total, m represents a message sub-identifier, the number is 0-7, eight numbers are provided in total, and 256 messages can be formed in total; each message defines three word formats: an initial word, an extended word and a continuation word, each word containing 72 bits;
the initial word structure is shown in table 1, with words labeled "00", with and without one initial word per message, and must start with the initial word:
TABLE 1
Character mark Message identification Message sub-identity Message length Information segment Error detection section
The extension word is shown in table 2, and its word is labeled "10", when the data length of the message that the node needs to send exceeds the payload of the initial word, the extension word is added to extend the message, each message has at most one extension word, and the extension word can only be sent after the initial word:
TABLE 2
Character mark Information segment Error detection section
As shown in table 3, the continuation word is labeled "01" and is a supplement to information based on the initial word and the extended word, each message can contain 0 to a plurality of extended words, but one message contains 8 words at most, each time the message is sent, a part of the extended words can be selected to be sent, and the sending sequence of the extended words is arbitrary:
TABLE 3
Character mark Continuation word mark Information segment Error detection section
Further, the step 3 of setting a message database structure, storing the message content in the database to form a data element dictionary, specifically:
the established message standard architecture is divided into five layers, namely a function group, a message category, a message word, a DFI and a DUI, wherein a data field identifier DFI represents a data element of each word, and a data use identifier DUI is a data item corresponding to the data element; each function group comprises a plurality of messages, each message consists of one to a plurality of words, and each word consists of DFI and DUI items; and storing the DFI and the DUI into a database to form a data element dictionary library, and forming a complete message by combining the DFI and the DUI.
Further, in step 4, the message is visually described by using XML, which specifically includes the following steps:
each node receives messages sent by other node devices from the network, converts binary code stream messages into visual XML files through JAVA language, and analyzes the messages according to the mapping relation in the database; when the information is transmitted to other node devices, the information to be transmitted is visually described by using an XML file, and the file is converted into a binary code stream by using a JAVA language and is transmitted into a network.
Further, each node encodes or decodes information received from within the network or information to be transmitted, step 5, wherein:
the message encoding process is as follows:
(1.1) loading a structured file, acquiring a message identifier (MessageID) and a Version number Version from a file header, and determining a corresponding template configuration file according to the message identifier and the Version number;
(1.2) loading a corresponding Q message configuration XML template from a template configuration file library, acquiring the number ElementCnt of message body elements and Reserve field, and splicing the message identifier, the version number, the number of the message body elements and the Reserve field into a message header of the Q message in sequence according to the definition of the Q message header;
(1.3) sequentially acquiring element configuration information in an XML template according to an XML template configured by Q messages and SN serial numbers, searching a corresponding attribute identifier ZBS and an attribute name, namely a word identifier, from a data element dictionary library according to the DFI and DUI serial numbers for the element with the SN being 1, searching the value of the element in the structured data according to the path/Message/Body/ZBS according to the attribute identifier, converting the value into a Bit value, supplementing the Bit value according to the length information in the XML template, completing the coding of the Message element, and splicing the coded Bit value to a Message Body;
(1.4) coding the elements in sequence according to the sequence of the SN to complete the splicing of the Q message body;
(1.5) splicing the Q message header and the Q message body into a complete Q message for outputting, and finishing coding;
the message decoding process is as follows:
(2.1) intercepting a Message header of the Q Message according to bits, namely the first 24Bit bits, analyzing a Message identifier and a Version number of the Q Message according to the bits, respectively outputting the Message identifier and the Version number to corresponding nodes/Message/Head/Message ID and/Message/Head/Version in the structured data, and determining a configuration XML template of the Q Message according to the Message identifier and the Version number;
(2.2) loading the determined Q Message configuration XML template, acquiring the element quantity ElementCnt of the Message Body, sequentially acquiring element configuration information in the XML template according to the SN serial number according to the XML template configured by the Q Message, searching a corresponding attribute identifier ZBS and an attribute name, namely a word identifier, in an element data dictionary library according to DFI/DUI for the element with the SN of 1, intercepting the offset length Bit value of the Message Body according to length, converting the Bit value into the value of structured data, and outputting the value to a corresponding node/Message/Body/QZGZBS in the structured data;
(2.3) decoding corresponding elements according to the SN sequence number sequence and outputting the elements to corresponding nodes in the structured data;
and (2.4) outputting the structured data as a whole, and finishing decoding.
The invention is described in further detail below with reference to the figures and the embodiments.
Examples
As shown in fig. 1, the functions of the nodes such as the unmanned aerial vehicle and the unmanned vehicle in this embodiment are implemented by using customized PCB boards, and the boards are integrated with basic units required by a data link system. The network scene provided by the embodiment comprises 50 nodes, wherein the nodes are divided into a command platform, an unmanned aerial vehicle, an unmanned vehicle and rescue workers, the nodes corresponding to the command platform are command nodes, the nodes corresponding to the unmanned aerial vehicle, the unmanned aerial vehicle and the rescue workers are execution nodes, and rescue goods and materials are reserved in each execution node and are used for rescuing when a rescue target is searched; each node corresponds to a node device.
The command nodes issue command messages to the execution nodes according to task needs, each execution node cooperatively executes the task according to requirements after receiving the command messages, and regularly sends self states and self monitoring information to the command nodes to wait for decision or directly sends the self states and the self monitoring information to other execution nodes, and the other execution nodes perform route obstacle avoidance or cooperative rescue according to target types after receiving the self states and the self monitoring information. For example, when the unmanned aerial vehicle finds a target to be rescued or a dangerous object or an area at high altitude, the unmanned aerial vehicle needs to report information to wait for a decision or directly sends the information to the nodes in the group to notify the decision, and after receiving the information, other nodes perform route obstacle avoidance or cooperative rescue according to the type of the target.
According to the analysis of the rescue scene, the required message content is specifically compiled by taking functions as categories, then the message standard format is formulated, the message database structure is reasonably designed, the message content is efficiently and orderly stored to form the data element dictionary, and the content can be rapidly and effectively obtained from the database when the message is transmitted conveniently. Then, in actual work, each node receives messages sent by other node devices from the network, converts the binary code stream messages into visual XML files through JAVA language, and extracts the information content transmitted in the visual XML files; when the information is transmitted to other node devices, the information to be transmitted is visually described by using an XML file, and the file is converted into a binary code stream by using a JAVA language and is transmitted into a network. The detailed steps of this example are as follows:
step 1: and (4) classifying the messages. Based on the analysis of the cooperative combat process among the nodes in the rescue scene, the messages related to the scene are divided into the following five types:
(1) air platform (drone) positioning and system status class messages. The method is used for reporting the participation state, the identification, the geographic position, the motion state and the positioning navigation content of the unmanned aerial vehicle platform network on one hand, and reporting the current state of the aerial platform, such as the electric quantity, the working state, the loading state, the medicine allowance and the like on the other hand. Each platform of the message must be periodically sent, so that the control center can master the node dynamics in time, and the reasonable command is favorably issued.
(2) Ground platform (unmanned vehicle and fighter) location and system status type messages. The platform geographic position, the motion state and the relative navigation information of the unmanned vehicle and the fighter are reported on one hand, and the current states of the unmanned vehicle and the fighter, including load, electric quantity, working state, platform system state, medicine allowance and the like, are reported on the other hand. This type of message also requires periodic transmissions per platform, but the transmission period may be longer than for over-the-air platforms.
(3) And forming the collaborative type message. The message content comprises that a command platform distributes tasks (detection, verification, rescue targets and the like) in a formation inside a command platform and distributes the tasks in the formation inside the formation, and provides target information for other unmanned aerial vehicles in the air, and also comprises that a command machine receives commands, plans the multilateral flight path information of different unmanned aerial vehicles in the formation, interacts the commands with the unmanned aerial vehicles, and simultaneously also comprises that the command platform sends actions (such as accurate launching, hovering detection, landing and the like of a control platform) needing accurate control and positioning information of the tasks to a controlled platform.
(4) The class messages are monitored. The message comprises monitoring messages of a special area or a fixed point and a flight path, is used for describing the situation of a sensitive area in detail for tactical planning, also comprises flight path management messages, data updating request messages and pointer messages, filter management messages and the like, and the monitoring contents are classified in detail for more efficient utilization.
(5) Command control class messages. The message is used for leading the situation of a battlefield by one party issuing control and cooperative commands or state information of engagement, control right of a platform, pairing message, track management message and the like.
Step 2: and establishing a message standard format. The message formulated in this embodiment is named as a Q message, the naming format of the Q message is qn.m, where n represents a message identifier, the number is 0-31, there are 32 numbers, m represents a message sub-identifier, the number is 0-7, there are eight numbers, and 256 messages can be formed. Each message defines three word formats: an initial word, a prolonged word and a continuation word, each word containing 72 bits.
The initial word structure is shown in table 1, with the word labeled "00", each message has one and only one initial word and must start with the initial word.
TABLE 1
Character mark Message identification Message sub-identity Message length Information segment Error detection section
The extension word is shown in table 2, and its word is marked as "10", when the data length of the message that the node needs to send exceeds the payload of the initial word, the extension word is added to extend the message, each message has at most one extension word, and the extension word can only be sent after the initial word.
TABLE 2
Character mark Information segment Error detection section
The continuation word, whose word designation is "01", is shown in table 3, and is a supplement to the information on the basis of the initial word and the extended word. Each message may contain 0 to a plurality of extension words, but a message contains at most 8 words, and each time a message is sent, a part of the extension words may be selected for sending, and the sending sequence of the extension words is arbitrary.
TABLE 3
Character mark Continuation word mark Information segment Error detection section
And step 3: and reasonably storing the formulated message into a database. As shown in fig. 2, a schematic diagram of a message standard architecture formulated for this embodiment is shown. The method is divided into five layers of function groups, message categories, message words, DFIs and DUIs, wherein the DFIs (data field identifiers) represent data elements of each word, and the DUIs (data use identifiers) are corresponding data items of the data elements. Each function group contains a plurality of messages, each message consisting of one to a plurality of words, each word in turn consisting of DFI and DUI entries. The hierarchical structure makes the whole message system more clear and the relationship between each part is clear. The embodiment stores the DFI and the DUI into the database to form a data element dictionary library, and forms a complete message by combining the DFI and the DUI.
And 4, step 4: and visually describing the message. Because XML is a meta-markup language, it is relatively suitable for describing formatted data, and has a strong extension function and good readability, the present embodiment uses XML to visually describe messages.
Taking the initial word of the associated message in the monitoring class message as an example, the XML template is shown in fig. 3. Each word comprises a file header and a file body, wherein the file header is formed by bits with fixed length, and the file body is formed by splicing one or more data elements according to a fixed sequence. The MessageID in the file header represents the message identifier, Version represents the Version number, ElementCnt represents the number of elements in the file body, and Reserve makes a reserved bit. In addition to each element needs to show its own bit number and DFI and DUI numbers, which is convenient for searching in a database when performing subsequent encoding and decoding, isRaw shows whether the element is a combination type, taking the element with "SN ═ 5" in fig. 2 as an example, the attribute name of the element is longitude, and the element is represented by a combination of east-west longitude identifiers and degrees of longitude. Such template files belong to the configuration files and are stored in a configuration file library.
The XML description file corresponding to the template is shown in fig. 4, the values of the header file of the XML description file are the same as those of the template header file, the data elements in the XML description file are the attribute names corresponding to the DFI/DUI in the template file body, and the values are the information to be transmitted.
And 5: information received or to be transmitted from within the network is coded and decoded. Specifically, the binary code streams transmitted in the network are all binary code streams, so that the received binary code streams need to be converted into XML files for content reading, and meanwhile, the information content needing to be transmitted is combined into XML files and then converted into binary code streams for transmission.
As shown in fig. 5, the message encoding process is as follows:
(1) loading the structured file shown in fig. 4, acquiring a message identifier (MessageID) and a Version number (Version) from a file header, and determining a corresponding template configuration file according to the message identifier and the Version number;
(2) loading a corresponding Q message configuration XML template from a template configuration file library, acquiring the number (ElementCnt) of message body elements and a reserved field (Reserve), and sequentially splicing a message identifier, a version number, the number of the message body elements and the reserved field into a message header of the Q message according to the definition of the Q message header;
(3) according to the XML template configured by the Q Message, sequentially obtaining element configuration information in the XML template according to (SN) sequence numbers, taking fig. 5 as an example, for an element with "SN ═ 1", searching a corresponding attribute identifier (ZBS) and attribute name (word identifier) in a data element dictionary library according to the DFI and the DUI sequence numbers, searching a value of the element in the structured data according to a path (/ Message/Body/ZBS) according to the attribute identifier, converting the value into a Bit value, performing Bit padding (generally, 0 padding before) on the Bit value according to length information in the XML template, completing coding of the Message element, and splicing the coded Bit value to a Message Body;
(4) sequentially coding the elements according to the sequence of the SN to complete the splicing of the Q message body;
(5) and splicing the Q message header and the Q message body into a complete Q message for outputting, and finishing the encoding.
As shown in fig. 6, the message decoding process is as follows:
(1) intercepting a Message header of the Q Message according to bits (the first 24Bit bits), analyzing a Message identifier and a Version number of the Q Message according to the bits, respectively outputting the Message identifier and the Version number to corresponding nodes (/ Message/Head/Message ID and/Message/Head/Version) in the structured data, and determining a configuration XML template of the Q Message according to the Message identifier and the Version number;
(2) loading the Q Message configuration XML template determined in the first step, acquiring the element quantity (Elementcnt Cnt) of a Message Body, sequentially acquiring element configuration information in the XML template according to the (SN) sequence number according to the XML template configured by the Q Message, taking the example of FIG. 6, searching a corresponding attribute identifier (ZBS) and an attribute name (word identifier) in an element data dictionary library according to the DFI/DUI of the element with the SN of 1, intercepting the offset length Bit value of the Message Body according to the length h, converting the Bit value into the value of structured data, and outputting the value to a corresponding node (/ Message/Body/QZGZZBS) in the structured data;
(3) decoding corresponding elements according to the SN sequence number sequence and outputting the elements to corresponding nodes in the structured data;
(4) and outputting the structured data as a whole, and finishing decoding.
Step 6: and completing tasks in cooperation with other nodes in the network according to the instructions given by the command nodes.
According to the embodiment, based on a remote special area rescue scene, a set of complete and definite message processing flow is designed and applied to an actual board card, and the problem of information intercommunication of all nodes in the scene is reasonably and effectively solved. The process improves the flexibility of the message processing process, gives consideration to various messages to be used in the special rescue scene, has easy maintainability and easy expandability, can be subsequently derived to other scenes, and has strong applicability.
In the embodiment, a VR-Force scene simulation system is used to perform strict simulation joint test with the message board card, and the message processor correctly and quickly completes message mapping between nodes, so that the effectiveness and the realizability of the embodiment are proved.

Claims (6)

1. A data chain message processing method based on a rescue scene is characterized by comprising the following steps:
step 1, classifying messages needing to be transmitted in a rescue scene based on analysis of a collaborative combat process among nodes in the rescue scene;
step 2, formulating a standard format of the message, which is specifically as follows: the formulated message is named as Q message, the naming format of the Q message is Qn.m, wherein n represents a message identifier, the number is 0-31, 32 numbers are provided in total, m represents a message sub-identifier, the number is 0-7, eight numbers are provided in total, and 256 messages can be formed in total; each message defines three word formats: an initial word, an extended word and a continuation word, each word containing 72 bits;
step 3, setting a message database structure, storing the message content in a database to form a data element dictionary;
and 4, visually describing the message by adopting XML:
step 5, all nodes and links form a network together, and each node encodes or decodes information received from the network or information to be sent;
and 6, each execution node cooperates with other execution nodes in the network to complete tasks according to the instructions issued by the command nodes.
2. The rescue scene-based data chain message processing method as claimed in claim 1, wherein the step 1 classifies messages to be transmitted in the rescue scene based on analysis of the cooperative combat process among the nodes in the rescue scene, and the classification is specifically divided into the following five categories:
(1) aerial platform positioning and system state class messages
The aerial platform comprises an unmanned aerial vehicle; the information is used for reporting the participation state, the identity recognition, the geographic position, the motion state and the positioning navigation content of the air platform network on one hand, and is used for reporting the current state of the air platform on the other hand, each air platform periodically sends the current state information, so that the control center masters the node dynamics and issues a corresponding command;
(2) ground platform positioning and system status type messages
The ground platform comprises an unmanned vehicle and rescue workers; the information reports the platform geographic position, the motion state and the relative navigation information of the unmanned vehicle and the rescue workers on one hand, and reports the current states of the unmanned vehicle and the rescue workers on the other hand, wherein the current states comprise load, electric quantity, working state, platform system state and medicine allowance; each ground platform also needs to periodically send current state information, but the sending period is longer than that of the air platform;
(3) formation of teamed homogeneous messages
The message comprises a command node for distributing tasks in a team and providing target information for the aerial unmanned aerial vehicle; the command platform also receives the command, plans the multilateral flight path information of different unmanned aerial vehicles in the formation and interacts the command with the unmanned aerial vehicles;
(4) monitoring class messages
The messages comprise monitoring messages of special areas or fixed points or tracks, and also comprise track management messages, data updating request messages, pointer messages and filter management messages;
(5) command control type messages
The messages refer to control and cooperation commands issued by command nodes to execution nodes, or state information of battles, control right of a platform, pairing messages and track management messages, and are used for leading the situation of a battlefield.
3. The rescue scenario-based data chain message processing method as claimed in claim 1, wherein the initial word structure is as shown in table 1, the word is identified as "00", each message has one and only one initial word, and the method must start with the initial word:
TABLE 1
Character mark Message identification Message sub-identity Message length Information segment Error detection section
The extension word is shown in table 2, and its word is labeled "10", when the data length of the message that the node needs to send exceeds the payload of the initial word, the extension word is added to extend the message, each message has at most one extension word, and the extension word can only be sent after the initial word:
TABLE 2
Character mark Information segment Error detection section
The continuation word is shown in table 3, the word label of which is "01", is a supplement to information based on the initial word and the extended word, each message can contain 0 to a plurality of continuation words, but one message contains 8 words at most, each time the message is sent, a part of the continuation words can be selected to be sent, and the sending sequence of the continuation words is arbitrary:
TABLE 3
Character mark Continuation word mark Information segment Error detection section
4. The rescue scenario-based data link message processing method according to claim 1, wherein the step 3 sets a message database structure, stores message contents into a database, and forms a data element dictionary, specifically:
the established message standard architecture is divided into five layers, namely a function group, a message category, a message word, a DFI and a DUI, wherein a data field identifier DFI represents a data element of each word, and a data use identifier DUI is a data item corresponding to the data element; each function group comprises a plurality of messages, each message consists of one to a plurality of words, and each word consists of DFI and DUI items; and storing the DFI and the DUI into a database to form a data element dictionary library, and forming a complete message by combining the DFI and the DUI.
5. The rescue scenario-based data chain message processing method according to claim 1, wherein in step 4, the message is visually described by using XML, and specifically the following steps are performed:
each node receives messages sent by other node devices from the network, converts binary code stream messages into visual XML files through JAVA language, and analyzes the messages according to the mapping relation in the database; when the information is transmitted to other node devices, the information to be transmitted is visually described by using an XML file, and the file is converted into a binary code stream by using a JAVA language and is transmitted into a network.
6. The rescue scenario-based data chain message processing method according to claim 1, wherein each node encodes or decodes information received from within a network or information to be transmitted at step 5, wherein:
the message encoding process is as follows:
(1.1) loading a structured file, acquiring a message identifier (MessageID) and a Version number Version from a file header, and determining a corresponding template configuration file according to the message identifier and the Version number;
(1.2) loading a corresponding Q message configuration XML template from a template configuration file library, acquiring the number ElementCnt of message body elements and Reserve field, and splicing the message identifier, the version number, the number of the message body elements and the Reserve field into a message header of the Q message in sequence according to the definition of the Q message header;
(1.3) each element has its own serial number SN, the sequence is increased from 1, according to an XML template configured by Q messages, according to the SN serial number, the element configuration information in the XML template is sequentially obtained, for the element with SN equal to 1, the corresponding attribute identifier ZBS and the attribute name, namely word identifier, are searched in a data element dictionary base according to the DFI and DUI serial numbers, according to the attribute identifier, the value of the element is searched in the structured data according to the path/Message/Body/ZBS, the value is converted into a Bit value, according to the length information in the XML template, the Bit value is complemented, the coding of the Message element is completed, and the coded Bit value is spliced to a Message Body;
(1.4) coding the elements in sequence according to the sequence of the SN to complete the splicing of the Q message body;
(1.5) splicing the Q message header and the Q message body into a complete Q message for outputting, and finishing coding;
the message decoding process is as follows:
(2.1) intercepting a Message header of the Q Message according to bits, namely the first 24Bit bits, analyzing a Message identifier and a Version number of the Q Message according to the bits, respectively outputting the Message identifier and the Version number to corresponding nodes/Message/Head/Message ID and/Message/Head/Version in the structured data, and determining a configuration XML template of the Q Message according to the Message identifier and the Version number;
(2.2) loading the determined Q Message configuration XML template, acquiring the element quantity ElementCnt of the Message Body, sequentially acquiring element configuration information in the XML template according to the SN serial number according to the XML template configured by the Q Message, searching a corresponding attribute identifier ZBS and an attribute name, namely a word identifier, in an element data dictionary library according to DFI/DUI for the element with the SN of 1, intercepting the offset length Bit value of the Message Body according to length, converting the Bit value into the value of structured data, and outputting the value to a corresponding node/Message/Body/QZGZBS in the structured data;
(2.3) decoding corresponding elements according to the SN sequence number sequence and outputting the elements to corresponding nodes in the structured data;
and (2.4) outputting the structured data as a whole, and finishing decoding.
CN202010874451.3A 2020-08-27 2020-08-27 Rescue scene-based data link message processing method Active CN112187717B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010874451.3A CN112187717B (en) 2020-08-27 2020-08-27 Rescue scene-based data link message processing method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010874451.3A CN112187717B (en) 2020-08-27 2020-08-27 Rescue scene-based data link message processing method

Publications (2)

Publication Number Publication Date
CN112187717A CN112187717A (en) 2021-01-05
CN112187717B true CN112187717B (en) 2021-10-29

Family

ID=73925107

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010874451.3A Active CN112187717B (en) 2020-08-27 2020-08-27 Rescue scene-based data link message processing method

Country Status (1)

Country Link
CN (1) CN112187717B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113946562A (en) * 2021-10-14 2022-01-18 国云科技股份有限公司 Visual design platform of data collaboration chain

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104143170A (en) * 2014-07-25 2014-11-12 南京航空航天大学 Low-altitude rescue air traffic dispatching command system and dispatching command method thereof
CN109120685A (en) * 2018-08-06 2019-01-01 北京北大青鸟安全系统工程技术有限公司 A kind of emergency management and rescue maneuvering platform based on security monitoring management

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3139518A1 (en) * 2015-09-07 2017-03-08 BAE Systems PLC Apparatus and method for communications management
CN106656300A (en) * 2016-12-21 2017-05-10 中国航天时代电子公司 UAV cluster combat system utilizing ad-hoc network data chain
CN108206715B (en) * 2017-12-18 2022-01-18 中交遥感天域科技江苏有限公司 Unmanned vehicles formation flight control data chain system based on ethernet
CN108008738A (en) * 2017-12-27 2018-05-08 贵州大学 Target Tracking System under being cooperateed with based on unmanned plane with unmanned vehicle
CN110557285B (en) * 2019-09-03 2022-04-19 明峰医疗系统股份有限公司 Detector data acquisition system architecture and communication method

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104143170A (en) * 2014-07-25 2014-11-12 南京航空航天大学 Low-altitude rescue air traffic dispatching command system and dispatching command method thereof
CN109120685A (en) * 2018-08-06 2019-01-01 北京北大青鸟安全系统工程技术有限公司 A kind of emergency management and rescue maneuvering platform based on security monitoring management

Also Published As

Publication number Publication date
CN112187717A (en) 2021-01-05

Similar Documents

Publication Publication Date Title
US10074220B2 (en) Big telematics data constructing system
CN105429858A (en) Real-time message transmission method among multiple robots
KR101212507B1 (en) Lvc interoperatiblity test method and appartus for weapon system modeling simulation
CN112187717B (en) Rescue scene-based data link message processing method
CN104680853A (en) Automatic ADS-B double-data-chain switching device based on height
CN108021144A (en) A kind of unmanned aerial vehicle flight path planning and dynamic threats evade emulator
CN109496303A (en) The methods of exhibiting and device and unmanned plane monitoring system of monitored data
Baumgärtner et al. LoRAgent: a DTN-based location-aware communication system using LoRa
CN110674584B (en) Multi-aircraft joint simulation system
CN112199816A (en) Flight ADS-B data simulation method
TWI698096B (en) Connected system for outdoor activity groups
Barth et al. Web-based solutions for communication and knowledge management in disaster situations
CN111770066B (en) Data chain variable message processing method and device for sea, land and air interaction scene
EP2877988A1 (en) Electronic interface device between communication networks among vehicles
CN108387237A (en) General Aviation radar number passes ip radio station networking navigation system
CN208924239U (en) The interacted system and interconnect device of outdoor activities group
CN108551475A (en) Data transmission method and device
CN208140134U (en) General Aviation radar number passes the radio station ip networking navigation system
Yeniçeri et al. Enabling Centralized UTM services through cellular network for VLL UAVs
CN103716382A (en) XML-based data communication method for Beidou navigation, search and rescue system
CN112214209A (en) Modeling method for interaction information and task time sequence in unmanned aerial vehicle operation scene
DuBois et al. Open Networking Technologies for the Integration of Net-Ready Applications on Rotorcraft
CN112130467B (en) Semi-physical simulation system and method based on tactical frontier network
Chen et al. UAV real-time data acquisition and visualization system based on 3D route planning
Pastor et al. Helicopter-based wildfire monitoring system software architecture

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant