DDS communication data monitoring method and system of avionics system

Abstract

The invention 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. The method comprises the following steps: S1, acquiring a monitoring configuration table which is published by the switch and carries a monitoring theme, a monitoring subject category and a monitoring content category; s2, each communication node matches the monitoring theme in the monitoring configuration table with the theme of the node, and if the corresponding theme exists, the monitoring subject is marked according to the type of the monitoring subject, and the monitoring content is marked according to the type of the monitoring content; and 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 performing monitoring by the switch. According to the invention, the data transmitted in each communication node is selectively transmitted by the bus, and data monitoring is carried out by means of the monitoring module of the switch, so that the requirement of data monitoring can be met, and the power consumption and the cost of the product are reduced.

Description

Technical Field

[0001] The present application belongs to the technical field of aircraft bus data management, and in particular, relates to a DDS communication data monitoring method and system for an avionics system. Background Art

[0002] As the core computer processing platform for the control and management of avionics systems, the integrated processing unit (ICP) has the ability of high-speed information processing and data calculation. The integrated processing unit is mainly composed of multiple data processing units (DPUs), which are interconnected through the FC bus and use DDS as the communication entity to provide a high-speed switching network for various application software. The multiple application software on the same processor node (also called the communication node) of the integrated processing unit adopts the DDS+RAM communication mode, that is, data is exchanged directly through the memory, while the application programs between processors adopt the DDS+FC communication mode, that is, data is transmitted through the switch. This method can ensure that the communication between the application programs within the processor does not occupy network resources, greatly saving the overhead of network resources and reducing the power consumption and cost of the product.

[0003] The network data monitoring of traditional avionics systems is based on the input and output ports of the switch. Data can only be monitored when it is transmitted in the network. As a result, the data transmitted through RAM between tasks in the same processor cannot be monitored, which makes system troubleshooting difficult 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 placed on the network, increasing the power consumption and cost of the product. Summary of the invention

[0004] In order to solve the above problems, the present application provides a DDS communication data monitoring method and system for an avionics system to solve the problem of monitoring the internal data of each communication node.

[0005] In a first aspect, the present application provides a DDS communication data monitoring method for an avionics system, wherein the avionics system includes a switch and communication nodes interconnected with the switch, and the DDS transmission protocol is used for data transmission. The monitoring method is used to monitor data transmitted between software inside the communication node, and the monitoring method includes:

[0006] Step S1, obtaining a monitoring configuration table containing monitoring topics, monitoring subject categories and monitoring content categories issued by the switch;

[0007] Step S2: Each communication node matches the monitoring subject in the monitoring configuration table with the subject of the node. If a corresponding subject 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 subject or the second type of monitoring data associated with the monitoring subject to the switch for monitoring.

[0009] Preferably, step S2 further comprises:

[0010] Step S21, determining the monitoring subject category as reader and / or writer, and determining the monitoring content category as data monitoring and / or packet loss rate monitoring;

[0011] Step S22: When the monitoring content category is data monitoring, the reader or writer monitoring attribute corresponding to the monitoring subject is set to valid, so that the data for reading or writing operations on the monitoring subject is taken as the second type of monitoring data; when the monitoring content category is packet loss rate monitoring, a read-write information table related to the monitoring subject is generated, so that all data associated with the monitoring subject is taken as the first type of monitoring data, and the read-write information table includes the monitoring subject, node ID, monitoring subject category, and monitoring subject ID.

[0012] Preferably, step S3 further comprises:

[0013] For the first type of monitoring data, a first monitoring identifier is sent to the switch, where 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 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 to count the packet loss rate.

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

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

[0016] In a second aspect, the present application provides a DDS communication data monitoring system for an avionics system, wherein the avionics system includes a switch and communication nodes interconnected with the switch, and the DDS transmission protocol is used for data transmission. The monitoring system is used to monitor data transmitted between software inside the communication node, and the monitoring system includes:

[0017] A monitoring configuration table acquisition module, used to acquire a monitoring configuration table containing monitoring topics, monitoring subject categories and monitoring content categories issued by the switch;

[0018] The monitoring subject and monitoring content marking module is used for each communication node to match the monitoring subject in the monitoring configuration table with the subject of the node. If there is a corresponding subject, the monitoring subject is marked according to the monitoring subject category, and the monitoring content is marked according to the monitoring content category;

[0019] The data sending module is used to send 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 for monitoring by the switch.

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

[0021] A monitoring subject and monitoring content determination unit, used 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 determination unit is used to set the reader or writer monitoring attribute corresponding to the monitoring subject to be valid when the monitoring content category is data monitoring, so as to treat the data for reading or writing the monitoring subject as the second type of monitoring data; when the monitoring content category is packet loss rate monitoring, generate a read-write information table related to the monitoring subject, so as to treat all data associated with the monitoring subject as the first type of monitoring data, wherein the read-write information table includes the monitoring subject, node ID, monitoring subject category, and monitoring subject ID.

[0023] Preferably, the data sending module includes:

[0024] The monitoring identifier sending unit is used to send a first monitoring identifier to the switch for the first type of monitoring data, wherein the first monitoring identifier is used to notify the switch to perform packet loss rate monitoring. The switch counts the number of packets sent and received by each monitoring subject based on the first type of monitoring data, and compares the number of packets sent and received by each monitoring subject fed back by each communication node to count the packet loss rate; and for the second type of monitoring data, sends a second monitoring identifier to the switch, wherein the second monitoring identifier is used to notify the switch to perform data content monitoring.

[0025] Preferably, the monitoring identification sending unit includes a packet number collecting subunit, which is used to periodically collect the number of data packets received and sent by each monitoring subject in the read-write information table for the first type of monitoring data, and send it to the switch together with the read-write information table.

[0026] The present application selectively transmits the data transmitted within each communication node to the bus for transmission, and uses the monitoring module of the switch to monitor the data, which can not only meet the needs of data monitoring, but also reduce the power consumption and cost of the product. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0028] In order to make the purpose, technical scheme and advantages of the implementation of this application clearer, the technical scheme in the implementation of this application will be described in more detail in combination with the drawings in the implementation of this application. In the drawings, the same or similar reference numerals throughout represent the same or similar elements or elements with the same or similar functions. The described implementation is a part of the implementation of this application, not all of the implementations. The implementation described below with reference to the drawings is exemplary and is intended to be used to explain this application, and cannot be understood as a limitation on this application. Based on the implementation in this application, all other implementations obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application. The implementation of this application is described in detail below in combination with the drawings.

[0029] In a first aspect, the present application provides a DDS communication data monitoring method for an avionics system, wherein the avionics system includes a switch and communication nodes interconnected with the switch, wherein the DDS transmission protocol is used for data transmission, wherein data is transmitted between communication nodes via an FC bus, wherein part of the data within each communication node is transmitted via RAM, and another part of the data is selected by the data monitoring method of the present application and transmitted via the FC bus via the switch, and data monitoring is performed with the aid of a monitoring module of the switch. Therefore, the monitoring method of the present application is used to monitor data transmitted between software within the communication node, such as Figure 1 As shown, the monitoring method includes:

[0030] Step S1, obtaining a monitoring configuration table containing monitoring topics, monitoring subject categories and monitoring content categories issued by the switch;

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

[0032] Step S3: Send 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 for monitoring.

[0033] This 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 it to the entire network. Then, in step S1, each communication node receives the monitoring configuration table. Then, in step S2, the monitoring subject required in the monitoring configuration table is matched with the subject of its own publication / subscription. After the corresponding monitoring subject exists, the relevant data is collected and the monitoring content is sent to the switch in step S3.

[0034] The switch monitors the received data, or outputs the data sent to itself to the monitoring port, and the monitoring device connected to the monitoring port monitors the data. This application can solve the problem that the communication data between tasks in the CPU cannot be monitored because the communication data through the memory is not output to the bus, and the monitoring content can be configured according to the topic, which improves the flexibility of bus data monitoring.

[0035] In this embodiment, the monitoring configuration table is shown in Table 1 below, which is used to record the configuration information of the monitoring topic of the entire network. topicName represents the name of the monitoring topic, which is a string, such as position, weather, and ends when it is NULL; monitorType represents the monitoring subject category, 1 represents monitoring readers, 2 represents monitoring writers, 3 represents monitoring readers and writers, and others are invalid; 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 others 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 initializes DDS to establish a writer of data monitoring information, whose Qos attributes are persistence (memory) and reliable transmission; the communication node is powered on and initializes DDS to establish a reader of data monitoring information, whose Qos attributes are persistence and reliable transmission; after the switch matches the subject of each communication node, it sends the information in the monitoring configuration table to each communication node. After receiving the above monitoring configuration table, the communication node stores it in the local memory space. Then in step S2, the monitoring subject in the monitoring configuration table is matched with the existing topic published / subscribed by this node, and the monitoring subject and monitoring content are marked. For example, if 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 serial number 3, and the data monitoring in the monitoring content is marked according to the monitoring content with serial number 1.

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

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

[0041] Step S22: When the monitoring content category is data monitoring, the reader or writer monitoring attribute corresponding to the monitoring subject is set to valid, so that the data for reading or writing operations on the monitoring subject is taken as the second type of monitoring data; when the monitoring content category is packet loss rate monitoring, a read-write information table related to the monitoring subject is generated, so that all data associated with the monitoring subject is taken as the first type of monitoring data, and the read-write information table includes the monitoring subject, node ID, monitoring subject category, and monitoring subject ID.

[0042] In this embodiment, there is a coupling relationship between the monitoring subject category and the monitoring content category. When the monitoring content category is data monitoring, the monitoring subject category needs to be considered and different monitoring subjects need to be marked so that the data involved in the monitoring subject can be uploaded to the switch for monitoring as the first type of monitoring data. When the monitoring content category is packet loss rate monitoring, the monitoring subject category is no longer considered, and all data related to the monitoring subject needs to be uploaded to the switch for monitoring as the second type of monitoring data.

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

[0044] Table 2 Read and 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 of the above situations are considered.

[0047] Back to Table 1, if the monitoring topic matched by a communication node is position, the monitoring attributes of the readers and writers of position are set to valid. If the monitoring topic matched is weather, the data transmitted by all readers and writers of weather are sent to the switch, and the switch transmits and counts the packet loss rate. If the monitoring topic matched is weixie, on the one hand, the reader monitoring attribute of weixie is set to valid, and the data participated by the reader will be monitored separately by the switch. At the same time, the data transmitted by all readers and writers of weixie will also be sent to the switch, and the switch will count the packet loss rate.

[0048] It should also be noted that when new readers and writers are created during the communication node's execution of step S2, the newly created readers or writers need to be matched with the monitoring topics in the monitoring configuration table. After a successful match, they are marked or reported to Table 2.

[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 subject are sent to the switch, which returns to the communication node after monitoring and sends it to other processing software. For the second type of monitoring data, the monitoring attribute of the reader or writer is searched, and if the monitoring attribute is valid, the corresponding data is sent to the switch.

[0050] In some optional implementations, step S3 further includes:

[0051] For the first type of monitoring data, a first monitoring identifier is sent to the switch, where 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 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 to count the packet loss rate.

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

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

[0054] In the above embodiment, when the first type of monitoring data or the second type of monitoring data is sent, the switch is informed of the type of data sent by sending a monitoring identifier so that the switch can perform targeted processing. 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 is data packet information, the data packet is submitted to the CPU of the switch. The CPU integrates the number of data packets sent and received by each communication node with the same topic, and finally calculates the packet loss rate. The monitoring data is finally formed and 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 is monitoring data, it is forwarded to the monitoring port of the switch.

[0055] The amount of monitoring data in this application is much smaller than the amount of data communicated between tasks, thereby avoiding the high bandwidth requirements brought by the FC bus for all data, which can not only meet the needs of data monitoring, but also reduce the power consumption and cost of the product.

[0056] In a second aspect, the present application provides a DDS communication data monitoring system for an avionics system corresponding to the above method, wherein the avionics system includes a switch and communication nodes interconnected with the switch, and the DDS transmission protocol is used for data transmission. The monitoring system is used to monitor data transmitted between software inside the communication node, and the monitoring system includes:

[0057] A monitoring configuration table acquisition module, used to acquire a monitoring configuration table containing monitoring topics, monitoring subject categories and monitoring content categories issued by the switch;

[0058] The monitoring subject and monitoring content marking module is used for each communication node to match the monitoring subject in the monitoring configuration table with the subject of the node. If there is a corresponding subject, the monitoring subject is marked according to the monitoring subject category, and the monitoring content is marked according to the monitoring content category;

[0059] The data sending module is used to send 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 for monitoring by the switch.

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

[0061] A monitoring subject and monitoring content determination unit, used 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;

[0062] A monitoring data determination unit is used to set the reader or writer monitoring attribute corresponding to the monitoring subject to be valid when the monitoring content category is data monitoring, so as to treat the data for reading or writing the monitoring subject as the second type of monitoring data; when the monitoring content category is packet loss rate monitoring, generate a read-write information table related to the monitoring subject, so as to treat all data associated with the monitoring subject as the first type of monitoring data, wherein the read-write information table includes the monitoring subject, node ID, monitoring subject category, and monitoring subject ID.

[0063] In some optional implementations, the data sending module includes:

[0064] The monitoring identifier sending unit is used to send a first monitoring identifier to the switch for the first type of monitoring data, wherein the first monitoring identifier is used to notify the switch to perform packet loss rate monitoring. The switch counts the number of packets sent and received by each monitoring subject based on the first type of monitoring data, and compares the number of packets sent and received by each monitoring subject fed back by each communication node to count the packet loss rate; and for the second type of monitoring data, sends a second monitoring identifier to the switch, wherein the second monitoring identifier is used to notify the switch to perform data content monitoring.

[0065] In some optional embodiments, the monitoring identification sending unit includes a packet number collection subunit, which is used to periodically collect the number of data packets received and the number of data packets sent by each monitoring subject in the read-write information table for the first type of monitoring data, and send it to the switch together with the read-write information table.

[0066] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A method for monitoring DDS communication data of an avionics system, wherein the avionics system comprises a switch and communication nodes interconnected with the switch, and the DDS transmission protocol is used for data transmission, wherein: The monitoring method is used to monitor data transmitted between various software within a communication node, and the monitoring method includes: Step S1, obtaining a monitoring configuration table containing monitoring topics, monitoring subject categories and monitoring content categories issued by the switch; Step S2: Each communication node matches the monitoring subject in the monitoring configuration table with the subject of the node. If a corresponding subject 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 subject or the second type of monitoring data associated with the monitoring subject to the switch for monitoring.

2. The DDS communication data monitoring method of an avionics system according to claim 1, characterized in that: Step S2 further comprises: Step S21, determining the monitoring subject category as reader and / or writer, and determining the monitoring content category as data monitoring and / or packet loss rate monitoring; Step S22: When the monitoring content category is data monitoring, the reader or writer monitoring attribute corresponding to the monitoring subject is set to valid, so that the data for reading or writing operations on the monitoring subject is taken as the second type of monitoring data; when the monitoring content category is packet loss rate monitoring, a read-write information table related to the monitoring subject is generated, so that all data associated with the monitoring subject is taken as the first type of monitoring data, and the read-write information table includes the monitoring subject, node ID, monitoring subject category, and monitoring subject ID.

3. The DDS communication data monitoring method of an avionics system according to claim 2, characterized in that: Step S3 further comprises: For the first type of monitoring data, a first monitoring identifier is sent to the switch, where 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 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 to count the packet loss rate. For the second type of monitoring data, a second monitoring identifier is sent to the switch, where the second monitoring identifier is used to notify the switch to perform data content monitoring.

4. The DDS communication data monitoring method of an avionics system according to claim 3, characterized in that: For the first type of monitoring data, the number of data packets received and the number of data packets sent by each monitoring subject 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 the DDS transmission protocol is used for data transmission, and the system is characterized in that: The monitoring system is used to monitor the data transmitted between the various software in the communication node, and the monitoring system includes: A monitoring configuration table acquisition module, used to acquire a monitoring configuration table containing monitoring topics, monitoring subject categories and monitoring content categories issued by the switch; The monitoring subject and monitoring content marking module is used for each communication node to match the monitoring subject in the monitoring configuration table with the subject of the node. If there is a corresponding subject, 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 sending module is used to send 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 for monitoring by the switch.

6. The DDS communication data monitoring system for an avionics system as claimed in claim 5, characterized in that: The monitoring subject and monitoring content marking module includes: A monitoring subject and monitoring content determination unit, used 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; A monitoring data determination unit is used to set the reader or writer monitoring attribute corresponding to the monitoring subject to be valid when the monitoring content category is data monitoring, so as to treat the data for reading or writing the monitoring subject as the second type of monitoring data; when the monitoring content category is packet loss rate monitoring, generate a read-write information table related to the monitoring subject, so as to treat all data associated with the monitoring subject as the first type of monitoring data, wherein the read-write information table includes the monitoring subject, node ID, monitoring subject category, and monitoring subject ID.

7. The DDS communication data monitoring system for an avionics system as claimed in claim 6, characterized in that: The data sending module comprises: The monitoring identifier sending unit is used to send a first monitoring identifier to the switch for the first type of monitoring data, wherein the first monitoring identifier is used to notify the switch to perform packet loss rate monitoring. The switch counts the number of packets sent and received by each monitoring subject based on the first type of monitoring data, and compares the number of packets sent and received by each monitoring subject fed back by each communication node to count the packet loss rate; and for the second type of monitoring data, sends a second monitoring identifier to the switch, wherein the second monitoring identifier is used to notify the switch to perform data content monitoring.

8. The DDS communication data monitoring system for an avionics system as claimed in claim 7, characterized in that: The monitoring identification sending unit includes a packet number collecting subunit, which is used to periodically collect the number of data packets received and sent by each monitoring subject in the read-write information table for the first type of monitoring data, and send it to the switch together with the read-write information table.

Images