An aircraft information class interface data configuration management method

Abstract

The application belongs to the technical field of aircraft information interface management, and particularly relates to a kind of aircraft information interface data configuration management methods.The method comprises the following steps: step S1, determining the interface relationship of each aircraft equipment;Step S2, determining the information interface type between each aircraft equipment with interface relationship;Step S3, defining each information interface, forming an interface definition file carrying an interface version number;Step S4, packaging the information interface between each aircraft equipment, among every two aircraft equipment, all information interfaces belonging to non-bus type are packaged into an interface configuration item, and all information interfaces belonging to the same bus type are packaged into an interface configuration item;Step S5, defining and signing the content of the interface configuration item in the interface configuration file.The application can conveniently complete the change and confirmation of interface information, and improve the processing efficiency of information interface control software.

Description

Technical Field

[0001] This application belongs to the field of aircraft information interface management technology, and specifically relates to a method for configuring and managing aircraft information interface data. Background Technology

[0002] Aircraft are highly complex systems, typically consisting of multiple systems and over a hundred devices, including flight control, electromechanical, avionics, and support systems, in addition to the aircraft platform itself. To ensure flight safety and mission success, these systems and devices must maintain coordinated and smooth information transmission. Meanwhile, different systems often use different interface types, such as non-bus interfaces (analog signals, discrete signals, audio signals, video signals, etc.) and bus interfaces (RS-422 bus, GJB289A bus, fiber optic bus, 1394B bus, etc.). This results in a very large number of interfaces and highly complex interconnections, posing a significant challenge to the management of aircraft information interfaces.

[0003] Currently, there are two main methods for managing aircraft information interfaces, both of which have significant shortcomings. The first is document-based information interface design and management, where specific interface information is recorded and transmitted in the form of text tables. This method struggles to ensure data consistency and is inconvenient for querying and version maintenance. The second method involves developing ICD (Interface Control Document) definition software for some bus information interfaces. This software can define and store individual information interfaces, but the storage capacity and technical approval workload are enormous. Considering the integrated connections between information interfaces, controlling changes to these interfaces is difficult. For example, changing one piece of information may require changes to all related information interfaces, making it difficult to ensure synchronized implementation and confirmation. Summary of the Invention

[0004] To address the aforementioned issues, this application provides a method for managing the configuration of aircraft information interface data, which packages several information interfaces between devices and manages them uniformly for version upgrades.

[0005] The aircraft information interface data configuration management method provided in this application mainly includes:

[0006] Step S1: Determine the interface relationships of each aircraft device;

[0007] Step S2: Determine the interface types of each information class between various aircraft equipment that have interface relationships;

[0008] Step S3: Define the information interfaces between each pair of aircraft equipment to form an interface definition file carrying the interface version number;

[0009] Step S4: Package the information interfaces between each aircraft device according to the interface configuration rules. Between every two aircraft devices, all information interfaces belonging to non-bus types are packaged into one interface configuration item, and all information interfaces belonging to the same bus type are packaged into one interface configuration item, forming an interface configuration file carrying the interface configuration item version number.

[0010] Step S5: Define and approve the interface configuration items in the interface configuration file;

[0011] Step S6: When making changes to the information class interface, determine the information class interface that needs to be changed;

[0012] Step S7: Based on the interface relationships of each aircraft device, determine all interfaces involved in the change;

[0013] Step S8: Complete the content changes for all information class interfaces and upgrade the version number of the interface definition file;

[0014] Step S9: Determine the valid versions of all information class interfaces in the interface configuration items;

[0015] Step S10: Upgrade the version number of the interface configuration item;

[0016] Step S11: Define and approve the content of the changed interface configuration items.

[0017] Preferably, in step S1, the interface relationships of each aircraft device are recorded using an N-squared diagram. The N-squared diagram lists all aircraft devices in both the vertical and horizontal headers. The interface relationships between the horizontal and vertical aircraft devices are marked at their intersections. The interface relationships include connected or disconnected connections.

[0018] Preferably, in step S2, the interface type includes non-bus interfaces and bus interfaces. The non-bus interfaces include, but are not limited to, analog signal interfaces, discrete signal interfaces, audio signal interfaces, and video signal interfaces. The bus interfaces include, but are not limited to, RS422 bus, GJB289A bus, fiber optic bus, and 1394B bus.

[0019] Preferably, in step S3, defining the information class interface includes:

[0020] Obtain the interface definition file template specified by the standard for the interface type;

[0021] The interface definition file is generated by obtaining the information filled in by the aircraft equipment at both ends of the interface based on the interface definition file template provided by the designer.

[0022] Determine the interface version number in the interface definition file.

[0023] Preferably, the version number of the interface in the interface definition file is marked with a letter, and the version number of the interface configuration item in the interface configuration file is marked with Arabic numerals.

[0024] Preferably, step S7 further includes:

[0025] Determine the source device to which the information class interface to be modified belongs;

[0026] Based on the interface relationships of each aircraft device, determine all target devices connected to the source device;

[0027] In each interface from the source device to the target device, determine whether it contains an information class interface to be changed, and then determine all interfaces involved in the change.

[0028] This application can effectively reduce the scale of information interface management, while facilitating the modification and confirmation of interface information. It can further improve the processing efficiency of information interface control software and improve management logic, thereby supporting the rapid review, reuse and efficient change control of information interface data, and improving the R&D quality of complex aircraft cross-linking interfaces. Attached Figure Description

[0029] Figure 1 This is a flowchart illustrating a preferred embodiment of the aircraft information interface data configuration management method of this application.

[0030] Figure 2 This application Figure 1 The flowchart of the modified embodiment shown.

[0031] Figure 3 This application Figure 1 The N-squared diagram of the illustrated embodiment. Detailed Implementation

[0032] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be described in more detail below with reference to the accompanying drawings. In the drawings, the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The described embodiments are only some, not all, of the embodiments of this application. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application. The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0033] This application provides a method for configuring and managing aircraft information interface data, such as... Figure 1 and Figure 2 As shown, it mainly includes:

[0034] Step S1: Determine the interface relationships of each aircraft device;

[0035] Step S2: Determine the interface types of each information class between various aircraft equipment that have interface relationships;

[0036] Step S3: Define the information interfaces between each pair of aircraft equipment to form an interface definition file carrying the interface version number;

[0037] Step S4: Package the information interfaces between each aircraft device according to the interface configuration rules. Between every two aircraft devices, all information interfaces belonging to non-bus types are packaged into one interface configuration item, and all information interfaces belonging to the same bus type are packaged into one interface configuration item, forming an interface configuration file carrying the interface configuration item version number.

[0038] Step S5: Define and approve the interface configuration items in the interface configuration file;

[0039] Step S6: When making changes to the information class interface, determine the information class interface that needs to be changed;

[0040] Step S7: Based on the interface relationships of each aircraft device, determine all interfaces involved in the change;

[0041] Step S8: Complete the content changes for all information class interfaces and upgrade the version number of the interface definition file;

[0042] Step S9: Determine the valid versions of all information class interfaces in the interface configuration items;

[0043] Step S10: Upgrade the version number of the interface configuration item;

[0044] Step S11: Define and approve the content of the changed interface configuration items.

[0045] First, it should be noted that this application's configuration management of aircraft information interface data mainly includes two aspects: one is building an information interface management database, and the other is modifying the information interface management database. Steps S1-S5 constitute the process of building the information interface management database, as follows... Figure 1 As shown; steps S6-S11 are the process of modifying the interface configuration items in the information interface management database, such as... Figure 2 As shown.

[0046] Secondly, it should be noted that an aircraft contains multiple devices, and these devices are connected through interfaces. Here, "interface" is a broad concept, referring to data communication between two aircraft devices. In actual communication, due to the large variety and quantity of communication data, multiple information interfaces need to be established between the two aircraft devices to transmit different data. In the existing technology, there are usually hundreds of information interfaces between two aircraft devices, and each information interface needs to be included in the management system, resulting in very chaotic version number management. The purpose of this application is to classify these information interfaces to facilitate the upgrade management of these information interfaces.

[0047] Returning to the management method steps of this application, the first step, S1, involves identifying all aircraft designs and their interfaces. An information class interface structure tree is defined according to the aircraft product decomposition structure, typically generated during the aircraft architecture trade-offs and definition phase. In some optional implementations, an N-squared diagram is used to record the interface relationships of various aircraft devices, such as... Figure 3 As shown, the N-squared diagram lists all aircraft equipment in both the vertical and horizontal headers. The intersections of the horizontal and vertical aircraft equipment indicate the interface relationships between the two pieces of equipment, which can be either connected or disconnected. This embodiment utilizes the N-squared diagram to identify all interface matrix points with cross-linking relationships, thereby identifying the aircraft equipment with interface relationships.

[0048] Subsequently, in step S2, the specific type of each information interface is determined according to system requirements. In some optional embodiments, the interface type includes non-bus interfaces and bus interfaces. The non-bus interfaces include, but are not limited to, analog signal interfaces, discrete signal interfaces, audio signal interfaces, and video signal interfaces. The bus interfaces include, but are not limited to, RS422 bus, GJB289A bus, fiber optic bus, and 1394B bus.

[0049] Next, in step S3, the detailed definitions of each information class interface are completed according to the standards of the corresponding interface types. These standards may originate from national standards, industry standards, or enterprise-defined standards, and generally determine the information expression method in the form of a table template. For example, in some optional embodiments, the definition of the information class interface includes:

[0050] Obtain the interface definition file template specified by the standard for the interface type;

[0051] The interface definition file is generated by obtaining the information filled in by the aircraft equipment at both ends of the interface based on the interface definition file template provided by the designer.

[0052] Determine the interface version number in the interface definition file.

[0053] The final step in this embodiment is used to specify the version of the interface. In some alternative implementations, the version number of the interface in the interface definition file is marked with letters, for example, using English letters starting from A and sequentially identified (A, B, C...).

[0054] In step S4, the packaging of information-type interfaces is completed, that is, the configuration items of information-type interfaces are determined. The interface configuration rules described in this step are divided into two categories according to whether they are non-bus or bus interfaces: For non-bus interfaces, the rule is "Source Device 1 - Non-bus - Target Device 2", that is, all non-bus interfaces between the source device and the target device are packaged into one configuration item, such as "Hydraulic Equipment - Non-bus - Electromechanical Integrated Processing Equipment"; For bus interfaces, the rule is "Source Device 1 - Specific Bus Type - Target Device 2", that is, a single bus interface between the source device and the target device is packaged into one configuration item, such as "Integrated Avionics Processing - Fiber Optic Bus - Display Control Equipment".

[0055] In step S4, the version number of the interface configuration item is also marked. In some optional embodiments, the version number of the interface configuration item of the interface configuration file is marked with Arabic numerals. For example, three digits are usually used to identify it sequentially starting from 001 (001, 002, 003...).

[0056] Step S5 is to complete the review and archiving of information interface configuration items according to the interface configuration review and approval rules, which includes four steps: "design, proofreading, countersigning, and approval". The designer is responsible for defining the content of the interface configuration items, the proofreader is responsible for verifying the content of the interface configuration items, the countersigner is responsible for confirming the delivery information between the cross-linking devices, and the approver is responsible for the final confirmation of the interface configuration items.

[0057] Step S6 onwards involves using the information interface management database constructed above. Through the packaging process described above, multiple information interfaces are packaged into a single configuration item, thus providing modular management for subsequent use. For example... Figure 2 As shown, firstly, based on business needs, the information type interfaces that need to be changed are determined. Then, in step S7, the interface scope is determined. In some optional embodiments, step S7 further includes:

[0058] Determine the source device to which the information class interface to be modified belongs;

[0059] Based on the interface relationships of each aircraft device, determine all target devices connected to the source device;

[0060] In each interface from the source device to the target device, determine whether it contains an information class interface to be changed, and then determine all interfaces involved in the change.

[0061] This embodiment combines the interface relationships shown in the N-squared diagram to analyze changes to the interconnecting interfaces, thereby determining the specific range of interfaces involved in the current modification. For example, if the A interface data of device 2 is to be changed, the target devices connected to device 2 must first be identified. The N-squared diagram can be used to directly query devices 4, 6, etc. Then, the engineer determines whether A interface data is transmitted between device 2 and device 4, whether interface data is transmitted between device 2 and device 6, and so on. Based on this, all interfaces involved in the current modification can be determined.

[0062] Then, in step S8, all information class interfaces are modified, and all modified information class interfaces are upgraded. For example, if the original version is "B", the current version should be "C".

[0063] Step S9 mainly prepares for the subsequent review and approval. It completes the scope of the interface configuration items included in the interface configuration item. Considering that not all interfaces are changed synchronously each time, different valid versions of the interfaces included in the interface configuration item may appear during the development process. Before initiating the review and approval of the interface configuration item change, the valid version of each interface should be determined. For example, if an interface configuration item includes three interfaces, A, B, and C, the valid versions of the interfaces to be reviewed and approved may be different, such as interface A (version A), interface B (version C), and interface C (version B).

[0064] In step S10, the interface configuration item is upgraded. For example, if the original version is "002", the current version should be "003".

[0065] The approval process in step S11 is the same as that in step S5. Step S9 provides the valid versions of each interface in the interface configuration items, and the final confirmation of the interface configuration items is completed in the approval process.

[0066] This application supports the definition and management of information interfaces according to configuration items, that is, it supports modular definition, approval, archiving and change control, which can effectively reduce the management scale of information interfaces, while conveniently completing the modification and confirmation of interface information. It can further improve the processing efficiency of information interface control software and improve management logic, thereby supporting the rapid approval, reuse and efficient change control of information interface data, and improving the R&D quality of complex aircraft cross-linking interfaces.

[0067] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for configuring and managing aircraft information interface data, characterized in that, include: Step S1: Determine the interface relationships of each aircraft device; Step S2: Determine the interface types of each information class between various aircraft equipment that have interface relationships; Step S3: Define the information interfaces between each pair of aircraft equipment to form an interface definition file carrying the interface version number; Step S4: Package the information interfaces between each aircraft device according to the interface configuration rules. Between every two aircraft devices, all information interfaces belonging to non-bus types are packaged into one interface configuration item, and all information interfaces belonging to the same bus type are packaged into one interface configuration item, forming an interface configuration file carrying the interface configuration item version number. Step S5: Define and approve the interface configuration items in the interface configuration file; Step S6: When making changes to the information class interface, determine the information class interface that needs to be changed; Step S7: Based on the interface relationships of each aircraft device, determine all interfaces involved in the change; Step S8: Complete the content changes for all information class interfaces and upgrade the version number of the interface definition file; Step S9: Determine the valid versions of all information class interfaces in the interface configuration items; Step S10: Upgrade the version number of the interface configuration item; Step S11: Define and approve the content of the changed interface configuration items.

2. The aircraft information interface data configuration management method as described in claim 1, characterized in that, In step S1, the interface relationships of each aircraft device are recorded using an N-squared diagram. All aircraft devices are listed in both the vertical and horizontal headers of the N-squared diagram. The interface relationships between the horizontal and vertical aircraft devices are marked at their intersections. These interface relationships include whether the devices are connected or not.

3. The aircraft information interface data configuration management method as described in claim 1, characterized in that, In step S2, the interface type includes non-bus interfaces and bus interfaces. The non-bus interfaces include, but are not limited to, analog signal interfaces, discrete signal interfaces, audio signal interfaces, and video signal interfaces. The bus interfaces include, but are not limited to, RS422 bus, GJB289A bus, fiber optic bus, and 1394B bus.

4. The aircraft information interface data configuration management method as described in claim 1, characterized in that, Step S3, defining the information class interface includes: Obtain the interface definition file template specified by the standard for the interface type; The interface definition file is generated by obtaining the information filled in by the aircraft equipment at both ends of the interface based on the interface definition file template provided by the designer. Determine the interface version number in the interface definition file.

5. The aircraft information interface data configuration management method as described in claim 1, characterized in that, The version number of the interface in the interface definition file is marked with a letter, and the version number of the interface configuration item in the interface configuration file is marked with Arabic numerals.

6. The aircraft information interface data configuration management method as described in claim 1, characterized in that, Step S7 further includes: Determine the source device to which the information class interface to be modified belongs; Based on the interface relationships of each aircraft device, identify all target devices connected to the source device; In each interface from the source device to the target device, determine whether it contains an information class interface to be changed, and then determine all interfaces involved in the change.

Images