CN101216832A - Data synchronization process and device - Google Patents
Data synchronization process and device Download PDFInfo
- Publication number
- CN101216832A CN101216832A CNA2007103063905A CN200710306390A CN101216832A CN 101216832 A CN101216832 A CN 101216832A CN A2007103063905 A CNA2007103063905 A CN A2007103063905A CN 200710306390 A CN200710306390 A CN 200710306390A CN 101216832 A CN101216832 A CN 101216832A
- Authority
- CN
- China
- Prior art keywords
- data
- service
- updating
- services
- synchronization
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 27
- 230000001360 synchronised effect Effects 0.000 claims description 18
- 238000001914 filtration Methods 0.000 claims description 2
- 230000001960 triggered effect Effects 0.000 claims description 2
- 238000012544 monitoring process Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000012508 change request Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000000246 remedial effect Effects 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention embodiment provides a data synchronization method which comprises data update records that the data synchronization center obtains from each operation and the corresponding marks for successful update of operational data items in each data update record. The method includes the following steps: the data synchronization center inter-compares each update record to find out the data item that only is contained by some operation data update records and not by other operations; the other operations are objective operations; the data synchronization center sends a notification of updating the content of the data item to the objective operations, wherein the notification carries the updated data content of the data item obtained by the data synchronization; the objective operations update the saved data content of the data item after receiving the notification. The invention embodiment further provides a synchronization device. The technical proposal of the invention embodiment can as far as possible guarantee the data content synchronization of the data item which needs to be maintained synchronization by each operation.
Description
Technical Field
The present invention relates to the field of data synchronization technologies, and in particular, to a data synchronization method and apparatus.
Background
Different services usually maintain some same data, and if data on a certain service changes, the data maintained on other services also needs to be changed accordingly to keep the data on different services the same, that is, keep synchronization of related data maintained on different services.
In the prior art, a real-time synchronization center is established to control the synchronicity of data to be synchronized maintained in different services, that is, the global data synchronicity, and the specific method includes: when data on a certain service changes, the service initiates a data updating request, namely, a synchronization center is informed that the data needs to be updated, and the updated data is informed; then, the real-time synchronization center notifies other related services to update the data so as to maintain the synchronization of the global data, and if the other related services can complete the data update, the real-time synchronization center notifies the service data initiating the data update request that the synchronization is successful. The service for sending the data updating request is called source service for short, and other related services are called target services.
For the case of failure in updating data of a target service, the existing real-time synchronization center allows the target service to try updating operation for multiple times based on a fault-tolerant mechanism, and if the updating still fails, the real-time synchronization center usually takes one of the following measures to end the data synchronization operation, the measure is one: the real-time synchronization center identifies the data synchronization failure; and step two: and the real-time synchronization center informs the source service and the target service which is successfully updated of the data rollback operation of the target service, and the source service and the target service which is successfully updated of the data change the changed data back to the original data.
In the prior art, the two measures taken for the data synchronization failure in the prior art cannot provide a remedial measure for the data synchronization failure, for example, for the first measure, the real-time synchronization center only identifies the data which is not successfully synchronized, and actually, the data maintained in the source service and the target service are different, that is, the data in the source service and the target service are not synchronized; the essence of the second measure is that the data change operation is not accepted, and the data update on all services fails, so that although the data on the source service and the data on the target service can be kept synchronous, if the data change request comes from the user, the data change fails, and the user is troubled.
Therefore, data synchronization failure easily occurs in the related art data synchronization scheme.
Disclosure of Invention
The embodiment of the invention provides a data synchronization method, which ensures the synchronism of the data content of the data items needing to be synchronized maintained on each service as much as possible.
A method of data synchronization, comprising:
the data synchronization center acquires data updating records recorded by each service; recording the identification of the data item which is successfully updated on the corresponding service in each data updating record;
the data synchronization center compares the data updating records and finds out data items which are only recorded on the data updating records of part of services and are not recorded on the data updating records of other services; the other services are target services;
the data synchronization center sends a notice for updating the data content in the data item on the target service to the target service, wherein the notice carries the updated data content of the data item acquired by the data synchronization center; and after receiving the notice, the target service updates the stored data content of the data item.
The embodiment of the invention provides a data synchronization device, which ensures the synchronization of the data content of data items needing to be synchronized maintained on each service as much as possible.
A data synchronization apparatus, comprising: the device comprises a record acquisition unit, a comparison processing unit, a data content acquisition unit and a notification sending unit; wherein,
the record acquisition unit acquires data updating records recorded by each service; recording the identification of the data item which is successfully updated on the corresponding service in each data updating record;
the comparison processing unit compares the data updating records to find out data items which are only recorded on the data updating records of part of the services and are not recorded on the data updating records of other services; the other services are target services;
the data content acquisition unit acquires the data content of the updated data item;
and the notification sending unit is used for sending a notification for updating the data content in the data item to the target service, wherein the notification carries the updated data content of the data item acquired by the data synchronization center.
According to the technical scheme of the data updating method and the data synchronization device provided by the embodiment of the invention, the data items which are successfully updated on part of the services but not successfully updated on other services are found by comparing the recorded data updating records on each service, and the data contents of the data items which are successfully updated on other services are notified to be updated, so that the synchronism of the data contents of the data items which are maintained on each service and need to be synchronized can be ensured as much as possible.
Drawings
FIG. 1 is a flow chart of a real-time synchronization center synchronizing data between services in an embodiment of the present invention;
FIG. 2 is a flow chart of a method of data synchronization in an embodiment of the present invention;
FIG. 3 is a schematic structural diagram of a data synchronization apparatus according to an embodiment of the present invention;
fig. 4 is a flowchart of a data synchronization center monitoring data synchronization on a service according to an embodiment of the present invention.
Detailed Description
The technical solutions of the embodiments of the present invention are further described in detail below with reference to the accompanying drawings.
In the embodiment of the invention, the data which is not successfully synchronized by the real-time synchronization center is further synchronized to ensure that the data synchronization between services can be successfully executed as much as possible.
The synchronous processing of the real-time synchronization center on the data of each service in the embodiment of the invention is explained first. For convenience, three global services are set and are recorded as: service 0, service 1, service 2, and setting the modified data items as the nicknames of the users. Referring to fig. 1, fig. 1 is a flowchart of a real-time synchronization center synchronizing data between services according to an embodiment of the present invention, where the flowchart may include the following steps:
step 101, the data content of the data item, namely the user nickname, on the service 0 is updated, the service 0 records the data content, namely a new value, which is successfully updated, in the data update record stored in the service 0, the identification of the updated data item, namely the user nickname, is further recorded in the data update record, the service 0 sends a data synchronization request to the real-time synchronization center, and the new value of the user nickname is carried in the request.
In the embodiment of the invention, the service with successful data update records the data related information which is successfully updated, wherein the data related information comprises the data item identification and the data content, and the data related information recorded by the service forms the data update record. In the embodiment of the present invention, the data update record is recorded in the data update log file. In practical applications, the data update record may also be recorded in a database or exist in other storage forms.
And 102, after receiving the request sent by the service 0, the real-time synchronization center returns a data synchronization request response to the service 0.
In the embodiment of the invention, because the data which is not successfully synchronized by the real-time synchronization center is further synchronized in the following process, the real-time synchronization center can directly return a response which represents that the synchronization is successful to the service 0. In practice, however, the response may be set as desired.
And 103, the real-time synchronization center sends a data updating instruction to the service 1 and the service 2, wherein the instruction carries the identification of the user nickname and the new value of the user nickname.
Step 104, after receiving the data updating instruction of the real-time synchronization center, the service 1 updates the data item of the user nickname, replaces the originally stored user nickname with the new value of the user nickname, records the data content, namely the new value, which is updated successfully into the data updating log file stored in the service 1, further records the identification of the updated data item, namely the user nickname, in the data updating record, and returns a response indicating that the data updating is successful to the real-time synchronization center by the service 1.
And 105, after receiving the response returned by the service 1, the real-time synchronization center confirms that the data updating on the service 1 is successful, and ends the monitoring of the data updating operation of the service 1.
And step 106, the service 2 performs data updating, if the data updating operation fails, the service 2 does not record the relevant information of the data updating, and the service 2 returns a response indicating the updating failure to the real-time synchronization center.
Step 107, after receiving the response returned by the service 2, the real-time synchronization center executes a fault-tolerant operation, stores the service identifier, the data item identifier and the new data content related to the update failure into a data update failure queue, and judges whether the update failure frequency of the service 2 for updating the nickname data item of the user at this time exceeds the preset maximum frequency of updating attempts, if not, executes the operation of step 103 again, that is, sends a data update instruction to the service 2 again, and tries the data update operation again after the service 2 receives the data update instruction; if the data updating instruction exceeds the preset updating instruction, the data updating instruction is not sent to the service 2 any more, and the data updating failure on the service 2 is marked.
Step 107 represents the fault-tolerant capability of the real-time synchronization center, that is, after a certain service fails to update data, the real-time synchronization center gives the service an opportunity to update again, and if the service is still unsuccessfully updated after multiple opportunities of updating attempts are given, the real-time synchronization center confirms that the service fails to update data.
In the embodiment of the present invention, if the operation frequency of the service 2 for attempting to update the nickname of the user reaches the preset maximum number of times that the user can attempt to update, and the service cannot be updated successfully, the data update log file of the service 2 is not recorded with the data update record for updating the nickname of the user this time.
In addition, in the embodiment of the present invention, each data update log file may include contents shown in table one:
| project (Field) | Description (Description) |
| data_identity | Data item identification |
| timestamp | Updating timestamps |
| hash | Hash value of updated data content |
Watch 1
In the first table, the log file includes an identifier of the data item, an update time stamp of the updated data recorded in the log file, and a hash (hash) value of the updated data content, where the hash value may be calculated by using the MD5 algorithm for the new data content, and may be used by the system to verify whether the updated data content of the data item on each service is the same. For data with more complex data content or data items with higher security requirements on the data content, the hash value of the corresponding data content can be recorded in the log file. For data items with simpler data content and low requirement on the confidentiality of the data content, the specific data content can be directly recorded in the log file in order to obtain the updated data content. In practical application, the content of the data update log file can be configured as required, but at least the data item identifier which is successfully updated needs to be contained in the data update log file. The information that may be used to describe the data content, such as the hash value of the data content or the data content, is referred to as data content description information.
In the embodiment of the invention, the data synchronization condition of each service can be further monitored based on the data update record recorded on each service, so as to ensure the synchronization of the data content of the data items which are maintained on each service and need to be synchronized as much as possible. In the embodiment of the invention, the data synchronization center is adopted to monitor the data synchronization condition of each service.
Referring to fig. 2, fig. 2 is a flow chart of a data synchronization method in an embodiment of the present invention, where the flow may include the following steps:
Referring to fig. 3, fig. 3 is a schematic structural diagram of a data synchronization apparatus in an embodiment of the present invention, where the data synchronization apparatus, that is, the data synchronization center, may include: the device comprises a record acquisition unit, a comparison processing unit, a data content acquisition unit and a notification sending unit; wherein,
the record acquisition unit acquires data updating records recorded by each service; recording the identification of the data item which is successfully updated on the corresponding service in each data updating record;
the comparison processing unit compares the data update records acquired by the record acquisition unit and finds out data items which are only recorded on the data update records of part of services and are not recorded on the data update records of other services; the other services are target services;
the data content acquisition unit acquires the data content of the updated data item;
and the notification sending unit is used for sending a notification for updating the data content in the data item to the target service found by the comparison processing unit, wherein the notification carries the updated data content of the data item acquired by the data content acquiring unit.
In the embodiment of the present invention, if the updated data content is recorded in a data update record of a part of services, such as a log file, the data synchronization center may directly obtain the updated data content of the data item to be updated of the target service from the log file, and if there is no related record in the log file, the data synchronization center may obtain the updated data content from the source service. As mentioned before, the so-called source service is the service that initiates the data update request, such as service 0 described above.
In the embodiment of the invention, the data synchronization center can be set to start at regular time, and the data synchronization center synchronously monitors the data on the global service. Referring to fig. 4, fig. 4 is a flowchart of a data synchronization center monitoring data synchronization on services in an embodiment of the present invention, in the process, data update records stored in each service are set as log files. The process may include the steps of:
step 401, the data synchronization center sends an instruction for acquiring a data update log file to each service.
Step 402, after receiving the instruction sent by the data synchronization center, the service 0 to the service 2 send the respective saved data update log files to the data synchronization center.
In the embodiment of the invention, data updating records are reserved in the log file once each time each service updates data.
Step 403, after receiving the log file returned by each service, the data synchronization center compares the data update information recorded in each log file to find out the data update record which is recorded in the log file of part of the services and not recorded in the log files of other services.
In the embodiment of the invention, the related information of the successfully updated data item recorded in the data updating record of each service takes the updating of the data item of the user nickname as an example, the log files of the service 0 and the service 1 have the data updating record of the data item of the user nickname at one time, and the log file of the service 2 does not have the data updating record of the user nickname, so that the data synchronization center finds out the data item of the user nickname.
Step 404, the data synchronization center sends an instruction for acquiring a new value of the user nickname to the service 0.
Step 405, after receiving the instruction sent by the data synchronization center, the service 0 returns the new value of the nickname of the user to the data synchronization center.
And step 406, after receiving the new value of the user nickname, the data synchronization center takes the service 2 as a target service, and sends a data updating instruction for requesting to update the data content of the user nickname to the service 2, wherein the instruction carries the new value of the user nickname.
Step 407, after receiving the data updating command sent by the data synchronization center, the service 2 performs an updating operation on the nickname of the user, and returns a response indicating that the data updating is successful to the data synchronization center after the updating is successful.
And step 408, after receiving the response returned by the service 2, the data synchronization center generates a global data state table by using the acquired data update states stored in the service 0 to the service 2, and stores the global data state table.
The global data state table may record an identifier of a data item that is successfully updated on each service, data content description information, and a timestamp of when the data item is successfully updated on the global service.
The process flow shown in fig. 4 may end.
The role of the global data state table is explained below.
If the user nickname on service 0 is updated again, service 0 will record the data update record on its data update log file. And, the service 0 will inform the real-time synchronization center again to inform the service 1 to perform the data synchronization operation with the service 2. If the service 2 successfully updates the data content of the nickname of the user, but before the service 2 writes the update record of the nickname of the user into the data update log file, the data synchronization center is restarted, the log file of the service 2 still has no record that the nickname of the user is modified again on the data update log file of each service acquired by the data synchronization center, so that the data synchronization center still notifies the service 2 to update the data content of the nickname of the user once again, the data content of the nickname of the user on the service 2 is updated twice, the updated data contents of the two times are the same, and the service 2 leaves the data update records of the two times on the data update log file thereof. And the data synchronization center updates the data content of the user nickname in the data state table.
Then, when the data synchronization center is restarted, after the data synchronization center acquires the data update records from the service 0 to the service 2, the user nickname recorded in the data update log file of the service 2 is updated more than the user nickname recorded in the service 0 and the service 1, so that the data synchronization center can find out the user nickname. At this moment, the data synchronization center does not directly send a data updating instruction to the service 0 and the service 1, but compares whether the data content description information of the user nickname in the stored data state table is the same as the data content description information of the user nickname obtained from the service 2, if so, the data synchronization center does not send a data updating instruction requiring updating of the user nickname to the service 0 and the service 1 any more, thereby avoiding that the synchronized data on each service is repeatedly updated and the normal operation of each service is influenced; if the service data are different from the service data, the data synchronization center determines that the service 0 and the service 1 need to be notified to update the data content of the user nickname, and sends a data updating instruction for updating the data content of the user nickname to the service 0 and the service 1, so that the data synchronization on each service is maintained.
Accordingly, referring to fig. 3, the apparatus of fig. 3 may further include a data state storage unit, an update filter unit, wherein,
the data state storage unit is used for storing the related information of the synchronized data items on each service, namely storing the data state table, wherein the related information can report the identification of the successfully updated data items on the global service, the description information of the data content, the time stamp of the successfully updated data items on the global service and the like as mentioned above;
and the updating filtering unit is used for comparing the data content description information of the data item stored in the data state storage unit with the data content description information of the data item in the data updating record on the target service acquired by the record acquisition unit, if so, the data content description information of the data item is not processed, and if not, the notification sending unit is triggered.
In summary, according to the technical solutions of the data updating method and the data synchronization apparatus provided in the embodiments of the present invention, by comparing the data updating records recorded in each service, the data item that is updated successfully on part of the services but not updated successfully on other services is found, and the other services are notified to update the data content of the data item, so that the synchronicity of the data content of the data item that needs to be synchronized and is maintained on each service can be ensured as much as possible.
Furthermore, in the embodiment of the present invention, a real-time synchronization center and a data synchronization center can be combined to perform synchronization processing on the data content of the data items that need to be synchronized on each service, so that the data synchronization reliability and timeliness are ensured while the synchronization of the data content of each data item is ensured.
Claims (10)
1. A method of data synchronization, comprising:
the data synchronization center acquires data updating records recorded by each service; recording the identification of the data item which is successfully updated on the corresponding service in each data updating record;
the data synchronization center compares the data updating records and finds out data items which are only recorded on the data updating records of part of services and are not recorded on the data updating records of other services; the other services are target services;
the data synchronization center sends a notice for updating the data content in the data item on the target service to the target service, wherein the notice carries the updated data content of the data item acquired by the data synchronization center; and after receiving the notice, the target service updates the stored data content of the data item.
2. The method of claim 1, wherein before the data synchronization center notifies the target service to update the data content in the data item, the method further comprises:
the data synchronization center finds out the data content description information of the data item from the pre-stored global data state information which records the related information of the data item which is successfully updated on each service, compares whether the data content description information of the data item recorded in the global data state information is the same as the data content description information of the data item recorded on the data updating record of the partial service, and determines that the target service needs to be notified to update the data content in the data item if the comparison result is different.
3. The method of claim 2, wherein the data content description information comprises: specific data content and/or hash value of data content.
4. The method of claim 1, wherein after receiving the notification and performing update processing on the data content of the stored data item, the target service further comprises:
and the data synchronization center stores the related information of the data items which are updated successfully on each service.
5. The method according to claim 2 or 4, wherein the related information comprises: identification of the data item, data content description information, and a timestamp of when the data item was successfully updated on each service.
6. The method of claim 1, wherein before the data synchronization center obtains the data update record for each business record, the method further comprises:
the real-time synchronization center informs other services except the one or more services of updating the data which indicates the need of updating in the data synchronization request according to the data synchronization request initiated by the one or more services;
the data updating record recorded by each service comprises: and the identification of the data item which is successfully updated by the one or more services, and the identification of the data item which is successfully updated by the services except the one or more services.
7. The method of claim 6, wherein before the real-time synchronization center notifies other services except the one or more services to update the data indicating the need for updating in the data update request, the method further comprises:
and the real-time synchronization center returns a response of the data updating request to the one or more services.
8. The method of claim 1, wherein the data synchronization center is started periodically.
9. A data synchronization apparatus, comprising: the device comprises a record acquisition unit, a comparison processing unit, a data content acquisition unit and a notification sending unit; wherein,
the record acquisition unit acquires data updating records recorded by each service; recording the identification of the data item which is successfully updated on the corresponding service in each data updating record;
the comparison processing unit compares the data updating records to find out data items which are only recorded on the data updating records of part of the services and are not recorded on the data updating records of other services; the other services are target services;
the data content acquisition unit acquires the data content of the updated data item;
and the notification sending unit is used for sending a notification for updating the data content in the data item to the target service, wherein the notification carries the updated data content of the data item acquired by the data synchronization center.
10. The apparatus of claim 9, further comprising:
a data state storage unit, an update filter unit, wherein,
the data state storage unit is used for storing the related information of the synchronized data items on each service;
and the updating filtering unit is used for comparing the data content description information of the data item stored in the data state storage unit with the data content description information of the data item in the data updating record on the target service, if so, the data content description information of the data item is not processed, and if not, the notification sending unit is triggered.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2007103063905A CN101216832A (en) | 2007-12-28 | 2007-12-28 | Data synchronization process and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2007103063905A CN101216832A (en) | 2007-12-28 | 2007-12-28 | Data synchronization process and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101216832A true CN101216832A (en) | 2008-07-09 |
Family
ID=39623264
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2007103063905A Pending CN101216832A (en) | 2007-12-28 | 2007-12-28 | Data synchronization process and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101216832A (en) |
Cited By (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010148762A1 (en) * | 2009-12-31 | 2010-12-29 | 中兴通讯股份有限公司 | Method for finding, updating and synchronizing modified record item and data synchronizing device |
| CN102143194A (en) * | 2010-06-10 | 2011-08-03 | 华为技术有限公司 | Data synchronization method and system, immediate data node and terminal data node |
| CN102413154A (en) * | 2010-09-21 | 2012-04-11 | 北大方正集团有限公司 | Method of data information synchronization between systems and apparatus thereof |
| CN102523499A (en) * | 2011-12-06 | 2012-06-27 | 中兴通讯股份有限公司 | Method and device for acquiring channel list |
| CN102739706A (en) * | 2011-04-07 | 2012-10-17 | 腾讯科技（深圳）有限公司 | Method and system for carrying out data synchronization |
| CN102750283A (en) * | 2011-04-20 | 2012-10-24 | 阿里巴巴集团控股有限公司 | Massive data synchronization system and method |
| CN103559301A (en) * | 2013-11-14 | 2014-02-05 | 华为技术有限公司 | Method of data update, database trigger and SE (search engine) |
| CN103618615A (en) * | 2013-11-22 | 2014-03-05 | 厦门雅迅网络股份有限公司 | Method for handheld terminal to obtain information announcements in real time |
| CN103973727A (en) * | 2013-01-28 | 2014-08-06 | 深圳市腾讯计算机系统有限公司 | Data synchronizing method and device |
| CN104994179A (en) * | 2015-05-14 | 2015-10-21 | 深圳市腾讯计算机系统有限公司 | Data processing method and server |
| WO2016155492A1 (en) * | 2015-04-01 | 2016-10-06 | 阿里巴巴集团控股有限公司 | Remote data synchronization method and apparatus for database |
| CN106407350A (en) * | 2016-09-05 | 2017-02-15 | 广州视睿电子科技有限公司 | Method and device for filtering error log information |
| CN106407334A (en) * | 2016-09-05 | 2017-02-15 | 乐视控股（北京）有限公司 | Cache cluster updating method and apparatus |
| CN107103068A (en) * | 2017-04-18 | 2017-08-29 | 聚好看科技股份有限公司 | The update method and device of service buffer |
| CN107636644A (en) * | 2015-03-20 | 2018-01-26 | 迪安比商业信息解决方案公司 | System and method for keeping complementary company data uniformity in global distributed environment |
| CN107885824A (en) * | 2017-11-07 | 2018-04-06 | 北京锐安科技有限公司 | A kind of data read-write method and system |
| CN108628901A (en) * | 2017-03-23 | 2018-10-09 | 深圳市优朋普乐传媒发展有限公司 | A kind of data-updating method and device |
| CN108667881A (en) * | 2017-03-31 | 2018-10-16 | 中国科学院声学研究所 | A kind of synchronous method of the business datum of intelligent terminal and Cloud Server |
| CN109032747A (en) * | 2018-08-10 | 2018-12-18 | 江苏奇异点网络有限公司 | Data-updating method and device |
| CN110175182A (en) * | 2019-05-30 | 2019-08-27 | 口碑(上海)信息技术有限公司 | Verification of data method and device |
| CN115545679A (en) * | 2022-11-29 | 2022-12-30 | 明度智云(浙江)科技有限公司 | Experimental data matching method and device, computer equipment and storage medium |
| CN115599798A (en) * | 2022-11-29 | 2023-01-13 | 明度智云（浙江）科技有限公司（Cn） | Experiment data storage method and device, server and storage medium |
-
2007
- 2007-12-28 CN CNA2007103063905A patent/CN101216832A/en active Pending
Cited By (32)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU2010265607B2 (en) * | 2009-12-31 | 2014-01-16 | Zte Corporation | Method for finding, updating and synchronizing modified record item and data synchronizing device |
| WO2010148762A1 (en) * | 2009-12-31 | 2010-12-29 | 中兴通讯股份有限公司 | Method for finding, updating and synchronizing modified record item and data synchronizing device |
| CN102143194A (en) * | 2010-06-10 | 2011-08-03 | 华为技术有限公司 | Data synchronization method and system, immediate data node and terminal data node |
| CN102413154B (en) * | 2010-09-21 | 2014-04-09 | 北大方正集团有限公司 | Method of data information synchronization between systems and apparatus thereof |
| CN102413154A (en) * | 2010-09-21 | 2012-04-11 | 北大方正集团有限公司 | Method of data information synchronization between systems and apparatus thereof |
| CN102739706A (en) * | 2011-04-07 | 2012-10-17 | 腾讯科技（深圳）有限公司 | Method and system for carrying out data synchronization |
| CN102750283A (en) * | 2011-04-20 | 2012-10-24 | 阿里巴巴集团控股有限公司 | Massive data synchronization system and method |
| CN102523499A (en) * | 2011-12-06 | 2012-06-27 | 中兴通讯股份有限公司 | Method and device for acquiring channel list |
| CN103973727A (en) * | 2013-01-28 | 2014-08-06 | 深圳市腾讯计算机系统有限公司 | Data synchronizing method and device |
| CN103973727B (en) * | 2013-01-28 | 2019-03-19 | 深圳市腾讯计算机系统有限公司 | Method of data synchronization and device |
| CN103559301A (en) * | 2013-11-14 | 2014-02-05 | 华为技术有限公司 | Method of data update, database trigger and SE (search engine) |
| CN103618615A (en) * | 2013-11-22 | 2014-03-05 | 厦门雅迅网络股份有限公司 | Method for handheld terminal to obtain information announcements in real time |
| CN103618615B (en) * | 2013-11-22 | 2019-03-29 | 厦门雅迅网络股份有限公司 | A kind of method that handheld terminal obtains information bulletin in real time |
| CN107636644A (en) * | 2015-03-20 | 2018-01-26 | 迪安比商业信息解决方案公司 | System and method for keeping complementary company data uniformity in global distributed environment |
| US10891283B2 (en) | 2015-03-20 | 2021-01-12 | D&B Business Information Solutions | System and method for preserving interdependent corporate data consistency in a globally distributed environment |
| CN107636644B (en) * | 2015-03-20 | 2021-08-17 | 迪安比商业信息解决方案公司 | System and method for maintaining interdependent corporate data consistency in a globally distributed environment |
| WO2016155492A1 (en) * | 2015-04-01 | 2016-10-06 | 阿里巴巴集团控股有限公司 | Remote data synchronization method and apparatus for database |
| US10877990B2 (en) | 2015-04-01 | 2020-12-29 | Advanced New Technologies Co., Ltd. | Remote database synchronization |
| CN104994179A (en) * | 2015-05-14 | 2015-10-21 | 深圳市腾讯计算机系统有限公司 | Data processing method and server |
| CN104994179B (en) * | 2015-05-14 | 2018-12-11 | 深圳市腾讯计算机系统有限公司 | A kind of data processing method and server |
| CN106407334A (en) * | 2016-09-05 | 2017-02-15 | 乐视控股（北京）有限公司 | Cache cluster updating method and apparatus |
| CN106407350A (en) * | 2016-09-05 | 2017-02-15 | 广州视睿电子科技有限公司 | Method and device for filtering error log information |
| CN108628901A (en) * | 2017-03-23 | 2018-10-09 | 深圳市优朋普乐传媒发展有限公司 | A kind of data-updating method and device |
| CN108667881A (en) * | 2017-03-31 | 2018-10-16 | 中国科学院声学研究所 | A kind of synchronous method of the business datum of intelligent terminal and Cloud Server |
| CN107103068A (en) * | 2017-04-18 | 2017-08-29 | 聚好看科技股份有限公司 | The update method and device of service buffer |
| CN107885824A (en) * | 2017-11-07 | 2018-04-06 | 北京锐安科技有限公司 | A kind of data read-write method and system |
| CN109032747A (en) * | 2018-08-10 | 2018-12-18 | 江苏奇异点网络有限公司 | Data-updating method and device |
| CN109032747B (en) * | 2018-08-10 | 2021-10-15 | 江苏奇异点网络有限公司 | Data updating method and device |
| CN110175182A (en) * | 2019-05-30 | 2019-08-27 | 口碑(上海)信息技术有限公司 | Verification of data method and device |
| CN110175182B (en) * | 2019-05-30 | 2021-07-02 | 口碑(上海)信息技术有限公司 | Data checking method and device |
| CN115545679A (en) * | 2022-11-29 | 2022-12-30 | 明度智云(浙江)科技有限公司 | Experimental data matching method and device, computer equipment and storage medium |
| CN115599798A (en) * | 2022-11-29 | 2023-01-13 | 明度智云（浙江）科技有限公司（Cn） | Experiment data storage method and device, server and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101216832A (en) | Data synchronization process and device | |
| JP4732661B2 (en) | How to synchronize the client database with the server database | |
| WO2017177941A1 (en) | Active/standby database switching method and apparatus | |
| CN100449548C (en) | Method and system for synchronizing data base | |
| US7912858B2 (en) | Data synchronization method | |
| CN111427728B (en) | State management method, main/standby switching method and electronic equipment | |
| WO2021103499A1 (en) | Multi-active data center-based traffic switching method and device | |
| TWI677797B (en) | Management method, system and equipment of master and backup database | |
| CN112468601B (en) | Data synchronization method, access method and system of distributed storage system | |
| CN108600284B (en) | Ceph-based virtual machine high-availability implementation method and system | |
| US20110161724A1 (en) | Data management apparatus, monitoring apparatus, replica apparatus, cluster system, control method and computer-readable medium | |
| CN112698926B (en) | Data processing method, device, equipment, storage medium and system | |
| CN110324564B (en) | Video conference data synchronization method and device | |
| CN110704281A (en) | Method for monitoring system operation | |
| CN113596187B (en) | Domain name configuration management system | |
| CN108509296B (en) | Method and system for processing equipment fault | |
| CN116185697B (en) | Container cluster management method, device and system, electronic equipment and storage medium | |
| CN108009045B (en) | Method and device for processing faults of main and standby databases | |
| CN110716828B (en) | Database real-time backup method | |
| CN110928945B (en) | Data processing method and device for database and data processing system | |
| CN115114112A (en) | Data synchronization method and device | |
| CN113064950B (en) | Data synchronization method, device, equipment and storage medium | |
| CN112819600A (en) | Timed task execution method, timed task execution device, timed task execution equipment and computer storage medium | |
| CN112988708A (en) | Version updating method and device, computer readable storage medium and processor | |
| JPH07114495A (en) | Multiplexing file managing system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20080709 |