An aviation flight training heterogeneous data synchronization method, system and device

Abstract

The application discloses an aviation flight training heterogeneous data synchronization method, system and equipment, and belongs to the technical field of aviation flight training data processing. The method comprises the following steps: performing metadata mapping on a heterogeneous training database, generating a unified training data model and a business unique identifier; constructing a constraint index based on the business unique identifier in a target database, storing resource identifiers, personnel identifiers and time intervals of unarchived tasks; converting training business change data into to-be-synchronized records carrying event serial numbers, judging time conflicts by using the constraint index, and performing time sequence verification based on the event serial numbers when there is no conflict; after the verification, distinguishing target record locking states, directly writing the to-be-synchronized records and updating the constraint index in a non-locking state, generating a correction record and writing the correction record into an event chain in a locking state; and recording synchronization information into the event chain after synchronization is completed. The application pre-intercepts training resource and personnel time occupation conflicts, and guarantees that locked audit records are complete and traceable.

Description

Technical Field

[0001] This invention belongs to the field of aviation flight training data processing technology, and specifically discloses a method, system and equipment for synchronizing heterogeneous aviation flight training data. Background Technology

[0002] In civil and general aviation flight training systems, training institutions typically deploy multiple business systems simultaneously to support end-to-end training management. Typical systems include a central training management system, a simulator operation control system, an aircraft operation management system, a student qualification management system, an instructor scheduling system, and a training quality auditing system. These systems are often built by different vendors, resulting in significant differences in database types, table structure design, primary key naming rules, and time precision standards, creating multiple heterogeneous data silos. To achieve comprehensive training data sharing and business collaboration, bidirectional data synchronization between these heterogeneous databases is necessary.

[0003] Existing heterogeneous database synchronization technologies are mainly divided into three categories, and all of them have significant shortcomings in aviation flight training scenarios: The first type is a scheduled batch synchronization solution based on ETL tools. This solution extracts data from the source database at fixed time intervals, cleans and transforms it, and then imports it into the target database. It is suitable for reporting statistics and offline analysis scenarios. However, in aviation flight training, there are often real-time business scenarios such as temporary class rescheduling, simulator malfunction rescheduling, temporary instructor replacement, and changes in student qualification status. The delay of scheduled synchronization cannot meet the second-level consistency requirements, which can easily lead to scheduling conflicts and information asymmetry.

[0004] The second type is a general CDC incremental synchronization solution based on log parsing. This solution captures incremental data and synchronizes it to the target database in real time by reading change records such as redo logs and binary logs, significantly improving synchronization real-time performance. However, general CDC tools only focus on CRUD operations at the data table level and are unaware of the business rules of aviation flight training. They cannot identify business constraints such as mutual exclusion of training resources, qualification matching, and audit locking, and may write data that does not conform to the business rules to the target database.

[0005] The third type is the general two-way synchronization scheme. This type of scheme typically resolves loopback and overwrite conflicts through data source identifiers and timestamps, defaulting to the rule of "latest timestamp overwrites old data." However, in flight training operations, different categories of data correspond to different authoritative sources, and uniformly overwriting by timestamp can lead to authoritative data being tampered with by non-authoritative sources. Furthermore, signed, reviewed, and regulated training records are audit-immutable; ordinary overwriting operations would disrupt the audit chain, creating compliance risks.

[0006] In addition, existing synchronization technologies have the following specific problems in flight training scenarios: First, they cannot identify the mutual exclusion constraints of training resources, only verify the uniqueness of primary keys, and do not verify the overlapping of resources such as simulators, instructors, and trainees within the same time window, which can easily lead to business errors such as double scheduling; Second, they cannot protect the audit compliance status of training records, and locked audit records can be easily overwritten by old version data, breaking the traceability chain; Third, the task backlog merging mechanism is not suitable for training business scenarios, and key status flow records are easily lost, resulting in a lack of basis for regulatory traceability.

[0007] Therefore, there is an urgent need for a heterogeneous data synchronization solution for aviation flight training operations, which embeds training business constraints into the pre-verification process of synchronous writing, while ensuring data consistency, business compliance and audit traceability. Summary of the Invention

[0008] To overcome the above-mentioned shortcomings, this invention proposes a method, system, and device for synchronizing heterogeneous data in aviation flight training. By constructing a constraint index, it achieves pre-verification of resource time conflicts, and combines event sequence number time-series verification to prevent old data from overwriting new states. For locked audit records, it uses an append correction method to ensure the integrity of the audit link, thereby achieving business compliance, data consistency, and audit integrity in the bidirectional synchronization process of heterogeneous training databases.

[0009] To achieve the above-mentioned objectives, the present invention adopts the following technical solution: In a first aspect, the present invention provides a method for synchronizing heterogeneous data in aviation flight training, the method comprising: Metadata mapping is performed on training business data in heterogeneous training databases to form a unified training data model, and a corresponding unique business identifier is assigned to the same training business object. A constraint index is constructed in the target training database based on the unique business identifier. The constraint index records the resource identifier, personnel identifier, and time interval of the unarchived task. According to the unified training data model, the pre-acquired training business change data is converted into a record to be synchronized carrying an event sequence number. Before writing the record to be synchronized, use the constraint index to retrieve unarchived task records that have resource usage conflicts and / or personnel usage conflicts with the record to be synchronized and have different business unique identifiers; If the unarchived task record is found, it is determined that the record to be synchronized has a time conflict with the existing task in the target training database, and the record to be synchronized is prevented from being written to the target training database; if the unarchived task record is not found, the target corresponding record with the same business unique identifier as the record to be synchronized is obtained from the target training database, and the time sequence verification of the record to be synchronized is performed based on the event sequence number of the record to be synchronized. When the timing verification passes, it is determined whether the record corresponding to the target is in a locked state; If the target corresponding record is not locked, the record to be synchronized is written into the target training database, and the synchronization status information corresponding to the record to be synchronized in the target training database is updated; if the target corresponding record is locked, overwriting the target corresponding record is prohibited, a correction record associated with the target corresponding record is generated, and the correction record is written into the event chain of the target training database.

[0010] Optionally, the step of mapping training business data in heterogeneous training databases to form a unified training data model includes: Extract the field names, data types, and relationships of the training business data from each of the heterogeneous training databases, and establish a field mapping table; Based on the field mapping table, heterogeneous training business data are unified into a unified training data model with a consistent data structure.

[0011] Optionally, the unique business identifier is generated based on at least two of the training date, training resource identifier, instructor number, and student number, and is used to associate the same training business object across different training databases.

[0012] Optionally, retrieving unarchived task records that have resource usage conflicts and / or personnel usage conflicts with the record to be synchronized, and whose business unique identifiers are different, using the constraint index includes: Using the resource identifier and / or personnel identifier in the record to be synchronized as the retrieval dimension, retrieve unarchived task records in the constraint index that have the same resource identifier and / or the same personnel identifier as the record to be synchronized, have overlapping time intervals, and correspond to different business unique identifiers; If a matching record is found, the matching record is identified as an unarchived task record that has resource usage conflicts and / or personnel usage conflicts with the record to be synchronized, and a conflict record is generated to terminate the synchronization of the record to be synchronized.

[0013] Optionally, the timing verification of the record to be synchronized based on the event sequence number of the record to be synchronized includes: Obtain the event sequence number of an existing record in the target training database that has the same unique business identifier as the record to be synchronized; If the existing record does not exist in the target training database, the time series verification is deemed to have passed. If the existing record exists, the timing verification is considered successful if the event sequence number of the record to be synchronized is greater than the event sequence number of the existing record.

[0014] Optionally, the locked status includes: signed status, reviewed status, archived status, or reported status.

[0015] Optionally, the event chain of generating a corrected record associated with the record corresponding to the target and writing the corrected record into the target training database includes: A correction record is generated based on the record to be synchronized, and the correction record is associated with the business unique identifier of the target corresponding record; The correction record includes the correction reason, operation time, operation type, and the event number to be synchronized. The event chain in which the correction record is written into the target training database according to the event sequence number.

[0016] Optionally, the step of writing the record to be synchronized into the target training database and updating the synchronization status information corresponding to the record to be synchronized in the target training database includes: After writing the record to be synchronized into the target training database, update the resource identifier, personnel identifier, or time interval of the task corresponding to the record to be synchronized in the constraint index; The event number, operation type, synchronization time, and synchronization result of this synchronization are written into the event chain of the target training database.

[0017] Secondly, the present invention provides a heterogeneous data synchronization system for aviation flight training, the system comprising: The metadata mapping module is used to perform metadata mapping on training business data in heterogeneous training databases, form a unified training data model, and assign a corresponding unique business identifier to the same training business object. The constraint index construction module is used to construct a constraint index in the target training database based on the unique business identifier. The constraint index records the resource identifier, personnel identifier, and time interval of the unarchived task. The incremental conversion module is used to convert the pre-acquired training business change data into a record to be synchronized carrying an event sequence number according to the unified training data model. Before writing the record to be synchronized, use the constraint index to retrieve unarchived task records that have resource usage conflicts and / or personnel usage conflicts with the record to be synchronized and have different business unique identifiers; If the unarchived task record is found, it is determined that the record to be synchronized has a time conflict with the existing task in the target training database, and the record to be synchronized is prevented from being written to the target training database; if the unarchived task record is not found, the target corresponding record with the same business unique identifier as the record to be synchronized is obtained from the target training database, and the time sequence verification of the record to be synchronized is performed based on the event sequence number of the record to be synchronized. The execution module is used to determine whether the record corresponding to the target is in a locked state when the timing verification passes. The synchronization update module is used to write the record to be synchronized into the target training database and update the synchronization status information corresponding to the record to be synchronized in the target training database if the record corresponding to the target is not locked; if the record corresponding to the target is locked, it is prohibited to overwrite the record corresponding to the target, a correction record associated with the record corresponding to the target is generated, and the correction record is written into the event chain of the target training database.

[0018] Thirdly, the present invention provides an electronic device, the electronic device comprising: At least one processor; and a memory communicatively connected to said at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor to enable the at least one processor to perform the method described in any one of the first aspects.

[0019] Compared with the closest existing technology, the present invention has the following advantages: This invention provides a method, system, and device for synchronizing heterogeneous data in aviation flight training. It eliminates heterogeneous differences between multiple databases through metadata mapping, generating a globally unified, unique business identifier. A dedicated constraint index is then built in the target database to pre-screen for conflicts related to training resources and personnel time occupancy. Business changes are standardized into records to be synchronized with event numbers, and time-series verification is performed based on these event numbers to prevent reverse overwriting of old data. Locked / unlocked records are distinguished, and direct write and event chain append correction operations are performed accordingly. The constraint index is updated synchronously, and the synchronization audit trail is fully retained. This solution embeds aviation training business constraints into the entire synchronization process, proactively intercepting scheduling conflicts while meeting the regulatory requirements of immutability and full-chain traceability for civil aviation training records. The real-time synchronization adapts to business scenarios such as temporary class rescheduling and equipment failure rebooking. It requires no modification to existing training business systems and has strong deployment versatility. Attached Figure Description

[0020] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the accompanying drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. In all the drawings, similar elements or parts are generally identified by similar reference numerals. In the drawings, the elements or parts are not necessarily drawn to scale.

[0021] Figure 1 This is a schematic diagram of the overall execution flow of the heterogeneous data synchronization method for aviation flight training provided in an embodiment of the present invention; Figure 2 This is a schematic diagram of the constraint index construction process provided in an embodiment of the present invention; Figure 3 This is a schematic diagram illustrating the step-by-step execution of time conflict verification and timing verification provided in an embodiment of the present invention; Figure 4 This is a schematic diagram showing the connection of the various modules of the heterogeneous data system for aviation flight training provided in an embodiment of the present invention; Figure 5 This is a block diagram of the internal structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0022] The embodiments of the technical solution of the present invention will now be described in detail with reference to the accompanying drawings. These embodiments are only used to more clearly illustrate the technical solution of the present invention and are therefore merely examples, and should not be construed as limiting the scope of protection of the present invention.

[0023] It should be noted that, unless otherwise stated, the technical or scientific terms used in this application should have the ordinary meaning as understood by those skilled in the art to which this invention pertains.

[0024] This invention provides a method and system for synchronizing heterogeneous data in aviation flight training. The embodiments of this invention are described below with reference to the accompanying drawings.

[0025] The embodiments of this invention relate to technical fields such as heterogeneous database processing, data index construction, time sequence verification, event chain auditing, and compliance management of civil aviation flight training data.

[0026] Heterogeneous databases refer to multiple training business databases with inconsistent vendors, table structures, and field specifications, including simulator databases, qualification databases, training management databases, and audit and supervision databases. Constraint Index: A dedicated retrieval index within the target database, storing resources, personnel, and time intervals for unarchived training tasks, used for quickly screening time-occupancy conflicts; Event Sequence Number: A globally incrementing number under a single training business object, used to distinguish the order in which data is generated and to achieve time sequence verification; Locked status: Training records that have been signed, reviewed, archived, and submitted for supervision cannot be directly modified; Event Chain: An audit data table that stores original records and correction records in an orderly manner according to event sequence number, and completely retains all modification traces.

[0027] The following description, with reference to the accompanying drawings, illustrates a method and system for synchronizing heterogeneous data in aviation flight training according to embodiments of the present invention. The implementing entity of the method is an aviation flight training heterogeneous data synchronization system, which can be implemented in software and / or hardware and can be configured in electronic devices such as servers and local workstations. The present invention uses a civil aviation dual heterogeneous training database synchronization scenario as an example for illustration.

[0028] Example 1: Overall Flow of Heterogeneous Data Synchronization Method for Aviation Flight Training Figure 1 Figure 1 is a schematic diagram of the overall process of a heterogeneous data synchronization method for aviation flight training according to an embodiment of the present invention. The method includes: S101: Perform metadata mapping on training business data in heterogeneous training databases to form a unified training data model, and assign a corresponding unique business identifier to the same training business object.

[0029] The heterogeneous training database includes at least two independent training business databases, such as the simulator operation source database and the central training target database; metadata mapping is used to smooth out differences in field names, data types, time precision, and encoding formats among the databases; the business unique identifier is a globally unique string used to associate the same set of flight training tasks across databases.

[0030] Optionally, the step of mapping training business data in heterogeneous training databases to form a unified training data model specifically includes: Step 1: Extract the field names, data types, and relationships of the training business data from each of the heterogeneous training databases, and establish a field mapping table; Step 2: Based on the field mapping table, unify the heterogeneous training business data into the unified training data model with a consistent data structure.

[0031] In this embodiment of the invention, the synchronization system automatically traverses all data tables of the accessed heterogeneous databases, extracts core fields such as training resources, instructors, students, training time periods, and review status, and establishes a global field mapping table. Based on the mapping table, it completes field alignment, unit unification, and time standardization, generating a unified training data model with a completely consistent structure. For the same training task, it combines the training date, simulator number, and student number to perform a hash operation to generate a unique business identifier, ensuring that the identifier for the same task is completely consistent across multiple databases.

[0032] S102: Construct a constraint index in the target training database based on the unique business identifier, wherein the constraint index records the resource identifier, personnel identifier, and time interval of the unarchived task.

[0033] Among them, the target training database is a synchronous writing end database; the resource identifier refers to the unique number of the simulator, training aircraft, and training site; the personnel identifier includes the instructor number and the trainee number; the time interval is composed of the planned start time and the planned end time; and the unarchived tasks refer to valid training tasks that have not been reviewed or submitted for supervision.

[0034] Optionally, constructing a constraint index in the target training database based on the business unique identifier specifically includes: Step 1: Traverse the training tasks in the target training database; Step 2: Using the unique business identifier as the primary key, store the resource identifier, personnel identifier, planned start time, and planned end time of the corresponding training task into the constraint index; Step 3: In the constraint index, establish a first composite index for the resource identifier and the time interval, and a second composite index for the personnel identifier and the time interval.

[0035] refer to Figure 2 During the initialization phase of the synchronization system, all training tasks in the target library are fully traversed, and unarchived entries are filtered and written into the constraint index. The primary key of the index is a unique identifier for the business. At the same time, two types of composite indexes are built to quickly retrieve time-overlapping tasks of the same resource and the same person, which greatly improves the efficiency of conflict retrieval. During the synchronization process, the constraint index is updated in real time after each data write or correction append.

[0036] S103: Based on the unified training data model, the pre-acquired training business change data is converted into a record to be synchronized carrying an event sequence number; using the constraint index, it is determined whether there is a time conflict between the record to be synchronized and the existing task in the target training database; if there is no time conflict, a time sequence verification is performed between the record to be synchronized and the corresponding target record based on the event sequence number.

[0037] Among them, training business change data are incremental data captured from the source database, such as class rescheduling, teacher change, duration adjustment, qualification update, etc.; the event sequence number is an auto-incrementing number under a unique identifier for a single business, and a new sequence number is assigned for each change; time conflict refers to the same resource / personnel being assigned multiple sets of training tasks during overlapping time periods.

[0038] Optionally, determining whether there is a time conflict between the record to be synchronized and an existing task in the target training database using the constraint index specifically includes: Step 1: Using the resource identifier and personnel identifier in the record to be synchronized as the search dimensions, retrieve unarchived task records in the constraint index that overlap with the time interval of the record to be synchronized and correspond to different unique business identifiers; Step 2: If a matching record is found, a time conflict is determined, a conflict record is generated, and the synchronization of the record to be synchronized is terminated.

[0039] Optionally, the step of performing time-series verification between the record to be synchronized and the corresponding target record based on the event sequence number specifically includes: Step 1: Obtain the event sequence number of an existing record in the target training database that has the same unique business identifier as the record to be synchronized; Step 2: When the sequence number of the event to be synchronized is greater than the sequence number of the existing event, the timing verification is deemed successful.

[0040] refer to Figure 3 After the synchronization system captures incremental changes in the source database, it encapsulates them in a standardized manner according to the unified training data model, assigns incremental event numbers to generate records to be synchronized, and first searches for time overlap using a two-dimensional constraint index. If there is a conflict, the synchronization is terminated directly and the conflict log is retained. If there is no conflict, the system compares the maximum event number of the same business unique identifier in the target database. Only the new number is allowed to enter the next process, and old changes that are lagging behind under weak network conditions are blocked from overwriting the latest training data.

[0041] S104: When the timing verification passes, if the record corresponding to the target is not in a locked state, the record to be synchronized is written into the target training database.

[0042] Optionally, the lock status of the record corresponding to the target includes: signed status, reviewed status, archived status, or reported to the regulator.

[0043] S105: If the record corresponding to the target is in a locked state, generate a correction record and write it to the event chain of the target training database; The event chain for generating the correction record and writing it to the target training database specifically includes: Step 1: Assign a new event number to the correction record and associate the correction record with the unique business identifier of the original task record; Step 2: Append the correction records to the event chain in sequence according to the event number, and record the reason for the correction and the operation time.

[0044] In this embodiment of the invention, after the timing verification is passed, the target record status field is read: draft and pending review are in an unlocked state, and are directly overwritten into the record to be synchronized. After successful writing, the resource identifier, personnel identifier, or time interval of the corresponding task in the constraint index is updated. At the same time, the event sequence number, operation type, synchronization time, and synchronization result of this synchronization are written into the event chain. Records that have been signed by instructors, quality reviewed, archived, or submitted for supervision are in a locked state. Overwriting the original data is prohibited. An independent correction record is generated, bound to the unique business identifier of the original task, and the reason for modification and operation time are filled in. The record is appended to the end of the event chain according to the sequence number. The original training record is permanently retained, and the resource identifier, personnel identifier, and time interval corresponding to the original task record in the constraint index remain unchanged.

[0045] After synchronization is complete, two scenarios are distinguished for subsequent processing: For scenarios requiring further updates, the resource, personnel, and time period fields are directly written into the scenario synchronization refresh constraint index, and the synchronization information is recorded in the event chain; for scenarios requiring further correction, only the event chain audit log is updated, without altering the original task constraint index. All synchronization actions and execution results are fully stored in the event chain, allowing for traceability and verification by civil aviation regulators.

[0046] In this embodiment, the heterogeneous data structure is first unified through metadata mapping and a unique business identifier is generated. The conflict of training resources and personnel time occupation is intercepted in advance by relying on the dedicated constraint index. The timing verification is completed by relying on the event sequence number to prevent old data from being overwritten. For audit lock records, the event chain is used to add correction to retain all modification traces. The constraint index and audit event chain are maintained simultaneously to take into account both real-time synchronization and civil aviation compliance requirements.

[0047] Example 2: Based on the same technical concept, Example 2 of this invention also provides a heterogeneous data synchronization system for aviation flight training, such as... Figure 4 As shown, the system includes: Metadata mapping module 210 is used to perform metadata mapping on training business data in heterogeneous training databases to form a unified training data model and assign a corresponding unique business identifier to the same training business object. The constraint index construction module 220 is used to construct a constraint index in the target training database based on the business unique identifier. The constraint index records the resource identifier, personnel identifier, and time interval of the unarchived task. The incremental conversion module 230 is used to convert the pre-acquired training business change data into a record to be synchronized carrying an event sequence number according to the unified training data model; use the constraint index to determine whether there is a time conflict between the record to be synchronized and an existing task in the target training database; if there is no time conflict, then perform a time sequence verification between the record to be synchronized and the corresponding target record based on the event sequence number. The write execution module 240 is used to write the record to be synchronized into the target training database if the target corresponding record is not in a locked state when the timing verification passes. The synchronous update module 250 is used to generate a corrected record and write it to the target training database if the record corresponding to the target is in a locked state.

[0048] In some embodiments, the metadata mapping module 210 is specifically used for: Extract the field names, data types, and relationships of the training business data from each of the heterogeneous training databases, and establish a field mapping table; Based on the field mapping table, heterogeneous training business data are unified into a unified training data model with a consistent data structure.

[0049] In some embodiments, the constraint index construction module 220 is specifically used for: Iterate through the training tasks in the target training database; Using the unique business identifier as the primary key, the resource identifier, personnel identifier, planned start time, and planned end time of the corresponding training task are stored in the constraint index; In the constraint index, a first composite index is established for the resource identifier and the time interval, and a second composite index is established for the personnel identifier and the time interval.

[0050] In some embodiments, the incremental conversion module 230 is specifically used for: Using the resource identifier and personnel identifier in the record to be synchronized as the retrieval dimension, retrieve unarchived task records in the constraint index that overlap with the time interval of the record to be synchronized and correspond to different unique business identifiers; If a matching record is found, a time conflict is determined, a conflict record is generated, and the synchronization of the record to be synchronized is terminated. Obtain the event sequence number of an existing record in the target training database that has the same unique business identifier as the record to be synchronized; If the existing record does not exist in the target training database, the time series verification is deemed to have passed. If the existing record exists, the timing verification is considered successful if the event sequence number of the record to be synchronized is greater than the event sequence number of the existing record.

[0051] In some embodiments, the write execution module 240 is specifically used for: The lock status of the record corresponding to the target includes: signed status, reviewed status, archived status, or reported to the regulator. In some embodiments, the synchronization update module 250 is specifically used for: Assign a new event number to the correction record and associate the correction record with the unique business identifier of the original task record; The correction records are appended to the event chain in sequence according to the event number, and the reason for the correction and the operation time are recorded. The event number, reason for correction, operation time, and synchronization result of this correction are written into the event chain, and the resource identifier, personnel identifier, and time interval corresponding to the original task record in the constraint index remain unchanged.

[0052] It should be noted that the foregoing explanation of the method for synchronizing heterogeneous data in aviation flight training also applies to the synchronization system of this embodiment, and will not be repeated here.

[0053] The present invention will be further described in detail below with reference to specific embodiments, but the scope of protection of the present invention is not limited to the following embodiments.

[0054] Example 3: This Example 3 also provides an electronic device, which can be a terminal, and its internal structure diagram can be as follows. Figure 5 As shown. The electronic device includes a processor, memory, communication interface, display screen, and input device connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements the heterogeneous data synchronization method for aviation flight training as described in any one of steps S101 to S105. The display screen can be a liquid crystal display (LCD) or an e-ink display. The input device can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the device's casing, or an external keyboard, touchpad, or mouse.

[0055] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0056] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0057] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0058] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0059] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0060] The above are merely embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention are included within the scope of the claims of the present invention pending approval.

Claims

1. A method for synchronizing heterogeneous data in aviation flight training, characterized in that, The method includes: Metadata mapping is performed on training business data in heterogeneous training databases to form a unified training data model, and a corresponding unique business identifier is assigned to the same training business object. A constraint index is constructed in the target training database based on the unique business identifier. The constraint index records the resource identifier, personnel identifier, and time interval of the unarchived task. According to the unified training data model, the pre-acquired training business change data is converted into a record to be synchronized carrying an event sequence number. Before writing the record to be synchronized, use the constraint index to retrieve unarchived task records that have resource usage conflicts and / or personnel usage conflicts with the record to be synchronized and have different business unique identifiers; If the unarchived task record is found, it is determined that the record to be synchronized has a time conflict with the existing task in the target training database, and the record to be synchronized is prevented from being written to the target training database; if the unarchived task record is not found, the target corresponding record with the same business unique identifier as the record to be synchronized is obtained from the target training database, and the time sequence verification of the record to be synchronized is performed based on the event sequence number of the record to be synchronized. When the timing verification passes, it is determined whether the record corresponding to the target is in a locked state; If the target corresponding record is not locked, the record to be synchronized is written into the target training database, and the synchronization status information corresponding to the record to be synchronized in the target training database is updated; if the target corresponding record is locked, overwriting the target corresponding record is prohibited, a correction record associated with the target corresponding record is generated, and the correction record is written into the event chain of the target training database. The step of mapping training business data in heterogeneous training databases to form a unified training data model includes: Extract the field names, data types, and relationships of the training business data from each of the heterogeneous training databases, and establish a field mapping table; Based on the field mapping table, heterogeneous training business data are unified into a unified training data model with a consistent data structure.

2. The method according to claim 1, characterized in that, The unique business identifier is generated based on at least two of the following: training date, training resource identifier, instructor number, and student number, and is used to associate the same training business object across different training databases.

3. The method according to claim 1, characterized in that, The process of retrieving unarchived task records that have resource usage conflicts and / or personnel usage conflicts with the records to be synchronized, and whose business unique identifiers are different, using the constraint index includes: Using the resource identifier and / or personnel identifier in the record to be synchronized as the retrieval dimension, retrieve unarchived task records in the constraint index that have the same resource identifier and / or the same personnel identifier as the record to be synchronized, have overlapping time intervals, and correspond to different unique business identifiers; If a matching record is found, the matching record is identified as an unarchived task record that has resource usage conflicts and / or personnel usage conflicts with the record to be synchronized, and a conflict record is generated to terminate the synchronization of the record to be synchronized.

4. The method according to claim 1, characterized in that, The timing verification of the record to be synchronized based on the event sequence number includes: Obtain the event sequence number of an existing record in the target training database that has the same unique business identifier as the record to be synchronized; If the existing record does not exist in the target training database, the time series verification is deemed to have passed. If the existing record exists, the timing verification is considered successful if the event sequence number of the record to be synchronized is greater than the event sequence number of the existing record.

5. The method according to claim 1, characterized in that, The locked status includes: signed, reviewed, archived, or submitted to regulatory authorities.

6. The method according to claim 1, characterized in that, The event chain of generating a corrected record associated with the record corresponding to the target and writing the corrected record into the target training database includes: A correction record is generated based on the record to be synchronized, and the correction record is associated with the business unique identifier of the target corresponding record; The correction record includes the correction reason, operation time, operation type, and the event number to be synchronized. The event chain in which the correction record is written into the target training database according to the event sequence number.

7. The method according to claim 1, characterized in that, The step of writing the record to be synchronized into the target training database and updating the synchronization status information corresponding to the record to be synchronized in the target training database includes: After writing the record to be synchronized into the target training database, update the resource identifier, personnel identifier, or time interval of the task corresponding to the record to be synchronized in the constraint index; The event number, operation type, synchronization time, and synchronization result of this synchronization are written into the event chain of the target training database.

8. A heterogeneous data synchronization system for aviation flight training, characterized in that, The system includes: The metadata mapping module is used to perform metadata mapping on training business data in heterogeneous training databases, form a unified training data model, and assign a corresponding unique business identifier to the same training business object. The step of mapping training business data in heterogeneous training databases to form a unified training data model includes: Extract the field names, data types, and relationships of the training business data from each of the heterogeneous training databases, and establish a field mapping table; Based on the field mapping table, heterogeneous training business data are unified into a unified training data model with a consistent data structure. The constraint index construction module is used to construct a constraint index in the target training database based on the unique business identifier. The constraint index records the resource identifier, personnel identifier, and time interval of the unarchived task. The incremental conversion module is used to convert the pre-acquired training business change data into a record to be synchronized carrying an event sequence number according to the unified training data model. Before writing the record to be synchronized, use the constraint index to retrieve unarchived task records that have resource usage conflicts and / or personnel usage conflicts with the record to be synchronized and have different business unique identifiers; If the unarchived task record is found, it is determined that the record to be synchronized has a time conflict with the existing task in the target training database, and the record to be synchronized is prevented from being written to the target training database; if the unarchived task record is not found, the target corresponding record with the same business unique identifier as the record to be synchronized is obtained from the target training database, and the time sequence verification of the record to be synchronized is performed based on the event sequence number of the record to be synchronized. The execution module is used to determine whether the record corresponding to the target is in a locked state when the timing verification passes. The synchronization update module is used to write the record to be synchronized into the target training database and update the synchronization status information corresponding to the record to be synchronized in the target training database if the record corresponding to the target is not locked; if the record corresponding to the target is locked, it is prohibited to overwrite the record corresponding to the target, a correction record associated with the record corresponding to the target is generated, and the correction record is written into the event chain of the target training database.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1-7.

Images