Synchronization data verification method and device, equipment, medium and program product
By obtaining and verifying synchronization information in real time during the data synchronization process and marking out-of-synchronous data, the problem of untimely synchronization verification in the existing technology is solved, and the synchronization terminal can promptly handle and verify data synchronization.
Patent Information
- Application Number
- CN202410954710.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-16
- Publication Date
- 2024-11-19
AI Technical Summary
The existing data synchronization method is verified after the data synchronization is completed, resulting in untimely synchronization verification and the synchronization terminal cannot process the synchronous data in a timely manner.
During the data synchronization process, data synchronization information is obtained in real time, data synchronization is verified, and the synchronization data is marked as out of sync when the verification result indicates that it is out of sync.
It realizes the timely discovery and processing of out-of-synchronous data during the data synchronization process, and improves the timeliness and efficiency of data synchronization verification.
Smart Images

Figure CN118981497A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of data processing technology, and in particular, relates to a method, device, equipment, medium and program product for verifying synchronization data. Background Art
[0002] Data synchronization is an important concept in information technology. It involves copying data from one location to another to ensure the consistency and integrity of data between multiple systems, devices, or databases. In order to ensure that the synchronized data remains consistent across all related systems or devices, the synchronization of the data needs to be verified after the data synchronization is completed. However, the current data synchronization method usually verifies the synchronization of the data after the data synchronization is completed, which results in untimely verification of the synchronization of the data, and the corresponding synchronization terminal cannot process the synchronized data accordingly during synchronization. Summary of the invention
[0003] The embodiments of the present application provide a synchronization data verification method, apparatus, device, medium and program product, which can facilitate users to promptly discover unsynchronized synchronization data and perform corresponding processing.
[0004] In a first aspect, an embodiment of the present application provides a method for verifying synchronization data, the method comprising:
[0005] When the synchronization terminal performs data synchronization on the synchronization data, acquiring data synchronization information of the synchronization data;
[0006] Verifying the synchronization data according to the data synchronization information and generating a verification result of the synchronization data, wherein the verification result is used to indicate whether the synchronization data is synchronized;
[0007] In a case where the verification result indicates that the synchronization data is out of synchronization, the synchronization data of the synchronization terminal is marked as out of synchronization.
[0008] In a second aspect, an embodiment of the present application provides a synchronization data verification device, the device comprising:
[0009] A first acquisition module, configured to acquire data synchronization information of the synchronization data when the synchronization terminal performs data synchronization on the synchronization data;
[0010] A verification module, used to verify the synchronization data according to the data synchronization information, and generate a verification result of the synchronization data, wherein the verification result is used to indicate whether the synchronization data is synchronized;
[0011] The first marking module is configured to mark the synchronization data of the synchronization terminal as being out of synchronization when the verification result indicates that the synchronization data is out of synchronization.
[0012] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the method for verifying synchronization data as described in any one of the above items is implemented.
[0013] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the method for verifying synchronization data as described in any one of the above items is implemented.
[0014] In a fifth aspect, an embodiment of the present application provides a computer program product. When instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the synchronization data verification method as described in any one of the above.
[0015] The verification method, device, equipment, medium and program product of the synchronization data of the embodiment of the present application can obtain the data synchronization information of the synchronization data when the synchronization terminal performs data synchronization on the synchronization data; verify the synchronization data according to the data synchronization information, and generate the verification result of the synchronization data, and the verification result is used to indicate whether the synchronization data is synchronized; when the verification result indicates that the synchronization data is not synchronized, the synchronization data of the synchronization terminal is marked as not synchronized. In this way, in the embodiment of the present application, while the synchronization terminal performs data synchronization on the synchronization data, the synchronization of the data can be verified and the synchronization data that is not synchronized can be marked, so that the user can find the synchronization data that is not synchronized in time and perform corresponding processing. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] In order to more clearly illustrate the technical solution of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0017] Figure 1 It is a flowchart of a method for verifying synchronization data provided by an embodiment of the present application;
[0018] Figure 2 It is a flowchart of a data synchronization method provided in an embodiment of the present application;
[0019] Figure 3 This is a flowchart of a scenario embodiment provided by an embodiment of the present application;
[0020] Figure 4 It is a flowchart of another scenario embodiment provided by the embodiment of the present application;
[0021] Figure 5It is a structural diagram of a verification device for synchronization data provided in an embodiment of the present application;
[0022] Figure 6 It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0023] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.
[0024] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article 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, article or device. In the absence of further restrictions, the elements defined by the statement "include..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0025] Data synchronization is an important concept in information technology. It involves copying data from one location to another to ensure the consistency and integrity of data between multiple systems, devices, or databases. In order to ensure that the synchronized data remains consistent across all related systems or devices, the synchronization of the data needs to be verified after the data synchronization is completed. However, the current data synchronization method usually verifies the synchronization of the data after the data synchronization is completed, which results in untimely verification of the synchronization of the data, and the corresponding synchronization terminal cannot process the synchronized data accordingly during synchronization.
[0026] In order to solve the problems in the prior art, the embodiments of the present application provide a method, device, equipment, medium and program product for verifying synchronization data. The following first introduces the method for verifying synchronization data provided by the embodiments of the present application.
[0027] Figure 1 FIG. 1 is a flow chart showing a method for verifying synchronization data provided by an embodiment of the present application. Figure 1 As shown, a method for verifying synchronization data may include the following steps S101 to S103:
[0028] S101. When a synchronization terminal performs data synchronization on synchronization data, data synchronization information of the synchronization data is acquired;
[0029] S102, verifying the synchronization data according to the data synchronization information, and generating a verification result of the synchronization data, where the verification result is used to indicate whether the synchronization data is synchronized;
[0030] S103: When the verification result indicates that the synchronization data is not synchronized, mark the synchronization data of the synchronization terminal as being not synchronized.
[0031] The method for verifying the synchronization data of the embodiment of the present application can obtain the data synchronization information of the synchronization data when the synchronization terminal performs data synchronization on the synchronization data; verify the synchronization data according to the data synchronization information, and generate the verification result of the synchronization data, and the verification result is used to indicate whether the synchronization data is synchronized; when the verification result indicates that the synchronization data is not synchronized, the synchronization data of the synchronization terminal is marked as not synchronized. In this way, in the embodiment of the present application, while the synchronization terminal performs data synchronization on the synchronization data, the synchronization of the data can be verified and the synchronization data that is not synchronized can be marked, so that the user can find the synchronization data that is not synchronized in time and perform corresponding processing.
[0032] In S101, the above-mentioned synchronization terminal may refer to each device or system node involved in the data synchronization process. These terminals may be physical devices, such as servers, personal computers, mobile devices, etc., or they may be database systems or applications running on these devices. The number of synchronization terminals depends on the synchronization requirements and the architectural design, and there may be multiple or two. Among them, among the synchronization terminals, the synchronization terminal that originally stores the data and provides data for synchronization is the source terminal, and the synchronization terminal that receives the data synchronization and receives the data from the source terminal is the target terminal. The above-mentioned verification method for synchronized data is mainly applied to the source terminal, but is not limited thereto in the present application, and may also be other terminal devices with data processing capabilities.
[0033] The above-mentioned synchronized data may refer to the data copied from one system or device to another system or device during the data synchronization process. Such data may be files, database records, configuration information, etc., and its purpose is to maintain the consistency and integrity of data between multiple systems or devices. The synchronized data may be full data (i.e. all data) or incremental data (i.e. data that has changed since the last synchronization).
[0034] The above data synchronization information can be used to characterize the synchronization status of the synchronization data in the synchronization terminal, specifically including a plurality of data synchronization progresses, and different data synchronization progresses correspond to different synchronization times.
[0035] In S102, the above verification result can be used to indicate whether the synchronization data is synchronized.
[0036] The above-mentioned verification of the synchronization data based on the data synchronization information and generation of the verification result of the synchronization data may be, for example, calculating at least one synchronization progress difference value based on multiple data synchronization progresses, where the synchronization progress difference value is the difference between the latter synchronization progress and the former synchronization progress among the multiple data synchronization progresses; comparing each synchronization progress difference value with a preset approved progress difference value to determine the progress difference type of each synchronization progress difference value, where the progress difference type includes a lagging progress difference type and a leading progress difference type, where the lagging progress difference type is used to characterize that the synchronization progress difference value is less than the approved progress difference, and the leading progress difference type is used to characterize that the synchronization progress difference value is greater than or equal to the approved progress difference; calculating the lagging progress value and the leading progress value based on the progress difference type of at least one synchronization progress difference value; calculating the synchronization verification value of the synchronization data based on the lagging progress value and the leading progress value, and the verification result includes the synchronization verification value.
[0037] In S103, when the verification result indicates that the synchronization data is not synchronized, the synchronization data of the synchronization terminal is marked as not synchronized. Exemplarily, when the synchronization verification value is less than a preset synchronization verification threshold, it is determined that the synchronization data is not synchronized and the synchronization data of the synchronization terminal is marked as not synchronized.
[0038] In some embodiments, the data synchronization information includes a plurality of data synchronization progresses, and different data synchronization progresses correspond to different synchronization times. The above S102 may specifically include:
[0039] Calculate at least one synchronization progress difference according to the plurality of data synchronization progresses, where the synchronization progress difference is a difference between a subsequent synchronization progress and a preceding synchronization progress among the plurality of data synchronization progresses;
[0040] Compare each synchronous progress difference with the preset approved progress difference to determine the progress difference type of each synchronous progress difference. The progress difference type includes a lagging progress difference type and a leading progress difference type. The lagging progress difference type is used to indicate that the synchronous progress difference is less than the approved progress difference, and the leading progress difference type is used to indicate that the synchronous progress difference is greater than or equal to the approved progress difference.
[0041] Calculate a lagging progress value and a leading progress value according to a progress difference type of at least one synchronous progress difference value;
[0042] According to the backward progress value and the leading progress value, the synchronization verification value of the synchronization data is calculated.
[0043] The verification result includes a synchronization verification value.
[0044] The above-mentioned data synchronization progress refers to an indicator used to measure and display the degree of completion of the data synchronization task during the data synchronization process. It is usually expressed as a percentage or the number of completed items, so that users or system administrators can intuitively understand the current status of data synchronization. The above-mentioned multiple data synchronization progresses are continuously detected at the same time interval, and the time interval includes but is not limited to detecting the data synchronization progress every 2s, 3s, and 4s.
[0045] The above-mentioned method calculates at least one synchronization progress difference based on multiple data synchronization progresses. Exemplarily, the multiple data synchronization progresses detected may be sorted in chronological order, and the data synchronization progress that is adjacent and sorted later after the sorting is marked as the post-sync progress, and the data synchronization progress that is adjacent and sorted earlier after the sorting is marked as the pre-sync progress, and the difference between the post-sync progress and the pre-sync progress is calculated to obtain the synchronization progress difference.
[0046] The above-mentioned progress difference types include a lagging progress difference type and a leading progress difference type. The lagging progress difference type is used to indicate that the synchronous progress difference is less than the approved progress difference, and the leading progress difference type is used to indicate that the synchronous progress difference is greater than or equal to the approved progress difference.
[0047] The above-mentioned comparison of each synchronization progress difference with the preset approved progress difference to determine the progress difference type of each synchronization progress difference can be performed by setting each synchronization progress difference to correspond to an approved progress difference. When the synchronization progress difference is less than the approved progress difference, the synchronization progress difference is marked as a lagging progress difference. When the synchronization progress difference is greater than or equal to the approved progress difference, the synchronization progress difference is marked as a leading progress difference. For example, when the approved progress difference is set to 5, when the synchronization progress difference is 4, the synchronization progress difference is marked as a lagging progress difference. When the synchronization progress difference is 6, the synchronization progress difference is marked as a leading progress difference.
[0048] The backward progress value and the leading progress value are calculated based on the progress difference type of at least one synchronous progress difference. For example, the backward progress value can be calculated based on the synchronous progress difference of the backward progress difference type, and the backward progress value is obtained by summing the backward total ratio difference multiplied by the first coefficient and the backward progress quantity multiplied by the second coefficient. The backward total ratio difference is the sum of the differences between the synchronous progress differences of each backward progress difference type in the at least one synchronous progress difference and the approved progress difference, and the backward progress quantity is the number of the synchronous progress differences of the backward progress difference type in the at least one synchronous progress difference; the leading progress value is calculated based on the synchronous progress differences of the leading progress difference type, and the leading progress value is obtained by summing the leading total ratio difference multiplied by the third coefficient and the leading progress quantity multiplied by the fourth coefficient. The leading total ratio difference is the sum of the differences between the synchronous progress differences of each leading progress difference type in the at least one synchronous progress difference and the approved progress difference, and the leading progress quantity is the number of the synchronous progress differences of the leading progress difference type in the at least one synchronous progress difference.
[0049] The synchronization verification value of the synchronization data is calculated based on the lagging progress value and the leading progress value, which can be specifically calculated using the following formula:
[0050]
[0051] The synchronization verification value Rt is obtained, where Bw is the lagging progress value, c1 is the lagging progress value coefficient, Hs is the leading progress value, and c2 is the leading progress value coefficient. In the embodiment of the present application, the value of c1 is 0.98, and the value of c2 is 0.97. Of course, c1 and c2 in the present application are not limited to this, and can also be set according to actual needs, which is not specifically limited here.
[0052] The above verification result includes a synchronization verification value, that is, when the synchronization verification value is less than a preset synchronization verification threshold, it is determined that the synchronization data is not synchronized; when the synchronization verification value is greater than or equal to the synchronization verification threshold, it is determined that the synchronization data is synchronized.
[0053] In an embodiment of the present application, the synchronization progress difference is calculated through the data synchronization progress at different synchronization moments, and compared with the approved progress difference, the progress difference type of each synchronization progress difference is identified, and then the lagging progress value and the leading progress value are calculated. Finally, the synchronization verification value of the synchronized data can be accurately calculated to realize the verification of data synchronization while performing data synchronization on the synchronization terminal.
[0054] In some embodiments, the calculation of the lagging progress value and the leading progress value according to the progress difference type of at least one synchronization progress difference value may specifically include:
[0055] According to the synchronous progress difference of the backward progress difference type, the backward progress value is calculated, and the backward progress value is obtained by summing the backward total ratio difference multiplied by the first coefficient and the backward progress quantity multiplied by the second coefficient. The backward total ratio difference is the sum of the differences between the synchronous progress difference of each backward progress difference type in at least one synchronous progress difference and the approved progress difference, and the backward progress quantity is the quantity of the synchronous progress difference of the backward progress difference type in at least one synchronous progress difference;
[0056] The leading progress value is calculated according to the synchronous progress difference of the leading progress difference type. The leading progress value is obtained by summing the leading total ratio difference multiplied by the third coefficient and the leading progress quantity multiplied by the fourth coefficient. The leading total ratio difference is the sum of the differences between the synchronous progress differences of each leading progress difference type in at least one synchronous progress difference and the approved progress difference. The leading progress quantity is the quantity of the synchronous progress differences of the leading progress difference type in at least one synchronous progress difference.
[0057] The backward progress value is calculated based on the synchronous progress difference of the backward progress difference type. For example, the difference between the approved progress difference and each synchronous progress difference of the backward progress difference type can be calculated to obtain each backward ratio difference, and all the backward ratio differences are summed to obtain the total backward ratio difference, which is marked as Fm, and the total number of times the synchronous progress difference is marked as the backward progress difference is obtained, which is marked as Py. The backward progress value Bw is obtained by using the formula Bw=Fm×a1+Py×a2, wherein the first coefficient a1 is the total backward ratio difference coefficient, and the second coefficient a2 is the backward progress quantity coefficient. In the embodiment of the present application, the value of a1 is 0.67, and the value of a2 is 0.75. Of course, a1 and a2 in the present application are not limited to this, and can also be set according to actual needs, which is not specifically limited here.
[0058] The leading progress value is calculated based on the synchronous progress difference of the leading progress difference type. For example, each synchronous progress difference of the leading progress difference type is calculated with the approved progress difference to obtain each leading ratio difference, and all leading ratio differences are summed to obtain the total leading ratio difference, which is marked as Kd, and the total number of times the synchronous progress difference is marked as the leading progress difference is obtained, which is marked as Ra. The leading progress value Hs is obtained by using the formula Hs=Kd×b1+Ra×b2, wherein the third coefficient b1 is the leading total ratio difference coefficient, and the fourth coefficient b2 is the leading progress quantity coefficient. In the embodiment of the present application, the value of b1 is 0.66, and the value of b2 is 0.76. Of course, in the present application, b1 and b2 are not limited to this, and can also be set according to actual needs, which is not specifically limited here.
[0059] In the embodiment of the present application, the backward progress value can be accurately calculated through the backward total ratio difference and the backward progress quantity in the synchronous progress difference of the backward progress difference type. Similarly, the backward progress value can be calculated through the leading total ratio difference and the leading progress quantity in the synchronous progress difference of the leading progress difference type.
[0060] In some embodiments, the above S103 may specifically include:
[0061] When the synchronization verification value is less than the preset synchronization verification threshold, it is determined that the synchronization data is out of synchronization, and the synchronization data of the synchronization terminal is marked as out of synchronization.
[0062] The above-mentioned preset synchronization verification threshold, for example, may be 5.5. Of course, in the embodiment of the present application, the synchronization verification threshold is not limited to a fixed value, but may also be set according to actual needs of the user, which is not specifically limited here.
[0063] In the embodiment of the present application, when the synchronization verification value is less than a preset synchronization verification threshold, it can be determined that the synchronization data is out of synchronization, and the synchronization data of the synchronization terminal can be marked as out of synchronization.
[0064] As another implementation of the present application, in order to intuitively understand the data synchronization status of the abnormal synchronization terminal, after the above S103, the above method may further include:
[0065] Mark the synchronous terminal as an abnormal synchronous terminal;
[0066] Obtaining the marking information of the abnormal synchronization terminal, the marking information includes the historical marking time and the historical marking times;
[0067] Calculate the abnormal marking value of the abnormal synchronization terminal according to the historical marking time and the historical marking number;
[0068] The abnormal mark value is compared with a preset abnormal mark low value and an abnormal mark high value to determine the abnormal type of the abnormal synchronization terminal.
[0069] The above-mentioned marking information may be the historical record of the abnormal synchronization terminal, including the historical marking time and the historical marking number. The historical marking time is used to represent the historical moments when the synchronization terminal is marked as an abnormal synchronization terminal, and the historical marking number is used to represent the historical times when the synchronization terminal is marked as an abnormal synchronization terminal.
[0070] The above-mentioned calculation of the abnormal marking value of the abnormal synchronization terminal based on the historical marking moment and the historical marking number can, for example, be to calculate at least one abnormal marking interval based on the historical marking moment, the abnormal marking interval being the time difference between adjacent marking moments in the historical marking moment; the average of at least one abnormal marking interval is determined as the abnormal marking average interval; the abnormal marking value is calculated by combining the abnormal marking average interval and the historical marking number.
[0071] The above-mentioned comparison of the abnormal mark value with the preset abnormal mark low value and the abnormal mark high value to determine the abnormal type of the abnormal synchronization terminal, exemplarily, can be that when the abnormal mark value is greater than the preset abnormal mark high value, the abnormal type of the abnormal synchronization terminal is determined to be a low-frequency abnormal type; when the abnormal mark value is greater than or equal to the preset abnormal mark low value, and the abnormal mark value is less than the abnormal mark high value, the abnormal type of the abnormal synchronization terminal is determined to be a medium-frequency abnormal type; when the abnormal mark value is greater than the abnormal mark low value, the abnormal type of the abnormal synchronization terminal is determined to be a high-frequency abnormal type; the abnormal types include low-frequency abnormal type, medium-frequency abnormal type and high-frequency abnormal type.
[0072] In an embodiment of the present application, the abnormal marking value of the abnormal synchronization terminal can be calculated based on the historical marking time and historical marking number of the abnormal synchronization terminal, and compared with the preset abnormal marking low value and abnormal marking high value to determine the abnormal type of the abnormal synchronization terminal, thereby helping users to intuitively understand the data synchronization status of the abnormal synchronization terminal.
[0073] In some embodiments, the above-mentioned calculation of the abnormal marking value of the abnormal synchronization terminal according to the historical marking time and the historical marking number may specifically include:
[0074] At least one abnormal marking interval is calculated based on the historical marking moments, where the abnormal marking interval is the time difference between adjacent marking moments in the historical marking moments;
[0075] determining the mean of at least one abnormal marker interval as the abnormal marker mean interval;
[0076] The abnormal mark value is calculated based on the abnormal mark interval and the historical mark times.
[0077] The above-mentioned abnormal marking interval may be the time difference between adjacent marking moments in the historical marking moments.
[0078] The above abnormal mark interval is the average value of at least one abnormal mark interval.
[0079] The above-mentioned abnormal mark value is calculated based on the abnormal mark interval and the number of historical marks. For example, it can be calculated using the following formula:
[0080]
[0081] The abnormal mark value Ea is obtained, where Jr is the abnormal mark average interval, d1 is the abnormal mark average interval coefficient, Gm is the historical mark number, and d2 is the historical mark number coefficient. In the embodiment of the present application, the value of d1 is 0.37 and the value of d2 is 0.46. Of course, d1 and d2 in the present application are not limited to this, and can also be set according to actual needs, which is not specifically limited here.
[0082] In an embodiment of the present application, at least one abnormal marking interval is calculated based on the historical marking moment, and the average of at least one abnormal marking interval is determined as the abnormal marking average interval. Finally, based on the abnormal marking average interval and the historical marking times, the abnormal marking value can be accurately calculated, thereby improving the accuracy of the abnormal type of the abnormal synchronization terminal.
[0083] In some embodiments, comparing the abnormal mark value with a preset abnormal mark low value and an abnormal mark high value to determine the abnormal type of the abnormal synchronization terminal may specifically include:
[0084] In the case where the abnormal mark value is greater than the preset abnormal mark high value, determining that the abnormal type of the abnormal synchronization terminal is a low-frequency abnormal type;
[0085] When the abnormal mark value is greater than or equal to the preset abnormal mark low value, and the abnormal mark value is less than the abnormal mark high value, determining that the abnormal type of the abnormal synchronization terminal is an intermediate frequency abnormal type;
[0086] In the case where the abnormal mark value is greater than the abnormal mark low value, determining that the abnormal type of the abnormal synchronization terminal is a high-frequency abnormal type;
[0087] The abnormality types include low-frequency abnormality type, medium-frequency abnormality type and high-frequency abnormality type.
[0088] The above-mentioned abnormal mark low value and abnormal mark high value, exemplarily, can be to set the abnormal mark low value to 2 and set the abnormal mark high value to 5. When the abnormal mark value of abnormal synchronization terminal A is 3.8, abnormal synchronization terminal A is marked as a medium frequency abnormal terminal, when the abnormal mark value of abnormal synchronization terminal B is 5.5, abnormal synchronization terminal B is marked as a low frequency abnormal terminal, and when the abnormal mark value of abnormal synchronization terminal C is 1.4, abnormal synchronization terminal C is marked as a high frequency abnormal terminal.
[0089] In an embodiment of the present application, the abnormal mark value is compared with the preset abnormal mark low value and the abnormal mark high value, and the abnormal type of the abnormal synchronization terminal can be accurately determined among the low-frequency abnormal type, medium-frequency abnormal type and high-frequency abnormal type, thereby helping the user to intuitively understand the data synchronization status of the abnormal synchronization terminal.
[0090] In order to facilitate the understanding of the verification method of synchronization data in the embodiment of the present application, the actual application process of the verification method of synchronization data is described as follows:
[0091] The purpose of the present invention is to solve the problem that the current data synchronization system usually verifies the synchronization of data after the data synchronization is completed, which results in that the data synchronization verification is not timely, and the corresponding synchronization terminal cannot process the synchronization data accordingly during synchronization. In addition, it is impossible to intuitively understand the data synchronization effect of each synchronization terminal.
[0092] like Figure 2 As shown, a data synchronization method comprises the following steps:
[0093] Step 1: Store data and synchronize data between synchronization terminals;
[0094] Step 2: Verify the synchronized data and mark it as verified synchronized data or verified unsynchronized data;
[0095] Step 3: Mark the abnormal frequency of the synchronous terminal.
[0096] Example 1
[0097] A data synchronization system includes a data synchronization module and a synchronization verification module.
[0098] The data synchronization module is used to store data and synchronize data between synchronization terminals.
[0099] The synchronization verification module is used to verify and mark the synchronization data, specifically:
[0100] On the basis of the same time interval, the data synchronization progress is continuously detected, and the time interval includes but is not limited to detecting the data synchronization progress once every 2s, 3s, and 4s. The detected data synchronization progress is sorted in chronological order, and the data synchronization progress that is adjacent and sorted later after the sorting is marked as the post-sync progress, and the data synchronization progress that is adjacent and sorted earlier after the sorting is marked as the pre-sync progress. The difference between the post-sync progress and the pre-sync progress is calculated to obtain the synchronization progress difference (i.e., the synchronization progress difference mentioned above).
[0101] Reference Figure 3, set each synchronization progress difference to correspond to an approved progress difference (i.e., the approved progress difference value mentioned above), when the synchronization progress difference is less than the approved progress difference, mark the synchronization progress difference as a backward progress difference (equivalent to the backward progress difference type mentioned above), set the approved progress difference to 5, when the synchronization progress difference is 4, mark the synchronization progress difference as a backward progress difference, and obtain the backward progress value Bw, the backward progress value Bw is obtained by the following steps: calculate the difference between the approved progress difference and the backward progress difference to obtain the backward ratio difference, sum up all the backward ratio differences to obtain the total backward ratio difference, and mark it as Fm, obtain the total number of times the synchronization progress difference is marked as the backward progress difference (i.e., the number of backward progress mentioned above), and mark it as Py, and use the formula Bw=Fm×a1+Py×a2 to obtain the backward progress value Bw, wherein a1 is the total backward ratio difference coefficient (i.e., the first coefficient mentioned above), a2 is the backward progress number coefficient (i.e., the second coefficient mentioned above), the value of a1 is 0.67, and the value of a2 is 0.75. When the synchronous progress difference is ≥ the approved progress difference, the synchronous progress difference is marked as the leading progress difference (equivalent to the above-mentioned leading progress difference type), and the approved progress difference is set to 5. When the synchronous progress difference is 6, the synchronous progress difference is marked as the leading progress difference, and the leading progress value Hs is obtained. The leading progress value Hs is obtained by the following steps: the leading progress difference is calculated by difference between the leading progress difference and the approved progress difference to obtain the leading ratio difference, all the leading ratio differences are summed up to obtain the leading total ratio difference and marked as Kd, the total number of times the synchronous progress difference is marked as the leading progress difference (i.e. the above-mentioned leading progress number) is obtained and marked as Ra, and the leading progress value Hs is obtained by using the formula Hs=Kd×b1+Ra×b2, where b1 is the leading total ratio difference coefficient (i.e. the above-mentioned third coefficient), b2 is the leading progress number coefficient (i.e. the above-mentioned fourth coefficient), the value of b1 is 0.66, and the value of b2 is 0.76.
[0102] The synchronization verification value Rt is obtained by the following steps: Using the formula The synchronization verification value Rt is obtained, where c1 is the coefficient of the lagging progress value, c2 is the coefficient of the leading progress value, the value of c1 is 0.98, and the value of c2 is 0.97. The synchronization verification threshold is set to Mx. When the synchronization verification value Rt ≥ the synchronization verification threshold Mx, the synchronization data is marked as the verification synchronization data. When the synchronization verification value Rt < the synchronization verification threshold Mx, the synchronization data is marked as the verification non-synchronization data. The synchronization verification threshold is set to 5.5. When the synchronization verification value of the synchronization data a is 5.8, the synchronization data is marked as the verification synchronization data. When the synchronization verification value of the synchronization data b is 3.2, the synchronization data is marked as the verification non-synchronization data. A synchronization verification module is set up to verify and mark the synchronization data of the synchronization terminal, verify the synchronization data in time, and verify the synchronization of the data while synchronizing the data. Then, the synchronization terminal can be processed in time when the verification is not synchronized.
[0103] Example 2
[0104] Reference Figure 4 , based on Example 1, further comprising a synchronization evaluation module, the synchronization evaluation module is used to mark the abnormal frequency of the synchronization terminal, specifically:
[0105] When the synchronization data is marked as verified asynchronous data, the corresponding synchronization terminal is marked as a synchronization abnormal terminal (i.e., the above-mentioned abnormal synchronization terminal), and the marking record (equivalent to the above-mentioned marking information) of the same synchronization terminal being marked as a synchronization abnormal terminal before the current system time is obtained, and the marking record includes the marking time (equivalent to the above-mentioned historical marking moment). The abnormal marking value Ea is obtained; the abnormal marking value Ea is obtained by the following steps: sorting the marking records in the order of marking time, calculating the time difference between the adjacent marking times after sorting, and obtaining the abnormal marking interval, summing up all the abnormal marking intervals of the same synchronization terminal and taking the average, and obtaining the abnormal marking average interval Jr, and obtaining the total number of times the same synchronization terminal was marked as a synchronization abnormal terminal before the current system time (equivalent to the above-mentioned historical marking number), and marking it as Gm, using the formula The abnormal mark value Ea is obtained, where d1 is the abnormal mark spacing coefficient, d2 is the synchronous abnormal terminal number coefficient, the value of d1 is 0.37, and the value of d2 is 0.46.
[0106] Set the low value of the abnormal mark to Ne, set the high value of the abnormal mark to Sq, when the abnormal mark value ≥ the high value of the abnormal mark Sq, mark the synchronization terminal as a low-frequency abnormal terminal (equivalent to the above-mentioned low-frequency abnormal type), when the low value of the abnormal mark Ne ≤ the abnormal mark value < the high value of the abnormal mark Sq, mark the synchronization terminal as a medium-frequency abnormal terminal (equivalent to the above-mentioned medium-frequency abnormal type), when the abnormal mark value < the low value of the abnormal mark Ne, mark the synchronization terminal as a high-frequency abnormal terminal (equivalent to the above-mentioned high-frequency abnormal type). Set the low value of the abnormal mark to 2, set the high value of the abnormal mark to 5, when the abnormal mark value of the synchronization terminal A is 3.8, mark the synchronization terminal A as a medium-frequency abnormal terminal, when the abnormal mark value of the synchronization terminal B is 5.5, mark the synchronization terminal B as a low-frequency abnormal terminal, when the abnormal mark value of the synchronization terminal C is 1.4, mark the synchronization terminal C as a high-frequency abnormal terminal. Set the synchronization evaluation module, you can mark the synchronization terminal according to the marking record of the synchronization abnormal terminal, you can more intuitively understand the data synchronization effect of each synchronization terminal.
[0107] In the embodiment of the present application, a synchronization verification module is set up to verify and mark the synchronization data of the synchronization terminal, and to verify the synchronization data in time. The synchronization of the data is verified while the data is synchronized, and then the synchronization terminal can be processed in time when the verification is not synchronized. A synchronization evaluation module is set up to mark the synchronization terminal according to the marking record of the synchronization abnormal terminal, so that the data synchronization effect of each synchronization terminal can be more intuitively understood.
[0108] Based on the synchronization data verification method provided in the above embodiment, the present application also provides a specific implementation of the synchronization data verification device. Please refer to the following embodiment.
[0109] like Figure 5 As shown, the synchronization data verification device 500 provided in the embodiment of the present application may include the following modules: a first acquisition module 501 , a verification module 502 and a first marking module 503 .
[0110] A first acquisition module 501 is used to acquire data synchronization information of the synchronization data when the synchronization terminal performs data synchronization on the synchronization data;
[0111] A verification module 502, used to verify the synchronization data according to the data synchronization information, and generate a verification result of the synchronization data, where the verification result is used to indicate whether the synchronization data is synchronized;
[0112] The first marking module 503 is configured to mark the synchronization data of the synchronization terminal as being out of synchronization when the verification result indicates that the synchronization data is out of synchronization.
[0113] The verification device for synchronization data in the embodiment of the present application can obtain data synchronization information of synchronization data when the synchronization terminal performs data synchronization on the synchronization data; verify the synchronization data according to the data synchronization information and generate a verification result of the synchronization data, the verification result is used to indicate whether the synchronization data is synchronized; when the verification result indicates that the synchronization data is not synchronized, the synchronization data of the synchronization terminal is marked as not synchronized. In this way, in the embodiment of the present application, while the synchronization terminal performs data synchronization on the synchronization data, the synchronization of the data can be verified and the synchronization data that is not synchronized can be marked, so that the user can find the synchronization data that is not synchronized in time and perform corresponding processing.
[0114] In some embodiments, the data synchronization information includes multiple data synchronization progresses, and different data synchronization progresses correspond to different synchronization times. The verification module 502 may specifically include:
[0115] A first calculation unit is used to calculate at least one synchronization progress difference according to a plurality of data synchronization progresses, where the synchronization progress difference is a difference between a subsequent synchronization progress and a preceding synchronization progress among the plurality of data synchronization progresses;
[0116] A first determining unit is used to compare each synchronous progress difference with a preset approved progress difference to determine a progress difference type of each synchronous progress difference. The progress difference type includes a lagging progress difference type and a leading progress difference type. The lagging progress difference type is used to indicate that the synchronous progress difference is less than the approved progress difference, and the leading progress difference type is used to indicate that the synchronous progress difference is greater than or equal to the approved progress difference.
[0117] A second calculation unit, configured to calculate a lagging progress value and a leading progress value according to a progress difference type of at least one synchronous progress difference value;
[0118] The third calculation unit is used to calculate the synchronization verification value of the synchronization data according to the lagging progress value and the leading progress value.
[0119] The verification result includes a synchronization verification value.
[0120] In some embodiments, the second calculation unit may specifically include:
[0121] A first calculation subunit is configured to calculate a backward progress value according to the synchronous progress difference of the backward progress difference type, wherein the backward progress value is obtained by summing the backward total ratio difference multiplied by the first coefficient and the backward progress quantity multiplied by the second coefficient, wherein the backward total ratio difference is the sum of the differences between the synchronous progress difference of each backward progress difference type in at least one synchronous progress difference and the approved progress difference, and the backward progress quantity is the quantity of the synchronous progress difference of the backward progress difference type in at least one synchronous progress difference;
[0122] The second calculation subunit is used to calculate the leading progress value according to the synchronous progress difference of the leading progress difference type, where the leading progress value is obtained by summing the leading total ratio difference multiplied by the third coefficient and the leading progress quantity multiplied by the fourth coefficient, the leading total ratio difference is the sum of the differences between the synchronous progress differences of each leading progress difference type in at least one synchronous progress difference and the approved progress difference, and the leading progress quantity is the quantity of the synchronous progress differences of the leading progress difference type in at least one synchronous progress difference.
[0123] In some embodiments, the first marking module 503 may be specifically used to determine that the synchronization data is out of synchronization when the synchronization verification value is less than a preset synchronization verification threshold, and mark the synchronization data of the synchronization terminal as out of synchronization.
[0124] As another implementation of the present application, in order to intuitively understand the data synchronization status of the abnormal synchronization terminal, the above device 500 may also include:
[0125] A second marking module, used for marking the synchronization terminal as an abnormal synchronization terminal;
[0126] A second acquisition module is used to acquire the marking information of the abnormal synchronization terminal, where the marking information includes a historical marking time and a historical marking number;
[0127] A calculation module, used for calculating the abnormal marking value of the abnormal synchronization terminal according to the historical marking time and the historical marking number;
[0128] The determination module is used to compare the abnormal mark value with a preset abnormal mark low value and abnormal mark high value to determine the abnormal type of the abnormal synchronization terminal.
[0129] In some embodiments, the computing module may specifically include:
[0130] A fourth calculation unit is used to calculate at least one abnormal marking interval according to the historical marking moments, where the abnormal marking interval is a time difference between adjacent marking moments in the historical marking moments;
[0131] A second determining unit, configured to determine a mean value of at least one abnormal marker interval as an abnormal marker average interval;
[0132] The fifth calculation unit is used to calculate the abnormal mark value according to the abnormal mark interval and the historical marking times.
[0133] In some embodiments, the determination module may specifically include:
[0134] A first determining unit, configured to determine that the abnormal type of the abnormal synchronization terminal is a low-frequency abnormal type when the abnormal mark value is greater than a preset abnormal mark high value;
[0135] A second determination unit is used to determine that the abnormal type of the abnormal synchronization terminal is an intermediate frequency abnormal type when the abnormal mark value is greater than or equal to a preset abnormal mark low value and the abnormal mark value is less than the abnormal mark high value;
[0136] A third determining unit is used to determine that the abnormal type of the abnormal synchronization terminal is a high-frequency abnormal type when the abnormal mark value is greater than the abnormal mark low value;
[0137] The abnormality types include low-frequency abnormality type, medium-frequency abnormality type and high-frequency abnormality type.
[0138] Figure 6 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application is shown.
[0139] The electronic device may include a processor 601 and a memory 602 storing computer program instructions.
[0140] Specifically, the processor 601 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
[0141] The memory 602 may include a large capacity memory for data or instructions. By way of example and not limitation, the memory 602 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, the memory 602 may include a removable or non-removable (or fixed) medium. In appropriate cases, the memory 602 may be inside or outside the integrated gateway disaster recovery device. In a specific embodiment, the memory 602 is a non-volatile solid-state memory.
[0142] In certain embodiments, the memory 602 may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to an aspect of the present disclosure.
[0143] The processor 601 implements any one of the synchronization data verification methods in the above embodiments by reading and executing computer program instructions stored in the memory 602 .
[0144] In one example, the electronic device may further include a communication interface 603 and a bus 610. Figure 6 As shown, the processor 601, the memory 602, and the communication interface 603 are connected via a bus 610 and communicate with each other.
[0145] The communication interface 603 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.
[0146] Bus 610 includes hardware, software or both, and the parts of electronic equipment are coupled to each other. For example, but not limitation, bus may include accelerated graphics port (AGP) or other graphics bus, enhanced industrial standard architecture (EISA) bus, front side bus (FSB), hypertransport (HT) interconnection, industrial standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In appropriate cases, bus 610 may include one or more buses. Although the present application embodiment describes and shows a specific bus, the application considers any suitable bus or interconnection.
[0147] The electronic device can execute the verification method of synchronization data in the embodiment of the present application, thereby realizing the combination Figure 1 and Figure 5 A method and device for verifying synchronization data are described.
[0148] In addition, in combination with the synchronization data verification method in the above embodiment, the embodiment of the present application can provide a computer-readable storage medium for implementation. The computer-readable storage medium stores computer program instructions; when the computer program instructions are executed by the processor, any one of the synchronization data verification methods in the above embodiment is implemented.
[0149] In combination with the synchronization data verification method in the above embodiments, an embodiment of the present application may provide a computer program product. When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes any one of the synchronization data verification methods above.
[0150] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.
[0151] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.
[0152] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.
[0153] Aspects of the present disclosure are described above with reference to the flowchart and / or block diagram of the method, device (system) and computer program product according to the embodiment of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box 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, or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each box in the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can also be implemented by dedicated hardware that performs a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.
[0154] The above is only a specific implementation of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.
Claims
1. A method for verifying synchronization data, It is characterized in that include: When the synchronization terminal performs data synchronization on the synchronization data, acquiring data synchronization information of the synchronization data; Verifying the synchronization data according to the data synchronization information and generating a verification result of the synchronization data, wherein the verification result is used to indicate whether the synchronization data is synchronized; In a case where the verification result indicates that the synchronization data is out of synchronization, the synchronization data of the synchronization terminal is marked as out of synchronization.
2. The method according to claim 1, It is characterized in that The data synchronization information includes a plurality of data synchronization progresses, and different data synchronization progresses correspond to different synchronization times. The verifying the synchronization data according to the data synchronization information and generating the verification result of the synchronization data includes: Calculate at least one synchronization progress difference according to the plurality of data synchronization progresses, where the synchronization progress difference is a difference between a subsequent synchronization progress and a preceding synchronization progress in the plurality of data synchronization progresses; Compare each of the synchronous progress difference values with a preset approved progress difference value, and determine a progress difference type of each of the synchronous progress difference values, wherein the progress difference type includes a lagging progress difference type and a leading progress difference type, wherein the lagging progress difference type is used to indicate that the synchronous progress difference value is less than the approved progress difference value, and the leading progress difference type is used to indicate that the synchronous progress difference value is greater than or equal to the approved progress difference value; Calculate a lagging progress value and a leading progress value according to the progress difference type of the at least one synchronous progress difference value; The synchronization verification value of the synchronization data is calculated according to the lagging progress value and the leading progress value, The verification result includes the synchronization verification value.
3. The method according to claim 2, It is characterized in that The calculating the lagging progress value and the leading progress value according to the progress difference type of the at least one synchronous progress difference value comprises: According to the synchronous progress difference of the backward progress difference type, a backward progress value is calculated, wherein the backward progress value is obtained by summing the backward total ratio difference multiplied by the first coefficient and the backward progress quantity multiplied by the second coefficient, wherein the backward total ratio difference is the sum of the differences between the synchronous progress differences of each backward progress difference type in the at least one synchronous progress difference and the approved progress difference, and the backward progress quantity is the quantity of the synchronous progress differences of the backward progress difference type in the at least one synchronous progress difference; A leading progress value is calculated according to the synchronous progress difference of the leading progress difference type, wherein the leading progress value is obtained by summing the leading total ratio difference multiplied by the third coefficient and the leading progress quantity multiplied by the fourth coefficient, wherein the leading total ratio difference is the sum of the differences between the synchronous progress differences of each leading progress difference type in the at least one synchronous progress difference and the approved progress difference, and the leading progress quantity is the quantity of the synchronous progress differences of the leading progress difference type in the at least one synchronous progress difference.
4. The method according to claim 2, It is characterized in that When the verification result indicates that the synchronization data is not synchronized, marking the synchronization data of the synchronization terminal as not synchronized includes: In a case where the synchronization verification value is less than a preset synchronization verification threshold, it is determined that the synchronization data is out of synchronization, and the synchronization data of the synchronization terminal is marked as out of synchronization.
5. The method according to claim 1, It is characterized in that After marking the synchronization data of the synchronization terminal as out of synchronization, the method further includes: Marking the synchronization terminal as an abnormal synchronization terminal; Acquire the marking information of the abnormal synchronization terminal, wherein the marking information includes a historical marking time and a historical marking number; Calculating the abnormal marking value of the abnormal synchronization terminal according to the historical marking time and the historical marking number; The abnormal mark value is compared with a preset abnormal mark low value and an abnormal mark high value to determine the abnormal type of the abnormal synchronization terminal.
6. The method according to claim 5, It is characterized in that The calculating the abnormal marking value of the abnormal synchronization terminal according to the historical marking time and the historical marking number includes: According to the historical marking moments, at least one abnormal marking interval is calculated, where the abnormal marking interval is a time difference between adjacent marking moments in the historical marking moments; Determine the mean value of the at least one abnormal marker interval as the abnormal marker mean interval; An abnormal marking value is calculated according to the abnormal marking interval and the historical marking times.
7. The method according to claim 5, It is characterized in that The comparing the abnormal mark value with a preset abnormal mark low value and an abnormal mark high value to determine the abnormal type of the abnormal synchronization terminal includes: In a case where the abnormal mark value is greater than a preset abnormal mark high value, determining that the abnormal type of the abnormal synchronization terminal is a low-frequency abnormal type; When the abnormal mark value is greater than or equal to the preset abnormal mark low value, and the abnormal mark value is less than the abnormal mark high value, determining that the abnormal type of the abnormal synchronization terminal is an intermediate frequency abnormal type; In a case where the abnormal mark value is greater than the abnormal mark low value, determining that the abnormal type of the abnormal synchronization terminal is a high-frequency abnormal type; The abnormality type includes the low-frequency abnormality type, the medium-frequency abnormality type and the high-frequency abnormality type.
8. A verification device for synchronization data, It is characterized in that The device comprises: A first acquisition module, configured to acquire data synchronization information of the synchronization data when the synchronization terminal performs data synchronization on the synchronization data; A verification module, used to verify the synchronization data according to the data synchronization information, and generate a verification result of the synchronization data, wherein the verification result is used to indicate whether the synchronization data is synchronized; The first marking module is configured to mark the synchronization data of the synchronization terminal as being out of synchronization when the verification result indicates that the synchronization data is out of synchronization.
9. An electronic device, It is characterized in that The device comprises: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the method for verifying synchronization data as described in any one of claims 1 to 7 is implemented.
10. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the method for verifying synchronization data according to any one of claims 1 to 7 is implemented.
11. A computer program product, It is characterized in that When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes the method for verifying synchronization data as described in any one of claims 1 to 7.
