Civil aircraft aerodynamic theme data management method

Abstract

The application discloses a kind of civil aircraft aerodynamic theme data management methods, belong to aerodynamics test data management technical field, the core of management method is using aerodynamic wind tunnel test train table to realize the management of test data for the basic model of civil aircraft and its research category;Managed data includes four levels of research category, research object, project and result, each level contains relevant data resources;The application includes civil aircraft aerodynamic theme data warehousing method based on train table, civil aircraft aerodynamic theme data organization management, civil aircraft aerodynamic theme data retrieval and display, civil aircraft aerodynamic theme data maintenance and civil aircraft aerodynamic theme data call.The application replaces the mode of original data organization with test condition and test state, and operation is more simple, intuitive and convenient and fast.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of aerodynamic data management, in particular to a civil aircraft aerodynamic theme data management method. BACKGROUND

[0002] In the face of the development trend of civil aircraft industry independent innovation and the era requirement of systematization, standardization and digitization, the research on data commonality and management technology is carried out to form a comprehensive basic aerodynamic data system of advanced civil aircraft, to break through the technical link of civil aircraft aerodynamic design and test evaluation, to establish a unified evaluation standard, and to provide data support for aircraft layout comparison and selection, CFD design tool verification, civil aircraft aerodynamic test quality evaluation, advanced technology reliability and effect evaluation, design, flight test and airworthiness certification test, etc.

[0003] The existing test data management method is to organize data by test equipment, test condition, test state and test result, and each level is one-to-many with respect to the next level. Generally speaking, this is also the general mode of information management.

[0004] However, the existing test data management mode has the following problems:

[0005] The existing management mode conforms to the operation habits and thinking mode of computer personnel and is the general way of information sorting, but it does not conform to the operation habits of aerodynamic personnel. For aerodynamic personnel, whether in the test planning stage, the test implementation process or the final test summary stage, the data is organized by train table.

[0006] Organizing data by using the existing mode leads to very tedious test data collection and storage work, because the data sorting personnel must manually identify the test condition and test state according to the relevant information, and correspond to the test result. However, most of these information can be located in the train table.

[0007] The existing mode can only retrieve and analyze data, but when the result data is not analyzed and stored in multiple files, the result data file is generally named by train number, which is almost meaningless data sequence number. Aerodynamic personnel cannot know the file content from the file name, which brings great inconvenience to data retrieval.

[0008] The management and operation of result files are also not intuitive, and meaningless result file names make it difficult for aerodynamic personnel to proceed with other operations.

[0009] Under this background, we invented an aerodynamic data management method based on wind tunnel test train table to manage civil aircraft basic model data and data of different research directions. SUMMARY

[0010] The present application aims to provide a civil aircraft aerodynamic theme data management method, the core of the management method is to use the train table of aerodynamic wind tunnel test to realize the management of the basic model data of civil aircraft and the characteristic data of different research directions, and the user uses the database application system realized by the present application to realize the functions of civil aircraft verification data warehousing, organization, display, maintenance and calling.

[0011] The specific technical solutions are as follows:

[0012] The present application is a civil aircraft aerodynamic theme data management method, which comprises:

[0013] A civil aircraft aerodynamic theme data warehousing method based on the train table is formulated, the whole process of data entry to data storage is established according to data warehousing requirements, and the data quality is guaranteed through validity check and data standardization to establish a standardized civil aircraft aerodynamic data source;

[0014] The civil aircraft aerodynamic theme data is organized and managed, the hierarchical management relationship of aerodynamic data is established, the test conditions of the supplementary description project are supplemented, and the data template is formulated as the organization requirement of data file input and output;

[0015] The civil aircraft aerodynamic theme data is searched and displayed, the related data relationship is sorted, and efficient and easy-to-use data browsing, searching and downloading services are provided for the user;

[0016] The civil aircraft aerodynamic theme data is maintained, the data configuration and safety monitoring are realized, and the data resource use permission is divided;

[0017] A civil aircraft aerodynamic theme data calling method is formulated, and a data calling interface is provided, other application systems can obtain the civil aircraft aerodynamic theme data in a standardized format through the calling interface, and the integration and sharing of data are realized.

[0018] Further, the train table is a table that plans the model state and test conditions in the wind tunnel test planning stage, and the test is carried out according to the test outline planning in the test implementation stage, and the test results are sorted and drawn in the summary stage; when data is warehoused, a standard train table must be provided, the user configures a train table template according to the specific test type, then adds related states, conditions and train information, and the system analyzes the train table when warehousing.

[0019] Further, the data warehousing requirements are determined according to the related data specifications of civil aircraft aerodynamic data, including data file warehousing requirements based on train table information, file tag warehousing requirements and aerodynamic force data warehousing requirements.

[0020] Further, the method for formulating civil aircraft aerodynamic theme data based on train table includes data entry, validity check, data standardization, data version control, data permission control, and data storage.

[0021] Further, the data version control has file as operation object, including valid version and invalid version. When the same file is repeatedly entered in the project, the system provides three processing options of reservation, reservation but invalid, and coverage.

[0022] The data permission control has file as operation object, and is used to specify the visible range of valid files, including internal and public permissions. The public means that all users can see the file information, and the internal file means that the users in the permission can see all the information of the data, and other users can only browse the file list. In the same project, public files and internal files can exist at the same time.

[0023] The data storage means that the database-based storage and access should be supported, and the function of unified storage of various formats of data is provided. In addition to business data, the system also supports file formats including txt file, word file, picture, video, audio, Excel data file, 3D file, CAD graphics and mesh file, etc. The data storage function provides structured storage service and unstructured storage service, forms a complete storage model for data characteristics, and is mainly described as follows:

[0024] 1. Structured storage service: structured storage is based on database as storage center, and stores user information, file tags and other business-related data, establishes the basis for all data access, and provides advanced features such as transaction, index and query optimization.

[0025] 2. Unstructured storage service: unstructured storage provides storage and access services for files such as pictures, sounds, videos, reports, etc. which do not need to be decomposed or cannot be decomposed.

[0026] Further, the organization and management of the civil aircraft aerodynamic theme data in the database includes basic information organization and management, data file organization and management, file tag organization and management, and aerodynamic data organization and management.

[0027] Further, the file tag organization and management includes test result file tag and other file tags. The test result file tag is managed after the file is entered, and the management of the file is operated through the visual view of the train table. Through the analysis of the train table, the tag corresponding to each file is generated. As shown in Figure 2 .

[0028] The aerodynamic data organization and management means that the aerodynamic data is organized and managed.

[0029] The train number displayed in the file has three states of parsed, unparsed and unmatched. The parsed means that the file matched with the train number has completed the file parsing function. The unparsed means that the train number has a matched file and the file has not been parsed. The unmatched means that the train number has no corresponding file.

[0030] Further, the data retrieval and display of the civil aircraft aerodynamic theme includes data browsing, data retrieval, file preview, data download and data comparison.

[0031] Further, the data retrieval means that the data stored in the database is extracted according to the user's demand according to the appropriate matching rules to form a filtering result. The data retrieval takes projects and various files as targets to provide two retrieval modes of quick retrieval and advanced retrieval, and provides further retrieval function for the retrieval result. The advanced retrieval can be divided into fuzzy retrieval and accurate retrieval. The key word of file retrieval is the label of the corresponding result file generated by the train table. For the retrieval result, the traceability information is provided to require the parent node information of the display result object. The retrieval result contains object names such as name and research category, and provides dynamic jump to view details.

[0032] The retrieval mode is described as follows:

[0033] Quick retrieval: directly input the key word of the retrieval object name for matching, and the default is single key word search;

[0034] Project advanced retrieval: matching is performed by inputting navigation attributes and project attributes. The attribute content examples are shown in the following table, and the specific content comes from the project basic information.

[0035] File advanced retrieval: the advanced retrieval is performed on navigation attributes and file attributes, and supports multi-attribute combination retrieval and Boolean operation. The file attribute examples are shown in the following table, and the specific file attribute comes from the information entered by the label management.

[0036] Further retrieval: in the retrieval result, the retrieval condition is increased, and the retrieval result is filtered and matched according to the first retrieval method.

[0037] From the accuracy of retrieval, the advanced retrieval is divided into accurate retrieval and fuzzy retrieval.

[0038] Accurate retrieval: the input field and the data contained in the retrieval target must be the same to match. This retrieval method needs to ensure the integrity of the input field. If it is not complete, the data containing the key word cannot be searched. Accurate search can quickly and accurately locate without secondary search, and is usually used in the scene with clear search target and complete known information.

[0039] Fuzzy search: Fuzzy search does not require the input of complete keywords, as long as the search input field exists in the search term, it can be matched, and it is usually used in the case of insufficient known information and relatively unclear search target.

[0040] The data browsing refers to providing page interactive data exploration for users, including multi-dimensional navigation, content view and data table.

[0041] 1. Multi-dimensional navigation

[0042] The data navigation node is determined by the data management organization level, and the selection of the navigation node will guide the data filtering and filtering display results. The established navigation tree includes aerodynamic data navigation and basic information navigation. The aerodynamic data navigation is established according to the logical relationship of "research category"→"research object"→"project", and for the management object with rich information, the secondary menu under each module is arranged to arrange the management object name and provide navigation selection.

[0043] 2. Content view

[0044] The system provides a view panel corresponding to the content for each navigation node, covering the display picture and related content of the node. For aerodynamic data navigation, the corresponding view provides information as shown in the figure. The research category includes research category information, research object list and publication list; the research object includes research object information and research object associated project list; the project is divided into wind tunnel test and numerical calculation, the wind tunnel test includes project information, test model, installation information, train schedule, test result, video / photo, reference literature, etc.; the numerical calculation includes project information, numerical model, grid, boundary condition, calculation result, video / photo, reference literature, etc. Figure 3

[0045] 3. Data table

[0046] The data table is a display form for the analysis result based on the aerodynamic force data. At present, the analysis objects mainly include aerodynamic force result data and train schedule, and the aerodynamic force file analysis result will be summarized to form a unified table to support users to view. The train schedule is a common information overview for aerodynamic personnel, and its data table requires to display more information.

[0047] ​The data comparison refers to, on the basis of the data analysis function, utilizing the visual label file and the storage result file list, selecting the train number and the file name in the resolved state autonomously, determining the data set information as the analysis basis, and automatically drawing the analysis result of the determined coordinate axis and grouping condition, such as the lift coefficient change and the resistance coefficient change. The data comparison supports the comparison and analysis of the analyzed data under the same project, and supports the comparison and analysis of the analyzed data of different projects, which is realized by utilizing the data search module. The data comparison result mainly adopts the label form, provides multiple analysis chart result displays for the user, and supports the user to download the current analysis result. The result display layout should conform to the user habit, has related elements, and does not have information shielding.

[0048] Further, the maintenance of the civil aircraft aerodynamic theme data includes user permission maintenance, aerodynamic force data maintenance, data statistics, and log maintenance.

[0049] The aerodynamic force data maintenance refers to that the aerodynamic force data under a project is consistent with the data file information marked as the resolved state. The aerodynamic force data management does not support manual operation. The administrator operates the file or train number, and influences the resolved data through the association operation.

[0050] The beneficial effects of the present application are as follows:

[0051] 1. The civil aircraft aerodynamic theme data management method provided by the present application replaces the original mode of organizing data according to the test conditions and test states, uses the train number table to realize the storage, organization and management, retrieval, download and comparison service of the result data file, and is intuitive and convenient. The system can configure the train number table template for the specific test project, and the storage personnel can download and use it. The files are stored in folders, and the test result files are organized by the train number table. The test result files are tagged by the analysis of the train number table when being stored, and other files are tagged by the attribute file. Manual editing and modification are supported. The organization and management of the result files are also completed by the train number table. The retrieval of other files including the result files can be searched by the tags in the query interface as the keywords.

[0052] 2. The civil aircraft aerodynamic theme data management method provided by the present application strictly follows the relevant national standards and industry standards for the naming of test equipment, equipment code and data parameter naming, and formulates the special specification of civil aircraft aerodynamic data on this basis. The special specification is used as the basis for data storage and access interface, and a unified input and output plan is formulated. A unified information standard is provided for subsequent data expansion.

[0053] 3、The civil aircraft aerodynamic theme data management method provided by the application supports the management of data files in multiple formats, provides a flexible operation interface, and enables users to preview files online without downloading related files and using professional software for viewing, thereby maintaining good human-computer interaction.

[0054] 4、The civil aircraft aerodynamic theme data management method provided by the application performs version control and hierarchical management on data files, can realize cross-year updating of wind tunnel tests, and retains old versions after data updating, thereby corresponding data versions and user permissions, and being refined to the file level, for example, ordinary users can view public data, and senior users can view internal data, thereby guaranteeing the security and concealment of data.

[0055] 5、The civil aircraft aerodynamic theme data management method provided by the application analyzes aerodynamic force results, can compare and analyze through graphics, and also completes data analysis and comparison through train numbers, if users select multiple train numbers, the train numbers can be grouped on a graphic; the visual train number table is used to determine which data has been analyzed; the train number table is selected by the user to determine the data set information as the analysis basis; and the analysis result of the determined X and Y coordinate axes and grouping conditions is automatically drawn.

[0056] 6、The civil aircraft aerodynamic theme data management method provided by the application is file-level in granularity of permissions, retrieval, configuration, uploading and downloading, but also provides multiple selection or batch operation, and provides multiple download modes, including project packaging download, classification download, retrieval result download, and selection file batch download. BRIEF DESCRIPTION OF DRAWINGS

[0057] In order to more clearly illustrate the technical solutions of the embodiments of the application, the following will briefly introduce the drawings needed to be used in the embodiments, and it should be understood that the following drawings only show some embodiments of the application, and therefore should not be regarded as a limitation to the scope, and for those skilled in the art, other related drawings can also be obtained without creative labor on the basis of these drawings, wherein:

[0058] Figure 1 The method flowchart of the application;

[0059] Figure 2 The relationship between the tag file management operation and state change;

[0060] Figure 3 The aerodynamic data navigation corresponding view;

[0061] Figure 4 The B / S architecture diagram;

[0062] Figure 5 A layered architecture diagram of the system;

[0063] Figure 6 A diagram illustrating the data ingestion activity;

[0064] Figure 7 Here is a flowchart of the data file import process;

[0065] Figure 8 The process of storing the result file tags into the database;

[0066] Figure 9 Here is an example of an aerodynamic test result file;

[0067] Figure 10 This refers to the process of importing aerodynamic data into the database.

[0068] Figure 11 A diagram of data management activities;

[0069] Figure 12 For data browsing activity graphs;

[0070] Figure 13 Local ER diagram for navigation attributes;

[0071] Figure 14 ER diagram of a portion of the test equipment;

[0072] Figure 15 A partial ER plot of the data file;

[0073] Figure 16 For label specification, a partial ER diagram is shown.

[0074] Figure 17 For the global ER diagram;

[0075] Figure 18 This is a schematic diagram of the business platform interface. Detailed Implementation

[0076] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only for explaining the invention and are not intended to limit the invention; that is, the described embodiments are merely some embodiments of the invention, and not all embodiments. The components of the embodiments of the invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0077] It should be noted that the terms “comprising,” “including,” or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.

[0078] Example 1

[0079] This embodiment provides a method for managing aerodynamic subject data of civil aircraft, such as Figure 1 As shown, the details are as follows:

[0080] S1. Determine the data entry requirements based on the relevant data specifications for civil aircraft aerodynamic data, including data file entry requirements based on train schedule information, file tag entry requirements, and aerodynamic data entry requirements.

[0081] S2. Based on S1, develop a method for storing civil aircraft aerodynamic theme data based on train schedules, including data entry, validity verification, data standardization, data version control, data access control, and data storage.

[0082] S3. The data entered through S2 is organized and managed according to the civil aircraft aerodynamics theme data organization method, including basic information organization and management, data file organization and management, file tag organization and management, and aerodynamic data organization and management.

[0083] S4. Retrieve and display civil aircraft aerodynamic data, including data browsing, data retrieval, data download, and data comparison.

[0084] S5. Maintain civil aircraft aerodynamic data, including user permission maintenance, aerodynamic data maintenance, data statistics, and log maintenance.

[0085] S6. Establish a method for retrieving civil aircraft aerodynamic subject data. Other application systems can obtain standardized civil aircraft aerodynamic subject data by calling the interface.

[0086] I. Architecture Design

[0087] Based on analysis, the civil aircraft aerodynamics database is proposed to be built as a shared aerodynamics database using a B / S (Browser / Server) architecture, forming a three-tier B / S architecture. The B / S architecture is as follows: Figure 4 As shown, the system is divided into a presentation layer, an application layer, and a data layer from top to bottom, ensuring system scalability, load balancing, and ease of maintenance. The presentation layer handles user interaction, the application layer implements the main functions of the application / business logic, and the data layer is responsible for database read / write and management.

[0088] The architecture concentrates the core part of system function to the server, and the user sends a request to the web server through the browser, and then the web server assigns the module to process the business logic according to the user request, connects the database server, calls the corresponding data, forms the processing result and returns it to the client browser.

[0089] The civil aircraft aerodynamic theme database adopts a layered architecture, as shown in Figure 5 The client user interface is established through the display page and the display framework on the basis of the infrastructure and the database, and the presentation layer communicates with the application layer through relevant protocols and interaction technologies. The application layer establishes the SAS system, the data system and the message system to provide logical services for the user business, and records important operation logs. The data layer realizes the reading and writing and management of the database through data caching, custom functions and transaction operations. The layered architecture concentrates the core part of system function to the server, guarantees the scalability, load balancing and convenience of system maintenance.

[0090] II. Function implementation

[0091] (21) The data warehousing activity flow is shown in Figure 6 and described as follows:

[0092] 1. The research category, research object and project information are entered according to the above. In order to make the stored data information as complete as possible, the research object entry supports the association of template information, the wind tunnel test project supports the association of wind tunnel and balance, and the numerical calculation project supports the association of calculation software;

[0093] 2. The aerodynamic data file is entered on the specified project;

[0094] 3. The duplicate files are processed to determine the valid version and the invalid version of the files;

[0095] 4. After the system receives the data file, the data is checked according to the data template. If the checking fails, an error is prompted and the process is ended. If the data checking is passed, the data permission control is set and the data file is stored in the database.

[0096] (22) The data file warehousing flow is shown in Figure 7 and described as follows:

[0097] In the management hierarchy of research category -> research object -> research project, the aerodynamic data file takes the specific project as the system data storage management unit, covering regular force test, regular heat test, regular pressure test, numerical simulation test, acoustic test, power test, jet test, and icing test. According to the above test requirements, the stored aerodynamic data file includes numerical simulation, grid, boundary control, calculation result file, model, installation information, train table, test result file, video, image, reference, project report, etc. During the storage process, these files first need to meet the system data template requirements, and then through version control and permission control to complete the file state, and finally realize storage.

[0098] (23) The test result file tag storage process is shown in Figure 8 , described as follows:

[0099] After the aerodynamic data is stored, most of the data exists in the form of files. When the data volume increases, how to handle massive data files and realize system data management becomes the biggest challenge for data utilization. In order to clarify the data relationship and speed up the data positioning efficiency, the system will describe the data files, form file tags, and improve data usability and maintainability.

[0100] Currently, test site researchers generate train tables while generating test result files, recording model state, test conditions, and other information related to train. The test result file tag will supplement information based on the file to form a tag file.

[0101] After the tag file is entered and parsed, the system will verify the data validity, including whether the tag name, symbol, and unit meet the system tag specification requirements, whether the tag value is within the value range set by the tag specification, etc. If the data validity verification is successful, the parsing result is output to the administrator to confirm whether to store, and the administrator verifies that there is no error and confirms storage before storing in the database. If the verification fails, including the name, symbol, unit does not meet the specification, the tag value does not meet the alternative value range, etc., the storage process will be interrupted, and the user will be reminded of the error reason.

[0102] (24) The aerodynamic force data storage process is shown in Figure 10 , described as follows:

[0103] After the aerodynamic file passes through the data file storage process, it is stored in the database in the form of a file. An example of the aerodynamic force test result file is shown in Figure 9 , wherein the aerodynamic force file will be parsed to read the aerodynamic force data, form structured data, and written into the database after verified by the data administrator.

[0104] However, aerodynamic data has the characteristics of large data volume, extensive sources, high dimension and complexity, and cannot completely determine the specific organization format of data files. In actual situations, some aerodynamic data documents describe test condition parameters in the file header, and the variable name and result data are behind the file header, as shown in the following figure. But some aerodynamic data files may only contain result data, and need to supplement test condition parameters and other information to ensure the integrity and readability of the data.

[0105] Therefore, the system needs to establish an association relationship between the test condition file and the result file to form complete and effective aerodynamic result data, and support subsequent plotting analysis. Before the result file is parsed, it is necessary to verify that the test condition corresponding to the file exists, and only if the condition is met, can the parsing and warehousing process be performed.

[0106] (25) Data organization and management

[0107] The goal of the data management module is to achieve overall management of aerodynamic data. Aerodynamic data files depend on projects, and other activities are carried out around project management, establish an association relationship, and expand project information. On each association node, different operations are performed on the selected object through different management items, as shown in the following figure. Figure 11

[0108] In the basic information management, the research object information management involves the association of the corresponding label, the project information management involves the association of the test wind tunnel, the balance and the calculation software, in addition to the data template and the label related to the data file. The management of these data objects belongs to the maintenance operation, and the functional requirements are described in the function design section. The activity diagram is not described in detail.

[0109] (26) Data browsing

[0110] The user selects the data object to be browsed, and the data object includes research category, research object and project. The data browsing activity is shown in the following figure. Figure 12 If it is a research category, the research category information is browsed, the research object browsing information can be selected, or the publication can be selected to download the file, and the operation process belongs to the file download selection. If it is a research object, the research object information is supported to be browsed, and the project information can be selected to browse the project information. If it is a project, the project information is directly browsed. For the project information, the project download, the file download selection and the classification download are provided, and part of the files support preview. The preview activity is described in the preview file activity diagram.

[0111] ​The system management module is responsible for the implementation of user management, department management, role management, data backup, system maintenance, data statistics and other functions. When the user management module is executed, the administrator is required to complete the allocation of department information and role information after establishing the basic information of the user, and to determine the basic rights of the user. For special users, the administrator supports individual permission information configuration. Finally, the operation information system is written into the system log for the administrator to view later, ensuring that important system operations can be traced.

[0112] III. Data structure design

[0113] The main entities of the civil aircraft aerodynamic theme database include research categories, research objects, projects, models, wind tunnels, balances, calculation software, files, logs, users, roles, and permissions. According to the relationships between entities, the data logical structure is designed for navigation attributes, test equipment, data files, and system management.

[0114] (31) Navigation attributes

[0115] According to the functional analysis, the research category, research object, and project information form the data navigation information, which is used to establish the hierarchical management relationship of aerodynamic data. The extended information of the research object information is the model information. As shown in the following table, the entities involved in the local logical structure design of the navigation attributes include: Figure 13

[0116] Research category: The description attributes include research category number, research category name, description, and display picture. The entity identifier is the research category number.

[0117] Model: The description attributes include code, model name, design unit, basic structure form and characteristics, applicable support form and matching struts, reference area, horizontal reference length, vertical reference length, total height, total length, total width, reference point position X, reference point position Y, reference point position Z, centroid position X direction, centroid position Y direction, centroid position Z direction, and display picture. The entity identifier is the code.

[0118] Research object: The description attributes include number, name, component parts, flap angle, description, and display picture. The entity identifier is the number.

[0119] Project: The description attributes include project number, project name, data source, release form, active control form, model, model form, speed range, description, and display picture. The entity identifier is the project number.

[0120] The four types of entities are associated with each other, where:

[0121] ​1、Research category and research object are many-to-many relationship. One research category can contain multiple research objects, and one research object can belong to multiple research categories;

[0122] 2、Research category and project are one-to-many relationship. One research category can contain multiple projects, and one project can only belong to one research category;

[0123] 3、Research object and project are one-to-many relationship. One research object can contain multiple projects, and one project can only belong to one research object;

[0124] 4、Research object and model are one-to-many relationship. One model can contain multiple research objects, and one research object can only belong to one model.

[0125] (32) Test equipment

[0126] As shown in Figure 14 , the relevant test equipment of the wind tunnel test project includes the wind tunnel, the balance, and the numerical calculation project. The relevant test equipment of the numerical calculation project is the calculation software. Establishing the logical structure between the project and the wind tunnel, the balance, and the calculation software involves entities including:

[0127] Wind tunnel: The description attributes include wind tunnel code, sub-name, belonging organization, country, construction time, test section size, test speed, Reynolds number, total pressure, total temperature, equipment, test capacity, test project, related literature, and picture. The entity identifier is the wind tunnel code.

[0128] Balance: The description attributes include balance code, balance name, form, connection size, static calibration center, normal force, axial force, lateral force, pitch moment, yaw moment, roll moment, length, width, height, diameter, and picture. The entity identifier is the balance code.

[0129] Project: The description attributes include project number, project name, data source, release form, active control form, model, model form, speed range, description, and display picture. The entity identifier is the project number.

[0130] Calculation software: The description attributes include software number, version, basic situation, applicable scope, control equation, running limit, and running environment. The entity identifier is the software number.

[0131] The four types of entities are centered on the project, and the project and the remaining entities form a dependent relationship. One project uses one wind tunnel and can use multiple balances and calculation software, and one wind tunnel / balance / calculation software can be used by multiple projects.

[0132] (33) Data file

[0133] The data files stored in the system include publication files and aerodynamic data files, and the data logic design is file-centered, as shown in Figure 15 The involved entities include:

[0134] Research Category: Same as the research category entity in the navigation attribute.

[0135] Project: Same as the project entity in the navigation attribute.

[0136] File: Description attributes include file number, name, file type, storage path, download path, file status, and notes. The entity is identified by the file number.

[0137] File Tag: Description attributes include file tag number and tag value. The entity is identified by the file tag number.

[0138] In Figure 15 , the entity relationships include:

[0139] Research Category and File: One-to-many relationship. One research category can contain multiple publication files, and one publication file can only belong to one research category. The publication entry records the entry time and user.

[0140] Project and File: One-to-many relationship. One project can contain multiple aerodynamic data files, and one aerodynamic data file can only belong to one project. The aerodynamic data file entry records the entry time and user.

[0141] File and File Tag: Many-to-many relationship. One file can have multiple file tags, and one file tag can belong to multiple files.

[0142] (34), Tag Specification

[0143] In the system, file tags are subject to tag specifications, and tag specifications are managed according to different classifications. As shown in Figure 16

[0144] Tag Classification: Description attributes include classification number and classification name. The entity is identified by the tag classification number.

[0145] Tag Specification: Description attributes include tag number, tag name, symbol, unit, data range, and notes, and there may be multiple alternative values. The entity is identified by the tag number.

[0146] In Figure 16 , the entity relationships include:

[0147] File Tag and Tag Specification: One-to-many relationship. One file tag corresponds to one tag specification, and one tag specification can correspond to multiple file tags.

[0148] ​Tag classification and tag specification are one-to-many relationship. One tag classification can have multiple tag specifications, and one tag specification belongs to only one tag classification.

[0149] (35) System management

[0150] The system management part manages user role permissions and other information, such as Figure 16 As shown, the entities involved include:

[0151] Permission: The description attributes include permission number, permission name, function point, and function point URL. The entity identifier is the permission number.

[0152] Department: The description attributes include department number, department name, function, and remarks. The entity identifier is the department number.

[0153] Log: The description attributes include log number, operation type, operation record, and remarks. The entity identifier is the log number.

[0154] Role: The description attributes include role number, role name, and remarks. The entity identifier is the role number.

[0155] User: The description attributes include user account, nickname, gender, phone, email, and remarks. The entity identifier is the user account.

[0156] (36) Global ER diagram

[0157] Integrate the local data logical structure design to obtain the global ER diagram, see Figure 17 .

[0158] Four, data interface

[0159] (41) Front-end and back-end interface

[0160] The system adopts B / S architecture, and there is a large amount of data interaction communication between the front-end component and the back-end component. The constraints of the interactive interface are conducive to forming unified rules and improving information readability. The constraint examples are shown in Table 1:

[0161] Table 1 Front-end and back-end data interaction constraints

[0162]

[0163]

[0164] (42) Database interface

[0165] The database interface refers to the data interaction between the program and the database. The system adopts a unified database driver, and the program establishes a link with the database by calling the driver. After the link is successfully established, the program sends SQL statements, and the database processes and returns the results according to the input SQL statements.

[0166] (43) Service platform interface

[0167] Service platform data interaction refers to the data interaction between the service platform of each unit and the database system. It mainly provides user system access points to enable seamless access to the database system and obtain data services. As shown in Figure 18 , the user triggers the access to the database system request at the unit service platform. After receiving it, the unit service platform transmits user information to the database system to realize user authentication.

[0168] The main data transmitted between the unit service platform and the database system is user account status information, including account registration, account login, and account cancellation. The transmission interface example is shown in the table below.

[0169] Table 2 User account status information transmission interface example

[0170]

[0171]

[0172] (44) Data call interface

[0173] In order to further break the shackles between different systems and realize the open sharing of aerodynamic data, the database application system provides a data call interface. Through the call interface, other systems can quickly realize data transmission, laying a service foundation for data reuse by each unit based on the system in the later stage. The data call interface provided by the system is shown in the table below.

[0174] Table 3 Data call interface example

[0175]

[0176]

[0177] Five, deployment

[0178] Hardware environment:

[0179] The application server runs on the Windows system and is responsible for receiving, processing, and responding to all requests from the client. The database server runs on the Windows system, and the platform database is MySQL, which is used to store platform application data. The file server is mainly used to store files in the system, such as digital-analog files, grid files, and test result files.

[0180] Table 4 Application server hardware specifications

[0181] Classification Name CPU 2GHz or above Memory 32G or above Hard disk capacity 500G or above

[0182] Software environment:

[0183] Table 5 Database server hardware metrics

[0184]

[0185]

[0186] The above merely illustrates the preferred embodiments of the present application, but the protection scope of the present application is not limited thereto, any person skilled in the art can think of the changes or replacements within the technical range disclosed by the present application without creative labor, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be defined by the protection scope of the claims.

Claims

1. A method for managing aerodynamic subject data of civil aircraft, characterized in that, include: Develop a method for storing civil aircraft aerodynamics data based on train schedules, establish a complete process for data entry and storage according to data storage requirements, and ensure data quality through validity verification and data standardization to establish a standardized civil aircraft aerodynamics data source; Organize and manage the civil aircraft aerodynamic data that has been entered into the database, establish a hierarchical management relationship for aerodynamic data, supplement the description of some test conditions of the project, and formulate data templates as organizational requirements for data file input and output; It provides data retrieval and display for civil aircraft aerodynamics, organizes relevant data relationships, and offers users efficient and easy-to-use data browsing, retrieval, and download services. Maintain civil aircraft aerodynamic data, including data configuration, security monitoring, and allocation of data resource usage permissions; A method for retrieving civil aircraft aerodynamic data was developed, and a data retrieval interface was provided to external systems. Other application systems can obtain standardized civil aircraft aerodynamic data through the interface, thereby achieving data integration and sharing. The train schedule table is used to plan the model status and test conditions during the wind tunnel test planning stage, to conduct the test according to the test outline during the test implementation stage, and to organize and draw the test results during the summary stage. A standard train schedule table must be provided when the data is entered into the database. Users can configure the train schedule table template according to the specific test type, and then add relevant status, conditions and train schedule information. The system will parse the train schedule table when the data is entered into the database. The data entry requirements are specifically determined according to the relevant data specifications for civil aircraft aerodynamic data, including data file entry requirements based on train schedule information, file tag entry requirements, and aerodynamic data entry requirements. The method for developing a civil aircraft aerodynamics-related data entry based on train schedules includes data entry, validity verification, data standardization, data version control, data access control, and data storage. The data version control operation targets files, including valid versions and invalid versions. When a file that has already been entered in the project is entered repeatedly with a newly entered file, the system provides three processing options: retain, retain but invalidate, or overwrite.

2. The method for managing aerodynamic subject data of civil aircraft according to claim 1, characterized in that, The organization and management of the civil aircraft aerodynamic data stored in the database includes basic information organization and management, data file organization and management, file tag organization and management, and aerodynamic data organization and management.

3. The method for managing aerodynamic subject data of civil aircraft according to claim 2, characterized in that, The document tag organization and management includes test result document tags and other document tags. The test result document tags are generated after the document is entered. The document management is operated through the visual view of the train schedule table. By parsing the train schedule table, a tag corresponding to each document is generated.

4. The method for managing aerodynamic subject data of civil aircraft according to claim 1, characterized in that, The aforementioned data retrieval and display for civil aircraft aerodynamics includes data browsing, data retrieval, file preview, data download, and data comparison.

5. The civil aircraft aerodynamic theme data management method according to claim 4, characterized in that, The data retrieval refers to extracting data stored in the database according to user needs based on appropriate matching rules, forming filtered results. Data retrieval targets projects and various types of files, providing two retrieval methods: quick retrieval and advanced retrieval. Further retrieval functions are provided for the retrieval results. Among them, advanced retrieval can be divided into fuzzy retrieval and precise retrieval. The keywords for file retrieval are the tags of the corresponding result files generated by the train schedule table. For the retrieval results, traceability information is provided, requiring the display of the parent node information of the result object.

6. The method for managing aerodynamic subject data of civil aircraft according to claim 1, characterized in that, The maintenance of civil aircraft aerodynamic data includes user permission maintenance, aerodynamic data maintenance, data statistics, and log maintenance.

Images