Data synchronization method and device

By modifying the service data attributes synchronized by the sending end in the data management system, the problem of data attributes not being supported in the dual-end system is solved, reducing the coupling and invasiveness of the sending end, and supporting synchronization after changes in the service data.

CN119003650AActive Publication Date: 2024-11-22QI AN XIN TECHNOLOGY GROUP INC
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202410866671.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-06-28
Publication Date
2024-11-22
Estimated Expiration
2044-06-28

AI Technical Summary

Technical Problem

In the prior art, due to different data control mechanisms, the service data attributes synchronized by the sending end to the receiving end cannot be supported. The code needs to be modified integrated on the sending end, resulting in strong coupling and high invasiveness, making it difficult to cope with changes in business data. .

Method used

By presetting configuration information in the data management system, the service data attributes synchronized by the sending end to the receiving end are determined and modified to make it conform to the support format of the receiving end, thereby reducing the coupling of the sending end and updating the configuration information without modification when the service data changes Send code.

Benefits of technology

It realizes synchronizing the service data attributes supported by the receiver without integrating and modifying the code at the sending end, reducing the coupling between data synchronization and the sending end, and supporting synchronization after changes in service data, reducing invasiveness to the sending end.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119003650A_ABST
    Figure CN119003650A_ABST
Patent Text Reader

Abstract

The invention discloses a data synchronization method and device, relates to the technical field of data synchronization, and mainly aims to reduce the coupling between data synchronization and a sending end. According to the main technical scheme, the data management system is associated with a sending end and a receiving end, and configuration information corresponding to at least one kind of service data is preset in the data management system; the configuration information is used for indicating that first attribute data of service data synchronized to the receiving end by the sending end is modified into second attribute data supported by the receiving end; determining target service data synchronized to the receiving end by the sending end; obtaining target configuration information corresponding to the target business data from preset configuration information; and modifying the first attribute data of the target service data into second attribute data supported by the receiving end based on the target configuration information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of data synchronization, and in particular to a data synchronization method and device. Background Art

[0002] The two ends of a two-end system usually have different data control mechanisms, which causes some attribute data (such as business identification) in the business data synchronized from one end (i.e., the sending end) to the other end (i.e., the receiving end) to not be supported by the receiving end. Therefore, these attribute data need to be modified to be supported by the receiving end to ensure that the receiving end can process and use the business data normally.

[0003] At present, the code for modifying attribute data is usually integrated at the sending end, so that before synchronizing the business data from the sending end to the receiving end, the attribute data in the business data that is not supported by the receiving end is first modified to be supported by the receiving end based on the code, and then the modified business data is synchronized to the receiving end. However, this method of integrating code at the sending end is highly coupled with the sending end. If the business data that needs to be synchronized between the sending end and the receiving end changes, the code integrated at the sending end needs to be modified, which is highly invasive to the sending end. Summary of the invention

[0004] In view of this, the present application proposes a data synchronization method and device, the main purpose of which is to reduce the coupling between data synchronization and the sending end.

[0005] In order to achieve the above objectives, this application mainly provides the following technical solutions:

[0006] In the first aspect, the present application provides a data synchronization method, which is applied to a data management system, wherein the data management system is associated with a sending end and a receiving end, and the data management system is preset with configuration information corresponding to at least one business data, and the configuration information is used to indicate that the first attribute data of the business data synchronized from the sending end to the receiving end is modified to the second attribute data supported by the receiving end. The data synchronization method includes: determining the target business data synchronized from the sending end to the receiving end; obtaining the target configuration information corresponding to the target business data from the preset configuration information; and modifying the first attribute data of the target business data to the second attribute data supported by the receiving end based on the target configuration information.

[0007] In some embodiments of the present application, the configuration information is also used to indicate enrichment of third attribute data from the business data, and the third attribute data is the data required to determine the second attribute data supported by the receiving end. Then, based on the target configuration information, the first attribute data of the target business data is modified to the second attribute data supported by the receiving end, including: based on the target configuration information, enriching the third attribute data from the target business data; based on the third attribute data, determining the second attribute data supported by the receiving end; and modifying the first attribute data of the target business data to the second attribute data.

[0008] In some embodiments of the present application, the data management system stores at least one second attribute data corresponding to a third attribute data. Then, based on the third attribute data, determining the second attribute data supported by the receiving end includes: searching for the second attribute data corresponding to the third attribute data in the data management system; and determining the found second attribute data as the second attribute data supported by the receiving end.

[0009] In some embodiments of the present application, the data synchronization method further includes: if the second attribute data corresponding to the third attribute data is not found in the data management system, performing any of the following operations: calling the corresponding attribute data generation interface of the receiving end to generate the second attribute data supported by the receiving end for the target business data based on the third attribute data;

[0010] or, detecting whether there is third attribute data associated with the third attribute data in the data management system, and the associated third attribute data has corresponding second attribute data, and if so, determining the second attribute data corresponding to the associated third attribute data as the second attribute data supported by the receiving end;

[0011] Or, a prompt is issued that the synchronization of the target business data has failed.

[0012] In some embodiments of the present application, the configuration information includes at least one attribute item, and the attribute data corresponding to the at least one attribute item in the business data is the data required to determine the second attribute data supported by the receiving end. Then, based on the target configuration information, third attribute data is enriched from the target business data, including: based on the target configuration information, extracting the attribute data corresponding to the at least one attribute item from the target business data; enriching the extracted attribute data into the third attribute data.

[0013] In some embodiments of the present application, the first attribute data and the second attribute data are business identifiers for uniquely identifying the business meaning of the business data, and the third attribute data is attribute data for describing the business meaning of the business data.

[0014] In some embodiments of the present application, the data synchronization method also includes: if the target configuration information of the target business data is not obtained from the preset configuration information, customizing corresponding target configuration information for the target business data, and adding the target configuration information to the preset configuration information.

[0015] In some embodiments of the present application, corresponding target configuration information is customized for the target business data, including: issuing a configuration information customization prompt for the target business data; if customized configuration information for the customized prompt is received, customizing the customized configuration information to the target configuration information corresponding to the target business data; if customized configuration information for the customized prompt is not received within the target time period, or feedback rejecting customization is received, preventing the target business data from being synchronized to the receiving end, or allowing the target business data to be synchronized to the receiving end and issuing a target prompt to the receiving end, the target prompt is used to prompt that the first attribute data of the target business data cannot be modified to the second attribute data supported by the receiving end.

[0016] In some embodiments of the present application, the data synchronization method further includes: detecting whether a business data type of the business data that needs to be synchronized between the sending end and the receiving end changes; if a change occurs, updating the preset configuration information.

[0017] In some embodiments of the present application, the preset configuration information is updated, including: if there is a new business data type after the change, identifying the first attribute data that is not supported by the receiving end in the business data of the new business data type, and setting the corresponding configuration information of the business data of the new business data type based on the unsupported first attribute data, and adding the corresponding configuration information to the preset configuration information.

[0018] In some embodiments of the present application, the sending end and the receiving end use different attribute data to uniquely identify business data with the same business meaning. Then, identifying the first attribute data in the business data of the newly added business data type that is not supported by the receiving end includes: searching for attribute data for uniquely identifying the business meaning of the business data of the newly added business data type in the business data of the newly added business data type; and identifying the found attribute data as the first attribute data in the business data of the newly added business data type that is not supported by the receiving end.

[0019] In a second aspect, the present application provides a data synchronization device, which is applied to a data management system, the data management system is associated with a sending end and a receiving end, the data management system is preset with configuration information corresponding to at least one business data, the configuration information is used to indicate that the first attribute data of the business data synchronized from the sending end to the receiving end is modified to the second attribute data supported by the receiving end, the data synchronization device includes:

[0020] A determination module, used to determine the target service data synchronized from the sending end to the receiving end;

[0021] An acquisition module, used to acquire target configuration information corresponding to the target business data from preset configuration information;

[0022] A modification module is used to modify the first attribute data of the target service data to second attribute data supported by the receiving end based on the target configuration information.

[0023] In a third aspect, the present application provides a computer-readable storage medium, wherein the storage medium includes a stored program, wherein when the program is executed, the device where the storage medium is located is controlled to execute the data synchronization method described in the first aspect.

[0024] In a fourth aspect, the present application provides an electronic device, comprising: a memory for storing a program; and a processor, coupled to the memory, for running the program to execute the data synchronization method described in the first aspect.

[0025] The data synchronization method and device provided by the present application preset configuration information corresponding to at least one business data in the data management system, and the configuration information is used to indicate that the first attribute data of the business data synchronized from the sender to the receiver is modified to the second attribute data supported by the receiver. When the sender synchronizes the target business data to the receiver, the target configuration information corresponding to the target business data is obtained from the preset configuration information, and the first attribute data of the target business data is modified to the second attribute data supported by the receiver based on the target configuration information. In this way, there is no need to integrate the code for modifying the attribute data at the sender. By obtaining the preset configuration information in the data management system, the first attribute data of the business data synchronized from the sender to the receiver can be modified to the second attribute data supported by the receiver, thereby ensuring that the receiver can normally use and process the business data synchronized from the sender, while reducing the coupling between the data synchronization and the sender. In addition, even if the business data that needs to be synchronized between the sender and the receiver changes, based on the changes that occur, the configuration information preset in the data management system is updated, so that the sender can synchronize the changed business data to the receiver. The whole process does not require the code of the sender to be modified, and is non-invasive to the sender.

[0026] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0028] Figure 1 A flow chart of a data synchronization method provided by an embodiment of the present application is shown;

[0029] Figure 2 A schematic diagram of the structure of a data synchronization device provided by an embodiment of the present application is shown;

[0030] Figure 3 A structural schematic diagram of a data synchronization device provided in another embodiment of the present application is shown. DETAILED DESCRIPTION

[0031] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0032] In some scenarios, one end (i.e., the sending end) of a two-end system will synchronize data to the other end (i.e., the receiving end) so that the other end can perform corresponding business processing based on the synchronized business data. However, the two ends in a two-end system usually have different data management mechanisms, and some attribute data (e.g., business identifier) ​​of the business data synchronized by the sending end to the receiving end cannot be supported by the receiving end. Therefore, in order to enable the receiving end to normally process and use the business data synchronized by the sending end, the code for modifying the attribute data is usually integrated at the sending end, so that before the sending end synchronizes the business data to the receiving end, the attribute data in the business data that is not supported by the receiving end is first modified to be supported by the receiving end based on the code, and then the modified business data is synchronized to the receiving end. However, although this method of integrating the code at the sending end can ensure that the receiving end correctly uses and processes the business data synchronized by the sending end, it is highly coupled with the sending end. If the business data that needs to be synchronized between the sending end and the receiving end changes, it is bound to be necessary to modify the code integrated by the sending end, which is highly invasive to the sending end.

[0033] After research, it is found that if a data management system is provided, the data management system presets configuration information corresponding to at least one type of business data, and the configuration information is used to indicate that the first attribute data of the business data synchronized from the sender to the receiver is modified to the second attribute data supported by the receiver, then when there is target business data synchronized from the sender to the receiver, the target configuration information corresponding to the target business data can be obtained from the preset configuration information, and the first attribute data of the target business data can be modified to the second attribute data supported by the receiver based on the target configuration information. In this way, there is no need to integrate the code for modifying the attribute data at the sender, and by obtaining the preset configuration information in the data management system, the first attribute data of the business data synchronized from the sender to the receiver can be modified to the second attribute data supported by the receiver, thereby ensuring that the receiver can normally use and process the business data synchronized from the sender, while reducing the coupling between data synchronization and the sender. In addition, even if the business data that needs to be synchronized between the sender and the receiver changes, the configuration information preset by the data management system is updated based on the change, so that the sender can synchronize the changed business data to the receiver, and the whole process does not need to modify the code of the sender, and is non-invasive to the sender.

[0034] Based on the above findings, this embodiment proposes a technical solution for data synchronization, specifically: a data management system is associated with a sending end and a receiving end, and the data management system is preset with configuration information corresponding to at least one business data, and the configuration information is used to indicate that the first attribute data of the business data synchronized from the sending end to the receiving end is modified to the second attribute data supported by the receiving end. Determine the target business data that the sending end synchronizes to the receiving end. From the preset configuration information, obtain the target configuration information corresponding to the target business data, and based on the target configuration information, modify the first attribute data of the target business data to the second attribute data supported by the receiving end.

[0035] The technical solution for data synchronization provided in this embodiment can realize data synchronization between the sending end and the receiving end in any two-end system, and reduce the decoupling of data synchronization from the sending end. This embodiment does not limit the specific type of the two-end system.

[0036] Based on the above technical solution for data synchronization, this embodiment specifically provides a data synchronization method and device. The data synchronization method and device provided by this embodiment are specifically described below.

[0037] The embodiment of the present application provides a data synchronization method, which is applied to a data management system, the data management system is associated with a sending end and a receiving end, and the data management system is preset with configuration information corresponding to at least one service data, and the configuration information is used to indicate that the first attribute data of the service data synchronized from the sending end to the receiving end is modified to the second attribute data supported by the receiving end. Figure 1 As shown, the data synchronization method mainly includes the following steps 101 to 103:

[0038] 101. Determine target business data that is synchronized from a sending end to a receiving end.

[0039] The sending end and the receiving end usually have different data management and control systems, which results in that the first attribute data in the business data synchronized from the sending end to the receiving end cannot be supported by the receiving end. In this embodiment, the sending end and the receiving end are associated with the data management system so as to modify the first attribute data of the business data synchronized from the sending end to the receiving end to the second attribute data supported by the receiving end through the data management system. The first attribute data and the second attribute data can be set based on business needs, and this embodiment does not specifically limit the first attribute data and the second attribute data. Exemplarily, the first attribute data and the second attribute data are both attribute data (for example, business identification) that uniquely identify the business meaning of the business data, and the first attribute data can be supported by the sending end but not by the receiving end, while the second attribute data can be supported by the receiving end. For example, the first attribute data of business data 1 is ID123, and the second attribute data is ID456, and the second attribute data ID456 is the attribute data supported by the receiving end.

[0040] The sending end and the receiving end are the two ends of a two-end system, and the sending end and the receiving end are defined based on the initiator of the synchronization data in the two-end system. For example, the two-end system includes a production end and a consumption end. When the production end synchronizes data to the consumption end, the production end is the sending end and the consumption end is the receiving end. When the consumption end synchronizes data to the production end, the consumption end is the sending end and the production end is the receiving end. In addition, the sending end and the receiving end can be deployed in different network domains or in the same network domain, which is not specifically limited in this embodiment.

[0041] When the data management system realizes data synchronization between the sender and the receiver, it first needs to determine the target business data that the sender synchronizes to the receiver. The methods for determining the target business data that the sender synchronizes to the receiver can include the following three methods:

[0042] First, when the sending end synchronizes business data to the receiving end, it issues a first synchronization prompt for the business data. The first synchronization prompt is used to indicate the business data that the sending end synchronizes to the receiving end. Then, the specific process of determining the target business data that the sending end synchronizes to the receiving end may include: detecting whether there is a first synchronization prompt, and if so, determining the business data indicated by the first synchronization prompt as the target business data that the sending end synchronizes to the receiving end.

[0043] For this method, the data management system can modify the target business data at any of the following times: First, before the receiving end synchronizes the business data to the receiving end, the data management system modifies the first attribute data of the target business data to the second attribute data supported by the receiving end, and then the sending end synchronizes the modified target business data to the receiving end. Second, after the receiving end receives the target business data synchronized by the sending end, the data management system modifies the first attribute data of the target business data to the second attribute data supported by the receiving end. Third, the data management system intercepts the target business data during the process of synchronizing the target business data to the receiving end, modifies the first attribute data of the intercepted target business data to the second attribute data supported by the receiving end, and then releases the modified target business data for synchronization to the receiving end.

[0044] Second, when the receiving end receives the business data synchronized by the sending end, it issues a second synchronization prompt for the business data, and the second synchronization prompt is used to indicate the business data received by the receiving end. Then, the specific process of determining the target business data synchronized from the sending end to the receiving end may include: detecting whether there is a second synchronization prompt, and if so, determining the business data indicated by the second synchronization prompt as the target business data synchronized from the sending end to the receiving end.

[0045] For this method, the data management system can modify the target service data at the following times: after the receiving end receives the target service data synchronized from the sending end, the data management system modifies the first attribute data of the target service data into the second attribute data supported by the receiving end.

[0046] Third, the specific process of determining the target business data synchronized from the sender to the receiver may include: detecting whether the data synchronization channel between the sender and the receiver transmits business data; if so, determining the corresponding business data as the target business data synchronized from the sender to the receiver.

[0047] For this method, the data management system can modify the target business data at any of the following times: First, after the data management system receives the target business data synchronized by the sending end at the receiving end, it modifies the first attribute data of the target business data to the second attribute data supported by the receiving end. Second, the data management system intercepts the target business data during the process of synchronizing the target business data to the receiving end, modifies the first attribute data of the intercepted target business data to the second attribute data supported by the receiving end, and then releases the modified target business data to be synchronized to the receiving end.

[0048] The above three methods for determining the target service data synchronized from the sending end to the receiving end can be flexibly selected based on service needs, and this embodiment does not make any specific limitations on this.

[0049] 102. Obtain target configuration information corresponding to the target business data from preset configuration information.

[0050] After determining the target service data synchronized from the sending end to the receiving end, it is necessary to obtain the target configuration information corresponding to the target service data from the preset configuration information, so as to modify the first attribute data of the target service data to the second attribute data supported by the receiving end based on the target configuration information.

[0051] Furthermore, the configuration information in the data management system may not be preset comprehensively, which may result in some business data not having corresponding target configuration information in the data management system. In order to be able to modify the first attribute data of these business data to the second attribute data supported by the receiving end, the data synchronization method provided in this embodiment may also include the following steps: If the target configuration information of the target business data is not obtained from the preset configuration information, the corresponding target configuration information is customized for the target business data, and the target configuration information is added to the preset configuration information.

[0052] If the target configuration information of the target business data is not obtained from the preset configuration information, it means that the data management system has not modified the first attribute data of the target business data to the modification basis of the second attribute data supported by the receiving end. Therefore, in order to obtain the modification basis, that is, the target configuration information of the target business data, it is necessary to customize the corresponding target configuration information for the target business data.

[0053] The methods for customizing corresponding target configuration information for target business data may include the following two methods:

[0054] The first one is to customize the corresponding target configuration information for the target business data, including: issuing a configuration information customization prompt for the target business data. If customized configuration information for the customization prompt is received, the customized configuration information is customized to the target configuration information corresponding to the target business data. If customized configuration information for the customization prompt is not received within the target time, or feedback of rejecting customization is received, any of the following operations is performed: first, preventing the target business data from being synchronized to the receiving end; second, allowing the target business data to be synchronized to the receiving end and issuing a target prompt to the receiving end.

[0055] The purpose of issuing a configuration information customization prompt for target business data is to enable the user to know, based on the customization prompt, that corresponding target configuration information needs to be customized for the target business data.

[0056] If customized configuration information for the customization prompt is received, it means that the customized configuration information is the target configuration information customized by the user for the target business data, so the customized configuration information is customized to the target configuration information corresponding to the target business data.

[0057] If no customized configuration information for the customized prompt is received within the target duration, or feedback of rejecting customization is received, it means that the user may not be willing to customize the target configuration information for the target business data. At this time, any of the following operations can be adopted: First, prevent the target business data from being synchronized to the receiving end. Since the target business data does not have the corresponding target configuration information, the first attribute information of the target business data cannot be modified to the second attribute data supported by the receiving end. Even if the target business data is synchronized to the receiving end, the receiving end cannot use and process the business data normally, so the target business data is prevented from being synchronized to the receiving end. In addition, a prompt that the target business data cannot be synchronized to the receiving end normally can be issued, so that the receiving end can handle the exception based on the prompt. Second, release the target business data to be synchronized to the receiving end and issue a target prompt to the receiving end. The target prompt is used to prompt that the first attribute data of the target business data cannot be modified to the second attribute data supported by the receiving end. Through the target prompt, the fact that the first attribute data of the target business data cannot currently be modified to the second attribute data supported by the receiving end is prompted, so that the receiving end temporarily does not use and process the target business data based on the target prompt.

[0058] The second type is that the sending end and the receiving end use different attribute data to uniquely identify the business data with the same business meaning. Then, the specific process of customizing the corresponding target configuration information for the target business data includes: determining the attribute data (for example, the business identifier) ​​in the target business data that uniquely identifies the business meaning of the target business data, determining the determined attribute data as the first attribute data in the target business data that is not supported by the receiving end, setting configuration information for indicating that the first attribute data of the target business data is modified to the second attribute data supported by the receiving end, and customizing the set configuration information as the target configuration information corresponding to the target business data.

[0059] The above two methods of customizing the corresponding target configuration information for the target business data can be used separately or in combination, and this embodiment does not limit this. Exemplarily, when used in combination, the first method can be used first, and if no customized configuration information for the customization prompt is received within the target time after executing the first method, or feedback of rejecting customization is received, the second method is continued.

[0060] After customizing the corresponding target configuration information for the target business data, add the target configuration information to the preset configuration information so that when the subsequent sender needs to synchronize business data of the same business type as the target business data again, it can directly obtain the corresponding target configuration information from the preset configuration information for use.

[0061] 103. Modify the first attribute data of the target service data to second attribute data supported by the receiving end based on the target configuration information.

[0062] The target configuration information is a modification basis for modifying the first attribute data of the target service data to the second attribute data supported by the receiving end. Therefore, after obtaining the target configuration information, a step of modifying the first attribute data of the target service data to the second attribute data supported by the receiving end based on the target configuration information is performed. The specific execution process of this step may include the following steps 103A to 103C:

[0063] 103A. Based on the target configuration information, third attribute data is enriched from the target business data.

[0064] The configuration information is also used to indicate enriching the third attribute data from the service data, and the third attribute data is the data required to determine the second attribute data supported by the receiving end. Therefore, in order to determine the second attribute data supported by the receiving end, it is necessary to enrich the third attribute data from the target service data based on the target configuration information.

[0065] The configuration information includes at least one attribute item, and the corresponding attribute data of the at least one attribute item in the business data is the data required to determine the second attribute data supported by the receiving end. That is, the configuration information indicates the enrichment of the third attribute data from the business data through at least one attribute item. At least one attribute item in the configuration information can be set based on business needs. Exemplarily, the first attribute data and the second attribute data are business identifiers that uniquely identify the business meaning of the business data, then, at least one attribute item should be the corresponding attribute data is the attribute data used to describe the business meaning of the business data, so that the third attribute data can be enriched from the business data based on at least one attribute item, and the third attribute data is the attribute data used to describe the business meaning of the business data.

[0066] The specific process of enriching the third attribute data from the target business data based on the target configuration information may include the following steps: based on the target configuration information, extracting attribute data corresponding to at least one attribute item from the target business data; enriching the extracted attribute data into the third attribute data.

[0067] Exemplarily, the attribute item included in the target configuration information is a name item, and the attribute data corresponding to the name item extracted from the target business data based on the target configuration information is "Zhang San", and Zhang San is used to describe the business meaning of the target business data as "Zhang San's business data", then the attribute data "Zhang San" is enriched into the third attribute data required for determining the second attribute data supported by the receiving end. The process of extracting the attribute data corresponding to the name item from the target business data based on the target configuration information can be: if the storage format of the target business data is Json format, the corresponding extraction tool is JsonPath, and the attribute data corresponding to the name item extracted from the target business data through JsonPath is "Zhang San".

[0068] 103B. Based on the third attribute data, determine the second attribute data supported by the receiving end.

[0069] Based on the third attribute data, the method of determining the second attribute data supported by the receiving end may include the following two methods:

[0070] One is that, based on the third attribute data, the specific process of determining the second attribute data supported by the receiving end may include the following steps: calling the corresponding attribute data generation interface of the receiving end, and generating the second attribute data supported by the receiving end for the target business data based on the third attribute data.

[0071] The attribute data generation interface is preset, and adopts the attribute data generation method specified by the receiving end to generate the interface of the second attribute data supported by the receiving end for the target business data based on the third attribute data.

[0072] Another is that the data management system stores at least one second attribute data corresponding to the third attribute data. Then, based on the third attribute data, the specific process of determining the second attribute data supported by the receiving end may include the following steps: searching for the second attribute data corresponding to the third attribute data in the data management system; and determining the found second attribute data as the second attribute data supported by the receiving end.

[0073] In order to facilitate the rapid generation of the second attribute data used to modify the first attribute data, the data management system stores at least one second attribute data corresponding to the third attribute data, so that when determining the second attribute data, the second attribute data can be directly searched from the data management system based on the third attribute data enriched from the target business data. For example, the data management system stores: the second attribute data "ID456" corresponding to the third attribute data "Zhang San", and the second attribute data "ID556" corresponding to the third attribute data "Li Si".

[0074] After the third attribute data is enriched from the target business data, the second attribute data corresponding to the third attribute data is searched in the data management system. If found, the second attribute data corresponding to the third attribute data is determined as the second attribute data supported by the receiving end.

[0075] Furthermore, considering that the correspondence between the third attribute data and the second attribute data stored in the data management system may not be comprehensive, some third attribute data may not find the corresponding second attribute data in the data management system. Therefore, in order to handle these third attribute data, the data synchronization method may also include the following steps: if the second attribute data corresponding to the third attribute data is not found in the data management system, perform any of the following operations:

[0076] Operation 1: Call the corresponding attribute data generation interface of the receiving end to generate second attribute data supported by the receiving end for the target business data based on the third attribute data.

[0077] The attribute data generation interface is preset, and adopts the attribute data generation method specified by the receiving end to generate the second attribute data supported by the receiving end for the target business data based on the third attribute data. The attribute data generation interface is called to generate the second attribute data supported by the receiving end, so as to modify the first attribute data of the target business data based on the second attribute data.

[0078] Operation 2: Check whether there is third attribute data associated with the third attribute data in the data management system, and the associated third attribute data has corresponding second attribute data. If so, determine the second attribute data corresponding to the associated third attribute data as the second attribute data supported by the receiving end.

[0079] The third attribute data associated with the third attribute data in the data management system can also be used as data required to determine the second attribute data supported by the receiving end. Therefore, it is detected whether there is third attribute data associated with the third attribute data in the data management system, and the associated third attribute data has corresponding second attribute data. If so, the second attribute data corresponding to the associated third attribute data is determined as the second attribute data supported by the receiving end.

[0080] It should be noted that the third attribute data associated with the third attribute data and the third attribute data itself are different data, and both have the same attribute, but the data content, data category, etc. may be the same or different. For example, in the following example, the third attribute data may be a mobile phone number, and the third attribute data associated with the third attribute data may be a person's name.

[0081] Exemplarily, the third attribute data enriched from the target business data is "mobile phone number 1111111111", and there is no corresponding second attribute data for this third attribute data in the data management system. However, the third attribute data "Zhang San" associated with "mobile phone number 1111111111" is stored in the data management system, and "Zhang San" has corresponding second attribute data "ID456". Therefore, the second attribute data "ID456" corresponding to "Zhang San" associated with "mobile phone number 1111111111" is determined as the second attribute data supported by the receiving end.

[0082] Operation 3: Issue a prompt indicating that synchronization of target business data has failed.

[0083] A prompt indicating that synchronization of the target service data has failed is issued to inform the user of the fact that the first attribute data in the target service data cannot be modified to the second attribute data supported by the receiving end.

[0084] The above three operations can be used alone or in combination, and this embodiment does not limit this. For example, operation 2 is used first, and after operation 2 is executed, if it is detected that there is no third attribute data associated with the third attribute data in the data management system, and the associated third attribute data has corresponding second attribute data, then operation 1 is continued.

[0085] 103C. Modify the first attribute data of the target business data into the second attribute data.

[0086] The configuration information includes a target attribute item, and the attribute data corresponding to the target attribute item in the business data is the first attribute data. Therefore, the configuration item indicates through the target attribute item that the first attribute data of the business data synchronized from the sender to the receiver is modified to the second attribute data supported by the receiver. Exemplarily, the sender and the receiver use different business identifiers to uniquely identify business data with the same business meaning. Then, the target attribute item included in the configuration information is the business identifier item, which is used to indicate that the first attribute data of the business data synchronized from the sender to the receiver (i.e., the business identifier of the business data in the sender) is modified to the second attribute data supported by the receiver (i.e., the business identifier of the business data in the receiver).

[0087] When the first attribute data of the target service data is modified to the second attribute data, the first attribute data in the target service data is first determined based on the target configuration item included in the configuration information, and then the first attribute data is modified to the second attribute data supported by the receiving end in a targeted manner. After the first attribute data of the target service data is modified to the second attribute data supported by the receiving end, the receiving end can use and process the target service data normally.

[0088] The data synchronization method provided in this embodiment presets configuration information corresponding to at least one type of business data in the data management system, and the configuration information is used to indicate that the first attribute data of the business data synchronized from the sender to the receiver is modified to the second attribute data supported by the receiver. When the sender synchronizes the target business data to the receiver, the target configuration information corresponding to the target business data is obtained from the preset configuration information, and the first attribute data of the target business data is modified to the second attribute data supported by the receiver based on the target configuration information. In this way, there is no need to integrate the code for modifying the attribute data at the sender. By obtaining the preset configuration information in the data management system, the first attribute data of the business data synchronized from the sender to the receiver can be modified to the second attribute data supported by the receiver, thereby reducing the coupling between data synchronization and the sender while ensuring that the receiver can normally use and process the business data synchronized from the sender. In addition, even if the business data to be synchronized between the sender and the receiver changes, based on the changes, the configuration information preset in the data management system is updated, so that the sender can synchronize the changed business data to the receiver. The whole process does not require the code of the sender to be modified, and is non-invasive to the sender.

[0089] In some embodiments of the present application, in actual production, the business data type of the business data that needs to be synchronized between the sending end and the receiving end may change with the change of the business. In order to enable the data management system to synchronize the business data of the changed business data type in time, the data synchronization method may also include the following steps: detecting whether the business data type of the business data that needs to be synchronized between the sending end and the receiving end has changed; if so, updating the preset configuration information.

[0090] If it is detected that the type of business data that needs to be synchronized between the sender and the receiver has changed, it means that some business data synchronized from the sender to the receiver may no longer be able to modify the first attribute data of the business data to the second attribute data supported by the receiver based on the current preset configuration information of the data management system. Therefore, the preset configuration information needs to be updated.

[0091] The situations for updating the preset configuration information may include the following two situations:

[0092] The first one is that if there is a new business data type after the change, the first attribute data that is not supported by the receiving end in the business data of the new business data type is identified, and based on the unsupported first attribute data, the corresponding configuration information of the business data of the new business data type is set, and the corresponding configuration information is added to the preset configuration information.

[0093] There is no corresponding configuration information for the business data of the newly added business data type in the data management system. Therefore, it is necessary to set corresponding configuration information for the business data of the newly added business data type to modify the first attribute data of the business data to the second attribute data supported by the receiving end based on the set configuration information.

[0094] When setting corresponding configuration information for the service data of the newly added service data type, it is first necessary to identify the first attribute data in the service data of the newly added service data type that is not supported by the receiving end. Considering that the sending end and the receiving end use different attribute data to uniquely identify the service data with the same service meaning, the specific process of identifying the first attribute data in the service data of the newly added service data type that is not supported by the receiving end may include: searching the service data of the newly added service data type for the attribute data (for example, the service identifier) ​​used to uniquely identify the service meaning of the service data of the newly added service data type; and identifying the found attribute data as the first attribute data in the service data of the newly added service data type that is not supported by the receiving end.

[0095] After identifying the first attribute data that is not supported by the receiving end in the service data of the newly added service data type, the configuration information corresponding to the service data of the newly added service data type is set based on the unsupported first attribute data, and the configuration information is used to indicate that the first attribute data of the service data of the newly added service data type is modified to the second attribute data supported by the receiving end. Then the corresponding configuration information is added to the preset configuration information to implement the update of the preset configuration information.

[0096] The second type is, if there is corresponding configuration information in the data management system after the change, and the business data type is no longer synchronized between the sender and the receiver, any of the following operations can be taken at this time: First, delete the corresponding configuration information of the business data type from the data management system to release the storage space of the data management system; second, retain the corresponding configuration information of the business data type in the data management system to prevent the subsequent sender and the receiver from resuming synchronization of the business data of the business data type.

[0097] In some embodiments of the present application, a specific example is used below to illustrate the data synchronization method provided by the present embodiment. The data synchronization method is applied to a data management system. The data management system presets configuration information corresponding to three types of business data, namely, business data corresponding configuration information 1 for business data type 1, business data corresponding configuration information 2 for business data type 2, and business data corresponding configuration information 3 for business data type 3. The data management system can store the preset configuration information in the same file to record the preset configuration information through the same file. The file can be a json structured file, in which $.data[*] is used to separate and identify the configuration information corresponding to each type of business data. The data management system is associated with a sending end located in network domain A and a receiving end located in network domain B.

[0098] The sending end triggers the action of synchronizing business data to the receiving end, and synchronizes business data 1 to the receiving end. The data management system determines that the target business data synchronized from the sending end to the receiving end is "business data 1", and obtains the corresponding target configuration information of business data 1 as "configuration information 1" from the preset configuration information. The business identification item "ID" included in the configuration information 1 modifies the first attribute data of the business data synchronized from the sending end to the receiving end (i.e., the business identification of the business data in the sending end) to the second attribute data supported by the receiving end (i.e., the business identification of the business data in the receiving end) through the business identification item. The configuration information 1 also includes a name item, which indicates the enrichment of the third attribute data from the business data through the name item.

[0099] Based on configuration information 1, the data management system determines that the first attribute information in business data 1 is "ID: 123", enriches the third attribute data "name: Zhang San" from business data 1, and associates the first attribute data of business data 1 with the third attribute data, and writes it to the disk as a file, which records {ID: 123, name: 123}.

[0100] The sender sends the file to the receiver through the network gate. After the receiver obtains the business data 1 synchronized by the sender, the data management system determines that the second attribute data supported by the receiver is "ID: 456" based on {ID: 123, name: 123} recorded in the file, and modifies the first attribute data "ID: 123" of business data 1 to the second attribute data "ID: 456". After the modification, the receiver can correctly use and process business data 1.

[0101] Furthermore, an embodiment of the present application also provides a data synchronization device, which is applied to a data management system, the data management system is associated with a sending end and a receiving end, the data management system is preset with configuration information corresponding to at least one business data, and the configuration information is used to indicate that the first attribute data of the business data synchronized from the sending end to the receiving end is modified to the second attribute data supported by the receiving end, such as Figure 2 As shown, the data synchronization device includes:

[0102] A determination module 21, used to determine the target service data synchronized from the sending end to the receiving end;

[0103] The acquisition module 22 is used to acquire the target configuration information corresponding to the target business data from the preset configuration information;

[0104] The modification module 23 is used to modify the first attribute data of the target service data to the second attribute data supported by the receiving end based on the target configuration information.

[0105] The data synchronization device provided by the embodiment of the present application presets configuration information corresponding to at least one business data in the data management system, and the configuration information is used to indicate that the first attribute data of the business data synchronized from the sender to the receiving end is modified to the second attribute data supported by the receiving end. When the sender synchronizes the target business data to the receiving end, the target configuration information corresponding to the target business data is obtained from the preset configuration information, and the first attribute data of the target business data is modified to the second attribute data supported by the receiving end based on the target configuration information. In this way, there is no need to integrate the code for modifying the attribute data at the sender. By obtaining the preset configuration information in the data management system, the first attribute data of the business data synchronized from the sender to the receiving end can be modified to the second attribute data supported by the receiving end, thereby ensuring that the receiving end can normally use and process the business data synchronized from the sender, while reducing the coupling of data synchronization with the sender. In addition, even if the business data that needs to be synchronized between the sender and the receiving end changes, based on the changes that occur, the configuration information preset in the data management system is updated, so that the sender can synchronize the changed business data to the receiving end. The whole process does not require the code of the sender to be modified, and is not invasive to the sender.

[0106] In some embodiments of the present application, Figure 3 As shown, the configuration information is also used to indicate enriching the third attribute data from the service data, and the third attribute data is the data required to determine the second attribute data supported by the receiving end. Then, the modification module 23 includes:

[0107] An enrichment unit 231, configured to enrich the target service data to obtain third attribute data based on the target configuration information;

[0108] A determining unit 232, configured to determine second attribute data supported by the receiving end based on the third attribute data;

[0109] The modifying unit 233 is used to modify the first attribute data of the target business data into the second attribute data.

[0110] In some embodiments of the present application, Figure 3 As shown, the data management system stores at least one second attribute data corresponding to a third attribute data, then the determination unit 232 is specifically used to search for the second attribute data corresponding to the third attribute data in the data management system; and determine the found second attribute data as the second attribute data supported by the receiving end.

[0111] In some embodiments of the present application, Figure 3As shown, the determination unit 232 is further configured to trigger any one of the following modules included in the data synchronization device if the second attribute data corresponding to the third attribute data is not found in the data management system:

[0112] A generating module 24, configured to call a corresponding attribute data generating interface of the receiving end, and generate second attribute data supported by the receiving end for the target service data based on the third attribute data;

[0113] or,

[0114] A detection module 25, configured to detect whether there is third attribute data associated with the third attribute data in the data management system, and the associated third attribute data has corresponding second attribute data, and if so, determine the second attribute data corresponding to the associated third attribute data as the second attribute data supported by the receiving end;

[0115] or,

[0116] The prompt module 26 is used to issue a prompt indicating that the synchronization of the target business data has failed.

[0117] In some embodiments of the present application, Figure 3 As shown, the configuration information includes at least one attribute item, and the attribute data corresponding to the at least one attribute item in the business data is the data required to determine the second attribute data supported by the receiving end. Then, the enrichment unit 231 is specifically used to extract the attribute data corresponding to the at least one attribute item from the target business data based on the target configuration information; and enrich the extracted attribute data into the third attribute data.

[0118] In some embodiments of the present application, the first attribute data and the second attribute data are business identifiers for uniquely identifying the business meaning of the business data, and the third attribute data is attribute data for describing the business meaning of the business data.

[0119] In some embodiments of the present application, Figure 3 As shown, the data synchronization device also includes:

[0120] The customization module 27 is used to customize corresponding target configuration information for the target business data if the target configuration information of the target business data determined by the determination module 21 is not obtained from the preset configuration information, and add the target configuration information to the preset configuration information.

[0121] In some embodiments of the present application, Figure 3 As shown, the customization module 27 includes:

[0122] Prompt unit 271, used to issue a configuration information customization prompt for the target service data;

[0123] A customization unit 272, configured to customize the customization configuration information into target configuration information corresponding to the target service data if customization configuration information for the customization prompt is received;

[0124] The handling unit 273 is used to prevent the target business data from being synchronized to the receiving end if no customized configuration information for the customized prompt is received within the target time period, or feedback rejecting the customization is received, or to allow the target business data to be synchronized to the receiving end and issue a target prompt to the receiving end, wherein the target prompt is used to prompt that the first attribute data of the target business data cannot be modified to the second attribute data supported by the receiving end.

[0125] In some embodiments of the present application, Figure 3 As shown, the data synchronization device also includes:

[0126] The updating module 28 is used to detect whether the type of the service data of the service data to be synchronized between the sending end and the receiving end has changed; if so, update the preset configuration information.

[0127] In some embodiments of the present application, Figure 3 As shown, the update module 28 includes:

[0128] An identification unit 281 is configured to identify first attribute data that is not supported by the receiving end in the service data of the newly added service data type if there is a newly added service data type after the change;

[0129] The updating unit 282 is used to set the configuration information corresponding to the service data of the newly added service data type based on the unsupported first attribute data, and add the corresponding configuration information to the preset configuration information.

[0130] In some embodiments of the present application, Figure 3 As shown, the sending end and the receiving end use different attribute data to uniquely identify the business data with the same business meaning. Then, the identification unit 281 is specifically used to search for attribute data used to uniquely identify the business meaning of the business data of the newly added business data type in the business data of the newly added business data type; and identify the found attribute data as the first attribute data in the business data of the newly added business data type that is not supported by the receiving end.

[0131] In some embodiments of the present application, the sending end and the receiving end are deployed in different network domains.

[0132] In the data synchronization device provided in the embodiment of the present application, the detailed explanations used in the operation of each functional module can be found in the corresponding detailed explanations of the above-mentioned data synchronization method embodiment, which will not be repeated here.

[0133] Furthermore, an embodiment of the present application also provides a computer-readable storage medium, wherein the storage medium includes a stored program, wherein when the program is executed, the device where the storage medium is located is controlled to execute the above-mentioned data synchronization method.

[0134] Furthermore, an embodiment of the present application also provides an electronic device, which includes: a memory for storing a program; and a processor, coupled to the memory, for running the program to execute the above-mentioned data synchronization method.

[0135] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0136] It is understandable that the related features in the above methods and devices can be referenced to each other. In addition, the "first", "second" and the like in the above embodiments are used to distinguish the embodiments, but do not represent the advantages and disadvantages of the embodiments.

[0137] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0138] The algorithm and display provided herein are not inherently related to any particular computer, virtual system or other device. Various general purpose systems can also be used together with the teachings based on this. According to the above description, it is obvious to construct the structure required for this type of system. In addition, the application is not directed to any specific programming language either. It should be understood that various programming languages ​​can be utilized to realize the content of the application described herein, and the description of the above specific language is to disclose the preferred embodiment of the application.

[0139] In addition, the memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0140] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0141] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data cutover device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data cutover device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0142] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data switching device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0143] These computer program instructions can also be loaded onto a computer or other programmable data transfer device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0144] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0145] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0146] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0147] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0148] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0149] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A data synchronization method, characterized in that: Applied to a data management system, the data management system is associated with a sending end and a receiving end, the data management system is preset with configuration information corresponding to at least one type of business data, the configuration information is used to indicate that first attribute data of the business data synchronized from the sending end to the receiving end is modified to second attribute data supported by the receiving end, the method comprising: Determine the target service data synchronized from the sending end to the receiving end; Obtaining target configuration information corresponding to the target service data from preset configuration information; Based on the target configuration information, the first attribute data of the target service data is modified to the second attribute data supported by the receiving end.

2. The method according to claim 1, characterized in that: The configuration information is further used to indicate that third attribute data is enriched from the service data, and the third attribute data is data required to determine the second attribute data supported by the receiving end. Then, based on the target configuration information, the first attribute data of the target service data is modified to the second attribute data supported by the receiving end, including: Based on the target configuration information, enriching the target service data with third attribute data; Based on the third attribute data, determining the second attribute data supported by the receiving end; The first attribute data of the target business data is modified into the second attribute data.

3. The method according to claim 2, characterized in that The data management system stores at least one second attribute data corresponding to the third attribute data, and then, based on the third attribute data, determining the second attribute data supported by the receiving end includes: In the data management system, searching for second attribute data corresponding to the third attribute data; The found second attribute data is determined as the second attribute data supported by the receiving end.

4. The method according to claim 3, characterized in that The method further comprises: If the second attribute data corresponding to the third attribute data is not found in the data management system, any of the following operations is performed: Calling the corresponding attribute data generation interface of the receiving end to generate second attribute data supported by the receiving end for the target service data based on the third attribute data; or, detecting whether there is third attribute data associated with the third attribute data in the data management system, and the associated third attribute data has corresponding second attribute data, and if so, determining the second attribute data corresponding to the associated third attribute data as the second attribute data supported by the receiving end; Or, a prompt is issued that the synchronization of the target business data has failed.

5. The method according to claim 2, characterized in that: The configuration information includes at least one attribute item, and attribute data corresponding to the at least one attribute item in the service data is data required to determine the second attribute data supported by the receiving end. Then, based on the target configuration information, enriching the third attribute data from the target service data includes: Based on the target configuration information, extracting attribute data corresponding to the at least one attribute item from the target service data; The extracted attribute data is enriched into the third attribute data.

6. The method according to any one of claims 2 to 5, characterized in that: The first attribute data and the second attribute data are business identifiers for uniquely identifying the business meaning of the business data, and the third attribute data is attribute data for describing the business meaning of the business data.

7. The method according to claim 1, characterized in that The method further comprises: If the target configuration information of the target service data is not obtained from the preset configuration information, the corresponding target configuration information is customized for the target service data, and the target configuration information is added to the preset configuration information.

8. The method according to claim 7, characterized in that Customize corresponding target configuration information for the target business data, including: Sending a configuration information customization prompt for the target business data; If customized configuration information for the customized prompt is received, the customized configuration information is customized to target configuration information corresponding to the target business data; If no customized configuration information for the customized prompt is received within the target time, or feedback rejecting the customization is received, the target business data is prevented from being synchronized to the receiving end, or the target business data is allowed to be synchronized to the receiving end and a target prompt is issued to the receiving end, wherein the target prompt is used to prompt that the first attribute data of the target business data cannot be modified to the second attribute data supported by the receiving end.

9. The method according to any one of claims 1-5, 7-8, characterized in that: The method further comprises: Detecting whether the type of service data of the service data to be synchronized between the sending end and the receiving end changes; If any changes occur, update the default configuration information.

10. The method according to claim 9, characterized in that Update the preset configuration information, including: If there is a new business data type after the change, identify the first attribute data that is not supported by the receiving end in the business data of the new business data type, set the corresponding configuration information of the business data of the new business data type based on the unsupported first attribute data, and add the corresponding configuration information to the preset configuration information.

11. The method according to claim 10, characterized in that The sending end and the receiving end use different attribute data to uniquely identify the service data with the same service meaning, and then identifying the first attribute data that is not supported by the receiving end in the service data of the newly added service data type includes: Searching, in the business data of the newly added business data type, attribute data for uniquely identifying the business meaning of the business data of the newly added business data type; The found attribute data is identified as first attribute data in the service data of the newly added service data type that is not supported by the receiving end.

12. The method according to any one of claims 1-5, 7-8, 10-11, characterized in that: The sending end and the receiving end are deployed in different network domains.

13. A data synchronization device, characterized in that: Applied to a data management system, the data management system is associated with a sending end and a receiving end, the data management system is preset with configuration information corresponding to at least one type of business data, the configuration information is used to indicate that first attribute data of the business data synchronized from the sending end to the receiving end is modified to second attribute data supported by the receiving end, the device includes: A determination module, used to determine the target service data synchronized from the sending end to the receiving end; An acquisition module, used to acquire target configuration information corresponding to the target business data from preset configuration information; A modification module is used to modify the first attribute data of the target service data to second attribute data supported by the receiving end based on the target configuration information.

14. A computer-readable storage medium, characterized in that: The storage medium includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the data synchronization method described in any one of claims 1 to claim 12.

15. An electronic device, characterized in that: The electronic device comprises: Memory, used to store programs; A processor, coupled to the memory, is used to run the program to execute the data synchronization method described in any one of claims 1 to 12.

Citation Information

Patent Citations

  • A method and apparatus for data synchronization

    CN109241044A

  • Traffic operation data processing method and device

    CN110795480A

  • Method and device for automatically enriching data stream

    CN116910135A

  • Cloud Based Master Data Management System with Configuration Advisor and Method Therefore

    US20130290690A1

  • Known-Deployed File Metadata Repository and Analysis Engine

    US20220366042A1