CN106788908B - Checking system and method for AFDX (avionics full Duplex switched Ethernet) bus messages - Google Patents
Checking system and method for AFDX (avionics full Duplex switched Ethernet) bus messages Download PDFInfo
- Publication number
- CN106788908B CN106788908B CN201710197466.9A CN201710197466A CN106788908B CN 106788908 B CN106788908 B CN 106788908B CN 201710197466 A CN201710197466 A CN 201710197466A CN 106788908 B CN106788908 B CN 106788908B
- Authority
- CN
- China
- Prior art keywords
- data
- message
- piece
- verification
- serial number
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 28
- 238000012795 verification Methods 0.000 claims description 40
- 230000005540 biological transmission Effects 0.000 abstract description 9
- 230000002159 abnormal effect Effects 0.000 description 10
- 230000006854 communication Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 3
- 238000013524 data verification Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0056—Systems characterized by the type of code used
- H04L1/0061—Error detection codes
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Small-Scale Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The application discloses checking system and method of AFDX bus message, wherein, the sending end of the checking system of AFDX bus message distributes a data sequence number in the payload of every data of message to mark the production order of every kind of data self, the receiving end of the checking system of AFDX bus message is according to the data sequence number is right every data in the message is checked to this judges whether this data self order is normal, thereby has realized carrying out the purpose of checking to the data order integrality of every message, avoids appearing the data in the message and keeps the order normal in the transmission process, but leads to the condition that the message data order that the receiving end received is unusual because of self data sequence mistake.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a system and a method for checking an AFDX bus message.
Background
In the communication process of the avionics network, some data or frames often have some correlation, and the sequence integrity of the received data needs to be maintained. AFDX (avinics Full Duplex Switched Ethernet) communication protocol requires data to maintain sequence integrity in a given virtual link, and for this reason, AFDX protocol proposes a communication rule for checking the data sequence in the virtual link: the sending end distributes an SN (Sequence Number) to each piece of data sent on a virtual link through a 'scheduler', the SN of each piece of data is located at the tail of the piece of data, the SN is circularly increased by 1 from 1 to 255, and 0 represents the first piece of data sent after the equipment at the sending end is reset. After receiving data of one virtual link, the receiving end compares the SN with the SN of the previous data received from the virtual link, and discards the currently received data when the difference value of the SNs of the adjacent data exceeds an effective window so as to ensure the sequence integrity of the data.
However, in the prior art, in the process of checking the sequence integrity of data, SNs are allocated in units of virtual links, and can only check the data sequence on one virtual link, but cannot check the sequence of the data of each message, and there is a possibility that the data in the message keeps normal sequence during transmission, but the sequence of the message data received by the receiving end is abnormal.
Disclosure of Invention
In order to solve the technical problem, the invention provides a system and a method for checking AFDX bus messages, so as to check the sequence of data of each message, and avoid the situation that the data in the messages keep normal sequence in the transmission process, but the sequence of the message data received by a receiving end is abnormal.
In order to achieve the technical purpose, the embodiment of the invention provides the following technical scheme:
a system for validating AFDX bus messages, comprising: a sending end and a receiving end; wherein,
the sending end is used for generating a message, wherein the message at least comprises a variety of data, and the variety of data at least comprises one piece of data;
distributing a data sequence number for each piece of data in the message, wherein the data sequence numbers of the same kind of data are increased progressively according to a preset step length;
the receiving end is used for receiving the message;
checking each piece of data in the message;
if the data in the message passes the verification, receiving the data passing the verification, and taking a data serial number of the data passing the verification as a comparison serial number of the data of the kind to which the data passing the verification belongs;
if the data in the message is not verified, discarding the data which is not verified, and taking the data sequence number of the data which is not verified as the comparison sequence number of the data of the kind to which the data which is not verified belongs.
Optionally, the allocating a data sequence number to each piece of data in the message specifically includes:
distributing a data sequence number to each piece of data in the message according to the generation sequence of the data; wherein the data sequence number is filled in a header of a payload of each piece of data.
Optionally, the verifying each piece of data in the message specifically includes:
checking each piece of data in the message according to the receiving sequence of the data;
the checking process comprises the following steps: and judging whether the difference value of the data serial number of the data and the comparison serial number of the data of the type to which the data belongs is smaller than an effective threshold value, if so, the data passes the verification, and if not, the data does not pass the verification.
Optionally, the effective threshold is greater than or equal to 1;
the size of the data sequence number is greater than or equal to 2 bytes.
A checking method of AFDX bus message is applied to a sending end; the checking method of the AFDX bus message comprises the following steps:
generating a message, wherein the message at least comprises a variety of data, and the variety of data at least comprises a piece of data;
and distributing a data sequence number for each piece of data in the message, wherein the data sequence numbers of the same kind of data are increased by a preset step length.
Optionally, the allocating a data sequence number to each piece of data in the message specifically includes:
distributing a data sequence number to each piece of data in the message according to the generation sequence of the data; wherein the data sequence number is filled in a header of a payload of each piece of data.
Optionally, the size of the data sequence number is greater than or equal to 2 bytes.
A method for checking AFDX bus message is applied to a receiving end, and comprises the following steps:
receiving a message sent by a sending end, wherein the message at least comprises a variety of data, and the variety of data at least comprises one piece of data;
checking each piece of data in the message;
if the data in the message passes the verification, receiving the data passing the verification, and taking a data serial number of the data passing the verification as a comparison serial number of the data of the kind to which the data passing the verification belongs;
if the data in the message is not verified, discarding the data which is not verified, and taking the data sequence number of the data which is not verified as the comparison sequence number of the data of the kind to which the data which is not verified belongs.
Optionally, the verifying each piece of data in the message specifically includes:
checking each piece of data in the message according to the receiving sequence of the data;
the checking process comprises the following steps: and judging whether the difference value of the data serial number of the data and the comparison serial number of the data of the type to which the data belongs is smaller than an effective threshold value, if so, the data passes the verification, and if not, the data does not pass the verification.
Optionally, the effective threshold is greater than or equal to 1.
It can be seen from the foregoing technical solutions that the embodiments of the present invention provide a system and a method for checking AFDX bus messages, wherein a sending end of the checking system for AFDX bus messages allocates a data sequence number in an effective load of each piece of data of a message to mark a generation sequence of each piece of data itself, and a receiving end of the checking system for AFDX bus messages checks each piece of data in the message according to the data sequence number to determine whether the sequence of the piece of data is normal, so as to achieve an objective of checking the integrity of the data sequence of each piece of message, and avoid a situation that the data in the message keeps normal sequence during a transmission process, but the sequence of the message data received by the receiving end is abnormal due to an error sequence of the data of the receiving end.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a schematic diagram of a system for checking AFDX bus messages according to an embodiment of the present application;
FIGS. 2 and 3 are schematic diagrams illustrating the format structure of AFDX bus message data in the prior art;
fig. 4 and fig. 5 are schematic diagrams illustrating format structures of AFDX bus message data according to an embodiment of the present application;
fig. 6 is a flowchart illustrating a method for checking an AFDX bus message according to an embodiment of the present application;
fig. 7 is a flowchart illustrating a method for checking AFDX bus messages according to another embodiment of the present application;
fig. 8 is a flowchart illustrating a method for checking AFDX bus messages according to another embodiment of the present application;
fig. 9 is a schematic flow chart of a data verification process according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
An embodiment of the present application provides a system for checking an AFDX bus message, as shown in fig. 1, including: a sending end and a receiving end; wherein,
the sending end is used for generating a message, wherein the message at least comprises a variety of data, and the variety of data at least comprises one piece of data;
distributing a data sequence number for each piece of data in the message, wherein the data sequence numbers of the same kind of data are increased progressively according to a preset step length;
the receiving end is used for receiving the message;
checking each piece of data in the message;
if the data in the message passes the verification, receiving the data passing the verification, and taking a data serial number of the data passing the verification as a comparison serial number of the data of the kind to which the data passing the verification belongs;
if the data in the message is not verified, discarding the data which is not verified, and taking the data sequence number of the data which is not verified as the comparison sequence number of the data of the kind to which the data which is not verified belongs.
It should be noted that the message generated by the sending end generally includes at least one kind of data, each kind of data carries different information, and the information may be flight altitude, flight speed, or the like. In this embodiment, the data sequence number of each type of data is incremented by a preset step, for example, if the data sequence number of the current data carrying the flight altitude is 1, the data sequence number allocated by the sending end for the next data carrying the flight altitude is 2.
The data format in the AFDX bus message in the prior art is shown in fig. 2 and fig. 3, where fig. 2 shows the data format of the minimum Ethernet frame length in the prior art, which includes: preamble (Preamble, 7bytes), Frame header Delimiter (Start Frame delimitator, 1byte), Destination physical Address (Destination Address, 6bytes), Source physical Address (Source Address, 6bytes), protocol type (0x800Ipv4, 2bytes), IP header (IP Structure, 20bytes), UDP header (UDP Structure, 8bytes), Payload (AFDX Payload, 1-17bytes), Padding (Padding, 0-16bytes), sequence number (SN, 1byte), Frame Check sequence (Frame Check Seq, 4bytes), and Frame interval (Inter Frame Gap, 12 bytes). Fig. 3 shows a data format of a maximum Ethernet frame length (maximum Ethernet frame length) in the prior art, which includes: preamble, 7bytes, Frame header Delimiter (Start Frame Delimiter, 1byte), Destination physical Address (Destination Address, 6bytes), Source physical Address (Source Address, 6bytes), protocol type (0x800Ipv4, 2bytes), IP header (IP Structure, 20bytes), UDP header (UDP Structure, 8bytes), Payload (AFDX Payload, 1471bytes), sequence number (SN, 1byte), Frame Check sequence (Frame Check Seq, 4bytes), and Frame interval (Inter Frame Gap, 12 bytes).
Because the SN is distributed by taking a virtual link as a unit and a plurality of pieces of message data can be transmitted on one virtual link, the integrity check rule in the AFDX protocol in the prior art can only check the integrity of the data sequence on one virtual link but cannot check the sequence of the data of each message;
in addition, since the SNs are distributed by a "scheduler", from the perspective of a seven-layer reference model of Open System Interconnection (OSI), the scheduler is located between the network layer and the link layer, that is, the SNs are distributed after data enters the network layer, and the payload of the data is generated in the application layer, which means that there may be a case where the sequence of the application data of one message at the transmitting end is abnormal, and even though the sequence is kept complete during transmission, the sequence of the data itself received by the receiving end is still wrong.
Therefore, referring to fig. 4 and 5, the payload of each piece of data sent by the sending end includes an assigned data sequence number (MSN), and this data sequence number may be located at any position of the payload of each piece of data theoretically, but in order to ensure the integrity of the content of the payload of each piece of data and reduce the difficulty of checking at the receiving end, the data sequence number is preferably located at the head or the tail of the payload. In the application, the sending end distributes a data sequence number in the effective load of each piece of data of the message to mark the generation sequence of each piece of data, and the receiving end verifies each piece of data in the message according to the data sequence number to judge whether the sequence of the piece of data is normal or not, so that the aim of verifying the data sequence integrity of each piece of message is fulfilled, and the condition that the sequence of the data in the message is normal in the transmission process but the sequence of the message data received by the receiving end is abnormal due to the error sequence of the data of the receiving end is avoided.
It should be further noted that the preset step length is generally set to 1, that is, the data sequence number is cyclically incremented by 1, and when the sender completes initialization, the MSN allocated in the first piece of data sent is set to 0. When the data sequence number grows to the maximum value that its data format can reach, it restarts from 0.
Whether the data to be checked passes the check or not, the data serial number of the data is used as the comparison serial number of the data of the type to which the data belongs. For example, if the data serial number carried by the currently verified data carrying the flight altitude information is 50, after the data is verified, the comparison serial number of the data carrying the flight altitude information is updated to 50, and the data serial number carried by the next data carrying the flight altitude information needs to be compared with 50 to determine whether the sequence integrity of the verified data is normal.
On the basis of the foregoing embodiment, in an embodiment of the present application, the verifying each piece of data in the message specifically includes:
checking each piece of data in the message according to the receiving sequence of the data;
the checking process comprises the following steps: and judging whether the difference value of the data serial number of the data and the comparison serial number of the data of the type to which the data belongs is smaller than an effective threshold value, if so, the data passes the verification, and if not, the data does not pass the verification.
It should be noted that the difference between the data serial number of the data and the comparison serial number of the data of the type to which the data belongs is a value obtained by subtracting the comparison serial number of the data of the type to which the data belongs from the data serial number of the data. For example, if the data serial number carried by the currently checked data is a, and the comparison serial number of the currently checked data is B, the difference between the data serial number of the data and the comparison serial number of the data of the type to which the data belongs is a-B.
Due to the reason that the MSN distributed in the first piece of data sent starts from 0 after the initialization of the sending end, even if the current data which is being verified is not verified, the data serial number of the data is used as the comparison serial number of the data of the type to which the data which is not verified belongs, so that the situation that normal data is continuously discarded after the initialization of the sending end is avoided. For example, if the data sequence number carried by the currently verified data is 100, the comparison sequence number is updated to 100, at this time, the sending end performs initialization once, the data sequence number carried by the next piece of data is 0, if 0 is not updated to the comparison sequence number of the type to which the piece of data belongs, the sent data is discarded later, and the data is normally received until the data with the carried data sequence number of 101, which obviously discards a large amount of data; however, if the data sequence number 0 carried by the first piece of data initialized by the sending end is updated to the comparison sequence number, only one piece of data is discarded, and the information communication of the whole system is not greatly influenced.
In a specific embodiment of the present application, the size of the data sequence number is greater than or equal to 2 bytes. The size of the SN is 1byte, the value range of the SN is 1-255, the data volume allowed to be transmitted on the AFDX bus is very large for the range of 1-255, when the AFDX bus is in flash or other abnormal conditions, the quantity of the transmitted data is easily over 255, so that the condition that the SN rolls back is caused, and the problem that the data with wrong sequence cannot be identified due to the fact that the data just roll back to the effective window of the SN cannot be avoided. And the size of the data sequence number is more than or equal to 2bytes, and the value range is greatly increased, so that the possibility that data with wrong sequence cannot be identified due to the rollback of the data sequence number is avoided.
In a preferred embodiment of the present application, the size of the data sequence number is preferably 2bytes, because when the data sequence number is 2bytes, the value range thereof is 0-65535, and the rollback phenomenon of the MSN is not generated within 10 minutes according to the maximum cycle of 10ms of a general AFDX bus communication message, thereby improving the robustness of the verification system of the AFDX bus message. However, the present application does not limit the specific size and data type of the data sequence number, which is determined according to the actual situation.
On the basis of the above embodiment, in another embodiment of the present application, the effective threshold is greater than or equal to 1.
In a specific embodiment of the present application, the specific value range of the effective threshold is 1-7, inclusive. The specific value of the effective threshold is not limited, and is determined according to the actual situation.
On the basis of the foregoing embodiment, in another embodiment of the present application, the allocating a data sequence number to each piece of data in the message specifically includes:
distributing a data sequence number to each piece of data in the message according to the generation sequence of the data; wherein the data sequence number is filled in a header of a payload of each piece of data.
It should be noted that, in this embodiment, the data serial number of each type of data is assigned according to the data generation sequence, for example, if the data serial number of the current data carrying the altitude that is currently generated is 9, the data serial number of the current data carrying the altitude that is next generated is 10, and these two pieces of data are referred to as adjacent data in this type of data.
In addition, in order to distinguish from the original SN of the data tail, it is preferable that the data sequence number is set to the head of the payload of each piece of data. The specific location of the data serial number is not limited in the present application, and is determined according to the actual situation.
Correspondingly, the embodiment of the present application further provides a method for checking an AFDX bus message, as shown in fig. 6, which is applied to a sending end; the checking method of the AFDX bus message comprises the following steps:
s101: generating a message, wherein the message at least comprises a variety of data, and the variety of data at least comprises a piece of data;
s102: and distributing a data sequence number for each piece of data in the message, wherein the data sequence numbers of the same kind of data are increased by a preset step length.
It should be noted that the message generated by the sending end generally includes multiple types of data, each type of data carries different information, and the information may be flight altitude or flight speed, etc. In this embodiment, the data sequence number of each type of data is incremented by a preset step, for example, if the data sequence number of the current data carrying the flight altitude is 1, the data sequence number allocated by the sending end for the next data carrying the flight altitude is 2.
As shown in fig. 7, in a preferred embodiment of the present application, the assigning a data sequence number to each piece of data in the message includes:
s1021: distributing a data sequence number to each piece of data in the message according to the generation sequence of the data; wherein the data sequence number is filled in a header of a payload of each piece of data.
For example, the data serial number of the current data carrying the altitude generated currently is 9, and the data serial number of the current data carrying the altitude generated next is 10, and these two pieces of data are called adjacent data in this kind of data.
Referring to fig. 4 and 5, the payload of each piece of data sent by the sending end includes an assigned data sequence number (MSN), and this data sequence number may be located at any position of the payload of each piece of data theoretically, but in order to ensure the integrity of the content of the payload of each piece of data and reduce the difficulty of checking at the receiving end, the data sequence number is preferably located at the head or the tail of the payload; but in order to distinguish from the original SN at the end of the data, it is more preferable to set the data sequence number to the head of the payload of each piece of data. The specific location of the data serial number is not limited in the present application, and is determined according to the actual situation.
In the application, the sending end distributes a data sequence number in the effective load of each piece of data of the message to mark the generation sequence of each piece of data, and the receiving end judges whether the sequence of each piece of data is normal or not according to the comparison sequence number of each piece of data in the received message and the type of data, so that the aim of verifying the data sequence integrity of each piece of message is fulfilled, and the condition that the sequence of the data in the message is normal in the transmission process but the sequence of the message data received by the receiving end is abnormal due to the error of the sequence of the data of the receiving end is avoided.
It should be further noted that the preset step length is generally set to 1, that is, the data sequence number is cyclically incremented by 1, and when the sender completes initialization, the MSN allocated in the first piece of data sent is set to 0. When the data sequence number grows to the maximum value that its data format can reach, it restarts from 0.
In a specific embodiment of the present application, the size of the data sequence number is greater than or equal to 2 bytes. The size of the SN is 1byte, the value range of the SN is 1-255, the data volume allowed to be transmitted on the AFDX bus is very large for the range of 1-255, when the AFDX bus is in flash or other abnormal conditions, the quantity of the transmitted data is easily over 255, so that the condition that the SN rolls back is caused, and the problem that the data with wrong sequence cannot be identified due to the fact that the data just roll back to the effective window of the SN cannot be avoided. And the size of the data sequence number is more than or equal to 2bytes, and the value range is greatly increased, so that the possibility that data with wrong sequence cannot be identified due to the rollback of the data sequence number is avoided.
In a preferred embodiment of the present application, the size of the data sequence number is preferably 2bytes, because when the data sequence number is 2bytes, the value range thereof is 0-65535, and the rollback phenomenon of the MSN is not generated within 10 minutes according to the maximum cycle of 10ms of a general AFDX bus communication message, thereby improving the robustness of the verification system of the AFDX bus message. However, the present application does not limit the specific size and data type of the data sequence number, which is determined according to the actual situation.
Correspondingly, an embodiment of the present application further provides a method for checking an AFDX bus message, as shown in fig. 8, which is applied to a receiving end, and the method for checking an AFDX bus message includes:
s201: receiving a message sent by a sending end, wherein the message at least comprises a variety of data, and the variety of data at least comprises one piece of data;
s202: checking each piece of data in the message;
if the data in the message passes the verification, receiving the data passing the verification, and taking a data serial number of the data passing the verification as a comparison serial number of the data of the kind to which the data passing the verification belongs;
if the data in the message is not verified, discarding the data which is not verified, and taking the data sequence number of the data which is not verified as the comparison sequence number of the data of the kind to which the data which is not verified belongs.
In this embodiment, the receiving end checks each piece of data in the message according to the data sequence number to determine whether the sequence of the piece of data is normal, so as to achieve the purpose of checking the integrity of the data sequence of each piece of message, and avoid the situation that the sequence of the data in the message is normal in the transmission process, but the sequence of the message data received by the receiving end is abnormal due to the wrong sequence of the data.
On the basis of the foregoing embodiment, in another embodiment of the present application, the verifying each piece of data in the message specifically includes:
checking each piece of data in the message according to the receiving sequence of the data;
as shown in fig. 9, the verification process is: and judging whether the difference value of the data serial number of the data and the comparison serial number of the data of the type to which the data belongs is smaller than an effective threshold value, if so, the data passes the verification, and if not, the data does not pass the verification.
It should be noted that the difference between the data serial number of the data and the comparison serial number of the data of the type to which the data belongs is a value obtained by subtracting the comparison serial number of the data of the type to which the data belongs from the data serial number of the data. For example, if the data serial number carried by the currently checked data is a, and the comparison serial number of the currently checked data is B, the difference between the data serial number of the data and the comparison serial number of the data of the type to which the data belongs is a-B.
Whether the data to be checked passes the check or not, the data serial number of the data is used as the comparison serial number of the data of the type to which the data belongs. For example, if the data serial number carried by the currently verified data carrying the flight altitude information is 50, after the data is verified, the comparison serial number of the data carrying the flight altitude information is updated to 50, and the data serial number carried by the next data carrying the flight altitude information needs to be compared with 50 to determine whether the sequence integrity of the verified data is normal.
It should be further noted that, due to the reason that the MSN allocated in the first piece of data sent after the initialization of the sending end starts from 0, even if the data currently being verified fails to be verified, the data sequence number of the data is used as the comparison sequence number of the data of the category to which the data failed to be verified belongs, so that the occurrence of the situation that normal data is continuously discarded after the initialization of the sending end is avoided. For example, if the data sequence number carried by the currently verified data is 100, the comparison sequence number is updated to 100, at this time, the sending end performs initialization once, the data sequence number carried by the next piece of data is 0, if 0 is not updated to the comparison sequence number of the type to which the piece of data belongs, the sent data is discarded later, and the data is normally received until the data with the carried data sequence number of 101, which obviously discards a large amount of data; however, if the data sequence number 0 carried by the first piece of data initialized by the sending end is updated to the comparison sequence number, only one piece of data is discarded, and the information communication of the whole system is not greatly influenced.
On the basis of the above embodiment, in another embodiment of the present application, the effective threshold is greater than or equal to 1.
In a specific embodiment of the present application, the specific value range of the effective threshold is 1-7, inclusive. The specific value of the effective threshold is not limited, and is determined according to the actual situation.
To sum up, the embodiment of the present application provides a system and a method for checking AFDX bus messages, wherein a sending end of the checking system for AFDX bus messages distributes a data sequence number in an effective load of each piece of data of the message to mark a generation sequence of each piece of data, and a receiving end of the checking system for AFDX bus messages checks each piece of data in the message according to the data sequence number, so as to determine whether the sequence of the piece of data is normal, thereby achieving the purpose of checking the integrity of the data sequence of each piece of message, and avoiding the occurrence of the situation that the sequence of the data in the message is normal in the transmission process, but the sequence of the message data received by the receiving end is abnormal due to the error of the sequence of the data.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (5)
1. An AFDX bus message verification system, comprising: a sending end and a receiving end; wherein,
the sending end is used for generating a message, wherein the message at least comprises a variety of data, and the variety of data at least comprises one piece of data;
distributing a data sequence number for each piece of data in the message, wherein the data sequence numbers of the same kind of data are increased progressively according to a preset step length;
the receiving end is used for receiving the message;
checking each piece of data in the message;
if the data in the message passes the verification, receiving the data passing the verification, and taking a data serial number of the data passing the verification as a comparison serial number of the data of the kind to which the data passing the verification belongs;
if the data in the message is not verified, discarding the data which is not verified, and taking the data serial number of the data which is not verified as the comparison serial number of the data of the kind to which the data which is not verified belongs;
the verifying each piece of data in the message specifically includes:
checking each piece of data in the message according to the receiving sequence of the data;
the checking process comprises the following steps: and judging whether the difference value of the data serial number of the data and the comparison serial number of the data of the type to which the data belongs is smaller than an effective threshold value, if so, the data passes the verification, and if not, the data does not pass the verification.
2. The system according to claim 1, wherein the assigning of a data sequence number to each piece of data in the message is specifically:
distributing a data sequence number to each piece of data in the message according to the generation sequence of the data; wherein the data sequence number is filled in a header of a payload of each piece of data.
3. The system of claim 1,
the effective threshold is greater than or equal to 1;
the size of the data sequence number is greater than or equal to 2 bytes.
4. A method for checking AFDX bus message is applied to a receiving end, and is characterized in that the method for checking the AFDX bus message comprises the following steps:
receiving a message sent by a sending end, wherein the message at least comprises a variety of data, and the variety of data at least comprises one piece of data;
checking each piece of data in the message;
if the data in the message passes the verification, receiving the data passing the verification, and taking a data serial number of the data passing the verification as a comparison serial number of the data of the kind to which the data passing the verification belongs;
if the data in the message is not verified, discarding the data which is not verified, and taking the data serial number of the data which is not verified as the comparison serial number of the data of the kind to which the data which is not verified belongs;
the verifying each piece of data in the message specifically includes:
checking each piece of data in the message according to the receiving sequence of the data;
the checking process comprises the following steps: and judging whether the difference value of the data serial number of the data and the comparison serial number of the data of the type to which the data belongs is smaller than an effective threshold value, if so, the data passes the verification, and if not, the data does not pass the verification.
5. The method of claim 4, wherein the effective threshold is greater than or equal to 1.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710197466.9A CN106788908B (en) | 2017-03-29 | 2017-03-29 | Checking system and method for AFDX (avionics full Duplex switched Ethernet) bus messages |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710197466.9A CN106788908B (en) | 2017-03-29 | 2017-03-29 | Checking system and method for AFDX (avionics full Duplex switched Ethernet) bus messages |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106788908A CN106788908A (en) | 2017-05-31 |
| CN106788908B true CN106788908B (en) | 2020-02-04 |
Family
ID=58967017
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710197466.9A Active CN106788908B (en) | 2017-03-29 | 2017-03-29 | Checking system and method for AFDX (avionics full Duplex switched Ethernet) bus messages |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106788908B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112564863A (en) * | 2020-12-24 | 2021-03-26 | 中国兵器装备集团自动化研究所 | Communication timeliness error detection system and detection method |
| CN113612679B (en) * | 2021-07-29 | 2023-02-24 | 百度在线网络技术（北京）有限公司 | Message verification method and device, electronic equipment and storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105281945A (en) * | 2014-09-19 | 2016-01-27 | 中国人民解放军第二炮兵工程大学 | Data flow-based deterministic network integrity fault detection method |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FR2902956B1 (en) * | 2006-06-23 | 2008-09-19 | Airbus France Sas | METHOD FOR ROUTING VIRTUAL LINKS IN A GUIDED DETERMINISM FRAME SWITCHING NETWORK |
| FR2920623B1 (en) * | 2007-09-03 | 2011-09-23 | Airbus France | FRAME SWITCHING DEVICE FOR AFDX NETWORK. |
-
2017
- 2017-03-29 CN CN201710197466.9A patent/CN106788908B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105281945A (en) * | 2014-09-19 | 2016-01-27 | 中国人民解放军第二炮兵工程大学 | Data flow-based deterministic network integrity fault detection method |
Non-Patent Citations (1)
| Title |
|---|
| 面向完整性要求的航空电子全双工交换式以太网可靠性评价参数研究;李硕等;《西安交通大学学报》;20130331;第47卷(第3期);126-131页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106788908A (en) | 2017-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10505841B1 (en) | Resilient data communications with physical layer link aggregation, extended failure detection and load balancing | |
| US10237153B2 (en) | Packet retransmission method and apparatus | |
| CN106850377B (en) | Checking system and method for AFDX (avionics full Duplex switched Ethernet) bus messages | |
| CN101141406B (en) | Distributed flow control method, system and device | |
| US9473599B2 (en) | High payload data packet transmission system and relay to lower latency | |
| EP3528409A1 (en) | Method and system for improving wireless link efficiency | |
| CN110943933A (en) | Method, device and system for realizing data transmission | |
| CN113542145A (en) | Method for sharing Ethernet link aggregation group load and network equipment | |
| KR20140132063A (en) | Apparatus and Method for CAN Comnunication | |
| KR101434422B1 (en) | Method for improving network by modulating virtual link and the system thereof | |
| US20220368626A1 (en) | Packet or frame replication and elimination with explict or implict notification to reset sequence number recovery | |
| US20220407742A1 (en) | Time-sensitive transmission of ethernet traffic between endpoint network nodes | |
| WO2013149587A1 (en) | Ethernet message compression and decompression methods and network element device | |
| CN106788908B (en) | Checking system and method for AFDX (avionics full Duplex switched Ethernet) bus messages | |
| CN104160735B (en) | Send out message processing method, transponder, message processor, message handling system | |
| CN102510385A (en) | Method for preventing fragment attack of IP (Internet Protocol) datagram | |
| CN112242956A (en) | Flow rate control method and device | |
| CN107666626B (en) | Data transmission method of multi-wavelength channel, optical line terminal and system | |
| CN109495289B (en) | Electronic device and method for receiving data, communication system and computer storage medium | |
| WO2019026465A1 (en) | Reliable cut-through switching for time sensitive networks | |
| CN105763375B (en) | A kind of data packet sending method, method of reseptance and microwave station | |
| US11330085B2 (en) | Data transmission protection method, device, system, and computer readable storage medium | |
| CN104283716A (en) | Data transmission method, equipment and system | |
| KR102368605B1 (en) | Method for transceiving data between heterogeneous network | |
| US11374787B2 (en) | Switch device, communication control method, and communication control program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |