A dds communication data monitoring method and system of avionics system

Abstract

The application belongs to the technical field of airplane bus data management, and particularly relates to a DDS communication data monitoring method and system of an avionics system. The method comprises the following steps: S1, obtaining a monitoring configuration table carrying a monitoring subject, a monitoring subject category and a monitoring content category and issued by the switch; S2, matching the monitoring subject in the monitoring configuration table with the subject of the node by each communication node, if the corresponding subject exists, marking the monitoring subject according to the monitoring subject category and marking the monitoring content according to the monitoring content category; S3, sending the first type of monitoring data associated with the monitoring subject or the second type of monitoring data associated with the monitoring subject to the switch, and monitoring by the switch. The data transmitted in each communication node is selectively transmitted by the bus, and the data is monitored by the monitoring module of the switch, which can meet the demand of data monitoring, and reduce the power consumption and cost of the product.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of aircraft bus data management, and particularly relates to a DDS communication data monitoring method and system of an avionics system. BACKGROUND

[0002] An integrated computer processor (ICP) is a core computer processing platform for controlling and managing an avionics system, and has the capabilities of high-speed information processing and data calculation. The integrated computer processor is mainly composed of multiple data processing units (DPUs) which are interconnected through an FC bus and use DDS as a communication entity to provide a high-speed exchange network for various application software. Multiple application software on the same processor node (also referred to as a communication node) of the integrated computer processor adopts a DDS+RAM communication mode, that is, data is directly exchanged through memory, and the application programs between processors adopt a DDS+FC communication mode, that is, data is transmitted through a switch. This mode can ensure that the communication between the application programs in the processor does not occupy network resources, greatly saves the network resource overhead, and reduces the power consumption and cost of the product.

[0003] The network data monitoring of a traditional avionics system is based on the input port and the output port of the switch, and can only be monitored when data is transmitted in the network. Therefore, the data transmitted between tasks in the same processor through RAM cannot be monitored, which causes difficulty in troubleshooting the system and reduces the maintainability of the system. If all data is transmitted through the FC bus and then monitored by the switch, higher requirements will be put on the network, and the power consumption and cost of the product will be increased. SUMMARY

[0004] To solve the above problems, the application provides a DDS communication data monitoring method and system of an avionics system to monitor the data in each communication node.

[0005] The first aspect of the application provides a DDS communication data monitoring method of an avionics system, the avionics system comprising a switch and each communication node interconnected with the switch, and data transmission adopts a DDS transmission protocol. The monitoring method is used to monitor the data transmitted between each software in the communication node, and comprises the following steps.

[0006] Step S1: obtaining a monitoring configuration table published by the switch, the monitoring configuration table carrying a monitoring topic, a monitoring subject category and a monitoring content category;

[0007] Step S2: Each communication node matches the monitoring topic in the monitoring configuration table with the topic of its own node. If a corresponding topic exists, the monitoring subject is marked according to the monitoring subject category, and the monitoring content is marked according to the monitoring content category.

[0008] Step S3: Send the first type of monitoring data associated with the monitoring topic or the second type of monitoring data associated with the monitoring subject to the switch for monitoring by the switch.

[0009] Preferably, step S2 further includes:

[0010] Step S21: Determine the monitoring subject category as readers and / or writers, and determine the monitoring content category as data monitoring and / or packet loss rate monitoring;

[0011] Step S22: When the monitoring content category is data monitoring, set the reader or writer monitoring attribute corresponding to the monitoring topic to be valid, so that the data that performs read or write operations on the monitoring topic is regarded as the second type of monitoring data. When the monitoring content category is packet loss rate monitoring, generate a read and write information table related to the monitoring topic, so that all the data associated with the monitoring topic is regarded as the first type of monitoring data. The read and write information table includes the monitoring topic, node ID, monitoring subject category, and monitoring subject ID.

[0012] Preferably, step S3 further includes:

[0013] For the first type of monitoring data, a first monitoring identifier is sent to the switch. The first monitoring identifier is used to notify the switch to monitor the packet loss rate. The switch counts the number of packets sent and received for each monitoring topic based on the first type of monitoring data, and compares it with the number of packets sent and received for each monitoring topic reported by each communication node to calculate the packet loss rate.

[0014] For the second type of monitoring data, a second monitoring identifier is sent to the switch. The second monitoring identifier is used to notify the switch to monitor the data content.

[0015] Preferably, for the first type of monitoring data, the number of data packets received and sent by each monitoring topic in the read / write information table is periodically collected and sent to the switch together with the read / write information table.

[0016] A second aspect of this application provides a DDS communication data monitoring system for an avionics system. The avionics system includes a switch and various communication nodes interconnected with the switch. Data transmission uses the DDS transmission protocol. This monitoring system is used to monitor data transmitted between software within the communication nodes. The monitoring system includes:

[0017] a monitoring configuration table obtaining module, configured to obtain a monitoring configuration table carrying a monitoring subject, a monitoring subject category and a monitoring content category, which is issued by the switch;

[0018] a monitoring subject and monitoring content marking module, configured to match the monitoring subject in the monitoring configuration table with a subject of the node, and if the subject exists, mark the monitoring subject according to the monitoring subject category and mark the monitoring content according to the monitoring content category;

[0019] a data sending module, configured to send first monitoring data associated with the monitoring subject or second monitoring data associated with the monitoring subject to the switch for monitoring by the switch.

[0020] Preferably, the monitoring subject and monitoring content marking module comprises:

[0021] a monitoring subject and monitoring content determining unit, configured to determine the monitoring subject category as a reader and / or a writer, and determine the monitoring content category as data monitoring and / or packet loss rate monitoring;

[0022] a monitoring data determining unit, configured to, when the monitoring content category is data monitoring, set a reader or writer monitoring attribute corresponding to the monitoring subject as valid, so as to take data subjected to read or write operation on the monitoring subject as the second monitoring data, and when the monitoring content category is packet loss rate monitoring, generate a read-write information table related to the monitoring subject, so as to take all data associated with the monitoring subject as the first monitoring data, wherein the read-write information table comprises the monitoring subject, a node ID, the monitoring subject category and a monitoring subject ID.

[0023] Preferably, the data sending module comprises:

[0024] a monitoring identifier sending unit, configured to, for the first monitoring data, send a first monitoring identifier to the switch, the first monitoring identifier being used to inform the switch to perform packet loss rate monitoring, and according to the first monitoring data, the switch is configured to count a number of packets sent and received by each monitoring subject, and compare the number of packets sent and received by each monitoring subject with a number of packets sent and received by each monitoring subject fed back by each communication node, so as to count a packet loss rate; and for the second monitoring data, send a second monitoring identifier to the switch, the second monitoring identifier being used to inform the switch to perform data content monitoring.

[0025] Preferably, the monitoring identifier sending unit comprises a packet number collecting subunit, configured to, for the first monitoring data, periodically collect a number of data packets received and a number of data packets sent by each monitoring subject in the read-write information table, and send the numbers of data packets to the switch together with the read-write information table.

[0026] The application selectively transmits the data transmitted in each communication node to the bus, and monitors the data by means of the monitoring module of the switch, so as to meet the demand of data monitoring and reduce the power consumption and cost of the product. BRIEF DESCRIPTION OF DRAWINGS

[0027] Figure 1 is a flow chart of a preferred embodiment of the DDS communication data monitoring method of the avionics system of the application. DETAILED DESCRIPTION

[0028] In order to make the purpose, technical scheme and advantages of the application clearer, the technical scheme of the embodiments of the application will be described in more detail below with reference to the drawings. In the drawings, the same or similar notations represent the same or similar elements or elements with the same or similar functions throughout. The described embodiments are part of the embodiments of the application, rather than all the embodiments of the application. The embodiments described below with reference to the drawings are exemplary and are intended to explain the application, and cannot be understood as a limitation of the application. Based on the embodiments in the application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the application. The embodiments of the application will be described in detail below with reference to the drawings.

[0029] The first aspect of the application provides a DDS communication data monitoring method of an avionics system, the avionics system comprising a switch and each communication node interconnected with the switch, the data transmission adopting a DDS transmission protocol, the data being transmitted between each communication node through an FC bus, part of the data in each communication node being transmitted through a RAM, and another part of the data being transmitted by the FC bus through the switch after being selected by the data monitoring method of the application, and the data being monitored by means of the monitoring module of the switch. Therefore, the monitoring method of the application is used to monitor the data transmitted between each software in the communication node, as shown in Figure 1 The monitoring method comprises the following steps:

[0030] Step S1: obtaining a monitoring configuration table carrying a monitoring topic, a monitoring subject category and a monitoring content category issued by the switch;

[0031] Step S2: matching the monitoring topic in the monitoring configuration table with the topic of the node by each communication node, if there is a corresponding topic, marking the monitoring subject according to the monitoring subject category and marking the monitoring content according to the monitoring content category;

[0032] Step S3: sending the first type of monitoring data associated with the monitoring topic or the second type of monitoring data associated with the monitoring subject to the switch, and monitoring by the switch.

[0033] The present application is based on the idea of data publishing and subscription. The switch integrates the subject data or other information that needs to be monitored into a monitoring configuration table and publishes the table to the whole network. Then, in step S1, each communication node receives the monitoring configuration table. In step S2, the required monitoring subject in the monitoring configuration table is matched with the subject published / subscribed by the communication node itself. If there is a corresponding monitoring subject, the relevant data is collected and sent to the switch in step S3.

[0034] The switch monitors the received data or outputs the data sent to itself to a monitoring port, and the monitoring device connected to the monitoring port monitors the data. The present application can solve the problem that the communication data between tasks in the CPU cannot be monitored because the communication data is not output to the bus, and can configure the monitoring content according to the subject, thereby improving the flexibility of bus data monitoring.

[0035] In this embodiment, the monitoring configuration table is shown in Table 1 below and is used to record the configuration information of the network monitoring subject. topicName represents the name of the monitoring subject and is a string, such as position or weather, and NULL ends; monitorType represents the monitoring subject category, 1 represents monitoring readers, 2 represents monitoring writers, 3 represents monitoring readers and writers, and other values are invalid; and monitorContent represents the monitoring content category, 1 represents data monitoring, 2 represents packet loss rate monitoring, 3 represents monitoring data and packet loss rate, and other values are invalid.

[0036] Table 1 Monitoring configuration table

[0037] topicName monitorType monitorContent position 3 1 weather 3 2 weixie 1 3 NULL … …

[0038] The switch is powered on and initialized DDS, and establishes a writer of data monitoring information, with the Qos attribute being persistent (in memory) and reliable transmission. After the communication node is powered on, the DDS is initialized, and a reader of data monitoring information is established, with the Qos attribute being persistent and reliable transmission. After the switch and each communication node are subject-matched, the switch sends the information in the monitoring configuration table to each communication node. After the communication node receives the above monitoring configuration table, the table is stored in the local memory space. Then, in step S2, the monitoring subject in the monitoring configuration table is matched with the existing subject published / subscribed by the node, and the monitoring subject and the monitoring content are marked. For example, the position monitoring subject in Table 1 is matched, the readers and writers in the monitoring subject are marked according to the monitoring subject category with the serial number 3, and the data monitoring in the monitoring content is marked according to the monitoring content with the serial number 1.

[0039] In some optional embodiments, step S2 further includes:

[0040] Step S21, determining that the monitoring subject category is a reader and / or a writer, and determining that the monitoring content category is data monitoring and / or packet loss rate monitoring;

[0041] Step S22, when the monitoring content category is data monitoring, setting the reader or writer monitoring attribute corresponding to the monitoring subject as valid, so as to take the data subjected to the read or write operation of the monitoring subject as the second type of monitoring data; when the monitoring content category is packet loss rate monitoring, generating a read-write information table related to the monitoring subject, so as to take all the data associated with the monitoring subject as the first type of monitoring data, wherein the read-write information table includes the monitoring subject, the node ID, the monitoring subject category, and the monitoring subject ID.

[0042] In this embodiment, the monitoring subject category and the monitoring content category are coupled, when the monitoring content category is data monitoring, the monitoring subject category needs to be considered, and different monitoring subjects are marked, so as to take the data related to the monitoring subject as the first type of monitoring data and upload the data to the switch for monitoring; when the monitoring content category is packet loss rate monitoring, the monitoring subject category is no longer considered, and all the data related to the monitoring subject are taken as the second type of monitoring data and need to be uploaded to the switch for monitoring.

[0043] Taking Table 1 as an example, under the premise that monitorContent is 1, when monitorType is 1, the reader monitoring attribute related to the monitoring subject is set as valid, when monitorType is 2, the writer monitoring attribute related to the monitoring subject is set as valid, and when monitorType is 3, the monitoring attributes of the reader and the writer related to the monitoring subject are both set as valid. Under the premise that monitorContent is 2, all the data of the monitoring subject need to be marked, in order to perform packet loss rate statistics on the data, a read-write information table needs to be constructed at this time, as shown in Table 2. In Table 2, topicName represents the name of the monitoring subject, which is a string, and ends when NULL; moduleID represents the node ID, which is an integer; monitorType represents the monitoring reader or writer, 1 represents the reader, 2 represents the writer, and other values are invalid; and identification represents the ID of the reader or the writer, which is a 64-bit integer.

[0044] Table 2 read-write information table

[0045] topicName moduleID monitorType identification position 0x10000a 1 … weather 0x10000b 1 … weather 0x10000b 2 … weixie 0x10000c 1 … NULL … … …

[0046] Under the premise that monitorContent is 3, both the above two cases are considered.

[0047] Back to Table 1, if the matched monitoring topic of a communication node is position, the monitoring attribute of the reader and the writer of position is set to be valid. If the matched monitoring topic is weather, the data transmitted by all readers and writers of weather is sent to the switch, and the transmission and packet loss rate is counted by the switch. If the matched monitoring topic is weixie, on one hand, the monitoring attribute of the reader of weixie is set to be valid, and the data participated by the reader is counted by the switch alone, on the other hand, the data transmitted by all readers and writers of weixie is sent to the switch, and the packet loss rate is counted by the switch.

[0048] In addition, it should be noted that, in the process of step S2, when a new reader and a new writer are created, the new created reader or writer needs to be matched with the monitoring topic in the monitoring configuration table, and after the matching is successful, the marking processing or the filling in Table 2 is performed.

[0049] In step S3, when the communication node publishes or receives data, for the first type of monitoring data, all the data to be circulated of the monitoring topic is sent to the switch, and after the monitoring by the switch, the data is returned to the communication node and sent to other processing software. For the second type of monitoring data, if the monitoring attribute of the reader or the writer is valid, the corresponding data is sent to the switch.

[0050] In some optional embodiments, step S3 further comprises:

[0051] For the first type of monitoring data, a first monitoring identifier is sent to the switch, the first monitoring identifier is used to inform the switch to perform packet loss rate monitoring, and the switch counts the number of packets sent and received by each monitoring topic according to the first type of monitoring data, and compares the number of packets sent and received by each monitoring topic fed back by each communication node, so as to count the packet loss rate.

[0052] For the second type of monitoring data, a second monitoring identifier is sent to the switch, the second monitoring identifier is used to inform the switch to perform data content monitoring.

[0053] In some optional embodiments, for the first type of monitoring data, the number of data packets received and the number of data packets sent by each monitoring topic in the read-write information table are periodically collected, and are sent to the switch together with the read-write information table.

[0054] In the above embodiments, when the first type of monitoring data or the second type of monitoring data is sent, the monitoring identifier is sent to inform the switch of the type of the data sent by the switch so that the switch can be processed accordingly. For the first type of monitoring data, when the FPGA of the switch receives data whose destination port is the port of the switch and whose data packet information is received, the data packet is submitted to the CPU of the switch. The CPU counts the number of data packets sent and received by each communication node for the same topic, and finally calculates the packet loss rate. The monitoring data is finally output through the monitoring port. For the second type of monitoring data, when the FPGA of the switch receives data whose destination port is the port of the switch and whose data packet information is received, the data packet is forwarded to the monitoring port of the switch.

[0055] The amount of monitoring data of the present application is much smaller than the amount of data communicated between tasks, thereby avoiding the high bandwidth requirement caused by all data on the FC bus, meeting the demand of data monitoring, and reducing the power consumption and cost of the product.

[0056] The second aspect of the present application provides a DDS communication data monitoring system of an avionics system corresponding to the above method. The avionics system includes a switch and each communication node interconnected with the switch. The data transmission adopts the DDS transmission protocol. The monitoring system is used to monitor the data transmitted between each software in the communication node. The monitoring system includes:

[0057] A monitoring configuration table acquisition module is configured to acquire a monitoring configuration table carrying a monitoring topic, a monitoring subject category and a monitoring content category issued by the switch;

[0058] A monitoring subject and monitoring content marking module is configured to match the monitoring topic in the monitoring configuration table with the topic of the node by each communication node. If there is a corresponding topic, the monitoring subject is marked according to the monitoring subject category, and the monitoring content is marked according to the monitoring content category.

[0059] A data sending module is configured to send the first type of monitoring data associated with the monitoring topic or the second type of monitoring data associated with the monitoring subject to the switch for monitoring by the switch.

[0060] In some optional embodiments, the monitoring subject and monitoring content marking module includes:

[0061] A monitoring subject and monitoring content determination unit is configured to determine that the monitoring subject category is a reader and / or a writer, and determine that the monitoring content category is data monitoring and / or packet loss rate monitoring.

[0062] The monitoring data determining unit sets a reader or a writer monitoring attribute corresponding to the monitoring subject as valid to take data of read or write operation on the monitoring subject as the second type of monitoring data when the monitoring content category is data monitoring, and generates a read-write information table related to the monitoring subject to take all data associated with the monitoring subject as the first type of monitoring data when the monitoring content category is packet loss rate monitoring, wherein the read-write information table includes the monitoring subject, the node ID, the monitoring subject category and the monitoring subject ID.

[0063] In some optional embodiments, the data sending module comprises:

[0064] The monitoring identification sending unit sends a first monitoring identification to the switch for the first type of monitoring data, wherein the first monitoring identification is used to inform the switch to perform packet loss rate monitoring, and the switch counts the number of packets sent and received by each monitoring subject according to the first type of monitoring data, and compares the number of packets sent and received by each monitoring subject with the number of packets sent and received by each communication node to count the packet loss rate; and sends a second monitoring identification to the switch for the second type of monitoring data, wherein the second monitoring identification is used to inform the switch to perform data content monitoring.

[0065] In some optional embodiments, the monitoring identification sending unit comprises a packet number collecting sub-unit, which periodically collects the number of data packets received and sent by each monitoring subject in the read-write information table and sends the number of data packets to the switch together with the read-write information table for the first type of monitoring data.

[0066] The above merely describes the specific embodiments of the present application, but the protection scope of the present application is not limited to this. Any changes or replacements within the technical scope disclosed by the present application can be easily thought of by those skilled in the art, and should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for monitoring DDS communication data in an avionics system, wherein the avionics system includes a switch and communication nodes interconnected with the switch, and all data transmissions employ the DDS transmission protocol, characterized in that... This monitoring method is used to monitor the data transmitted between various software programs within a communication node. The method determines a portion of the data transmitted between these software programs via the FC bus and a switch, while other data is transmitted via RAM. The monitoring method includes: Step S1: Obtain the monitoring configuration table published by the switch, which contains the monitoring topic, monitoring subject category, and monitoring content category; Step S2: Each communication node matches the monitoring topic in the monitoring configuration table with the topic of its own node. If a corresponding topic exists, the monitoring subject is marked according to the monitoring subject category, and the monitoring content is marked according to the monitoring content category. Step S3: Send the first type of monitoring data associated with the monitoring topic or the second type of monitoring data associated with the monitoring subject to the switch for monitoring by the switch.

2. The DDS communication data monitoring method for an avionics system as described in claim 1, characterized in that, Step S2 further includes: Step S21: Determine the monitoring subject category as readers and / or writers, and determine the monitoring content category as data monitoring and / or packet loss rate monitoring; Step S22: When the monitoring content category is data monitoring, set the reader or writer monitoring attribute corresponding to the monitoring topic to be valid, so that the data that performs read or write operations on the monitoring topic is regarded as the second type of monitoring data. When the monitoring content category is packet loss rate monitoring, generate a read and write information table related to the monitoring topic, so that all the data associated with the monitoring topic is regarded as the first type of monitoring data. The read and write information table includes the monitoring topic, node ID, monitoring subject category, and monitoring subject ID.

3. The DDS communication data monitoring method for an avionics system as described in claim 2, characterized in that, Step S3 further includes: For the first type of monitoring data, a first monitoring identifier is sent to the switch. The first monitoring identifier is used to notify the switch to monitor the packet loss rate. The switch counts the number of packets sent and received for each monitoring topic based on the first type of monitoring data, and compares it with the number of packets sent and received for each monitoring topic reported by each communication node to calculate the packet loss rate. For the second type of monitoring data, a second monitoring identifier is sent to the switch. The second monitoring identifier is used to notify the switch to monitor the data content.

4. The DDS communication data monitoring method for an avionics system as described in claim 3, characterized in that, For the first type of monitoring data, the number of data packets received and sent by each monitoring topic in the read / write information table are periodically collected and sent to the switch together with the read / write information table.

5. A DDS communication data monitoring system for an avionics system, the avionics system comprising a switch and communication nodes interconnected with the switch, wherein data transmission employs the DDS transmission protocol, characterized in that, This monitoring system is used to monitor the data transmitted between various software programs within a communication node. The system determines a portion of the data transmitted between these programs via the FC bus and a switch, while other data is transmitted via RAM. The monitoring system includes: The monitoring configuration table acquisition module is used to acquire the monitoring configuration table published by the switch, which carries the monitoring topic, monitoring subject category and monitoring content category; The monitoring subject and monitoring content marking module is used by each communication node to match the monitoring topics in the monitoring configuration table with the topics of this node. If a corresponding topic exists, the monitoring subject is marked according to the monitoring subject category, and the monitoring content is marked according to the monitoring content category. The data transmission module is used to send the first type of monitoring data associated with the monitoring topic or the second type of monitoring data associated with the monitoring subject to the switch for monitoring by the switch.

6. The DDS communication data monitoring system for avionics systems as described in claim 5, characterized in that, The monitoring subject and monitoring content marking module includes: The monitoring subject and monitoring content determination unit is used to determine the monitoring subject category as readers and / or writers, and to determine the monitoring content category as data monitoring and / or packet loss rate monitoring. The monitoring data determination unit is used to set the reader or writer monitoring attribute corresponding to the monitoring topic to be valid when the monitoring content category is data monitoring, so that the data that performs read or write operations on the monitoring topic is regarded as the second type of monitoring data. When the monitoring content category is packet loss rate monitoring, it generates a read and write information table related to the monitoring topic, so that all data associated with the monitoring topic is regarded as the first type of monitoring data. The read and write information table includes the monitoring topic, node ID, monitoring subject category, and monitoring subject ID.

7. The DDS communication data monitoring system for avionics systems as described in claim 6, characterized in that, The data transmission module includes: The monitoring identifier sending unit is used to send a first monitoring identifier to the switch for the first type of monitoring data. The first monitoring identifier is used to notify the switch to monitor the packet loss rate. The switch counts the number of packets sent and received for each monitoring topic based on the first type of monitoring data and compares it with the number of packets sent and received for each monitoring topic reported by each communication node to calculate the packet loss rate. For the second type of monitoring data, the unit sends a second monitoring identifier to the switch. The second monitoring identifier is used to notify the switch to monitor the data content.

8. The DDS communication data monitoring system for avionics systems as described in claim 7, characterized in that, The monitoring identifier sending unit includes a packet count collection subunit, which periodically collects the number of data packets received and sent by each monitoring topic in the read / write information table for the first type of monitoring data, and sends them to the switch together with the read / write information table.

Images