Method, device and equipment for data synchronization between heterogeneous systems

Abstract

The invention relates to a method, a device and equipment for data synchronization between heterogeneous systems. The method comprises the steps that a data source and a target system are configured, a mapping relation table between source data fields in the data source and UI elements of the target system is constructed, and a multi-dimensional verification rule and an exception handling decision are defined; monitoring a data change event in the data source, extracting source data related to the data change event, and writing the source data into the UI element corresponding to the target system according to the mapping relation table to obtain synchronous data; verifying the synchronous data according to a multi-dimensional verification rule to obtain a verification result; and judging whether the verification result is verification failure or not, and if yes, executing multi-dimensional early warning and selecting a disposal process according to an exception handling decision. According to the method, through closed-loop design of execution and verification, the accuracy of data synchronization can be effectively ensured; the configurable exception handling decision can effectively deal with complex business scenes and unforeseen circumstances, and the continuity of the data synchronization process is ensured.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus, and device for data synchronization between heterogeneous systems. Background Technology

[0002] In today's enterprise IT environment, data synchronization between different business systems is a critical requirement for ensuring business continuity and data consistency. Currently, the mainstream technical solutions for cross-system data synchronization mainly fall into two categories: one is the integration method based on traditional APIs, which relies on both systems to pre-open standard programming interfaces and exchange structured data through interface calls; the other is the method based on basic Robotic Process Automation (RPA) tools, which simulates user operations and uses interface element recognition and recording / playback technology to execute predetermined data entry or retrieval steps on the interface of systems that do not have open APIs, thereby achieving automated operation.

[0003] However, existing technologies have significant shortcomings in practical applications. First, their level of intelligence is low, especially basic RPA tools, most of which only achieve mechanical replacement of manual operations, i.e., "operation automation," but lack the ability to intelligently verify the business logic of data processing results, thus failing to ensure the correctness of the data processing results. Second, exception handling is weak. When encountering situations such as data verification failure, changes in interface elements, or network anomalies during process execution, existing solutions can usually only issue simple error messages and stop the process, lacking multi-level, flexible exception warning, automatic retry, or manual intervention mechanisms, resulting in business processes being prone to interruption and lacking reliability. Summary of the Invention

[0004] The present invention provides a method, apparatus and device for data synchronization between heterogeneous systems, in order to overcome at least one of the above-mentioned technical problems existing in the prior art.

[0005] To achieve the above objectives, the embodiments of the present invention adopt the following technical solutions: In a first aspect, the present invention provides a method for data synchronization between heterogeneous systems, comprising: Configure the data source and target system, construct a mapping table between source data fields in the data source and UI elements in the target system, and define multi-dimensional validation rules and exception handling decisions; Listen for data change events in the data source, extract the source data involved in the data change events, and write the source data into the UI element corresponding to the target system according to the mapping relationship table to obtain synchronized data; The synchronized data is verified according to the multi-dimensional verification rules to obtain the verification result; Determine whether the verification result is a verification failure. If so, execute a multi-dimensional early warning and select a handling process based on the anomaly handling decision.

[0006] In one possible implementation of the first aspect, the configuration of the data source and the target system includes: Configure the data source and target system through a graphical interface.

[0007] In one possible implementation of the first aspect, the definition of the multi-dimensional verification rules includes: The multi-dimensional verification rules are defined in a pluggable manner, and the multi-dimensional verification rules include at least data consistency verification, data integrity verification, and business logic verification.

[0008] In one possible implementation of the first aspect, the extraction of the source data involved in the data change event includes: Use Selector and / or XPath to extract source data related to the data change event from the data source.

[0009] In one possible implementation of the first aspect, the step of verifying the synchronized data according to the multi-dimensional verification rules to obtain a verification result includes: The synchronization data is obtained from the UI of the target system, and the synchronization data is verified according to the multi-dimensional verification rules to obtain the verification result.

[0010] In one possible implementation of the first aspect, determining whether the verification result is a verification failure includes: The synchronized data is verified dimension by dimension according to the multi-dimensional verification rules. If all dimensions pass the validation, the characterization validation is successful. If any dimension fails to validate, the characterization validation fails.

[0011] In one possible implementation of the first aspect, the execution of multidimensional early warning includes: Capture a screenshot of the current UI of the target system and generate a structured error log; Send the error log to the operations and maintenance team.

[0012] In one possible implementation of the first aspect, selecting a handling procedure based on the exception handling decision includes: Pause the current data synchronization process or skip the currently erroneous synchronization data and continue the subsequent data synchronization process.

[0013] Compared with the prior art, the present invention has at least the following beneficial effects: The present invention provides a method for data synchronization between heterogeneous systems. Through a closed-loop design of execution and verification, it can effectively ensure the accuracy of data synchronization. Configurable exception handling decisions can effectively cope with complex business scenarios and unexpected situations, ensuring the continuity of the data synchronization process. Based on UI-level operation, it does not require system APIs and can be adapted to most graphical interface software, including legacy systems and closed systems, and has high versatility.

[0014] Secondly, the present invention provides an apparatus for data synchronization between heterogeneous systems, comprising: The configuration module is used to configure the data source and the target system, construct a mapping table between the source data fields in the data source and the UI elements of the target system, and define multi-dimensional validation rules and exception handling decisions. The data synchronization module is used to monitor data change events in the data source, extract the source data involved in the data change events, and write the source data into the UI element corresponding to the target system according to the mapping relationship table to obtain synchronized data. The data verification module is used to verify the synchronized data according to the multi-dimensional verification rules and obtain the verification result; The anomaly decision module is used to determine whether the verification result is a verification failure. If so, it executes a multi-dimensional early warning and selects a handling process based on the anomaly handling decision.

[0015] Thirdly, the present invention provides an electronic device comprising: at least one processor and at least one memory, wherein the memory stores computer-readable instructions; the computer-readable instructions are executed by one or more of the processors to cause the electronic device to implement a method for data synchronization between heterogeneous systems as described in any implementation of the first aspect.

[0016] Fourthly, the present invention provides a storage medium having a computer-executable program stored thereon, the computer-executable program being used to cause a computer to perform a method for data synchronization between heterogeneous systems as in any implementation of the first aspect.

[0017] Understandably, the beneficial effects achieved by the system of the second aspect, the electronic device of the third aspect, and the storage medium of the fourth aspect provided above can be referred to in light of the beneficial effects of the first aspect and any of its possible design embodiments, which will not be repeated here. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in 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 some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention; Figure 2 A flowchart illustrating a method for data synchronization between heterogeneous systems provided in an embodiment of the present invention; Figure 3 This is a structural block diagram of a device for data synchronization between heterogeneous systems, provided in an embodiment of the present invention. Detailed Implementation

[0020] The technical solutions of the embodiments of the present invention will be described below with reference to the accompanying drawings. In the description of the present invention, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. The "or" in the present invention is merely a description of the relationship between the related objects, indicating that three relationships can exist. For example, A or B can represent: A alone, A and B simultaneously, and B alone. A and B can be singular or plural. Furthermore, in the description of the present invention, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items.

[0021] Furthermore, to facilitate a clear description of the technical solutions of the embodiments of the present invention, the terms "first" and "second" are used in the embodiments of the present invention to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0022] In this embodiment of the invention, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in this embodiment of the invention should not be construed as superior or more advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.

[0023] In today's enterprise IT environment, data synchronization between different business systems is a critical requirement for ensuring business continuity and data consistency. Currently, the mainstream technical solutions for cross-system data synchronization mainly fall into two categories: one is the integration method based on traditional APIs, which relies on both systems to pre-open standard programming interfaces and exchange structured data through interface calls; the other is the method based on basic Robotic Process Automation (RPA) tools, which simulates user operations and uses interface element recognition and recording / playback technology to execute predetermined data entry or retrieval steps on the interface of systems that do not have open APIs, thereby achieving automated operation.

[0024] However, existing technologies have significant shortcomings in practical applications. First, their level of intelligence is low, especially basic RPA tools, most of which only achieve mechanical replacement of manual operations, i.e., "operation automation," but lack the ability to intelligently verify the business logic of data processing results, thus failing to ensure the correctness of the data processing results. Second, exception handling is weak. When encountering situations such as data verification failure, changes in interface elements, or network anomalies during process execution, existing solutions can usually only issue simple error messages and stop the process, lacking multi-level, flexible exception warning, automatic retry, or manual intervention mechanisms, resulting in business processes being prone to interruption and lacking reliability.

[0025] In view of this, on the one hand, embodiments of the present invention provide a method for data synchronization between heterogeneous systems, comprising: configuring a data source and a target system, constructing a mapping relationship table between source data fields in the data source and UI elements of the target system, and defining multi-dimensional verification rules and exception handling decisions; monitoring data change events in the data source, extracting the source data involved in the data change events, and writing the source data into the corresponding UI elements of the target system according to the mapping relationship table to obtain synchronized data; verifying the synchronized data according to the multi-dimensional verification rules to obtain a verification result; determining whether the verification result is a verification failure, and if so, executing a multi-dimensional early warning and selecting a handling process according to the exception handling decision.

[0026] The method for data synchronization between heterogeneous systems provided in this invention can effectively ensure the accuracy of data synchronization through a closed-loop design of execution and verification; configurable exception handling decisions can effectively cope with complex business scenarios and unexpected situations, ensuring the continuity of the data synchronization process; based on UI-level operation, no system API is required, and it can be adapted to most graphical interface software, including legacy systems and closed systems, and has high versatility.

[0027] In some embodiments, the method for data synchronization between heterogeneous systems provided by the present invention can be executed by any electronic device 20 with data processing capabilities, such as a general-purpose computer, personal computer, laptop computer, switch, or tablet computer, etc. The specific implementation of the electronic device 20 is not limited here.

[0028] Figure 1 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present invention is shown. The electronic device 20 includes a processor 210, a memory 220, and a communication interface 230.

[0029] Processor 210 may include one or more processing cores. Processor 210 connects to various parts within electronic device 200 using various interfaces and lines, and performs various functions and processes data of electronic device 200 by running or executing instructions, programs, code sets, or instruction sets stored in memory 220, and by calling data stored in memory 220. Optionally, processor 210 may be implemented using at least one of the following hardware forms: Central Processing Unit (CPU), Graphics Processing Unit (GPU), Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA).

[0030] The memory 220 may include random access memory (RAM) or read-only memory (ROM). Optionally, the memory 220 may include a non-transitory computer-readable storage medium. The memory 220 may be used to store instructions, programs, code, code sets, or instruction sets. The memory 220 may include a program storage area. This program storage area may store instructions for implementing an operating system, instructions for implementing at least one function, instructions for implementing the various method embodiments described above, etc.

[0031] Communication interface 230 is used to communicate with other devices, equipment or communication networks, such as data storage devices, image processing devices or Ethernet, wireless access network (RAN), wireless local area network (WLAN), etc.

[0032] In terms of physical implementation, the aforementioned devices (such as processor 210, memory 220, and communication interface 230) can each be devices within the same device (such as a laptop computer). Alternatively, at least two of these devices can be located within the same device, i.e., as different devices within the same device, similar to the deployment of devices or components in a distributed system.

[0033] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 20. In other embodiments of the present invention, the electronic device 20 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0034] The following description, in conjunction with the accompanying drawings, illustrates a method for data synchronization between heterogeneous systems provided by an embodiment of the present invention.

[0035] like Figure 2 As shown, embodiments of the present invention provide a method for data synchronization between heterogeneous systems, which may include, but is not limited to: S1: Configure the data source and target system, construct a mapping table between the source data fields in the data source and the UI elements of the target system, and define multi-dimensional validation rules and exception handling decisions.

[0036] In specific implementation, the data source in the embodiments of the present invention may include, but is not limited to, Excel files, databases and web pages, and the target system may include, but is not limited to, ERP, CRM, etc., without limitation.

[0037] In one feasible implementation, the configuration of the data source and target system described in this embodiment of the invention may include, but is not limited to: Configure the data source and target system through a graphical interface.

[0038] In the specific implementation process, configuring the data source and target system through a graphical interface means that users do not need to write any code, but rather complete the "setting up" of the entire automated process through intuitive visual operations such as dragging, clicking, and filling out forms. Specifically, for example: Configure the data source: In a graphical window, users can select the "Excel file" icon and then click the "Browse" button to select a local file; or select the "database" icon and then fill in form information such as IP address, database name, username, and password; or enter the web page URL to configure web page crawling.

[0039] Configure the target system: Users can select "SAP ERP", "Salesforce CRM", etc. from the list, or record a manual operation (such as logging in or clicking a button) to allow the system to automatically recognize the interface of the target application.

[0040] Establish mapping: The interface can display the source data field list (such as Excel column headers) and the target system's UI elements (recognized as "Name Input Box", "Order Amount Table", etc.) side by side. Users can complete the field mapping simply by drawing a line between the two lists with the mouse.

[0041] The embodiments of the present invention use a graphical interface to configure the data source and target system, which can effectively reduce the technical threshold and improve deployment efficiency and flexibility.

[0042] It should be noted that, in the embodiments of the present invention, the configuration of the above-mentioned data source and target system can be achieved not only through a graphical interface, but also by writing configuration files (such as XML, JSON) or specific scripts. The core of both is to generate a set of mappings and rule definitions that can be read by subsequent steps.

[0043] In one feasible implementation, the definition of multi-dimensional verification rules in this embodiment of the invention may include, but is not limited to: The multi-dimensional verification rules are defined in a pluggable manner, and the multi-dimensional verification rules include at least data consistency verification, data integrity verification, and business logic verification.

[0044] The embodiments of the present invention use a pluggable approach to define the multi-dimensional verification rules, which can improve the flexibility and responsiveness of defining verification rules. Especially in business environments that need to cope with frequent changes, different sets of verification rules can be enabled at different times and for different types of data, thereby providing fine-grained control over process execution and greatly enhancing adaptability.

[0045] In specific implementation, the pluggable method described in the embodiments of the present invention may be implemented by, but is not limited to, encapsulating the verification rules into independent plug-in modules, defining rule expressions in configuration files, or integrating external rule engines, etc., and is not limited here.

[0046] In specific implementation, the data consistency verification in this embodiment of the invention typically refers to a horizontal comparison between the source data and the synchronized data of the target system to ensure that the information has not been tampered with or lost during the process. For example, if the reimbursement amount in the data source is 1250.80 yuan, is the amount displayed in the target system 1250.80 yuan, or has it become 1250.8 or 1258.00, etc.? The data integrity verification typically refers to whether the fields or field combinations of the synchronized data of the source data and the target system are aligned and correctly shaped. For example, when reimbursing, are the required fields [reimbursing person, department, total amount] empty? Is the data format [employee ID] an 8-digit number? Is the [number of receipts] a positive integer? The business logic verification typically refers to the inherent logic and status flow of the data itself. For example, in reimbursement, the time logic is that the end date of the reimbursement cannot be earlier than the start date, and the status logic is that a document with the status "rejected" cannot directly enter the "paid" status, but must first change to "resubmitted," etc.

[0047] It should be noted that the multi-dimensional verification rules in this embodiment of the invention are an extensible set. In addition to the three types mentioned above, the verification dimensions may also include technical validity verification, security compliance verification, etc., which are not limited here.

[0048] S2: Listen for data change events in the data source, extract the source data involved in the data change events, and write the source data into the UI element corresponding to the target system according to the mapping relationship table to obtain synchronization data.

[0049] In specific implementation, different listening methods can be adopted in this embodiment of the invention depending on the data source, such as file system event listening, database trigger listening, polling, message queue subscription, Webhook callback, etc., which are not limited here.

[0050] In one feasible implementation, the source data involved in extracting the data change event in this embodiment of the invention may include, but is not limited to: Use Selector and / or XPath to extract source data related to the data change event from the data source.

[0051] Selector and XPath are both positioning technologies used in UI interfaces, capable of accurately extracting source data related to the data change events.

[0052] It should be noted that, in addition to Selector and XPath, other positioning technologies can also be used in the embodiments of the present invention, such as positioning based on image recognition, positioning based on accessibility interfaces, etc., which are not limited here.

[0053] S3: Verify the synchronized data according to the multi-dimensional verification rules to obtain the verification result.

[0054] In one feasible implementation, the step of verifying the synchronized data according to the multi-dimensional verification rules to obtain the verification result in this embodiment of the invention may include, but is not limited to: The synchronization data is obtained from the UI of the target system, and the synchronization data is verified according to the multi-dimensional verification rules to obtain the verification result.

[0055] This invention, by retrieving the synchronous data from the UI of the target system, can effectively capture silent errors caused by front-end processing, asynchronous loading, and permission restrictions in the target system during data writing. This provides accurate and reliable data input for subsequent business logic verification, ensuring the validity of the verification results. It also achieves end-to-end integrity verification of data from the source system to the display layer of the target system, thus constructing a closed loop for data quality.

[0056] In specific implementation, embodiments of the present invention can pre-set a timing strategy for retrieving the synchronization data in reverse, waiting for the target system's UI interface data to stabilize, such as fixed delay waiting, dynamic waiting based on element state changes, or multiple sampling verification based on numerical stability. After the target system's UI interface data stabilizes, the synchronization data is located and read using UI element recognition technology (such as Selector, XPath, etc.), and then the synchronization data is verified according to the multi-dimensional verification rules.

[0057] S4: Determine whether the verification result is a verification failure. If so, execute a multi-dimensional early warning and select a handling process based on the anomaly handling decision.

[0058] In one feasible implementation, determining whether the verification result is a verification failure in this embodiment of the invention includes: The synchronized data is verified dimension by dimension according to the multi-dimensional verification rules. If all dimensions pass the validation, the characterization validation is successful. If any dimension fails to validate, the characterization validation fails.

[0059] In the specific implementation process, the process of verifying the synchronized data dimension by dimension in this embodiment of the invention can adopt a funnel shape, that is: first, perform data integrity verification to ensure that the necessary fields in the target system have been filled in correctly and that the data format meets the system requirements (such as email format, mobile phone number length, etc.); second, perform business logic verification to verify the logical rationality of the data according to business rules; and finally, perform data consistency verification to ensure the accuracy of the data.

[0060] In one feasible implementation, the execution of multi-dimensional early warning in this embodiment of the invention may include, but is not limited to: Capture a screenshot of the current UI of the target system and generate a structured error log; Send the error log to the operations and maintenance team.

[0061] In specific implementation, the error logs in this embodiment of the invention may include, but are not limited to, structured data such as timestamps, data identifiers, and error types, which are not limited here. This embodiment of the invention can send the error logs to the operations and maintenance (O&M) end via email or SMS, or it can integrate with the robot interfaces of office tools such as WeChat Work, DingTalk, and Slack to send the error logs to the O&M end, which are not limited here.

[0062] In one feasible implementation, the selection of the handling process based on the anomaly handling decision in this embodiment of the invention may include, but is not limited to: Pause the data synchronization process or skip the currently erroneous data synchronization and continue the subsequent data synchronization process.

[0063] In practical implementation, when defining anomaly handling decisions, this embodiment of the invention can select different handling methods based on the category and severity of erroneous data. For example, for erroneous data such as individual data format errors in batch data migration, individual page anomalies in web page data crawling, and missing non-critical fields in financial statement generation, the current erroneous synchronized data can be skipped and the subsequent data synchronization process can continue. For erroneous data such as sequentially dependent process processing, operations involving fund security, system-level or environment-level errors, and violations of core business rules, the data synchronization process can be suspended. By intelligently selecting "skip" or "suspend" based on the category and severity of erroneous data, business continuity can be ensured while effectively controlling risks.

[0064] The method for data synchronization between heterogeneous systems provided in this invention can effectively ensure the accuracy of data synchronization through a closed-loop design of execution and verification; configurable exception handling decisions can effectively cope with complex business scenarios and unexpected situations, ensuring the continuity of the data synchronization process; based on UI-level operation, no system API is required, and it can be adapted to most graphical interface software, including legacy systems and closed systems, and has high universality.

[0065] Based on the method for data synchronization between heterogeneous systems provided in the first aspect, embodiments of the present invention provide an apparatus for data synchronization between heterogeneous systems, such as... Figure 3 As shown, the device for data synchronization between heterogeneous systems includes: Configuration module 110 is used to configure the data source and the target system, construct a mapping relationship table between the source data fields in the data source and the UI elements of the target system, and define multi-dimensional verification rules and exception handling decisions; The data synchronization module 120 is used to monitor data change events in the data source, extract the source data involved in the data change events, and write the source data into the UI element corresponding to the target system according to the mapping relationship table to obtain synchronized data. Data verification module 130 is used to verify the synchronized data according to the multi-dimensional verification rules and obtain the verification result; The exception decision module 140 is used to determine whether the verification result is a verification failure. If so, it selects a handling process according to the exception handling decision.

[0066] Based on the method for data synchronization between heterogeneous systems provided in the first aspect, embodiments of the present invention also provide a storage medium storing a computer-executable program, which is used to cause a computer to execute the method for data synchronization between heterogeneous systems as described in any implementation of the first aspect. Explanations of the relevant content and descriptions of the beneficial effects of any of the computer-readable storage media provided above can be found in the corresponding embodiments described above, and will not be repeated here.

[0067] Those skilled in the art will understand that the program for implementing all or part of the steps of the above embodiments, which can be executed by a program instructing related hardware, can be stored in a computer-readable storage medium. The storage medium mentioned above can be a read-only memory, a random access memory, etc. The processing unit or processor mentioned above can be a central processing unit, a general-purpose processor, an application-specific integrated circuit (ASIC), a microprocessor (DSP), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.

[0068] This invention also provides a computer program product containing instructions that, when executed on a computer, cause the computer to perform any of the methods described in the above embodiments. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this invention is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., SSD), etc.

[0069] It should be noted that the devices for storing computer instructions or computer programs provided in the embodiments of the present invention, such as, but not limited to, the aforementioned memory, computer-readable storage medium, and communication chip, are all non-transitory. Those skilled in the art should recognize that the functions described in the embodiments of the present invention in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable storage medium or transmitted as one or more instructions or code on a computer-readable storage medium. Computer-readable storage media include computer storage media and communication media, wherein communication media include any medium that facilitates the transmission of computer programs from one place to another. Storage media can be any available medium accessible to general-purpose or special-purpose computers.

[0070] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.

Claims

1. A method for data synchronization between heterogeneous systems, characterized in that, include: Configure the data source and target system, construct a mapping table between source data fields in the data source and UI elements in the target system, and define multi-dimensional validation rules and exception handling decisions; Listen for data change events in the data source, extract the source data involved in the data change events, and write the source data into the UI element corresponding to the target system according to the mapping relationship table to obtain synchronized data; The synchronized data is verified according to the multi-dimensional verification rules to obtain the verification result; Determine whether the verification result is a verification failure. If so, execute a multi-dimensional early warning and select a handling process based on the anomaly handling decision.

2. The method for data synchronization between heterogeneous systems according to claim 1, characterized in that, The configuration of the data source and target system includes: Configure the data source and target system through a graphical interface.

3. The method for data synchronization between heterogeneous systems according to claim 1, characterized in that, The defined multi-dimensional verification rules include: The multi-dimensional verification rules are defined in a pluggable manner, and the multi-dimensional verification rules include at least data consistency verification, data integrity verification, and business logic verification.

4. The method for data synchronization between heterogeneous systems according to claim 1, characterized in that, The source data involved in extracting the data change event includes: Use Selector and / or XPath to extract source data related to the data change event from the data source.

5. The method for data synchronization between heterogeneous systems according to claim 1, characterized in that, The step of verifying the synchronized data according to the multi-dimensional verification rules to obtain the verification result includes: The synchronization data is obtained from the UI of the target system, and the synchronization data is verified according to the multi-dimensional verification rules to obtain the verification result.

6. The method for data synchronization between heterogeneous systems according to claim 5, characterized in that, The step of determining whether the verification result is a verification failure includes: The synchronized data is verified dimension by dimension according to the multi-dimensional verification rules. If all dimensions pass the validation, the characterization validation is successful. If any dimension fails to validate, the characterization validation fails.

7. The method for data synchronization between heterogeneous systems according to claim 1, characterized in that, The execution of multi-dimensional early warning includes: Capture a screenshot of the current UI of the target system and generate a structured error log; Send the error log to the operations and maintenance team.

8. The method for data synchronization between heterogeneous systems according to claim 1, characterized in that, The step of selecting a handling procedure based on the anomaly handling decision includes: Pause the data synchronization process or skip the currently erroneous data synchronization and continue the subsequent data synchronization process.

9. A device for data synchronization between heterogeneous systems, characterized in that, include: The configuration module is used to configure the data source and the target system, construct a mapping table between the source data fields in the data source and the UI elements of the target system, and define multi-dimensional validation rules and exception handling decisions. The data synchronization module is used to monitor data change events in the data source, extract the source data involved in the data change events, and write the source data into the UI element corresponding to the target system according to the mapping relationship table to obtain synchronized data. The data verification module is used to verify the synchronized data according to the multi-dimensional verification rules and obtain the verification result; The anomaly decision module is used to determine whether the verification result is a verification failure. If so, it executes a multi-dimensional early warning and selects a handling process based on the anomaly handling decision.

10. An electronic device, characterized in that, include: A memory, one or more processors; the memory is coupled to the processors; wherein the memory stores computer program code, the computer program code including computer instructions, which, when executed by the processor, cause the electronic device to perform a method for data synchronization between heterogeneous systems as described in any one of claims 1 to 8.

Images