Method for exchanging data between artillery information processing system and bus

Abstract

The invention discloses a data exchange method between an artillery information processing system and a bus, which realizes automatic receiving and unpacking and automatic packing and sending functions of system data by constructing a data exchange protocol and bus relation table, an exchange protocol relation table, a lookup table corresponding to a sending message association relation and a specific exchange protocol data structure. Universalization processing of data receiving and transmitting between an artillery information processing system and a bus is completed; according to the method and the device, aiming at the conditions of communication protocol adjustment and the like caused by system demand change, only the adjusted communication protocol needs to be re-recorded into the database according to the predefined format, so that the research and development pressure of a data encoding and decoding program is effectively reduced, and the system research and development cost caused by the demand change and the protocol adjustment is greatly reduced. Meanwhile, the user can complete data interaction with the bus by directly accessing the data center, so that software and hardware differences of heterogeneous buses are shielded for the user, the system coupling is reduced, and the software reliability is improved.

Description

Technical Field

[0001] The invention relates to the field of data processing, and in particular to a method for exchanging data between a gun information processing system and a bus. Background Art

[0002] During the design and development of the artillery information processing system, it is necessary to formulate the communication protocol between the artillery information processing system and the bus according to the combat process and requirements of the weapon system, and the researchers will develop the data encoding and decoding program according to the formulated communication protocol. However, with the frequent changes in the requirements of the weapon system and the continuous optimization and adjustment of the combat process, the communication protocol between the system and the bus must also be adjusted accordingly, which brings cumbersome and heavy workload for the researchers to develop and debug the data encoding and decoding program; at the same time, when the artillery information processing system interacts with different types of buses, it needs to go through the corresponding bus interface, resulting in too high coupling between the entire system and the bus and poor scalability. Summary of the invention

[0003] The purpose of the present invention is to provide a method for exchanging data between an artillery information processing system and a bus, so as to meet the demand for exchanging data between the artillery information processing system and the bus and reduce the coupling of the system.

[0004] In order to achieve the above tasks, the present invention adopts the following technical solutions:

[0005] A method for exchanging data between a gun information processing system and a bus, comprising:

[0006] Step 1, defining a data exchange protocol between the artillery information processing system and the bus; a data exchange protocol includes a plurality of sub-protocol frames, wherein a sub-protocol frame is composed of a plurality of fields having specific meanings;

[0007] Step 2, the exchange protocol is stored in a database, and a data exchange protocol and bus relationship table and an exchange protocol relationship table are constructed, wherein the data exchange protocol and bus relationship table records the corresponding relationship between the data exchange protocol and the bus and the table name in the database that have been entered into the database, and the exchange protocol relationship table records the specific contents of all fields of different sub-protocol frames in the data exchange protocol;

[0008] Step 3, querying the data exchange protocol in the data exchange protocol and bus relationship table according to the bus type, and obtaining the name of the exchange protocol relationship table corresponding to the data exchange protocol;

[0009] Step 4: According to the name of the exchange protocol relationship table found, the corresponding exchange protocol relationship table is associated from the database, and according to the number of sub-protocol frames in the table, corresponding memory space is opened for different message types;

[0010] Step 5, based on the exchange protocol relationship table, first classify the different fields in the table according to the message type, and then based on the frame identifier, put all the fields belonging to the same sub-protocol frame into the memory space corresponding to the corresponding message type to form an exchange protocol data structure;

[0011] Step 6, associating the positions of all fields of the sub-protocol frame whose message type is the sending message in the exchange protocol relationship table in the memory space with the frame identifier of the sub-protocol frame, and constructing a lookup table corresponding to the sending message association relationship;

[0012] Step 7, establishing a hash table, taking the frame identifier of the subprotocol frame of the message type as the input parameter, calculating the hash value by the hash function as its storage position in the hash table, and storing the frame identifier and the position index of the frame identifier in the memory space corresponding to the corresponding message type in the storage position;

[0013] Step 8, from the exchange protocol relationship table, find the location in the memory space corresponding to all fields of the sub-protocol frame of the sent message and the received message, and then allocate corresponding storage space to each storage location in the memory space and name it with the name of the storage location.

[0014] Furthermore, when the bus data needs to be written into the memory space of the artillery information processing system, the receiving data processing flow is entered:

[0015] The artillery information processing system reads the data frame from the bus and obtains the frame identifier, then uses the frame identifier as an input parameter, uses a hash function to calculate a hash value, and obtains the position index in the memory space corresponding to the frame identifier from the hash table according to the hash value; then, according to the position index, the data blocks of the fields corresponding to the frame identifier are parsed in sequence from the corresponding data exchange structure, and the parsed data is written to the storage space corresponding to the field in the memory space.

[0016] Furthermore, when the memory space update data of the artillery information processing system needs to be sent to the bus, the data sending process is entered:

[0017] After the value of the storage location corresponding to the field of the sub-protocol frame in the memory space of the artillery information processing system is updated, the updated data is read, and then the corresponding lookup table is searched according to the association relationship of the sent message to find the frame identifier corresponding to the storage location, and then the exchange protocol data structure corresponding to the sub-protocol frame is found from the memory space according to the frame identifier, and the data content in the storage location is converted into bus format data in turn and then sent to the bus.

[0018] Furthermore, the sub-protocol frame includes a message name, a message type, a frame identifier, a message length, a sequence number, a byte placeholder, a data type, a field name, and a key name, wherein:

[0019] The message name indicates the name of the sub-protocol frame message; the message type indicates whether the frame message is a message received from the bus, i.e., a receive message, or a message sent to the bus, i.e., a send message; the frame identifier indicates the data identifier of the frame, which is used to distinguish different sub-protocol frames; the message length indicates how many bytes of valid data the sub-protocol frame has; the sequence number indicates the order of the fields in the sub-protocol frame; the byte placeholder indicates how many bytes the field has; the data type indicates the specific data type of the field; the field name indicates the meaning represented by the field; the key name indicates the storage location of the field in the memory space.

[0020] Furthermore, in the data exchange protocol and bus relationship table:

[0021] bus_name indicates the name of the data exchange protocol, which is used to distinguish different data exchange protocols; bus_type indicates the type of the bus; "table_name" indicates the name of the exchange protocol relationship table of the data exchange protocol in the database; using indicates whether the data exchange protocol is used.

[0022] Furthermore, in the exchange protocol relationship table:

[0023] rule_id indicates the primary key of a row of records, which is used to distinguish different fields of the entered subprotocol frame; frame_id is the frame identifier of the subprotocol frame; field_sn indicates the order of the fields in the subprotocol frame; field_type indicates the data type of the field; field_len indicates the byte length of the field; pack_set is the message type, indicating that the field belongs to a received message or a sent message; key indicates the corresponding position of the data of the field in the memory space.

[0024] Furthermore, in the memory space corresponding to the received message or the sent message, the frame identifier of the sub-protocol frame is placed at the memory space position index 0, and all the fields of the sub-protocol frame are arranged sequentially according to the field order; each field and the corresponding byte length and its position in the memory space are regarded as a data block, thereby forming an exchange protocol data structure.

[0025] A data exchange system comprises a gun information processing system and a bus. The exchange system adopts the data exchange method between the gun information processing system and the bus to exchange data.

[0026] Compared with the prior art, the present invention has the following technical features:

[0027] The present invention completes the automatic reception and transmission of data information, realizes the universalization of data transmission and reception between the system and the bus, and the researchers only need to re-enter the adjusted protocol into the database, which effectively reduces the research and development pressure of the data encoding and decoding program. At the same time, the method realizes the data interaction between the system and the bus through the data center, and the user can directly access the data center to complete the data interaction of the bus, thereby shielding the software and hardware differences of the heterogeneous bus from the user, reducing the system coupling, and improving the reliability of the software. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 This is a schematic diagram of the data exchange method architecture of the present invention;

[0029] Figure 2 It is a data exchange protocol data structure;

[0030] Figure 3 Schematic diagram of the frame identifier storage structure in the hash table. DETAILED DESCRIPTION

[0031] See attached Figure 1 The present invention provides a method for exchanging data between a gun information processing system and a bus, comprising the following steps:

[0032] Step 1, define the data exchange protocol between the artillery information processing system and the CAN bus; a data exchange protocol includes multiple sub-protocol frames, where a sub-protocol frame consists of multiple fields with specific meanings, including message name, message type, frame identifier, message length, sequence number, byte placeholder, data type, field name and key name, as shown in Table 1.

[0033] Table 1 Example of data exchange protocol between artillery information processing system and CAN bus

[0034]

[0035] Among them, "Message Name" indicates the name of the protocol frame message; "Message Type" indicates whether the frame message is a message received from the bus, that is, a receive message, or a message sent to the bus, that is, a send message; "Frame Identifier" indicates the data identifier of the frame, which is used to distinguish different sub-protocol frames; "Message Length" indicates how many bytes of valid data the sub-protocol frame has; "Sequence Number" indicates the order of the field in the sub-protocol frame; "Byte Placeholder" indicates how many bytes the field has; "Data Type" indicates the specific data type of the field; "Field Name" indicates the meaning of the field; "Key Name" indicates the storage location of the field in the data center, and the data center is the memory space that stores all data in the artillery information processing system.

[0036] For example, the "diagnostic report" message is a receiving message, which consists of three fields: "diagnostic unit", "diagnostic result", and "reporting time". The "photoelectric mode" message is a sending message, which consists of six fields: "message time", "photoelectric mode", "automatic tracking", "laser emission", "automatic focusing", and "resolution".

[0037] Step 2, enter the data exchange protocol between the artillery information processing system and the CAN bus in step 1 into the database to form the relationship tables shown in Table 2 and Table 3. Table 2 is the data exchange protocol and bus relationship table, which records the correspondence between the data exchange protocol that has been entered into the database and the bus and the table name in the database; Table 3 is the exchange protocol relationship table, which records the specific contents of all fields of different sub-protocol frames in the data exchange protocol.

[0038] Table 2 Data exchange protocol and bus relationship table

[0039] bus_name bus_type table_name using Exchange Protocol 1 CAN tbl_2023 1

[0040] Table 3 Exchange protocol relationship table of exchange protocol 1 (tbl_2023)

[0041] rule_id frame_id field_sn field_type field_len pack_set key 20232526 0x08f00010 1 uint8 1 0 zdt 20232527 0x08f00010 2 uint8 1 0 zdj 20232528 0x08f00010 3 uint8 1 0 sbsk 20232529 0x04100020 1 uint8 1 1 wxya 20232530 0x04100020 2 uint8 1 1 gdms 20232531 0x04100020 3 uint8 1 1 zdj 20232532 0x04100020 4 uint8 1 1 f 20232533 0x04100020 5 uint8 1 1 zdj 20232534 0x04100020 6 uint8 1 1 fbl

[0042] In Table 2, "bus_name" represents the name of the data exchange protocol. In this embodiment, for the exchange protocol in Table 1, its value is "bus protocol 1", which means the name of the data exchange protocol between the artillery information processing system and the bus, and is used to distinguish different data exchange protocols; "bus_type" represents the type of the bus, and is used to distinguish different types of buses; if the value is "CAN", it means that the bus is a CAN bus; "table_name" represents the name of the exchange protocol relationship table of the data exchange protocol in the database, if the value is "tbl_2023", it means that the corresponding relationship table name of the data exchange protocol in the database is "tbl_2023", which is used to find the relationship table of the data exchange protocol from the database; "using" indicates whether the data exchange protocol is used, and its value is "1", which means that the data exchange protocol is used, and if the value is "0", it is not used.

[0043] In Table 3, "rule_id" indicates the primary key of a row of records, which is used to distinguish different fields of the entered sub-protocol frame; "frame_id" is the frame identifier of the sub-protocol frame; "field_sn" indicates the field order, which is the order of the field in the sub-protocol frame, and its value is "1", "2", etc., which means that the fields are first and second in the sub-protocol frame respectively; "field_type" indicates the data type of the field; "field_len" indicates the byte length of the field, that is, how many bytes it occupies; "pack_set" is the message type, indicating that the field belongs to a received message or a sent message, and the value is "0" for receiving a message, and the value is "1" for sending a message; "key" indicates the corresponding position of the data of the field in the memory space.

[0044] Step 3, according to the bus type, query the data exchange protocol in the data exchange protocol and bus relationship table, that is, Table 2, for the data exchange protocol in use state, and obtain the name of the exchange protocol relationship table corresponding to the data exchange protocol.

[0045] For example, based on Table 2, if communication with CAN is required, then according to the conditions that bus_type is equal to "CAN" and using is equal to "1", the exchange protocol relationship table name corresponding to the data exchange protocol is found to be "tbl_2023" from the data exchange protocol and bus relationship table.

[0046] Step 4: According to the found exchange protocol relationship table name, associate with the corresponding exchange protocol relationship table from the database, and according to the number of sub-protocol frames in the table, open up corresponding memory space for different message types.

[0047] Step 5, based on the contents in the exchange protocol relationship table, firstly classify the different fields in the table into receive messages and send messages according to the value of the message type "pack_set" being "0" or "1"; then, based on the frame identifier, put all the fields belonging to the same sub-protocol frame into the memory space corresponding to the "receive message" or "send message";

[0048] Among them, in the memory space corresponding to the "receive message" or "send message", the frame identifier of the sub-protocol frame is placed at the memory space position index 0, and all the fields of the sub-protocol frame are arranged in sequence according to the field order; each field and the corresponding byte length and its position in the memory space are regarded as a data block, thereby forming an exchange protocol data structure.

[0049] See also Figure 2The data structure is given, where "type" corresponds to "field_type" in Table 3, "len" corresponds to "field_len" in Table 3, and "key" corresponds to "key" in Table 3; in this memory space, the received message data exchange protocol represented by the frame identifier 0x08f00010 is stored at index 0 of the received message memory space, and the sent message data exchange protocol represented by the frame identifier 0x04100020 is stored at index 0 of the sent message memory space.

[0050] Step 6, associate the positions of all fields of the sub-protocol frame whose message type is the sending message in the exchange protocol relationship table in the memory space with the frame identifier of the sub-protocol frame, and construct a corresponding lookup table for the sending message association relationship, as shown in Table 4; in this table, the corresponding frame identifier can be queried through the position of the field in the memory, that is, the key value.

[0051] Table 4 Sending message association relationship corresponding lookup table

[0052]

[0053] Step 7, establish a hash table, take the frame identifier of the subprotocol frame of the message type sending message as the input parameter, calculate the hash value by the hash function as its storage position in the hash table, and store the frame identifier and the position index of the frame identifier in the memory space corresponding to the corresponding message type in step 5 into the storage position, such as Figure 3 shown.

[0054] For example, the received message frame identifier 0x08f00010 in the data exchange protocol in Table 3 is used as the input parameter, and the hash function selects the division and remainder method, that is, H(k)=kmodp, p≤m, where H(k) represents the hash value obtained after hashing k, k is the input parameter, that is, the frame identifier, mod represents the modulus division operation, p is the modulus, usually a prime number or a large integer, and m is the length of the hash table; when different input parameters are hashed to obtain the same hash value, a conflict occurs, and the continuous address method (zipper method) can be selected to resolve the conflict.

[0055] Here, 0x08f00010 is used as the input parameter, that is, the k value, the p value is 13, and the m value is 13. After calculation by the hash function H(k), the hash value is 3, that is, the frame identifier 0x08f00010 and its corresponding data exchange protocol data structure are stored at position 3 of the hash table at position index 0 in the memory space shown in step 5.

[0056] Step 8, from the exchange protocol relationship table, find the keys corresponding to all fields of the sub-protocol frames of the sent message and the received message, and then allocate corresponding storage space for each key in the memory space and name it with the key.

[0057] When the data of the CAN bus needs to be written into the memory space of the artillery information processing system, the receiving data processing flow is entered; when the memory space update data of the artillery information processing system needs to be sent to the CAN bus, the sending data processing flow is entered.

[0058] The received data processing flow is as follows:

[0059] The artillery information processing system reads the data frame from the CAN bus and obtains the frame identifier, such as 0x08f00010; then the frame identifier is used as an input parameter, and the hash value is calculated using the hash function selected in step 7, and the position index 0 in the memory space corresponding to the frame identifier is obtained from the hash table according to the hash value; then according to the position index, the data blocks of the fields corresponding to the frame identifier are parsed in sequence from the corresponding data exchange structure, and the parsed data are written to the storage space corresponding to the field in the memory space; for example, the parsed data is written to the storage space corresponding to zddt, zdjg, and sbsk.

[0060] The data sending process is as follows:

[0061] After the storage location corresponding to the field of the sub-protocol frame in the memory space of the artillery information processing system, that is, the value of the key such as bwsk, gdms, zdgz, fsjg, zdtj, fbl, etc. is updated (that is, the information of the field is changed), the updated data is read, and then the corresponding lookup table is searched according to the sending message association relationship established in step 6 to find the frame identifier 0x04100020 corresponding to the storage location key, and then the exchange protocol data structure corresponding to the sub-protocol frame is found from the memory space of step 5 according to the frame identifier, and then the values ​​of the keys such as bwsk, gdms, zdgz, fsjg, zdtj, fbl, etc. are converted into CAN bus format data in turn, and then sent to the CAN bus.

[0062] The data exchange method provided by the present invention can automatically receive and send data information, and realize the universalization of data transmission and reception between the system and the bus; researchers only need to re-enter the adjusted protocol into the database, which effectively reduces the research and development pressure of data encoding and decoding programs. At the same time, the method realizes data interaction between the system and the bus through the data center, and users can directly access the data center to complete data interaction on the bus, thereby shielding the software and hardware differences of heterogeneous buses from users, reducing system coupling, and improving software reliability.

[0063] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for exchanging data between a gun information processing system and a bus, characterized in that: include: Step 1, defining a data exchange protocol between the artillery information processing system and the bus; a data exchange protocol includes a plurality of sub-protocol frames, wherein a sub-protocol frame is composed of a plurality of fields having specific meanings; Step 2, the exchange protocol is stored in a database, and a data exchange protocol and bus relationship table and an exchange protocol relationship table are constructed, wherein the data exchange protocol and bus relationship table records the corresponding relationship between the data exchange protocol and the bus and the table name in the database that have been entered into the database, and the exchange protocol relationship table records the specific contents of all fields of different sub-protocol frames in the data exchange protocol; Step 3, querying the data exchange protocol in the data exchange protocol and bus relationship table according to the bus type, and obtaining the name of the exchange protocol relationship table corresponding to the data exchange protocol; Step 4: According to the name of the exchange protocol relationship table found, the corresponding exchange protocol relationship table is associated from the database, and according to the number of sub-protocol frames in the table, corresponding memory space is opened for different message types; Step 5, based on the exchange protocol relationship table, first classify the different fields in the table according to the message type, and then based on the frame identifier, put all the fields belonging to the same sub-protocol frame into the memory space corresponding to the corresponding message type to form an exchange protocol data structure; Step 6, associating the positions of all fields of the sub-protocol frame whose message type is the sending message in the exchange protocol relationship table in the memory space with the frame identifier of the sub-protocol frame, and constructing a lookup table corresponding to the sending message association relationship; Step 7, establishing a hash table, taking the frame identifier of the subprotocol frame of the message type as the input parameter, calculating the hash value by the hash function as its storage position in the hash table, and storing the frame identifier and the position index of the frame identifier in the memory space corresponding to the corresponding message type in the storage position; Step 8, from the exchange protocol relationship table, find the location in the memory space corresponding to all fields of the sub-protocol frame of the sent message and the received message, and then allocate corresponding storage space to each storage location in the memory space and name it with the name of the storage location.

2. The data exchange method between the artillery information processing system and the bus according to claim 1, characterized in that: When the bus data needs to be written into the memory space of the artillery information processing system, the receiving data processing flow is entered: The artillery information processing system reads the data frame from the bus and obtains the frame identifier, then uses the frame identifier as an input parameter, uses a hash function to calculate a hash value, and obtains the position index in the memory space corresponding to the frame identifier from the hash table according to the hash value; then, according to the position index, the data blocks of the fields corresponding to the frame identifier are parsed in sequence from the corresponding data exchange structure, and the parsed data is written to the storage space corresponding to the field in the memory space.

3. The data exchange method between the artillery information processing system and the bus according to claim 1, characterized in that: When the memory space update data of the artillery information processing system needs to be sent to the bus, the data sending process begins: After the value of the storage location corresponding to the field of the sub-protocol frame in the memory space of the artillery information processing system is updated, the updated data is read, and then the corresponding lookup table is searched according to the association relationship of the sent message to find the frame identifier corresponding to the storage location, and then the exchange protocol data structure corresponding to the sub-protocol frame is found from the memory space according to the frame identifier, and the data content in the storage location is converted into bus format data in turn and then sent to the bus.

4. The data exchange method between the artillery information processing system and the bus according to claim 1, characterized in that: The sub-protocol frame includes a message name, a message type, a frame identifier, a message length, a sequence number, a byte placeholder, a data type, a field name, and a key name, wherein: The message name indicates the name of the sub-protocol frame message; the message type indicates whether the frame message is a message received from the bus, i.e., a receive message, or a message sent to the bus, i.e., a send message; the frame identifier indicates the data identifier of the frame, which is used to distinguish different sub-protocol frames; the message length indicates how many bytes of valid data the sub-protocol frame has; the sequence number indicates the order of the fields in the sub-protocol frame; the byte placeholder indicates how many bytes the field has; the data type indicates the specific data type of the field; the field name indicates the meaning represented by the field; the key name indicates the storage location of the field in the memory space.

5. The data exchange method between the artillery information processing system and the bus according to claim 1, characterized in that: In the data exchange protocol and bus relationship table: bus_name indicates the name of the data exchange protocol, which is used to distinguish different data exchange protocols; bus_type indicates the type of the bus; "table_name" indicates the name of the exchange protocol relationship table of the data exchange protocol in the database; using indicates whether the data exchange protocol is used.

6. The data exchange method between the artillery information processing system and the bus according to claim 1, characterized in that: In the Exchange Protocol Relationship table: rule_id indicates the primary key of a row of records, which is used to distinguish different fields of the entered subprotocol frame; frame_id is the frame identifier of the subprotocol frame; field_sn indicates the order of the fields in the subprotocol frame; field_type indicates the data type of the field; field_len indicates the byte length of the field; pack_set is the message type, indicating that the field belongs to a received message or a sent message; key indicates the corresponding position of the data of the field in the memory space.

7. The data exchange method between the artillery information processing system and the bus according to claim 1, characterized in that: In the memory space corresponding to the received message or the sent message, the frame identifier of the sub-protocol frame is placed at the memory space position index 0, and all the fields of the sub-protocol frame are arranged in sequence according to the field order; each field and the corresponding byte length and its position in the memory space are regarded as a data block, thereby forming an exchange protocol data structure.

8. A data exchange system, comprising a gun information processing system and a bus; characterized in that: The exchange system uses the data exchange method between the artillery information processing system and the bus according to any one of claims 1-7 to exchange data.

Images