Method for processing bitstream data by using code-free reconstruction, and computing device therefor

Abstract

The present invention provides a method for processing bitstream data by using code-free reconstruction, and a computing device therefor. A code-free protocol template file is used to define content parameters for each field of bitstream data in a communication protocol. A data parsing and processing method is used to parse a bitstream data frame, and perform forward processing on the bitstream data on the basis of field parameter information in the code-free protocol template, so as to obtain data content information suitable for display and application. An information packaging and processing method is used to perform reverse processing on user-inputted field content information on the basis of the field parameter information in the code-free protocol template, so as to generate bitstream data for communication transmission. The present invention uses different protocol template files to accommodate bitstream data of different protocols. During implementation iterations of engineering projects, a new data protocol can be accommodated merely by editing a code-free protocol template file without the need to modify source code, thereby shortening the development cycle of data processing software, reducing quality risks and management costs, and improving development efficiency.

Description

A non-coded reconstruction method for bitstream data processing and its computing device Technical Field

[0001] This invention relates to the field of electronic digital data processing technology, and specifically to a non-coded reconstruction bitstream data processing method and computing device thereof. Background Technology

[0002] Bitstream communication is characterized by high information transmission efficiency, flexible content definition, and high data processing efficiency. It is often used in scenarios such as communication between aerospace equipment and ground, communication between electronic equipment and monitoring systems, and debugging, development, and testing of industrial equipment. However, due to the above factors, bitstream communication has the characteristics of poor universality and low direct identification, requiring dedicated data processing software to be configured at the communication transceiver end.

[0003] Traditional bitstream data processing software often relies on a defined communication protocol. Software developers customize a set of dedicated processing methods for specific data protocols and develop dedicated encoding and decoding programs to parse and package bitstream data.

[0004] In the aforementioned data processing, each modification, supplement, or deletion of the protocol requires software developers to rewrite, debug, and test the code before it can be applied. However, in actual engineering development, communication protocols are often finalized and continuously iterated and modified during implementation. This is especially true for ground monitoring products for aerospace equipment, which are often not the core products of the system. Frequent changes cause delays in the debugging and testing of the main aerospace products, increasing development and maintenance costs.

[0005] Therefore, there is an urgent need for a bitstream data processing method that supports rapid reconstruction of communication protocols without code editing. Summary of the Invention

[0006] This invention addresses the problem of reconstructing bitstream data processing software by providing a non-coded bitstream data processing method and its computing device. It employs a non-coded protocol template file to define the field content parameters of bitstream data in a communication protocol. A data parsing method parses the bitstream data frames and processes the bitstream data forward based on the field parameter information in the non-coded protocol template, obtaining data content information that is easy to display and apply. An information packaging method reverse-processes the user-input field content information based on the field parameter information in the non-coded protocol template, generating bitstream data for communication transmission. This invention adapts to bitstream data of different protocols using different protocol template files. During project implementation iterations, only the non-coded protocol template file needs to be edited to adapt to new data protocols, without modifying the source code. This reduces the data processing software development cycle, lowers quality risks and management costs, and improves development efficiency.

[0007] This invention provides a non-coded reconstruction bitstream data processing method, which involves receiving bitstream data frames, parsing the data to enter step S1, and packaging and processing the user-input data field content information to enter step S2.

[0008] S1. Load the non-coded protocol template file, read the received bitstream data frames into the buffer, then parse the bitstream data frames according to the field parameter information in the non-coded protocol template file and output data content information that is easy to display and apply.

[0009] S2. Load the non-coded protocol template file and calculate the total bit length of the data packets in the non-coded protocol template file. Generate a bit data frame buffer and initialize it. Import the data field content information, reverse process the user input field content according to the field parameter information in the non-coded protocol template file to generate bit data segments and insert them into the bit stream data packets. Then output the bit stream data packets used for communication transmission.

[0010] In steps S1 and S2, the non-coded protocol template is a specific description of the defined data content. The non-coded protocol template includes one or more of the following: field name, bit placeholder parameter, data type parameter, data operation parameter, display type parameter, and display supplementary parameter for each field in the bitstream data frame.

[0011] The non-coded reconstruction bitstream data processing method of the present invention, as a preferred embodiment, includes bit placeholder parameters including bit start position and number of bits in the field, data operation parameters including one or more of data resolution parameters, data offset value parameters and exponentiation parameters, and display supplementary parameters including one or more of display prefix parameters and display suffix parameters.

[0012] The non-coded reconstructed bitstream data processing method described in this invention, as a preferred embodiment, involves receiving bitstream data frames and user-inputted data field content information that both conform to an example of a non-coded protocol template file.

[0013] The non-coded reconstruction bitstream data processing method of the present invention, in a preferred embodiment, includes the following steps in step S1:

[0014] S11. Load the non-coded protocol template file;

[0015] S12. Read the received bitstream data frame into the buffer;

[0016] S13. Parse the bitstream data frame based on the parameter information of each field in the non-coded protocol template file;

[0017] S131. Read the single-field parameter information of the non-coded protocol template file to obtain the field name, bit place parameter, data type parameter, data operation parameter, display type parameter and display supplementary parameter;

[0018] S132. Extract the bit data segment corresponding to the field from the bit stream data frame according to the bit placeholder parameter;

[0019] S133. Convert the extracted bit data segment into the basic value of the data type parameter according to the data type parameter;

[0020] S134. Based on the data operation parameters, perform positive processing on the basic values ​​to obtain intermediate values ​​after data operation;

[0021] S135. Convert the intermediate values ​​after data calculation according to the data display type parameter and convert them into display values ​​of the corresponding display type;

[0022] S136. Based on the field name and supplementary display parameters, supplement the displayed values ​​with field names and prefix / suffix information to obtain the displayed content;

[0023] S14. Output data content information that is easy to display and apply.

[0024] In a preferred embodiment of the non-coded reconstruction bitstream data processing method of the present invention, in step S13, when the number of fields is at least two, the fields are processed sequentially according to their order.

[0025] The non-coded reconstruction bitstream data processing method of the present invention, in a preferred embodiment, includes the following steps in step S132:

[0026] S1321. Based on the bit start position S and the number of bits in the field L, obtain the number of remaining bytes h from the start position P to the end of the byte in the start byte of the field's valid data, and determine whether the bit data segment spans bytes.

[0027] If not, calculate the starting byte of the field where the bit start position is located, and the starting position of the valid data of the field within the byte of the starting byte; extract a bit data segment of the length of the field starting from the starting position within the byte of the starting byte;

[0028] If so, proceed to step S1322, which includes:

[0029] S13221. Calculate the starting byte where the field starts, the starting position of the valid data of the field within the byte of the starting byte, and the number of bits occupied by the data segment in the starting byte to obtain the number of complete bytes occupied by the data segment, the incomplete bytes occupied by the end of the valid data segment, and the ending position of the last bit of the valid data of the field within the incomplete bytes occupied by the end of the valid data segment.

[0030] S13222. Extract the bit segment from the start position within the start byte to the end of the start byte, and use it as the start segment;

[0031] S13223. Extract a data segment starting from the first byte to the right of the start byte, occupying several full bytes, as an intermediate segment;

[0032] S13224. Extract the bit segment from the beginning of the incomplete byte occupied by the end of the valid data segment to the end position of the last bit of the valid data segment in the incomplete byte occupied by the end of the valid data segment, and use it as the end segment;

[0033] S13225. The bit segments of the start segment, middle segment and end segment are concatenated sequentially from left to right to obtain the bit data segments corresponding to the fields.

[0034] In the non-coded reconstruction bitstream data processing method of the present invention, as a preferred embodiment, in step S1321, the starting byte b of the field where the bit start position is located is: b = integer (S ÷ 8);

[0035] The starting position P of the valid data in the field within the starting byte is: P = Sb × 8;

[0036] The number of bytes h remaining from the start position to the end of the byte within the start byte of the valid data is: h = 8 - P;

[0037] The method to determine whether a bit data segment spans multiple bytes is: determine whether h is less than L;

[0038] When h ≥ L, the data field does not span bytes;

[0039] When h < L, the data field spans bytes;

[0040] In step S13221, the number of bits occupied by the data segment in the starting byte is L0, L0 = h, the number of complete bytes occupied by the data segment is L1, L1 = rounded up ((L-L0) / 8)), and the end position of the last bit of the valid data in the incomplete byte occupied by the end of the valid data segment is L2, L2 = L-L0-L1*8;

[0041] In step S13222, a data segment of length L0 is extracted from the starting position P of the field's valid data in the starting byte b of the starting byte where the bit start position is located, and this segment is the starting segment.

[0042] In step S13223, the bit content of L1 bytes, starting from the first byte after the first byte b of the field where the bit start position is located, is extracted as the intermediate segment;

[0043] In step S13224, a bit segment of length L2 bits, starting from the start bit of byte b+L1+1, is extracted as the end segment.

[0044] The non-coded reconstruction bitstream data processing method of the present invention, in a preferred embodiment, includes the following steps in step S2:

[0045] S21. Load the non-coded protocol template file;

[0046] S22. Calculate the total bit length of the data packets in the non-coded protocol template file, generate a bit data frame buffer and initialize it;

[0047] S23. Import the data field content entered by the user;

[0048] S24. Reverse process the user-input data field content information based on the field parameter information in the non-coded protocol template file, and generate bit data segments to insert into bit stream data packets;

[0049] S25. Output bit stream data packets for communication transmission;

[0050] Step S24 includes the following steps:

[0051] S241. Read the single-field parameter information of the non-coded protocol template file to obtain the field name, bit place parameter, data type parameter, data operation parameter, display type parameter and display supplementary parameter of the single field;

[0052] S242. Extract information content that matches the field name in the non-coded protocol template file from the data field content entered by the user based on the field name;

[0053] S243. Extract the display supplementary parameters from the data field content entered by the user to obtain the display value;

[0054] S244. Perform reverse processing on the displayed values ​​according to the display type parameters to obtain the intermediate values ​​after data calculation;

[0055] S245. The intermediate values ​​are reverse-processed according to the data operation parameters to obtain the basic values;

[0056] S246. Insert the basic values ​​into the bit data frame buffer in the form of bit fields according to the bit placeholder parameters.

[0057] S247. Output the bit data packet with completed field filling.

[0058] The non-coded reconstruction bitstream data processing method of the present invention, as a preferred embodiment, includes the following specific steps in step S246 for inserting bit data segments:

[0059] S2461. Calculate the bit length from the start position to the end of the byte within the starting byte of the valid data in the starting byte based on the bit start position and the number of bits in the bit placeholder parameter, and determine whether the bit data segment spans bytes.

[0060] If not, calculate the starting byte of the field where the bit start position is located, and the starting position of the valid data of the field within the byte of the starting byte; insert a bit data segment of the corresponding bit length starting from the starting position within the byte of the starting byte;

[0061] If so, proceed to step S2462, which includes:

[0062] S24621. Calculate the starting byte where the field starts, the starting position of the valid data of the field within the byte of the starting byte, and the starting bit length of the starting segment from the starting position within the byte to the end of the starting byte; calculate the number of complete bytes occupied by the data segment, the bit length of the intermediate segment corresponding to the number of complete bytes, the incomplete bytes occupied by the end segment of the valid data, and the ending position and bit length of the end segment of the last bit of the valid data of the field within the incomplete bytes occupied by the end segment of the valid data;

[0063] S24622. Insert bits of data of length to the left of the starting segment of valid data in the field, starting from the beginning position within the byte of the starting byte.

[0064] S24623. Insert a bit data of the middle bit length starting from the first byte to the right of the starting byte, with the bit length of the field's valid data starting one bit after the starting bit length;

[0065] S24624. Insert bit data of the length of the rightmost end segment of the valid data into the position from the leftmost bit of the incomplete byte occupied by the end segment of the valid data to the end position of the incomplete byte occupied by the end segment of the valid data.

[0066] This invention provides a non-coded reconstructed bitstream data computing device, including a bitstream data parsing processor for parsing bitstream data frames and a bitstream data information packaging processor for packaging bitstream data frames according to user-filled information;

[0067] The bitstream data parsing processor uses the method in step S1 to receive bitstream data frames and parse the data. The bitstream data information packaging processor uses the method in step S2 to package and process the data field content information input by the user and output bit data packets.

[0068] The present invention has the following advantages:

[0069] This invention adapts to new data protocols by editing non-coded protocol template files, enabling protocol updates and the reconstruction of parsing and packaging processes without modifying the source code. This reduces quality risks and management costs, and improves development efficiency. Attached Figure Description

[0070] Figure 1 is a flowchart of a non-coded reconstruction bitstream data processing method and its computing device data parsing and processing method;

[0071] Figure 2 is a flowchart of a non-coded reconstruction bitstream data processing method and its computing device for parsing bitstream data frames;

[0072] Figure 3 is a flowchart of a non-coded reconstruction bitstream data processing method and its computing device for extracting bit data segments;

[0073] Figure 4 is a flowchart of a non-coded reconstruction bitstream data processing method and its computing device information packaging processing method;

[0074] Figure 5 is a flowchart of a non-coded reconstruction bitstream data processing method and its computing device for generating bit data segments and inserting them into bitstream data packets;

[0075] Figure 6 is a flowchart of a non-coded reconstruction bitstream data processing method and its method for inserting bit data segments into a computing device. Detailed Implementation

[0076] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments.

[0077] Example 1

[0078] A non-coded reconstruction bitstream data processing method and its computing device are applied to the receiving end of a communication terminal to parse example bitstream data frames conforming to the example data protocol, as shown in Figure 1, including the following steps:

[0079] S11. Load the non-coded protocol template file.

[0080] The non-coded protocol template file describes the bitstream data protocol in a formatted manner. In some embodiments, it can adopt multiple formats such as xml, ini, and json. In one specific embodiment, the bitstream data protocol is defined as follows:

[0081] This embodiment describes the bitstream data protocol using a JSON file format, including the field names, bit placeholder parameters, data type parameters, data operation parameters, display type parameters, and display supplementary parameters for fields 1 to 5 in the bitstream data frame. Bit placeholder parameters include the bit start position and the number of bits in the field; data operation parameters include the data resolution parameter and the data offset parameter; display supplementary parameters include the display suffix. The content within "para": followed by "[]" is the protocol content, listing the protocol content of each field in order, with each field represented by "{}" and fields separated by commas. Within "{}", "name" represents the field name, "startBit" represents the start position, "bitLength" represents the number of bits in the field, "coefficient" represents the resolution, "offset" represents the data offset, "type" represents the data type, "showType" represents the display type, and "suffix" represents the display suffix. See below:

[0082] In this embodiment, the bitstream data parsing processor loads the non-coded protocol template file and interprets it to obtain the processing parameters of each field.

[0083] S12. Read the received bitstream data frame into the buffer.

[0084] In this embodiment, the bitstream data parsing processor reads the bitstream data frames received by the receiving end into the data buffer. In a specific embodiment, the read bitstream data frames are as follows:

[0085] 0000001001000101000000111110100001010010110000000000000000111000100100000000000011111110000000

[0086] S13. Parse the bitstream data frame according to the parameter information of each field in the non-coded protocol template file, and process multiple fields in sequence.

[0087] In this embodiment, as shown in Figure 2, step S13 is as follows:

[0088] S131. Read the field name "frame number", read the bit start position, denoted as startBit(S) and the number of bits, denoted as length(L).

[0089] S132. Extract a bit data segment of length length from the data buffer, starting from the startBit bit.

[0090] As shown in Figure 3, S1321, calculate the starting byte of the field where the bit starts, denoted as byteNum(b). byteNum = startBit ÷ 8, and byteNum is an integer.

[0091] The starting position of the valid data in the field within the starting byte is denoted as startPosInByte(P), where startPosInByte = startBit - byteNum × 8.

[0092] Calculate the number of bytes remaining from the start position of the valid data within the starting byte to the end of that byte, denoted as headRem(h), headRem = 8 - startPosInByte.

[0093] Determine whether the bit data segment of this field spans multiple bytes, i.e., whether headRem is less than length.

[0094] If headRem≥length, the data field does not span bytes. Extract a bit segment of length length starting from startPosInByte within the byteNum byte to obtain the bit data segment of that field.

[0095] If headRem < length, then the data field spans bytes, and the following steps are performed:

[0096] Calculate the number of bits occupied by the data segment in the starting byte, denoted as L0 = headRem;

[0097] Calculate the number of complete bytes occupied by the data segment, denoted as L1, L1 = (length - L0) / 8, L1 is an integer; calculate the ending position of the last bit of the valid data in the incomplete byte occupied by the last valid data segment, denoted as L2, L2 = length - L0 - L1 * 8;

[0098] S1322. Extract a data segment of length L0 starting from the start position startPosInByte within the starting byte byteNum, and denote it as the starting segment.

[0099] S1323. Extract the bit content of L1 bytes starting from the first byte after the starting byte byteNum, and denote it as the intermediate segment.

[0100] S1324. Extract a bit segment of length L2 bits starting from the start bit of byteNum+L1+1 bytes, and denote it as the end segment.

[0101] S1325. Concatenate the start segment, middle segment, and end segment bit segments sequentially from left to right to obtain the bit data segment corresponding to the field.

[0102] S133. Based on the data type parameter, convert the extracted bit data segment into the basic value of the data type.

[0103] S134. Perform positive processing on the basic values ​​according to the data operation parameters to obtain the intermediate values ​​after data operation.

[0104] S135. Based on the data display type parameter, perform type conversion on the intermediate values ​​after data calculation, and convert them into display values ​​of the data display type.

[0105] S136. Based on the field name and supplementary display parameters, supplement the displayed values ​​with field names and prefix / suffix information to obtain the displayed content.

[0106] Step 13 is processed as follows in this specific embodiment:

[0107] (1) Process the first field.

[0108] (1.1) Read the first field of the protocol template in the buffer;

[0109] (1.2) Read the first field name "Frame Number";

[0110] (1.3) Read the first bit start position "0" and the number of bits "16";

[0111] (1.4) Extract a 16-bit data segment from the data buffer, starting from the 0th bit, which is 0000001001000101;

[0112] (1.5) Read the first field type "INT";

[0113] (1.6) Convert the data segment 0000 0010 0100 0101 to INT type, which is 581;

[0114] (1.7) Read data template display type is HEX;

[0115] (1.8) Convert the data obtained in step 1.6 into HEX format, 0x0245;

[0116] (1.9) Record the parsed content of the first field: "Frame number: 0245".

[0117] (2) Process the second field.

[0118] (2.1) Read the second field from the protocol template in the buffer;

[0119] (2.2) Read the second field name "height";

[0120] (2.3) Read the starting position of the second bit "16" and the number of bits "16";

[0121] (2.4) Starting from the 16th bit of the data in the data buffer, extract a 16-bit data segment of length, which is 0000001111101000;

[0122] (2.5) Read the second field type "INT";

[0123] (2.6) Convert the data segment 0000001111101000 to INT type, which is 1000;

[0124] (2.7) Read the resolution 1 and offset -1000 of the second field;

[0125] (2.8) Multiply the value obtained in (2.6) by the resolution and add the offset, 1000*1-1000=0;

[0126] (2.9) Read data template display type is DEC;

[0127] (2.10) Convert the data calculated in step (2.8) into DEC form, 0;

[0128] (2.11) Read data templates and display them with the suffix "m";

[0129] (2.12) Add a suffix to the data obtained in step (2.10), which is 0m;

[0130] (2.13) Record the parsed content of the second field: "Height: 0m".

[0131] (3) Process the third field.

[0132] (3.1) Read the third field from the protocol template in the buffer;

[0133] (3.2) Read the name of the third field as "longitude";

[0134] (3.3) Read the starting position "32" and the number of bits "25" of the third field;

[0135] (3.4) Extract a 25-bit data segment 010100101100000000000000 from the 32nd bit of the data in the data buffer;

[0136] (3.5) Find the third field with type "INT";

[0137] (3.6) Convert the data segment obtained in step (3.4) into INT type, 10846208;

[0138] (3.7) Read the resolution 0.0000107288360595703125 and offset 0 of the third field;

[0139] (3.8) Multiply the value obtained in step (3.6) by the resolution and add the offset, 10846208*0.0000107288360595703125+0=116.3671875;

[0140] (3.9) The data template display type is DOULBE;

[0141] (3.10) Convert the data obtained in step (3.8) into DOULBE form, 116.3671875;

[0142] (3.11) Read data templates and display them with the suffix "deg";

[0143] (3.12) Add a suffix to the data obtained in step (3.10): 116.3671875deg;

[0144] (3.13) Record the parsed content of the third field, “Longitude: 116.3671875deg”.

[0145] (4) Process the fourth field.

[0146] (4.1) Read the fourth field from the protocol template in the buffer;

[0147] (4.2) Read the name of the fourth field as "Latitude";

[0148] (4.3) Read the starting position "57" and the number of bits "24" of the fourth field;

[0149] (4.4) Extract a 24-bit data segment 00111000100100000000000 from the data buffer, starting from the 57th bit.

[0150] (4.5) Find the fourth field type "INT";

[0151] (4.6) Convert the data segment obtained in step (4.4) into INT type, 3706880;

[0152] (4.7) Read the resolution 0.0000107288360595703125 and offset 0 of the 4th field;

[0153] (4.8) Multiply the value obtained in step (4.6) by the resolution and add the offset, 3706880*0.0000107288360595703125+0=39.7705078125;

[0154] (4.9) The data template display type is DOULBE;

[0155] (4.10) Convert the data obtained in step (4.8) into DOULBE form, 39.7705078125;

[0156] (4.11) Read data templates and display them with the suffix "deg";

[0157] (4.12) Add the suffix 39.7705078125deg to the data obtained in step (4.10);

[0158] (4.13) Record the parsed content of the 4th field: "Latitude: 39.7705078125deg".

[0159] (5) Process the 5th field.

[0160] (5.1) Read the 5th field from the protocol template in the buffer;

[0161] (5.2) Read the name of the 5th field as "Device Identification Code";

[0162] (5.3) Read the starting position "81" and the number of bits "15" of the 5th field;

[0163] (5.4) Extract a 15-bit data segment 0111111 1000 0000 from the data buffer, starting from the 81st bit.

[0164] (5.5) Find the 5th field type "INT";

[0165] (5.6) Convert the data segment obtained in step (5.4) into INT type, 16320;

[0166] (5.7) The data template display type is HEX;

[0167] (5.8) Convert the data obtained in step (5.6) into HEX form, 3FC0;

[0168] (5.9) Record the parsed content of the 5th field: "Device Identification Code: 3FC0".

[0169] Step 14: Merge the parsed content.

[0170] In this embodiment, the parsed content is "Frame number: 0245; Altitude: 0m; Longitude: 116.367deg; Latitude: 39.7705deg; Device identification code: 3FC0".

[0171] A bitstream data information packaging processor employing the non-coded reconstruction bitstream data processing method provided by this invention is applied to the sending end of a communication terminal. It packages bitstream data frames conforming to an example data protocol based on user-submitted information, as shown in Figure 4, and includes the following steps:

[0172] S21. Load the non-coded protocol template file. In this embodiment, the example of the non-coded protocol template file is the same as in Embodiment 1. The bitstream data information packaging processor in this embodiment loads the non-coded protocol template file and interprets it to obtain the processing parameters of each field.

[0173] S22. Calculate the total bit length of the data packets in the non-coded protocol template file, generate a bit data frame buffer, and initialize it. In the example protocol of this embodiment, the total bit length of the data packets is 96, and a 12-byte buffer is generated.

[0174] S23. Import the data field content information entered by the user;

[0175] In this embodiment, the user input is as follows:

[0176] S24. Reverse process the user input field content according to the field parameter information in the non-coded protocol template file, generate bit data segments and insert them into the bit stream data packet, and process multiple fields in sequence.

[0177] In this embodiment, the steps for processing fields are as shown in Figure 5:

[0178] S241. Read the parameter information of a single field in the non-coded protocol template file to obtain the field name, bit placeholder parameter, data type parameter, data operation parameter, display type parameter, and display supplementary parameter.

[0179] S242. Based on the field name, extract the information content that matches the field name in the non-coded protocol template file from the user input field content.

[0180] S243. Based on the supplementary display parameters, extract the supplementary display parameters from the information provided by the user to obtain the display values.

[0181] S244. Perform reverse processing on the displayed values ​​according to the display type parameters to obtain the intermediate values ​​after data calculation.

[0182] S245. Perform reverse processing on the intermediate values ​​according to the data operation parameters to obtain the basic values.

[0183] S246. Based on the bit placeholder parameters, insert the basic values ​​into the bit data frame buffer in the form of bit fields, and process each field in turn.

[0184] As shown in Figure 6, S2461, calculate the starting byte of the field where the bit starts, denoted as byteNum(b), byteNum = startBit ÷ 8, and byteNum is an integer.

[0185] The starting position of the valid data in the calculated field within the starting byte is denoted as startPosInByte(P), where startPosInByte = startBit - byteNum * 8.

[0186] Calculate the number of bytes remaining from the start position of the valid data within the starting byte to the end of that byte, denoted as headRem(h) = 8 - startPosInByte.

[0187] Determine whether the bit data segment of this field spans multiple bytes, i.e., whether headRem is less than length.

[0188] If headRem≥length, then the data field does not span bytes, and a bit segment of length to the left of the basic numerical bit segment is inserted starting from the startPosInByte bit within the bit data frame buffer byteNum.

[0189] If headRem < length, then the data field spans bytes, and the following steps are performed:

[0190] S24621. Calculate the number of bits occupied by the data segment in the starting byte, denoted as L0 = headRem;

[0191] Calculate the number of complete bytes occupied by the data segment, denoted as L1, L1 = (length - L0) / 8, and round to the nearest integer;

[0192] The end position of the last bit of the valid data in the field within the incomplete byte occupied by the end of the valid data is denoted as L2, where L2 = length - L0 - L1 * 8;

[0193] S24622. Start inserting data from the starting position startPosInByte within the starting byte of the bit data frame buffer byteNum. The inserted content is a data segment of length L0 to the left of the basic value bit data segment.

[0194] S24623. Starting from the first byte after the first byte byteNum of the bit data frame buffer, insert a bit data segment of length L1×8, starting from the left L0+1 bit of the basic value bit segment, for a total of L1 bytes;

[0195] S24624. Starting from the start bit of byteNum+L1+1 in the bit data frame buffer, insert a bit segment of length L2 starting from L0+L1×8+1 on the left side of the basic value bit segment.

[0196] S247. Output the bit data packet with completed field filling. In this embodiment, the generated data packet is as follows:

[0197] 0000001001000101000000111110100001010010110000000000000000111000100100000000000011111110000000

[0198] The non-coded reconstructed bitstream data computing device includes at least a memory and a processor. The memory stores executable code and a non-coded data protocol template file. When the processor executes the executable code, it implements any one of the parsing processing method and / or information packaging processing method provided by this invention.

[0199] The above description is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any equivalent substitutions or modifications made by those skilled in the art within the scope of the technology disclosed in the present invention, based on the technical solution and inventive concept of the present invention, should be covered within the scope of protection of the present invention.

Claims

1. A method of processing bitstream data for non-coded reconstruction, characterized by: Step S1 involves receiving bitstream data frames and parsing them. Step S2 involves packaging and processing the data field content information input by the user. S1. Load the non-coded protocol template file, read the received bitstream data frame into the buffer, and then parse the bitstream data frame according to the field parameter information in the non-coded protocol template file and output data content information that is easy to display and apply. S2. Load the non-coded protocol template file and calculate the total bit length of the data packets in the non-coded protocol template file, generate a bit data frame buffer and initialize it; import the data field content information, reverse process the user input field content according to the field parameter information in the non-coded protocol template file to generate bit data segments and insert them into bit stream data packets, and then output the bit stream data packets for communication transmission; In steps S1 and S2, the non-coded protocol template is a specific description of the defined data content. The non-coded protocol template includes one or more of the following: field name, bit placeholder parameter, data type parameter, data operation parameter, display type parameter, and display supplementary parameter for each field in the bitstream data frame.

2. The method of claim 1, wherein: The bit placeholder parameters include the bit start position and the number of bits in the field; the data operation parameters include one or more of the data resolution parameters, data offset parameters, and exponentiation parameters; and the display supplementary parameters include one or more of the display prefix parameters and display suffix parameters.

3. The method of claim 1, wherein: The received bitstream data frames and the data field content information input by the user both conform to the example of the non-coded protocol template file.

4. The method of claim 2, wherein: Step S1 includes the following steps: S11. Load the non-coded protocol template file; S12. Read the received bitstream data frame into the buffer; S13. Parse the bitstream data frame according to the parameter information of each field in the non-coded protocol template file; S131. Read the single-field parameter information of the non-coded protocol template file to obtain the field name, the bit place parameter, the data type parameter, the data operation parameter, the display type parameter, and the display supplementary parameter; S132. Extract the bit data segment corresponding to the field from the bit stream data frame according to the bit placeholder parameter; S133. Convert the extracted bit data segment into the basic value of the data type parameter according to the data type parameter; S134. Perform forward processing on the basic value according to the data operation parameters to obtain the intermediate value after data operation; S135. Based on the data display type parameter, perform type conversion on the intermediate value of the data after calculation and convert it into a display value of the corresponding display type; S136. Based on the field name and the display supplementary parameters, supplement the display value with field name and prefix / suffix information to obtain the display content; S14. Output the data content information in a way that facilitates display and application.

5. The method of non- coded reconfigurable bitstream data processing according to claim 4, characterized in that: In step S13, when there are at least two fields, they are processed sequentially according to the field order.

6. The method of claim 4, wherein: Step S132 includes the following steps: S1321. Based on the bit start position S and the number of bits in the field L, obtain the number of remaining bytes h from the start position P to the end of the byte in the start byte of the field's valid data, and determine whether the bit data segment spans bytes. If not, calculate the starting byte of the field where the bit start position is located, and the starting position of the field's valid data within the byte of the starting byte; extract a bit data segment of the field's bit length starting from the starting position within the byte of the starting byte; If so, proceed to step S1322, which includes: S13221. Calculate the starting byte where the field starts, the starting position of the valid data of the field within the bytes of the starting byte, and the number of bits occupied by the data segment in the starting byte to obtain the number of complete bytes occupied by the data segment, the incomplete bytes occupied by the end of the valid data segment, and the ending position of the last bit of the valid data of the field within the incomplete bytes occupied by the end of the valid data segment. S13222. Extract the bit segment from the start position within the byte of the start byte to the end of the start byte, and use it as the start segment; S13223. Extract a data segment occupying several complete bytes from the first byte to the right of the starting byte, and use it as an intermediate segment; S13224. Extract the bit segment from the beginning of the incomplete byte occupied by the end of the valid data segment to the end position of the last bit of the valid data segment in the incomplete byte occupied by the end of the valid data segment, and use it as the end segment; S13225. The bit segments of the start segment, the middle segment and the end segment are concatenated sequentially from left to right to obtain the bit data segment corresponding to the field.

7. The method of non- coded reconfigurable bitstream data processing according to claim 6, characterized in that: In step S1321, the starting byte b of the field where the bit starts is located is: b = integer (S ÷ 8); The starting position P of the valid data in the field within the starting byte is: P = Sb × 8; The number of bytes h remaining from the start position to the end of the byte within the start byte of the valid data is: h = 8 - P; The method for determining whether the bit data segment spans multiple bytes is: determine whether h is less than L; When h ≥ L, the data field does not span bytes; When h < L, the data field spans bytes; In step S13221, the number of bits occupied in the starting byte of the data segment is L0, L0 = h, the number of complete bytes occupied by the data segment is L1, L1 = ((L-L0) / 8)), and the end position of the last bit of the valid data in the incomplete byte occupied by the end segment of the valid data is L2, L2 = L-L0-L1*8; In step S13222, a data segment with a length of L0 is extracted from the starting byte b of the starting byte of the field where the bit start position is located, starting from the starting position P within the starting byte of the starting byte, which is the starting segment; In step S13223, the bit content of L1 bytes, starting from the first byte after the first byte b of the field where the bit start position is located, is extracted as the intermediate segment; In step S13224, a bit segment of length L2 bits, starting from the start bit of byte b+L1+1, is extracted as the end segment.

8. The method of claim 1, wherein: Step S2 includes the following steps: S21. Load the non-coded protocol template file; S22. Calculate the total bit length of the data packets in the non-coded protocol template file, generate the bit data frame buffer and initialize it; S23. Import the data field content input by the user; S24. Reverse process the data field content information input by the user according to the field parameter information in the non-coded protocol template file, and generate the bit data segment insertion bit stream data packet; S25. Output the bit stream data packet used for communication transmission; Step S24 includes the following steps: S241. Read the single-field parameter information of the non-coded protocol template file to obtain the field name, bit placeholder parameter, data type parameter, data operation parameter, display type parameter and display supplementary parameter of the single field; S242. Extract information content that matches the field name in the non-coded protocol template file from the data field content input by the user based on the field name; S243. Based on the display supplementary parameters, extract the display supplementary parameters from the data field content input by the user to obtain the display value; S244. Perform reverse processing on the display value according to the display type parameter to obtain the intermediate value after data calculation; S245. The intermediate value is processed in reverse according to the data operation parameters to obtain the basic value; S246. Insert the basic value into the bit data frame buffer in the form of a bit field according to the bit placeholder parameter. S247. Output the bit data packet with the fields filled.

9. The method of non- coded reconstructed bitstream data processing according to claim 8, wherein: In step S246, the specific steps for inserting the bit data segment include: S2461. Calculate the bit length from the start position to the end of the byte within the starting byte of the valid data in the starting byte based on the bit start position and the number of bits in the bit placeholder parameter, and determine whether the bit data segment spans bytes; If not, calculate the starting byte of the field where the bit start position is located, and the starting position of the valid data of the field within the byte of the starting byte; insert a bit data segment of the corresponding bit length starting from the starting position within the byte of the starting byte; If so, proceed to step S2462, which includes: S24621. Calculate the starting byte where the field starts, the starting position of the valid data of the field within the byte of the starting byte, and the starting bit length of the starting segment from the starting position within the byte to the end of the starting byte; calculate the number of complete bytes occupied by the data segment, the bit length of the intermediate segment corresponding to the number of complete bytes, the incomplete bytes occupied by the end segment of the valid data, the ending position of the last bit of the valid data of the field in the incomplete byte occupied by the end segment of the valid data, and the bit length of the ending segment; S24622. Insert bit data of length to the left of the starting segment of valid data in the field, starting from the starting position within the byte of the starting byte; S24623. Insert bit data of the middle segment length starting from the first byte to the right of the starting byte, starting from the first bit after the starting segment bit length of the field valid data; S24624. Insert bit data of the length of the rightmost end segment of the valid data into the position from the leftmost bit of the incomplete byte occupied by the end segment of the valid data to the end position of the incomplete byte occupied by the end segment of the valid data.

10. A non-coded reconfigurable bit stream data computing device according to any one of claims 1 to 9, characterized in that: It includes a bitstream data parsing processor that parses bitstream data frames and a bitstream data information packaging processor that packages bitstream data frames based on user-submitted information; The bitstream data parsing processor uses the method in step S1 to receive bitstream data frames for data parsing, and the bitstream data information packaging processor uses the method in step S2 to package and process the data field content information input by the user and output bit data packets.

Images