Data synchronization processing method and device, electronic equipment and storage medium

Abstract

The invention discloses a data synchronization processing method and device, electronic equipment and a storage medium. The method is applied to each software operation environment in a plurality of software operation environments, each software operation environment performs data interaction with an LDAP server, and the LDAP server comprises user information generated by the plurality of software operation environments; the method comprises the steps of obtaining timed task configuration information in response to a timed task creation operation; generating a target timed task based on the timed task configuration information through an XXL-JOB task scheduling engine; and acquiring to-be-synchronized data from the LDAP server according to a timing rule corresponding to the target timing task, and performing synchronization processing on the to-be-synchronized data. According to the scheme, timing task management is realized by interacting with the LDAP server in the multiple software operation environments and utilizing the XXL-JOB task scheduling engine, unified management and interaction of user information across the operation environments are realized, regularity and automation of data synchronization are ensured through a timing task mechanism, and omission and delay of manual intervention are avoided.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular to a data synchronization processing method and device, electronic equipment and storage medium. BACKGROUND

[0002] With the rapid development of digital transformation, the platform operation management system as the unified entrance of the technology middle station shoulders the key responsibility of user management of the technology middle station. In the system development process, for the huge system, complex environment, large number of services, and the data inequality of production, development, testing and other environments, it leads to the problem of unified management from the development environment to the test environment and then to the deployment production.

[0003] In the prior art, the user management of the platform operation management system under multiple environments has many deficiencies. In the traditional mode, each system needs to maintain the user account independently, and relies on manual creation, update and permission configuration. This mode not only leads to the fragmentation of cross-system user information, and it is difficult to guarantee data consistency, but also the manual operation efficiency is low, and it is easy to make input information error and the maintenance and management is complex, and there is a problem of poor data synchronization processing efficiency. SUMMARY

[0004] The present application provides a data synchronization processing method, device, electronic equipment and storage medium to solve the problem of poor data synchronization processing efficiency across operating environments.

[0005] According to an aspect of the present application, a data synchronization processing method is provided, which is applied to each software operating environment in a plurality of software operating environments, each software operating environment respectively interacts with an LDAP server for data, and the LDAP server includes user information generated by each software operating environment; the method comprises:

[0006] In response to a timing task creation operation, timing task configuration information is obtained, wherein the timing task configuration information includes executor information, scheduling type, running mode, task processor and strategy information;

[0007] A target timing task is generated based on the executor information, scheduling type, running mode, task processor and strategy information through an XXL-JOB task scheduling engine;

[0008] The target timing task is started, and the to-be-synchronized data is obtained from the LDAP server according to the timing rule corresponding to the target timing task, and the to-be-synchronized data is synchronized.

[0009] Optionally, before obtaining the scheduled task configuration information in response to the scheduled task creation operation, it also includes: registering an event listener for the scheduled task creation operation; monitoring the scheduled task creation operation in real time through the event listener, and triggering the process of obtaining the scheduled task configuration information when the scheduled task creation operation is detected.

[0010] Optionally, the target scheduled task is generated through the task scheduling engine of XXL-JOB based on the executor information, scheduling type, operation mode, task processor and policy information, including: constructing a task configuration object that conforms to the preset XXL-JOB specification based on the executor information, scheduling type, operation mode, task processor and policy information; calling the task management interface of the XXL-JOB task scheduling engine, persisting the task configuration object to the database, and generating the target scheduled task.

[0011] Optionally, after obtaining the scheduled task configuration information, the method also includes: calling the mapping relationship between the configuration information and the verifier, matching each configuration item in the scheduled task configuration information with the mapping relationship, determining the verifier corresponding to each configuration item in the scheduled task configuration information, and binding each configuration item with the corresponding verifier; verifying the corresponding configuration item based on the verifier corresponding to each configuration item to obtain the verification result corresponding to each configuration item; when the verification result corresponding to each configuration item meets the preset conditions, executing the generation processing of the target scheduled task.

[0012] Optionally, the method also includes: upon receiving a user information change request, determining the user information to be changed based on the user information change request; performing verification processing on the user information to be changed, and transmitting the user information to be changed that has successfully been verified to the LDAP server to update the user information in the LDAP server, wherein the verification processing includes at least format verification processing, business rule verification processing and uniqueness verification processing.

[0013] Optionally, the data to be synchronized includes at least one incremental user information; synchronization processing of the data to be synchronized includes: for any incremental user information, searching in the target database based on the user name and user email in the incremental user information; if the same user name and user email are retrieved, updating the corresponding data in the target database based on the incremental user information; if the same user name and user email are not retrieved, creating a new record and filling the data in the incremental user information into the new record until each incremental user information is stored in the target database.

[0014] According to another aspect of the present invention, there is provided a data synchronization processing device, comprising:

[0015] A scheduled task configuration information acquisition module is used to obtain scheduled task configuration information in response to a scheduled task creation operation, wherein the scheduled task configuration information includes executor information, scheduling type, operation mode, task processor and policy information;

[0016] The target scheduled task generation module is used to generate target scheduled tasks based on executor information, scheduling type, operation mode, task processor and strategy information through the XXL-JOB task scheduling engine;

[0017] The data synchronization processing module is used to start the target scheduled task, obtain the data to be synchronized from the LDAP server according to the timing rules corresponding to the target scheduled task, and synchronize the data to be synchronized.

[0018] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0019] at least one processor; and

[0020] a memory communicatively connected to at least one processor; wherein,

[0021] The memory stores a computer program that can be executed by at least one processor. The computer program is executed by the at least one processor so that the at least one processor can execute the data synchronization processing method of any embodiment of the present invention.

[0022] According to another aspect of the present invention, a computer-readable storage medium is provided. The computer-readable storage medium stores computer instructions, which are used to enable a processor to implement the data synchronization processing method of any embodiment of the present invention when executed.

[0023] According to another aspect of the present invention, a computer program product is provided, comprising a computer program, wherein the computer program implements the data synchronization processing method according to any embodiment of the present invention when executed by a processor.

[0024] The technical solution of an embodiment of the present invention is applied to each software operating environment in multiple software operating environments, each software operating environment interacts with an LDAP server for data exchange, and the LDAP server includes user information generated by the multiple software operating environments respectively; by responding to a scheduled task creation operation, the scheduled task configuration information is obtained, wherein the scheduled task configuration information includes executor information, scheduling type, operating mode, task processor and policy information; through the XXL-JOB task scheduling engine, a target scheduled task is generated based on the executor information, scheduling type, operating mode, task processor and policy information; the target scheduled task is started, and the data to be synchronized is obtained from the LDAP server according to the timing rules corresponding to the target scheduled task, and the data to be synchronized is synchronized. The solution interacts with the LDAP server in multiple software runtime environments and uses the XXL-JOB task scheduling engine to implement scheduled task management, which can achieve unified management and interaction of user information across runtime environments. The scheduled task mechanism ensures the regularity and automation of data synchronization, avoiding omissions and delays in manual intervention. The comprehensiveness of configuration information makes task generation more flexible and targeted, and can adapt to the scheduling needs of different business scenarios. The introduction of the XXL-JOB engine provides distributed task scheduling capabilities, supports efficient execution and management of tasks in high-concurrency scenarios, and improves system stability and scalability. According to the timing rules, the data to be synchronized is obtained and processed from the LDAP server, ensuring the consistency and real-time nature of user information in multiple software runtime environments, effectively solving the problem of data silos, providing a solid data foundation for cross-system business collaboration, and effectively improving the efficiency of data synchronization processing.

[0025] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the present invention. Other features of the present invention will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0027] Figure 1 This is a flow chart of a data synchronization processing method provided by the first embodiment of the present invention;

[0028] Figure 2 This is a flow chart of a data synchronization processing method provided by the second embodiment of the present invention;

[0029] Figure 3This is a structural diagram of a data synchronization processing device provided by Embodiment 3 of the present invention;

[0030] Figure 4 It is a structural diagram of an electronic device for implementing the data synchronization processing method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0031] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0032] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0033] Example 1

[0034] Figure 1 This is a flowchart of a data synchronization method provided in Example 1 of the present invention. This embodiment is applicable to data synchronization. The method can be executed by a data synchronization device, which can be implemented in hardware and / or software and configured in electronic devices such as computers and servers. The method is applied to each of multiple software runtime environments, each of which interacts with an LDAP server. The LDAP server contains user information generated by each of the multiple software runtime environments.

[0035] The software operating environment can be specifically understood as the sum of the conditions and resources required to support the normal operation of the software program, including the hardware environment (such as the processor, memory, storage and other hardware configurations of the server and terminal device) and the software environment (such as the operating system, database management system, middleware, runtime library, driver, etc.). It also involves related configurations such as network connection status, system permission settings, and security policies. These elements together constitute the basic conditions for the software to execute code, process data, and interact with users or other systems. Different software has different requirements for the operating environment due to differences in their functions and technical architectures. Only when the environment meets the needs of the software can the program start correctly and perform its functions. In short, the environment is a necessary condition for the survival and work of the software. Developers need to ensure that the target environment is compatible with the development environment, and users need to configure the environment as needed to use the software. In the actual development process, the software operating environment includes but is not limited to the development environment, test environment, pre-release environment and production environment. Different operating environments can be deployed according to the software development cycle and usage scenarios, which are not limited here.

[0036] In this embodiment, an application system can be deployed in each software operating environment, and the application system can be deployed including but not limited to a platform operation management system. The user information generated by the application system of each software operating environment can be used as the user information generated by the corresponding software operating environment. The user information generated by each software operating environment needs to be synchronized across the operating environments to avoid repeated additions and modifications to each software operating environment. It is necessary to synchronize the user information generated by multiple software operating environments. Taking the platform operation management system as an example, the platform operation management system in each software operating environment needs to independently maintain user information, and needs to synchronize the user information maintained in each software operating environment to avoid the fragmentation of user information across operating environments and the difficulty in ensuring data consistency. The data synchronization processing method in this application can be applied to each software operating environment in multiple software operating environments. Each software operating environment interacts with the LDAP server for data, obtains the data to be synchronized from the LDAP server, and performs synchronization processing. The LDAP server includes user information generated by multiple software operating environments.

[0037] like Figure 1 As shown, the method includes:

[0038] S110 . In response to the scheduled task creation operation, obtain scheduled task configuration information.

[0039] Scheduled task configuration information includes executor information, scheduling type, run mode, task processor, and policy information. Information synchronization requirements for different business modules or systems can be configured through a visual interface, including but not limited to executor information, scheduling type, run mode, task processor, and policy information. Executor information can be understood as specifying the service carrier for task execution, including but not limited to the executor name and registered IP port, ensuring the scheduler can accurately route task requests. Scheduling type can be understood as defining task triggering rules, including but not limited to periodic execution via CRON expressions, or triggering with a fixed frequency or fixed delay, which determines when the task starts. Run mode can be understood as the method for loading task code, including but not limited to BEAN mode, GLUE mode, script mode, and API mode. BEAN mode calls methods of beans registered in the Spring container. GLUE mode supports dynamic execution of Java code written online to meet code deployment requirements in different scenarios. Script mode implements task logic by executing script files (such as Python, Shell, JavaScript, etc.). API mode triggers task execution by calling external API interfaces. Task logic is encapsulated in third-party services, and task parameters (such as execution time and data range) can be dynamically adjusted through API parameters. The task processor can be understood as a specific execution method or class path, specifying the bean method name or execution entry point in the GLUE code, and clearly defining the operation to be performed by the task. Policy information can be understood as including strategies such as task blocking handling (such as single-machine serialization and overlay execution), failure retry counts, and timeout control to ensure the stability and fault tolerance of task execution. The various information in the scheduled task configuration information together constitute the complete execution rules of the scheduled task, enabling full process control from scheduling triggering to logical execution.

[0040] Specifically, in any software runtime environment, when the system responds to a scheduled task creation operation, it first triggers the configuration information acquisition process. This process can be achieved by receiving a scheduled task creation request from a user interface or API (Application Programming Interface). The complete configuration data, including executor information, scheduling type, operating mode, task processor, and policy information, is then extracted from the scheduled task creation request. After the data is verified for legitimacy, it can be parsed by a task scheduling engine (such as XXL-JOB) to generate a target task instance, which is then registered with the scheduling center for scheduled triggering.

[0041] In this embodiment, the structured acquisition of standardized configuration information is used to ensure the detailed integrity and traceability of task configuration, and avoid execution anomalies caused by configuration missing; by setting the executor information, scheduling type, operation mode, task processor and policy information separately, subsequent maintenance and dynamic adjustment are facilitated, and flexible scheduling types and operation modes support different business scenarios, enhancing the system adaptability; the built-in policy information (such as retry, timeout) ensures the stability of task execution, reduces the cost of manual intervention, and provides a data basis for subsequent task monitoring and optimization.

[0042] Optionally, before obtaining the scheduled task configuration information in response to the scheduled task creation operation, it also includes: registering an event listener for the scheduled task creation operation; monitoring the scheduled task creation operation in real time through the event listener, and triggering the process of obtaining the scheduled task configuration information when the scheduled task creation operation is detected.

[0043] Among them, the event listener can be specifically understood as a component based on the publish-subscribe model, which is used to monitor the occurrence of scheduled task events in the system in real time and trigger the corresponding processing logic. By binding the event handler to the event type, the corresponding logic is automatically executed when the event is published. The registration method of the event listener can be based on automatic registration with annotations, such as marking the listening method with the @EventListener annotation in Spring, and automatically scanning and registering when the framework starts; or, it can be registered manually through the interface, that is, defining the event interface and type, and manually registering the listener to the event manager after implementing the interface; or, it can be registered through a configuration file, like declaring the binding relationship between the listener and the event in the traditional XML configuration of Spring; or, it can be registered through dynamic registration, and dynamically register or unregister the listener according to the conditions through the corresponding API at runtime; or, it can be through distributed registration based on message queues, which is suitable for microservice architectures, and is implemented by publishing events to message queues and subscribers consuming messages; or, it can be through automatic discovery registration based on the service provider interface (SPI), using the service provider interface mechanism, and automatically loading and registering the implementation class when the framework starts. For example, when a specific operation occurs in the system, such as the creation of a scheduled task, the corresponding event object is generated by the event source. A TaskCreateEvent event object can be created and published to the event bus. The event bus searches for all registered listeners according to the event type, filters out the processors bound to the event type, calls the listener's processing method in sequence, passes the event object, and executes specific logic, such as triggering the configuration information acquisition process. The processing method supports synchronous (blocking the main thread) or asynchronous (asynchronous execution through the thread pool).

[0044] Specifically, when implementing the response mechanism of the scheduled task creation operation, you can register the event listener through the preset event listener registration method, bind the event listener to the event bus, and bind the event listener to the scheduled task creation event type to listen to the scheduled task creation event. When the user initiates the scheduled task creation operation through the parameter configuration interface or API of the scheduled task configuration information, the system generates an event object containing the operation context, that is, the event object TaskCreateEvent is generated according to the configuration information corresponding to the scheduled task creation operation, and published to the event bus. When the event listener captures the event triggered by the scheduled task creation operation in real time, it actively triggers the acquisition process of the scheduled task configuration information through the publish-subscribe mode, such as calling the configuration parsing service or loading the default parameter template, to achieve automated connection from operation triggering to configuration collection.

[0045] In this embodiment, the task creation operation is decoupled through an event-driven architecture, which supports dynamic addition of listeners without modifying the core logic, thereby improving the scalability of the system; the standardized event interface enables centralized management of the listening logic, reducing maintenance costs; the events of the scheduled task creation operation are processed through a unified event bus to ensure the consistency of business logic; the event mechanism supports the addition of monitoring points, which helps to enhance the observability of the system.

[0046] S120 , generating a target scheduled task based on executor information, scheduling type, operation mode, task processor and strategy information through the XXL-JOB task scheduling engine.

[0047] Among them, the XXL-JOB task scheduling engine is a lightweight distributed task scheduling engine. Through an architectural design that separates task scheduling from execution, it provides a visual management interface, flexible configuration parameters (such as executor information, scheduling type, operating mode, etc.), and comprehensive task lifecycle management (such as failure retries and timeout control). Target scheduled tasks are executable entities generated by this engine. They are a complex system that includes static configuration, dynamic triggers, execution instances, and monitoring records. They use database records as a persistent carrier (to store configuration information), Quartz triggers as an in-memory operating form (to implement timed triggering), and thread instances in the executor as execution units (to process specific business logic). They form a complete closed loop through runtime monitoring data (such as execution logs). In short, XXL-JOB is the infrastructure for task scheduling, and target scheduled tasks are specific business jobs that run on this infrastructure. Together, they form the core framework for enterprise-level scheduled task management. In addition, users can also view task lists, execution records, and other information through the XXL-JOB management interface.

[0048] Specifically, the XXL-JOB task scheduling engine obtains executor information, which can be core parameters such as the application name and registration address. It also specifies the scheduling type, which can be a CRON expression or a fixed interval trigger. It selects the run mode, which supports BEAN mode invoking a Spring container or dynamic GLUE script execution. It binds specific task processors and configures policy information, such as the number of failed retries and routing algorithms. The engine encapsulates the executor information, scheduling type, run mode, task processor, and policy information as task metadata, registers it with the scheduling center via a REST API, and is persistently stored by the scheduling node and dynamically added to the task queue. Ultimately, the configured rules trigger the executor cluster to complete task execution through RPC calls.

[0049] In this embodiment, the target scheduled task is generated by the XXL-JOB task scheduling engine, which realizes the complete decoupling of scheduling configuration and business logic. High-reliability scheduled tasks can be quickly built according to the obtained parameter configuration information, thereby improving development efficiency. The XXL-JOB task scheduling engine supports visual operation and real-time effectiveness, and policy adjustments can be completed without restarting the service. Through automatic registration of executors and intelligent routing strategies, task reliability is guaranteed in a distributed environment. At the same time, the XXL-JOB task scheduling engine also provides a complete log tracking, performance monitoring and failure alarm system, which effectively reduces the complexity of operation and maintenance, and is particularly suitable for enterprise-level scheduled task scenarios that require high availability and elastic expansion.

[0050] Based on the above embodiment, after obtaining the scheduled task configuration information, the method also includes: calling the mapping relationship between the configuration information and the verifier, matching each configuration item in the scheduled task configuration information with the mapping relationship, determining the verifier corresponding to each configuration item in the scheduled task configuration information, and binding each configuration item with the corresponding verifier; verifying the corresponding configuration item based on the verifier corresponding to each configuration item to obtain the verification result corresponding to each configuration item; when the verification result corresponding to each configuration item meets the preset conditions, executing the generation processing of the target scheduled task.

[0051] Specifically, a validator can be understood as a dedicated validation component for scheduled task configuration items. It encapsulates the validity check logic for specific configuration items, such as CRON expression format validation and executor ID validity verification. Corresponding validators can be pre-set for each scheduled task configuration item that requires validation, and a mapping relationship between configuration information and validators can be established. When the configuration information needs to be validated, the mapping relationship can be directly called to determine the validator corresponding to the configuration information. It can be implemented as a separate class or method, accepting configuration item parameters and returning validation results, including pass / fail and error descriptions. Its core function is to ensure that the configuration information complies with system requirements and business rules. Preconditions are the criteria that the validation results must meet. For example, preconditions can be set as "all configuration items pass validation" or "no fatal errors in critical configuration items." Only when the validation results of all configuration items meet the corresponding preconditions will the system allow the target scheduled task to be generated. This forms a preemptive defense mechanism to prevent task generation failure or execution anomalies due to configuration errors, ensuring the accuracy and effectiveness of task configuration.

[0052] Specifically, after obtaining the scheduled task configuration information, the mapping relationship between the configuration information and the validator is called, the configuration items are matched with the mapping relationship, the validator corresponding to the configuration items is obtained, and the configuration items are dynamically bound to the validators. This process can be implemented through reflection or factory mode, for example, searching for classes ending with Validator based on the configuration item name; then, the validator executes the verification logic in sequence, such as checking whether the CRON expression format is legal and whether the executor is online. Each validator returns a verification result object containing a status code and error information; finally, the system aggregates all results and compares them with the preset conditions. Only when the conditions are fully met will the subsequent task generation process be triggered.

[0053] In this embodiment, by determining the verifier of the scheduled task configuration information and performing verification processing, a pre-error interception mechanism is implemented to avoid abnormalities in the task execution phase, improve system stability, and ensure the accuracy and effectiveness of task configuration.

[0054] S130: Start the target scheduled task, obtain the data to be synchronized from the LDAP server according to the timing rule corresponding to the target scheduled task, and synchronize the data to be synchronized.

[0055] Specifically, when the target scheduled task is successfully started, the XXL-JOB scheduling engine triggers the task execution according to the timing rules in the task configuration (such as CRON expressions). After the executor receives the scheduling instruction, it establishes a connection based on the configured LDAP server connection information (address, port, authentication credentials), and queries and obtains the qualified data to be synchronized from the server through the LDAP protocol (such as simple binding, search operations). For example, the purpose of obtaining incremental data from the LDAP server can be achieved by sending incremental information acquisition instructions to the LDAP server. After obtaining the incremental data, the executor cleans and integrates the data according to the preset synchronization processing logic (such as data format conversion, field mapping, deduplication verification), and finally synchronizes the processed data to the target storage database or system to complete the entire data synchronization process. In the event of a connection failure with the LDAP server, the application system in each software running environment can obtain user information from the local database for information verification, avoiding system login timeout or login failure problems, which helps to improve the user experience.

[0056] In this embodiment, the data to be synchronized is obtained from the LDAP server and synchronized through the timing rules corresponding to the target scheduled task, so that data synchronization is automated through the scheduled task mechanism, manual intervention is reduced, and the timeliness and accuracy of data updates are improved; data is obtained based on the LDAP protocol to ensure the standardization and security of the data source; the flexible configuration of the synchronization processing logic can adapt to different data structures and business needs, and enhance the scalability of the system; at the same time, relying on the scheduling management capabilities of XXL-JOB, visual monitoring of tasks, failure retries and exception alarms can be achieved, effectively ensuring the stability and reliability of data synchronization tasks.

[0057] Optionally, the data to be synchronized includes at least one incremental user information; synchronization processing of the data to be synchronized includes: for any incremental user information, searching in the target database based on the user name and user email in the incremental user information; if the same user name and user email are retrieved, updating the corresponding data in the target database based on the incremental user information; if the same user name and user email are not retrieved, creating a new record and filling the data in the incremental user information into the new record until each incremental user information is stored in the target database.

[0058] Specifically, the data to be synchronized includes at least one incremental user information, for each incremental user information, the system first extracts the username and user mailbox field content in the incremental user information as a search condition to perform a query operation in the target database, wherein the username and user mailbox constitute a unique identifier. If the query result exists a matching record, that is, the same username and user mailbox combination is found, the data in the incremental user information is overwritten or merged into the corresponding field of the record in the target database, and the data update is completed; if there is no matching record in the query, a new blank record is created in the target database, and then each item of data contained in the incremental user information is filled into the corresponding field of the new record one by one to ensure complete data entry. The incremental user information includes user ID, contact information, and permission information, etc., which are not limited here. The system continues to cycle the above operation until all incremental user information is successfully stored in the target database.

[0059] In the embodiment, by synchronously processing the data to be synchronized, the double verification of the username and the user mailbox avoids duplicate data entry, and improves the database data quality; the update mechanism can reflect the latest changes of the user information in time, and ensures the data timeliness; the process automation reduces manual intervention, and improves the data processing efficiency; at the same time, the unified processing logic adapts to various incremental data scenarios, ensures the accuracy and integrity of the data, has good universality and expansibility, and is convenient for subsequent function maintenance and upgrading.

[0060] On the basis of the above embodiment, the method further includes: in the case that the user information change request is received, determining the user information to be changed based on the user information change request; performing a verification process on the user information to be changed, and transmitting the user information to be changed that passes the verification to the LDAP server to update the user information in the LDAP server.

[0061] The verification process at least includes format verification processing, business rule verification processing, and uniqueness verification processing. The format verification processing is used to check whether each item of information in the user information to be changed conforms to a preset format standard, for example, whether the username, the email format, and the date format belong to the corresponding preset format standard; the business rule verification processing is used to verify the rationality of the information according to the system business logic, for example, whether the permission range is compliant, and whether the username and the email are valid; and the uniqueness verification processing is used to check whether the key information such as the username and the user mailbox is repeated in the LDAP server or the associated database, and the username and the user mailbox constitute unique information.

[0062] Specifically, when the system receives a user information change request, it parses the request content and extracts the user information to be changed, which includes but is not limited to the user name, user email address, contact information, and permission information. Subsequently, the system performs verification processing on the information to be changed in sequence. If the information to be changed passes all verifications, the system encapsulates it into a data packet that conforms to the LDAP protocol, establishes a connection with the LDAP server, and sends the data. The server then updates the corresponding entry, completing the user information change. This ensures that the LDAP server stores the full user information of multiple operating environments, allowing other software operating environments to obtain incremental user information from the LDAP server, achieving data synchronization across operating environments.

[0063] In this embodiment, a layered validation mechanism effectively avoids system anomalies caused by data errors or irregularities, ensuring the accuracy and integrity of LDAP server data. Format validation ensures standardized data storage and interaction, reducing subsequent processing costs. Business rule validation strengthens system security and compliance, preventing risks such as overreaching permissions. Uniqueness validation avoids data redundancy and improves data retrieval efficiency. Fully automated processing reduces manual intervention, while strict validation logic enhances the system's fault tolerance and stability. Furthermore, it helps each software operating environment obtain accurate and complete incremental user information from the LDAP server, enabling data synchronization across operating environments.

[0064] The technical solution of this embodiment is applied to each software running environment in multiple software running environments, and each software running environment interacts with an LDAP server for data exchange, and the LDAP server includes user information generated by multiple software running environments respectively; by responding to a scheduled task creation operation, the scheduled task configuration information is obtained, wherein the scheduled task configuration information includes executor information, scheduling type, operation mode, task processor and policy information; through the XXL-JOB task scheduling engine, a target scheduled task is generated based on the executor information, scheduling type, operation mode, task processor and policy information; the target scheduled task is started, and the data to be synchronized is obtained from the LDAP server according to the timing rules corresponding to the target scheduled task, and the data to be synchronized is synchronized. This solution interacts with the LDAP server in multiple software runtime environments and uses the XXL-JOB task scheduling engine to implement scheduled task management. This allows for unified management and interaction of user information across multiple runtime environments. The scheduled task mechanism ensures the regularity and automation of data synchronization, avoiding omissions and delays in manual intervention. The comprehensiveness of configuration information makes task generation more flexible and targeted, and can adapt to the scheduling needs of different business scenarios. The introduction of the XXL-JOB engine provides distributed task scheduling capabilities, supports efficient execution and management of tasks in high-concurrency scenarios, and improves system stability and scalability. Based on timing rules, data to be synchronized is obtained and processed from the LDAP server, ensuring the consistency and real-time nature of user information in multiple runtime environments, effectively solving the problem of data silos, providing a solid data foundation for cross-system business collaboration, and effectively improving data synchronization processing efficiency.

[0065] Example 2

[0066] Figure 2 This is a flow chart of a data synchronization processing method provided by the second embodiment of the present invention. The method of this embodiment is a further optimization of the method of the above embodiment. Optionally, a task configuration object that conforms to the preset XXL-JOB specification is constructed based on the executor information, scheduling type, operation mode, task processor and strategy information; the task management interface of the XXL-JOB task scheduling engine is called to persist the task configuration object to the database and generate the target scheduled task. Figure 2 As shown, the method includes:

[0067] S210 . In response to a scheduled task creation operation, obtain scheduled task configuration information, wherein the scheduled task configuration information includes executor information, scheduling type, operation mode, task processor, and policy information.

[0068] S220: Construct a task configuration object that complies with the preset XXL-JOB specification based on the executor information, scheduling type, operation mode, task processor and strategy information.

[0069] Among them, the task configuration object, which conforms to the pre-set XXL-JOB specification, is a parameter encapsulation that follows the standard interfaces and data structures of the XXL-JOB platform and is used to define task scheduling rules and execution logic. This object must contain basic information such as the task ID, executor group, and CRON expression, as well as enhanced parameters such as failure retry strategy and task timeout settings. It also associates specific business logic by implementing designated interfaces (such as IJobHandler) or through annotations, ensuring that the scheduling center can uniformly parse and trigger tasks, achieving standardized management in a distributed environment. The XXL-JOB specification is a standardized distributed task scheduling solution designed to simplify task management and execution. Its core components include the scheduling center (a unified platform for task registration, triggering, and monitoring), executors (service nodes that host business logic), and task configuration (a set of parameters that define execution rules). The specification covers at least the following aspects: 1) Tasks must implement the IJobHandler interface and be registered through annotations; 2) support CRON expressions or fixed-frequency scheduling; 3) provide failure retry, timeout control, and blocking handling strategies; and 4) integrate log storage and alerting mechanisms. By following this specification, you can quickly build a highly available and easy-to-maintain distributed task scheduling system.

[0070] Specifically, by creating a task handler class that implements the XXL-JOB specified interface (such as IJobHandler), the specific business logic is encapsulated. Then, the target execution environment is located through executor information (such as executor group name and address). The trigger rules are defined in combination with the scheduling type (such as CRON expression, fixed rate), and the operation mode (such as BEAN mode or GLUE mode) is selected to determine the task loading method. Finally, the policy parameters (such as the number of failed retries and routing strategy) are configured. This information is verified for validity according to the preset configuration information verification rules. Once the verification passes, the various parameters are filled into the corresponding fields according to the data structure of the task configuration object in the XXL-JOB specification (such as the attribute requirements of the JobInfo class), completing the construction of the task configuration object.

[0071] In this embodiment, a task configuration object that complies with the XXL-JOB specification is constructed based on the configured scheduled task configuration information to ensure that the task configuration strictly follows the XXL-JOB specification, achieves seamless docking with the scheduling engine, and improves system compatibility; parameterized configuration makes task definitions flexible and reusable, and when business requirements change, only the configuration parameters need to be adjusted for rapid adaptation; the legality verification mechanism avoids incorrect configurations from the source, reduces task runtime exceptions, and ensures system stability; the modular configuration structure separates and manages information such as executors and scheduling rules, greatly facilitating later maintenance and function expansion; the constructed standardized task configuration object supports visual management and persistent storage, which facilitates monitoring and tracing of the entire life cycle of tasks, and significantly improves the management efficiency of task scheduling.

[0072] S230: Call the task management interface of the XXL-JOB task scheduling engine, persist the task configuration object to the database, and generate the target scheduled task.

[0073] Specifically, after constructing a task configuration object (such as JobInfo) that conforms to the XXL-JOB specification, call the task management interface provided by XXL-JOB (such as JobInfoService.add()) and pass the configuration object as a parameter. The interface maps the configuration information into SQL statements through an ORM framework (such as MyBatis) and persistently stores it in a database table preset by XXL-JOB (such as xxl_job_info), including key information such as the executor ID, scheduling strategy, and task processor. After the database operation is successful, the task configuration is assigned a unique identifier (such as an auto-increment ID). The scheduling engine automatically detects the new task and registers it to the in-memory scheduling queue. It triggers execution according to the preset timing rules (such as CRON expressions), completing the creation of the target scheduled task.

[0074] In this embodiment, unified management of task configuration is achieved through standardized interfaces, avoiding the complexity and risks of manual database operations; database persistence ensures permanent storage of task configuration and supports automatic restoration of scheduling status after system restart; the unique identification mechanism facilitates subsequent operations such as querying, modifying, and deleting tasks, thereby improving management efficiency; the automatic registration mechanism simplifies the task launch process and reduces operation and maintenance costs; at the same time, the centralized storage of task configuration provides the system with a complete task list, facilitating unified monitoring and auditing, and enhancing the observability and reliability of the system.

[0075] S240: Start the target scheduled task, obtain the data to be synchronized from the LDAP server according to the timing rule corresponding to the target scheduled task, and synchronize the data to be synchronized.

[0076] The technical solution of this embodiment obtains scheduled task configuration information in response to a scheduled task creation operation, wherein the scheduled task configuration information includes executor information, scheduling type, operation mode, task processor and policy information; constructs a task configuration object that conforms to the preset XXL-JOB specification based on the executor information, scheduling type, operation mode, task processor and policy information; calls the task management interface of the XXL-JOB task scheduling engine, persists the task configuration object to the database, and generates a target scheduled task; starts the target scheduled task, obtains the data to be synchronized from the LDAP server according to the timing rules corresponding to the target scheduled task, and synchronizes the data to be synchronized. This solution achieves full-link closed-loop management of scheduled tasks from creation to execution through standardized configuration and automated scheduling. Task configuration objects are constructed with the help of XXL-JOB specifications to ensure the standardization and reusability of task definitions and improve system compatibility. Database persistent storage ensures the permanence and traceability of task configurations and supports automatic resumption of scheduling after system restart. The automated startup mechanism simplifies the task launch process and reduces operation and maintenance costs. Data synchronization processing based on LDAP servers enables scheduled data updates and synchronizes processing across software operating environments, enhancing the real-time and accuracy of data in each software operating environment. Automated execution of the entire process reduces manual intervention and improves task execution efficiency. At the same time, centralized task management and monitoring improve the maintainability and reliability of the system.

[0077] Example 3

[0078] Figure 3 It is a structural diagram of a data synchronization processing device provided in the third embodiment of the present invention.

[0079] like Figure 3 As shown, the device includes:

[0080] The scheduled task configuration information acquisition module 310 is used to obtain the scheduled task configuration information in response to the scheduled task creation operation, wherein the scheduled task configuration information includes executor information, scheduling type, operation mode, task processor and policy information;

[0081] The target scheduled task generation module 320 is used to generate the target scheduled task based on the executor information, scheduling type, operation mode, task processor and strategy information through the XXL-JOB task scheduling engine;

[0082] The data synchronization processing module 330 is used to start the target scheduled task, obtain the data to be synchronized from the LDAP server according to the timing rule corresponding to the target scheduled task, and perform synchronization processing on the data to be synchronized.

[0083] The technical scheme of the embodiment, through the timing task configuration information acquisition module, in response to the timing task creation operation, the timing task configuration information is acquired, wherein the timing task configuration information includes executor information, scheduling type, running mode, task processor and strategy information; the target timing task generation module generates the target timing task through the XXL-JOB task scheduling engine based on the executor information, the scheduling type, the running mode, the task processor and the strategy information; the data synchronization processing module starts the target timing task, acquires the to-be-synchronized data from the LDAP server according to the timing rule corresponding to the target timing task, and synchronously processes the to-be-synchronized data. The scheme can realize the unified management and interaction of user information across running environments by respectively interacting with the LDAP server in multiple software running environments and utilizing the XXL-JOB task scheduling engine to implement timing task management, ensures the regularity and automation of data synchronization through the timing task mechanism, avoids the omissions and delays of manual intervention, the comprehensiveness of the configuration information makes the task generation more flexible and targeted, and can adapt to the scheduling requirements of different business scenarios; the introduction of the XXL-JOB engine provides distributed task scheduling capability, supports efficient task execution and management in a high-concurrency scenario, and improves system stability and scalability; the to-be-synchronized data is acquired from the LDAP server based on the timing rule and processed, which guarantees the consistency and real-time performance of user information in multiple environments, effectively solves the data island problem, provides a solid data foundation for cross-system business collaboration, and effectively improves the data synchronization processing efficiency.

[0084] On the basis of the above-mentioned embodiments, optionally, before acquiring the timing task configuration information in response to the timing task creation operation, the apparatus is further configured to register an event listener of the timing task creation operation; the event listener is used to monitor the timing task creation operation in real time, and when the timing task creation operation is detected, the acquisition process of the timing task configuration information is triggered.

[0085] Optionally, the target timing task generation module 320 is specifically configured to construct a task configuration object conforming to a preset XXL-JOB specification based on the executor information, the scheduling type, the running mode, the task processor and the strategy information; and call a task management interface of the XXL-JOB task scheduling engine to persist the task configuration object to a database, and generate the target timing task.

[0086] Optionally, after acquiring the timing task configuration information, the apparatus is further configured to call a mapping relationship between the configuration information and the verifiers, match each configuration item in the timing task configuration information with the mapping relationship, determine the verifiers corresponding to each configuration item in the timing task configuration information, and bind each configuration item with the corresponding verifier; verify the corresponding configuration item based on the verifier corresponding to the configuration item, and obtain the verification result corresponding to each configuration item; and in a case where the verification result corresponding to each configuration item meets a preset condition, perform the generation processing of the target timing task.

[0087] Optionally, the device is also used to, upon receiving a user information change request, determine the user information to be changed based on the user information change request; perform verification processing on the user information to be changed, and transmit the user information to be changed that has successfully been verified to the LDAP server to update the user information in the LDAP server, wherein the verification processing includes at least format verification processing, business rule verification processing and uniqueness verification processing.

[0088] Optionally, the data to be synchronized includes at least one incremental user information; the data synchronization processing module 330 is specifically used to search the target database for any incremental user information based on the user name and user email in the incremental user information; if the same user name and user email are retrieved, the corresponding data in the target database is updated based on the incremental user information; if the same user name and user email are not retrieved, a new record is created and the data in the incremental user information is filled into the new record until each incremental user information is stored in the target database.

[0089] The data synchronization processing device provided in the embodiment of the present invention can execute the data synchronization processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0090] Example 4

[0091] Figure 4 1 is a structural diagram of an electronic device provided in Embodiment 4 of the present invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0092] like Figure 4As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., which is communicatively connected to the at least one processor 11. The memory stores a computer program that can be executed by the at least one processor. The processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 into the random access memory (RAM) 13. Various programs and data required for the operation of the electronic device 10 can also be stored in the RAM 13. The processor 11, ROM 12, and RAM 13 are connected to each other via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0093] Multiple components in the electronic device 10 are connected to the I / O interface 15, including an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a magnetic disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0094] The processor 11 can be any general-purpose and / or specialized processing component with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various processors that run machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as the data synchronization processing method.

[0095] In some embodiments, the data synchronization processing method can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the data synchronization processing method described above can be performed. Alternatively, in other embodiments, the processor 11 can be configured to perform the data synchronization processing method in any other appropriate manner (for example, by means of firmware).

[0096] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0097] Computer programs for implementing the data synchronization processing method of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when executed by the processor, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The computer programs can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0098] Example 5

[0099] Embodiment 5 of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to cause a processor to execute a data synchronization processing method, the method comprising:

[0100] In response to the scheduled task creation operation, obtaining scheduled task configuration information, wherein the scheduled task configuration information includes executor information, scheduling type, operation mode, task processor and policy information;

[0101] Generate target scheduled tasks based on executor information, scheduling type, operation mode, task processor and strategy information through the XXL-JOB task scheduling engine;

[0102] Start the target scheduled task, obtain the data to be synchronized from the LDAP server according to the timing rules corresponding to the target scheduled task, and synchronize the data to be synchronized.

[0103] In the context of the present invention, computer-readable storage media can be tangible media that can contain or store a computer program for use with an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. Computer-readable storage media can include but are not limited to electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, computer-readable storage media can be machine-readable signal media. More specific examples of machine-readable storage media can include electrical connections based on one or more lines, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0104] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0105] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0106] The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system, to solve the defects of large management difficulty and weak business scalability in traditional physical host and VPS service.

[0107] It should be understood that the various forms of flow shown above can be used to reorder, add or delete steps. For example, each step described in the present application can be executed in parallel, sequentially or in a different order, as long as the desired results of the technical solutions of the present application can be achieved, which is not limited herein.

[0108] The above detailed description does not constitute a limitation on the scope of protection of the present application. Those skilled in the art should understand that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A data synchronization processing method, characterized in that: Applied to each of the multiple software running environments, each of the software running environments respectively exchanges data with an LDAP server, and the LDAP server includes user information generated by the multiple software running environments respectively; The method comprises: In response to a scheduled task creation operation, obtaining scheduled task configuration information, wherein the scheduled task configuration information includes executor information, scheduling type, operation mode, task processor, and policy information; Generate a target scheduled task based on the executor information, the scheduling type, the operating mode, the task processor and the strategy information through the XXL-JOB task scheduling engine; The target scheduled task is started, the data to be synchronized is obtained from the LDAP server according to the timing rule corresponding to the target scheduled task, and synchronization processing is performed on the data to be synchronized.

2. The method according to claim 1, characterized in that Before obtaining the scheduled task configuration information in response to the scheduled task creation operation, the method further includes: Register an event listener for the scheduled task creation operation; The scheduled task creation operation is monitored in real time by the event listener, and when the scheduled task creation operation is detected, a process for obtaining the scheduled task configuration information is triggered.

3. The method according to claim 1, characterized in that The task scheduling engine of XXL-JOB generates the target scheduled task based on the executor information, the scheduling type, the operation mode, the task processor and the strategy information, including: Constructing a task configuration object that complies with a preset XXL-JOB specification based on the executor information, the scheduling type, the operating mode, the task processor, and the strategy information; Call the task management interface of the XXL-JOB task scheduling engine, persist the task configuration object to the database, and generate the target scheduled task.

4. The method according to claim 1, wherein After obtaining the scheduled task configuration information, the method further includes: Calling the mapping relationship between configuration information and verifiers, matching each configuration item in the scheduled task configuration information with the mapping relationship, determining the verifier corresponding to each configuration item in the scheduled task configuration information, and binding each configuration item to the corresponding verifier; Verify the corresponding configuration item based on the verifier corresponding to each of the configuration items, and obtain the verification result corresponding to each of the configuration items; When the verification results corresponding to the configuration items meet the preset conditions, the generation process of the target scheduled task is executed.

5. The method according to claim 1, wherein The method also includes: Upon receiving a user information change request, determining user information to be changed based on the user information change request; The user information to be changed is verified and transmitted to the LDAP server to update the user information in the LDAP server, wherein the verification process at least includes format verification, business rule verification and uniqueness verification.

6. The method according to claim 1, characterized in that The data to be synchronized includes at least one incremental user information; and the synchronizing processing of the data to be synchronized includes: For any incremental user information, a search is performed in the target database based on the user name and user email address in the incremental user information. If the same user name and user email address are retrieved, the corresponding data in the target database is updated based on the incremental user information. If the same user name and user email address are not retrieved, a new record is created and the data in the incremental user information is filled into the new record until all the incremental user information is stored in the target database.

7. A data synchronization processing device, characterized in that: include: A scheduled task configuration information acquisition module is used to obtain scheduled task configuration information in response to a scheduled task creation operation, wherein the scheduled task configuration information includes executor information, scheduling type, operation mode, task processor and policy information; A target scheduled task generation module is used to generate a target scheduled task based on the executor information, the scheduling type, the operation mode, the task processor and the strategy information through the XXL-JOB task scheduling engine; The data synchronization processing module is used to start the target scheduled task, obtain the data to be synchronized from the LDAP server according to the timing rule corresponding to the target scheduled task, and perform synchronization processing on the data to be synchronized.

8. An electronic device, characterized in that: The electronic device comprises: 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. The computer program is executed by the at least one processor to enable the at least one processor to perform the data synchronization processing method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the data synchronization processing method according to any one of claims 1 to 6 when executed.

10. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the computer program implements the data synchronization processing method according to any one of claims 1 to 6.

Images