WO2019052112A1

WO2019052112A1 - Incremental data synchronization method, readable storage medium, terminal device, and apparatus

Info

Publication number: WO2019052112A1
Application number: PCT/CN2018/074869
Authority: WO
Inventors: 覃娆; 覃无愧
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-09-14
Filing date: 2018-01-31
Publication date: 2019-03-21
Also published as: CN107689998B; CN107689998A

Abstract

The present application relates to the technical field of computers, and in particular, to an incremental data synchronization method, a computer-readable storage medium, a terminal device, and an apparatus. The method comprises: separately obtaining first incremental data from each service subsystem, the first incremental data being user data actually added to each service subsystem within a preset first period of time; aggregating the obtained first incremental data to obtain second incremental data, the second incremental data being user data that should be added to each service subsystem within the first period of time; separately comparing the first incremental data with the second incremental data to obtain a missing incremental record of each service subsystem; and separately adding the missing incremental record to the corresponding service subsystem to complete synchronization of the incremental data of each service subsystem. By means of the present application, consistency between incremental data between service subsystems is ensured.

Description

Incremental data synchronization method, readable storage medium, terminal device and device

This application is required to be submitted to the China Patent Office on September 14, 2017, and the application number is CN. The priority of the Chinese Patent Application, which is incorporated herein by reference.

Technical field

The present application belongs to the field of computer technologies, and in particular, to an incremental data synchronization method, a computer readable storage medium, a terminal device, and a device.

Background technique

The current financial business subsystem is large in scale and complex in structure, and the entire system is often divided into multiple service subsystems according to service classification. Therefore, the incremental data of users often needs to be synchronized in multiple service subsystems. The main purpose is to record incremental data in real time to multiple different service subsystems through interface calling. The consistency of data synchronization is difficult to guarantee and the error rate is high.

technical problem

In view of this, the embodiment of the present application provides an incremental data synchronization method, a computer readable storage medium, a terminal device, and a device, to solve the problem that when incremental data is recorded in real time to multiple different service subsystems through an interface calling manner. The consistency of data synchronization is difficult to guarantee, and the error rate is high.

Technical solution

A first aspect of the embodiment of the present application provides an incremental data synchronization method, which may include:

The first incremental data is obtained from each of the service subsystems, where the first incremental data is user data actually added by each of the service subsystems in a preset first time period;

And summarizing the obtained first incremental data to obtain second incremental data, where the second incremental data is user data that should be added by each of the service subsystems in the first time period. ;

Comparing each of the first incremental data with the second incremental data, respectively, to obtain an incremental record missing from each of the service subsystems, where the incremental records are basic units of incremental data, each The incremental record contains a piece of business information;

The missing incremental records are separately added to corresponding business subsystems to complete synchronization of incremental data for each of the business subsystems.

A second aspect of embodiments of the present application provides a computer readable storage medium storing computer readable instructions that, when executed by a processor, implement the following steps:

A third aspect of an embodiment of the present application provides an incremental data synchronization terminal device comprising a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processor The following steps are implemented when the computer readable instructions are executed:

A fourth aspect of the embodiments of the present application provides an incremental data synchronization apparatus, which may include:

The incremental data obtaining module is configured to obtain first incremental data from each service subsystem, where the first incremental data is a user newly added by each of the service subsystems in a preset first time period. data;

An incremental data summary module, configured to summarize the obtained first incremental data to obtain second incremental data, where the second incremental data is used by each of the service subsystems in the first time period User data that should be added internally;

a first comparison module, configured to compare each of the first incremental data with the second incremental data, to obtain an incremental record that is missing from each of the service subsystems, where the incremental record is increased The basic unit of quantity data, each incremental record contains a piece of business information;

The missing record adding module is configured to separately add the missing incremental records to the corresponding service subsystem to complete synchronization of the incremental data of each of the service subsystems.

Beneficial effect

Compared with the prior art, the embodiment of the present application has the beneficial effects that: by using the embodiment of the present application, incremental data is first obtained from each service subsystem, and then summarized, and the aggregated incremental data provides synchronization. Standard, the incremental data of each business subsystem is compared with it, and the difference record between the data and the synchronization standard can be obtained. Since these differences are obtained based on the same synchronization standard, as long as the respective services are According to the synchronization processing of the respective incremental data, the subsystem can ensure that the incremental data between them is consistent, and since the synchronization standard summarizes the data of each service subsystem, the accuracy is greatly ensured. Using this as a reference can greatly reduce the error rate during synchronization.

DRAWINGS

1 is a schematic diagram of an implementation environment in an embodiment of the present application;

2 is a flowchart of an embodiment of an incremental data synchronization method in an embodiment of the present application;

3 is a flowchart of an embodiment of an incremental data synchronization method in a scenario in which a data error exists in the embodiment of the present application;

4 is a schematic flowchart of determining a system to be checked in an embodiment of the present application;

FIG. 5 is a schematic block diagram of an incremental data synchronization terminal device according to an embodiment of the present application;

FIG. 6 is a block diagram of an incremental data synchronization computer readable instruction according to an embodiment of the present application.

Embodiments of the invention

FIG. 1 is a schematic diagram of an implementation environment of an embodiment of the present application. The execution entity in the embodiment of the present application is a synchronization processing system shown in the figure, and the synchronization processing system is connected to each service subsystem to read each service. Incremental data of the subsystem, and summarizes it, then compares the incremental data of each business subsystem with the aggregated incremental data to obtain the incremental data missing from each business subsystem, and finally the missing incremental The records are separately added to the corresponding service subsystems to complete the synchronization of the incremental data for each of the service subsystems.

Referring to FIG. 2, an embodiment of an incremental data synchronization method in the embodiment of the present application may include:

Step S201: Acquire first incremental data from each service subsystem.

The first incremental data is user data that is newly added by each of the service subsystems in a preset first time period. In this embodiment, the synchronization processing system may separately receive the preset data at the first time. The first storage location is configured to read first incremental data of each service subsystem, and the first incremental data is separately extracted by each of the service subsystems at a preset second moment and stored in the first storage location.

For example, a company routinely synchronizes incremental data every morning, and each business subsystem starts a scheduled task at 00:05:00 on the T+1 day (ie, the second time), and the T day in the respective system. The incremental data (i.e., the first incremental data) of 00:00:00 to 24:00:00 (i.e., the first time period) is extracted and stored in the first storage location. The synchronization processing system starts a timing task at 02:00:00 (i.e., the first time) on the T+1 day, and reads the first incremental data from the first storage location. In order to ensure that the synchronous processing system can smoothly read out the data, and avoid the case where there is no data stored in the first storage location during reading, the first moment should be later than the second moment, and the The interval between the first time and the second time should be greater than the preset time interval. The specific value of the time interval can be set according to actual conditions to ensure sufficient data processing and storage for each service subsystem. Prevail.

Step S202, summarizing the acquired first incremental data to obtain second incremental data.

The second incremental data is user data that should be added by each of the service subsystems during the first time period.

In this embodiment, the incremental data is composed of a plurality of incremental records, which are basic units of incremental data, and each incremental record contains a piece of business information, for example, each incremental record can be Represents a binding relationship between a user and a product account.

When summarizing each of the read first incremental data, each incremental data can be regarded as a set, incrementally recorded as an element thereof, and then the union of the sets is obtained, that is, The second incremental data is described. Specifically, all the incremental records may be extracted first and formed into one incremental data, and then only one incremental record is retained for the plurality of incremental records containing the same business information, and other duplicates are deleted. Incremental recording.

For example, if the first incremental data of the service subsystem 1 includes: incremental record 1, incremental record 2, incremental record 3, and incremental record 4, the first incremental data of the service subsystem 2 includes: incremental record 1, incremental record 4, incremental record 5 and incremental record 6, then the second incremental data obtained after the summary includes: incremental record 1, incremental record 2, incremental record 3, incremental record 4, Incremental record 5 and incremental record 6.

Step S203, comparing each of the first incremental data with the second incremental data, to obtain an incremental record missing by each of the service subsystems.

In the above example, the first incremental data of the service subsystem 1 is compared with the second incremental data, and the obtained incremental increments are recorded as an incremental record 5 and an incremental record 6, and the business is The first incremental data of system 2 is compared to the second incremental data, and the resulting missing incremental records are incremental record 2 and incremental record 3.

Step S204: Add the missing incremental records to the corresponding service subsystems respectively to complete synchronization of the incremental data of each of the service subsystems.

Specifically, the synchronization processing system may separately store the missing incremental records in a preset second storage location at a preset third moment, so that each of the service subsystems respectively receives the preset fourth moments. The second storage location reads the incremental records that are each missing, and adds the missing incremental records to the corresponding first incremental data to obtain synchronized incremental data.

It is easy to understand that the third moment should be later than the first moment, and the interval between the first moment and the third moment should be greater than a certain time interval to ensure sufficient synchronization processing system to complete reading. The summation and comparison processes are correct, the fourth time should be later than the third time, and the interval between the third time and the fourth time should be greater than a certain time interval to ensure sufficient The synchronous processing system completes the stored procedure.

For example, the synchronization processing system starts the timing task for reading, summarizing, and comparing at 02:00:00 (that is, the first moment) on the T+1 day, and at 05:00:00 on the T+1 day. (that is, the third time) starts a timed task to perform a stored procedure, and each service subsystem starts a timed task for reading and adding at 06:00:00 (that is, the fourth time) on the T+1 day.

In the above embodiments, it is based on the premise that the data of the service subsystem is all trusted data. However, in practical applications, the data of the business subsystem may be wrong and needs to be considered. Referring to FIG. 3, an embodiment in the context of considering a data error may include:

Step S301: Acquire first incremental data from each service subsystem.

The step S301 is the same as the step S201 in the foregoing embodiment. For details, refer to the description in the foregoing embodiment.

Step S302, summarizing the acquired first incremental data to obtain second incremental data.

The step S302 is the same as the step S202 in the foregoing embodiment. For details, refer to the description in the foregoing embodiment.

Step S303: Calculate the credibility of each incremental record in the second incremental data according to a preset data credibility of each of the service subsystems.

The data credibility of each of the service subsystems is determined according to historical statistics. If in the historical statistics, the service subsystem performs the modification operation on the incremental data (including the operation of adding the incremental record and deleting the incremental record). The more operations, the higher the probability that the data will be wrong, and the lower the data credibility. The data credibility of the service subsystem ranges from [0, 1]. When 0 is used, the data is completely untrustworthy. When 1 is taken, the data is completely trusted.

In this embodiment, the credibility of the incremental record can be calculated by summing the data credibility of each service subsystem in which the incremental record occurs, and dividing by the total number of service subsystems. The resulting quotient is the credibility of the incremental record. Similarly, the credibility of the incremental record ranges from [0, 1]. When 0, it means that the data is completely untrustworthy. Its data is completely trustworthy.

For example, if there are three service subsystems, namely, service subsystem 1, service subsystem 2, and service subsystem 3, the data reliability is 0.9, 0.8, and 0.7. Among them, the incremental record 1 appears in the business subsystem 2 and the business subsystem 3, but does not appear in the business subsystem 1, then the credibility of the incremental record 1 is (0.8 + 0.7) / 3 = 0.5.

Step S304, extracting, from each of the incremental records in the second incremental data, the preferred record whose reliability is greater than a preset second threshold.

The value of the second threshold may be set according to the actual situation. This embodiment does not specifically limit this, but it should be noted that if the value is larger, the preferred record extracted is less, if its value is The smaller, the more preferred records are extracted.

Optionally, the following processing manner may be adopted as a simplification of step S303 and step S304: respectively counting the total number of occurrences of each incremental record in the second incremental data in the first incremental data. Extracting, from each of the incremental records in the second incremental data, a preferred record that is greater than a preset first threshold, the first threshold being a total of the service subsystems The number is determined. For example, if the total number of service subsystems is 10, the first threshold is set to half of the total number, that is, the value is 5, and the total number of occurrences of the incremental record 1 in the first incremental data is 4. The total number of occurrences of the incremental record 2 in the first incremental data is 6, then the incremental record 2 is the preferred record and the incremental record 1 is not the preferred record.

Step S305, the extracted pieces of the preferred records are combined into the second increment data of the preferred ones.

Compared with the initial second incremental data, only the incremental record with higher reliability is retained in the preferred second incremental data, and the synchronization result obtained is more accurate.

Step S306, comparing each of the first incremental data with the preferred second incremental data, to obtain an incremental record and a redundant incremental record of each of the service subsystems.

For example, if the first incremental data of the service subsystem 1 includes: incremental record 1, incremental record 2, incremental record 3, and incremental record 4, the first incremental data of the service subsystem 2 includes: incremental record 1. Incremental record 2, incremental record 3 and incremental record 5, and the preferred second incremental data includes: incremental record 1, incremental record 2, incremental record 3, and incremental record 5.

Comparing the first incremental data of the service subsystem 1 with the preferred second incremental data, the obtained incremental increment record is an incremental record 5, and the redundant incremental record is an incremental record 4, The first incremental data of the service subsystem 2 is compared with the second incremental data, and the two are completely identical, and there is neither a missing incremental record nor a redundant incremental record.

Step S307: Add the missing incremental records to the corresponding service subsystems respectively, and delete the redundant incremental records from the corresponding service subsystems.

Specifically, the synchronization processing system may separately store the missing incremental record and the redundant incremental record into a preset second storage location, so that each of the service subsystems respectively from the second storage location Reading the incremental records that are each missing and the incremental incremental records, and adding the missing incremental records to the corresponding first incremental data, and from the corresponding first incremental data The redundant incremental records are deleted, and the synchronized incremental data is obtained.

Preferably, for a business subsystem with low data credibility, it needs to be checked to reduce the probability of its error. Specifically, the steps as shown in FIG. 4 may be included:

In step S401, the total number of historical operation records of each of the service subsystems is separately counted.

The historical operation record is an operation record (including an operation of adding an incremental record and an operation of deleting an incremental record) performed by the service subsystem during the synchronization of the preset second time period, in order to avoid short-term sudden The second time period should be long enough, for example, one week, one month, and the like.

Step S402, determining, by the service subsystem that the total number of historical operation records is greater than a preset third threshold, as a to-be-checked system;

The greater the total number of historical operational records, the higher the probability that their data will be incorrect. The value of the third threshold may be set according to the actual situation. This embodiment does not specifically limit this, but it should be noted that if the value is larger, the less the system to be checked is determined, if it is taken. The smaller the value, the more systems are determined to be investigated.

Step S403, notifying the designated staff to check the to-be-checked system.

In summary, in the embodiment of the present application, incremental data is first obtained from each service subsystem, and then summarized, and the aggregated incremental data provides synchronization standards, and the incremental data of each service subsystem is separately In comparison with it, a difference record between the synchronization standard and the synchronization standard can be obtained. Since the differences are obtained based on the same synchronization standard, each of the service subsystems can perform the respective incremental data accordingly. Synchronous processing ensures that the incremental data between them is consistent, and since the synchronization standard summarizes the data of each business subsystem, the accuracy is greatly ensured, and as a reference, the synchronization error can be greatly reduced. rate.

Corresponding to the incremental data synchronization method described in the foregoing embodiment, FIG. 5 is a schematic block diagram of the incremental data synchronization terminal device provided by the embodiment of the present application. For the convenience of description, only the embodiment of the present application is shown. part.

In this embodiment, the incremental data synchronization terminal device may be a computing device such as a desktop computer, a notebook, a palmtop computer, or a cloud server. The incremental data synchronization terminal device can include a processor 50, a memory 51, and computer readable instructions 52 stored in the memory 51 and executable on the processor 50.

The processor 50 can be a central processing unit (Central Processing Unit, CPU), can also be other general-purpose processors, digital signal processors (DSP), ASICs (Application) Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 51 may be an internal storage unit of the incremental data synchronization terminal device 5, such as a hard disk or a memory of the incremental data synchronization terminal device 5. The memory 51 may also be an external storage device of the incremental data synchronization terminal device 5, for example, a plug-in hard disk equipped with the smart data card (SMC) provided on the incremental data synchronization terminal device 5, Secure Digital (SD) card, flash card (Flash Card) and so on. Further, the memory 51 may also include both an internal storage unit of the incremental data synchronization terminal device 5 and an external storage device. The memory 51 is used to store the computer readable instructions and other instructions and data required by the incremental data synchronization terminal device 5. The memory 51 can also be used to temporarily store data that has been output or is about to be output.

Please refer to FIG. 6, which is a block diagram of computer readable instructions 52 provided by an embodiment of the present application. In the present embodiment, the computer readable instructions 52 may be partitioned into one or more modules, the one or more modules being stored in the memory 51 and executed by the processor 50, To complete this application. For example, in FIG. 6, the computer readable instructions 52, ie, incremental data synchronization computer readable instructions, may be segmented into an incremental data acquisition module 601, an incremental data summary module 602, and a first alignment module 603. The missing record adding module 604. The following description will specifically describe the functions of the modules 601-604.

The incremental data obtaining module 601 is configured to obtain first incremental data from each service subsystem, where the first incremental data is actually added by each of the service subsystems in a preset first time period. User data;

The incremental data summary module 602 is configured to summarize the obtained first incremental data to obtain second incremental data, where the second incremental data is used by each of the service subsystems at the first time User data that should be added in the segment;

a first comparison module 603, configured to compare each of the first incremental data with the second incremental data, to obtain an incremental record that is missing from each of the service subsystems, where the incremental record is The basic unit of incremental data, each incremental record contains a piece of business information;

The missing record adding module 604 is configured to separately add the missing incremental records to the corresponding service subsystem to complete synchronization of the incremental data of each of the service subsystems.

Optionally, the computer readable instructions 52 may further include:

a quantity statistics module, configured to separately count the total number of occurrences of each incremental record in the second incremental data in the first incremental data;

a first preferred record extraction module, configured to extract, from each of the incremental records in the second incremental data, the preferred record that is greater than a preset first threshold, the first threshold being The total number of the service subsystems is determined;

And a first component module, configured to form the extracted pieces of the preferred records into the second incremental data after the selection.

Optionally, the computer readable instructions 52 may further include:

a credibility calculation module, configured to calculate, according to a preset data credibility of each of the service subsystems, a credibility of each incremental record in the second incremental data;

a second preferred record extraction module, configured to extract, from each of the incremental records in the second incremental data, the preferred record whose reliability is greater than a preset second threshold;

And a second component module, configured to form the extracted pieces of the preferred records into the second incremental data after the selection.

Further, the computer readable instructions 52 may further include:

a second comparison module, configured to compare each of the first incremental data with the preferred second incremental data to obtain an incremental incremental record of each of the service subsystems;

The redundant record deletion module is configured to delete the redundant incremental records from the corresponding service subsystems.

Further, the computer readable instructions 52 may further include:

The operation statistics module is configured to separately count the total number of historical operation records of each of the service subsystems, where the historical operation record is an operation record performed by the service subsystem during synchronization processing in a preset second time period. ;

The to-be-checked system determining module is configured to determine the service subsystem whose total number of historical operation records is greater than a preset third threshold as a to-be-checked system;

The troubleshooting module is configured to notify the designated staff to check the system to be checked.

A person skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the above embodiments, the descriptions of the various embodiments are different, and the parts that are not detailed or described in the specific embodiments may be referred to the related descriptions of other embodiments.

Those of ordinary skill in the art will appreciate that the modules, units, and/or method steps of the various embodiments described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

In the several embodiments provided by the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application, in essence or the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), and a random access memory (RAM, Random Access). A variety of media that can store computer readable instructions, such as a Memory, a disk, or an optical disk.

The above embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still The technical solutions described in the embodiments are modified, or the equivalents of the technical features are replaced by the equivalents. The modifications and substitutions of the embodiments do not depart from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

An incremental data synchronization method, comprising:

The first incremental data is obtained from each of the service subsystems, where the first incremental data is user data actually added by each of the service subsystems in a preset first time period;

And summarizing the obtained first incremental data to obtain second incremental data, where the second incremental data is user data that should be added by each of the service subsystems in the first time period. ;

Comparing each of the first incremental data with the second incremental data, respectively, to obtain an incremental record missing from each of the service subsystems, where the incremental records are basic units of incremental data, each The incremental record contains a piece of business information;

The missing incremental records are separately added to corresponding business subsystems to complete synchronization of incremental data for each of the business subsystems.
The incremental data synchronization method according to claim 1, wherein after obtaining the second incremental data, the method further comprises:

And counting, respectively, a total number of times that each of the incremental data records in the second incremental data appears in the first incremental data;

Extracting, from each of the incremental records in the second incremental data, a preferred record that is greater than a preset first threshold, the first threshold being the total number of the service subsystems determine;

Each of the extracted preferred records is composed of the preferred second incremental data.
The incremental data synchronization method according to claim 1, wherein after obtaining the second incremental data, the method further comprises:

Calculating the credibility of each incremental record in the second incremental data according to a preset data credibility of each of the service subsystems;

Extracting, from each of the incremental records in the second incremental data, the preferred record whose reliability is greater than a preset second threshold;

Each of the extracted preferred records is composed of the preferred second incremental data.
The incremental data synchronization method according to claim 2 or 3, further comprising:

Comparing each of the first incremental data with the preferred second incremental data to obtain an incremental incremental record of each of the service subsystems;

The redundant incremental records are respectively deleted from the corresponding service subsystem.
The incremental data synchronization method according to any one of claims 1 to 3, further comprising:

Counting, respectively, a total number of historical operation records of each of the service subsystems, where the historical operation record is an operation record performed by the service subsystem when performing synchronization processing in a preset second time period;

Determining, by the service subsystem, that the total number of historical operation records is greater than a preset third threshold, as a system to be checked;

Notify the designated staff to check the system to be investigated.
A computer readable storage medium storing computer readable instructions, wherein the computer readable instructions, when executed by a processor, implement the following steps:

The first incremental data is obtained from each of the service subsystems, where the first incremental data is user data actually added by each of the service subsystems in a preset first time period;

And summarizing the obtained first incremental data to obtain second incremental data, where the second incremental data is user data that should be added by each of the service subsystems in the first time period. ;

Comparing each of the first incremental data with the second incremental data, respectively, to obtain an incremental record missing from each of the service subsystems, where the incremental records are basic units of incremental data, each The incremental record contains a piece of business information;

The missing incremental records are separately added to corresponding business subsystems to complete synchronization of incremental data for each of the business subsystems.
The computer readable storage medium according to claim 6, wherein after obtaining the second incremental data, the method further comprises:

And counting, respectively, a total number of times that each of the incremental data records in the second incremental data appears in the first incremental data;

Extracting, from each of the incremental records in the second incremental data, a preferred record that is greater than a preset first threshold, the first threshold being the total number of the service subsystems determine;

Each of the extracted preferred records is composed of the preferred second incremental data.
The computer readable storage medium according to claim 6, wherein after obtaining the second incremental data, the method further comprises:

Calculating the credibility of each incremental record in the second incremental data according to a preset data credibility of each of the service subsystems;

Extracting, from each of the incremental records in the second incremental data, the preferred record whose reliability is greater than a preset second threshold;

Each of the extracted preferred records is composed of the preferred second incremental data.
The computer readable storage medium according to claim 7 or 8, further comprising:

Comparing each of the first incremental data with the preferred second incremental data to obtain an incremental incremental record of each of the service subsystems;

The redundant incremental records are respectively deleted from the corresponding service subsystem.
The computer readable storage medium according to any one of claims 6 to 8, further comprising:

Counting, respectively, a total number of historical operation records of each of the service subsystems, where the historical operation record is an operation record performed by the service subsystem when performing synchronization processing in a preset second time period;

Determining, by the service subsystem, that the total number of historical operation records is greater than a preset third threshold, as a system to be checked;

Notify the designated staff to check the system to be investigated.
An incremental data synchronization terminal device comprising a memory, a processor, and computer readable instructions stored in the memory and operative on the processor, wherein the processor executes the computer readable The following steps are implemented when the instruction is executed:

The first incremental data is obtained from each of the service subsystems, where the first incremental data is user data actually added by each of the service subsystems in a preset first time period;

And summarizing the obtained first incremental data to obtain second incremental data, where the second incremental data is user data that should be added by each of the service subsystems in the first time period. ;

Comparing each of the first incremental data with the second incremental data, respectively, to obtain an incremental record missing from each of the service subsystems, where the incremental records are basic units of incremental data, each The incremental record contains a piece of business information;

The missing incremental records are separately added to corresponding business subsystems to complete synchronization of incremental data for each of the business subsystems.
The incremental data synchronization terminal device according to claim 11, wherein after obtaining the second incremental data, the method further comprises:

And counting, respectively, a total number of times that each of the incremental data records in the second incremental data appears in the first incremental data;

Extracting, from each of the incremental records in the second incremental data, a preferred record that is greater than a preset first threshold, the first threshold being the total number of the service subsystems determine;

Each of the extracted preferred records is composed of the preferred second incremental data.
The incremental data synchronization terminal device according to claim 11, wherein after obtaining the second incremental data, the method further comprises:

Calculating the credibility of each incremental record in the second incremental data according to a preset data credibility of each of the service subsystems;

Extracting, from each of the incremental records in the second incremental data, the preferred record whose reliability is greater than a preset second threshold;

Each of the extracted preferred records is composed of the preferred second incremental data.
The incremental data synchronization terminal device according to claim 12 or 13, further comprising:

Comparing each of the first incremental data with the preferred second incremental data to obtain an incremental incremental record of each of the service subsystems;

The redundant incremental records are respectively deleted from the corresponding service subsystem.
The incremental data synchronization terminal device according to any one of claims 11 to 13, further comprising:

Counting, respectively, a total number of historical operation records of each of the service subsystems, where the historical operation record is an operation record performed by the service subsystem when performing synchronization processing in a preset second time period;

Determining, by the service subsystem, that the total number of historical operation records is greater than a preset third threshold, as a system to be checked;

Notify the designated staff to check the system to be investigated.
An incremental data synchronization device, comprising:

The incremental data obtaining module is configured to obtain first incremental data from each service subsystem, where the first incremental data is a user newly added by each of the service subsystems in a preset first time period. data;

An incremental data summary module, configured to summarize the obtained first incremental data to obtain second incremental data, where the second incremental data is used by each of the service subsystems in the first time period User data that should be added internally;

a first comparison module, configured to compare each of the first incremental data with the second incremental data, to obtain an incremental record that is missing from each of the service subsystems, where the incremental record is increased The basic unit of quantity data, each incremental record contains a piece of business information;

The missing record adding module is configured to separately add the missing incremental records to the corresponding service subsystem to complete synchronization of the incremental data of each of the service subsystems.
The incremental data synchronization device of claim 16, further comprising:

a quantity statistics module, configured to separately count the total number of occurrences of each incremental record in the second incremental data in the first incremental data;

a first preferred record extraction module, configured to extract, from each of the incremental records in the second incremental data, the preferred record that is greater than a preset first threshold, the first threshold being The total number of the service subsystems is determined;

And a first component module, configured to form the extracted pieces of the preferred records into the second incremental data after the selection.
The incremental data synchronization device of claim 16, further comprising:

a credibility calculation module, configured to calculate, according to a preset data credibility of each of the service subsystems, a credibility of each incremental record in the second incremental data;

a second preferred record extraction module, configured to extract, from each of the incremental records in the second incremental data, the preferred record whose reliability is greater than a preset second threshold;

And a second component module, configured to form the extracted pieces of the preferred records into the second incremental data after the selection.
The incremental data synchronization device according to claim 17 or 18, further comprising:

a second comparison module, configured to compare each of the first incremental data with the preferred second incremental data to obtain an incremental incremental record of each of the service subsystems;

The redundant record deletion module is configured to delete the redundant incremental records from the corresponding service subsystems.
The incremental data synchronization device according to any one of claims 16 to 18, further comprising:

The operation statistics module is configured to separately count the total number of historical operation records of each of the service subsystems, where the historical operation record is an operation record performed by the service subsystem during synchronization processing in a preset second time period. ;

The to-be-checked system determining module is configured to determine the service subsystem whose total number of historical operation records is greater than a preset third threshold as a to-be-checked system;

The troubleshooting module is configured to notify the designated staff to check the system to be checked.