CN110505290B - Method and device for synchronizing contact information - Google Patents
Method and device for synchronizing contact information Download PDFInfo
- Publication number
- CN110505290B CN110505290B CN201910727265.4A CN201910727265A CN110505290B CN 110505290 B CN110505290 B CN 110505290B CN 201910727265 A CN201910727265 A CN 201910727265A CN 110505290 B CN110505290 B CN 110505290B
- Authority
- CN
- China
- Prior art keywords
- information
- contact information
- target contact
- timestamp
- synchronization
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
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/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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/26—Devices for calling a subscriber
- H04M1/27—Devices whereby a plurality of signals may be stored simultaneously
- H04M1/274—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc
- H04M1/2745—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc using static electronic memories, e.g. chips
Abstract
The embodiment of the invention provides a method and a device for synchronizing contact information, wherein the method comprises the following steps: obtaining first target contact information from the mobile device in a server, wherein the first target contact information is updated after the first synchronization timestamp; searching second target contact information, wherein the second target contact information is updated after the first synchronization timestamp; comparing the first synchronization timestamp and the second synchronization timestamp to obtain a first comparison result; and synchronizing the first target contact person information and the second target contact person information according to the first comparison result. The embodiment of the invention realizes the purpose of differentially synchronizing the contact information, avoids uploading all the contact information to the server, reduces the uploaded data volume, thereby reducing the consumption of flow, and simultaneously reduces the compared data volume, thereby reducing the time consumption of synchronization.
Description
The application is a divisional application of Chinese patent application 201610395683.4 entitled "a method and a device for synchronizing contact information" filed on 2016, 06, 03.
Technical Field
The present invention relates to the field of computer processing technologies, and in particular, to a method and an apparatus for synchronizing contact information.
Background
With the development of communication technology, mobile devices such as mobile phones and watches have higher and higher usage rates in various aspects of work, study, daily communication and the like.
The frequency of the communication and the short message contact between the user and other people through the mobile equipment is high, so that more contact information is accumulated in the mobile equipment.
When a user changes the mobile device or the mobile device is in a failure, the contact information may be lost, and therefore, the contact information is usually backed up in the cloud.
In order to keep consistency between the mobile device and the cloud, the mobile device and the cloud can be synchronized under certain conditions.
Most mobile devices upload all local contact information to the server during synchronization, and the changed contact information is transmitted to the client side in a comparison mode at the server side.
Because the local contact information needs to be uploaded to the server in each synchronization, the transmission quantity is large, more flow can be consumed, and meanwhile, compared data quantity is large, and synchronization time is long.
Disclosure of Invention
In view of the above problems, in order to solve the problems that the synchronization of the contact information consumes more traffic and has longer synchronization time, embodiments of the present invention provide a method and a device for synchronizing the contact information.
In order to solve the above problem, an embodiment of the present invention discloses a method for synchronizing contact information, where first contact information and a first synchronization timestamp are stored in a mobile device, and second contact information and a second synchronization timestamp are stored in a server, the method including:
obtaining first target contact information from the mobile device in a server, wherein the first target contact information is updated after the first synchronization timestamp;
searching second target contact information, wherein the second target contact information is updated after the first synchronization timestamp;
comparing the first synchronization timestamp and the second synchronization timestamp to obtain a first comparison result;
and synchronizing the first target contact person information and the second target contact person information according to the first comparison result.
Preferably, the step of synchronizing the first target contact information and the second target contact information according to the first comparison result includes:
and when the first synchronization timestamp is equal to the second synchronization timestamp, updating the second target contact information by using the first target contact information.
Preferably, the first contact information has first update type information and a first update time stamp, and the second contact information has second update type information and a second update time stamp;
the first updating type information comprises first deleting information and/or first modifying information, and the second updating information comprises second deleting information and/or first modifying information;
the step of updating the second target contact information with the first target contact information comprises:
when the first deletion information is marked, marking the second deletion information;
assigning a value of the first update timestamp to the second update timestamp;
alternatively, the first and second liquid crystal display panels may be,
when the first modification information is marked and corresponding second target contact information is found, covering the content of the first target contact information with the content of the second target contact information;
marking the second modification information;
assigning a value of the first update timestamp to the second update timestamp;
alternatively, the first and second liquid crystal display panels may be,
when the first modification information is marked and corresponding second target contact information is not found, storing the content of the first target contact information to new second contact information;
marking the second modification information;
assigning a value of the first update timestamp to the second update timestamp.
Preferably, the first contact information has a corresponding first update timestamp, and the second contact information has a corresponding second update timestamp;
the step of synchronizing the first target contact information and the second target contact information according to the first comparison result comprises:
comparing the first target contact information and the second target contact information when the first synchronization timestamp is less than the second synchronization timestamp;
when the first target contact information is the same as the second target contact information, ignoring the first target contact information;
when the first target contact person information is different from the second target contact person information, comparing the first updating time stamp with the second updating time stamp to obtain a second comparison result;
and synchronizing the first target contact information and the second target contact information according to the second comparison result.
Preferably, the step of synchronizing the first target contact information and the second target contact information according to the second comparison result includes:
when the first update timestamp is greater than the second update timestamp, updating the second target contact information by adopting the first target contact information;
alternatively, the first and second electrodes may be,
and when the first updating time stamp is smaller than the second time stamp, sending the second target contact information to mobile equipment so as to update the first target contact information.
Preferably, the method further comprises the following steps:
recording time information when synchronization is completed;
updating the first synchronization timestamp and the second synchronization timestamp with the time information.
The embodiment of the invention also discloses a device for synchronizing the contact information, wherein the mobile equipment stores the first contact information and the first synchronization timestamp, and the server stores the second contact information and the second synchronization timestamp, and the device comprises:
a first target contact information obtaining module, configured to obtain, in a server, first target contact information from the mobile device, where the first target contact information is first contact information updated after the first synchronization timestamp;
a second target contact information searching module, configured to search for second target contact information, where the second target contact information is second contact information updated after the first synchronization timestamp;
a synchronization timestamp comparison module, configured to compare the first synchronization timestamp with the second synchronization timestamp, and obtain a first comparison result;
and the contact person information synchronization module is used for synchronizing the first target contact person information and the second target contact person information according to the first comparison result.
Preferably, the contact information synchronization module includes:
and the contact person information updating submodule is used for updating the second target contact person information by adopting the first target contact person information when the first synchronization timestamp is equal to the second synchronization timestamp.
Preferably, the first contact information has first update type information and a first update time stamp, and the second contact information has second update type information and a second update time stamp;
the first updating type information comprises first deleting information and/or first modifying information, and the second updating information comprises second deleting information and/or first modifying information;
the contact information updating submodule comprises:
a first marking unit configured to mark the second deletion information when the first deletion information is marked;
a first assigning unit configured to assign a value of the first update timestamp to the second update timestamp;
alternatively, the first and second electrodes may be,
the first covering unit is used for covering the content of the first target contact person information with the content of the second target contact person information when the first modification information is marked and the corresponding second target contact person information is found;
a second marking unit, configured to mark the second modification information;
a second assigning unit configured to assign a value of the first update timestamp to the second update timestamp;
alternatively, the first and second electrodes may be,
the storage unit is used for storing the content of the first target contact information to new second contact information when the first modification information is marked and the corresponding second target contact information is not found;
a third marking unit, configured to mark the second modification information;
a third assigning unit for assigning the value of the first update timestamp to the second update timestamp.
Preferably, the first contact information has a corresponding first update timestamp and the second contact information has a corresponding second update timestamp;
the contact information synchronization module comprises:
a target contact information comparison submodule, configured to compare the first target contact information with the second target contact information when the first synchronization timestamp is smaller than the second synchronization timestamp;
the target contact person information ignoring sub-module is used for ignoring the first target contact person information when the first target contact person information is the same as the second target contact person information;
the update timestamp comparison submodule is used for comparing the first update timestamp and the second update timestamp to obtain a second comparison result when the first target contact information is different from the second target contact information;
and the comparison synchronization sub-module is used for synchronizing the first target contact information and the second target contact information according to the second comparison result.
Preferably, the comparison synchronization sub-module includes:
the server updating unit is used for updating the second target contact person information by adopting the first target contact person information when the first updating time stamp is larger than the second updating time stamp;
alternatively, the first and second electrodes may be,
and the mobile equipment updating unit is used for sending the second target contact information to the mobile equipment when the first updating time stamp is smaller than the second time stamp so as to update the first target contact information.
The embodiment of the invention has the following advantages:
the contact synchronization of the embodiment of the invention relates to the communication between mobile equipment and a server, wherein the mobile equipment stores first contact information and a first synchronization timestamp, and the server stores second contact information and a second synchronization timestamp.
The mobile device may select first target contact information from the first contact information that is updated after the first synchronization timestamp, that is, the contact information which may generate a difference with the server is selected and sent to the server, the server reflects the difference of the synchronization progress between the mobile device and the server according to the comparison result between the first synchronization timestamp and the second synchronization timestamp, and further synchronizing the first contact information and the second contact information using the first target contact information, because the first target contact information is part of the contact information generally, the embodiment of the invention realizes the purpose of synchronizing the contact information differentially, avoids uploading all the contact information to the server, reduces the uploaded data volume, therefore, the consumption of flow is reduced, and meanwhile, the compared data volume is reduced, so that the time consumption of synchronization is reduced.
Drawings
Fig. 1 is a flowchart of steps of an embodiment 1 of a method for synchronizing contact information according to the present invention;
FIGS. 2A-2C are exemplary diagrams of a synchronization of contact information according to embodiments of the invention;
fig. 3 is a flowchart of the steps of embodiment 2 of the method for synchronizing contact information according to the present invention;
fig. 4 is a block diagram of a contact information synchronization apparatus 1 according to an embodiment of the present invention;
fig. 5 is a block diagram of a contact information synchronization apparatus in accordance with embodiment 2 of the present invention.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in further detail below.
Referring to fig. 1, a flowchart illustrating steps of embodiment 1 of a method for synchronizing contact information according to the present invention is shown, which may specifically include the following steps:
in particular implementations, the mobile device may include a cell phone, a tablet, a personal digital assistant, a wearable device (e.g., glasses, watch, etc.), and so forth.
The operating systems of these mobile communication terminals may include Android (Android), IOS, Windows Phone, Windows, and the like.
In order to enable those skilled in the art to better understand the embodiment of the present invention, in the present specification, Android is described as an example of an operating system.
The mobile devices can communicate with other users, send or receive short messages, send or receive multimedia messages and other communication operations through a cellular network and other modes.
To communicate with other users, the user typically enters contact information of the other users, such as the contact's name, phone, home address, email address, company, etc., into the mobile device and stores it in an address book.
The address book may be a system address book of the mobile device, or may also be an address book of a third party application, which is not limited in the embodiment of the present invention.
The user can log in an account in the mobile equipment, and the contact information stored in the mobile equipment is sent to the server for backup, so that the contact information is also stored in the server.
In order to distinguish the mobile device from the server, in the embodiment of the present invention, the contact information stored in the mobile device may be referred to as first contact information, and the contact information stored in the server may be referred to as second contact information.
Taking the Andord system as an example, a ContentProvider application generally carried by the system can access an address book (such as contacts2.db file) through the ContentProvider application to operate contact information.
In one aspect, write (update) operations may include adding contact information, modifying contact information, deleting contact information, and the like.
On the other hand, a read operation to query contact information may be included.
For example, if the mobile device employs an SQLite database to store contact information, the Query may be performed using a standard SQL (Structured Query Language) statement.
Contactcontact is stored based on a three-layer data model, which includes three main databases, respectively:
1、ContactsContact.Data；
the Data table is a table that stores specific contact information including mail, telephone numbers, and the like.
2、ContactsContact.RawContacts；
The RawContacts table is a data set of contacts that specifies the user account and type.
3、ContactsContact.Contacts。
The Contacts table contains records of different Contacts.
In the embodiment of the invention, the structure of the address list can be modified, and the update time stamp and the update type information are added to each piece of contact information.
The update type information includes deletion information and modification information.
Further, the update timestamp is time information recorded when a record of a piece of contact information is updated (e.g., added, modified, deleted, etc.).
Since the update time stamp overlaps the update time stamp of the last record at each update, the update time stamp is the latest update time of the record recording some piece of contact information.
The deleting information is information for marking whether the contact information is deleted or not, and the modifying information is information for marking whether the contact information is modified or not.
A general modification modifies a field of existing contact information, and in the embodiment of the present invention, adding contact information also belongs to modification.
Then in an embodiment of the present invention, an example of the data of the contact information may be as shown in table 1:
TABLE 1
| _id | Account_id | Contact_id | Display_name | latest_update_timestamp | delete | dirty |
| 1 | 1 | 21 | Zhang San | 1456916952007 | 0 | 1 |
| 2 | 1 | 42 | Li Si | 1456916952007 | 0 | 1 |
| 3 | 1 | 32 | Wang Wu | 1456916952007 | 1 | 0 |
Wherein, the _idfield is the ID of the current record;
the Account _ ID field is an Account ID;
contact _ ID is a Contact ID;
the Display _ name field is the name of the contact;
the last _ update _ timestamp is an update timestamp;
delete is deletion information, defaults to 0, and marks as 1 when the contact information is deleted;
dirty is modification information, default is 0, and the contact information is marked as 1 when modified;
it should be noted that, since there are usually many tables in the address book, there are usually many fields in each table, in this example, part of the key fields in the RawContacts table are extracted, and it does not mean that there are only these fields in the address book.
In order to distinguish the mobile device from the server, in the embodiment of the present invention, the update timestamp stored in the mobile device may be referred to as a first update timestamp, and the update timestamp stored in the server may be referred to as a second update timestamp, but the update timestamps are substantial update timestamps, and for convenience of synchronization, the data structures of the two are generally the same.
And, the update type information (deletion information, modification information) stored in the mobile device may be referred to as first update type information (first deletion information, first modification information), and the update type information (deletion information, modification information) stored in the server may be referred to as second update type information (second deletion information, second modification information), but it is substantial update type information (deletion information, modification information), and the data structures of both are generally the same for the sake of synchronization.
Furthermore, since a user may have multiple mobile devices or other terminals (e.g., televisions), the terminals may all synchronize with the mobile devices.
To differentiate the synchronization progress of the mobile device and the server, a first synchronization timestamp may be stored in the mobile device indicating the time the server last synchronized the contact information with the current mobile device.
The server may store a second synchronization timestamp indicating the time when the server last synchronized the contact information with the terminal, which may be the current mobile device, another mobile device, or another terminal.
In the embodiment of the invention, the mobile device and the server perform the contact information synchronization operation on the condition that a synchronization request triggered by a user is detected or a specified time (such as 0 time every day) is reached.
The mobile device may select the first contact information updated after the timestamp from the first contact information as first target contact information and send the first target contact information to the server.
For example, if the data structure shown in table 1 is applied, the first target contact information is the first contact information whose first update timestamp latest _ update _ timestamp is greater than the first synchronization timestamp.
If the first contact information is updated before the first synchronization timestamp, the first contact information is synchronized with the server, and no difference exists between the first contact information and the second contact information stored by the server.
On the contrary, the first target contact information is the first contact information updated after the first synchronization timestamp, and is not synchronized with the server, and may be different from the second contact information stored by the server.
It should be noted that, because there are many contact information fields, generally, a key/value form is not selected for transmission, but the changed contact information is written into a file in a custom format (similar to a vcard file), and the file is transmitted to a server by communicating with a Protocol such as HTTPS (Hyper Text Transfer Protocol over Secure Socket Layer).
For example, an example of a file containing two changed contacts is as follows:
BEGIN:VCARD
BEGIN:CONTACTS
FLAG:Delete
NAME:Tom
TEL;WORK;VOICE:13298789000
TEL;HOME;VOICE:053286754211
ADR;WORK:;;100 Waters Edge;Baytown;LA;30314;United States of America
EMAIL;PREF;INTERNET:tom@example.com
END: CONTACTS
BEGIN：CONTACTS
FLAG:Dirty
NAME:Jack
TEL;WORK;VOICE: 18698789999
TEL;HOME;VOICE: 053286754200
ADR;WORK:;;100 Waters Edge;Baytown;LA;30314;United States of America
EMAIL;PREF;INTERNET:jack@example.com
END: CONTACTS
END:VCARD
wherein the second target contact information is second contact information updated after the first synchronization timestamp.
For example, if the data structure shown in table 1 is applied, the second target contact information is the second contact information whose second update timestamp, latest _ update _ timestamp, is greater than the first synchronization timestamp.
in one way of comparison, the mobile device may send a first synchronization timestamp to the server, and the server compares the received first synchronization timestamp with a second synchronization timestamp stored locally to obtain a first comparison result.
Taking the Android system as an example, the first synchronization timestamp may be recorded in a shared reference, and the first synchronization timestamp may be transmitted to the server in a key/value form by using a protocol such as HTTPS for secure communication.
In another comparison manner, the server may send the second synchronization timestamp to the mobile device, and the mobile device compares the locally stored first synchronization timestamp with the received second synchronization timestamp, and returns the obtained first comparison result to the server.
In a specific implementation, the first comparison result includes two cases:
in one case, the first synchronization timestamp is equal to the second synchronization timestamp;
alternatively, the first synchronization timestamp is less than the second synchronization timestamp.
And 104, synchronizing the first target contact information and the second target contact information according to the first comparison result.
In a specific implementation, the first comparison result may reflect a synchronization progress of the mobile device and the server, and based on the synchronization progress, the first contact information and the second contact information may be synchronized by using the first target contact information that may have a difference.
In one embodiment of the present invention, step 104 may include the following sub-steps:
and a substep S11 of updating the second target contact information with the first target contact information when the first synchronization timestamp is equal to the second synchronization timestamp.
And if the first synchronization timestamp is equal to the second synchronization timestamp, the synchronization progress of the contact information between the mobile device and the server is the same.
Therefore, the modification of the contact information is performed on the second target contact information corresponding to the server with respect to the first target contact of the mobile device.
The correspondence in the embodiment of the present invention means that the first target contact information and the second target contact information both belong to the same contact information.
For example, if the data structure shown in table 1 is applied, the Contact _ id of the first target Contact information is the same as the Contact _ id of the second target Contact information.
In a specific implementation, the first contact information has first update type information, a first update timestamp, and the second contact information has second update type information, a second update timestamp.
In one example, when the first deletion information is marked (e.g., value of delete is 1), the second deletion information is marked (e.g., value of delete is 1).
The value of the first update timestamp is assigned to the second update timestamp.
Alternatively, the first and second electrodes may be,
in another example, when the first modified information is tagged (e.g., dirty has a value of 1) and the corresponding second target contact information is located, the content of the first target contact information (e.g., name, phone call, E-mail, etc.) is overlaid with the content of the second target contact information (e.g., name, phone call, E-mail, etc.).
The second modification information is marked (e.g., dirty has a value of 1).
The value of the first update timestamp is assigned to the second update timestamp.
Alternatively, the first and second electrodes may be,
in another example, when the first modified information is marked (e.g., dirty has a value of 1) and the corresponding second target contact information is not found, the content of the first target contact information (e.g., name, phone call, E-mail, etc.) is stored to the new second contact information;
marking the second modification information (for example, dirty has a value of 1);
the value of the first update timestamp is assigned to the second update timestamp.
Of course, the above synchronization manner is only an example, and when the embodiment of the present invention is implemented, other synchronization manners may be set according to actual situations, which is not limited in the embodiment of the present invention. In addition, besides the above synchronization modes, those skilled in the art may also adopt other synchronization modes according to actual needs, and the embodiment of the present invention is not limited thereto.
In another embodiment of the present invention, step 104 may include the following sub-steps:
sub-step S21, comparing the first target contact information and the second target contact information when the first synchronization timestamp is less than the second synchronization timestamp;
and if the first synchronization timestamp is smaller than the second synchronization timestamp, the synchronization progress of the contact information between the mobile equipment and the server is different.
After the current mobile device synchronizes with the server, the server also synchronizes with other mobile devices or other terminals.
In embodiments of the present invention, values of the same fields (e.g., phone numbers, contacts, etc.) in the first target contact and the corresponding second target contact may be compared.
The correspondence in the embodiment of the present invention means that the first target contact information and the second target contact information both belong to the same contact information.
For example, if the data structure shown in table 1 is applied, the Contact _ id of the first target Contact information is the same as the Contact _ id of the second target Contact information.
It should be noted that, in the case that the first contact information is newly added to the current mobile device, the server does not store the corresponding second contact information, that is, some first target contact information may not have the corresponding second target contact information.
In addition, under the condition that other terminals add new contact information and synchronize to the server as second contact information, and the like, the current mobile device does not store corresponding first contact information, that is, some second target contact information may not have corresponding first target contact information.
Substep S22, when the first target contact information is the same as the second target contact information, ignoring the first target contact information;
if the first target contact information is the same as the second target contact information, the first target contact information can be ignored, and the second target contact information is not modified.
Substep S23, when the first target contact information is different from the second target contact information, comparing the first update timestamp with the second update timestamp to obtain a second comparison result;
and a substep S24 of synchronizing the first target contact information and the second target contact information according to the second comparison result.
In the embodiment of the invention, the first contact information has a corresponding first updating time stamp, and the second contact information has a corresponding second updating time stamp.
If the first target contact information is different from the second target contact information, the first update timestamp and the second update timestamp can be further compared to obtain the modification progress of the first target contact information and the second target contact information, and therefore the first contact information and the second contact information are synchronized.
In one case, when the first update timestamp is greater than the second update timestamp, i.e., the first target contact information is newer than the modification of the second target contact information, the second contact information of the server is modified based on the first target contact information of the mobile device.
That is, the first target contact information is used to update the second target contact information.
Specifically, when the first deletion information is marked, the second deletion information is marked;
assigning a value of the first update timestamp to a second update timestamp;
alternatively, the first and second electrodes may be,
when the first modification information is marked and the second target contact information is found, covering the content of the first target contact information with the content of the second target contact information;
marking the second modification information;
assigning a value of the first update timestamp to a second update timestamp;
alternatively, the first and second electrodes may be,
when the first modification information is marked and corresponding second target contact information is not found, storing the content of the first target contact information to new second contact information;
marking the second modification information;
the value of the first update timestamp is assigned to the second update timestamp.
In another case, when the first update timestamp is less than the second timestamp, that is, the first target contact information is older than the second target contact information, the first target contact information of the mobile device is modified with respect to the second contact information of the server.
That is, the second target contact information is sent to the mobile device to update the first target contact information.
Specifically, when the second deletion information is marked, the first deletion information is marked;
assigning a value of the second update timestamp to the first update timestamp;
alternatively, the first and second electrodes may be,
when the second modification information is marked and the first target contact information is found, covering the content of the second target contact information with the content of the first target contact information;
marking the first modification information;
assigning a value of the second update timestamp to the first update timestamp;
alternatively, the first and second liquid crystal display panels may be,
when the second modification information is marked and the corresponding first target contact information is not found, storing the content of the second target contact information to new first contact information;
marking the first modification information;
the value of the second update timestamp is assigned to the first update timestamp.
Of course, the above synchronization manner is only an example, and when implementing the embodiment of the present invention, other synchronization manners may be set according to actual situations, and the embodiment of the present invention is not limited thereto. In addition, besides the above synchronization modes, those skilled in the art may also adopt other synchronization modes according to actual needs, and the embodiment of the present invention is not limited thereto.
The contact synchronization of the embodiment of the invention relates to the communication between mobile equipment and a server, wherein the mobile equipment stores first contact information and a first synchronization timestamp, and the server stores second contact information and a second synchronization timestamp.
The mobile device may select first target contact information from the first contact information that is updated after the first synchronization timestamp, namely selecting the contact information which possibly generates difference with the server, sending the contact information to the server, reflecting the difference of the synchronization progress between the mobile equipment and the server by the server according to the comparison result between the first synchronization timestamp and the second synchronization timestamp, and further to synchronize the first contact information and the second contact information using the first target contact information, because the first target contact information is part of contact information generally, the embodiment of the invention realizes the purpose of differentially synchronizing the contact information, avoids uploading all the contact information to a server, reduces the uploaded data volume, therefore, the consumption of flow is reduced, and meanwhile, the compared data volume is reduced, so that the time consumption of synchronization is reduced.
In order to make the embodiment of the present invention better understood, the following describes a method for synchronizing contact information according to the embodiment of the present invention by using a specific example.
Referring to fig. 2A, the mobile device locally stores A, B, C three contact information, syncing with the cloud (server) so that the cloud also stores A, B, C three contact information.
The first synchronization timestamp local to the mobile device is equal to the second synchronization timestamp of the cloud.
Referring to fig. 2B, the user deletes the contact information a, the contact information C, and adds the contact information D locally on the mobile device.
The user deletes the contact person information C in other terminals, newly adds the contact person information E and synchronizes to the cloud.
At this time, the second synchronization timestamp of the cloud is updated.
Referring to fig. 2C, if the current mobile device is synchronized with the server, the mobile device uploads the contact information a, the contact information C, and the contact information D as first target contact information to the cloud.
Because the first synchronization timestamp of the current mobile device is smaller than the second synchronization timestamp of the cloud, the contact information C and the contact information E are used as second target contact information in the cloud.
The contact information A is mainly the mobile device, and the contact information A in the cloud is marked and deleted.
The content of the contact person information C of the mobile device and the cloud is consistent, and the contact person information C is ignored.
The contact information D is mainly of the mobile equipment, and the contact information D is newly added at the cloud.
The contact person information E is mainly of the mobile equipment, and the contact person information E is newly added to the mobile equipment.
Referring to fig. 3, a flowchart of the steps of embodiment 2 of the method for synchronizing contact information according to the present invention is shown, where first contact information and a first synchronization timestamp are stored in a mobile device, and second contact information and a second synchronization timestamp are stored in a server, and the method specifically includes the following steps:
wherein the first target contact information is first contact information updated after the first synchronization timestamp;
step 305, updating the first synchronization timestamp and the second synchronization timestamp with the time information.
In the embodiment of the present invention, if the mobile device and the server perform the synchronization operation on the contact information, the time information when the synchronization is completed may be recorded.
In a specific implementation, since both the mobile device and the server may modify the contact information, the mobile device may record one completion time and the server may record another completion time.
The two times are compared in the mobile device or the server and the first synchronization timestamp of the mobile device and the second synchronization timestamp of the server are updated based on the latest (i.e., maximum) completion time so that the two remain the same.
It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the illustrated order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments of the present invention. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the invention.
Referring to fig. 4, a block diagram of an embodiment 1 of a device for synchronizing contact information according to the present invention is shown, in which a mobile device stores first contact information and a first synchronization timestamp, and a server stores second contact information and a second synchronization timestamp, and the device includes: the method specifically comprises the following modules:
a first target contact information obtaining module 401, configured to obtain, in a server, first target contact information from the mobile device, where the first target contact information is first contact information updated after the first synchronization timestamp;
a second target contact information searching module 402, configured to search for second target contact information, where the second target contact information is second contact information updated after the first synchronization timestamp;
a synchronization timestamp comparing module 403, configured to compare the first synchronization timestamp with the second synchronization timestamp, to obtain a first comparison result;
a contact information synchronization module 404, configured to synchronize the first target contact information and the second target contact information according to the first comparison result.
In one embodiment of the present invention, the contact information synchronization module 404 may include the following sub-modules:
and the contact person information updating submodule is used for updating the second target contact person information by adopting the first target contact person information when the first synchronization timestamp is equal to the second synchronization timestamp.
In one example of the embodiment of the present invention, the first contact information has first update type information and a first update time stamp, and the second contact information has second update type information and a second update time stamp;
the first updating type information comprises first deleting information and/or first modifying information, and the second updating information comprises second deleting information and/or first modifying information;
the contact information updating sub-module may include the following elements:
a first marking unit configured to mark the second deletion information when the first deletion information is marked;
a first assigning unit configured to assign a value of the first update timestamp to the second update timestamp;
alternatively, the first and second electrodes may be,
the first covering unit is used for covering the content of the first target contact person information with the content of the second target contact person information when the first modification information is marked and the corresponding second target contact person information is found;
a second marking unit, configured to mark the second modification information;
a second assigning unit configured to assign a value of the first update timestamp to the second update timestamp;
alternatively, the first and second electrodes may be,
the storage unit is used for storing the content of the first target contact information to new second contact information when the first modification information is marked and the corresponding second target contact information is not found;
a third marking unit, configured to mark the second modification information;
a third assigning unit for assigning the value of the first update timestamp to the second update timestamp.
In one embodiment of the invention, the first contact information has a corresponding first update timestamp and the second contact information has a corresponding second update timestamp;
the contact information synchronization module 404 may include the following sub-modules:
the target contact person information comparison sub-module is used for comparing the first target contact person information with the second target contact person information when the first synchronization timestamp is smaller than the second synchronization timestamp;
the target contact information ignoring sub-module is used for ignoring the first target contact information when the first target contact information is the same as the second target contact information;
the update timestamp comparison submodule is used for comparing the first update timestamp and the second update timestamp to obtain a second comparison result when the first target contact information is different from the second target contact information;
and the comparison synchronization sub-module is used for synchronizing the first target contact information and the second target contact information according to the second comparison result.
In one embodiment of the present invention, the comparison synchronization sub-module may include the following units:
the server updating unit is used for updating the second target contact information by adopting the first target contact information when the first updating time stamp is larger than the second updating time stamp;
alternatively, the first and second electrodes may be,
and the mobile equipment updating unit is used for sending the second target contact information to the mobile equipment when the first updating time stamp is smaller than the second time stamp so as to update the first target contact information.
Referring to fig. 5, a block diagram of an embodiment 2 of the apparatus for synchronizing contact information according to the present invention is shown, in which a mobile device stores first contact information and a first synchronization timestamp, and a server stores second contact information and a second synchronization timestamp, and the apparatus includes: the method specifically comprises the following modules:
a first target contact information obtaining module 501, configured to obtain, in a server, first target contact information from the mobile device, where the first target contact information is first contact information updated after the first synchronization timestamp;
a second target contact information searching module 502, configured to search for second target contact information, where the second target contact information is second contact information updated after the first synchronization timestamp;
a synchronization timestamp comparing module 503, configured to compare the first synchronization timestamp with the second synchronization timestamp, to obtain a first comparison result;
a contact information synchronization module 504, configured to synchronize the first target contact information and the second target contact information according to the first comparison result;
a time information recording module 505, configured to record time information when synchronization is completed;
a synchronization timestamp update module 506, configured to update the first synchronization timestamp and the second synchronization timestamp with the time information.
For the apparatus embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and reference may be made to the partial description of the method embodiment for relevant points.
The embodiments in the present specification are all described in a progressive manner, and each embodiment focuses on differences from other embodiments, and portions that are the same and similar between the embodiments may be referred to each other.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the invention.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
The above detailed description is provided for the method and the device for synchronizing contact information, and specific examples are applied herein to explain the principle and the implementation of the present invention, and the description of the above embodiments is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (9)
1. A method for synchronizing contact information, which is applied to a mobile device, and comprises the following steps:
the mobile equipment sets an update timestamp on the contact information, wherein the update timestamp is recorded time information when a record of certain contact information is updated;
the mobile device detects a synchronization request triggered by a user, or reaches a specified synchronization time;
the mobile device takes the contact information of which the update timestamp is after a first synchronization timestamp as first target contact information, wherein the first synchronization timestamp is the time of last contact information synchronization between the mobile device and the server;
the mobile device sending the first target contact information and the first synchronization timestamp to the server;
the mobile equipment receives a second synchronous time stamp sent by the server, compares the locally stored first synchronous time stamp with the received second synchronous time stamp, and returns an obtained first comparison result to the server;
when the first synchronization timestamp is equal to the second synchronization timestamp, updating second target contact information by using the first target contact information, and assigning the value of the update timestamp to a second update timestamp;
when the first synchronization timestamp is smaller than the second synchronization timestamp, the mobile device receives a second target contact sent by the server, the second target contact information is second contact information updated in the server after the first synchronization timestamp, and the second target contact is provided with a second update timestamp;
comparing the values of the same fields in the first target Contact person and the corresponding second target Contact person, wherein the first target Contact person information and the second target Contact person information both belong to the same Contact person information, and the Contact _ ids are the same;
when the first target contact information is the same as the second target contact information, ignoring the first target contact information;
when the first target contact information is different from the second target contact information, comparing a first updating time stamp with a second updating time stamp to obtain a second comparison result;
and synchronizing the first target contact information and the second target contact information according to the second comparison result.
2. The synchronization method of claim 1, further comprising:
the mobile equipment sets update type information on the contact information, wherein the update type information comprises deletion information and modification information.
3. The synchronization method according to claim 1, wherein the synchronizing the contact information according to the comparison of the first update timestamp of the first target contact and the second update timestamp of the second target contact comprises:
when the first update timestamp is greater than the second update timestamp, not updating first target contact information;
alternatively, the first and second electrodes may be,
and when the first update timestamp is smaller than the second update timestamp, updating the first target contact information by adopting the second target contact information.
4. The synchronization method of claim 3, further comprising:
the first target contact information has first update type information and a first update timestamp, and the second target contact information has second update type information and a second update timestamp;
the first updating type information comprises first deleting information and/or first modifying information, and the second updating information comprises second deleting information and/or second modifying information;
the step of updating the first target contact information with the second target contact information comprises:
when the second deletion information is marked, marking the first deletion information;
assigning a value of the second update timestamp to the first update timestamp;
alternatively, the first and second electrodes may be,
when the second modification information is marked and corresponding first target contact information is found, covering the content of the second target contact information with the content of the first target contact information;
marking the first modification information;
assigning a value of the second update timestamp to the first update timestamp;
alternatively, the first and second electrodes may be,
when the second modification information is marked and corresponding first target contact information is not found, storing the content of the second target contact information to new first contact information;
marking the first modification information;
assigning a value of the second update timestamp to the first update timestamp.
5. A method for synchronizing contact information is applied to a server, and the method comprises the following steps:
the method comprises the steps that a server receives first target contact information and a first synchronization timestamp which are sent by mobile equipment, wherein the first target contact information is contact information which is updated by the mobile equipment after the first synchronization timestamp, and the first synchronization timestamp is the time when the mobile equipment and the server perform contact information synchronization last time;
comparing the first synchronization timestamp with a second synchronization timestamp stored locally, wherein the second synchronization timestamp is the time when the server and the terminal perform contact person information synchronization last time;
if the first synchronization timestamp is equal to the second synchronization timestamp, modifying the contact person information in the server by adopting the first target contact person information, and assigning the value of the update timestamp to a second update timestamp;
when the first synchronization timestamp is smaller than the second synchronization timestamp, the server sends a second target Contact to the mobile device for receiving, wherein the second target Contact information is second Contact information updated in the server after the first synchronization timestamp, and the second target Contact is provided with a second update timestamp, so that the mobile device compares values of the same fields in the first target Contact and the corresponding second target Contact, wherein the first target Contact information and the second target Contact information both belong to the same Contact information, and Contact _ id are the same;
when the first target contact person information is the same as the second target contact person information, ignoring the first target contact person information;
when the first target contact information is different from the second target contact information, comparing a first updating time stamp with a second updating time stamp to obtain a second comparison result;
synchronizing the first target contact information and the second target contact information according to the second comparison result;
and recording the updated time information, updating the second synchronization timestamp by adopting the time information, and sending the recorded updated time information to the mobile equipment, so that the mobile equipment updates the first synchronization timestamp by adopting the time information.
6. The method according to claim 5, wherein the first target contact information specifically includes:
the first target contact information has first update type information, a first update timestamp, wherein the first update type information includes first deletion information and/or first modification information.
7. The method according to claim 5 or 6, wherein the step of modifying the contact information in the server by using the first target contact specifically comprises:
when the first deletion information is marked, marking second deletion information of a corresponding contact of the server;
assigning the value of the first update timestamp to a second update timestamp of a corresponding contact of a server;
alternatively, the first and second electrodes may be,
when the first modification information is marked and the corresponding contact information of the server is found, covering the content of the first target contact information with the content of the corresponding contact information;
marking second modification information of the corresponding contact persons of the server;
assigning the value of the first updating time stamp to a second updating time stamp of a corresponding contact of a server;
alternatively, the first and second electrodes may be,
when the first modification information is marked and the corresponding contact information of the server is not found, storing the content of the first target contact information to new second contact information;
marking the second modification information;
assigning a value of the first update timestamp to the second update timestamp.
8. A mobile device for synchronizing contact information, the mobile device comprising a processor, a memory,
the mobile equipment sets an update timestamp on the contact information, wherein the update timestamp is recorded time information when a record of some contact information is updated;
the mobile equipment detects a synchronization request triggered by a user, or reaches a specified synchronization time;
the mobile device takes the contact information of which the update timestamp is after a first synchronization timestamp as first target contact information, wherein the first synchronization timestamp is the time of last contact information synchronization between the mobile device and the server;
the mobile device sending the first target contact information and the first synchronization timestamp to the server;
the mobile equipment receives a second synchronous time stamp sent by the server, compares the locally stored first synchronous time stamp with the received second synchronous time stamp, and returns an obtained first comparison result to the server;
when the first synchronization timestamp is equal to the second synchronization timestamp, updating second target contact information by adopting the first target contact information, and assigning the value of the update timestamp to a second update timestamp;
when the first synchronization timestamp is smaller than the second synchronization timestamp, the mobile device receives a second target contact sent by the server, the second target contact information is second contact information updated in the server after the first synchronization timestamp, and the second target contact is provided with a second update timestamp;
comparing the values of the same fields in the first target Contact person and the corresponding second target Contact person, wherein the first target Contact person information and the second target Contact person information both belong to the same Contact person information, and the Contact _ ids are the same;
when the first target contact information is the same as the second target contact information, ignoring the first target contact information;
when the first target contact information is different from the second target contact information, comparing a first updating time stamp with a second updating time stamp to obtain a second comparison result;
and synchronizing the first target contact information and the second target contact information according to the second comparison result.
9. A server for synchronizing contact information is characterized in that the server comprises a processor and a memory,
the method comprises the steps that a server receives first target contact information and a first synchronization timestamp which are sent by mobile equipment, wherein the first target contact information is contact information which is updated by the mobile equipment after the first synchronization timestamp, and the first synchronization timestamp is the time when the mobile equipment and the server perform contact information synchronization last time;
comparing the first synchronization timestamp with a second synchronization timestamp stored locally, wherein the second synchronization timestamp is the time when the server and the terminal perform contact person information synchronization last time;
if the first synchronization timestamp is equal to the second synchronization timestamp, modifying the contact information in the server by adopting the first target contact information, and assigning the value of the update timestamp to the second update timestamp;
when the first synchronization timestamp is smaller than the second synchronization timestamp, the server sends a second target Contact to the mobile device for receiving, wherein the second target Contact information is second Contact information updated in the server after the first synchronization timestamp, and the second target Contact is provided with a second update timestamp, so that the mobile device compares values of the same fields in the first target Contact and the corresponding second target Contact, wherein the first target Contact information and the second target Contact information both belong to the same Contact information, and Contact _ id are the same;
when the first target contact information is the same as the second target contact information, ignoring the first target contact information;
when the first target contact information is different from the second target contact information, comparing a first updating time stamp with a second updating time stamp to obtain a second comparison result;
synchronizing the first target contact information and the second target contact information according to the second comparison result;
and recording the updated time information, updating the second synchronization timestamp by adopting the time information, and sending the recorded updated time information to the mobile equipment, so that the mobile equipment updates the first synchronization timestamp by adopting the time information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910727265.4A CN110505290B (en) | 2016-06-03 | 2016-06-03 | Method and device for synchronizing contact information |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910727265.4A CN110505290B (en) | 2016-06-03 | 2016-06-03 | Method and device for synchronizing contact information |
| CN201610395683.4A CN105915636B (en) | 2016-06-03 | 2016-06-03 | A kind of synchronous method and device of contact information |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610395683.4A Division CN105915636B (en) | 2016-06-03 | 2016-06-03 | A kind of synchronous method and device of contact information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110505290A CN110505290A (en) | 2019-11-26 |
| CN110505290B true CN110505290B (en) | 2022-09-02 |
Family
ID=56750432
Family Applications (5)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910727265.4A Active CN110505290B (en) | 2016-06-03 | 2016-06-03 | Method and device for synchronizing contact information |
| CN201610395683.4A Active CN105915636B (en) | 2016-06-03 | 2016-06-03 | A kind of synchronous method and device of contact information |
| CN201910726430.4A Active CN110365797B (en) | 2016-06-03 | 2016-06-03 | Method and device for synchronizing contact information |
| CN201910727266.9A Active CN110474972B (en) | 2016-06-03 | 2016-06-03 | Method and device for synchronizing contact information |
| CN201910726429.1A Active CN110460660B (en) | 2016-06-03 | 2016-06-03 | Method and device for synchronizing contact information |
Family Applications After (4)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610395683.4A Active CN105915636B (en) | 2016-06-03 | 2016-06-03 | A kind of synchronous method and device of contact information |
| CN201910726430.4A Active CN110365797B (en) | 2016-06-03 | 2016-06-03 | Method and device for synchronizing contact information |
| CN201910727266.9A Active CN110474972B (en) | 2016-06-03 | 2016-06-03 | Method and device for synchronizing contact information |
| CN201910726429.1A Active CN110460660B (en) | 2016-06-03 | 2016-06-03 | Method and device for synchronizing contact information |
Country Status (1)
| Country | Link |
|---|---|
| CN (5) | CN110505290B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106899734A (en) * | 2017-03-30 | 2017-06-27 | 努比亚技术有限公司 | Mobile terminal and mobile terminal contact person method of data synchronization |
| CN108243252A (en) * | 2018-01-10 | 2018-07-03 | 上海展扬通信技术有限公司 | The method and terminal, computer readable storage medium that contact head image synchronizes |
| CN109194779A (en) * | 2018-09-14 | 2019-01-11 | 山东浪潮通软信息科技有限公司 | A kind of safe and efficient enterprise directory update method |
| CN111835855A (en) * | 2020-07-17 | 2020-10-27 | 浪潮软件股份有限公司 | Data synchronization method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6535892B1 (en) * | 1999-03-08 | 2003-03-18 | Starfish Software, Inc. | System and methods for exchanging messages between a client and a server for synchronizing datasets |
| CN1984176A (en) * | 2006-05-30 | 2007-06-20 | 华为技术有限公司 | Server and system for managing personal information and synchronization for controlling information |
| CN101232467A (en) * | 2008-02-22 | 2008-07-30 | 中兴通讯股份有限公司 | Method for obtaining information using time jab in real time communicating business |
| CN105227663A (en) * | 2015-10-09 | 2016-01-06 | 努比亚技术有限公司 | A kind of information synchronization method, terminal equipment and server |
| CN105577767A (en) * | 2015-12-17 | 2016-05-11 | 北京乐动卓越科技有限公司 | Contact person information backup method and apparatus |
| CN105635215A (en) * | 2014-11-04 | 2016-06-01 | 阿里巴巴集团控股有限公司 | Contact information synchronization method and device and cloud server |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100586112C (en) * | 2006-05-31 | 2010-01-27 | 阿里巴巴集团控股有限公司 | Method for establishing contact list and managing contact information in instant communication |
| CN100566234C (en) * | 2007-07-16 | 2009-12-02 | 腾讯科技（深圳）有限公司 | Method of data synchronization and processing method, client device, server |
| US20090164667A1 (en) * | 2007-12-21 | 2009-06-25 | General Instrument Corporation | Synchronizing of Personal Content |
| CN101325478A (en) * | 2008-08-06 | 2008-12-17 | 北京北纬通信科技股份有限公司 | Method and system for data synchronization |
| CN102510357A (en) * | 2011-09-26 | 2012-06-20 | 深圳中兴网信科技有限公司 | Synchronous method of enterprise organization structure address book and system thereof |
| KR20130123482A (en) * | 2012-05-03 | 2013-11-13 | 삼성전자주식회사 | Time stamp management method for data synchronizing and terminal thereof |
| EP2862120B1 (en) * | 2012-06-18 | 2019-05-08 | OLogN Technologies AG | Systems, methods and apparatuses for secure time management |
| CN104580454A (en) * | 2014-12-31 | 2015-04-29 | 乐视网信息技术（北京）股份有限公司 | Data synchronizing method, device and system |
-
2016
- 2016-06-03 CN CN201910727265.4A patent/CN110505290B/en active Active
- 2016-06-03 CN CN201610395683.4A patent/CN105915636B/en active Active
- 2016-06-03 CN CN201910726430.4A patent/CN110365797B/en active Active
- 2016-06-03 CN CN201910727266.9A patent/CN110474972B/en active Active
- 2016-06-03 CN CN201910726429.1A patent/CN110460660B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6535892B1 (en) * | 1999-03-08 | 2003-03-18 | Starfish Software, Inc. | System and methods for exchanging messages between a client and a server for synchronizing datasets |
| CN1984176A (en) * | 2006-05-30 | 2007-06-20 | 华为技术有限公司 | Server and system for managing personal information and synchronization for controlling information |
| CN101232467A (en) * | 2008-02-22 | 2008-07-30 | 中兴通讯股份有限公司 | Method for obtaining information using time jab in real time communicating business |
| CN105635215A (en) * | 2014-11-04 | 2016-06-01 | 阿里巴巴集团控股有限公司 | Contact information synchronization method and device and cloud server |
| CN105227663A (en) * | 2015-10-09 | 2016-01-06 | 努比亚技术有限公司 | A kind of information synchronization method, terminal equipment and server |
| CN105577767A (en) * | 2015-12-17 | 2016-05-11 | 北京乐动卓越科技有限公司 | Contact person information backup method and apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105915636A (en) | 2016-08-31 |
| CN105915636B (en) | 2019-08-20 |
| CN110460660A (en) | 2019-11-15 |
| CN110474972A (en) | 2019-11-19 |
| CN110460660B (en) | 2022-05-10 |
| CN110474972B (en) | 2022-07-08 |
| CN110365797B (en) | 2022-03-18 |
| CN110365797A (en) | 2019-10-22 |
| CN110505290A (en) | 2019-11-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2018219178A1 (en) | Data synchronization method and apparatus, server, and storage medium | |
| CN110505290B (en) | Method and device for synchronizing contact information | |
| US9002344B2 (en) | Phone content service | |
| US10469626B2 (en) | Systems and methods of address book management | |
| US10110536B2 (en) | System for managing event notifications to client devices | |
| EP2378437A1 (en) | Data synchronization methods in communication systems | |
| US20090307284A1 (en) | Data backup for a mobile computing device | |
| US20090233591A1 (en) | Data synchronization method between mobile terminal and server | |
| TW200842627A (en) | Techniques to cross-synchronize data | |
| WO2011050714A1 (en) | Method and system for maintaining multi-dimensional relevant information related to contacts in address book | |
| TW201433930A (en) | File tracking methods and network communication devices using the same | |
| US20150032828A1 (en) | Friendly Names for Stored CPM Conversation Histories | |
| CN114185489A (en) | Data synchronization method and device, electronic equipment and storage medium | |
| CN102594874B (en) | Synchronization processing method and device | |
| CN110442844A (en) | Data processing method, device, electronic equipment and storage medium | |
| CN110489483B (en) | Data synchronization method, device, computer equipment and storage medium | |
| WO2018001054A1 (en) | Method and device for synchronizing cloud desktop data | |
| WO2011116616A1 (en) | Method and device for backing up non-read short messages | |
| WO2016197884A1 (en) | Identity-based data processing method and device | |
| CN114928620B (en) | User information synchronization method, apparatus, device, storage medium, and program product | |
| KR20070014324A (en) | Method of automatically synchronizing address information in mobile communication system | |
| CN114546992A (en) | Database migration method and device, storage medium and electronic equipment | |
| CN111953722B (en) | Synchronization method and device for terminal address book | |
| CN110990359A (en) | Method and system for cleaning useless data in synchronous framework | |
| CN111050311A (en) | Data management method, device, storage medium and terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 266071 Shandong city of Qingdao province Jiangxi City Road No. 11 Patentee after: Qingdao Hisense Mobile Communication Technology Co.,Ltd. Address before: 266071 Shandong city of Qingdao province Jiangxi City Road No. 11 Patentee before: HISENSE MOBILE COMMUNICATIONS TECHNOLOGY Co.,Ltd. |