CN118277381A - Aeroengine parameter storage method based on zipper structure - Google Patents
Aeroengine parameter storage method based on zipper structureInfo
- Publication number
- CN118277381A CN118277381A CN202410299523.4A CN202410299523A CN118277381A CN 118277381 A CN118277381 A CN 118277381A CN 202410299523 A CN202410299523 A CN 202410299523A CN 118277381 A CN118277381 A CN 118277381A
- Authority
- CN
- China
- Prior art keywords
- protocol
- parameter
- parameters
- establishing
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000013507 mapping Methods 0.000 claims abstract description 41
- 238000013500 data storage Methods 0.000 claims abstract description 34
- 238000004590 computer program Methods 0.000 claims description 12
- 238000010276 construction Methods 0.000 claims 1
- 238000007726 management method Methods 0.000 description 6
- 230000036541 health Effects 0.000 description 5
- 230000008676 import Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013075 data extraction Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
Abstract
The invention discloses an aeroengine parameter storage method based on a zipper structure, which comprises the following steps: (1) establishing a standard parameter table; (2) establishing a protocol parameter table; (3) establishing a file information table; (4) building a data storage entity table; (5) establishing a mapping table of the protocol parameters and the storage entity zipper; (6) aero-engine protocol parameters and data storage; according to the invention, through automatic matching of protocol parameters and automatic establishment of mapping relation, the protocol automatic matching of known parameters is dynamically completed; the parameter mapping pull chain table is adopted, so that the user can conveniently and manually re-match and manage the parameters and the standard parameters; based on the real-time column database, the parameters can be quickly searched in real time.
Description
Technical Field
The invention relates to the technical field of parameter processing of aeroengines, in particular to an aeroengine parameter storage method based on a zipper structure.
Background
When analyzing the data of the engine data recorder, the existing aeroengine health management system needs to rely on the data protocol of control software, analyzes the masked data files according to the parameter sequence specified in the protocol, and stores the data files in the specified data sequence. However, the control software version has a longer life cycle and is changed frequently, so that the data protocol parameters are changed accordingly. When the protocol parameters of different versions are stored, a small amount of parameters are required to be stored in different columns due to different names or data formats, and finally the large scale of the data columns is caused, so that the data columns cannot be stored or the space is caused to be large, the data reading efficiency is reduced, and the difficulty of data use is increased. Therefore, it is important to automatically align the protocol parameters of different versions and uniformly store the parameters under different protocols. Therefore, an automatic alignment and storage method for parameters of the aero-engine must be designed and integrated into an aero-engine health management system, so as to meet the requirements of the aero-engine health management system software for data extraction and data processing analysis of certain parameters.
The data parameter protocol in the aeroengine health management system is the most important metadata in the health management system, is the core data of all subsequent businesses, and only the parameter protocol can extract, process, analyze and mine the data of different time periods and different protocols.
Disclosure of Invention
The invention aims to: the invention aims to provide an aeroengine parameter storage method based on a zipper structure, which aims at the characteristic of engine parameter protocol change (more than 98% of parameter items are unchanged), automatically compares each parameter in a new data protocol with the protocol passing name and data characteristics (formats) in a system, automatically maps the parameter of the new protocol with the existing protocol library once identified, stores unidentified parameters as new parameters and can manually modify the mapping relation.
The technical scheme is as follows: the invention discloses an aeroengine parameter storage method based on a zipper structure, which comprises the following steps of:
(1) Establishing a standard parameter table;
(2) Establishing a protocol parameter table;
(3) Establishing a file information table;
(4) Establishing a data storage entity table;
(5) Establishing a zipper mapping table of protocol parameters and storage entities;
(6) Aeroengine protocol parameters and data storage.
Further, the step (1) specifically includes: the physical meaning of each parameter of the engine is combed, standardized naming of the parameters is carried out one by one, and a standard parameter table is established, which comprises the following steps: id. Parameter name, parameter description, protocol mask ID.
Further, the step (2) specifically includes the following steps: establishing a protocol parameter table, and storing all parameter information under a certain protocol comprises: ID. Parameter name, engine model, version number, ID corresponding to standard parameter table in step (1); the protocol parameter table is associated with the standard parameter table by the ID of the standard parameter.
Further, the step (3) specifically includes the following steps: the method comprises the following steps: establishing a file information table, and storing physical information of a data file, wherein the column head of the table is file ID, file name, protocol version number and file auxiliary information; and associating the file information table with the protocol parameter table through the protocol version number.
Further, the step (4) specifically includes the following steps: establishing a data storage entity table, wherein the column head of the table is as follows: the relative storage time of the parameter physical entity is time stamp, file ID, protocol mask ID. When storing aeroengine data, the data are corresponded to the protocol mask ID by columns, and the file information table is associated with the data storage entity table through the file ID.
Further, the step (5) specifically comprises the following steps: establishing a zipper mapping table of protocol parameters and a storage entity, wherein the zipper mapping table stores an ID, a parameter ID and a storage mask ID; the zipper mapping table is associated with the protocol parameter table through the parameter ID; the zipper mapping table is associated with the data storage entity table by a storage mask ID.
Further, the step (6) specifically includes the following steps:
(61) And for the new version protocol to be stored, acquiring the initialized protocol version number through the protocol file name. Checking whether the version number is repeated with the historical protocol version number stored in the step (2), and if so, prompting that the same version protocol exists and terminating the protocol storage.
(62) For the non-repeated protocol version number, analyzing the protocol file, and acquiring a parameter list in the protocol comprises the following steps: ID. Parameter name and engine model;
(63) Comparing the parameter list obtained by analysis with the history protocol stored in the step (2), wherein the parameter name or the parameter alias of the parameters are the same, and checking whether the protocol is repeated;
(64) For the repeated parameter list protocol, parameter detail information of the existing protocol version in the database is returned;
(65) Comparing the parameters in the protocol with the standard parameter list established in the step (1) for the newly added protocol of the non-repeated parameter list, wherein the parameter names in the protocol are the same as the parameter names of the standard parameter list, and copying the mapping relation of the existing parameters established in the step (5) to the parameters of the newly added protocol;
(66) And (3) when the newly added protocol parameter is not matched with the standard parameter table established in the step (1), the newly added parameter is regarded as a newly added parameter field, and the newly added parameter is added to the standard parameter table established in the step (1) to form a new protocol mask ID. Preparing a new storage entity space for the parameter, namely adding the new storage entity space as a new added column into the data storage entity table established in the step (4), wherein the column name is a protocol mask ID;
(67) Repeating the steps (65) and (66), returning the protocol parameter mapping table established in the step (5) after all parameters of the newly-added protocol are stored, providing a mapping result between the newly-added protocol parameters and the established standard parameter table for user page auditing, and supporting the user to manually modify the mapping result in the step (5);
(68) When the aeroengine data is stored, storing the file ID, the file name, the protocol version number and the file auxiliary information into a file information table according to the selected protocol version in the step (3), acquiring the protocol parameter table in the step (2) according to the protocol version number, and storing the data column content into the data storage entity table established in the step (4) according to the mapped protocol mask ID.
The invention relates to an aeroengine parameter storage system based on a zipper structure, which comprises:
standard parameter module: for establishing a standard parameter table;
protocol parameter module: for establishing a protocol parameter table;
file information module: the method is used for establishing a file information table;
The data storage entity module: for building a data storage entity table;
zipper mapping module: the method is used for establishing a zipper mapping table of protocol parameters and storage entities;
Protocol parameters and data storage module: the method is used for storing the protocol parameters and data of the aeroengine.
The electronic equipment comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, and is characterized in that the computer program is loaded to the processor to realize any one of the aeroengine parameter storage methods based on the zipper structure.
The storage medium of the present invention stores a computer program, and the computer program is executed by a processor to implement any one of the aeroengine parameter storage methods based on a zipper structure.
The beneficial effects are that: compared with the prior art, the invention has the following remarkable advantages: automatically completing the protocol automatic matching of the known parameters through the automatic matching of the protocol parameters and the automatic establishment of the mapping relation; the parameter mapping pull chain table is adopted, so that the user can conveniently and manually re-match and manage the parameters and the standard parameters; based on the real-time column database, the parameters can be quickly searched in real time.
Drawings
FIG. 1 is an overall flow chart of the present invention;
FIG. 2 is a schematic diagram of parameter multi-protocol matching according to the present invention;
FIG. 3 is a flow chart of the protocol parameter storage of the present invention;
Detailed Description
The technical scheme of the invention is further described below with reference to the accompanying drawings.
As shown in fig. 1, an embodiment of the present invention provides an aeroengine parameter storage method based on a zipper structure, including the following steps:
(1) Establishing a standard parameter table; the method comprises the following steps: the physical meaning of each parameter of the engine is combed, standardized naming of the parameters is carried out one by one, and a standard parameter table is established, which comprises the following steps: ID. Parameter name, parameter description, protocol mask ID.
(2) Establishing a protocol parameter table; the method comprises the following steps: establishing a protocol parameter table, and storing all parameter information under a certain protocol comprises: ID. Parameter name, engine model, version number, ID corresponding to standard parameter table in step (1); the protocol parameter table is associated with the standard parameter table by the ID of the standard parameter.
(3) Establishing a file information table; the method comprises the following steps: the method comprises the following steps: establishing a file information table, and storing physical information of a data file, wherein the column head of the table is file ID, file name, protocol version number and file auxiliary information; and associating the file information table with the protocol parameter table through the protocol version number.
(4) Establishing a data storage entity table; the method comprises the following steps: establishing a data storage entity table, wherein the column head of the table is as follows: the relative storage time of the parameter physical entity is time stamp, file ID, protocol mask ID. When storing aeroengine data, the data are corresponded to the protocol mask ID by columns, and the file information table is associated with the data storage entity table through the file ID.
(5) Establishing a zipper mapping table of protocol parameters and storage entities; the method comprises the following steps: establishing a zipper mapping table of protocol parameters and a storage entity, wherein the zipper mapping table stores an ID, a parameter ID and a storage mask ID; the zipper mapping table is associated with the protocol parameter table through the parameter ID; the zipper mapping table is associated with the data storage entity table by a storage mask ID.
As shown in fig. 2, the above information is used for inquiring different protocol data, when a 1 file is inquired, a corresponding protocol version a is found in a file information table, all parameter protocol information with version a is found in a parameter protocol table, and the corresponding ID of 1-12 in a standard protocol is found correspondingly as follows in the a-L parameters of the protocol a in fig. 2;
When the protocol version is updated, the protocol parameters of the new version are changed, and the standard protocol is expanded accordingly; as shown in fig. 2, the parameters "a" - "L" are stored in the protocol a, and are identified in green and different in yellow in the same meaning as the parameters of the standard protocol of the current system; when the system imports the protocol A, the parameters marked by green automatically correspond to the standard protocol, and the parameters marked by yellow are added to the standard protocol as new parameters, thereby completing the expansion of the standard protocol. When the system imports the protocol B, the corresponding rule of the green and yellow identification parameters is the same as that of the protocol A, and the blue identification parameters represent the nonstandard naming parameters shown in the step (1), and are mapped onto the standard protocol through the standard parameter table, so that the protocol field multiplexing of the parameters with the same physical meaning is realized.
As shown in fig. 2, for the protocols a and B of different versions, there are 12 columns of engine parameters corresponding to each, when data storage of 24 columns is performed, mapping is performed to the same data column through the standard protocol, and the database only needs to establish a table of 14 columns corresponding to the standard protocol, so that the scale of the data column is reduced, and redundant memory occupation is avoided. And establishing mapping relation between different versions of protocol parameters and standard protocol parameters, realizing standardized management of multiple protocols, and improving data storage multiplexing and reading efficiency.
(6) Aeroengine protocol parameters and data storage. As shown in fig. 3, the method specifically comprises the following steps:
(61) And for the new version protocol to be stored, acquiring the initialized protocol version number through the protocol file name. Checking whether the version number is repeated with the historical protocol version number stored in the step (2), and if so, prompting that the same version protocol exists and terminating the protocol storage.
(62) For the non-repeated protocol version number, analyzing the protocol file, and acquiring a parameter list in the protocol comprises the following steps: ID. Parameter name and engine model;
(63) Comparing the parameter list obtained by analysis with the history protocol stored in the step (2), wherein the parameter name or the parameter alias of the parameters are the same, and checking whether the protocol is repeated;
(64) For the repeated parameter list protocol, parameter detail information of the existing protocol version in the database is returned;
(65) Comparing the parameters in the protocol with the standard parameter list established in the step (1) for the newly added protocol of the non-repeated parameter list, wherein the parameter names in the protocol are the same as the parameter names of the standard parameter list, and copying the mapping relation of the existing parameters established in the step (5) to the parameters of the newly added protocol;
(66) And (3) when the newly added protocol parameter is not matched with the standard parameter table established in the step (1), the newly added parameter is regarded as a newly added parameter field, and the newly added parameter is added to the standard parameter table established in the step (1) to form a new protocol mask ID. Preparing a new storage entity space for the parameter, namely adding the new storage entity space as a new added column into the data storage entity table established in the step (4), wherein the column name is a protocol mask ID;
(67) Repeating the steps (65) and (66), returning the protocol parameter mapping table established in the step (5) after all parameters of the newly-added protocol are stored, providing a mapping result between the newly-added protocol parameters and the established standard parameter table for user page auditing, and supporting the user to manually modify the mapping result in the step (5);
(68) When the aeroengine data is stored, storing the file ID, the file name, the protocol version number and the file auxiliary information into a file information table according to the selected protocol version in the step (3), acquiring the protocol parameter table in the step (2) according to the protocol version number, and storing the data column content into the data storage entity table established in the step (4) according to the mapped protocol mask ID.
The embodiment of the invention also provides an aeroengine parameter storage system based on the zipper structure, which comprises:
standard parameter module: for establishing a standard parameter table;
protocol parameter module: for establishing a protocol parameter table;
file information module: the method is used for establishing a file information table;
The data storage entity module: for building a data storage entity table;
zipper mapping module: the method is used for establishing a zipper mapping table of protocol parameters and storage entities;
Protocol parameters and data storage module: the method is used for storing the protocol parameters and data of the aeroengine.
The embodiment of the invention also provides electronic equipment, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, and is characterized in that the computer program is loaded to the processor to realize the aeroengine parameter storage method based on the zipper structure.
The embodiment of the invention also provides a storage medium, which stores a computer program, and is characterized in that the computer program realizes the aeroengine parameter storage method based on the zipper structure when being executed by a processor.
Claims (11)
1. The aeroengine parameter storage method based on the zipper structure is characterized by comprising the following steps of:
(1) Establishing a standard parameter table;
(2) Establishing a protocol parameter table;
(3) Establishing a file information table;
(4) Establishing a data storage entity table;
(5) Establishing a zipper mapping table of protocol parameters and storage entities;
(6) Aeroengine protocol parameters and data storage.
2. The method for storing parameters of an aeroengine based on a zipper structure according to claim 1, wherein the step (1) is specifically: the physical meaning of each parameter of the engine is combed, standardized naming of the parameters is carried out one by one, and a standard parameter table is established, which comprises the following steps: ID. Parameter name, parameter alias, parameter description, protocol mask ID.
3. The method for storing parameters of an aircraft engine based on a zipper structure according to claim 1, wherein the step (2) is specifically as follows: establishing a protocol parameter table, and storing all parameter information under a certain protocol comprises: ID. Parameter name, engine model, version number, ID corresponding to standard parameter table in step (1); the protocol parameter table is associated with the standard parameter table by the ID of the standard parameter.
4. The method for storing parameters of an aircraft engine based on a zipper structure according to claim 1, wherein the step (3) is specifically as follows: establishing a file information table, and storing physical information of a data file, wherein the column head of the table is file ID, file name, protocol version number and file auxiliary information; and associating the file information table with the protocol parameter table through the protocol version number.
5. The method for storing parameters of an aircraft engine based on a zipper structure according to claim 1, wherein the step (4) is specifically as follows: establishing a data storage entity table, wherein the column head of the table is as follows: the relative storage time of the parameter physical entity is time stamp, file ID, protocol mask ID; when storing aeroengine data, the data are corresponded to the protocol mask ID by columns, and the file information table is associated with the data storage entity table through the file ID.
6. The method for storing parameters of an aircraft engine based on a zipper structure according to claim 1, wherein the step (5) is specifically as follows: establishing a zipper mapping table of protocol parameters and a storage entity, wherein the zipper mapping table stores an ID, a parameter ID and a storage mask ID; the zipper mapping table is associated with the protocol parameter table through the parameter ID; the zipper mapping table is associated with the data storage entity table by a storage mask ID.
7. The method for storing parameters of an aircraft engine based on a zipper structure according to claim 1, wherein the step (6) specifically comprises the following steps:
(61) And for the new version protocol to be stored, acquiring the initialized protocol version number through the protocol file name. Checking whether the version number is repeated with the historical protocol version number stored in the step (2), and if so, prompting that the same version protocol exists and terminating the protocol storage.
8. (62) For the non-repeated protocol version number, analyzing the protocol file, and acquiring a parameter list in the protocol comprises the following steps: ID. Parameter name and engine model;
(63) Comparing the parameter list obtained by analysis with the history protocol stored in the step (2), wherein the parameter name or the parameter alias of the parameters are the same, and checking whether the protocol is repeated;
(64) For the repeated parameter list protocol, parameter detail information of the existing protocol version in the database is returned;
(65) Comparing the parameters in the protocol with the standard parameter list established in the step (1) for the newly added protocol of the non-repeated parameter list, wherein the parameter names in the protocol are the same as the parameter names of the standard parameter list, and copying the mapping relation of the existing parameters established in the step (5) to the parameters of the newly added protocol;
(66) And (3) when the newly added protocol parameter is not matched with the standard parameter table established in the step (1), the newly added parameter is regarded as a newly added parameter field, and the newly added parameter is added to the standard parameter table established in the step (1) to form a new protocol mask ID. Preparing a new storage entity space for the parameter, namely adding the new storage entity space as a new added column into the data storage entity table established in the step (4), wherein the column name is a protocol mask ID;
(67) Repeating the steps (65) and (66), returning the protocol parameter mapping table established in the step (5) after all parameters of the newly-added protocol are stored, providing a mapping result between the newly-added protocol parameters and the established standard parameter table for user page auditing, and supporting the user to manually modify the mapping result in the step (5);
(68) When the aeroengine data is stored, storing the file ID, the file name, the protocol version number and the file auxiliary information into a file information table according to the selected protocol version in the step (3), acquiring the protocol parameter table in the step (2) according to the protocol version number, and storing the data column content into the data storage entity table established in the step (4) according to the mapped protocol mask ID.
9. An aircraft engine parameter storage system based on a zipper structure, comprising:
standard parameter module: for establishing a standard parameter table;
protocol parameter module: for establishing a protocol parameter table;
file information module: the method is used for establishing a file information table;
The data storage entity module: for building a data storage entity table;
zipper mapping module: the method is used for establishing a zipper mapping table of protocol parameters and storage entities;
Protocol parameters and data storage module: the method is used for storing the protocol parameters and data of the aeroengine.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the computer program when loaded into the processor implements a zipper structure based aeroengine parameter storage method according to any one of claims 1-7.
11. A storage medium storing a computer program, characterized in that the computer program, when executed by a processor, implements an aeroengine parameter storage method based on a zipper construction according to any one of claims 1-7.
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118277381A true CN118277381A (en) | 2024-07-02 |
Family
ID=
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20180157724A1 (en) | Designating Fields in Machine Data Using Templates | |
| US8122066B2 (en) | Database query profiler | |
| US6925462B2 (en) | Database management system, and query method and query execution program in the database management system | |
| CN103186639B (en) | Data creation method and system | |
| US7885933B2 (en) | Apparatus and system for analyzing computer events recorded in a plurality of chronicle datasets | |
| CN109376142B (en) | Data migration method and terminal equipment | |
| WO2007121001A2 (en) | Method and apparatus for interactive generation of device response template and analysis | |
| US5895473A (en) | System for extracting text from CAD files | |
| CN101645073A (en) | Method for guiding prior database file into embedded type database | |
| CN112084246B (en) | Financial software information acquisition method | |
| CN113238865A (en) | Method for quickly constructing knowledge graph based on Excel one-key import | |
| CN116303834B (en) | Data warehouse historical data storage and processing method, system and device | |
| CN104636471A (en) | Procedure code finding method and device | |
| CN118277381A (en) | Aeroengine parameter storage method based on zipper structure | |
| CN110069489A (en) | A kind of information processing method, device, equipment and computer readable storage medium | |
| CN107291938A (en) | Order Query System and method | |
| CN106682153A (en) | Data extraction tool on basis of data modeling and data increment implementation | |
| CN115757479A (en) | Database query optimization method, machine-readable storage medium and computer device | |
| CN113282609A (en) | Intelligent data analysis method based on big data technology | |
| CN112612812A (en) | Method and device for processing multi-system data | |
| CN112764740B (en) | Shell-based processing method applied to file interaction between systems | |
| CN111339378A (en) | Character command auditing method and system in operation and maintenance management | |
| CN113722294B (en) | Data migration method and system from graph database to relational database | |
| CN113032406B (en) | Data archiving method for centralized management of sub-tables through metadata database | |
| CN110515913B (en) | Log processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication |