A method for implementing correctness of data segmentation mechanism in airborne network communication ports

Abstract

The present invention provides a method for processing the correctness of the data segmentation mechanism of an airborne network communication port. According to the fault type and mode of the airborne network communication port when segmenting data, a segmentation fault detection state machine is designed, and the correctness of the data segmentation mechanism of the airborne network communication port is processed according to the segmentation fault detection state machine. The above method uses the segmentation fault detection state machine to judge the correctness of the data segmentation mechanism, ensures that incorrect and complete data will not be submitted to the data receiving end, and avoids the data receiving end from receiving erroneous data.

Description

Technical Field

[0001] The invention relates to the technical field of computer communication, in particular to a processing method for realizing correctness of a data segmentation mechanism of an airborne network communication port. Background Art

[0002] Airborne network communication ports have the characteristics of high bandwidth, high reliability, low latency and flexible expansion, and are widely used in aircraft avionics systems.

[0003] During data transmission, the airborne network communication port divides the data block to be sent into multiple payloads in a sequence according to the segmentation mechanism, and puts each payload into a frame, completing the transmission of the large data block through sequence transmission. However, when the airborne network communication port does not correctly implement the segmentation mechanism, it will cause data transmission anomalies and thus cause the problem of data not being received normally.

[0004] Therefore, a method is required to automatically detect and process the correctness of the execution of the data segmentation mechanism when the airborne network communication port segments the data, so as to ensure the correctness and completeness of the data transmission and processing between the airborne network ports. Summary of the invention

[0005] When the airborne network communication port segments data, in order to avoid abnormal data transmission and failure to receive data normally due to errors in the execution of the data segmentation mechanism, and thereby ensure the correctness of the execution of the data segmentation mechanism, the present invention designs a processing method for realizing the correctness of the data segmentation mechanism of the airborne network communication port.

[0006] The technical solution to achieve the purpose of the invention is as follows: a method for processing the correctness of the data segmentation mechanism of an airborne network communication port, designing a segmentation fault detection state machine according to the fault type and mode of the airborne network communication port when segmenting data, and processing the correctness of the data segmentation mechanism of the airborne network communication port according to the segmentation fault detection state machine;

[0007] The method for achieving correctness of the data segmentation mechanism includes the following steps:

[0008] S1, the airborne network communication port obtains link synchronization information;

[0009] S2, the segment fault detection state machine detects whether the data receiving end is waiting to receive a SOFi3 primitive or a loss of synchronization from the airborne network communication link;

[0010] S21, if SOFi3 primitive is detected, go to step S3;

[0011] S22, if out-of-synchronization is detected, the segment fault detection state machine returns to the initial state;

[0012] S23, if none of them are detected, continue to detect;

[0013] S3, the airborne network communication port obtains and parses the length information of the message to be sent, and obtains multiple field information;

[0014] S4, the data receiving end receives the data;

[0015] S41, when the airborne network communication port detects the first error message, stops receiving data, returns to step S2, and waits again for the data frame output in the next sequence;

[0016] S42, when the second error message is detected, enter and execute the following step S5;

[0017] S43, when the third error message is detected, enter and execute step S3 or S1;

[0018] S5. The airborne network communication port detects the fill word of the single sequence with offset.

[0019] In one embodiment, in the above step S3, the field information includes a relative offset, a frame size, a SEQ_ID, a SEQ_CNT, an end frame, and a filler word in the airborne network frame header.

[0020] In one embodiment, in the above step S41, the first error message includes any one of an erroneous data frame, a non-continuous frame error, a non-same frame error, a message length error, a single-sequence single-frame no offset error, a single-sequence multiple-frame no offset error, a single-frame offset 1 type fill word error, a single-frame offset 2 type fill word error, a single-frame offset 3 type fill word error, multiple frames offset 1 type fill word error, multiple frames offset 2 type fill word error, and multiple frames offset 3 type fill word error.

[0021] In one embodiment, in the above step S42, the second error message includes any one of a single-sequence single-frame offset error and a single-sequence multiple-frame offset error.

[0022] In one embodiment, in the above step S5, the onboard network communication port detects the fill word with offset in the single sequence, including:

[0023] S51, the airborne network communication port detects that there are type 1 filling words, type 2 filling words and type 3 filling words when a single sequence single frame has an offset;

[0024] S52. The airborne network communication port detects the presence of type 1 filling words, type 2 filling words, and type 3 filling words when a single sequence multiple frames have an offset.

[0025] In one embodiment, in the above step S43, the third error message includes any one of a SOFi3 primitive error or an airborne network communication link out-of-sync error;

[0026] When it is detected that an error in receiving the SOFi3 primitive is detected, step S3 is entered and executed;

[0027] When an airborne network communication link out-of-synchronization error is detected, the process enters and executes step S1.

[0028] Compared with the prior art, the beneficial effects of the present invention are: the processing method for realizing the correctness of the data segmentation mechanism of the airborne network communication port designed by the present invention can use the segmentation fault detection state machine to judge the correctness of the data segmentation mechanism implementation, ensuring that incorrect and complete data will not be submitted to the data receiving end, thereby avoiding the data receiving end from receiving erroneous data. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0030] Figure 1 The present invention is a flowchart of a method for implementing correctness of an airborne network communication port data segmentation mechanism. DETAILED DESCRIPTION

[0031] The present invention will be further described below in conjunction with specific embodiments, and the advantages and features of the present invention will become clearer as the description proceeds. However, these embodiments are exemplary only and do not constitute any limitation to the scope of the present invention. It should be understood by those skilled in the art that the details and forms of the technical solution of the present invention may be modified or replaced without departing from the spirit and scope of the present invention, but these modifications and replacements all fall within the scope of protection of the present invention.

[0032] In the description of this embodiment, it should be understood that the terms "center", "longitudinal", "lateral", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside" and "outside" etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the invention.

[0033] In addition, the terms "first", "second", "third", etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first", "second", etc. may explicitly or implicitly include one or more of the features. In the description of the present invention, unless otherwise specified, "plurality" means two or more.

[0034] This specific embodiment discloses a method for processing the correctness of the data segmentation mechanism of an airborne network communication port. According to the fault type and mode of the airborne network communication port when segmenting data, a segmentation fault detection state machine is designed, and the correctness of the data segmentation mechanism of the airborne network communication port is processed based on the segmentation fault detection state machine.

[0035] See also Figure 1 As shown, the processing method for achieving correctness of the data segmentation mechanism includes the following steps:

[0036] S1, the airborne network communication port obtains link synchronization information;

[0037] S2, the segment fault detection state machine detects whether the data receiving end is waiting to receive a SOFi3 primitive or a loss of synchronization from the airborne network communication link;

[0038] S21, if SOFi3 primitive is detected, go to step S3;

[0039] S22, if out-of-synchronization is detected, the segment fault detection state machine returns to the initial state;

[0040] S23, if none of them are detected, continue to detect;

[0041] S3, the airborne network communication port obtains and parses the length information of the message to be sent, and obtains multiple field information;

[0042] S4, the data receiving end receives the data;

[0043] S41, when the airborne network communication port detects the first error message, stops receiving data, returns to step S2, and waits again for the data frame output in the next sequence;

[0044] S42, when the second error message is detected, enter and execute the following step S5;

[0045] S43, when the third error message is detected, enter and execute step S3 or S1;

[0046] S5. The airborne network communication port detects the fill word of the single sequence with offset.

[0047] In one embodiment, in the above step S3, the field information includes a relative offset, a frame size, a SEQ_ID, a SEQ_CNT, an end frame, a filler word, etc. in the airborne network frame header.

[0048] In one embodiment, in the above step S41, the first error message includes any one of an erroneous data frame, a non-continuous frame error, a non-same frame error, a message length error, a single-sequence single-frame no offset error, a single-sequence multiple-frame no offset error, a single-frame offset 1 type fill word error, a single-frame offset 2 type fill word error, a single-frame offset 3 type fill word error, multiple frames offset 1 type fill word error, multiple frames offset 2 type fill word error, and multiple frames offset 3 type fill word error.

[0049] In one embodiment, in the above step S42, the second error message includes any one of a single-sequence single-frame offset error and a single-sequence multiple-frame offset error.

[0050] In one embodiment, in the above step S5, the onboard network communication port detects the fill word with offset in the single sequence, including:

[0051] S51, the airborne network communication port detects that there are type 1 filling words, type 2 filling words and type 3 filling words when a single sequence single frame has an offset;

[0052] S52. The airborne network communication port detects the presence of type 1 filling words, type 2 filling words, and type 3 filling words when a single sequence multiple frames have an offset.

[0053] In one embodiment, in the above step S43, the third error message includes any one of a SOFi3 primitive error or an airborne network communication link out-of-sync error;

[0054] When it is detected that an error in receiving the SOFi3 primitive is detected, step S3 is entered and executed;

[0055] When an airborne network communication link out-of-synchronization error is detected, the process enters and executes step S1.

[0056] The above method can automatically detect and process the correctness of the execution of the data segmentation mechanism when the airborne network communication port segments the data. By defining the detection and processing mechanism for the correctness of the execution of the data segmentation mechanism by the airborne network communication port, according to the characteristics and application modes of airborne network data segmentation faults (including frame errors, non-continuous frame errors, non-same frame errors, message length errors, single-sequence single-frame no offset errors, single-sequence multiple-frame no offset errors, single-sequence single-frame with offset errors, single-sequence multiple-frame no offset errors, etc.), an independent segmentation fault detection state machine and corresponding control logic are designed. The control logic automatically detects and processes the correctness of the execution of the data segmentation mechanism under the control of the state machine.

[0057] The following uses a specific example to explain in detail the operation logic of the segmentation fault detection state machine. The segmentation fault detection state machine (hereinafter referred to as the state machine) has a total of 13 states. When the data segmentation mechanism performs automatic detection and processing of execution correctness, the process of jumping between the states is as follows:

[0058] 1. State 0 This state is the initial state of the state machine.

[0059] When the power is initially turned on or reset, the state machine enters this state. In this state, the airborne network communication port obtains link synchronization information. If the Active state is reached, the state machine enters state 1; otherwise, it stays in state 0.

[0060] 2. State 1: This state is the first frame judgment state.

[0061] In this state, the receiving port waits for the SOFi3 primitive to be detected on the link. If the SOFi3 primitive is detected, the state machine enters state 2; if loss of synchronization is detected, the state machine returns to state 0; otherwise, the state machine stays in state 1.

[0062] 3. State 2: This state is the normal frame data reception state.

[0063] In this state, the airborne network communication port obtains the length information of the message to be sent according to the configuration file information, and parses the field information such as relative offset, frame size, SEQ_ID, SEQ_CNT, end frame, and padding in the airborne network frame header. During the normal data reception process, if the airborne network communication port detects an error frame, the state machine enters state 3; if the airborne network communication port detects a non-continuous frame error, the state machine enters state 4; if the airborne network communication port detects a non-same frame error, the state machine enters state 5; if the airborne network communication port detects a message length error, the state machine enters state 6; if the airborne network communication port detects a single-sequence single-frame without offset error, the state machine enters state 7; if the airborne network communication port detects a single-sequence multiple-frame without offset error, the state machine enters state 8; if the airborne network communication port detects a single-sequence single-frame with offset error, the state machine enters state 9; if the airborne network communication port detects a single-sequence multiple-frame with offset error, the state machine enters state 13; if the receiving end receives the SOFi3 primitive, the state machine returns to state 1; if the airborne network communication link is detected to be out of synchronization, the state machine returns to state 0.

[0064] 4. State 3: This state is when the onboard network communication port detects an error frame.

[0065] In this state, when the airborne network communication port detects that the data frame has an over-length error, an over-short error, an EOF missing error, a CRC check error, a consistency error, an 8 / 10B encoding error, and an invalid MsgID error, it stops receiving the airborne network data frame, reports the detection of the error data frame, and the state machine returns to state 1, waiting for the arrival of the next data frame in the sequence again.

[0066] 5. State 4: This state is when a non-continuous frame error is detected.

[0067] In this state, if the airborne network communication port detects that the transmission message length is greater than the maximum frame length of a single frame, that is, the current transmission is single-sequence multi-frame, and the SEQ_CNT values ​​of two adjacent frames in the current sequence are not continuous, then the reception of airborne network data frames is stopped, and a non-continuous frame error is reported. The state machine jumps to state 1 and waits for the arrival of the data frame in the next sequence again.

[0068] 6. State 5: This state is when the onboard network communication port detects a non-synchronous frame error.

[0069] In this state, if the airborne network communication port detects that the transmission message length is greater than the maximum frame length of a single frame, that is, the current transmission is single-sequence multi-frame, and the SEQ_ID values ​​of two adjacent frames in the current sequence are inconsistent, then the reception of airborne network data frames is stopped, and a non-same-frame error is reported. The state machine jumps to state 1 and waits for the arrival of the data frame in the next sequence again.

[0070] 7. State 6: This state is when the airborne network communication port detects a message length error.

[0071] In this state, if the airborne network communication port detects that the message length value corresponding to the message data payload length field in the ASM message header is inconsistent with the actual message length defined in the configuration file, it stops receiving the airborne network data frame, reports the detected message length error, and the state machine jumps to state 1, waiting for the arrival of the data frame in the next sequence again.

[0072] 8. State 7: This state is when the airborne network communication port detects a single sequence single frame with no offset error.

[0073] In this state, if the airborne network communication port detects that the third bit (relative offset bit) of the airborne network frame header F_CTL field is not 0, the single frame length is incorrect, or the frame content is incorrect, it stops receiving the airborne network data frame, reports the detection of a single-sequence single-frame no offset error, and the state machine jumps to state 1, waiting for the arrival of the data frame in the next sequence again.

[0074] 9. State 8: This state is when the airborne network communication port detects a single sequence multi-frame no offset error.

[0075] In this state, if the airborne network communication port detects that the third bit (relative offset bit) of the airborne network frame header F_CTL field is not 0, the message length is incorrect, the frame content is incorrect, SEQ_CNT is not incremented by 1 in sequence, the non-first frame frame delimiter is not SOFn3, or the non-last frame frame delimiter is not EOFt, then it stops receiving airborne network data frames, reports the detection of a single-sequence multi-frame no offset error, and the state machine jumps to state 1, waiting for the arrival of the data frame in the next sequence again.

[0076] 10. State 9: This state is when the airborne network communication port detects a single sequence single frame with an offset error.

[0077] In this state, if the airborne network communication port detects that a single frame has a type 1 offset fill word, the state machine enters state 10; if the airborne network communication port detects that a single frame has a type 2 offset fill word, the state machine enters state 11; if the airborne network communication port detects that a single frame has a type 3 offset fill word, the state machine enters state 12;

[0078] 11. State 10: This state is when the airborne network communication port detects that a single frame has an offset type 1 fill word.

[0079] In this state, the frame length Frame_size is between 0 and 2112 bytes and Frame_size%4=1. If the airborne network communication port detects that the sequence does not contain 1 SOFi3 primitive, the fill word contained in the data valid field is not 1 byte, the 19th bit (sequence end bit) of the airborne network frame header F_CTL field is not 1, or the 0th and 1st bits (fill byte bits) of the airborne network frame header F_CTL field are not 01b, then the airborne network data frame is stopped from being received, and a single frame offset 1 fill word error is detected. The state machine jumps to state 1 and waits for the arrival of the data frame in the next sequence again.

[0080] 12. State 11: This state is when the airborne network communication port detects that a single frame has offset 2 types of fill words.

[0081] In this state, the frame length Frame_size is between 0 and 2112 bytes and Frame_size%4=2. If the airborne network communication port detects that the sequence does not contain 1 SOFi3 primitive, the padding word contained in the data valid field is not 2 bytes, the 19th bit (sequence end bit) of the airborne network frame header F_CTL field is not 1, or the 0th and 1st bits (padding byte bits) of the airborne network frame header F_CTL field are not 10b, then the airborne network data frame is stopped from being received, and a report is issued that a single frame has an offset 2 type of padding word error, and the state machine jumps to state 1, waiting for the arrival of the data frame in the next sequence again.

[0082] 13. State 12: This state is when the airborne network communication port detects that a single frame has offset 3 types of fill words.

[0083] In this state, the frame length Frame_size is between 0 and 2112 bytes and Frame_size%4=3. If the airborne network communication port detects that the sequence does not contain 1 SOFi3 primitive, the padding word contained in the data valid field is not 3 bytes, the 19th bit (sequence end bit) of the airborne network frame header F_CTL field is not 1, or the 0th and 1st bits (padding byte bits) of the airborne network frame header F_CTL field are not 11b, then the airborne network data frame is stopped from being received, and a report is issued that a single frame has an offset 2 type of padding word error, and the state machine jumps to state 1, waiting for the arrival of the data frame in the next sequence again.

[0084] 14. State 13: This state is when the airborne network communication port detects a single sequence multi-frame offset error.

[0085] In this state, if the onboard network communication port detects that multiple frames have offset type 1 filler words, the state machine enters state 14; if the onboard network communication port detects that multiple frames have offset type 2 filler words, the state machine enters state 15; if the onboard network communication port detects that multiple frames have offset type 3 filler words, the state machine enters state 16.

[0086] 15. State 14: This state is when the airborne network communication port detects that multiple frames have offset 1 type of fill words.

[0087] In this state, the length of the entire message is greater than the maximum frame length, and the length of the last data frame after segmentation Frame_size%4=1. If the airborne network communication port detects that the first frame in the sequence is not a SOFi3 primitive, the last frame is not an EOFt3 data frame, the padding contained in the valid field of the last frame data is not 1 byte, the 19th bit (sequence end bit) of the airborne network frame header F_CTL field is not 1, or the 0th and 1st bits (padding byte bits) of the airborne network frame header F_CTL field are not 01b, then the airborne network data frame is stopped from being received, and a type 1 padding error is reported that multiple frames have offset. The state machine jumps to state 1 and waits for the arrival of the data frame in the next sequence again.

[0088] 16. State 15: This state is when the airborne network communication port detects that multiple frames have offset 2 type fill words.

[0089] In this state, the length of the entire message is greater than the maximum frame length, and the length of the last data frame after segmentation Frame_size%4=2. If the airborne network communication port detects that the first frame in the sequence is not a SOFi3 primitive, the last frame is not an EOFt3 data frame, the padding contained in the valid field of the last frame data is not 2 bytes, the 19th bit (sequence end bit) of the airborne network frame header F_CTL field is not 1, or the 0th and 1st bits (padding byte bits) of the airborne network frame header F_CTL field are not 10b, then the reception of airborne network data frames is stopped, and a report is issued that a type 2 padding error has been detected in multiple frames with offsets. The state machine jumps to state 1 and waits for the arrival of the data frame in the next sequence again.

[0090] 17. State 16: This state is when the airborne network communication port detects that multiple frames have offset 3 types of fill words.

[0091] In this state, the length of the entire message is greater than the maximum frame length, and the length of the last data frame after segmentation Frame_size%4=3. If the airborne network communication port detects that the first frame in the sequence is not a SOFi3 primitive, the last frame is not an EOFt3 data frame, the padding contained in the valid field of the last frame data is not 3 bytes, the 19th bit (sequence end bit) of the airborne network frame header F_CTL field is not 1, or the 0th and 1st bits (padding byte bits) of the airborne network frame header F_CTL field are not 11b, then the reception of airborne network data frames is stopped, and a report is issued that a multi-frame offset 3 type padding error has been detected. The state machine jumps to state 1 and waits for the arrival of the next data frame in the sequence again.

[0092] The control of the segment fault detection state machine is clear and applicable to the design of various airborne network interfaces and test equipment, and can ensure the correctness and integrity of the data frame at the data receiving end.

[0093] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

[0094] In addition, although this specification is described according to implementation modes, not every implementation mode contains only one independent technical solution. This description of the specification is only for the sake of clarity. Those skilled in the art should regard the specification as a whole. The technical solutions in each embodiment can also be appropriately combined to form other implementation modes that can be understood by those skilled in the art.

Claims

1. A method for processing the correctness of the data segmentation mechanism of an airborne network communication port, characterized in that: According to the fault type and mode of the airborne network communication port when segmenting data, a segmentation fault detection state machine is designed, and the correctness of the implementation of the airborne network communication port data segmentation mechanism is processed according to the segmentation fault detection state machine; The correctness of the data segmentation mechanism is handled by the following steps: S1, the airborne network communication port obtains link synchronization information; S2, the segment fault detection state machine detects whether the data receiving end is waiting to receive a SOFi3 primitive or a loss of synchronization from the airborne network communication link; S21, if SOFi3 primitive is detected, go to step S3; S22, if out-of-synchronization is detected, the segment fault detection state machine returns to the initial state; S23, if none of them are detected, continue to detect; S3, the airborne network communication port obtains and parses the length information of the message to be sent, and obtains multiple field information, wherein the field information includes the relative offset, frame size, SEQ_ID, SEQ_CNT, end frame, and padding in the airborne network frame header; S4, the data receiving end receives the data; S41. When the airborne network communication port detects a first error message, it stops receiving data, returns to step S2, and waits again for the data frame output in the next sequence, wherein the first error message includes any one of an error data frame, a non-continuous frame error, a non-same frame error, a message length error, a single-sequence single-frame no offset error, a single-sequence multiple-frame no offset error, a single-frame offset 1 type fill word error, a single-frame offset 2 type fill word error, a single-frame offset 3 type fill word error, a multiple-frame offset 1 type fill word error, a multiple-frame offset 2 type fill word error, and a multiple-frame offset 3 type fill word error; S42, when a second error message is detected, entering and executing the following step S5, wherein the second error message includes any one of a single sequence single frame offset error and a single sequence multiple frames offset error; S43, when a third error message is detected, entering and executing step S3 or S1, the third error message includes any one of a SOFi3 primitive reception error and an airborne network communication link loss of synchronization error; S5. The airborne network communication port detects the fill word of the single sequence with offset.

2. The method for processing the correctness of the airborne network communication port data segmentation mechanism according to claim 1, characterized in that: In step S5, the onboard network communication port detects the filling word of the single sequence having an offset, including: S51, the airborne network communication port detects that there are type 1 filling words, type 2 filling words and type 3 filling words when a single sequence single frame has an offset; S52. The airborne network communication port detects the presence of type 1 filling words, type 2 filling words, and type 3 filling words when a single sequence multiple frames are offset.

3. The method for processing the correctness of the airborne network communication port data segmentation mechanism according to claim 1, characterized in that: When it is detected that an error in receiving the SOFi3 primitive is detected, step S3 is entered and executed; When an airborne network communication link out-of-synchronization error is detected, the process enters and executes step S1.

Images