CN106656709A - Airborne avionic bus state exchange protocol processing method - Google Patents
Airborne avionic bus state exchange protocol processing method Download PDFInfo
- Publication number
- CN106656709A CN106656709A CN201611140142.3A CN201611140142A CN106656709A CN 106656709 A CN106656709 A CN 106656709A CN 201611140142 A CN201611140142 A CN 201611140142A CN 106656709 A CN106656709 A CN 106656709A
- Authority
- CN
- China
- Prior art keywords
- bus
- data
- total bytes
- message
- request message
- 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.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40006—Architecture of a communication node
- H04L12/40013—Details regarding a bus controller
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
- H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L2012/40267—Bus for use in transportation systems
- H04L2012/4028—Bus for use in transportation systems the transportation system being an aircraft
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Small-Scale Networks (AREA)
Abstract
The invention belongs to the field of computer software-system application, and relates to an airborne avionic bus state exchange protocol processing method. The method comprises the steps: waiting to receive an external application request message; analyzing the request message if the external application request message is received; determining that the request message is an access command A, R, S message through analysis, and obtaining the corresponding bus type and the bus state information on a bus ID in an airborne avionic bus management information base according to the bus type in the access command A, R, S message and the bus state information requested by the bus ID; assembling the access command A, R, S response messages, and transmitting the assembled access command A, R, S response message to an external application.
Description
Technical field
The design belongs to computer software-system software field, is related to a kind of airborne end avionics bus state and exchanges
Protocol processes method.
Background technology
With the development of civil avionics system, the avionics bus types of interior of aircraft are more and more, airborne avionics number
It is responsible for gathering data in avionics bus in real time according to information management system, and by the data of collection by certain mode
It is sent to applications.When applications do not receive the data of avionics data information management system transmission, need certain remote
Journey mode is obtained in that the historical information in bus, the historic state that bus is analyzed according to historical information and the shape being presently in
State.How the historical information of airborne avionics bus is remotely obtained, and this is accomplished by the long-range acquisition of a set of lightweight of User Defined
The agreement of airborne avionics bus management information, the airborne equipment resource of the airborne avionics bus management information protocol occupancy of lightweight
It is few, and interactive mode is simple, realizes beneficial on airborne equipment, and good using effect can be reached.
The content of the invention
The purpose of the present invention：
The present invention provides a kind of airborne end avionics bus state exchange agreement processing method, can develop on airborne equipment
The service of airborne avionics bus management, and then monitor in real time and management are carried out to avionics bus state information, it is long-range so as to give
Applications obtain airborne end avionics bus state information and provide convenience, and are easy to external management personnel to understand airborne equipment in real time
Avionics bus state, be easy to find avionics bus fault message, so as to be beneficial to the maintenance to Aerial Electronic Equipment and maintenance.
Technical scheme：
A kind of airborne end avionics bus state exchange agreement processing method, including：
Step 1, etc. applications request message to be received；If receiving applications request message, parsing is described please
Seek message；
If it is visit order A message that step 2, parsing obtain the request message, according to bus in visit order A message
Type and the bus state information of bus ID request, obtain in airborne end avionics bus management information bank corresponding bus type and
Bus state information in bus ID；
Step 3, the response message of assembling visit order A are simultaneously sent to applications, return to step 1；
If it is visit order R message that step 4, parsing obtain the request message, according to bus in visit order R message
Type and the bus state information of bus ID request, obtain in airborne end avionics bus management information bank corresponding bus type and
Bus state information in bus ID；
Step 5, the response message of assembling visit order R are simultaneously sent to applications, return to step 1；
If it is visit order S message that step 6, parsing obtain the request message, according to bus in visit order S message
Type and the bus state information of bus ID request, obtain in airborne end avionics bus management information bank corresponding bus type and
Bus state information in bus ID；
Step 7, the response message of assembling visit order S are simultaneously sent to applications, return to step 1；
Airborne end avionics bus management information model is in avionics bus management information bank：
(1) airborne end avionics bus management information model adopts tree structure, and using four layers of tree, root node is management to model
Information bank, one layer is bus type node, and two layers is Bus number node, and three layers is the avionics bus state information for recording；
(2) following relation is included in the status information of avionics bus management information model：
When normally receiving situation：
A. bus data total bytes number of times * 4294967296+ are received and receives bus data total bytes=(receiving data
Successful total bytes number of times * 4294967296+ receive bus data success total bytes)+(receiving data failure total byte is for several times
Number * 4294967296+ receive bus data failure total bytes)；
B. when bus data total bytes are received equal to 4294967296, receive bus data total bytes number of times and add 1；
C. when bus data success total bytes are received equal to 4294967296, receiving data success total bytes number of times adds
1；
D. whenever a secondary data is received, data are then received bus data success total bytes and are updated by completeness check
It is byte number of the original value plus the data of this reception, receives bus data total bytes and be updated to original value plus originally
The byte number of the data of secondary reception, receives number of success and adds 1, and the last time reception bus data success time is updated to receive number
According to when the time；When receiving data is first packet, receiving data time first time is recorded；
E. when bus data failure total bytes are received equal to 4294967296, receiving data failure total bytes number of times adds
1；
F. whenever a secondary data is received, data fail by completeness check, then receive bus data failure total bytes
Byte number of the original value plus the data of this reception is updated to, reception bus data total bytes are updated to original value and add
The byte number of upper this data for receiving, reception failure number of times adds 1, and the last time receives bus data Time To Failure and is updated to connect
Time when receiving data；When receiving data is first packet, receiving data time first time is recorded；
G. after reception failure number of times reaches the threshold value of setting, receive bus state and be set to failure state, otherwise receive
Bus state is set to normal operating conditions；
Situation is sent when normal：
A. bus data total bytes number of times * 4294967296+ are sent and sends bus data total bytes=(transmission data
Successful total bytes number of times * 4294967296+ send bus data success total bytes)+(send data failure total byte for several times
Number * 4294967296+ send bus data failure total bytes number of times)；
B. when bus data total bytes are sent equal to 4294967296, send bus data total bytes number of times and add 1；
C. when bus data success total bytes are sent equal to 4294967296, data success total bytes number of times is sent
Plus 1；
D. whenever a secondary data is sent, data is activation success then sends bus data success total bytes and is updated to originally
Value plus this transmission data byte number, send bus data total bytes be updated to original value plus this send
Data byte number, send number of success add 1, the last time send bus data success the time be updated to send data constantly
Between；When it is first packet to send data, record sends for the first time data time；
E. when bus data failure total bytes are sent equal to 4294967296, send data failure total bytes number of times and add
1；
F. whenever a secondary data is sent, data is activation failure then sends bus data failure total bytes and is updated to originally
Value plus this transmission data byte number, send bus data total bytes be updated to original value plus this send
Data byte number, send the frequency of failure add 1, the last time send bus data Time To Failure be updated to send data constantly
Between；When it is first packet to send data, record sends for the first time data time；
G. after the transmission frequency of failure reaches the threshold value of setting, send bus state and be set to failure state, otherwise threshold value
It is interior, send bus state and be set to normal operating conditions.
During the bus state information that bus type and bus ID are asked in visit order A, R, S message, airborne avionics bus
Information management protocol interaction flow process includes：
First, visit order A interactions：Using the request message that visit order A is sent to airborne end, airborne end receives please
Ask and processed after message, when request message content is completely correct, reply the response comprising data field；When request message content
There is mistake in inspection, then reply the response not comprising data field；
2nd, visit order R interactions：Using the request message that visit order R is sent to airborne end, airborne end receives please
Ask and processed after message, when request message content is completely correct, reply the response comprising data field；When request message content
There is mistake in inspection, then reply the response not comprising data field；
3rd, visit order S interactions：Using the request message that visit order S is sent to airborne end, airborne end receives please
Ask and processed after message, when request message content is completely correct, reply the response comprising data field；When request message content
There is mistake in inspection, then reply the response not comprising data field.
During the bus state information that bus type and bus ID are asked in visit order A, R, S message, airborne avionics bus
The interaction protocol data model of information management protocol interaction flow process is specially：
It is divided into request message and response message two parts, the field definition of two message is as follows：
(1) bus type：Represent request bus type；
(2) bus ID：Represent specific certain bus of request.
(3) visit order：The bus state information of request is represented, visit order is divided into：
A：Represent and obtain all status informations below this bus；
R：Represent and obtain status information relevant with reception below this bus；
S：Represent and obtain status information relevant with transmission below this bus.
(4) request message conditional code：The message correctness of request is represented, conditional code is divided into：
0：Represent that all fields are all correct in request message；
1：Represent the CRC check mistake of request message；
2：Represent in request message without this bus type；
3：Represent in request message without this bus ID；
4：Represent in request message without this visit order.
(5) response command：The reply to visit order in request message is represented, response command is divided into：
AR：Represent the response to visit order A；
RR：Represent the response to visit order R；
SR：Represent the response to visit order S.
(6) data：When request message Content inspection is correct and passes through, then response message includes this field, if request disappears
There is mistake in breath inspection, then response message does not include this field.
(7)CRC：Represent the CRC check code of message.
The present invention has the advantage that effect：
The design can obtain in use following beneficial effect：
(1) condition monitoring and the management to airborne avionics bus is provided, is navigated by each to each class avionics bus
The statistics of the status information of electric bus, is easy to airborne attendant and administrative staff to learn that avionics is total by remote mode in time
The historic state information of line, analyzes whether airborne avionics bus breaks down, time point and the frequency of generation that failure occurs, carries
The high maintainable and maintainability of equipment.
(2) versatility of method：This method is a kind of agreement of lightweight, and the hardware money taken during agreement is realized at airborne end
Source is few, facilitates implementation and operability, is whether all capable of achieving this agreement using TCP or UDP.
Description of the drawings
Fig. 1 is airborne end avionics bus management information model schematic diagram.
Fig. 2 is that airborne avionics bus message manages interaction protocol data model schematic diagram.
Fig. 3 is airborne avionics bus message management agreement interaction flow schematic diagram.
Fig. 4 is airborne end avionics bus switch protocol data handling process schematic diagram.
Specific embodiment
A kind of airborne end avionics bus state exchange agreement processing method, including：
Step 1, etc. applications request message to be received；If receiving applications request message, parsing is described please
Seek message；
If it is visit order A message that step 2, parsing obtain the request message, according to bus in visit order A message
Type and the bus state information of bus ID request, obtain in airborne end avionics bus management information bank corresponding bus type and
Bus state information in bus ID；
Step 3, the response message of assembling visit order A are simultaneously sent to applications, return to step 1；
If it is visit order R message that step 4, parsing obtain the request message, according to bus in visit order R message
Type and the bus state information of bus ID request, obtain in airborne end avionics bus management information bank corresponding bus type and
Bus state information in bus ID；
Step 5, the response message of assembling visit order R are simultaneously sent to applications, return to step 1；
If it is visit order S message that step 6, parsing obtain the request message, according to bus in visit order S message
Type and the bus state information of bus ID request, obtain in airborne end avionics bus management information bank corresponding bus type and
Bus state information in bus ID；
Step 7, the response message of assembling visit order S are simultaneously sent to applications, return to step 1.
Airborne end avionics bus management information model is in avionics bus management information bank：
(1) airborne end avionics bus management information model adopts tree structure, and using four layers of tree, root node is management to model
Information bank, one layer is bus type node, and two layers is Bus number node, and three layers is the avionics bus state information for recording；
(2) following relation is included in the status information of avionics bus management information model：
When normally receiving situation：
A. bus data total bytes number of times * 4294967296+ are received and receives bus data total bytes=(receiving data
Successful total bytes number of times * 4294967296+ receive bus data success total bytes)+(receiving data failure total byte is for several times
Number * 4294967296+ receive bus data failure total bytes)；
B. when bus data total bytes are received equal to 4294967296, receive bus data total bytes number of times and add 1；
C. when bus data success total bytes are received equal to 4294967296, receiving data success total bytes number of times adds
1；
D. whenever a secondary data is received, data are then received bus data success total bytes and are updated by completeness check
It is byte number of the original value plus the data of this reception, receives bus data total bytes and be updated to original value plus originally
The byte number of the data of secondary reception, receives number of success and adds 1, and the last time reception bus data success time is updated to receive number
According to when the time；When receiving data is first packet, receiving data time first time is recorded；
E. when bus data failure total bytes are received equal to 4294967296, receiving data failure total bytes number of times adds
1；
F. whenever a secondary data is received, data fail by completeness check, then receive bus data failure total bytes
Byte number of the original value plus the data of this reception is updated to, reception bus data total bytes are updated to original value and add
The byte number of upper this data for receiving, reception failure number of times adds 1, and the last time receives bus data Time To Failure and is updated to connect
Time when receiving data；When receiving data is first packet, receiving data time first time is recorded；
G. after reception failure number of times reaches the threshold value of setting, receive bus state and be set to failure state, otherwise receive
Bus state is set to normal operating conditions；
Situation is sent when normal：
A. bus data total bytes number of times * 4294967296+ are sent and sends bus data total bytes=(transmission data
Successful total bytes number of times * 4294967296+ send bus data success total bytes)+(send data failure total byte for several times
Number * 4294967296+ send bus data failure total bytes number of times)；
B. when bus data total bytes are sent equal to 4294967296, send bus data total bytes number of times and add 1；
C. when bus data success total bytes are sent equal to 4294967296, data success total bytes number of times is sent
Plus 1；
D. whenever a secondary data is sent, data is activation success then sends bus data success total bytes and is updated to originally
Value plus this transmission data byte number, send bus data total bytes be updated to original value plus this send
Data byte number, send number of success add 1, the last time send bus data success the time be updated to send data constantly
Between；When it is first packet to send data, record sends for the first time data time；
E. when bus data failure total bytes are sent equal to 4294967296, send data failure total bytes number of times and add
1；
F. whenever a secondary data is sent, data is activation failure then sends bus data failure total bytes and is updated to originally
Value plus this transmission data byte number, send bus data total bytes be updated to original value plus this send
Data byte number, send the frequency of failure add 1, the last time send bus data Time To Failure be updated to send data constantly
Between；When it is first packet to send data, record sends for the first time data time；
G. after the transmission frequency of failure reaches the threshold value of setting, send bus state and be set to failure state, otherwise threshold value
It is interior, send bus state and be set to normal operating conditions.
During the bus state information that bus type and bus ID are asked in visit order A, R, S message, airborne avionics bus
Information management protocol interaction flow process includes：
First, visit order A interactions：Using the request message that visit order A is sent to airborne end, airborne end receives please
Ask and processed after message, when request message content is completely correct, reply the response comprising data field；When request message content
There is mistake in inspection, then reply the response not comprising data field；
2nd, visit order R interactions：Using the request message that visit order R is sent to airborne end, airborne end receives please
Ask and processed after message, when request message content is completely correct, reply the response comprising data field；When request message content
There is mistake in inspection, then reply the response not comprising data field；
3rd, visit order S interactions：Using the request message that visit order S is sent to airborne end, airborne end receives please
Ask and processed after message, when request message content is completely correct, reply the response comprising data field；When request message content
There is mistake in inspection, then reply the response not comprising data field.
During the bus state information that bus type and bus ID are asked in visit order A, R, S message, airborne avionics bus
The interaction protocol data model of information management protocol interaction flow process is specially：
It is divided into request message and response message two parts, the field definition of two message is as follows：
(1) bus type：Represent request bus type；
(2) bus ID：Represent specific certain bus of request.
(3) visit order：The bus state information of request is represented, visit order is divided into：
A：Represent and obtain all status informations below this bus；
R：Represent and obtain status information relevant with reception below this bus；
S：Represent and obtain status information relevant with transmission below this bus.
(4) request message conditional code：The message correctness of request is represented, conditional code is divided into：
0：Represent that all fields are all correct in request message；
1：Represent the CRC check mistake of request message；
2：Represent in request message without this bus type；
3：Represent in request message without this bus ID；
4：Represent in request message without this visit order.
(5) response command：The reply to visit order in request message is represented, response command is divided into：
AR：Represent the response to visit order A；
RR：Represent the response to visit order R；
SR：Represent the response to visit order S.
(6) data：When request message Content inspection is correct and passes through, then response message includes this field, if request disappears
There is mistake in breath inspection, then response message does not include this field.
(7)CRC：Represent the CRC check code of message.
Embodiment
Airborne end avionics bus interaction protocol flow chart of data processing describes airborne end avionics bus interaction protocol service center
The process and flow process of reason, as shown in Figure 4.
(1) the applications request message to be received such as airborne end service, then waits always without message, goes to when having message
(2)；
(2) request message that applications send is parsed, is disappeared to parse according to request message format (Fig. 2 request messages)
Breath；If request message is correct, and visit order is A, then perform the visit order A processes in Fig. 3, is gone to (3)；If visit order
It is R, then performs the visit order R processes in Fig. 3, goes to (6)；If visit order is S, the visit order S mistakes in Fig. 3 are performed
Journey, goes to (9)；If analysis request message mistake, goes to (1)；
(3) visit order A in request message, bus type and bus ID, obtain airborne end avionics bus in Fig. 1
Bus state information in management information bank on corresponding bus type and bus ID, after obtaining success, goes to (4)；
(4) response message of visit order A is assembled by response message format in Fig. 2, after assembling success, is gone to (5)；
(5) the corresponding response messages of request visit order A are sent to applications.After being sent completely, go to (1)；
(6) visit order R in request message, bus type and bus ID, obtain airborne end avionics bus in Fig. 1
Bus state information in management information bank on corresponding bus type and bus ID, after obtaining success, goes to (7)；
(7) response message of visit order R is assembled by response message format in Fig. 2, after assembling success, is gone to (8)；
(8) the corresponding response messages of request visit order R are sent to applications.After being sent completely, go to (1)；
(9) visit order S in request message, bus type and bus ID, obtain airborne end avionics bus in Fig. 1
Bus state information in management information bank on corresponding bus type and bus ID, after obtaining success, goes to (10)；
(10) response message of visit order S is assembled by response message format in Fig. 2, after assembling success, is gone to (11)；
(11) the corresponding response messages of visit order S are sent to applications.After being sent completely, go to (1)；
1. airborne end avionics bus management information model
Airborne end avionics bus management information model is as shown in Figure 1.
(1) airborne end avionics bus management information model adopts tree structure, and using four layers of tree, root node is management to model
Information bank, one layer is bus type node, and two layers is Bus number node, and three layers is the avionics bus state information for recording.
(2) following relation is included in the status information of avionics bus management information model：
When normally receiving situation：
H. bus data total bytes number of times * 4294967296+ are received and receives bus data total bytes=(receiving data
Successful total bytes number of times * 4294967296+ receive bus data success total bytes)+(receiving data failure total byte is for several times
Number * 4294967296+ receive bus data failure total bytes)；
I. when bus data total bytes are received equal to 4294967296, receive bus data total bytes number of times and add 1；
J. when bus data success total bytes are received equal to 4294967296, receiving data success total bytes number of times adds
1；
K. whenever a secondary data is received, data are then received bus data success total bytes and are updated by completeness check
It is byte number of the original value plus the data of this reception, receives bus data total bytes and be updated to original value plus originally
The byte number of the data of secondary reception, receives number of success and adds 1, and the last time reception bus data success time is updated to receive number
According to when the time；When receiving data is first packet, receiving data time first time is recorded.
L. when bus data failure total bytes are received equal to 4294967296, receiving data failure total bytes number of times adds
1；
M. whenever a secondary data is received, data fail by completeness check, then receive bus data failure total bytes
Byte number of the original value plus the data of this reception is updated to, reception bus data total bytes are updated to original value and add
The byte number of upper this data for receiving, reception failure number of times adds 1, and the last time receives bus data Time To Failure and is updated to connect
Time when receiving data；When receiving data is first packet, receiving data time first time is recorded.
N. after reception failure number of times reaches the threshold value of setting, receive bus state and be set to failure state, otherwise receive
Bus state is set to normal operating conditions.
Situation is sent when normal：
H. bus data total bytes number of times * 4294967296+ are sent and sends bus data total bytes=(transmission data
Successful total bytes number of times * 4294967296+ send bus data success total bytes)+(send data failure total byte for several times
Number * 4294967296+ send bus data failure total bytes number of times)
I. when bus data total bytes are sent equal to 4294967296, send bus data total bytes number of times and add 1；
J. when bus data success total bytes are sent equal to 4294967296, data success total bytes number of times is sent
Plus 1；
K. whenever a secondary data is sent, data is activation success then sends bus data success total bytes and is updated to originally
Value plus this transmission data byte number, send bus data total bytes be updated to original value plus this send
Data byte number, send number of success add 1, the last time send bus data success the time be updated to send data constantly
Between；When it is first packet to send data, record sends for the first time data time.
L. when bus data failure total bytes are sent equal to 4294967296, send data failure total bytes number of times and add
1；
M. whenever a secondary data is sent, data is activation failure then sends bus data failure total bytes and is updated to originally
Value plus this transmission data byte number, send bus data total bytes be updated to original value plus this send
Data byte number, send the frequency of failure add 1, the last time send bus data Time To Failure be updated to send data constantly
Between；When it is first packet to send data, record sends for the first time data time.
N. after the transmission frequency of failure reaches the threshold value of setting, send bus state and be set to failure state, otherwise threshold value
It is interior, send bus state and be set to normal operating conditions.
2. airborne avionics bus message manages interaction protocol data model
Airborne avionics bus message management interaction protocol data model as shown in Fig. 2
Interaction protocol data model is divided into request message and response message two parts, and the field definition of two message is such as
Under：
(1) bus type：Represent request bus type；
(2) bus ID：Represent specific certain bus of request.
(3) visit order：The bus state information of request is represented, visit order is divided into：
A：Represent and obtain all status informations below this bus；
R：Represent and obtain status information relevant with reception below this bus；
S：Represent and obtain status information relevant with transmission below this bus.
(4) request message conditional code：The message correctness of request is represented, conditional code is divided into：
0：Represent that all fields are all correct in request message；
1：Represent the CRC check mistake of request message；
2：Represent in request message without this bus type；
3：Represent in request message without this bus ID；
4：Represent in request message without this visit order.
(5) response command：The reply to visit order in request message is represented, response command is divided into：
AR：Represent the response to visit order A；
RR：Represent the response to visit order R；
SR：Represent the response to visit order S.
(6) data：When request message Content inspection is correct and passes through, then response message includes this field, if request disappears
There is mistake in breath inspection, then response message does not include this field.
(7)CRC：Represent the CRC check code of message.
3. airborne avionics bus message management agreement interaction flow
Airborne avionics bus message management agreement interaction flow is as shown in figure 3, total with airborne end avionics for description application
The interaction of line information management protocol service.
(1) visit order A interactions：Using the request message that visit order A is sent to airborne end, airborne end receives please
Ask and processed after message, when request message content is completely correct, reply the response comprising data field；When request message content
There is mistake in inspection, then reply the response not comprising data field.
(2) visit order R interactions：Using the request message that visit order R is sent to airborne end, airborne end receives please
Ask and processed after message, when request message content is completely correct, reply the response comprising data field；When request message content
There is mistake in inspection, then reply the response not comprising data field.
(3) visit order S interactions：Using the request message that visit order S is sent to airborne end, airborne end receives please
Ask and processed after message, when request message content is completely correct, reply the response comprising data field；When request message content
There is mistake in inspection, then reply the response not comprising data field.
4. airborne end avionics bus interaction protocol flow chart of data processing
Airborne end avionics bus interaction protocol flow chart of data processing describes airborne end avionics bus interaction protocol service center
The process and flow process of reason, as shown in Figure 4.
Airborne end avionics bus interaction protocol handling process is by the process shown in Fig. 4, the request message to carrying out self-application
Parsed, and corresponding data are obtained according to avionics bus type, bus ID and visit order, finally sent responses to
Using.
In the airborne avionics bus data acquisition function of the airborne information management systems of MA700, using this method come supervisor
The status information for carrying avionics bus and the status information for remotely obtaining airborne avionics bus.
Claims (4)
1. a kind of airborne end avionics bus state exchange agreement processing method, it is characterised in that include：
Step 1, etc. applications request message to be received；If receiving applications request message, parse the request and disappear
Breath；
If it is visit order A message that step 2, parsing obtain the request message, according to bus type in visit order A message
With the bus state information of bus ID request, corresponding bus type and bus in airborne end avionics bus management information bank is obtained
Bus state information on ID；
Step 3, the response message of assembling visit order A are simultaneously sent to applications, return to step 1；
If it is visit order R message that step 4, parsing obtain the request message, according to bus type in visit order R message
With the bus state information of bus ID request, corresponding bus type and bus in airborne end avionics bus management information bank is obtained
Bus state information on ID；
Step 5, the response message of assembling visit order R are simultaneously sent to applications, return to step 1；
If it is visit order S message that step 6, parsing obtain the request message, according to bus type in visit order S message
With the bus state information of bus ID request, corresponding bus type and bus in airborne end avionics bus management information bank is obtained
Bus state information on ID；
Step 7, the response message of assembling visit order S are simultaneously sent to applications, return to step 1.
2. a kind of airborne end avionics bus state exchange agreement processing method as claimed in claim 1, it is characterised in that avionics
Airborne end avionics bus management information model is in bus management information bank：
(1) airborne end avionics bus management information model adopts tree structure, and using four layers of tree, root node is management information to model
Storehouse, one layer is bus type node, and two layers is Bus number node, and three layers is the avionics bus state information for recording；
(2) following relation is included in the status information of avionics bus management information model：
When normally receiving situation：
A. bus data total bytes number of times * 4294967296+ are received and receives bus data total bytes=(receiving data success
Total bytes number of times * 4294967296+ receive bus data success total bytes)+(receiving data failure total bytes number of times *
4294967296+ receives bus data failure total bytes)；
B. when bus data total bytes are received equal to 4294967296, receive bus data total bytes number of times and add 1；
C. when bus data success total bytes are received equal to 4294967296, receiving data success total bytes number of times adds 1；
D. whenever a secondary data is received, data then receive bus data success total bytes and are updated to original by completeness check
The value come adds the byte number of the data of this reception, and reception bus data total bytes are updated to original value and connect plus this
The byte number of the data of receipts, receives number of success and adds 1, when the last time reception bus data success time is updated to receiving data
Time；When receiving data is first packet, receiving data time first time is recorded；
E. when bus data failure total bytes are received equal to 4294967296, receiving data failure total bytes number of times adds 1；
F. whenever a secondary data is received, data fail by completeness check, then receive bus data failure total bytes and update
It is byte number of the original value plus the data of this reception, receives bus data total bytes and be updated to original value plus originally
The byte number of the data of secondary reception, reception failure number of times adds 1, and the last time receives bus data Time To Failure and is updated to receive number
According to when the time；When receiving data is first packet, receiving data time first time is recorded；
G. after reception failure number of times reaches the threshold value of setting, receive bus state and be set to failure state, otherwise receive bus
State is set to normal operating conditions；
Situation is sent when normal：
A. bus data total bytes number of times * 4294967296+ are sent and sends bus data total bytes=(transmission data success
Total bytes number of times * 4294967296+ send bus data success total bytes)+(send data failure total bytes number of times *
4294967296+ sends bus data failure total bytes number of times)；
B. when bus data total bytes are sent equal to 4294967296, send bus data total bytes number of times and add 1；
C. when bus data success total bytes are sent equal to 4294967296, send data success total bytes number of times and add 1；
D. whenever a secondary data is sent, data is activation success then sends bus data success total bytes and is updated to original value
Plus the byte number of this data for sending, send bus data total bytes and be updated to number of the original value plus this transmission
According to byte number, send number of success add 1, the last time send bus data success the time be updated to send data when the time；
When it is first packet to send data, record sends for the first time data time；
E. when bus data failure total bytes are sent equal to 4294967296, send data failure total bytes number of times and add 1；
F. whenever a secondary data is sent, data is activation failure then sends bus data failure total bytes and is updated to original value
Plus the byte number of this data for sending, send bus data total bytes and be updated to number of the original value plus this transmission
According to byte number, send the frequency of failure add 1, the last time send bus data Time To Failure be updated to send data when the time；
When it is first packet to send data, record sends for the first time data time；
G. after the transmission frequency of failure reaches the threshold value of setting, send bus state and be set to failure state, otherwise in threshold value, send out
Bus state is sent to be set to normal operating conditions.
3. a kind of airborne end avionics bus state exchange agreement processing method as claimed in claim 1, it is characterised in that
During the bus state information that bus type and bus ID are asked in visit order A, R, S message, airborne avionics bus message
Management agreement interaction flow includes：
First, visit order A interactions：Using the request message that visit order A is sent to airborne end, airborne end receives request and disappears
Processed after breath, when request message content is completely correct, replied the response comprising data field；When request message Content inspection
There is mistake, then reply the response not comprising data field；
2nd, visit order R interactions：Using the request message that visit order R is sent to airborne end, airborne end receives request and disappears
Processed after breath, when request message content is completely correct, replied the response comprising data field；When request message Content inspection
There is mistake, then reply the response not comprising data field；
3rd, visit order S interactions：Using the request message that visit order S is sent to airborne end, airborne end receives request and disappears
Processed after breath, when request message content is completely correct, replied the response comprising data field；When request message Content inspection
There is mistake, then reply the response not comprising data field.
4. a kind of airborne end avionics bus state exchange agreement processing method as claimed in claim 3, it is characterised in that
During the bus state information that bus type and bus ID are asked in visit order A, R, S message, airborne avionics bus message
The interaction protocol data model of management agreement interaction flow is specially：
It is divided into request message and response message two parts, the field definition of two message is as follows：
(1) bus type：Represent request bus type；
(2) bus ID：Represent specific certain bus of request.
(3) visit order：The bus state information of request is represented, visit order is divided into：
A：Represent and obtain all status informations below this bus；
R：Represent and obtain status information relevant with reception below this bus；
S：Represent and obtain status information relevant with transmission below this bus.
(4) request message conditional code：The message correctness of request is represented, conditional code is divided into：
0：Represent that all fields are all correct in request message；
1：Represent the CRC check mistake of request message；
2：Represent in request message without this bus type；
3：Represent in request message without this bus ID；
4：Represent in request message without this visit order.
(5) response command：The reply to visit order in request message is represented, response command is divided into：
AR：Represent the response to visit order A；
RR：Represent the response to visit order R；
SR：Represent the response to visit order S.
(6) data：When request message Content inspection is correct and passes through, then response message includes this field, if request message inspection
Existing mistake is found, then response message does not include this field.
(7)CRC：Represent the CRC check code of message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611140142.3A CN106656709B (en) | 2016-12-12 | 2016-12-12 | A kind of airborne end avionics bus state exchange agreement processing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611140142.3A CN106656709B (en) | 2016-12-12 | 2016-12-12 | A kind of airborne end avionics bus state exchange agreement processing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106656709A true CN106656709A (en) | 2017-05-10 |
| CN106656709B CN106656709B (en) | 2019-11-15 |
Family
ID=58825672
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611140142.3A Active CN106656709B (en) | 2016-12-12 | 2016-12-12 | A kind of airborne end avionics bus state exchange agreement processing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106656709B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107592307A (en) * | 2017-09-11 | 2018-01-16 | 中国航空工业集团公司西安飞机设计研究所 | A kind of airborne audio management system voice transfer verification method |
| CN107833437A (en) * | 2017-11-17 | 2018-03-23 | 中国航空工业集团公司西安航空计算技术研究所 | Phonic warning method based on the multichannel multipriority control command with delay |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8155804B2 (en) * | 2007-10-12 | 2012-04-10 | Airbus Operations Gmbh | Device and method for providing a flight status signal |
| CN103346931A (en) * | 2013-07-10 | 2013-10-09 | 北京航天自动控制研究所 | 1553B bus monitoring system |
| CN103685273A (en) * | 2013-12-14 | 2014-03-26 | 中国航空工业集团公司第六三一研究所 | Method for controlling multi-stage access to avionic data by civil onboard network service system |
| CN105911979A (en) * | 2016-05-31 | 2016-08-31 | 中国航空工业集团公司西安飞机设计研究所 | Flight bus data processing method |
-
2016
- 2016-12-12 CN CN201611140142.3A patent/CN106656709B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8155804B2 (en) * | 2007-10-12 | 2012-04-10 | Airbus Operations Gmbh | Device and method for providing a flight status signal |
| CN103346931A (en) * | 2013-07-10 | 2013-10-09 | 北京航天自动控制研究所 | 1553B bus monitoring system |
| CN103685273A (en) * | 2013-12-14 | 2014-03-26 | 中国航空工业集团公司第六三一研究所 | Method for controlling multi-stage access to avionic data by civil onboard network service system |
| CN105911979A (en) * | 2016-05-31 | 2016-08-31 | 中国航空工业集团公司西安飞机设计研究所 | Flight bus data processing method |
Non-Patent Citations (1)
| Title |
|---|
| 霍朝晖等: "未来战机光纤通道航电总线试飞测试技术探析", 《测控技术》 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107592307A (en) * | 2017-09-11 | 2018-01-16 | 中国航空工业集团公司西安飞机设计研究所 | A kind of airborne audio management system voice transfer verification method |
| CN107833437A (en) * | 2017-11-17 | 2018-03-23 | 中国航空工业集团公司西安航空计算技术研究所 | Phonic warning method based on the multichannel multipriority control command with delay |
| CN107833437B (en) * | 2017-11-17 | 2019-06-28 | 中国航空工业集团公司西安航空计算技术研究所 | Phonic warning method based on the multichannel multipriority control command with delay |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106656709B (en) | 2019-11-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3684033A1 (en) | Systems and methods for collecting, monitoring, and analyzing vehicle data from a plurality of vehicles using edge computing | |
| EP1922597B1 (en) | Fault data management | |
| EP1748394A2 (en) | Automated integration of fault reporting | |
| CN107921981A (en) | The monitoring and control of distributed machines | |
| CN105429905A (en) | Method, device and system for monitoring advertisement putting terminal | |
| CN110083544A (en) | Distributed automatization test system, method, electronic equipment and storage medium | |
| CN113419920B (en) | Real-time monitoring method for joint debugging test process of simulation test system of Internet of things management platform | |
| CN106656709A (en) | Airborne avionic bus state exchange protocol processing method | |
| CN117544676B (en) | Multi-terminal operation and maintenance data interactive transmission method and system | |
| CN114390112A (en) | Rail transit emergency disposal method and device, electronic equipment and storage medium | |
| EP3792186B1 (en) | Internet connected auxiliary power unit airline maintenance system | |
| CN110825538A (en) | MQ-based method for dynamically interacting data by self-defining data types | |
| CN206237041U (en) | A kind of clustering system of power transmission and transforming equipment electric power data | |
| CN112688835B (en) | Signal real-time monitoring method, system, electronic equipment and storage medium | |
| CN109889369A (en) | Multi-network redundant data transmission method | |
| CN109494872A (en) | A kind of distribution terminal is from register method and system | |
| CN109309526A (en) | A kind of boat-carrying satellite communication network backup management system | |
| CN109120488A (en) | CAN bus data collection system and method | |
| CN107729059A (en) | A kind of task loading method based on FC networks | |
| CN112134636B (en) | Remote centralized monitoring system and method for remote sensing satellite ground station network | |
| CN107181632A (en) | A kind of means of communication based on protocol configuration | |
| CN105323098A (en) | Method, device and system for processing alarm message | |
| CN209103514U (en) | A kind of unmanned plane | |
| CN108833192A (en) | A kind of method for monitoring network and monitoring device | |
| Zhang et al. | The Scheme for Solving the Conflicts Between Downstream and Backward Data in an Integrated Test System |
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 |