A method, system, device, and storage medium for version management and difference analysis of a flight simulator configuration database.

Abstract

This application relates to the field of flight simulator configuration management technology, and provides a method, system, device, and storage medium for version management and difference analysis of flight simulator configuration databases. It addresses the problems of insufficient real-time performance, coarse-grained conflict detection, and weak parallel processing capabilities in distributed file system version synchronization schemes. This application collects the topological relationships, semantic information, and version operation history of configuration items in the flight simulator configuration database, establishes a configuration item change model to identify key configuration items and their impact scope; stores multi-version configuration data in a non-volatile memory cross-connect array, enabling high-speed parallel access and parallel comparison through connection state reconstruction; processes multi-site configuration changes to complete version synchronization, conflict detection, and resolution, generating synchronized data; and combines relevant information using structured difference synthesis technology to generate a hierarchical configuration difference report. This application enables effective management and difference analysis of flight simulator configuration database versions.

Description

Technical Field

[0001] This application relates to the field of flight simulator configuration management technology, and in particular to a method, system, device and storage medium for version management and difference analysis of flight simulator configuration database. Background Technology

[0002] In a multi-site collaborative version management scenario for flight simulator configuration databases, each site needs to share and modify configuration data containing topological relationships and semantic information. The technical requirements focus on configuration version synchronization and accurate conflict detection in a distributed environment. Flight simulator configuration items are highly interconnected, and changes have a wide impact, requiring multi-site operations to be quickly synchronized globally. Simultaneously, it is necessary to accurately identify conflicting modifications to the same configuration item by different sites to avoid simulator operational deviations or security risks due to version inconsistencies.

[0003] The current solution for this technical requirement is a version synchronization solution based on a distributed file system. This solution deploys a file system client on each site, stores configuration database file shards on distributed nodes, and uses a timed incremental synchronization mechanism to achieve data interaction between multiple sites. Conflict detection relies on file attribute comparison. When different attributes are detected in the same file shard, a conflict alarm is triggered and the synchronization process is paused.

[0004] The existing solution has obvious drawbacks: First, it lacks real-time performance. The timed synchronization mechanism causes delays in configuration updates between sites, which cannot meet the immediacy requirements of flight simulator configuration changes. Second, the conflict detection granularity is coarse. It is based solely on file fragment attribute comparison, which makes it difficult to identify semantic-level conflicts within configuration items and easily misses key conflict points. Third, the parallel processing capability is weak. The locking mechanism for conflicting file fragments during synchronization limits the efficiency of parallel modification of non-conflicting configuration items by multiple sites. Summary of the Invention

[0005] The purpose of this application is to provide a method, system, device, and storage medium for version management and difference analysis of flight simulator configuration database, so as to solve the problems of insufficient real-time performance, coarse conflict detection granularity, and weak parallel processing capability in the existing distributed file system version synchronization scheme.

[0006] To address the aforementioned technical problems, in a first aspect, this application provides a method for version management and difference analysis of flight simulator configuration databases, comprising:

[0007] Collect topological relationship data between configuration items, semantic information of configuration items, and version operation history from the flight simulator configuration database;

[0008] Based on the topological relationship data, configuration item semantic information, and version operation history, a configuration item change model is established through dependency analysis to identify key configuration items and the scope of their impact.

[0009] Configuration data containing multiple configuration item versions is stored in a non-volatile memory crossbar switch array to achieve high-speed parallel access to multiple version configuration data. Parallel comparison processing of the multiple configuration item versions is supported by reconstructing the connection state of the crossbar switch network in the non-volatile memory crossbar switch array to obtain parallel comparison results.

[0010] Based on the configuration item change model, the impact range of the key configuration items, and the parallel comparison results, the operation conversion technology is applied to convert the configuration change operations generated by different locations into an exchangeable operation sequence. By executing the operation sequence, version synchronization and conflict detection and resolution between multiple sites are completed, and synchronized configuration data is generated.

[0011] Based on the synchronized configuration data and the storage information in the non-volatile memory crossbar switch array, combined with the topological relationship data between the configuration items and the semantic information of the configuration items, the structured difference synthesis technology is used to hierarchically organize and semantically analyze the configuration change content, and generate a hierarchical configuration difference report.

[0012] Optionally, based on the configuration item change model, the impact range of the key configuration items, and the parallel comparison results, the operation transformation technology is applied to convert the configuration change operations generated by different locations into an exchangeable operation sequence. By executing the operation sequence, version synchronization between multiple sites and conflict detection and resolution between multiple sites are completed, generating synchronized configuration data, including:

[0013] Based on the change weights in the configuration item change model and the influence scope of the key configuration items, determine the set of potential conflicting operations among the configuration change operations received from each site;

[0014] Based on the bitmap information in the parallel comparison results, analyze the data modification content of the same configuration item in the set of potential conflicting operations;

[0015] By applying operation transformation technology, the execution order of the configuration change operations is adjusted according to the timestamp of the configuration change operation and the data modification content, thereby generating an operation sequence that is consistent and interchangeable across all sites.

[0016] According to the operation sequence, each configuration change operation is executed to complete the multi-site version synchronization. During the execution, conflict detection is performed on change operations targeting the same configuration item. At the same time, conflicts are resolved based on the keyword set in the semantic information of the configuration item to generate synchronized configuration data.

[0017] Optionally, the application operation conversion technology adjusts the execution order of the configuration change operations based on the timestamp of the configuration change operation and the data modification content, generating an operation sequence that is consistent and interchangeable across all sites, including:

[0018] The conflict resolution rules of the application operation conversion technology establish a partial order relationship of operation execution based on the timestamp of the configuration change operation;

[0019] Based on the data modification content, identify concurrent modification operations on the same configuration item parameter;

[0020] Based on the partial order relationship and the semantic relevance of concurrent modification operations, the execution context of the configuration change operation is reconstructed;

[0021] By using the state transition function of the operation transformation algorithm, operations with execution conflicts are converted into commutative operation units;

[0022] The operation sequence is reorganized according to the transformed interchangeable operation unit to generate an operation sequence that is consistent and interchangeable across all sites.

[0023] Optionally, storing the configuration data containing multiple configuration item versions in a non-volatile memory crossbar array enables high-speed parallel access to the multi-version configuration data. Parallel comparison processing of the multiple configuration item versions is supported by reconstructing the connection state of the crossbar network in the non-volatile memory crossbar array to obtain parallel comparison results, including:

[0024] Multiple versions of data for each configuration item are stored in a contiguous storage area of ​​a non-volatile memory crossbar switch array in order of version identifier;

[0025] Each configuration item is assigned an independent cross switch control line, and the connection path of each switch unit in the cross switch network is reconstructed by changing the level state of the cross switch control line.

[0026] When performing version comparison, the configuration item data of different versions are simultaneously routed to multiple parallel comparators by coordinating the combination of the level states of multiple cross switch control lines.

[0027] The parallel comparator simultaneously compares the configuration item data of multiple versions, generates and outputs bitmap information that identifies data differences as the parallel comparison result, and the parallel comparison result contains the specific location and content information of the data differences between each version.

[0028] Optionally, based on the synchronized configuration data and the storage information in the non-volatile memory crossbar switch array, combined with the topological relationship data and semantic information between configuration items, a structured difference synthesis technique is used to hierarchically organize and semantically analyze the configuration change content, generating a hierarchical configuration difference report, including:

[0029] Identify configuration items whose content has changed from the synchronized configuration data and form a set of changed configuration items;

[0030] Based on the directed graph structure in the topological relationship data, and using the configuration items in the set of changed configuration items as nodes, a hierarchical tree structure representing the dependencies between configuration items is constructed.

[0031] Traverse the hierarchical tree structure, group the change configuration items at the same level according to the semantic association strength provided by the keyword set in the semantic information of the configuration items, and determine the semantic theme of each group;

[0032] For each changed configuration item within a group, a text fragment describing the specific changes to the changed configuration item is generated by combining the version comparison results stored in the non-volatile memory crossbar switch array.

[0033] Based on the hierarchical relationship of the tree structure and the semantic topics of the groups, the text fragments are organized to synthesize a configuration difference report with a hierarchical structure.

[0034] Optionally, the step of establishing a configuration item change model based on the topology relationship data, configuration item semantic information, and version operation history through dependency analysis to identify key configuration items and the scope of influence of the key configuration items includes:

[0035] Based on the directed graph structure in the topological relationship data, calculate the number of in-degree connections and the number of out-degree connections for each configuration item in the directed graph structure;

[0036] Based on the set of keywords in the semantic information of the configuration items, the frequency of keyword occurrence for each configuration item is statistically analyzed.

[0037] Based on the operation records in the version operation history, the modification frequency of each configuration item is calculated;

[0038] By combining the number of in-degree connections, the number of out-degree connections, the frequency of keyword occurrence, and the frequency of modification, a change weight for each configuration item is generated;

[0039] Configuration items whose change weight exceeds a preset threshold are identified as critical configuration items;

[0040] Starting with the key configuration item as the starting node, traverse along the edges of the directed graph structure, and determine the set of all configuration items reached by the traversal as the influence range of the key configuration item.

[0041] Optionally, the acquisition of topological relationship data between configuration items, semantic information of configuration items, and version operation history in the flight simulator configuration database includes:

[0042] Extract the attribute tables of each configuration item from the system registry of the flight simulator configuration database. Based on the connection guidance information in the attribute tables, parse the physical connections and logical references between the configuration items, construct a directed graph structure with configuration items as nodes and the physical connections and logical references as edges, and form the topological relationship data between the configuration items.

[0043] Extract a set of keywords that characterize the function and attributes of the configuration item from the preset description text field and annotation field of the configuration item in the flight simulator configuration database to form the configuration item semantic information;

[0044] Extract all operation records for configuration items from the transaction log of the flight simulator configuration database. The operation records include operation type, target configuration item identifier, operation timestamp, and operation content details. Organize the operation records in the order of operation timestamps to form a version operation history.

[0045] Secondly, this application provides a flight simulator configuration database version management and difference analysis system, including:

[0046] The data acquisition module is used to collect topological relationship data between configuration items, semantic information of configuration items, and version operation history from the flight simulator configuration database.

[0047] The identification module is used to establish a configuration item change model based on the topological relationship data, configuration item semantic information and version operation history through dependency analysis, so as to identify key configuration items and the scope of influence of the key configuration items;

[0048] The processing module is used to store configuration data containing multiple configuration item versions in a non-volatile memory cross switch array to achieve high-speed parallel access to multiple version configuration data, and to support parallel comparison processing of the multiple configuration item versions by reconstructing the connection state of the cross switch network in the non-volatile memory cross switch array to obtain parallel comparison results.

[0049] The synchronization module is used to convert configuration change operations generated by different locations and stations into an exchangeable operation sequence based on the configuration item change model, the impact range of the key configuration items, and the parallel comparison results. By executing the operation sequence, version synchronization between multiple stations and conflict detection and resolution between multiple stations are completed, and synchronized configuration data is generated.

[0050] The generation module is used to generate a hierarchical configuration difference report by using structured difference synthesis technology to hierarchically organize and semantically analyze the configuration change content based on the synchronized configuration data and the storage information in the non-volatile memory cross switch array, combined with the topological relationship data between the configuration items and the semantic information of the configuration items.

[0051] Thirdly, this application provides an electronic device, comprising:

[0052] Memory, used to store computer programs;

[0053] A processor, used to execute the computer program, implements the steps of the flight simulator configuration database version management and difference analysis method as described in the first aspect above.

[0054] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the steps of the flight simulator configuration database version management and difference analysis method described in the first aspect above.

[0055] The beneficial effects of this application are:

[0056] The method for version management and difference analysis of flight simulator configuration database provided in this application collects topological relationship data, semantic information, and version operation history of the flight simulator configuration database. Combined with a configuration item change model established by dependency analysis, it can accurately identify key configuration items and their impact scope, providing clear targets for subsequent management. Storing multi-version configuration data in a non-volatile memory crossbar array enables high-speed parallel access to multi-version data and efficient parallel comparison by reconstructing the crossbar network connection state. Based on the change model, the impact scope of key configuration items, and the parallel comparison results, operation conversion technology is applied to convert multi-site configuration change operations into exchangeable operation sequences, effectively completing version synchronization and conflict detection and resolution between multiple sites, ensuring configuration consistency in a distributed environment. Finally, combining synchronized data, storage information, and topological semantic information, a hierarchical configuration difference report is generated using structured difference synthesis technology, achieving a clear presentation of configuration change content and semantic association analysis. Overall, it achieves the technical effects of efficient management, synchronization, accurate conflict handling, and intuitive difference display of multi-site collaborative versions of the flight simulator configuration database.

[0057] Furthermore, based on the change weights and impact scope of key configuration items in the configuration item change model, a set of potential conflicting operations is determined. This is combined with bitmap information analysis of the parallel comparison results to analyze the data modifications of the same configuration item within the set. Then, operation transformation technology is applied to adjust the execution order based on the change operation timestamps and data modifications, generating a consistent and interchangeable operation sequence for each site. Finally, the execution sequence completes multi-site version synchronization. During this process, conflicts involving changes to the same configuration item are detected, and conflicts are resolved based on a set of semantic information keywords for the configuration items, generating synchronized configuration data. This step accurately locates potential conflicts in configuration changes across multiple sites, ensures the consistency and interchangeability of operation sequences across sites through operation transformation technology, efficiently completes version synchronization, and accurately resolves conflicts using semantic information, further improving the accuracy and reliability of configuration synchronization in a distributed environment. Attached Figure Description

[0058] To more clearly illustrate the technical solutions of the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0059] Figure 1 A flowchart illustrating a method for version management and difference analysis of a flight simulator configuration database provided in this application embodiment;

[0060] Figure 2 This application provides a schematic diagram illustrating the specific implementation process of a method for version management and difference analysis of a flight simulator configuration database.

[0061] Figure 3 This application provides a schematic diagram illustrating a specific implementation of a method for version management and difference analysis of a flight simulator configuration database.

[0062] Figure 4 This is a schematic diagram of the structure of a flight simulator configuration database version management and difference analysis system provided in an embodiment of this application. Detailed Implementation

[0063] In multi-site collaborative version management of flight simulator configuration databases, existing version synchronization schemes based on distributed file systems have significant drawbacks: the timed incremental synchronization mechanism causes delays in configuration updates between sites, making it difficult to meet real-time requirements; the conflict detection method that relies solely on file fragment attribute comparison is coarse-grained and cannot identify semantic-level conflicts within configuration items; the locking mechanism for conflicting file fragments during synchronization limits the efficiency of parallel modification of non-conflicting configuration items by multiple sites. These problems can easily lead to inconsistent configuration versions, which in turn can cause deviations in flight simulator operation or safety risks, necessitating a better management solution.

[0064] To address the aforementioned issues, this application proposes a method for version management and difference analysis of flight simulator configuration databases. Its core lies in establishing a change model by collecting configuration item topological relationships, semantic information, and version operation history. This is combined with the high-speed parallel access and comparison capabilities of a non-volatile memory crossbar array, along with operation conversion technology and structured difference synthesis technology, to achieve end-to-end management. Specifically, this method first identifies key configuration items and their impact scope through the change model. Then, it utilizes a non-volatile memory crossbar array to improve the efficiency of multi-version data processing. Subsequently, it applies operation conversion technology to generate exchangeable operation sequences to complete multi-site synchronization and accurate conflict resolution. Finally, it generates a hierarchical difference report. This solution addresses the real-time performance deficiency through high-speed parallel storage and comparison, achieves fine-grained conflict detection through the change model and semantic analysis, and overcomes the limitations of parallel processing through exchangeable operation sequences. It fundamentally solves the shortcomings of existing solutions, effectively ensuring the efficiency and accuracy of multi-site collaborative management of flight simulator configuration databases.

[0065] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are merely some embodiments of the present application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0066] The core of this application is to provide a method for version management and difference analysis of flight simulator configuration databases, and a flowchart of one specific implementation is shown below. Figure 1 As shown, the method includes:

[0067] S101. Collect topological relationship data between configuration items, semantic information of configuration items, and version operation history from the flight simulator configuration database;

[0068] Optionally, step S101 may specifically include the following steps:

[0069] S1011. Extract the attribute table of each configuration item from the system registry of the flight simulator configuration database. Based on the connection guidance information in the attribute table, parse the physical connection and logical reference relationship between the configuration items, construct a directed graph structure with the configuration items as nodes and the physical connection and logical reference relationship as edges, and form the topological relationship data between the configuration items.

[0070] S1012. Extract a set of keywords that characterize the function and attributes of the configuration item from the preset description text field and annotation field of the configuration item in the flight simulator configuration database to form configuration item semantic information.

[0071] S1013. Extract all operation records for configuration items from the transaction log of the flight simulator configuration database. The operation records include operation type, target configuration item identifier, operation timestamp and operation content details. Organize the operation records in the order of operation timestamps to form a version operation history.

[0072] In the above scheme, the flight simulator configuration database refers to a database that stores various settings parameters and configuration information of the flight simulator. It contains data on various configuration items required for the operation of the flight simulator and can be used for configuration management and parameter control of the flight simulator. The topological relationship data between configuration items refers to structured data reflecting the physical connections and logical references between configuration items, including information on configuration item nodes and connection edges, which can be used to analyze the associations between configuration items. The semantic information of configuration items refers to a set of keywords that embody the functions and attributes of configuration items, containing words that characterize the core functions and associated attributes of configuration items, which can be used for configuration item conflict resolution and semantic association analysis. The version operation history refers to a set of records of operations performed on configuration items arranged in chronological order, including operation type, target configuration item identifier, operation timestamp, and operation content details, which can be used to trace the change trajectory of configuration items.

[0073] In this embodiment, firstly, in step S1011, attribute tables for each configuration item are exported in batches from the system registry of the flight simulator configuration database. These attribute tables record in detail the name, unique identifier, parameter range, and connection guidance information of the configuration item. Then, a relational parsing algorithm is used to semantically decompose the connection guidance information in the attribute tables to distinguish between physical connections and logical references. Next, a directed graph is generated using graph structure construction technology, with the configuration item as a node and the parsed connection relationship as a directed edge, thus forming topological relationship data. For example, the attribute tables for configuration item A (flight attitude sensor parameters) and configuration item B (flight control module parameters) are extracted from the system registry. According to the connection guidance information in the attribute table that "configuration item A outputs data through communication port COM3 to configuration item B input port COM5", the physical connection between the two is first parsed as COM3-COM5 port docking, and the logical reference relationship is A transmitting data to B. Then, A and B are used as nodes, and a directed edge from A to B is drawn to construct a directed graph containing the relationship between the two configuration items.

[0074] Secondly, in step S1012, the preset description text fields and annotation fields of each configuration item are found based on text positioning technology. The field text is segmented, stop words are removed, and weights are calculated using keyword extraction algorithms such as TF-IDF. High-frequency keywords that represent the core functions and related attributes of the configuration items are selected and organized into a set to form the semantic information of the configuration items. For example, from the description text of configuration item C (engine thrust parameters) "used to set the maximum thrust of the engine and the thrust adjustment rate, supporting dynamic response to throttle commands" and the annotation "related to throttle control module and fuel injection parameters", the algorithm calculates and extracts "maximum thrust of the engine", "throttle adjustment rate", "throttle control module" and "fuel injection parameters" as a set of keywords.

[0075] Finally, in step S1013, the database transaction log file is opened using a log reading tool. Log parsing technology is used to extract all configuration item operation records by time dimension. Each record contains information such as operation type (modify, add, delete, etc.), target configuration item identifier, operation timestamp accurate to the second, and specific parameter changes. Then, a timestamp sorting algorithm is used to sort the extracted operation records in ascending order to form a version operation history. For example, operation records such as "2025-09-01 10:00:32 Modify configuration item A, adjust sampling frequency from 40Hz to 50Hz", "2025-09-01 10:30:15 Add configuration item D, set navigation map update cycle to 30min", and "2025-09-01 11:15:08 Delete configuration item E, old version meteorological data receiving parameters" are extracted from the transaction log. These records are arranged in order of operation timestamp to form the version operation history.

[0076] In practical applications, in the configuration database management of the Model A flight simulator, the attribute tables of 20 configuration items, including avionics system configuration items and control system configuration items, were first extracted from the system registry. Based on the connection guidance information in the attribute tables, the logical reference relationship between the avionics system configuration items and the display system configuration items, and the physical connection relationship between the control system configuration items and the actuator configuration items were parsed out, and a directed graph with these configuration items as nodes and relationships as edges was constructed. Next, the set of keywords such as "avionics data fusion" and "control stick travel" were extracted from the preset description text and annotation fields of each configuration item. Finally, 80 operation records of these configuration items within the past month were extracted from the transaction log and organized into a version operation history according to the operation timestamp.

[0077] The above-mentioned S101 overall solution provides comprehensive and basic data support for subsequent operations such as establishing configuration item change models, realizing multi-version data processing and multi-site synchronization by collecting three types of key information from the flight simulator configuration database. This enables subsequent management processes to be carried out based on accurate raw data, ensuring the smooth progress of the entire configuration database version management and difference analysis work.

[0078] S102. Based on the topological relationship data, configuration item semantic information, and version operation history, a configuration item change model is established through dependency analysis to identify key configuration items and the scope of influence of the key configuration items.

[0079] Optionally, step S102 may specifically include the following steps:

[0080] S1021. Based on the directed graph structure in the topological relationship data, calculate the number of in-degree connections and the number of out-degree connections for each configuration item in the directed graph structure;

[0081] S1022. Based on the set of keywords in the semantic information of the configuration items, count the frequency of keyword occurrence for each configuration item;

[0082] S1023. Based on the operation records in the version operation history, calculate the modification frequency of each configuration item;

[0083] S1024. By combining the number of in-degree connections, the number of out-degree connections, the frequency of occurrence of keywords, and the frequency of modification, a change weight for each configuration item is generated.

[0084] S1025. Identify configuration items whose change weight exceeds a preset threshold as key configuration items;

[0085] S1026. Starting with the key configuration item as the starting node, traverse along the edges of the directed graph structure, and determine the set of all configuration items reached by the traversal as the influence range of the key configuration item.

[0086] In the above scheme, topological relationship data refers to structured data reflecting the physical connections and logical references between configuration items, including information on configuration item nodes and connection edges, which can be used to analyze the association between configuration items. Configuration item semantic information refers to a set of keywords reflecting the functions and attributes of configuration items, including words representing the core functions and associated attributes of configuration items, which can be used for configuration item conflict resolution and semantic association analysis. Version operation history refers to a set of records of operations performed on configuration items in chronological order, including operation type, target configuration item identifier, operation timestamp, and operation content details, which can be used to trace the change trajectory of configuration items. Dependency analysis is an analytical method that determines the degree of interdependence between configuration items by analyzing the connections, semantics, and operations between them, and can be used to build configuration item change models. Configuration item change models are models that integrate multi-dimensional information about configuration items to assess the importance and scope of impact of configuration item changes, and can be used to identify key configuration items. Key configuration items are those whose change weight exceeds a preset threshold and have a significant impact on system operation, and can be designated as key management objects. The scope of influence of a critical configuration item refers to the set of all configuration items reached by traversing the directed graph along the topology, starting from the critical configuration item. It can be used to clarify the scope of the impact of a change.

[0087] In this embodiment, firstly, the graph structure analysis algorithm in step S1021, based on the directed graph structure in the topological relationship data, employs a graph node degree calculation algorithm to traverse each configuration item node and count the number of edges pointing to that node as the in-degree connection number. For example, for node D, there are two edges pointing to it, B→D and C→D, so its in-degree connection number is 2. Simultaneously, the number of edges pointing from this node to other nodes is counted as the out-degree connection number. For example, for node A, there are two edges pointing from it, A→B and A→C, so its out-degree connection number is 2. In this way, the in-degree and out-degree connection numbers for all configuration item nodes are calculated.

[0088] Secondly, step S1022 uses text statistics technology to summarize the keyword sets of all configuration items into a keyword summary set based on the keyword set in the semantic information of the configuration items. Then, for each keyword in the keyword set of each configuration item, the number of times it appears in the keyword summary set is counted. The occurrence frequency of all keywords is added together to obtain the keyword occurrence frequency of the configuration item. For example, the keyword set of configuration item B is "thrust adjustment", "fuel control" and "throttle response". These three words appear 15 times in all the semantic information of the configuration items, so its keyword occurrence frequency is 15.

[0089] Next, step S1023 calculates the time range of modification frequency and then obtains the version operation history, which contains all operation records within that time range. Each record is labeled with information such as operation type and target configuration item identifier. Each operation record in the version operation history is traversed, and records with the operation type "modification" are filtered out. These modification records are then categorized and statistically analyzed according to the target configuration item identifier. This completes the statistical analysis of the modification frequency of each configuration item within the specified time range. For example, if configuration item C is modified 8 times in one month in the version operation history, its modification frequency is 8.

[0090] Then, in step S1024, the number of in-degree connections, the number of out-degree connections, the frequency of keyword occurrence, and the frequency of modification are fused according to a preset weight ratio using a weight fusion algorithm to generate a change weight for each configuration item. For example, the preset weights for in-degree, out-degree, keyword frequency, and modification frequency are 0.2, 0.2, 0.3, and 0.3, respectively. If the in-degree of configuration item D is 2, the out-degree is 3, the keyword frequency is 12, and the modification frequency is 6, then the change weight is 2×0.2+3×0.2+12×0.3+6×0.3=0.4+0.6+3.6+1.8=6.4.

[0091] Next, in step S1025, based on factors such as the management needs of the flight simulator configuration database, system stability requirements, and historical operating data, a threshold for change weight is preset. This threshold can be adjusted according to actual conditions. Then, the change weight of each configuration item generated in step S1024 is obtained, and the change weight of each configuration item is compared with the preset threshold one by one. Finally, configuration items with change weights greater than the preset threshold are marked and identified as key configuration items. For example, if the preset threshold is 5 and the change weight of configuration item K is 6.2, which is greater than the threshold, then configuration item K is identified as a key configuration item.

[0092] Finally, step S1026 uses the key configuration item as the starting node and employs a graph traversal algorithm (such as depth-first traversal) to traverse along the edges of the directed graph structure. All configuration items visited during the traversal are collected to form a set, which is the influence range of the key configuration item. For example, if the key configuration item M is the starting node and the directed graph is traversed to nodes N, O, P, and Q, then {M, N, O, P, Q} is the influence range of configuration item M.

[0093] In practical applications, in the configuration database management of the Model A flight simulator, the avionics system configuration item is first calculated based on the directed graph of topological relationship data, with an in-degree connection of 4 and an out-degree connection of 5. Then, the frequency of occurrence of keywords such as "avionics data fusion" and "signal processing" is counted as 18. Then, it is found from the version operation history that it has been modified 7 times in one month. Next, the change weight is obtained by fusion according to the preset weight as 4×0.2+5×0.2+18×0.3+7×0.3=0.8+1+5.4+2.1=9.3. Since the preset threshold is 6, the avionics system configuration item is identified as a critical configuration item. Finally, the avionics system configuration item is traversed along the directed graph as the starting node to reach 6 configuration items such as the display system and navigation system. These configuration items constitute the influence range of the critical configuration item.

[0094] The overall solution of S102 described above, by integrating multi-dimensional data to establish a configuration item change model, can accurately identify the key configuration items that have a significant impact on the operation of the flight simulator configuration database and their scope of impact. This provides clear key objects and impact boundaries for subsequent configuration item change management, conflict detection and other work, which helps to improve the targeting and efficiency of configuration database version management and reduce system risks caused by changes in key configuration items.

[0095] S103. The configuration data containing multiple configuration item versions is stored in a non-volatile memory cross switch array to achieve high-speed parallel access to the configuration data of multiple versions. The parallel comparison processing of the multiple configuration item versions is supported by reconstructing the connection state of the cross switch network in the non-volatile memory cross switch array to obtain the parallel comparison result.

[0096] Optionally, step S103 may specifically include the following steps:

[0097] S1031. Store multiple versions of each configuration item in a contiguous storage area of ​​a non-volatile memory crossbar switch array in order of version identifier.

[0098] S1032. Assign an independent cross switch control line to each configuration item, and reconstruct the connection path of each switch unit in the cross switch network by changing the level state of the cross switch control line.

[0099] S1033. When performing version comparison, the configuration item data of different versions are simultaneously routed to multiple parallel comparators by coordinating the combination of the level states of multiple cross switch control lines.

[0100] S1034. The parallel comparator simultaneously compares the configuration item data of multiple versions, generates and outputs bitmap information that identifies data differences as the parallel comparison result, and the parallel comparison result includes the specific location and content information of the data differences between each version.

[0101] In the above scheme, configuration data for multiple configuration item versions refers to the modified data set of the same configuration item generated at different time points, containing parameter information and version identifiers for each version, which can be used for version comparison and tracing. A non-volatile memory crossbar switch array is a storage device that combines non-volatile storage characteristics with a crossbar switch network structure, containing storage units and crossbar switch units, enabling high-speed data storage and flexible routing. High-speed parallel access refers to an efficient data access method that performs read and write operations on multiple data simultaneously, improving data processing speed. The connection status of the crossbar switch network refers to the on / off status of each switch unit in the crossbar switch array, which determines the data transmission path. Parallel comparison processing refers to the operation method of comparing multiple configuration item version data simultaneously, which can quickly obtain version differences. Parallel comparison results refer to the information generated through parallel comparison that identifies data differences, including the location and content of the differences, which can be used for subsequent conflict detection and analysis.

[0102] In this embodiment, firstly, all version data of each configuration item are organized and sorted according to the version identifier in step S1031. Then, a dedicated storage area is allocated for each configuration item in the non-volatile memory crossbar switch array, and the storage unit addresses in the area are ensured to be continuous. Finally, the sorted version data is written into the allocated continuous storage area in sequence. Each version data occupies a continuous sub-area. For example, configuration item A has three versions, V1, V2, and V3. Its data is stored in the continuous storage units 001-005, 006-010, and 011-015 of the array in the order of the version identifier from oldest to newest.

[0103] Secondly, in step S1032, an independent cross switch control line is assigned to each configuration item based on the number of configuration items, ensuring that each control line corresponds to only one configuration item. Next, the correspondence between the control line level and the on / off state of the switch unit is determined. The control circuit changes the level state of each cross switch control line. When data transmission for a configuration item is required, its corresponding control line is set to a high level, causing the relevant switch unit to conduct and form a connection path; when not required, it is set to a low level to disconnect the path. In this way, the connection paths of each switch unit in the cross switch network are reconstructed. For example, control line L1 is assigned to configuration item A. When L1 is high, the corresponding switch unit is on; when it is low, it is off, thus reconstructing its data transmission path.

[0104] Then, step S1033 clarifies the configuration items and their specific versions that need to be compared, for example, determining that versions V2, V3, and V4 of configuration item D will be compared. Based on the storage areas where these versions reside and the corresponding cross-switch control lines, the required level states for each control line are planned, forming a level state combination scheme. For example, for configuration item D, V2 corresponds to control line L4, V3 to L5, and V4 to L6; a combination scheme is planned where L4, L5, and L6 are all set to high level. Then, the control circuit coordinates the level states of these three cross-switch control lines, ensuring they are simultaneously at a high level according to the planned combination scheme. At this time, the switch units corresponding to the storage areas where each version's data resides are turned on, and the data is simultaneously routed to multiple parallel comparators through the reconstructed connection path. For example, V2 data is routed to comparator C5, V3 to C6, and V4 to C7.

[0105] Finally, using the parallel comparison algorithm in step S1034, multiple parallel comparators simultaneously compare the received version data bit by bit. Based on the comparison results, bitmap information is generated, and the bit corresponding to the data position in the bitmap is set. If the data at that position is the same, it is marked as "0"; if there is a difference, it is marked as "1". The specific content of the difference position is recorded. For example, if the 5th bit of the data in versions V2 and V3 is different, the 5th bit of the bitmap is set to "1", and the bit is recorded as "a" in V2 and "b" in V3. Finally, the generated bitmap information and the difference content are output as the parallel comparison result.

[0106] In practical applications, during the configuration database management of the Model A flight simulator, when executing step S103, the four versions of engine control parameter configuration items V1-V4 are first stored in the continuous storage areas 020-024, 025-029, 030-034, and 035-039 of the non-volatile memory cross switch array according to the version identifier. Then, an independent control line L2 is assigned to this configuration item, and the connection path of the corresponding switch unit in the cross switch network is reconstructed by adjusting the level state of L2. When it is necessary to compare versions V2 and V4, the control line level combination of L2 and the corresponding version is coordinated to route the two versions of data to parallel comparators C3 and C4 respectively. Finally, the parallel comparators compare the two data bit by bit and generate difference information presented in the form of a bitmap. The 8th and 15th bits of the bitmap are marked as "1", indicating that there is a difference in the data at these two positions. This bitmap is the parallel comparison result.

[0107] The above-mentioned S103 overall solution achieves high-speed parallel access and comparison of multi-version configuration data through a non-volatile memory crossbar switch array, which greatly improves the data storage access efficiency and version comparison speed. It can quickly and accurately obtain the difference information between versions, providing an efficient data processing foundation for subsequent multi-site configuration synchronization and conflict detection, and ensuring the timeliness and accuracy of configuration database version management.

[0108] S104. Based on the configuration item change model, the impact range of the key configuration items and the parallel comparison results, the operation conversion technology is applied to convert the configuration change operations generated by different location sites into an exchangeable operation sequence. By executing the operation sequence, version synchronization between multiple sites and conflict detection and resolution between multiple sites are completed, and synchronized configuration data is generated.

[0109] Optionally, step S104 may specifically include the following steps:

[0110] S1041. Based on the change weight in the configuration item change model and the influence range of the key configuration item, determine the set of potential conflicting operations in the configuration change operations received from each site;

[0111] S1042. Based on the bitmap information in the parallel comparison results, analyze the data modification content of the same configuration item in the potential conflict operation set;

[0112] S1043. Apply operation conversion technology to adjust the execution order of the configuration change operation based on the timestamp of the configuration change operation and the data modification content, and generate an operation sequence that is consistent and interchangeable across all sites.

[0113] S1044. According to the operation sequence, execute each configuration change operation to complete multi-site version synchronization, and during the execution, perform conflict detection on change operations for the same configuration item, and resolve conflicts based on the keyword set in the semantic information of the configuration item to generate synchronized configuration data.

[0114] Specifically, step S1043 includes the following processes: applying the conflict resolution rules of the operation transformation technology, establishing a partial order relationship for operation execution based on the timestamp of the configuration change operation; identifying concurrent modification operations on the same configuration item parameter based on the data modification content; reconstructing the execution context of the configuration change operation based on the partial order relationship and the semantic relevance of the concurrent modification operations; converting operations with execution conflicts into exchangeable operation units through the state transition function of the operation transformation algorithm; and reorganizing the operation sequence according to the converted exchangeable operation units to generate an operation sequence with consistency and exchangeability across all sites.

[0115] In the above scheme, operation conversion technology refers to the technique of adjusting the order of configuration change operations in a distributed environment to make the operations interchangeable, thus achieving consistency across multiple sites. Different location sites refer to flight simulator configuration management sites distributed across different regions or network nodes, each capable of generating configuration change operations. Configuration change operations refer to modifications, additions, and deletions performed by a site on configuration items, including operation content and timestamps. An interchangeable operation sequence refers to a set of operations whose execution order does not affect the final result, ensuring version consistency across multiple sites. Version synchronization between multiple sites refers to the process of keeping configuration data consistent across sites, avoiding data discrepancies; multi-site conflict detection and resolution refers to identifying and resolving configuration change conflicts between sites, ensuring the accuracy of configuration data. Synchronized configuration data refers to unified configuration data formed after version synchronization and conflict resolution, which can be used uniformly across all sites.

[0116] In this embodiment of the application, firstly, step S1041 extracts the change weight of each configuration item, as well as the key configuration items and their scope of influence from the configuration item change model. Then, all configuration change operations sent from different location stations are collected. Each operation includes information such as the target configuration item identifier and operation content. Through a conflict screening algorithm, it is determined whether the target configuration item of each configuration change operation belongs to a key configuration item or a configuration item within its scope of influence. If it does, the operation is included in the potential conflict operation set. For example, if the change weight of a key configuration item A exceeds the threshold, its scope of influence includes B and C. The change operations of each station on A, B, and C are determined as the potential conflict operation set.

[0117] Secondly, the parallel comparison results generated in step S1034 are obtained through step S1042. Bitmap information used to identify data differences is extracted from the results. Operations with the same target configuration item identification are selected from the set of potential conflicting operations, i.e., change operations for the same configuration item. Then, the specific modification content of these change operations for the same configuration item is viewed by combining the difference positions marked in the bitmap information. For example, the bitmap shows that both site 1 and site 2 have modified the 5th bit of configuration item A. Analysis shows that site 1 changed it to "10" and site 2 changed it to "15".

[0118] Next, step S1043 applies the conflict resolution rules of the operation transformation technology to extract the timestamp of each configuration change operation. A partial order relationship for operation execution is established based on the chronological order of the timestamps. Based on the data modification content analyzed in step S1042, concurrent modification operations modifying the same configuration item and parameter are identified. Then, based on the established partial order relationship and the semantic relevance of the concurrent modification operations, the execution context of the configuration change operations is reconstructed, clarifying the initial state of the configuration data during each operation's execution. Next, through the state transition function of the operation transformation algorithm, conflicting operations and their execution contexts are input, converting conflicting operations into commutative operation units. According to these commutative operation units, the operation sequence is reorganized based on the partial order relationship, generating a consistent and commutative operation sequence whose execution order does not affect the final result across all sites. For example, if the timestamp determines that operation 1 occurs before operation 2, the conversion ensures that the execution order of the two operations does not affect the result, generating a commutative operation sequence.

[0119] Finally, in step S1044, the interchangeable operation sequence generated in step S1043 is distributed to various location stations to ensure that each station obtains the same operation sequence. Each station executes each configuration change operation sequentially according to the operation sequence. During execution, a conflict detection algorithm is used to detect whether there are contradictions in the change operations for the same configuration item. When a conflict is detected, the keyword set in the semantic information of the configuration item is called to analyze the configuration item functions and associated attributes involved in the conflicting operation. For example, based on the keyword "associated with flight attitude stability control" in the semantic information of configuration item M, the impact of the conflicting operation on this function is determined, and then the modification value that better meets the requirements of flight attitude stability control is selected. Finally, after all stations have executed the operation sequence and completed conflict resolution, the resulting configuration data is the synchronized configuration data, and the configuration data of each station is consistent.

[0120] In practical applications, during the multi-site configuration management of the A-series flight simulator, when executing step S104, the 12 change operations of sites 1, 2, and 3 on the three configuration items with a change weight of 8.5 in the configuration item change model, namely "avionics system parameters" and their scope of influence (display system, communication system), are identified as a set of potential conflicting operations. Then, based on the bitmap information of the parallel comparison results, it is found that both sites 1 and 2 have modified the 8th bit of the avionics system parameters, changing it to "20" and "25" respectively. Next, operation conversion technology is applied to determine that the operation of site 1 comes first according to the timestamp, and the conflicting operations are converted through the state transition function to generate an exchangeable operation sequence. Finally, the sequence is executed to complete the synchronization. During the process, the above-mentioned conflict is detected. Combining the keyword "associated navigation data transmission rate" in the semantic information of the avionics system parameters to resolve the conflict, "22" is determined as the synchronization value, and the synchronized configuration data is generated.

[0121] The above-mentioned S104 overall solution, through the combination of operation conversion technology and multi-dimensional information, realizes the generation of exchangeable sequences of configuration change operations at different sites, effectively completes multi-site version synchronization, and accurately detects and resolves configuration conflicts, ensuring the consistency and accuracy of configuration data in a distributed environment, and providing unified and reliable configuration data support for each site of the flight simulator.

[0122] S105. Based on the synchronized configuration data and the storage information in the non-volatile memory cross switch array, combined with the topological relationship data between the configuration items and the semantic information of the configuration items, the structured difference synthesis technology is used to hierarchically organize and semantically analyze the configuration change content, and generate a hierarchical configuration difference report.

[0123] Optionally, step S105 may specifically include the following steps:

[0124] S1051. Identify configuration items whose content has changed from the synchronized configuration data and form a set of changed configuration items;

[0125] S1052. Based on the directed graph structure in the topological relationship data, and using the configuration items in the set of changed configuration items as nodes, construct a hierarchical tree structure representing the dependency relationship between configuration items;

[0126] S1053. Traverse the hierarchical tree structure, group the change configuration items at the same level according to the semantic association strength provided by the keyword set in the semantic information of the configuration items, and determine the semantic theme of each group.

[0127] S1054. For each changed configuration item in each group, a text fragment describing the specific changes to the changed configuration item is generated by combining the version comparison results stored in the non-volatile memory cross switch array.

[0128] S1055. Organize the text fragments according to the hierarchical relationship of the hierarchical tree structure and the semantic topics of the groups, and synthesize a configuration difference report with a hierarchical structure.

[0129] In the above scheme, the storage information in the non-volatile memory crossbar switch array refers to the multi-version configuration data and version comparison information stored in the array, which can provide a basis for tracing changes. Structured difference synthesis technology refers to the technology of hierarchically organizing and semantically associating configuration change content, which can generate a clear and organized difference report. Configuration change content refers to the specific information of the modifications made to configuration items in the version update, including the location and content of the changes. Hierarchical organization refers to the method of dividing the change content into different levels according to the dependencies between configuration items, which can reflect the hierarchical relationship of changes. Semantic association analysis refers to the process of analyzing the functional relationships between changed configuration items based on a set of keywords, which can achieve grouping of similar changes. A hierarchical configuration difference report is a report document that clearly presents the configuration change situation, organized by hierarchy and semantic themes, and can intuitively display the change information.

[0130] In the embodiments of this application, such as Figure 2 As shown, firstly, step S1051 obtains the synchronized configuration data generated in step S1044, as well as the historical version data of the corresponding configuration items stored in the non-volatile memory crossbar switch array. For example, the synchronized configuration data includes the latest content of configuration items A, B, C, and D, and the array stores the historical V1 version data of these configuration items. Secondly, a data comparison algorithm is used to compare the content of each configuration item in the synchronized configuration data with its historical version data stored in the array bit by bit or field by field to determine whether there are differences. For example, comparing the content of synchronized configuration item A with the V1 version, three differences are found; the content of configuration item B is consistent with the V1 version. Finally, all configuration items with differences are filtered out and organized into a set of changed configuration items. For example, if configuration items A, C, and D have differences, a set of changed configuration items {A, C, D} is formed.

[0131] Secondly, in step S1052, a directed graph structure is extracted from the topological relationship data, and all configuration item nodes are extracted from the set of changed configuration items. Then, a tree structure construction algorithm is used to construct a hierarchical tree structure representing the dependencies between configuration items, based on these changed configuration item nodes and the dependency edges in the directed graph. Nodes with no dependencies or the fewest dependencies are designated as top-level nodes, and dependent nodes are designated as lower-level nodes. For example, with E as the top-level node, F as the middle-level node connecting E, G as the bottom-level node connecting F, and H as another top-level node with no dependencies, a hierarchical tree structure with two branches is formed. For example, if A depends on B and B depends on C, C is designated as the bottom-level node, B as the middle-level node pointing to C, and A as the top-level node pointing to B.

[0132] Next, in step S1053, a tree traversal algorithm is used to traverse the hierarchical tree structure constructed in step S1052 layer by layer, sequentially obtaining the change configuration items in each level, and extracting the keyword set from the semantic information of each change configuration item. For example, the keyword set for configuration item F is {fuel control, pressure regulation}, for G it is {fuel injection, flow control}, and for H it is {navigation and positioning, signal reception}. Then, a semantic similarity calculation algorithm is used to calculate the semantic association strength between configuration items in the same level based on the overlap or relevance of the keyword sets. For example, the keywords of F and G are both related to fuel, and the association strength is 0.8; the keywords of F and H are not related, and the strength is 0.2. Then, a clustering algorithm is used to group configuration items with semantic association strength higher than a preset threshold together. Finally, for each group, the common core words in its keyword set are extracted to determine the semantic theme of each group.

[0133] Then, in step S1054, for each group divided in step S1053, all changed configuration items within that group are obtained. Version comparison results for these changed configuration items are retrieved from the non-volatile memory crossbar switch array. These results include the difference positions between the versions of each configuration item, the old content before modification, and the new content after modification. For example, the version comparison result for configuration item I shows that the 4th position has an old content of "5" and a new content of "7"; the comparison result for configuration item J shows that the 6th position has an old content of "F" and a new content of "G". Then, a text generation algorithm is used to integrate the configuration item name, change position, old content, and new content of each changed configuration item into a text fragment describing it in natural language. For example, a text fragment is generated for configuration item I: "Configuration item I: The 4th data has been changed from '5' to '7'"; and for configuration item J: "Configuration item J: The 6th data has been changed from 'F' to 'G'". Finally, the generated text fragments are associated with the corresponding changed configuration items and stored to prepare for subsequent organizational difference reports.

[0134] Finally, step S1055 determines the hierarchical tree structure's presentation order, typically organized from top to bottom. For example, if the hierarchical tree has three levels—top, middle, and bottom—it's presented in the order of top → middle → bottom. Next, for each level, the groups within that level are sorted according to the semantic themes determined in step S1053. This can be based on the importance of the semantic themes or alphabetical order. For example, the middle level might have two groups: "Fuel System Related Changes" and "Navigation and Positioning Related Changes," sorted by importance with the former first and the latter last. Then, the level name of each level, such as "Top Level Change" or "Middle Level Change," is used as the report's first-level heading. The semantic theme of each group is used as a second-level heading, and the text snippets within that group are the specific content under the second-level headings, arranged sequentially. Finally, the organized content is formatted, with necessary separators and explanatory text added to create a configuration difference report with a clear hierarchical structure and semantic theme classification. For example, the report might begin with the top-level change heading, followed by the corresponding groups and text snippets, then the middle-level change headings and their corresponding content, and finally the bottom-level change content.

[0135] In practical applications, during the configuration database management of the A-series flight simulator, when executing step S105, the synchronized configuration data is first compared with the historical data stored in the array to identify "avionics system parameters," "display system parameters," and "communication system parameters" as the set of changed configuration items. Then, based on the relationship that "avionics system parameters depend on display system parameters and communication system parameters" in the directed graph of topological relationships, a hierarchical tree is constructed with "avionics system parameters" as the top layer and the other two as the middle layers. When traversing the tree structure, since the semantic keywords of "display system parameters" and "communication system parameters" both contain "data transmission," they are grouped together due to their high association strength, with the semantic theme of "data transmission related parameter changes." Next, a change text fragment is generated for each configuration item based on the version comparison results, such as "the 8th position of the avionics system parameter has been changed from '20' to '22'." Finally, the text fragments are organized according to the hierarchy and semantic theme to generate a hierarchical configuration difference report with the top layer being avionics system changes and the middle layer being data transmission related changes.

[0136] The S105 solution described above uses structured difference synthesis technology to organize and analyze configuration changes according to hierarchical relationships and semantic themes. The generated configuration difference report is clear in hierarchy and semantics, allowing users to intuitively grasp the hierarchical relationships and functional classifications of the changes. This facilitates a quick understanding of the overall configuration changes and provides a convenient and easy-to-understand reference for the review, traceability, and maintenance of flight simulator configurations.

[0137] The following is a complete example for steps 101-105, such as Figure 3As shown, in the A-series flight simulator multi-site configuration database management project, firstly, attribute tables for 20 configuration items, including avionics systems, engine control, and navigation systems, are extracted from the configuration database system registry. Based on the connection guidance information in the attribute tables, the physical connections and logical references between each configuration item are parsed, and a directed graph with configuration items as nodes and relationships as edges is constructed as topological relationship data. At the same time, a set of keywords is extracted from the description text and annotation fields of each configuration item to form semantic information. For example, the keywords for the engine control configuration item are "thrust adjustment" and "fuel control". Finally, operation records from the past month are extracted from the transaction log and sorted by timestamp to form a version operation history.

[0138] Next, based on the topology data, the number of in-degree connections for the avionics system configuration item was calculated to be 4 and the number of out-degree connections to be 5. The frequency of its keywords was counted as 18, and combined with the version operation history, it was found that it was modified 7 times. The change weight was generated by merging the preset weights of 0.2, 0.2, 0.3, and 0.3 to 4×0.2+5×0.2+18×0.3+7×0.3=9.3. Since the preset threshold is 6, it was identified as a key configuration item. Then, starting from the avionics system configuration item, the directed graph was traversed to determine the six configuration items, including the display system and communication system, that were within its scope of influence.

[0139] Subsequently, the V1-V4 versions of the engine control configuration item are stored in the continuous storage area of ​​the non-volatile memory cross switch array in the order of identification. An independent cross switch control line is assigned to the configuration item, and the connection path is reconstructed by adjusting the control line level. When it is necessary to compare the V2 and V4 versions, the corresponding control line levels are controlled in a coordinated manner to route the data of the two versions to a parallel comparator. The comparator compares bit by bit and generates bitmap information, marking the difference between the 8th and 15th bits, thus forming a parallel comparison result.

[0140] Subsequently, based on the configuration item change model and the impact range of key configuration items, 12 change operations on configuration items such as avionics system and display system at each station were identified as a set of potential conflicting operations. Combined with the parallel comparison results, it was found that both Station 1 and Station 2 modified the 8th data of the avionics system configuration item, changing it to "20" and "25" respectively. Using operation conversion technology, the operation of Station 1 was determined to be earlier according to the timestamp, and the conflicting operations were converted into an exchangeable sequence through the state transition function. When the sequence was executed, a conflict was detected. Combining the keyword "associated navigation data transmission rate" in the semantic information of the avionics system, the conflict was resolved, and the synchronization value was determined to be "22", generating the synchronized configuration data.

[0141] Finally, by comparing the synchronized data with the array's historical data, the avionics system, display system, and communication system were identified as sets of changed configuration items. Based on the topology, a hierarchical tree was constructed with the avionics system at the top and the other two at the middle levels. When traversing the tree structure, the display system and communication system were grouped together because their keywords both contained "data transmission," with the semantic theme "data transmission related parameter changes." Text fragments were generated for each configuration item based on the version comparison results, such as "the 8th parameter of the avionics system was changed from '20' to '22'." The text fragments were organized according to the hierarchy and semantic theme to synthesize a hierarchical configuration difference report.

[0142] Figure 4 This is a schematic diagram illustrating a specific implementation of a flight simulator configuration database version management and difference analysis system provided in this application embodiment. (Refer to...) Figure 4 The system may include:

[0143] The data acquisition module 41 is used to acquire topological relationship data between configuration items, semantic information of configuration items, and version operation history in the flight simulator configuration database.

[0144] The identification module 42 is used to establish a configuration item change model based on the topological relationship data, configuration item semantic information and version operation history through dependency relationship analysis, so as to identify key configuration items and the scope of influence of the key configuration items;

[0145] Processing module 43 is used to store configuration data containing multiple configuration item versions in a non-volatile memory cross switch array to achieve high-speed parallel access to multiple version configuration data, and to support parallel comparison processing of the multiple configuration item versions by reconstructing the connection state of the cross switch network in the non-volatile memory cross switch array to obtain parallel comparison results.

[0146] Synchronization module 44 is used to convert configuration change operations generated by different locations and stations into an exchangeable operation sequence based on the configuration item change model, the impact range of the key configuration items and the parallel comparison results, and to complete version synchronization and conflict detection and resolution between multiple stations by executing the operation sequence, and generate synchronized configuration data.

[0147] The generation module 45 is used to generate a hierarchical configuration difference report by using structured difference synthesis technology to hierarchically organize and semantically analyze the configuration change content based on the synchronized configuration data and the storage information in the non-volatile memory cross switch array, combined with the topological relationship data between the configuration items and the semantic information of the configuration items.

[0148] The flight simulator configuration database version management and difference analysis system of this application embodiment is used to implement the aforementioned flight simulator configuration database version management and difference analysis method. Therefore, the specific implementation of the flight simulator configuration database version management and difference analysis system can be found in the embodiment section of the flight simulator configuration database version management and difference analysis method above. The specific implementation can be referred to the description of the corresponding embodiment, and will not be repeated here.

[0149] This application also provides an electronic device, comprising: a memory for storing a computer program; and a processor for executing the computer program to implement the steps of the flight simulator configuration database version management and difference analysis method described above.

[0150] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of any of the above-described flight simulator configuration database version management and difference analysis methods.

[0151] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as USB flash drives, read-only memory, random access memory, portable hard drives, magnetic disks, or optical disks.

[0152] Embodiments of the present invention also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the flight simulator configuration database version management and difference analysis method embodiments described above.

[0153] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0154] The foregoing has provided a detailed description of a method, system, device, and storage medium for version management and difference analysis of a flight simulator configuration database, as provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and its core ideas. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of this application.

Claims

1. A method for managing and analyzing differences of a flight simulator configuration database version, characterized in that, The method comprises the following steps: Collecting topology relationship data between configuration items in a flight simulator configuration database, configuration item semantic information, and version operation history; Based on the topology relationship data, the configuration item semantic information, and the version operation history, a configuration item change model is established through dependency relationship analysis to identify key configuration items and the influence range of the key configuration items; Configuration data containing multiple configuration item versions are stored in a non-volatile memory crossbar array to realize high-speed parallel access of the multiple version configuration data, and parallel comparison processing of the multiple configuration item versions is supported by reconfiguring the connection state of the crossbar network in the non-volatile memory crossbar array to obtain a parallel comparison result; Based on the configuration item change model, the influence range of the key configuration items, and the parallel comparison result, an operation conversion technology is applied to convert configuration change operations generated by different location sites into an operation sequence with commutativity, version synchronization between multiple sites and multi-site conflict detection and analysis are completed by executing the operation sequence, and synchronized configuration data are generated; Based on the synchronized configuration data and the storage information in the non-volatile memory crossbar array, combined with the topology relationship data between the configuration items and the configuration item semantic information, a structured difference synthesis technology is used to hierarchically organize and semantically analyze the configuration change content to generate a configuration difference report with a hierarchical structure.

2. The flight simulator configuration database version management and difference analysis method according to claim 1, wherein, The operation conversion technology is applied to convert configuration change operations generated by different location sites into an operation sequence with commutativity, version synchronization between multiple sites and multi-site conflict detection and analysis are completed by executing the operation sequence, and synchronized configuration data are generated based on the configuration item change model, the influence range of the key configuration items, and the parallel comparison result, which comprises the following steps: Based on the change weight in the configuration item change model and the influence range of the key configuration items, a set of potential conflict operations in the configuration change operations received from each site is determined; Based on the bitmap information in the parallel comparison result, the data modification content of the potential conflict operations set to the same configuration item is analyzed; An operation conversion technology is applied to adjust the execution order of the configuration change operations according to the timestamp of the configuration change operation and the data modification content, and an operation sequence with consistency and commutativity on all sites is generated; According to the operation sequence, each configuration change operation is executed to complete multi-site version synchronization, and conflict detection is performed on change operations for the same configuration item during the execution process, and conflicts are resolved based on a set of key words in the configuration item semantic information to generate synchronized configuration data.

3. The method of claim 2, wherein the database version management and difference analysis method of the flight simulator configuration database is characterized by, The operation conversion technology is applied to adjust the execution order of the configuration change operations according to the timestamp of the configuration change operation and the data modification content, and an operation sequence with consistency and commutativity on all sites is generated, which comprises the following steps: A conflict resolution rule of the operation conversion technology is applied to establish a partial order relationship of operation execution according to the timestamp of the configuration change operation; Based on the data modification content, concurrent modification operations to the same configuration item parameter are identified; According to the partial order relation and semantic correlation of concurrent modification operations, the execution context of the configuration change operation is reconstructed; By operating the state transition function of the algorithm, the operation with execution conflict is converted into an exchangeable operation unit; According to the converted exchangeable operation unit, the operation sequence is reorganized to generate an operation sequence with consistency and exchangeability on all sites.

4. The flight simulator configuration database version management and difference analysis method of claim 1, wherein, The configuration data containing multiple versions of configuration items is stored in the non-volatile memory crossbar array to realize high-speed parallel access of multi-version configuration data, and the connection state of the crossbar network in the non-volatile memory crossbar array is reconstructed to support parallel comparison processing of the multiple versions of configuration items to obtain a parallel comparison result, including: Multiple version data of each configuration item are stored in a continuous storage area of the non-volatile memory crossbar array in order of version identification; An independent crossbar control line is allocated to each configuration item, and the connection path of each switch unit in the crossbar network is reconstructed by changing the level state of the crossbar control line; When version comparison is performed, different versions of configuration item data are simultaneously routed to multiple parallel comparators by cooperatively controlling the level state combination of multiple crossbar control lines. The parallel comparator simultaneously compares the content of multiple versions of configuration item data, generates and outputs a bitmap information identifying data differences as a parallel comparison result, and the parallel comparison result contains specific position and content information of data differences between versions.

5. The flight simulator configuration database version management and difference analysis method of claim 1, wherein, Based on the synchronized configuration data and the storage information in the non-volatile memory crossbar array, combined with the topology relationship data and configuration item semantic information between the configuration items, a structured difference synthesis technology is used to hierarchically organize and semantically analyze the configuration change content, and a configuration difference report with a hierarchical structure is generated, including: Identify the configuration items with content changes from the synchronized configuration data to form a set of changed configuration items; According to the directed graph structure in the topology relationship data, the configuration items in the set of changed configuration items are used as nodes to build a hierarchical tree structure representing the dependency relationship between configuration items; Traverse the hierarchical tree structure, group the changed configuration items at the same level according to the semantic association strength provided by the keyword set in the configuration item semantic information, and determine the semantic theme of each group; For each changed configuration item in a group, combine the version comparison result stored in the non-volatile memory crossbar array to generate a text segment describing the specific change content of the changed configuration item; According to the hierarchical relationship of the hierarchical tree structure and the semantic theme of the group, the text segments are organized to synthesize a configuration difference report with a hierarchical structure.

6. The flight simulator configuration database version management and difference analysis method of claim 1, wherein, Based on the topology relationship data, configuration item semantic information and version operation history, a configuration item change model is established through dependency relationship analysis to identify key configuration items and the influence range of the key configuration items, including: Based on the directed graph structure in the topology relationship data, the in-degree connection number and out-degree connection number of each configuration item in the directed graph structure are calculated; Based on the keyword set in the configuration item semantic information, the keyword appearance frequency of each configuration item is counted; Based on the operation records in the version operation history, the modification frequency of each configuration item is counted; The in-degree connection number, the out-degree connection number, the keyword appearance frequency and the modification frequency are fused to generate the change weight of each configuration item; The configuration item whose change weight exceeds a preset threshold is identified as a key configuration item; The key configuration item is taken as a starting node, and all configuration items reached by traversing along the edges of the directed graph structure are determined as the influence range of the key configuration item.

7. The flight simulator configuration database version management and difference analysis method of claim 1, wherein, The topology relationship data among configuration items, the configuration item semantic information and the version operation history in the flight simulator configuration database are collected, including: The attribute table of each configuration item is extracted from the system registry of the flight simulator configuration database, the physical connection and the logical reference relationship among the configuration items are parsed according to the connection guide information in the attribute table, a directed graph structure taking the configuration item as a node and taking the physical connection and the logical reference relationship as an edge is constructed, and the topology relationship data among the configuration items is formed; The keyword set used to represent the function and the attribute of the configuration item is extracted from the preset description text field and the annotation field of the configuration item in the flight simulator configuration database, and the configuration item semantic information is formed; All operation records on the configuration item are extracted from the transaction log of the flight simulator configuration database, the operation records include the operation type, the target configuration item identifier, the operation timestamp and the operation content details, and the operation records are organized in the order of the operation timestamp, and the version operation history is formed.

8. A flight simulator configuration database version management and difference analysis system, characterized by, It includes: The collection module is used to collect the topology relationship data among configuration items, the configuration item semantic information and the version operation history in the flight simulator configuration database; The identification module is used to identify the key configuration item and the influence range of the key configuration item by establishing a configuration item change model based on the topology relationship data, the configuration item semantic information and the version operation history through dependency analysis; The processing module is used to store the configuration data containing multiple configuration item versions in the non-volatile memory crossbar array, to realize high-speed parallel access of the multiple version configuration data, and to support parallel comparison processing of the multiple configuration item versions by reconstructing the connection state of the crossbar network in the non-volatile memory crossbar array, to obtain a parallel comparison result; The synchronization module is used to convert the configuration change operations generated by different location sites into an operation sequence with interchangeability based on the configuration item change model, the influence range of the key configuration item and the parallel comparison result, to complete version synchronization among multiple sites and multi-site conflict detection and analysis by executing the operation sequence, and to generate synchronized configuration data; The generation module is used to generate a configuration difference report with a hierarchical structure based on the synchronized configuration data and the storage information in the non-volatile memory crossbar array, in combination with the topology relationship data among the configuration items and the configuration item semantic information, by using a structured difference synthesis technology to hierarchically organize and semantically analyze the configuration change content.

9. An electronic device, comprising: It includes: a memory for storing a computer program; a processor for implementing the steps of the flight simulator configuration database version management and difference analysis method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that, The computer program is stored in the computer readable storage medium and can be executed by the processor to implement the flight simulator configuration database version management and difference analysis method according to any one of claims 1 to 7.

Images