CN105812469A - Address book synchronization method and device - Google Patents
Address book synchronization method and device Download PDFInfo
- Publication number
- CN105812469A CN105812469A CN201610156376.0A CN201610156376A CN105812469A CN 105812469 A CN105812469 A CN 105812469A CN 201610156376 A CN201610156376 A CN 201610156376A CN 105812469 A CN105812469 A CN 105812469A
- Authority
- CN
- China
- Prior art keywords
- database table
- data
- synchrodata
- address book
- address list
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
Abstract
The invention discloses an address book synchronization method and device. The method comprises following steps of obtaining update data of a local address book; uploading the update data to a server, wherein the update data is used for updating a cloud address book in the server; and downloading synchronization data of which update time is later than the final update time of the local address book in the server, and synchronizing the local address book according to the synchronization data. According to the method and the device, the update data is uploaded firstly and then the synchronization data is downloaded when synchronization is carried out, therefore the synchronization error problem resulting from the fact that various terminals share a user account can be avoided, and the synchronization accuracy is improved.
Description
Technical field
The invention belongs to mobile terminal and communication technical field, particularly relate to a kind of address book synchronization method and device.
Background technology
What address list cloud of the prior art synchronization was generally adopted is all the simple mode covered, such as, address list in mobile phone is deleted, click synchronization again, directly the address list on Cloud Server will be replicated, but such method of synchronization there will be when multiple terminals share a user account cannot the problem of accurate synchronization.Such as when two mobile phones are used in conjunction with same user account, assume that First mobile phone have modified the telephone number of contact person in address list A, but do not revise the telephone number of contact person B, and second mobile phone have modified the telephone number of contact person in address list B, but do not revise the telephone number of contact person A, then according to the existing method of synchronization, owing to being direct duplication, then no matter how being synchronized by Cloud Server, that be finally modified is also in the telephone number of contact person A or the telephone number of contact person B.
Summary of the invention
The present invention provides a kind of address book synchronization method and device, aiming to solve the problem that the multiple terminals existed in prior art there will be when sharing a user account cannot the problem of accurate synchronization, synchrodata is downloaded again by first uploading more new data when synchronizing, the problem that the synchronization caused because of the shared user account of multiple terminals can be avoided to make mistakes, improves the accuracy synchronized.
The embodiment of the present invention provides a kind of address book synchronization method, including: obtaining the more new data of local address book, and uploaded onto the server by described more new data, described more new data is in order to update the high in the clouds address list in server；The synchrodata of the final updating time that the renewal time in described server is later than described local address book is downloaded, and according to described synchrodata, described local address book is synchronized.
The embodiment of the present invention provides a kind of address list synchronization device, including: acquisition module, for obtaining the more new data of local address book；Sending module, for being uploaded onto the server by described more new data, described more new data is in order to update the high in the clouds address list in server；Download module, the synchrodata for the renewal time in described server is later than the final updating time of described local address book is downloaded；Synchronization module, for synchronizing described local address book according to described synchrodata.
From the invention described above embodiment, first the more new data of local address book is uploaded onto the server when synchronizing local address book by mobile terminal, server is made to update high in the clouds address list according to more new data, then the synchrodata of the high in the clouds address list after data update is downloaded from server, high in the clouds address list after local address book being updated with data according to synchrodata carries out synchronize, can be prevented effectively from because multiple terminals share the problem that the synchronization that user account causes makes mistakes, improve the accuracy synchronized.
Accompanying drawing explanation
In order to be illustrated more clearly that the embodiment of the present invention or technical scheme of the prior art, the accompanying drawing used required in embodiment or description of the prior art will be briefly described below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those skilled in the art, under the premise not paying creative work, it is also possible to obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 be first embodiment of the invention provide a kind of address book synchronization method realize schematic flow sheet；
Fig. 2 be second embodiment of the invention provide a kind of address book synchronization method realize schematic flow sheet；
Fig. 3 is the structural representation of a kind of address list synchronization device that third embodiment of the invention provides；
Fig. 4 is the structural representation of a kind of address list synchronization device that fourth embodiment of the invention provides；
Fig. 5 is the structural representation of a kind of address list synchronization device that fifth embodiment of the invention provides；
Fig. 6 is the structural representation of a kind of address list synchronization device that sixth embodiment of the invention provides.
Detailed description of the invention
For making the goal of the invention of the present invention, feature, the advantage can be more obvious and understandable, below in conjunction with the accompanying drawing in the embodiment of the present invention, technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is only a part of embodiment of the present invention, and not all embodiments.Based on the embodiment in the present invention, the every other embodiment that those skilled in the art obtain under not making creative work premise, broadly fall into the scope of protection of the invention.
What refer to a kind of address book synchronization method that Fig. 1, Fig. 1 provide for first embodiment of the invention realizes schematic flow sheet.The address book synchronization method that the present embodiment provides can be applicable to have the mobile terminals such as the smart mobile phone of address book function, panel computer, Intelligent worn device, the present embodiment is the explanation carried out from mobile terminal side, as it is shown in figure 1, the method mainly comprises the steps that
S101, obtain local address book more new data, and will more new data upload onto the server, more new data is in order to update the high in the clouds address list in server；
It is to be appreciated that mobile terminal is preinstalled with client-side program, for performing each operation related in the present embodiment under the control of mobile terminal.When detecting that synchronous task is triggered, obtain current point in time and performed the more new data changed in local address book between the time point of the simultaneously operating of high in the clouds and local address book last time, and by this more new data upload onto the server so that server updates high in the clouds address list according to more new data.
As another embodiment of the present invention, record database table and system communication record database table at mobile terminal configuration Three-Part protocol.
System communication record database table is to be generated by system communication record, for recording each bar address list information and the related data of user's input.System communication record database table can be, but not limited to include following field: contact_id field, version field and for recording the field of each bar address list information in address list.
Wherein, contact_id is the only local identification identifier (Identity, ID) of every address list information, system communication record provide, and same address book data is in different clients, and the local ident of its correspondence is not unique.
Version is the revision number of each address book data, and each amendment all from increasing, can be provided by system communication record.
Address list information can be, but not limited to include: contact name, telephone number and contact address etc., and all associated contact information of same contact person are considered as an address list information.
When user revises the address list information in address list, system communication record operates according to the amendment of user, update the data that in system communication record database table, this amendment operation is pointed to, as: record in database table the address list information increasing, revise, delete correspondence at system communication, update corresponding value of version field etc..
Three-Part protocol record database table belongs to middle table, is recorded by Three-Part protocol and sets up incidence relation between database table cloud address book data and the system communication record data of mobile terminal this locality in the server.Three-Part protocol record database table (contact_data table) can be, but not limited to include following field: contact_id field, version field, cloud_id field, data_status field and for recording the field of each bar address list information in address list.
Wherein, cloud_id is every unique cloud ID of address book data the whole network, server provide, even same address book data is in different clients, the cloud ID of its correspondence is also unique.
Data_status is updating type indications, namely data additions and deletions change mark, for instance, as data_status=1, represent that the updating type (or wheel synchronization type) of corresponding data is newly-increased；During data_status=-1, represent that the updating type of corresponding data is for deleting；As data_status=0, represent that the updating type of corresponding data is amendment.
Contact_id, version in Three-Part protocol record database table and contact_id, version one_to_one corresponding in system communication record database table, for avoiding confusion, below Three-Part protocol is recorded the field contact_id in database table and version and is referred to as local_contact_id and local_version.
Specifically, the process that realizes obtaining the more new data of local address book may include that with system communication record database table for benchmark, system communication being recorded database table compare with Three-Part protocol record database table, the variance data recorded between database table and Three-Part protocol record database table by system communication obtains more new data.
Three-Part protocol is recorded database table by mobile terminal and system communication record database table is stored in set and contrasts, if contact_id exists, local_contact_id is absent from, then corresponding address book data is the data increased newly in system communication record database table；If contact_id exists, local_contact_id exists, version > local_version, then corresponding address book data is modified data；If contact_id is absent from, local_contact_id exists, then corresponding address book data has been recorded in database table from system communication and deleted.
Specifically, the process that realizes that more new data uploads onto the server be may comprise steps of:
Step one, variance data is synchronized to Three-Part protocol record database table；
Mobile terminal is by contrasting, obtain above-mentioned newly-increased, amendment, or the address book data deleted, and it is synchronized in Three-Part protocol record database table, specifically comprise the steps that in above-mentioned newly-increased or the address list information write Three-Part protocol record database table of amendment, and according to the contact_id of address book data that is above-mentioned newly-increased or that revise, the local_contact_id that version amendment is corresponding, local_version, make the related data in Three-Part protocol record database table record related data corresponding in database table with system communication and keep consistent, record, at Three-Part protocol, the data_status revising correspondence in database table is 0 (amendment) or 1 (increasing newly) simultaneously；Being recorded database table from Three-Part protocol by the address list information of above-mentioned deletion and delete, record the data_status revising correspondence in database table at Three-Part protocol be-1 (deletion) simultaneously.
If the step 2 method of synchronization is for amendment or deletes data, then the first synchrodata is sent to server, first synchrodata includes: in Three-Part protocol record database table, this amendment or the address list information deleted, the amendment of each bar or cloud identification information corresponding to address list information deleted and updating type indications, cloud identification information and updating type identifier are in order to be synchronized to high in the clouds address list by amendment or the address list information deleted；
If the step 3 method of synchronization is newly-increased data, then the second synchrodata is sent to server, second synchrodata includes: this newly-increased address list information in Three-Part protocol record database table, the second synchrodata is in order to be synchronized to high in the clouds address list by newly-increased address list information；
Step 4, receive the cloud identification information of described second synchrodata that described server returns, and the cloud identification information of described second synchrodata is write described Three-Part protocol record database table.
Server is according to whether including cloud ID in synchrodata, and the value of the data_status in synchrodata determines the method for synchronization, and wherein the first synchrodata includes cloud ID, and the second synchrodata does not include cloud ID.If the synchrodata that mobile terminal sends does not include cloud ID, it is determined that the method for synchronization is newly-increased data；If this synchrodata includes cloud ID and data_status=0, it is determined that the method for synchronization is amendment data；If this synchrodata includes cloud ID and data_status=-1；Then determine that the method for synchronization is delete data.
Specifically, if the method for synchronization is newly-increased data, in the Three-Part protocol record database table then sent by corresponding mobile terminal, newly-increased address list information increases in the table of cloud address book data storehouse, and in the table of cloud address book data storehouse, the data_status of this newly-increased address book data is revised as 1, generate corresponding cloud ID for this newly-increased address book data simultaneously, and by this cloud ID record at the correspondence position of cloud address book data storehouse table, it is handed down to mobile terminal simultaneously.
If the method for synchronization is amendment data, the Three-Part protocol then sent according to corresponding mobile terminal records the address list information of amendment in database table, related data in the table of amendment cloud address book data storehouse, and in the table of cloud address book data storehouse, the data_status of the address book data of this amendment is revised as 0.
If the method for synchronization is for deleting data, the data_status of the address book data being deleted in the Three-Part protocol record database table then sent by corresponding mobile terminal in the table of cloud address book data storehouse is revised as 0, understandably, delete data really not delete, simply revise indications, be judged as deleting for other client.
Server is also configured with update timetable, including the item_last_update_time field of the final updating time for recording each address book data.The time of the server updated, when carrying out each address book data and updating, is recorded in item_last_update_time field by server.
S102, the synchrodata of the final updating time that the renewal time in server is later than local address book are downloaded, and according to synchrodata, local address book are synchronized.
Specifically, the final updating time of bar address list information each in local address book is sent to server so that server, according to this final updating time, determines that the renewal time is later than the synchrodata of this final updating time the high in the clouds address list after updating from data；Receive the synchrodata that server returns, and according to synchrodata, local address book is synchronized.
As another embodiment of the present invention, Three-Part protocol is recorded the final updating time of each bar address book data in database table and is sent to server by mobile terminal, make server according to the final updating time, the high in the clouds address list after updating from data determines that the renewal time is later than the synchrodata of final updating time.
Server Three-Part protocol is recorded in database table final updating time (last_update_time) of each bar address book data of storage update with data after cloud address book data storehouse table corresponding to high in the clouds address list in final updating time (item_last_update_time) of each bar address book data of storing compare, by utilizing last_update_time < item_last_update_time as search condition, it is retrieved the synchrodata needing to be handed down to mobile terminal.This synchrodata includes: meet cloud_id and data_status corresponding to the address list information of last_update_time < item_last_update_time condition, this address list information and the final updating time at server in the table of cloud address book data storehouse.Preferably, in order to improve the accuracy of comparative result, the present invention relates to be all as the criterion with the system time of server if having time.
Mobile terminal receives the synchrodata that server returns, the high in the clouds address list after updating according to synchrodata, synchro system address book data storehouse table and data；Record the one-to-one relationship of the local identification information in database table and the local identification information in system communication record database table based on Three-Part protocol, Three-Part protocol is recorded database table with Tong Bu after system communication record database table and synchronize.
Specifically, first the address list information that the address list information in synchrodata is recorded in database table with system communication one by one is mated, address list information if there being the data matched, then according to the address list information in synchrodata, in amendment system communication record database table；If without the data matched, then being increased to by the address list information in synchrodata in system communication record database table, the address list information for newly increasing generates contact_id and version simultaneously.
Then, the contact_id of the address list information changed in database table is recorded according to system communication, record at Three-Part protocol and database table is searched the address list information with identical contact_id, if finding the address list information with identical contact_id, then record address list information corresponding for this contact_id in database table, address list information corresponding for this contact_id in amendment Three-Part protocol record database table according to system communication；If not finding the address list information with identical contact_id, then this contact_id and the address list information of correspondence thereof, version are increased in Three-Part protocol record database table.
Further, last in simultaneously operating, preferably, according to the server time of final updating in each bar address list information comprised in synchrodata high in the clouds address list after data update, address book data corresponding in system communication record database table and Three-Part protocol record database table is updated.
It should be noted that, in other embodiments, also can first according to synchrodata, synchronize the high in the clouds address list after Three-Part protocol record database table updates with data, then record the one-to-one relationship of the local identification information in database table and the local identification information in system communication record database table again based on Three-Part protocol, system communication is recorded database table with Tong Bu after Three-Part protocol record database table and synchronize.
Specifically, mobile terminal carries out the renewal of data by cloud_id, contact_id, data_status.First, update the data in Three-Part protocol record database table, record the data to be modified searching identical cloud_id and correspondence in database table at Three-Part protocol according to the cloud_id in the synchrodata that server issues, if not recording in database table at Three-Part protocol and finding identical cloud_id, then synchrodata being increased in Three-Part protocol record database table, the value of now corresponding version field is empty；If recording in database table at Three-Part protocol and finding identical cloud_id, and data_status=0, then according to the address list information in synchrodata, amendment Three-Part protocol record database table has the address list information of identical cloud_id, updates the value of corresponding version field；If recording in database table at Three-Part protocol and finding cloud_id and data_status=-1, then delete address list information and other related datas in Three-Part protocol record database table with identical cloud_id.And after the data in having updated Three-Part protocol record database table, the final updating time sent according to server updates last_update_time.
Then, one-to-one relationship and the Three-Part protocol of recording contact_id and the contact_id in system communication record database table in database table based on Three-Part protocol record the value of data_status field in database table, update the data in system communication record database table according to the Three-Part protocol record database table after updating.Specifically, contact_id according to the Three-Part protocol record database table after updating records the data to be modified searching identical contact_id and correspondence in database table at system communication, if recording in database table at system communication and finding identical contact_id, and data_status=0, then according to the address list information in the Three-Part protocol record database table after updating, amendment system communication record database table has the address list information of identical contact_id and updates the value of corresponding version field；If recording in database table at system communication and finding identical contact_id and data_status=-1, then deletion system address book data storehouse table has address list information and other related datas of identical contact_id；Three-Part protocol is recorded the address list information without contact_id in database table, increase to system communication record database table, now, system communication record is also recorded the address list information newly increased in database table and is generated the value of corresponding contact_id and version for system communication, mobile terminal controls above-mentioned client-side program and obtains the value of contact_id and version that system communication record generates, and writes position corresponding in Three-Part protocol record database table.
Thus it is synchronization with the cloud address book data storehouse table in server to be finally completed the local Three-Part protocol record database table of mobile terminal, system communication record database table.
Through checking, in the existing method of synchronization, it is assumed that mobile phone 1: number A is 123, number B is 1234；Mobile phone 2: number A is 123, number B is 1234；Cloud Server: number A is 123 number B is 1234.If it is 321 that the user of mobile phone 1 revises number A, it is 4321 that the user of mobile phone 2 revises number B, when then mobile phone 1 user synchronizes, number A in Cloud Server becomes 321, number B becomes 1234, if now the user of mobile phone 2 synchronizes again, number A in mobile phone 2 and Cloud Server becomes 321, number B becomes 1234, or the number A in mobile phone 2 and Cloud Server is turned into 123, number B becomes 4321, and actually now it is desirable that number A is become 321, number B is become 4321.
And use the address book synchronization method that the present embodiment provides to synchronize, under the same terms, if mobile phone 1 user synchronizes, then Cloud Server reversion code A is 321, number B is 1234, if now the user of mobile phone 2 synchronizes again, owing to amended content can first be synchronized to Cloud Server, so now the number B in Cloud Server is modified to 4321, then mobile phone 2 downloads synchrodata from Cloud Server again, now the number A of mobile phone 2 is modified to 321, number B remains as 4321, number A in Cloud Server is 321, number B is 4321, thus avoiding because multiple terminals share the problem that the synchronization that user account causes makes mistakes.
As another embodiment of the present invention, before step S101, further comprising the steps of:
S201, this locality build Three-Part protocol record database table, system communication is recorded the address book data in database table and imports in Three-Part protocol record database table, and the address book data of importing is sent to server so that server, according to the address book data received, builds high in the clouds address list；
The cloud identification information of each bar address book data that S202, reception server return, and write Three-Part protocol record database table.
Specifically, mobile terminal builds Three-Part protocol record database table in this locality, and Three-Part protocol record database table includes: Local ED field, revision field, cloud id field, updating type indicator field and for recording the field of each bar address list information in address list；System communication is recorded data import in Three-Part protocol record database table, and the address book data in the Three-Part protocol record database table after importing data to is sent to server；Owing to being synchronize first, server can generate corresponding ID for each bar address book data that mobile terminal sends and be handed down to mobile terminal, mobile terminal receives cloud ID corresponding to each bar address book data that server returns, and writes the cloud id field in Three-Part protocol record database table.
It should be noted that mobile terminal is also configured with synchronized update timetable Contact_update_time, including literary name section: last_update_time, for recording the time that each bar communication data finally synchronizes or updates.Mobile terminal system communication is recorded in data update address book data be synchronized to Three-Part protocol record database table after, the time of this synchronized update is recorded in last_update_time, then the time of the synchronized update of record and this hyposynchronous data is sent to server in the lump.The data synchronized include: newly-increased during this is subsynchronous, amendment or the communication information deleted, corresponding cloud ID (local_contact_id) and updating type indications (data_status).
A kind of address book synchronization method that the embodiment of the present invention provides, first the more new data of local address book is uploaded onto the server when synchronizing local address book by mobile terminal, server is made to update high in the clouds address list according to more new data, then the synchrodata of the high in the clouds address list after data update is downloaded from server, high in the clouds address list after local address book being updated with data according to synchrodata carries out synchronize, can be prevented effectively from because multiple terminals share the problem that the synchronization that user account causes makes mistakes, improve the accuracy synchronized.
What refer to a kind of address book synchronization method that Fig. 2, Fig. 2 provide for second embodiment of the invention realizes schematic flow sheet.The address book synchronization method that the present embodiment provides can be applicable in server, and the present embodiment is the explanation carried out from server side, as in figure 2 it is shown, the method mainly comprises the steps that
The more new data of the local address book in the mobile terminal that S301, reception mobile terminal are uploaded, according to more new data, updates high in the clouds address list；
Mobile terminal is when detecting that synchronous task is triggered, obtain current point in time and performed the more new data changed in local address book between the time point of the simultaneously operating of high in the clouds and local address book last time, and by this more new data be sent to server, server, according to this more new data, updates high in the clouds address list.
Further, mobile terminal is configured with Three-Part protocol record database table and system communication record database table, mobile terminal is when performing simultaneously operating, first Three-Part protocol is recorded database table and carries out synchronize with system communication record database table, with the concordance of both maintenances related data, then it is sent to server by updating the data recorded in database table at Three-Part protocol when synchronizing.Concrete update mode is referred to the corresponding contents in first embodiment shown in above-mentioned Fig. 1, repeats no more herein.
Mobile terminal will synchronize to the data in Three-Part protocol record database table and last synchronized update time of these data is sent to server.Wherein, difference according to the method for synchronization, when the method for synchronization is for amendment or when deleting data, synchrodata includes: amendment or the address list information deleted, the amendment of each bar or cloud identification information ID corresponding to address list information deleted and updating type indications data_status；When the method for synchronization is for newly-increased data, synchrodata includes: newly-increased address list information.Owing to cloud ID is generated by server, so when having in certain data mobile terminal and do not have in server, this data is the cloud ID not having correspondence in the terminal.
As another embodiment of the present invention, step S301 specifically includes:
The more new data that S3011, reception mobile terminal send；
If S3012 more new data is the first synchrodata, then based on the cloud identification information in the first synchrodata and updating type identifier, by the address list information in the first synchrodata in the way of amendment or deletion, it is synchronized to high in the clouds address list；
If S3013 more new data is the second synchrodata, then by the address list information in the second synchrodata in the way of newly-increased, it is synchronized to high in the clouds address list, and generate corresponding cloud identification information for newly-increased address list information, cloud identification information is sent to mobile terminal, and by cloud identification information recording address list beyond the clouds.
Specifically, the value that whether server includes the data_status in cloud ID and synchrodata according to the more new data that mobile terminal sends determines the method for synchronization.If this more new data be the first synchrodata, then include cloud ID.If this more new data be the second synchrodata, then do not include cloud ID.If the more new data that mobile terminal sends does not include cloud ID, it is determined that the method for synchronization is newly-increased data；If this more new data include cloud ID and data_status=0, it is determined that the method for synchronization for amendment data；If this more new data include cloud ID and data_status=-1；Then determine that the method for synchronization is delete data.
If the method for synchronization is newly-increased data, in the Three-Part protocol record database table then sent by corresponding mobile terminal, newly-increased address list information increases in the table of cloud address book data storehouse, and in the table of cloud address book data storehouse, the data_status of this newly-increased address book data is revised as 1, generate corresponding cloud ID for this newly-increased address book data simultaneously, and this cloud ID is recorded the correspondence position at cloud address book data storehouse table, it is handed down to mobile terminal simultaneously, make mobile terminal record in database table by this cloud ID record at Three-Part protocol, in order to use when synchronizing next time.
If the method for synchronization is amendment data, the Three-Part protocol then sent according to corresponding mobile terminal records the address list information of amendment in database table, related data in the table of amendment cloud address book data storehouse, and in the table of cloud address book data storehouse, the data_status of the address book data of this amendment is revised as 0.
If the method for synchronization is for deleting data, the data_status of the address book data being deleted in the Three-Part protocol record database table then sent by corresponding mobile terminal in the table of cloud address book data storehouse is revised as 0, understandably, delete data really not delete, simply revise indications, be judged as deleting for other client.
Server is also configured with update timetable, including the item_last_update_time field of the final updating time for recording each address book data.The time of the server updated, when carrying out each address book data and updating, is recorded in item_last_update_time field by server.
S302, the renewal time in the high in the clouds address list after data update that obtains are later than the synchrodata of the final updating time of local address book and are sent to mobile terminal, and synchrodata carries out synchronize in order to the high in the clouds address list after the local address book in mobile terminal being updated with data.
The synchrodata obtaining the high in the clouds address list after data update specifically includes: receive the final updating time of each bar address list information in the local address book that mobile terminal sends；High in the clouds address list after updating from data according to the final updating time determines that the renewal time is later than the synchrodata of final updating time.Wherein the data in the address list of high in the clouds can be stored in the table of cloud address book data storehouse.
Specifically, in cloud address book data storehouse table after the final updating time (last_update_time) of each bar address book data stored in the Three-Part protocol record database table that mobile terminal is uploaded by server and data renewal, the final updating time (item_last_update_time) of each bar address book data of storage compares, by utilizing last_update_time < item_last_update_time as search condition, it is retrieved the synchrodata needing to be handed down to mobile terminal.This synchrodata includes: meet the target communication record information of last_update_time < item_last_update_time condition in the table of cloud address book data storehouse, this target communication records cloud_id and data_status corresponding to information and final updating time.The synchrodata retrieved is sent to mobile terminal by server so that mobile terminal updates Three-Part protocol record database table and system communication record database table according to this synchrodata.The process that mobile terminal updates Three-Part protocol record database table and system communication record database table according to this synchrodata is specifically referred to the corresponding contents in first embodiment shown in Fig. 1, repeats no more herein.
As another embodiment of the present invention, before step S301, further comprising the steps of:
The address book data that S401, reception mobile terminal send, builds the high in the clouds address list of high in the clouds address list, and address book data writes high in the clouds address list；
S402, each bar address book data for write generate corresponding cloud identification information, and cloud identification information are sent to mobile terminal and by cloud identification information recording address list beyond the clouds.
Specifically, server receives the address book data in the newly constructed Three-Part protocol record database table that mobile terminal sends, build corresponding cloud address book data storehouse, namely high in the clouds address list is built, and this address book data is write in the table of cloud address book data storehouse, this address book data includes mobile terminal and records the address list information of database table importing Three-Part protocol record database table first from system communication, this cloud address book data storehouse table includes: cloud ID (cloud_id) field, updating type indications (data_status) field and for recording the field of each bar address list information；Generate corresponding cloud ID for each bar address book data, and cloud ID is sent to mobile terminal, and this cloud ID is recorded in this cloud id field.
Simultaneously, each bar address book data that server is write cloud address book data storehouse table generates the corresponding unique cloud ID of the whole network, the cloud ID record relevant position of cloud_id field in the table of cloud address book data storehouse that will generate, the cloud ID of generation is sent to mobile terminal so that each cloud ID record is recorded the relevant position of cloud_id field in database table at Three-Part protocol by mobile terminal simultaneously.
A kind of address book synchronization method that the embodiment of the present invention provides, the more new data of the local address book of the mobile terminal sent according to mobile terminal by server updates high in the clouds address list, the synchrodata of the high in the clouds address list after then data being updated again is sent to mobile terminal, can be prevented effectively from because multiple terminals share the problem that the synchronization that user account causes makes mistakes, improve the accuracy synchronized.
Refer to the structural representation that Fig. 3, Fig. 3 are a kind of address list synchronization devices that third embodiment of the invention provides, for the ease of illustrating, illustrate only the part relevant to the embodiment of the present invention.The address list synchronization device of Fig. 3 example can be the executive agent of a kind of address book synchronization method that aforementioned first embodiment provides, and it can be a functional module in mobile terminal or mobile terminal.The address list synchronization device of Fig. 3 example, specifically includes that acquisition module 501, sending module 502, download module 503 and synchronization module 504.Each functional module describes in detail as follows:
Acquisition module 501, for obtaining the more new data of local address book；
Sending module 502, for by this more new data upload onto the server, this more new data in order to update the high in the clouds address list in server；
Download module 503, the synchrodata for the renewal time in this server is later than the final updating time of local address book is downloaded；
Synchronization module 504, for according to this synchrodata, synchronizing this local address book.
Above-mentioned module realizes the detailed process of respective function and is referred to the related content of first embodiment shown in Fig. 1, repeats no more herein.
It should be noted that, in the embodiment of the address list synchronization device of above-mentioned Fig. 3 example, the division of each functional module is merely illustrative of, can be as required in practical application, the convenient consideration of the configuration requirement of such as corresponding hardware or the realization of software, and above-mentioned functions distribution is completed by different functional modules, it is divided into different functional modules by the internal structure of this device, to complete all or part of function described above.And, in practical application, corresponding functional module in the present embodiment can be realized by corresponding hardware, it is also possible to is performed corresponding software by corresponding hardware and completes (each embodiment that this specification provides all can apply foregoing description principle, below repeats no more).
A kind of address list synchronization device that the embodiment of the present invention provides, first the more new data of local address book is uploaded onto the server when synchronizing local address book by mobile terminal, server is made to update high in the clouds address list according to more new data, then the synchrodata of the high in the clouds address list after data update is downloaded from server, high in the clouds address list after local address book being updated with data according to synchrodata carries out synchronize, can be prevented effectively from because multiple terminals share the problem that the synchronization that user account causes makes mistakes, improve the accuracy synchronized.
Refer to the structural representation that Fig. 4, Fig. 4 are a kind of address list synchronization devices that fourth embodiment of the invention provides, for the ease of illustrating, illustrate only the part relevant to the embodiment of the present invention.With third embodiment of the invention shown in Fig. 3 provide a kind of address list synchronization device the difference is that, in the present embodiment:
Further, acquisition module 501, it is additionally operable to record database table for benchmark with system communication, this system communication being recorded database table compare with Three-Part protocol record database table, the variance data recorded between database table and this Three-Part protocol record database table by this system communication obtains this more new data.
Further, synchronization module 504, it is additionally operable to this variance data is synchronized to this Three-Part protocol record database table；
Sending module 502, if being additionally operable to the method for synchronization for amendment or to delete data, then the first synchrodata is sent to server, this first synchrodata includes: in this Three-Part protocol record database table, this amendment or the address list information deleted, the amendment of each bar or cloud identification information corresponding to address list information deleted and updating type indications, this cloud identification information and this updating type identifier in order to be synchronized to this high in the clouds address list by the address list information of this amendment or deletion；
Sending module 502, if being additionally operable to this method of synchronization for newly-increased data, then the second synchrodata is sent to this server, this second synchrodata includes: this newly-increased address list information in this Three-Part protocol record database table, this second synchrodata is in order to be synchronized to this high in the clouds address list by the address list information that this is newly-increased.
This device also includes:
Receiver module 601, for receiving the cloud identification information of this second synchrodata that this server returns；
Writing module 602, for writing this Three-Part protocol record database table by the cloud identification information of this second synchrodata.
Further, synchronization module 504, it is additionally operable to, according to this synchrodata, synchronize the high in the clouds address list after this system communication record database table updates with these data；And record the one-to-one relationship of the local identification information in database table and the local identification information in this system communication record database table based on this Three-Part protocol, this Three-Part protocol is recorded database table with Tong Bu after this system communication record database table and synchronize.
Further, this device also includes:
Build module 603, for building Three-Part protocol record database table in this locality, system communication is recorded the address book data in database table and imports in this Three-Part protocol record database table；
Sending module 502, is additionally operable to the address book data of importing is sent to this server so that this server, according to the address book data received, builds this high in the clouds address list；
Receiver module 601, is additionally operable to receive the cloud identification information of each bar address book data that this server returns；
Writing module 602, is additionally operable to write this Three-Part protocol record database table.
Above-mentioned module realizes the detailed process of respective function and is referred to the related content of first embodiment shown in Fig. 1, repeats no more herein.
A kind of address list synchronization device that the embodiment of the present invention provides, first the more new data of local address book is uploaded onto the server when synchronizing local address book by mobile terminal, server is made to update high in the clouds address list according to more new data, then the synchrodata of the high in the clouds address list after data update is downloaded from server, high in the clouds address list after local address book being updated with data according to synchrodata carries out synchronize, can be prevented effectively from because multiple terminals share the problem that the synchronization that user account causes makes mistakes, improve the accuracy synchronized.
Refer to the structural representation that Fig. 5, Fig. 5 are a kind of address list synchronization devices that fifth embodiment of the invention provides, for the ease of illustrating, illustrate only the part relevant to the embodiment of the present invention.The address list synchronization device of Fig. 5 example can be the executive agent of a kind of address book synchronization method that aforementioned second embodiment provides, and it can be a functional module in server or server.The address list synchronization device of Fig. 5 example, specifically includes that receiver module 701, more new module 702, acquisition module 703 and sending module 704.Each functional module describes in detail as follows:
Receiver module 701, for receiving the more new data of the local address book in this mobile terminal that mobile terminal is uploaded；
More new module 702, for according to this more new data, updating high in the clouds address list；
Acquisition module 703, is later than the synchrodata of the final updating time of local address book for obtaining the renewal time in the high in the clouds address list after data update；
Sending module 704, for this synchrodata is sent to this mobile terminal, this synchrodata carries out synchronize in order to the high in the clouds address list after the local address book in this mobile terminal being updated with these data.
Above-mentioned module realizes the detailed process of respective function and is referred to the related content of the second embodiment shown in Fig. 2, repeats no more herein.
A kind of address list synchronization device that the embodiment of the present invention provides, the more new data of the local address book of the mobile terminal sent according to mobile terminal by server updates high in the clouds address list, the synchrodata of the high in the clouds address list after then data being updated again is sent to mobile terminal, can be prevented effectively from because multiple terminals share the problem that the synchronization that user account causes makes mistakes, improve the accuracy synchronized.
Refer to the structural representation that Fig. 6, Fig. 6 are a kind of address list synchronization devices that sixth embodiment of the invention provides, for the ease of illustrating, illustrate only the part relevant to the embodiment of the present invention.With fifth embodiment of the invention shown in Fig. 5 provide a kind of address list synchronization device the difference is that, in the present embodiment:
Further, more new module 702, if be additionally operable to this more new data be the first synchrodata, then based on the cloud identification information in this first synchrodata and updating type identifier, by the address list information in this first synchrodata in the way of amendment or deletion, it is synchronized to high in the clouds address list；
More new module 702, if be additionally operable to this more new data be the second synchrodata, then by the address list information in this second synchrodata in the way of newly-increased, be synchronized to this high in the clouds address list；
This device also includes:
Generation module 801, generates corresponding cloud identification information for the address list information newly-increased for this；
Sending module 704, is additionally operable to this cloud identification information is sent to this mobile terminal；
Logging modle 802, is used for this cloud identification information recording in this high in the clouds address list.
Further, receiver module 701, it is additionally operable to receive the address book data that this mobile terminal sends；
This device also includes:
Build module 803, be used for building this high in the clouds address list, and this address book data is write this high in the clouds address list；
Generation module 801, is additionally operable to each bar address book data into write and generates corresponding cloud identification information；
Sending module 704, is additionally operable to this cloud identification information is sent to this mobile terminal；
Logging modle 802, is additionally operable to this cloud identification information recording at this high in the clouds address list.
Above-mentioned module realizes the detailed process of respective function and is referred to the related content of the second embodiment shown in Fig. 2, repeats no more herein.
A kind of address list synchronization device that the embodiment of the present invention provides, the more new data of the local address book of the mobile terminal sent according to mobile terminal by server updates high in the clouds address list, the synchrodata of the high in the clouds address list after then data being updated again is sent to mobile terminal, can be prevented effectively from because multiple terminals share the problem that the synchronization that user account causes makes mistakes, improve the accuracy synchronized.
In several embodiments provided herein, it should be understood that disclosed apparatus and method, it is possible to realize by another way.Such as, device embodiment described above is merely schematic, such as, the division of described module, being only a kind of logic function to divide, actual can have other dividing mode when realizing, for instance multiple modules or assembly can in conjunction with or be desirably integrated into another system, or some features can ignore, or do not perform.Another point, shown or discussed coupling each other or direct-coupling or communication connection can be through INDIRECT COUPLING or the communication connection of some interfaces, device or module, it is possible to be electrical, machinery or other form.
The described module illustrated as separating component can be or may not be physically separate, and the parts shown as module can be or may not be physical module, namely may be located at a place, or can also be distributed on multiple mixed-media network modules mixed-media.Some or all of module therein can be selected according to the actual needs to realize the purpose of the present embodiment scheme.
It addition, each functional module in each embodiment of the present invention can be integrated in a processing module, it is also possible to be that modules is individually physically present, it is also possible to two or more modules are integrated in a module.Above-mentioned integrated module both can adopt the form of hardware to realize, it would however also be possible to employ the form of software function module realizes.
If described integrated module is using the form realization of software function module and as independent production marketing or use, it is possible to be stored in a computer read/write memory medium.Based on such understanding, part or all or part of of this technical scheme that prior art is contributed by technical scheme substantially in other words can embody with the form of software product, this computer software product is stored in a storage medium, including some instructions with so that a computer equipment (can be personal computer, server, or the network equipment etc.) perform all or part of step of method described in each embodiment of the present invention.And aforesaid storage medium includes: USB flash disk, portable hard drive, read only memory (ROM, Read-OnlyMemory), the various media that can store program code such as random access memory (RAM, RandomAccessMemory), magnetic disc or CD.
It should be noted that, for aforesaid each embodiment of the method, in order to simplicity describes, therefore it is all expressed as a series of combination of actions, but those skilled in the art should know, the present invention is not by the restriction of described sequence of movement, because according to the present invention, some step can adopt other order or carry out simultaneously.Secondly, those skilled in the art also should know, it might not be all necessary to the present invention that embodiment described in this description belongs to preferred embodiment, involved action and module.
In the above-described embodiments, the description of each embodiment is all emphasized particularly on different fields, certain embodiment there is no the part described in detail, it is possible to referring to the associated description of other embodiments.
It it is more than the description to a kind of address book synchronization method provided by the present invention and device, for those skilled in the art, according to the thought of the embodiment of the present invention, all will change in specific embodiments and applications, to sum up, this specification content should not be construed as limitation of the present invention.
Claims (10)
1. an address book synchronization method, it is characterised in that described method includes:
Obtaining the more new data of local address book, and uploaded onto the server by described more new data, described more new data is in order to update the high in the clouds address list in server；
The synchrodata of the final updating time that the renewal time in described server is later than described local address book is downloaded, and according to described synchrodata, described local address book is synchronized.
2. method according to claim 1, it is characterised in that the more new data packets of described acquisition local address book is drawn together:
Database table is recorded for benchmark with system communication, described system communication is recorded database table and Three-Part protocol record database table compare, by described system communication record the variance data between database table and described Three-Part protocol record database table obtain described in more new data.
3. method according to claim 2, it is characterised in that described being uploaded onto the server by described more new data includes:
Described variance data is synchronized to described Three-Part protocol record database table；
If the method for synchronization is for amendment or deletes data, then the first synchrodata is sent to server, described first synchrodata includes: in described Three-Part protocol record database table, this amendment or the address list information deleted, the amendment of each bar or cloud identification information corresponding to address list information deleted and updating type indications, described cloud identification information and described updating type identifier in order to be synchronized to described high in the clouds address list by the address list information of described amendment or deletion；
If the described method of synchronization is newly-increased data, then the second synchrodata is sent to described server, described second synchrodata includes: this newly-increased address list information in described Three-Part protocol record database table, described second synchrodata is in order to be synchronized to described high in the clouds address list by described newly-increased address list information；
Receive the cloud identification information of described second synchrodata that described server returns, and the cloud identification information of described second synchrodata is write described Three-Part protocol record database table.
4. method according to claim 2, it is characterised in that described according to described synchrodata, described local address book carried out synchronization and include:
According to described synchrodata, synchronize the high in the clouds address list after described system communication record database table updates with described data；
Record the one-to-one relationship of the local identification information in database table and the local identification information in described system communication record database table based on described Three-Part protocol, described Three-Part protocol is recorded database table with Tong Bu after described system communication record database table and synchronize.
5. method according to claim 1, it is characterised in that include before the more new data of described acquisition local address book:
Three-Part protocol record database table is built in this locality, system communication is recorded the address book data in database table and imports in described Three-Part protocol record database table, and the address book data of importing is sent to described server, make described server according to the address book data received, build described high in the clouds address list；
Receive the cloud identification information of each bar address book data that described server returns, and write described Three-Part protocol record database table.
6. an address list synchronization device, it is characterised in that described device includes:
Acquisition module, for obtaining the more new data of local address book；
Sending module, for being uploaded onto the server by described more new data, described more new data is in order to update the high in the clouds address list in server；
Download module, the synchrodata for the renewal time in described server is later than the final updating time of described local address book is downloaded；
Synchronization module, for synchronizing described local address book according to described synchrodata.
7. device according to claim 6, it is characterised in that
Described acquisition module, it is additionally operable to record database table for benchmark with system communication, described system communication is recorded database table and Three-Part protocol record database table compare, by described system communication record the variance data between database table and described Three-Part protocol record database table obtain described in more new data.
8. device according to claim 7, it is characterised in that
Described synchronization module, is additionally operable to described variance data is synchronized to described Three-Part protocol record database table；
Described sending module, if being additionally operable to the method for synchronization for amendment or to delete data, then the first synchrodata is sent to server, described first synchrodata includes: in described Three-Part protocol record database table, this amendment or the address list information deleted, the amendment of each bar or cloud identification information corresponding to address list information deleted and updating type indications, described cloud identification information and described updating type identifier in order to be synchronized to described high in the clouds address list by the address list information of described amendment or deletion；
Described sending module, if being additionally operable to the described method of synchronization for newly-increased data, then the second synchrodata is sent to described server, described second synchrodata includes: this newly-increased address list information in described Three-Part protocol record database table, described second synchrodata is in order to be synchronized to described high in the clouds address list by described newly-increased address list information；
Described device also includes:
Receiver module, for receiving the cloud identification information of described second synchrodata that described server returns；
Writing module, for writing described Three-Part protocol record database table by the cloud identification information of described second synchrodata.
9. device according to claim 8, it is characterised in that
Described synchronization module, is additionally operable to, according to described synchrodata, synchronize the high in the clouds address list after described system communication record database table updates with described data；And record the one-to-one relationship of the local identification information in database table and the local identification information in described system communication record database table based on described Three-Part protocol, described Three-Part protocol is recorded database table with Tong Bu after described system communication record database table and synchronize.
10. device according to claim 9, it is characterised in that described device also includes:
Build module, for building Three-Part protocol record database table in this locality, system communication is recorded the address book data in database table and imports in described Three-Part protocol record database table；
Described sending module, is additionally operable to the address book data of importing is sent to described server so that described server, according to the address book data received, builds described high in the clouds address list；
Described receiver module, is additionally operable to receive the cloud identification information of each bar address book data that described server returns；
Said write module, is additionally operable to write described Three-Part protocol record database table.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610156376.0A CN105812469A (en) | 2016-03-18 | 2016-03-18 | Address book synchronization method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610156376.0A CN105812469A (en) | 2016-03-18 | 2016-03-18 | Address book synchronization method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105812469A true CN105812469A (en) | 2016-07-27 |
Family
ID=56453990
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610156376.0A Pending CN105812469A (en) | 2016-03-18 | 2016-03-18 | Address book synchronization method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105812469A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106412056A (en) * | 2016-09-27 | 2017-02-15 | 北京奇虎科技有限公司 | Intelligent address book creating method and device |
| CN107249045A (en) * | 2017-07-31 | 2017-10-13 | 合肥工业大学 | Portable endoscope multi-modal information synchronous storage method and system |
| CN107547683A (en) * | 2017-08-10 | 2018-01-05 | 青岛海信移动通信技术股份有限公司 | Data processing method and device |
| CN107733982A (en) * | 2017-09-12 | 2018-02-23 | 维沃移动通信有限公司 | A kind of method of data synchronization, terminal device, cloud server and system |
| CN115460227A (en) * | 2022-11-14 | 2022-12-09 | 成都怡康科技有限公司 | Method, device and system for synchronizing data, computer equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102761861A (en) * | 2011-04-27 | 2012-10-31 | 中国移动通信集团广东有限公司 | Information updating method, server and information updating system |
| CN103067453A (en) * | 2012-12-14 | 2013-04-24 | 北京思特奇信息技术股份有限公司 | Address book sharing method and system |
| CN103327037A (en) * | 2012-03-20 | 2013-09-25 | 中兴通讯股份有限公司 | Data synchronizing method and device |
| US20140068018A1 (en) * | 2012-08-30 | 2014-03-06 | Samsung Electronics Co., Ltd. | Content synchronization apparatus and method for cloud service system |
| CN105847336A (en) * | 2016-03-18 | 2016-08-10 | 周奇 | Address book synchronization method and device |
-
2016
- 2016-03-18 CN CN201610156376.0A patent/CN105812469A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102761861A (en) * | 2011-04-27 | 2012-10-31 | 中国移动通信集团广东有限公司 | Information updating method, server and information updating system |
| CN103327037A (en) * | 2012-03-20 | 2013-09-25 | 中兴通讯股份有限公司 | Data synchronizing method and device |
| US20140068018A1 (en) * | 2012-08-30 | 2014-03-06 | Samsung Electronics Co., Ltd. | Content synchronization apparatus and method for cloud service system |
| CN103067453A (en) * | 2012-12-14 | 2013-04-24 | 北京思特奇信息技术股份有限公司 | Address book sharing method and system |
| CN105847336A (en) * | 2016-03-18 | 2016-08-10 | 周奇 | Address book synchronization method and device |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106412056A (en) * | 2016-09-27 | 2017-02-15 | 北京奇虎科技有限公司 | Intelligent address book creating method and device |
| CN107249045A (en) * | 2017-07-31 | 2017-10-13 | 合肥工业大学 | Portable endoscope multi-modal information synchronous storage method and system |
| CN107249045B (en) * | 2017-07-31 | 2018-07-10 | 合肥工业大学 | Portable endoscope multi-modal information synchronous storage method and system |
| US10664494B2 (en) | 2017-07-31 | 2020-05-26 | Hefei University Of Technology | Method and system for synchronously storing multi-modal information of portable endoscope |
| CN107547683A (en) * | 2017-08-10 | 2018-01-05 | 青岛海信移动通信技术股份有限公司 | Data processing method and device |
| CN107547683B (en) * | 2017-08-10 | 2021-04-30 | 青岛海信移动通信技术股份有限公司 | Data processing method and device |
| CN107733982A (en) * | 2017-09-12 | 2018-02-23 | 维沃移动通信有限公司 | A kind of method of data synchronization, terminal device, cloud server and system |
| CN115460227A (en) * | 2022-11-14 | 2022-12-09 | 成都怡康科技有限公司 | Method, device and system for synchronizing data, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105847336A (en) | Address book synchronization method and device | |
| US11516288B2 (en) | Synchronized content library | |
| CN1988535B (en) | Synchronous method, system for file storage and customer terminal | |
| US9697225B2 (en) | Method for synchronizing file | |
| CN105812469A (en) | Address book synchronization method and device | |
| CN102207957B (en) | Partial item change tracking and synchronization | |
| CN103457905B (en) | Method of data synchronization, system and equipment | |
| JP2019519025A (en) | Division and movement of ranges in distributed systems | |
| EP2378437A1 (en) | Data synchronization methods in communication systems | |
| CN107391758A (en) | Database switching method, device and equipment | |
| CN108038114A (en) | A kind of path query method, terminal, computer-readable recording medium | |
| CN104426955A (en) | Processing method of shared file, and cloud storage server | |
| US9690796B2 (en) | Non-transitory computer-readable media storing file management program, file management apparatus, and file management method | |
| CN103064637A (en) | Network disk cache synchronizing method and system | |
| CN1983277A (en) | Method of assembling bookmark and computer device for setting updated main bookmark database | |
| CN103067480A (en) | Synchronized method and system of network disk | |
| US11507277B2 (en) | Key value store using progress verification | |
| CN103312489A (en) | Method and device for synchronizing terminal and server | |
| WO2019040146A1 (en) | Key ticketing system with lock-free concurrency and versioning | |
| CN104065752A (en) | Synchronization method of data between terminals | |
| KR20120044550A (en) | Cloud storage server and system by use of virtual nas and method thereof | |
| CN114185489A (en) | Data synchronization method and device, electronic equipment and storage medium | |
| CN105205100A (en) | Data synchronization method based on MTP between terminals and terminals | |
| US11210212B2 (en) | Conflict resolution and garbage collection in distributed databases | |
| CN110297812A (en) | File memory method, the method for file synchronization, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20180425 Address after: 644000 Lingang Economic and Technological Development Zone, Yibin, Sichuan, No. 713, section 17, 17 section of Changjiang North Road, Lingnan economic and Technological Development Zone. Applicant after: Yibin bond China smart technology Co., Ltd. Address before: 518029 Shenzhen, Futian District, Guangdong Province garden Ridge Street, Bagua road 31, Zhongxin science and Technology Building 9 storey (building 10 10) 1001 Applicant before: Zhou Qi |
|
| TA01 | Transfer of patent application right | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160727 |
|
| RJ01 | Rejection of invention patent application after publication |