CN113312186B - Automatic generation method for inter-partition communication configuration under IMA platform - Google Patents

Abstract

The invention belongs to the field of airborne networks of avionics systems, and particularly relates to an automatic generation method of inter-partition communication configuration under an IMA platform. The method defines an ICD file format firstly, is used for describing the communication requirement of a user, and comprises a partition name, a partition version, a sending port and a receiving port; secondly, automatically generating partition port configuration according to the ICD file of the user communication requirement, wherein the partition port configuration comprises a queue and a sampling port; automatically generating virtual partition port configuration and a partition port-virtual port link relation according to partition port configuration; and finally, automatically generating a mapping relation between the partition ports and the communication ports according to the ICD file of the user communication requirement. The method has the advantages that the inter-partition communication configuration under the IMA platform can be automatically generated according to the communication requirements of the user, and the problems that the traditional manual configuration is complex in work and easy to go on business are solved.

Description

Automatic generation method for inter-partition communication configuration under IMA platform

Technical Field

The invention belongs to the field of airborne networks of avionics systems, and particularly relates to an automatic generation method of inter-partition communication configuration under an IMA platform.

Background

Integrated, modular avionics systems (IMA) have become a major trend in the development of aircraft, being applied to advanced military or civilian aircraft in many cases, and continuing to develop in the direction of high integration. The comprehensive avionics system integrates a plurality of original independent tasks or applications into one computer with high-speed processing capability, so that resource sharing and data fusion are realized, and the performance of the aircraft is improved. In addition, due to the complexity of integration, the integrated electronic system also brings about various problems in reliability, safety and the like. The international ARINC organization developed a robust partitioning concept for avionics system integration, and established ARINC653 standard.

The ARINC653 operating system defined partition communicates through ports and channels. Ports include two types: a sample port and a queue port. As the name suggests, the sampling port refreshes at a refresh rate, holding the most recently refreshed data all the time, while the queue port buffers the received message in a message queue.

However, the communication configuration between the partitions under the IMA platform is completed through manual configuration, so that the work is complicated and errors are easy to occur, and therefore, how to design an automatic generation method for the communication configuration between the partitions under the IMA platform is very necessary.

Disclosure of Invention

In order to solve the problems in the background art, the invention provides an automatic generation method of inter-partition communication configuration under an IMA platform, which solves the problems of complicated work and easy business trip of the traditional manual configuration.

An automatic generation method for inter-partition communication configuration under an IMA platform, the method comprising:

s1, defining a format of an ICD (interface control document) of user communication requirements based on an IMA working scene, wherein the ICD of the user communication requirements is used for describing the user communication requirements;

s2, generating partition port configuration according to the ICD file of the user communication requirement;

s3, generating virtual partition port configuration and a link relation between the partition ports and the virtual partition ports according to the partition port configuration;

s4, generating a link relation between the partition ports and the communication ports according to the ICD file of the user communication requirement.

The technical scheme of the invention is characterized in that:

(1) In S1, the format of the ICD file required for user communication specifically includes: partition name, partition version, transmit port, and receive port.

(2) The transmitting port and the receiving port have the following properties: port name, port type, message size, port source/destination partition;

the port name is used to identify a transmission/reception port name employed for partition communication;

the port types include: EVENT message EVENT and PERIOD message PERIOD;

the message size is used for defining the length of a transmitted/received message, and the message size is smaller than or equal to the maximum message length supported by the bottom communication port;

the port source/destination partition is used to define the source/destination partition for the message.

(3) S2 specifically comprises the following steps:

creating a corresponding partition port according to the port name defined in the ICD file of the user communication requirement, wherein the partition port comprises the following attributes: port name, port type, port direction, message size, queue depth, protocol, refresh frequency.

(4) For port types: if the port type in the ICD file of the user communication requirement is 'EVENT', setting the port type as 'QueuingPort', and if the port type in the ICD file of the user communication requirement is 'PERIOD', setting the port type as 'SamplingPort';

the port name is consistent with the port name in the ICD file of the user communication requirement;

port direction: if the port name in the ICD file of the user communication requirement is a sending port, the port direction is set as SOURCE; if the port name in the ICD file of the user communication requirement is a receiving port, the port direction is set as 'DESTINATION';

message size: the message size of a port in the ICD file is consistent with the communication requirement of the user;

queue depth: if the port type in the ICD file of the user communication requirement is 'EVENT', setting the queue depth value to 10, wherein the queue depth is only applicable to the queue port;

the protocol, if the port name in the ICD file of the user communication requirement is a sending port, the attribute of the protocol is set as SENDER_BLOCK; if the port name in the ICD file of the user communication requirement is a receiving port, the attribute of the protocol is set as NOT_APPLICABLE;

refresh frequency: if the port type in the ICD file is "PERIOD", the value of the refresh rate is set to "INFINITE_TIME", and the refresh rate is only applicable to sampling ports.

(5) S3 specifically comprises the following steps:

creating virtual partitions, sequentially completing the creation of virtual ports in the virtual partitions according to partition port names, and establishing port link relations according to the partition ports and the created virtual ports;

in the process of creating virtual partition, firstly, the name and ID of the existing partition in the module configuration file are obtained _i Then creating a virtual partition with unique name, and setting the created virtual partition ID as Max { ID } _i }+1。

(6) And in the process of sequentially completing the creation of the virtual ports in the virtual partition according to the partition port names, the virtual ports comprise the following attributes:

port type: keeping consistent with the port type in the partition port;

port attribute: set to pseudo_port;

port name: adding a 'pseudo_' character in front of the port name of the partition;

the direction is: opposite to the direction of the partition port; specifically, the partition port direction is "SOURCE", and the virtual port direction should be "DESTINATION"; the partition port direction is 'DESTINATION', and the virtual port direction is 'SOURCE';

message size: the message size defined by the partition ports is kept consistent;

queue depth: keeping consistent with the queue depth defined by the partition ports;

if the attribute of the partition port protocol is NOT_APPLICABLE, the attribute of the virtual port protocol is SENDER_BLOCK; if the attribute of the partition port protocol is "sender_block", the attribute of the virtual port protocol should be "not_application";

drive name: set to "PseudoPQ/virtual port name";

refresh frequency: set to "INFINITE_TIME".

(7) In the process of automatically establishing a port link relation according to the established partition ports and virtual ports, carrying out automatic indexing according to port names;

if the partition port names are consistent with the virtual port names after the 'pseudo_' characters are removed, the partition port names are considered as a group of ports; if the partition port name contains "_Snd", the port is a source port, and the virtual port is a destination port; if the partition port name contains "_rcv", the port is a destination port, and the virtual port is a source port;

and filling partition names corresponding to each group of ports according to the port names, and distributing a channel ID for each group of ports, wherein the initial value is 1.

(8) S4 specifically comprises the following steps:

and reading the bottom network driving communication configuration, automatically matching port names defined in the ICD file of the user communication requirement according to the message type, the message size and the source/destination partition, and taking the matching result as the link relation between the partition ports and the communication ports.

The technical scheme of the invention defines a set of ICD format based on IMA platform working scene, and is used for describing the communication requirement of users; the method can automatically generate partition port configuration according to the ICD file of the user communication requirement; the method can automatically generate virtual partition port configuration and port link relation according to partition port configuration; the method can automatically generate the mapping relation between the partition ports and the communication ports according to the ICD file of the user communication requirement.

Drawings

Fig. 1 is a schematic flow chart of a method for automatically generating inter-partition communication configuration under an IMA platform according to an embodiment of the present invention;

fig. 2 is a schematic diagram of an IMA platform working scenario provided in an embodiment of the present invention;

fig. 3 is a schematic diagram of an ICD file format provided in an embodiment of the present invention;

fig. 4 is a schematic diagram of port information in a GPM1 partition configuration file according to an embodiment of the present invention;

fig. 5 is a schematic diagram of virtual partition configuration in a GPM1 module configuration file according to an embodiment of the present invention;

fig. 6 is a schematic diagram of a port link relationship in a GPM1 module configuration file according to an embodiment of the present invention;

fig. 7 is a schematic diagram of a link relationship between a GPM1 partition port and a communication port according to an embodiment of the present invention;

fig. 8 is a schematic diagram of port information in a GPM2 partition configuration file according to an embodiment of the present invention;

fig. 9 is a schematic diagram of virtual partition configuration in a GPM2 module configuration file according to an embodiment of the present invention;

fig. 10 is a schematic diagram of a port link relationship in a GPM2 module configuration file according to an embodiment of the present invention;

fig. 11 is a schematic diagram of a link relationship between a GPM2 partition port and a communication port according to an embodiment of the present invention.

Detailed Description

The embodiment of the invention provides an automatic generation method of inter-partition communication configuration under an IMA platform, as shown in fig. 1, the method specifically comprises the following steps:

firstly, the embodiment of the invention defines an IMA platform working scenario (see fig. 2), wherein the general processing module 1GMP1 and the general processing module 2GMP2 run a multi-partition operating system for ensuring the reliability of application software.

(1) Defining ICD file according to user communication demand

Fig. 3 is an ICD file format, specifically including a partition name, a partition version, a transmitting port, and a receiving port. If multiple partitions are involved in the communication, separate definitions should be made. Wherein the port parameters are defined as follows:

port name: the name of the transmitting/receiving port used for identifying the partition communication should have uniqueness, and for convenience of understanding, the name naming rule of the transmitting port is "module name_snd_xxx", wherein xxx is a port serial number, and the initial value is 001; the name naming rule of the receiving port is 'module name_rcv_xxx', wherein xxx is port serial number, and the initial value is 001;

port type: divided into EVENT messages (EVENT) and PERIOD messages (PERIOD);

message size: to define a send/receive message length that should not exceed the maximum message length supported by the underlying communication ports (AFDX, FC);

port source/destination partition: to define the source/destination partition of the message.

(2) Automatic generation of partition port configuration from ICD file

To implement the automatic generation of partition port configuration in fig. 4 and 8, the method proposed herein creates a corresponding partition port according to the port name defined in the ICD file, and the partition port attribute is defined as follows:

port type: if the port type in the ICD file is "EVENT", the port type is set as "QueuingPort", and if the port type in the ICD file is "PERIOD", the port type is set as "samplingPort";

port Name (Name): keeping consistent with the port name in the ICD file;

port Direction (Direction): if the port in the ICD file is a transmitting port, the attribute is set as SOURCE; if the port in the ICD file is a receiving port, the attribute is set to be DESTINATION;

message size (MessageSize): the port message size in the ICD file is kept consistent;

queue depth (queue length): if the port type in the ICD file is "EVENT", the attribute value is set to 10, and the attribute is only applicable to the queue port;

a Protocol (Protocol) that if the port in the ICD file is a transmission port, the attribute is set to "sender_block" (transmission BLOCK); if the port in the ICD file is a receiving port, the attribute is set as 'NOT_APPLICABLE';

refresh frequency (refresh rate): if the port type in the ICD file is "PERIOD", the attribute value is set to "INFINITE_TIME", and the attribute is applicable only to sampling ports.

(3) Automatic generation of virtual port configuration and port link relationships based on partition port configuration

In order to realize the configuration of virtual partition ports in fig. 5 and fig. 9 and the automatic generation of the port link relationship in fig. 6 and fig. 10, the method proposed herein firstly completes the creation of the virtual partition, secondly completes the creation of the virtual ports in turn according to the partition port names, and finally automatically establishes the port link relationship according to the created partition ports and the virtual ports.

In the virtual partition creation process, the method will first obtain the name and ID of the existing partition in the module configuration file (module. Xml) _i Then create a virtual partition (e.g., pse) with unique name and set partition ID to Max { ID } _i }+1。

In the virtual port creation process, the method sequentially completes the virtual port creation according to the partition port names, and the virtual port attribute definition is as follows:

port type: consistent with definition in partition ports;

port Attribute (Attribute): set to pseudo_port;

port Name (Name): adding a 'pseudo_' character in front of the original partition port name;

direction (Direction): opposite to the partition port direction, such as: the partition port direction is SOURCE, and the virtual port direction is DESTINATION; the partition port direction is "DESTINATION" and the virtual port direction should be "SOURCE".

Message size: keeping the message size consistent with the partition definition port;

queue depth (queue length): the depth of the queue of the port is consistent with that of the partition definition, and the method is applicable to the port of the queue only;

protocol (Protocol) if the partition port Protocol attribute is "NOT_APPLICABLE", the virtual port Protocol attribute should be "SENDER_BLOCK"; the partition port protocol attribute is "sender_block", and the virtual port protocol attribute should be "not_application";

drive name (DriverName): set to "PseudoPQ/virtual port name";

refresh frequency (refresh rate): set to "INFINITE_TIME" only applies to the sampling port.

In the process of automatically establishing the port link relation according to the established partition port and the virtual port, the method automatically indexes according to the port names, and if the partition port names and the virtual port names are consistent after the 'pseudo_' characters are removed, the partition port names and the virtual port names are considered to be a group of ports. If the partition port name contains "_Snd", the port is a source port, and the virtual port is a destination port; if the partition port name contains "_rcv", the port is the destination port and the virtual port is the source port. According to the method, the partition names corresponding to each group of ports are filled according to the port names, a channel ID is allocated to each group of ports, and the initial value is 1.

(4) Map. Txt of partition port and communication port mapping file is automatically generated according to ICD file

The underlying communication ports referred to herein are network driven (AFDX, FC) communication ports, which typically run at the core operating system layer (COS), each representing a communication link, should contain a communication port number, a message type (event/period), a message size, and a source/destination partition name.

In order to realize the automatic generation of the mapping relationship between the partition ports and the communication ports in fig. 7 and 11, the method provided herein firstly reads the underlying network driving communication configuration, then automatically matches the port names defined in the ICD according to the message type, the message size and the source/destination partition, and finally saves the matching result to the map.

The technical scheme of the invention defines a set of ICD format based on IMA platform working scene, and is used for describing the communication requirement of users; the method can automatically generate partition port configuration according to the ICD file of the user communication requirement; the method can automatically generate virtual partition port configuration and port link relation according to partition port configuration; the method can automatically generate the mapping relation between the partition ports and the communication ports according to the ICD file of the user communication requirement.

Claims (7)

1. An automatic generation method for inter-partition communication configuration under an IMA platform, which is characterized by comprising the following steps:

s1, defining a format of an ICD (interface control document) of user communication requirements based on an IMA working scene, wherein the ICD of the user communication requirements is used for describing the user communication requirements;

s2, generating partition port configuration according to the ICD file of the user communication requirement;

s3, generating virtual partition port configuration and a link relation between the partition ports and the virtual partition ports according to the partition port configuration; s3 specifically comprises the following steps:

creating virtual partitions, sequentially completing the creation of virtual ports in the virtual partitions according to partition port names, and establishing port link relations according to the partition ports and the created virtual ports;

in the process of creating virtual partition, firstly, a module configuration file is obtainedName and ID of the existing partition in the list _i Then creating a virtual partition with unique name, and setting the created virtual partition ID as Max { ID } _i }+1；

And in the process of sequentially completing the creation of the virtual ports in the virtual partition according to the partition port names, the virtual ports comprise the following attributes:

port type: keeping consistent with the port type in the partition port;

port attribute: set to pseudo_port;

port name: adding a 'pseudo_' character in front of the port name of the partition;

the direction is: opposite to the direction of the partition port; specifically, the partition port direction is "SOURCE", and the virtual port direction should be "DESTINATION"; the partition port direction is 'DESTINATION', and the virtual port direction is 'SOURCE';

message size: the message size defined by the partition ports is kept consistent;

queue depth: keeping consistent with the queue depth defined by the partition ports;

if the attribute of the partition port protocol is NOT_APPLICABLE, the attribute of the virtual port protocol is SENDER_BLOCK; if the attribute of the partition port protocol is "sender_block", the attribute of the virtual port protocol should be "not_application";

drive name: set to "PseudoPQ/virtual port name";

refresh frequency: set to "INFINITE_TIME";

s4, generating a link relation between the partition ports and the communication ports according to the ICD file of the user communication requirement.

2. The method for automatically generating inter-partition communication configuration under an IMA platform according to claim 1, wherein in S1, the format of the ICD file of the user communication requirement specifically includes: partition name, partition version, transmit port, and receive port.

3. The method for automatically generating inter-partition communication configuration under an IMA platform according to claim 2, wherein the transmitting port and the receiving port have the following properties: port name, port type, message size, port source/destination partition;

the port name is used to identify a transmission/reception port name employed for partition communication;

the port types include: EVENT message EVENT and PERIOD message PERIOD;

the message size is used for defining the length of a transmitted/received message, and the message size is smaller than or equal to the maximum message length supported by the bottom communication port;

the port source/destination partition is used to define the source/destination partition for the message.

4. The method for automatically generating inter-partition communication configuration under an IMA platform according to claim 1, wherein S2 specifically is:

creating a corresponding partition port according to the port name defined in the ICD file of the user communication requirement, wherein the partition port comprises the following attributes: port name, port type, port direction, message size, queue depth, protocol, refresh frequency.

5. An inter-partition communication configuration automatic generation method under an IMA platform according to claim 4, wherein,

for port types: if the port type in the ICD file of the user communication requirement is 'EVENT', setting the port type as 'QueuingPort', and if the port type in the ICD file of the user communication requirement is 'PERIOD', setting the port type as 'SamplingPort';

the port name is consistent with the port name in the ICD file of the user communication requirement;

port direction: if the port name in the ICD file of the user communication requirement is a sending port, the port direction is set as SOURCE; if the port name in the ICD file of the user communication requirement is a receiving port, the port direction is set as 'DESTINATION';

message size: the message size of a port in the ICD file is consistent with the communication requirement of the user;

queue depth: if the port type in the ICD file of the user communication requirement is 'EVENT', setting the queue depth value to 10, wherein the queue depth is only applicable to the queue port;

the protocol, if the port name in the ICD file of the user communication requirement is a sending port, the attribute of the protocol is set as SENDER_BLOCK; if the port name in the ICD file of the user communication requirement is a receiving port, the attribute of the protocol is set as NOT_APPLICABLE;

refresh frequency: if the port type in the ICD file is "PERIOD", the value of the refresh rate is set to "INFINITE_TIME", and the refresh rate is only applicable to sampling ports.

6. The method for automatically generating inter-partition communication configuration under an IMA platform according to claim 1, wherein in the process of automatically establishing a port link relationship according to the created partition port and virtual port, automatic indexing is performed according to the port name;

if the partition port names are consistent with the virtual port names after the 'pseudo_' characters are removed, the partition port names are considered as a group of ports; if the partition port name contains "_Snd", the port is a source port, and the virtual port is a destination port; if the partition port name contains "_rcv", the port is a destination port, and the virtual port is a source port;

and filling partition names corresponding to each group of ports according to the port names, and distributing a channel ID for each group of ports, wherein the initial value is 1.

7. The method for automatically generating inter-partition communication configuration under an IMA platform according to claim 1, wherein S4 specifically is:

and reading the bottom network driving communication configuration, automatically matching port names defined in the ICD file of the user communication requirement according to the message type, the message size and the source/destination partition, and taking the matching result as the link relation between the partition ports and the communication ports.