CN104065752A - Synchronization method of data between terminals - Google Patents
Synchronization method of data between terminals Download PDFInfo
- Publication number
- CN104065752A CN104065752A CN201410331468.9A CN201410331468A CN104065752A CN 104065752 A CN104065752 A CN 104065752A CN 201410331468 A CN201410331468 A CN 201410331468A CN 104065752 A CN104065752 A CN 104065752A
- Authority
- CN
- China
- Prior art keywords
- data
- user side
- segment data
- service end
- segment
- 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
Abstract
The invention relates to a synchronization method of data between terminals, and belongs to the technical field of computers. According to the method, data of a user side and a server side are stored in a segmented mode, each segment of data is provided with synchronization identification, and the user side sets the synchronization identification of modified segmented data as identification requiring synchronization when a user performs modification; furthermore, the segmented data with the identification requiring synchronization is synchronized with the server side; thus, when the data are synchronized, transmission quantity is smaller, data to be deleted are marked through deleting identification, data recovery is supported, and a perfect conflict resolution mechanism can be provided through a timestamp. In addition, the synchronization method of the data between the terminals is easy and convenient to apply and very wide in application range.
Description
Technical field
The present invention relates to field of computer technology, particularly And Methods of Computer Date Processing technical field, specifically refers to a kind of inter-terminal data synchronous method.
Background technology
Existing method of data synchronization, volume of transmitted data is large, and supported data does not recover, and Mechanism of Conflict Among is also perfect not, cannot define data collision settlement mechanism, thereby has synchronously formed obstacle for the data of each terminal room.
Therefore, how to provide a kind of, volume of transmitted data is less, and supported data recovers, and the method for data synchronization of perfect Mechanism of Conflict Among can be provided again, becomes the art problem demanding prompt solution.
Summary of the invention
The object of the invention is to have overcome above-mentioned shortcoming of the prior art, providing a kind of adopts data sectional storage and synchronizes, thereby while making data synchronous, transmission quantity is less, supported data recovers, can provide again perfect Mechanism of Conflict Among, and application process is easy, the inter-terminal data synchronous method having wide range of applications.
User side and service end all have database, the data of storing in described user side and the database of service end are divided into some sections of segment datas, segment data described in each section is provided with corresponding sync id, between user side and service end, connects by data-signal.For realizing above-mentioned object, inter-terminal data synchronous method of the present invention comprises the following steps:
(1) according to user's operation, a certain or some segment datas that user side is stored it are modified, and the sync id of modified segment data is set to " needing synchronous ";
(2) described user side sends synchronization request to described service end, and described synchronization request comprises the segment data of described sync id for " needs are synchronous ";
(3) described service end is received described synchronization request, and upgrades the database of service end according to the segment data in described synchronization request.
In this inter-terminal data synchronous method, described user side also stores Termination ID and the segment data ID of this user side, and described service end also stores segment data ID; Described synchronization request also comprises the Termination ID of this user side and the segment data ID that sync id is the segment data of " needs are synchronous "; Described step (3) specifically comprises the following steps:
(31) described service end is received described synchronization request, and obtains sync id for the segment data of " needing synchronous ", corresponding segment data ID and user side Termination ID;
(32) described service end is searched the data that whether have same segment data ID in service end database according to segment data ID; If have, enter step (33), if nothing enters step (34);
(33) described service end is replaced legacy data corresponding to same segment data ID by the segment data receiving, and storage, then enters step (35);
(34) segment data that described service end storing received arrives, then enters step (35);
(35) described service end records the user side Termination ID in the source of the segment data of upgrading.
In this inter-terminal data synchronous method, the segment data of storing in the database of described user side and service end is provided with corresponding deletion mark, and described step (1) specifically comprises the following steps:
(11), according to user's operation, described described being operating as of user side judgement rewritten or deleted, if rewrite, enters step (12), if delete, enters step (13);
(12) described user side is rewritten its memory segment data, and enters step (14);
(13) deletion of described user side institute memory segment data mark is set to " deleting ", and enters step (14);
(14) described user side is all set to the sync id of the segment data through rewriting and delete " needing synchronous ";
In this inter-terminal data synchronous method, described synchronization request also comprises that sync id is set to the corresponding deletion mark of segment data of " needs are synchronous ", and described step (33) specifically comprises the following steps:
(33-1) described service end is need to segment data be rewritten or be deleted according to deleting the described synchronization request of mark judgement, if rewrite, enters step (33-2), if delete, enters step (33-3);
(33-2) described service end is replaced legacy data corresponding to same segment data ID by the segment data receiving, and storage, then enters step (35);
(33-3) deletion of the described corresponding legacy data of service end segment data ID mark is set to " deleting ", then enters step (35).
In this inter-terminal data synchronous method, described service end stores the synchrodata table of comparisons and user side label table, and the described synchrodata table of comparisons comprises each segment data ID and deletion mark and the timestamp corresponding with each segment data ID; Described user side label table comprises each user side Termination ID and corresponding synchronization times;
Described step (33-2) is specially:
Described service end is replaced legacy data corresponding to same segment data ID by the segment data receiving, and storage, and revises timestamp corresponding to this segment data ID in the described synchrodata table of comparisons, then enters step (35);
Described step (33-3) is specially:
In the described service end synchrodata table of comparisons, the corresponding deletion mark of this segment data ID is set to " deleting ", then enters step (35);
Described step (34) is specially:
The segment data that described service end storing received arrives, and in the described synchrodata table of comparisons, set up this segment data ID and corresponding deletion mark and timestamp thereof, then enter step (35);
Described step (35) is specially:
Described service end is upgraded synchronization times corresponding to this user side Termination ID in described user side label table.
In this inter-terminal data synchronous method, described user side stores tables of data and synchronization times table, and described tables of data comprises each segment data ID and deletion mark and the sync id corresponding with each segment data ID; Described synchronization times table comprises user side ID and the corresponding synchronization times of this user side; Described step (2) specifically comprises the following steps:
(21) described user side sends synchronization request to described service end;
(22) described user side upgrades the synchronization times in described synchronization times table.
In this inter-terminal data synchronous method, described method is further comprising the steps of before in step (1):
(0) operate according to user, described user side and service end are carried out just subsynchronous, user side is downloaded and stores service end data, and service end is set up described the synchrodata table of comparisons and user side label table, and user side is set up described tables of data and synchronization times table.
Adopt the inter-terminal data synchronous method of this invention, due to its user side and the storage of service end employing data sectional, therefore in the time that data are synchronous, transmission quantity is less, simultaneously, utilize and delete the data that mark and label is deleted, thereby supported data recovers, and further can provide perfect Mechanism of Conflict Among by timestamp, and inter-terminal data synchronous method of the present invention, its application process is easy, and range of application is also quite extensive.
Brief description of the drawings
Fig. 1 is the flow chart of steps of inter-terminal data synchronous method of the present invention.
Fig. 2 is for utilizing inter-terminal data synchronous method of the present invention to realize the first hyposynchronous step schematic diagram.
Fig. 3 utilizes inter-terminal data synchronous method of the present invention to realize the step schematic diagram of subsequent synchronisation.
Embodiment
In order more clearly to understand technology contents of the present invention, describe in detail especially exemplified by following examples.
Referring to shown in Fig. 1, is the flow chart of steps of inter-terminal data synchronous method of the present invention.
In one embodiment, user side and service end all have database, the data of storing in described user side and the database of service end are divided into some sections of segment datas, segment data described in each section is provided with corresponding sync id, between user side and service end, connects by data-signal.This inter-terminal data synchronous method comprises the following steps:
(1) according to user's operation, a certain or some segment datas that user side is stored it are modified, and the sync id of modified segment data is set to " needing synchronous ";
(2) described user side sends synchronization request to described service end, and described synchronization request comprises the segment data of described sync id for " needs are synchronous ";
(3) described service end is received described synchronization request, and upgrades the database of service end according to the segment data in described synchronization request.
In execution mode more preferably, described user side also stores Termination ID and the segment data ID of this user side, and described service end also stores segment data ID; Described synchronization request also comprises the Termination ID of this user side and the segment data ID that sync id is the segment data of " needs are synchronous "; Described step (3) specifically comprises the following steps:
(31) described service end is received described synchronization request, and obtains sync id for the segment data of " needing synchronous ", corresponding segment data ID and user side Termination ID;
(32) described service end is searched the data that whether have same segment data ID in service end database according to segment data ID; If have, enter step (33), if nothing enters step (34);
(33) described service end is replaced legacy data corresponding to same segment data ID by the segment data receiving, and storage, then enters step (35);
(34) segment data that described service end storing received arrives, then enters step (35);
(35) described service end records the user side Termination ID in the source of the segment data of upgrading.
In further preferred embodiment, the segment data of storing in the database of described user side and service end is provided with corresponding deletion mark, and described step (1) specifically comprises the following steps:
(11), according to user's operation, described described being operating as of user side judgement rewritten or deleted, if rewrite, enters step (12), if delete, enters step (13);
(12) described user side is rewritten its memory segment data, and enters step (14);
(13) deletion of described user side institute memory segment data mark is set to " deleting ", and enters step (14);
(14) described user side is all set to the sync id of the segment data through rewriting and delete " needing synchronous ";
Further preferred embodiment in, described synchronization request also comprises that sync id is set to the corresponding deletion mark of segment data of " needs synchronous ", described step (33) specifically comprises the following steps:
(33-1) described service end is need to segment data be rewritten or be deleted according to deleting the described synchronization request of mark judgement, if rewrite, enters step (33-2), if delete, enters step (33-3);
(33-2) described service end is replaced legacy data corresponding to same segment data ID by the segment data receiving, and storage, then enters step (35);
(33-3) deletion of the described corresponding legacy data of service end segment data ID mark is set to " deleting ", then enters step (35).
And described service end stores the synchrodata table of comparisons and user side label table, the described synchrodata table of comparisons comprises each segment data ID and deletion mark and the timestamp corresponding with each segment data ID; Described user side label table comprises each user side Termination ID and corresponding synchronization times;
Described step (33-2) is specially:
Described service end is replaced legacy data corresponding to same segment data ID by the segment data receiving, and storage, and revises timestamp corresponding to this segment data ID in the described synchrodata table of comparisons, then enters step (35);
Described step (33-3) is specially:
In the described service end synchrodata table of comparisons, the corresponding deletion mark of this segment data ID is set to " deleting ", then enters step (35);
Described step (34) is specially:
The segment data that described service end storing received arrives, and in the described synchrodata table of comparisons, set up this segment data ID and corresponding deletion mark and timestamp thereof, then enter step (35);
Described step (35) is specially:
Described service end is upgraded synchronization times corresponding to this user side Termination ID in described user side label table.
In preferred execution mode, described user side stores tables of data and synchronization times table, and described tables of data comprises each segment data ID and deletion mark and the sync id corresponding with each segment data ID; Described synchronization times table comprises user side ID and the corresponding synchronization times of this user side; Described step (2) specifically comprises the following steps:
(21) described user side sends synchronization request to described service end;
(22) described user side upgrades the synchronization times in described synchronization times table.
And described method is further comprising the steps of before in step (1):
(0) operate according to user, described user side and service end are carried out just subsynchronous, user side is downloaded and stores service end data, and service end is set up described the synchrodata table of comparisons and user side label table, and user side is set up described tables of data and synchronization times table.
Inter-terminal data synchronous method of the present invention synchronization principles is in actual applications as follows:
Service end comprises synchrodata, the synchrodata table of comparisons and user side label table.Each line item of the synchrodata of database is added to insert trigger, update trigger, delete trigger.Trigger indicates associative operation in the synchrodata table of comparisons, and in the table of comparisons, records that number of operations increases progressively and timestamp.
Synchrodata table of comparisons structure is as follows:
| Id | isDelete | timestamp |
| Id is identical with former tables of data id | IsDelete represents whether delete | Timestamp record operating time stamp |
In the time that adding or revise, the data in database upgrade timestamp timestamp.
When deletion, isDelete is True and upgrades timestamp timestamp.
User side label table structure is as follows:
| Id | TimeStamp | SyncCount |
| User side id | Synchronized timestamp | Synchronization times |
When user side generates a sign to user side when access synchronized for the first time, record synchronized timestamp and number of times simultaneously, return to all data table related data.
User side comprises tables of data and synchronization times table.
Data list structure is as follows:
User side tables of data increases isDelete and isSync for synchronously in original row.
When user side has retouching operation, amendment isSync is that True indicates synchronously.
When user side has retouching operation, isDelete is that True amendment isSync is that True indicates synchronously.
Synchronization times list structure is as follows:
| Id | SyncCount |
| User side id | Synchronization times |
When user side is synchronous for the first time, submit request to, obtain synchronous marking and table data from server, insert and indicate table and tables of data.
When user side is later synchronous, having isSync is that True or isDelete are that True just submits Upload request to, submit to and indicate table sign and number of times, isSync is the mark row data (segment data) of True, server is that True mark row data id deletes server corresponding data according to isDelete, for False amendment or interpolation server data, server data table sign id and and the new sign table synchronization times finally returning to the server data newer than user side synchronized timestamp and revised or deleted.
User side is asked synchronous step as shown in Figure 2 for the first time, comprises the following steps:
101. user sides ask to submit to download request to generate synchronous marking and downloading data for the first time.
102. service ends generate data table related data and beacon information, return to user side.
103. user sides obtain beacon information and data table related data, data inserting storehouse.
Utilize step that inter-terminal data synchronous method of the present invention realizes subsequent synchronisation as shown in Figure 3, comprise the following steps:
201. user side requests are synchronous, submit to user side to indicate table information, submit to if user side isSync is True, and submitting together isSync to is the capable data of True.
202. service ends are synchronously processed:
First process the table data that user side is submitted to, isDelete is that True just deletes server data, and isDelete is that False just inserts user side server or amendment server data,
203. service ends are synchronously processed:
If discovery server data manipulation timestamp is larger than the timestamp of user side submission last time, and user side submits to these data to carry out synchronously revising and being solved by Mechanism of Conflict Among.
Utilize the explanation of Mechanism of Conflict Among in synchronous method of the present invention:
1, taking user side as main: by server related data according to user side request processing.
2, taking service end as main: by user side request msg, according to the treated result treatment of server.
Utilize the explanation of time data recovery mechanism in synchronous method of the present invention:
1, the each data of submitting to of user side are all carried out record, are convenient to data and recover.
If 2 recover data and do not want to reduce server indicate synchronization times, just all data are upgraded.
Adopt the inter-terminal data synchronous method of this invention, due to its user side and the storage of service end employing data sectional, therefore in the time that data are synchronous, transmission quantity is less, simultaneously, utilize and delete the data that mark and label is deleted, thereby supported data recovers, and further can provide perfect Mechanism of Conflict Among by timestamp, and inter-terminal data synchronous method of the present invention, its application process is easy, and range of application is also quite extensive.
In this specification, the present invention is described with reference to its specific embodiment.But, still can make various amendments and conversion obviously and not deviate from the spirit and scope of the present invention.Therefore, specification and accompanying drawing are regarded in an illustrative, rather than a restrictive.
Claims (7)
1. an inter-terminal data synchronous method, it is characterized in that, user side and service end all have database, the data of storing in described user side and the database of service end are divided into some sections of segment datas, segment data described in each section is provided with corresponding sync id, between user side and service end, connect by data-signal, described method comprises the following steps:
(1) according to user's operation, a certain or some segment datas that user side is stored it are modified, and the sync id of modified segment data is set to " needing synchronous ";
(2) described user side sends synchronization request to described service end, and described synchronization request comprises the segment data of described sync id for " needs are synchronous ";
(3) described service end is received described synchronization request, and upgrades the database of service end according to the segment data in described synchronization request.
2. inter-terminal data synchronous method according to claim 1, is characterized in that, described user side also stores Termination ID and the segment data ID of this user side, and described service end also stores segment data ID; Described synchronization request also comprises the Termination ID of this user side and the segment data ID that sync id is the segment data of " needs are synchronous "; Described step (3) specifically comprises the following steps:
(31) described service end is received described synchronization request, and obtains sync id for the segment data of " needing synchronous ", corresponding segment data ID and user side Termination ID;
(32) described service end is searched the data that whether have same segment data ID in service end database according to segment data ID; If have, enter step (33), if nothing enters step (34);
(33) described service end is replaced legacy data corresponding to same segment data ID by the segment data receiving, and storage, then enters step (35);
(34) segment data that described service end storing received arrives, then enters step (35);
(35) described service end records the user side Termination ID in the source of the segment data of upgrading.
3. inter-terminal data synchronous method according to claim 2, is characterized in that, the segment data of storing in the database of described user side and service end is provided with corresponding deletion mark, and described step (1) specifically comprises the following steps:
(11), according to user's operation, described described being operating as of user side judgement rewritten or deleted, if rewrite, enters step (12), if delete, enters step (13);
(12) described user side is rewritten its memory segment data, and enters step (14);
(13) deletion of described user side institute memory segment data mark is set to " deleting ", and enters step (14);
(14) described user side is all set to the sync id of the segment data through rewriting and delete " needing synchronous ".
4. inter-terminal data synchronous method according to claim 3, it is characterized in that, described synchronization request also comprises that sync id is set to the corresponding deletion mark of segment data of " needs are synchronous ", and described step (33) specifically comprises the following steps:
(33-1) described service end is need to segment data be rewritten or be deleted according to deleting the described synchronization request of mark judgement, if rewrite, enters step (33-2), if delete, enters step (33-3);
(33-2) described service end is replaced legacy data corresponding to same segment data ID by the segment data receiving, and storage, then enters step (35);
(33-3) deletion of the described corresponding legacy data of service end segment data ID mark is set to " deleting ", then enters step (35).
5. want the inter-terminal data synchronous method described in 4 according to right, it is characterized in that, described service end stores the synchrodata table of comparisons and user side label table, and the described synchrodata table of comparisons comprises each segment data ID and deletion mark and the timestamp corresponding with each segment data ID; Described user side label table comprises each user side Termination ID and corresponding synchronization times;
Described step (33-2) is specially:
Described service end is replaced legacy data corresponding to same segment data ID by the segment data receiving, and storage, and revises timestamp corresponding to this segment data ID in the described synchrodata table of comparisons, then enters step (35);
Described step (33-3) is specially:
In the described service end synchrodata table of comparisons, the corresponding deletion mark of this segment data ID is set to " deleting ", then enters step (35);
Described step (34) is specially:
The segment data that described service end storing received arrives, and in the described synchrodata table of comparisons, set up this segment data ID and corresponding deletion mark and timestamp thereof, then enter step (35);
Described step (35) is specially:
Described service end is upgraded synchronization times corresponding to this user side Termination ID in described user side label table.
6. want the inter-terminal data synchronous method described in 5 according to right, it is characterized in that, described user side stores tables of data and synchronization times table, and described tables of data comprises each segment data ID and deletion mark and the sync id corresponding with each segment data ID; Described synchronization times table comprises user side ID and the corresponding synchronization times of this user side; Described step (2) specifically comprises the following steps:
(21) described user side sends synchronization request to described service end;
(22) described user side upgrades the synchronization times in described synchronization times table.
7. want the inter-terminal data synchronous method described in 6 according to right, it is characterized in that, described method is further comprising the steps of before in step (1):
(0) operate according to user, described user side and service end are carried out just subsynchronous, user side is downloaded and stores service end data, and service end is set up described the synchrodata table of comparisons and user side label table, and user side is set up described tables of data and synchronization times table.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410331468.9A CN104065752A (en) | 2014-07-11 | 2014-07-11 | Synchronization method of data between terminals |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410331468.9A CN104065752A (en) | 2014-07-11 | 2014-07-11 | Synchronization method of data between terminals |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104065752A true CN104065752A (en) | 2014-09-24 |
Family
ID=51553279
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410331468.9A Pending CN104065752A (en) | 2014-07-11 | 2014-07-11 | Synchronization method of data between terminals |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104065752A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104462477A (en) * | 2014-12-18 | 2015-03-25 | 深圳市科漫达智能管理科技有限公司 | Data synchronizing method, device and system based on timestamp |
| CN104468569A (en) * | 2014-12-04 | 2015-03-25 | 北京国双科技有限公司 | Integrity detection method and device of distributed data |
| CN105915572A (en) * | 2015-12-12 | 2016-08-31 | 乐视移动智能信息技术（北京）有限公司 | Mobile terminal data conflict processing method and device |
| WO2017162079A1 (en) * | 2016-03-25 | 2017-09-28 | 阿里巴巴集团控股有限公司 | Data synchronization method and apparatus |
| CN109104501A (en) * | 2018-09-30 | 2018-12-28 | 北京奇虎科技有限公司 | A kind of method of data synchronization, apparatus and system |
| CN110674148A (en) * | 2019-08-30 | 2020-01-10 | 福建中信网安信息科技有限公司 | Data updating synchronization method and device for database |
| CN110769061A (en) * | 2019-10-24 | 2020-02-07 | 华为技术有限公司 | Data synchronization method and equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101247315A (en) * | 2007-02-12 | 2008-08-20 | 上海贝尔阿尔卡特股份有限公司 | Content synchronization method and apparatus for single-frequency network transmission |
| CN102054035A (en) * | 2010-12-29 | 2011-05-11 | 北京播思软件技术有限公司 | Data range-based method for synchronizing data in database |
| CN103428242A (en) * | 2012-05-18 | 2013-12-04 | 阿里巴巴集团控股有限公司 | Method, device and system for increment synchronization |
-
2014
- 2014-07-11 CN CN201410331468.9A patent/CN104065752A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101247315A (en) * | 2007-02-12 | 2008-08-20 | 上海贝尔阿尔卡特股份有限公司 | Content synchronization method and apparatus for single-frequency network transmission |
| CN102054035A (en) * | 2010-12-29 | 2011-05-11 | 北京播思软件技术有限公司 | Data range-based method for synchronizing data in database |
| CN103428242A (en) * | 2012-05-18 | 2013-12-04 | 阿里巴巴集团控股有限公司 | Method, device and system for increment synchronization |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104468569A (en) * | 2014-12-04 | 2015-03-25 | 北京国双科技有限公司 | Integrity detection method and device of distributed data |
| CN104468569B (en) * | 2014-12-04 | 2017-12-22 | 北京国双科技有限公司 | The integrality detection method and device of distributed data |
| CN104462477A (en) * | 2014-12-18 | 2015-03-25 | 深圳市科漫达智能管理科技有限公司 | Data synchronizing method, device and system based on timestamp |
| CN104462477B (en) * | 2014-12-18 | 2018-03-30 | 深圳市科漫达智能管理科技有限公司 | The method, apparatus and system of data syn-chronization based on timestamp |
| CN105915572A (en) * | 2015-12-12 | 2016-08-31 | 乐视移动智能信息技术（北京）有限公司 | Mobile terminal data conflict processing method and device |
| WO2017162079A1 (en) * | 2016-03-25 | 2017-09-28 | 阿里巴巴集团控股有限公司 | Data synchronization method and apparatus |
| CN109104501A (en) * | 2018-09-30 | 2018-12-28 | 北京奇虎科技有限公司 | A kind of method of data synchronization, apparatus and system |
| CN109104501B (en) * | 2018-09-30 | 2023-02-17 | 北京奇虎科技有限公司 | Data synchronization method, device and system |
| CN110674148A (en) * | 2019-08-30 | 2020-01-10 | 福建中信网安信息科技有限公司 | Data updating synchronization method and device for database |
| CN110769061A (en) * | 2019-10-24 | 2020-02-07 | 华为技术有限公司 | Data synchronization method and equipment |
| CN110769061B (en) * | 2019-10-24 | 2021-02-26 | 华为技术有限公司 | Data synchronization method and equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104065752A (en) | Synchronization method of data between terminals | |
| CN108074177B (en) | Data reconciliation method, system and computer-readable storage medium | |
| CN108628942B (en) | Block chain node equipment and data reading and writing method of distributed database | |
| CN107291869B (en) | Distributed service system and data query method thereof | |
| CN108388599B (en) | Electronic device, data migration and calling method and storage medium | |
| US20170161297A1 (en) | Data synchronization in a storage network | |
| CN103428242B (en) | A kind of method of increment synchronization, Apparatus and system | |
| CN108846753B (en) | Method and apparatus for processing data | |
| CN105243067A (en) | Method and apparatus for realizing real-time increment synchronization of data | |
| CN103152398A (en) | Method and system for file synchronization among multiple terminal files | |
| CN102195802A (en) | Terminal software transmission method, server and terminal | |
| CN105045770A (en) | Automatic document new version prompting method | |
| CN108536745B (en) | Shell-based data table extraction method, terminal, equipment and storage medium | |
| CN104462477A (en) | Data synchronizing method, device and system based on timestamp | |
| CN107656729B (en) | List view updating apparatus, method and computer-readable storage medium | |
| CN107092652B (en) | Navigation method and device for target page | |
| US20090319540A1 (en) | Synchronization adapter for synchronizing data to applications that do not directly support synchronization | |
| US20150193404A1 (en) | Operational transformations proxy for thin clients | |
| EP2988226A1 (en) | Electronic document data updating method and device | |
| US9311622B2 (en) | Resolving mutations in a partially-loaded spreadsheet model | |
| CN105847336A (en) | Address book synchronization method and device | |
| CN103761102A (en) | Unified data service platform and implementation method thereof | |
| CN104657387A (en) | Data query method and device | |
| CN105812469A (en) | Address book synchronization method and device | |
| CN103198100A (en) | Renaming method and renaming system for file synchronization among multiple devices |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20140924 |
|
| WD01 | Invention patent application deemed withdrawn after publication |