CN105872124B - Contact person synchronization device and method - Google Patents
Contact person synchronization device and method Download PDFInfo
- Publication number
- CN105872124B CN105872124B CN201610188845.7A CN201610188845A CN105872124B CN 105872124 B CN105872124 B CN 105872124B CN 201610188845 A CN201610188845 A CN 201610188845A CN 105872124 B CN105872124 B CN 105872124B
- Authority
- CN
- China
- Prior art keywords
- contact
- local
- cloud
- server
- synchronized
- 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
- 238000000034 method Methods 0.000 title claims abstract description 45
- 230000001360 synchronised effect Effects 0.000 claims abstract description 124
- 238000012986 modification Methods 0.000 claims description 50
- 230000004048 modification Effects 0.000 claims description 50
- 238000013507 mapping Methods 0.000 claims description 20
- 230000004083 survival effect Effects 0.000 claims description 9
- 238000000605 extraction Methods 0.000 claims description 8
- 230000006870 function Effects 0.000 description 18
- 238000012545 processing Methods 0.000 description 17
- 230000008569 process Effects 0.000 description 11
- 238000004891 communication Methods 0.000 description 10
- 230000004044 response Effects 0.000 description 7
- 230000001960 triggered effect Effects 0.000 description 6
- 239000000284 extract Substances 0.000 description 5
- 238000012217 deletion Methods 0.000 description 4
- 230000037430 deletion Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000010295 mobile communication Methods 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001629 suppression Effects 0.000 description 1
- 239000010409 thin film Substances 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4594—Address books, i.e. directories containing contact information about correspondents
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a contact person synchronizing device, comprising: the request module is used for sending a contact person synchronization request to a server so that the server can return a cloud contact person item to be synchronized based on the received contact person synchronization request; the merging module is used for merging the received cloud contact item to be synchronized with the local contact item to obtain the local contact item to be synchronized; and the synchronization module is used for sending the local contact item to be synchronized to the server so that the server can update the cloud contact item based on the received local contact item to be synchronized. The invention also discloses a contact person synchronization method. The method and the device can improve the efficiency of contact person synchronization.
Description
Technical Field
The invention relates to the technical field of networks, in particular to a contact person synchronizing device and method.
Background
The communication range of modern people is wider and wider, and more contact information needs to be stored. In order to prevent the loss of the contact information in the equipment, various mobile phone manufacturers and software manufacturers have introduced a function of cloud synchronization of the contact information. It can be understood that the same contact may have more than one number, such as a contact telephone, a fixed telephone or a mobile phone number in an office or a home, so that a plurality of the same or similar contact names may exist in the device, and the numbers are different, which causes confusion and inconvenience in viewing the contact information. Therefore, when the synchronization server in the cloud synchronizes the contact information, the contact entries of the same contact are usually merged. However, the merging process of the contact entries needs to consume a certain processing resource of the synchronization server, and under a huge user base, the synchronization server is often overloaded, and the efficiency is seriously reduced.
Disclosure of Invention
The invention provides a contact person synchronizing device and method, aiming at improving the efficiency of contact person synchronization.
In order to achieve the above object, the present invention provides a contact synchronization apparatus, including:
the request module is used for sending a contact person synchronization request to a server so that the server can return a cloud contact person item to be synchronized based on the received contact person synchronization request;
the merging module is used for merging the received cloud contact item to be synchronized with the local contact item to obtain the local contact item to be synchronized;
and the synchronization module is used for sending the local contact item to be synchronized to the server so that the server can update the cloud contact item based on the received local contact item to be synchronized.
Optionally, the merging module is further configured to sequentially extract each cloud contact entry in the cloud contact entries to be synchronized; and
acquiring a local identification corresponding to the extracted cloud contact item based on a cloud identification carried by the extracted cloud contact item, and judging whether a modification mark associated with the acquired local identification is a preset value or not;
when the obtained modification mark associated with the local identification is a preset value, creating a new local contact item based on the extracted cloud contact item, allocating a new local identification, associating the allocated local identification with a default cloud identification, and setting the modification mark associated with the allocated local identification as the preset value;
when the obtained modification mark associated with the local identifier is not a preset value, replacing the obtained local contact item associated with the local identifier with the extracted cloud contact item; and
after the extraction operation of the cloud contact items to be synchronized is completed, a contact merging function is called to merge the local contact items marked with the preset values in association modification, and the local contact items obtained after merging and the local contact items not subjected to the merging operation are used as the local contact items to be synchronized.
Optionally, the contact synchronizing apparatus further includes:
and the updating module is used for receiving and updating the mapping relation between the stored cloud end identification and the local identification based on the cloud end identification returned by the server, wherein the returned cloud end identification is returned by the server based on the received local contact item to be synchronized associated with the default cloud end identification.
Optionally, the request module is further configured to send authentication information to the server, so that the server performs an authentication operation based on the received authentication information, and returns a synchronization grant configured with a lifetime when the authentication is passed; and
and sending a contact person synchronization request carrying the synchronization permission to the server so that the server can respond to the contact person synchronization request within the survival time of the synchronization permission.
Optionally, the synchronization module is further configured to call a JSON data protocol to package the local contact entry to be synchronized, and send the obtained packaged data to the server.
In addition, for the above purpose, the present invention further provides a contact person synchronization method, including the following steps:
sending a contact person synchronization request to a server, so that the server returns a cloud contact person item to be synchronized based on the received contact person synchronization request;
merging the received cloud contact item to be synchronized with a local contact item to obtain a local contact item to be synchronized;
and sending the local contact item to be synchronized to the server so that the server can update the cloud contact item based on the received local contact item to be synchronized.
Optionally, the merging the received cloud contact entry to be synchronized with the local contact entry to obtain the local contact entry to be synchronized includes:
step A, sequentially extracting all cloud terminal contact items in the cloud terminal contact items to be synchronized;
b, acquiring a local identification corresponding to the extracted cloud terminal contact person entry based on the cloud terminal identification carried by the extracted cloud terminal contact person entry, and judging whether a modification mark associated with the acquired local identification is a preset value, if so, executing the step C, otherwise, executing the step D;
step C, creating a new local contact item based on the extracted cloud contact item, allocating a new local identification, associating the allocated local identification with a default cloud identification, and setting a modification mark associated with the allocated local identification to a preset value; if the currently extracted cloud contact item is the last item, switching to the step E, and otherwise, switching to the step A;
step D, replacing the obtained local contact item associated with the local identification with the extracted cloud contact item; if the currently extracted cloud contact item is the last item, switching to the step E, and otherwise, switching to the step A;
and step E, calling a contact merging function to merge the local contact items marked as the preset values by the association modification, and taking the local contact items obtained after merging and the local contact items which are not subjected to the merging operation as the local contact items to be synchronized.
Optionally, after the step of sending the local contact entry to be synchronized to the server, the method further includes:
and receiving and updating the mapping relation between the stored cloud end identification and the local identification based on the cloud end identification returned by the server, wherein the returned cloud end identification is returned by the server based on the received local contact item to be synchronized associated with the default cloud end identification.
Optionally, before the step of sending the contact synchronization request to the server, the method further includes:
sending authentication information to the server so that the server can carry out authentication operation based on the received authentication information, and returning a synchronous permission configured with a survival time when the authentication is passed;
the step of sending the contact synchronization request to the server comprises:
and sending a contact person synchronization request carrying the synchronization permission to the server so that the server can respond to the contact person synchronization request within the survival time of the synchronization permission.
Optionally, the step of sending the local contact entry to be synchronized to the server includes:
and calling a JSON data protocol to package the local contact item to be synchronized, and sending the obtained packaged data to the server.
The contact person synchronization device and the method can reduce the processing pressure of the synchronization server by dispersing the merging processing of the contact person items which are intensively executed in the synchronization server to each independent contact person synchronization device at the user side for execution, so that the synchronization server can have more processing resources to provide normal contact person synchronization service, and the efficiency of contact person synchronization is improved.
Drawings
Fig. 1 is a schematic diagram of a hardware structure of a mobile terminal implementing various embodiments of the present invention;
FIG. 2 is a functional block diagram of a first embodiment of a contact synchronization apparatus according to the present invention;
FIG. 3 is a functional block diagram of a contact synchronization apparatus according to a third embodiment of the present invention;
FIG. 4 is a flowchart illustrating a first embodiment of a contact synchronization method according to the present invention;
FIG. 5 is a flowchart illustrating a contact synchronization method according to a second embodiment of the present invention;
fig. 6 is a flowchart illustrating a contact synchronization method according to a third embodiment of the present invention.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. It should be noted that the embodiments and features of the embodiments of the present invention may be arbitrarily combined with each other without conflict.
A mobile terminal implementing various embodiments of the present invention will now be described with reference to the accompanying drawings. In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in themselves. Thus, "module" and "component" may be used in a mixture.
The mobile terminal may be implemented in various forms. For example, the mobile terminal described in the present invention may include devices such as a mobile phone, a smart phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a navigation device, etc., and it will be understood by those skilled in the art that the configuration according to the embodiment of the present invention can be applied to a fixed type terminal in addition to elements particularly used for mobile purposes.
Fig. 1 is a schematic diagram of a hardware structure of an optional mobile terminal for implementing various embodiments of the present invention.
The mobile terminal 100 may include a wireless communication unit 110, an a/V (audio/video) input unit 120, a user input unit 130, a sensing unit 140, an output unit 150, a memory 160, an interface unit 170, a controller 180, and a power supply unit 190, etc. Fig. 1 illustrates a mobile terminal having various components, but it is to be understood that not all illustrated components are required to be implemented. More or fewer components may alternatively be implemented. Elements of the mobile terminal will be described in detail below.
The wireless communication unit 110 typically includes one or more components that allow radio communication between the mobile terminal 100 and a wireless communication system or network. For example, the wireless communication unit may include at least one of a mobile communication module 111 and a wireless internet module 112.
The mobile communication module 111 transmits and/or receives radio signals to and/or from at least one of a base station (e.g., access point, node B, etc.), an external terminal, and a server. Such radio signals may include voice call signals, video call signals, or various types of data transmitted and/or received according to text and/or multimedia messages.
The wireless internet module 112 supports wireless internet access of the mobile terminal. The module may be internally or externally coupled to the terminal. The wireless internet access technology to which the module relates may include WLAN (wireless LAN) (Wi-Fi), Wibro (wireless broadband), Wimax (worldwide interoperability for microwave access), HSDPA (high speed downlink packet access), and the like.
The a/V input unit 120 is used to receive an audio or video signal. The a/V input unit 120 may include a camera 121 and a microphone 122, and the camera 121 processes image data of still pictures or video obtained by an image capturing apparatus in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 151. The image frames processed by the cameras 121 may be stored in the memory 160 (or other storage medium) or transmitted via the wireless communication unit 110, and two or more cameras 121 may be provided according to the construction of the mobile terminal. The microphone 122 may receive sounds (audio data) via the microphone in a phone call mode, a recording mode, a voice recognition mode, or the like, and can process such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via the mobile communication module 112 in case of a phone call mode. The microphone 122 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting audio signals.
The user input unit 130 may generate key input data according to a command input by a user to control various operations of the mobile terminal. The user input unit 130 allows a user to input various types of information, and may include a keyboard, dome sheet, touch pad (e.g., a touch-sensitive member that detects changes in resistance, pressure, capacitance, and the like due to being touched), scroll wheel, joystick, and the like. In particular, when the touch pad is superimposed on the display unit 151 in the form of a layer, a touch screen may be formed.
The sensing unit 140 detects a current state of the mobile terminal 100 (e.g., an open or closed state of the mobile terminal 100), a position of the mobile terminal 100, presence or absence of contact (i.e., touch input) by a user with the mobile terminal 100, an orientation of the mobile terminal 100, acceleration or deceleration movement and direction of the mobile terminal 100, and the like, and generates a command or signal for controlling an operation of the mobile terminal 100. For example, when the mobile terminal 100 is implemented as a slide-type mobile phone, the sensing unit 140 may sense whether the slide-type phone is opened or closed. In addition, the sensing unit 140 can detect whether the power supply unit 190 supplies power or whether the interface unit 170 is coupled with an external device.
The interface unit 170 serves as an interface through which at least one external device is connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The identification module may store various information for authenticating a user using the mobile terminal 100 and may include a User Identity Module (UIM), a Subscriber Identity Module (SIM), a Universal Subscriber Identity Module (USIM), and the like. In addition, a device having an identification module (hereinafter, referred to as an "identification device") may take the form of a smart card, and thus, the identification device may be connected with the mobile terminal 100 via a port or other connection means. The interface unit 170 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal and the external device.
In addition, when the mobile terminal 100 is connected with an external cradle, the interface unit 170 may serve as a path through which power is supplied from the cradle to the mobile terminal 100 or may serve as a path through which various command signals input from the cradle are transmitted to the mobile terminal. Various command signals or power input from the cradle may be used as signals for recognizing whether the mobile terminal is accurately mounted on the cradle. The output unit 150 is configured to provide output signals (e.g., audio signals, video signals, alarm signals, vibration signals, etc.) in a visual, audio, and/or tactile manner. The output unit 150 may include a display unit 151, an audio output module 152, and the like.
The display unit 151 may display information processed in the mobile terminal 100. For example, when the mobile terminal 100 is in a phone call mode, the display unit 151 may display a User Interface (UI) or a Graphical User Interface (GUI) related to a call or other communication (e.g., text messaging, multimedia file downloading, etc.). When the mobile terminal 100 is in a video call mode or an image capturing mode, the display unit 151 may display a captured image and/or a received image, a UI or GUI displaying a video or an image and related functions, and the like.
Meanwhile, when the display unit 151 and the touch pad are overlapped with each other in the form of a layer to form a touch screen, the display unit 151 may serve as an input device and an output device. The display unit 151 may include at least one of a Liquid Crystal Display (LCD), a thin film transistor LCD (TFT-LCD), an Organic Light Emitting Diode (OLED) display, a flexible display, a three-dimensional (3D) display, and the like. Some of these displays may be configured to be transparent to allow a user to view from the outside, which may be referred to as transparent displays, and a typical transparent display may be, for example, a TOLED (transparent organic light emitting diode) display or the like. Depending on the particular desired implementation, the mobile terminal 100 may include two or more display units (or other display devices), for example, the mobile terminal may include an external display unit (not shown) and an internal display unit (not shown). The touch screen may be used to detect a touch input pressure as well as a touch input position and a touch input area.
The audio output module 152 may convert audio data received by the wireless communication unit 110 or stored in the memory 160 into an audio signal and output as sound when the mobile terminal is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output module 152 may provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output module 152 may include a speaker, a buzzer, and the like.
The memory 160 may store a software program or the like for processing and controlling operations performed by the controller 180, for example, may store a software program implementing the contact synchronization method of the present invention, or may temporarily store data (e.g., a phonebook, messages, still images, videos, and the like) that has been or will be output. Also, the memory 160 may store data regarding various ways of vibration and audio signals output when a touch is applied to the touch screen.
The memory 160 may include at least one type of storage medium including a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. Also, the mobile terminal 100 may cooperate with a network storage device that performs a storage function of the memory 160 through a network connection.
The controller 180 generally controls the overall operation of the mobile terminal. For example, the controller 180 performs control and processing related to voice calls, data communications, video calls, and the like. The controller 180 may perform a mode recognition process to recognize a handwriting input or a picture drawing input performed on the touch screen as a character or an image.
The power supply unit 190 receives external power or internal power and provides appropriate power required to operate various elements and components under the control of the controller 180.
The various embodiments described herein may be implemented in a computer-readable medium using, for example, computer software, hardware, or any combination thereof. For a hardware implementation, the embodiments described herein may be implemented using at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a processor, a controller, a microcontroller, a microprocessor, an electronic unit designed to perform the functions described herein, and in some cases, such embodiments may be implemented in the controller 180. For a software implementation, the implementation such as a process or a function may be implemented with a separate software module that allows performing at least one function or operation. The software codes may be implemented by software applications (or programs) written in any suitable programming language, which may be stored in the memory 160 and executed by the controller 180.
Based on the above mobile terminal hardware structure, various embodiments of the contact synchronization device of the present invention are provided.
Referring to fig. 2, in a first embodiment of the contact synchronization apparatus of the present invention, the contact synchronization apparatus includes:
the request module 10 is configured to send a contact synchronization request to the server, so that the server returns a cloud contact entry to be synchronized based on the received contact synchronization request;
it should be noted that, the contact synchronization apparatus provided in this embodiment is operated based on the mobile terminal, and may be specifically configured to be operated by being built in the mobile terminal, or being externally installed to the mobile terminal, or being implemented in a form of a software module. The following description will be given taking an example in which the contact synchronization apparatus is built in the mobile terminal.
In this embodiment, the operation of the request module 10 for sending the contact synchronization request may be automatically triggered when the mobile terminal where the mobile terminal is located reaches a preset synchronization time point, or triggered when the mobile terminal where the mobile terminal is located receives the synchronization operation of the user, or triggered when other conditions meet the trigger condition.
Further, in this embodiment, in order to ensure the security of the contact entries and the server, the request module 10 is further configured to send authentication information to the server, so that the server performs an authentication operation based on the received authentication information, and returns a synchronization permission configured with a lifetime when the authentication is passed; and
and sending the contact person synchronization request carrying the received synchronization permission to the server, so that the server can respond to the received contact person synchronization request within the survival time of the synchronization permission.
The authentication information sent by the request module 10 includes the user identifier and the password of the home subscriber of the mobile terminal where the mobile terminal is located. The server verifies whether the user is legal or not through the user identification and the password, and if so, the authentication is passed.
The contact synchronization request sent by the request module 10 is shown in table 1.
TABLE 1
The server storage record structure is shown in table 2.
TABLE 2
In this embodiment, after receiving the contact synchronization request sent by the request module 10, the server first verifies whether syncocken (synchronization permission) is valid, that is, whether the lifetime is exceeded; when the Synctoken is effective, all records of Version > LastSyncversion in the data set of the target user are searched through the mapping relation between the user identification generated in the authentication operation and the Synctoken, and the cloud contact items in the searched records are used as the cloud contact items to be synchronized.
The merging module 20 is configured to merge the received cloud contact entry to be synchronized with the local contact entry to obtain a local contact entry to be synchronized;
the merging module 20 merges the received cloud contact entry to be synchronized with the local contact entry of the mobile terminal when the mobile terminal where the mobile terminal is located receives the cloud contact entry to be synchronized returned by the server, and specifically may call the contact merging function of the mobile terminal where the mobile terminal is located to complete the merging operation of the cloud contact entry to be synchronized and the local contact entry to be synchronized, and take all the local contact entries of the mobile terminal where the mobile terminal is located after the merging operation is completed as the local contact entries to be synchronized.
The synchronization module 30 is configured to send the obtained local contact entry to be synchronized to the server, so that the server updates the cloud contact entry based on the received local contact entry to be synchronized.
In this embodiment, after the merging module 20 completes the merging operation of the cloud contact entry to be synchronized and the local contact entry, and obtains the local contact entry to be synchronized, the synchronization module 30 sends the obtained local contact entry to be synchronized to the server.
After receiving the local contact item to be synchronized sent by the synchronization module 30, the server updates the corresponding cloud contact item based on the received local contact item to be synchronized, so that the cloud contact item stored in the server and the local contact item stored in the mobile terminal are kept synchronized.
Further, in this embodiment, in order to increase the support type of the contact entry to avoid additional special processing, the synchronization module 30 is further configured to call a JSON data protocol to encapsulate the to-be-synchronized local contact entry, and send the obtained encapsulated data to the server.
Correspondingly, after receiving the encapsulated data sent by the synchronization module 30, the server calls a JSON data protocol to decapsulate the received encapsulated data, and thus the local contact item to be synchronized can be obtained.
It should be noted that json (javascript Object notification) is a lightweight data exchange format, which is based on a subset of ECMAScript. JSON employs a text format that is completely language independent, but also uses conventions similar to the family of C languages (including C, C + +, C #, Java, JavaScript, Perl, Python, etc.). These properties make JSON an ideal data exchange language. The network transmission rate can be improved.
The method and the device have the advantages that the merging processing of the contact items which is intensively executed in the synchronization server is distributed to each independent contact synchronization device at the user side for execution, so that the processing pressure of the synchronization server can be reduced, the synchronization server can have more processing resources to provide normal contact synchronization service, and the efficiency of contact synchronization is improved.
Further, a second embodiment of the contact synchronization apparatus of the present invention is provided, and this embodiment is based on the first embodiment, adds a detailed description of the implementation of the merging module 20, and continues with reference to fig. 2, and the contact synchronization apparatus includes:
the request module 10 is configured to send a contact synchronization request to the server, so that the server returns a cloud contact entry to be synchronized based on the received contact synchronization request;
the merging module 20 is configured to sequentially extract each cloud contact entry from the received cloud contact entries to be synchronized; and
acquiring a local identifier corresponding to the extracted cloud contact item based on a cloud identifier carried by the extracted cloud contact item, and judging whether a modification mark associated with the acquired local identifier is a preset value or not;
when the modification mark associated with the acquired local identification is a preset value, creating a new local contact item based on the extracted cloud terminal contact item, allocating a new local identification, associating the allocated local identification with the default cloud terminal identification, and setting the modification mark associated with the allocated local identification as the preset value;
when the modification mark associated with the acquired local identification is not a preset value, replacing the local contact item associated with the acquired local identification with the extracted cloud contact item; and
after the extraction operation of the cloud contact items to be synchronized is completed, calling a contact merging function to merge the local contact items marked with the preset values in association modification, and taking the local contact items obtained after merging and the local contact items which are not subjected to the merging operation as the local contact items to be synchronized;
the synchronization module 30 is configured to send the obtained local contact entry to be synchronized to the server, so that the server updates the cloud contact entry based on the received local contact entry to be synchronized.
In the present embodiment, the mobile terminal storage record structure is shown in table 3.
TABLE 3
It should be noted that each local contact entry stored by the mobile terminal is associated with a corresponding storage record.
In this embodiment, the structure of the response of the server based on the contact synchronization request sent by the request module 10 is shown in table 4.
TABLE 4
The structure of ServerData is shown in table 5.
TABLE 5
The structure of the servereltem list is shown in table 6.
TABLE 6
In this embodiment, after receiving a response returned by the server based on the contact synchronization request, the mobile terminal of the merging module 20 sequentially processes each serveretem (including the cloud identifier and the corresponding cloud contact entry) in the response, and specifically, the merging module 20 sequentially extracts each cloud contact entry in the received cloud contact entries to be synchronized; when a cloud contact item is extracted each time, if a deletion mark (Deleted in table 6) of the extracted cloud contact item is true, deleting a corresponding storage record and a local contact item based on a cloud identifier (ServerID in table 6) carried by the extracted cloud contact item and a mapping relation (shown in table 3) between the cloud identifier and the local identifier stored in a mobile terminal where the cloud contact item is located, otherwise, judging whether a modification mark (Dirty in table 1) associated with the corresponding local identifier is true (a preset value);
when the modification flag associated with the corresponding local identifier is true, the merging module 20 creates a new local contact entry based on the extracted cloud contact entry, allocates a new local identifier, associates the new local identifier with the default cloud identifier (which is 0), and sets the modification flag of the new local identifier to true;
when the modification mark associated with the corresponding local identifier is false, the merging module 20 replaces the local contact entry associated with the corresponding local identifier with the extracted cloud contact entry; and
after the extraction operation of the cloud contact item to be synchronized is completed (that is, each serveretem is extracted and judged), the merging module 20 calls the contact merging function of the mobile terminal where the mobile terminal is located to merge the local contact items marked as true in the current modification, and the local contact items obtained after merging and the local contact items not subjected to merging are used as local contact items to be synchronized.
When a local identifier associated with the cloud identifier carried by the extracted cloud contact item does not exist locally, the merging module 20 directly calls a contact merging function of the mobile terminal where the mobile terminal is located to merge the cloud contact item, so as to merge the cloud contact item into possible local contact items, and if the merging is successful, the modification mark of the merged local contact item is set to true; and if the combination fails, creating a new local contact item based on the extracted cloud end contact item, distributing a new local identification, associating the new local identification with the default cloud end identification, and setting the modification mark of the new local identification as false.
Further, referring to fig. 3, a third embodiment of the contact synchronization apparatus of the present invention is provided, where the present embodiment is based on the second embodiment and includes:
the request module 10 is configured to send a contact synchronization request to the server, so that the server returns a cloud contact entry to be synchronized based on the received contact synchronization request;
the merging module 20 is configured to sequentially extract each cloud contact entry from the received cloud contact entries to be synchronized; and
acquiring a local identifier corresponding to the extracted cloud contact item based on a cloud identifier carried by the extracted cloud contact item, and judging whether a modification mark associated with the acquired local identifier is a preset value or not;
when the modification mark associated with the acquired local identification is a preset value, creating a new local contact item based on the extracted cloud terminal contact item, allocating a new local identification, associating the allocated local identification with the default cloud terminal identification, and setting the modification mark associated with the allocated local identification as the preset value;
when the modification mark associated with the acquired local identification is not a preset value, replacing the local contact item associated with the acquired local identification with the extracted cloud contact item; and
after the extraction operation of the cloud contact items to be synchronized is completed, calling a contact merging function to merge the local contact items marked with the preset values in association modification, and taking the local contact items obtained after merging and the local contact items which are not subjected to the merging operation as the local contact items to be synchronized;
the synchronization module 30 is configured to send the obtained local contact entry to be synchronized to the server, so that the server updates the cloud contact entry based on the received local contact entry to be synchronized;
and the updating module 40 is configured to receive and update the mapping relationship between the stored cloud identifier and the local identifier based on the cloud identifier returned by the server, where the cloud identifier returned by the server is returned by the server based on the received local contact entry to be synchronized associated with the default cloud identifier.
It should be noted that the difference between the present embodiment and the second embodiment is that the update module 40 is added in the present embodiment, and the implementation of the update module 40 is described below.
In this embodiment, the merge module 20 sets LastSyncVersion to ServerVersion after the merge operation is completed, and records the SessionID in the response.
The synchronization module 30 sends a push-up request to the server, the structure of which is shown in table 7.
TABLE 7
The structure of ClientData is shown in Table 8.
TABLE 8
The structure of the ClientItem list is shown in table 9.
TABLE 9
After receiving the push-up request sent by the synchronization module 30, the server verifies the SessionID and LastSyncVersion in the push-up request, and if the SessionID is invalid (the SessionID exceeds the lifetime and is invalid) or the LastSyncVersion < ServerVersion, returns indication information to the mobile terminal where the synchronization module 30 is located, and indicates the request module 10 to reinitiate the contact synchronization request; processing the ClientItems one by one when the verification is passed, specifically, sequentially extracting each local contact item in the local contact items to be synchronized by the server; when a local contact item is extracted each time, if a deletion mark (Deleted in table 9) of the extracted local contact item is true, deleting the corresponding cloud contact item based on a cloud identifier (ServerID) carried by the extracted local contact item and a mapping relation (shown in table 2) between the cloud identifier stored in the server and the cloud contact item, otherwise, judging whether the cloud identifier carried by the extracted local contact item is a default cloud identifier;
when the cloud end identification carried by the extracted local contact item is the default cloud end identification, creating a new cloud end contact item based on the extracted local contact item, distributing a new cloud end identification, and associating the new cloud end identification with the local identification carried by the extracted local contact item;
when the cloud identification carried by the extracted local contact item is not the default cloud identification, replacing the cloud contact item associated with the cloud identification carried by the extracted local contact item with the extracted local contact item, and updating the Version field of the record to be Serverversion + 1;
and after the extraction operation of the local contact item to be synchronized is completed, the server updates the Serverversion to be Serverversion + 1.
When the cloud end identification carried by the extracted local contact item is not the default cloud end identification and no cloud end contact item associated with the cloud end identification carried by the extracted local contact item exists, the server creates a new cloud end contact item based on the extracted local contact item, allocates a new cloud end identification, and associates the new cloud end identification with the local identification carried by the extracted local contact item.
After the server completes the updating operation, the server returns the mapping relationship between the new cloud identifier and the local identifier to the mobile terminal where the updating module 40 is located, so that the updating module 40 updates the mapping relationship between the cloud identifier and the local identifier stored in the mobile terminal where the updating module is located, and the synchronization of the mapping relationship between the service side and the mapping relationship between the user side is realized.
Further, the present invention also provides a contact person synchronization method, and with reference to fig. 2 and fig. 4, in a first embodiment of the contact person synchronization method of the present invention, the contact person synchronization method includes:
step S10, sending a contact person synchronization request to a server, so that the server can return a cloud contact person item to be synchronized based on the received contact person synchronization request;
it should be noted that the contact synchronization method provided in this embodiment is executed by the contact synchronization apparatus shown in fig. 2, and the contact synchronization apparatus is operated based on the mobile terminal, and may be specifically configured to be operated internally in the mobile terminal, or operated externally in the mobile terminal, or implemented in a form of a software module. The following description will be given taking an example in which the contact synchronization apparatus is built in the mobile terminal.
In this embodiment, the operation of the request module 10 for sending the contact synchronization request may be automatically triggered when the mobile terminal where the mobile terminal is located reaches a preset synchronization time point, or triggered when the mobile terminal where the mobile terminal is located receives the synchronization operation of the user, or triggered when other conditions meet the trigger condition.
Further, in this embodiment, in order to ensure the security of the contact entry and the server, step S10 is preceded by:
sending authentication information to a server for the server to perform authentication operation based on the received authentication information, and returning a synchronization permission configured with a survival time when the authentication is passed;
step S10 includes:
and sending the contact person synchronization request carrying the synchronization permission to the server, so that the server can respond to the received contact person synchronization request within the survival time of the synchronization permission.
Specifically, the authentication information sent by the request module 10 includes the user identifier and the password of the home subscriber of the mobile terminal where the mobile terminal is located. The server verifies whether the user is legal or not through the user identification and the password, and if so, the authentication is passed.
With reference to table 1 and table 2, in this embodiment, after receiving the contact synchronization request sent by the request module 10, the server first verifies whether syncocken (synchronization permission) is valid, that is, whether the lifetime is exceeded; when the Synctoken is effective, all records of Version > LastSyncversion in the data set of the target user are searched through the mapping relation between the user identification generated in the authentication operation and the Synctoken, and the cloud contact items in the searched records are used as the cloud contact items to be synchronized.
Step S20, merging the received cloud contact item to be synchronized with the local contact item to obtain the local contact item to be synchronized;
and step S30, sending the obtained local contact item to be synchronized to the server, so that the server can update the cloud contact item based on the received local contact item to be synchronized.
In this embodiment, after the merging module 20 completes the merging operation of the cloud contact entry to be synchronized and the local contact entry, and obtains the local contact entry to be synchronized, the synchronization module 30 sends the obtained local contact entry to be synchronized to the server.
After receiving the local contact item to be synchronized sent by the synchronization module 30, the server updates the corresponding cloud contact item based on the received local contact item to be synchronized, so that the cloud contact item stored in the server and the local contact item stored in the mobile terminal are kept synchronized.
Further, in this embodiment, to add a support type of the contact entry to avoid an additional special process, step S30 includes:
and calling a JSON data protocol to package the local contact item to be synchronized, and sending the obtained packaged data to the server.
In this embodiment, when the synchronization module 30 executes the sending operation of the local contact item to be synchronized, the JSON data protocol of the mobile terminal where the synchronization module is located is called to package the local contact item to be synchronized, and the obtained packaged data is sent to the server.
Correspondingly, after receiving the encapsulated data sent by the synchronization module 30, the server calls a JSON data protocol to decapsulate the received encapsulated data, and thus the local contact item to be synchronized can be obtained.
It should be noted that json (javascript Object notification) is a lightweight data exchange format, which is based on a subset of ECMAScript. JSON employs a text format that is completely language independent, but also uses conventions similar to the family of C languages (including C, C + +, C #, Java, JavaScript, Perl, Python, etc.). These properties make JSON an ideal data exchange language. The network transmission rate can be improved.
The method and the device have the advantages that the merging processing of the contact items which is intensively executed in the synchronization server is distributed to each independent contact synchronization device at the user side for execution, so that the processing pressure of the synchronization server can be reduced, the synchronization server can have more processing resources to provide normal contact synchronization service, and the efficiency of contact synchronization is improved.
Further, a second embodiment of the contact synchronization method of the present invention is provided, where the embodiment is based on the first embodiment, and a detailed description of a merging processing step of a cloud contact entry to be synchronized and a local contact entry is added, and with reference to fig. 5, the contact synchronization method includes:
step S10, sending a contact person synchronization request to a server, so that the server can return a cloud contact person item to be synchronized based on the received contact person synchronization request;
step S201, sequentially extracting all cloud terminal contact items in the received cloud terminal contact items to be synchronized;
step S202, acquiring a local identification corresponding to the extracted cloud terminal contact item based on a cloud terminal identification carried by the extracted cloud terminal contact item, and judging whether a modification mark associated with the acquired local identification is a preset value, if so, executing step S203, otherwise, executing step S204;
step S203, creating a new local contact item based on the extracted cloud contact item, allocating a new local identification, associating the allocated local identification with a default cloud identification, and setting a modification mark associated with the allocated local identification to a preset value; if the currently extracted cloud contact entry is the last entry, executing the step S205, otherwise, executing the step 201;
step S204, replacing the local contact item associated with the acquired local identifier with the extracted cloud contact item; if the currently extracted cloud contact entry is the last entry, executing the step S205, otherwise, executing the step 201;
step S205, calling a contact merging function to merge the local contact items marked as the preset values by the association modification, and taking the local contact items obtained after merging and the local contact items not subjected to the merging operation as local contact items to be synchronized;
and step S30, sending the obtained local contact item to be synchronized to the server, so that the server can update the cloud contact item based on the received local contact item to be synchronized.
In the present embodiment, the mobile terminal storage record structure is shown in table 3. And each local contact item stored by the mobile terminal is associated with a corresponding storage record.
With reference to tables 4 to 6, after receiving a response returned by the server based on the contact synchronization request, the combining module 20 sequentially processes each serveretem (including the cloud identifier and the corresponding cloud contact entry) in the response, specifically, the combining module 20 sequentially extracts each cloud contact entry in the received cloud contact entries to be synchronized; when a cloud contact item is extracted each time, if a deletion mark (Deleted in table 6) of the extracted cloud contact item is true, deleting a corresponding storage record and a local contact item based on a cloud identifier (ServerID in table 6) carried by the extracted cloud contact item and a mapping relation (shown in table 3) between the cloud identifier and the local identifier stored in a mobile terminal where the cloud contact item is located, otherwise, judging whether a modification mark (Dirty in table 1) associated with the corresponding local identifier is true (a preset value);
when the modification flag associated with the corresponding local identifier is true, the merging module 20 creates a new local contact entry based on the extracted cloud contact entry, allocates a new local identifier, associates the new local identifier with the default cloud identifier (which is 0), and sets the modification flag of the new local identifier to true;
when the modification mark associated with the corresponding local identifier is false, the merging module 20 replaces the local contact entry associated with the corresponding local identifier with the extracted cloud contact entry; and
after the extraction operation of the cloud contact item to be synchronized is completed (that is, each serveretem is extracted and judged), the merging module 20 calls the contact merging function of the mobile terminal where the mobile terminal is located to merge the local contact items marked as true in the current modification, and the local contact items obtained after merging and the local contact items not subjected to merging are used as local contact items to be synchronized.
When a local identifier associated with the cloud identifier carried by the extracted cloud contact item does not exist locally, the merging module 20 directly calls a contact merging function of the mobile terminal where the mobile terminal is located to merge the cloud contact item, so as to merge the cloud contact item into possible local contact items, and if the merging is successful, the modification mark of the merged local contact item is set to true; and if the combination fails, creating a new local contact item based on the extracted cloud end contact item, distributing a new local identification, associating the new local identification with the default cloud end identification, and setting the modification mark of the new local identification as false.
Further, referring to fig. 6, a third embodiment of the contact synchronization method of the present invention is provided, where the present embodiment is based on the second embodiment and includes:
step S10, sending a contact person synchronization request to a server, so that the server can return a cloud contact person item to be synchronized based on the received contact person synchronization request;
step S201, sequentially extracting all cloud terminal contact items in the received cloud terminal contact items to be synchronized;
step S202, acquiring a local identification corresponding to the extracted cloud terminal contact item based on a cloud terminal identification carried by the extracted cloud terminal contact item, and judging whether a modification mark associated with the acquired local identification is a preset value, if so, executing step S203, otherwise, executing step S204;
step S203, creating a new local contact item based on the extracted cloud contact item, allocating a new local identification, associating the allocated local identification with a default cloud identification, and setting a modification mark associated with the allocated local identification to a preset value; if the currently extracted cloud contact entry is the last entry, executing the step S205, otherwise, executing the step 201;
step S204, replacing the local contact item associated with the acquired local identifier with the extracted cloud contact item; if the currently extracted cloud contact entry is the last entry, executing the step S205, otherwise, executing the step 201;
step S205, calling a contact merging function to merge the local contact items marked as the preset values by the association modification, and taking the local contact items obtained after merging and the local contact items not subjected to the merging operation as local contact items to be synchronized;
step S30, sending the obtained local contact item to be synchronized to a server, so that the server can update the cloud contact item based on the received local contact item to be synchronized;
and step S40, receiving and updating the mapping relation between the stored cloud end identification and the local identification based on the cloud end identification returned by the server, wherein the cloud end identification returned by the server is returned by the server based on the received local contact item to be synchronized related to the default cloud end identification.
It should be noted that the difference between the present embodiment and the second embodiment is that, referring to fig. 3, the contact synchronization apparatus in the present embodiment adds an update module 40, and the implementation of the update module 40 is described below.
In this embodiment, the merge module 20 sets LastSyncVersion to ServerVersion after the merge operation is completed, and records the SessionID in the response.
Referring to tables 7 to 9 in combination, the synchronization module 30 sends a push-up request to the server; after receiving the push-up request sent by the synchronization module 30, the server verifies the SessionID and LastSyncVersion in the push-up request, and if the SessionID is invalid (the SessionID exceeds the lifetime and is invalid) or the LastSyncVersion < ServerVersion, returns indication information to the mobile terminal where the synchronization module 30 is located, and indicates the request module 10 to reinitiate the contact synchronization request; when the verification passes, processing the ClientItems one by one (as shown in table 9), specifically, sequentially extracting each local contact item in the local contact items to be synchronized by the server; when a local contact item is extracted each time, if a deletion mark (Deleted in table 9) of the extracted local contact item is true, deleting the corresponding cloud contact item based on a cloud identifier (ServerID) carried by the extracted local contact item and a mapping relation (shown in table 2) between the cloud identifier stored in the server and the cloud contact item, otherwise, judging whether the cloud identifier carried by the extracted local contact item is a default cloud identifier;
when the cloud identification carried by the extracted local contact item is the default cloud identification, creating a new cloud contact item based on the extracted local contact item, distributing a new cloud identification, and associating the new cloud identification with the local identification carried by the extracted local contact item;
when the cloud identification carried by the extracted local contact item is not the default cloud identification, replacing the cloud contact item associated with the cloud identification carried by the extracted local contact item with the extracted local contact item, and updating the Version field of the record to be Serverversion + 1;
and after the extraction operation of the local contact item to be synchronized is completed, the server updates the Serverversion to be Serverversion + 1.
When the cloud end identification carried by the extracted local contact item is not the default cloud end identification and no cloud end contact item associated with the cloud end identification carried by the extracted local contact item exists, the server creates a new cloud end contact item based on the extracted local contact item, allocates a new cloud end identification, and associates the new cloud end identification with the local identification carried by the extracted local contact item.
After the server completes the updating operation, the server returns the mapping relationship between the new cloud identifier and the local identifier to the mobile terminal where the updating module 40 is located, so that the updating module 40 updates the mapping relationship between the cloud identifier and the local identifier stored in the mobile terminal where the updating module is located, and the synchronization of the mapping relationship between the service side and the mapping relationship between the user side is realized.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus 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 apparatus. 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 apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the invention. However, it will be apparent to one skilled in the art that the specific details are not required in order to practice the invention. The foregoing descriptions of specific embodiments of the present invention have been presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching. The embodiments are shown and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalents.
Claims (10)
1. A contact synchronization apparatus, comprising:
the request module is used for sending a contact person synchronization request to a server so that the server can return a cloud contact person item to be synchronized based on the received contact person synchronization request;
the merging module is used for merging the received cloud contact item to be synchronized with the local contact item to obtain the local contact item to be synchronized;
the synchronization module is used for sending the local contact item to be synchronized to the server so that the server can update the cloud contact item based on the received local contact item to be synchronized;
the merging module is further used for sequentially extracting all cloud contact entries in the cloud contact entries to be synchronized; and
acquiring a local identifier corresponding to the extracted cloud contact item based on a cloud identifier carried by the extracted cloud contact item, and judging whether a modification mark associated with the acquired local identifier is a preset value or not;
and when the obtained modification mark associated with the local identifier is a preset value, creating a new local contact item based on the extracted cloud contact item, allocating a new local identifier, associating the allocated local identifier with a default cloud identifier, and setting the modification mark associated with the allocated local identifier as the preset value.
2. The contact synchronization apparatus of claim 1, wherein the merge module is further configured to,
when the obtained modification mark associated with the local identifier is not a preset value, replacing the obtained local contact item associated with the local identifier with the extracted cloud contact item; and
after the extraction operation of the cloud contact items to be synchronized is completed, a contact merging function is called to merge the local contact items marked with the preset values in association modification, and the local contact items obtained after merging and the local contact items not subjected to the merging operation are used as the local contact items to be synchronized.
3. The contact synchronization apparatus of claim 2, further comprising:
and the updating module is used for receiving and updating the mapping relation between the stored cloud end identification and the local identification based on the cloud end identification returned by the server, wherein the returned cloud end identification is returned by the server based on the received local contact item to be synchronized associated with the default cloud end identification.
4. The contact synchronization device according to any of claims 1-3, wherein the request module is further configured to send authentication information to the server, so that the server performs an authentication operation based on the received authentication information, and returns a synchronization permission configured with a lifetime when the authentication is passed; and
and sending a contact person synchronization request carrying the synchronization permission to the server so that the server can respond to the contact person synchronization request within the survival time of the synchronization permission.
5. The contact synchronization apparatus according to any of claims 1 to 3, wherein the synchronization module is further configured to invoke a JSON data protocol to encapsulate the local contact entry to be synchronized, and send the obtained encapsulated data to the server.
6. A contact synchronization method, characterized in that the contact synchronization method comprises the following steps:
sending a contact person synchronization request to a server, so that the server returns a cloud contact person item to be synchronized based on the received contact person synchronization request;
merging the received cloud contact item to be synchronized with a local contact item to obtain a local contact item to be synchronized;
sending the local contact item to be synchronized to the server so that the server can update a cloud contact item based on the received local contact item to be synchronized;
the step of merging the received cloud contact item to be synchronized with the local contact item to obtain the local contact item to be synchronized comprises:
step A, sequentially extracting all cloud terminal contact items in the cloud terminal contact items to be synchronized;
b, acquiring a local identification corresponding to the extracted cloud terminal contact person entry based on the cloud terminal identification carried by the extracted cloud terminal contact person entry, and judging whether a modification mark associated with the acquired local identification is a preset value or not;
and when the modification mark associated with the acquired local identification is a preset value, executing the step C: creating a new local contact item based on the extracted cloud terminal contact item, allocating a new local identification, associating the allocated local identification with a default cloud terminal identification, and setting a modification mark associated with the allocated local identification to a preset value.
7. The contact synchronization method of claim 6, wherein the step of merging the received cloud contact entry to be synchronized with a local contact entry to obtain a local contact entry to be synchronized further comprises:
step D, when the obtained modification mark associated with the local identification is not a preset value, replacing the obtained local contact item associated with the local identification with the extracted cloud contact item; if the currently extracted cloud contact item is the last item, switching to the step E, and otherwise, switching to the step A;
and step E, calling a contact merging function to merge the local contact items marked as the preset values by the association modification, and taking the local contact items obtained after merging and the local contact items which are not subjected to the merging operation as the local contact items to be synchronized.
8. The contact synchronization method of claim 7, wherein after the step of sending the local contact entry to be synchronized to the server, further comprising:
and receiving and updating the mapping relation between the stored cloud end identification and the local identification based on the cloud end identification returned by the server, wherein the returned cloud end identification is returned by the server based on the received local contact item to be synchronized associated with the default cloud end identification.
9. The contact synchronization method according to any one of claims 6 to 8, wherein the step of sending a contact synchronization request to the server is preceded by the step of:
sending authentication information to the server so that the server can carry out authentication operation based on the received authentication information, and returning a synchronous permission configured with a survival time when the authentication is passed;
the step of sending the contact synchronization request to the server comprises:
and sending a contact person synchronization request carrying the synchronization permission to the server so that the server can respond to the contact person synchronization request within the survival time of the synchronization permission.
10. The contact synchronization method according to any one of claims 6 to 8, wherein the step of sending the local contact entry to be synchronized to the server comprises:
and calling a JSON data protocol to package the local contact item to be synchronized, and sending the obtained packaged data to the server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610188845.7A CN105872124B (en) | 2016-03-29 | 2016-03-29 | Contact person synchronization device and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610188845.7A CN105872124B (en) | 2016-03-29 | 2016-03-29 | Contact person synchronization device and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105872124A CN105872124A (en) | 2016-08-17 |
| CN105872124B true CN105872124B (en) | 2020-01-10 |
Family
ID=56626718
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610188845.7A Active CN105872124B (en) | 2016-03-29 | 2016-03-29 | Contact person synchronization device and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105872124B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106850738A (en) * | 2016-12-15 | 2017-06-13 | 努比亚技术有限公司 | A kind of contact person's sychronisation and method |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102413223A (en) * | 2010-09-24 | 2012-04-11 | 深圳富泰宏精密工业有限公司 | Contact item merging and dividing method and system |
| CN102905002A (en) * | 2012-10-31 | 2013-01-30 | 广东欧珀移动通信有限公司 | Method and system for automatically combining contact items |
| CN101902476B (en) * | 2010-07-27 | 2013-04-24 | 浙江大学 | Method for authenticating identity of mobile peer-to-peer user |
| CN104169861A (en) * | 2014-02-26 | 2014-11-26 | 华为技术有限公司 | Method and apparatus for combining contact information, and terminal |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103685406B (en) * | 2012-09-19 | 2018-09-25 | 腾讯科技（深圳）有限公司 | The method and device of mobile terminal contact person backup |
-
2016
- 2016-03-29 CN CN201610188845.7A patent/CN105872124B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101902476B (en) * | 2010-07-27 | 2013-04-24 | 浙江大学 | Method for authenticating identity of mobile peer-to-peer user |
| CN102413223A (en) * | 2010-09-24 | 2012-04-11 | 深圳富泰宏精密工业有限公司 | Contact item merging and dividing method and system |
| CN102905002A (en) * | 2012-10-31 | 2013-01-30 | 广东欧珀移动通信有限公司 | Method and system for automatically combining contact items |
| CN104169861A (en) * | 2014-02-26 | 2014-11-26 | 华为技术有限公司 | Method and apparatus for combining contact information, and terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105872124A (en) | 2016-08-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10187855B2 (en) | Message processing method and apparatus | |
| US8660033B2 (en) | Apparatus and method for providing service in service zone | |
| US8726405B1 (en) | Techniques for providing security using a mobile wireless communications device having data loss prevention circuitry | |
| KR102150624B1 (en) | Method and apparatus for notifying smishing | |
| CN105722059B (en) | Mobile terminal and communication method of dual-modem system | |
| US20150311934A1 (en) | Communication method, electronic device, and storage medium | |
| US10009838B2 (en) | Access point connection method and electronic device thereof | |
| CN106507422B (en) | Mobile terminal and network switching method | |
| CN109600740B (en) | File downloading method and device and computer readable storage medium | |
| EP3553663A1 (en) | Message reminding method for terminal, and terminal | |
| CN109219004B (en) | Short message unsubscribing method and device, mobile terminal and readable storage medium | |
| CN106131285B (en) | Call method and terminal | |
| CN106547439B (en) | Method and device for processing message | |
| CN107862217B (en) | Position information acquisition method, mobile terminal and computer storage medium | |
| CN114629932B (en) | Cooperative method between electronic devices, electronic device and storage medium | |
| CN107172605B (en) | Emergency call method, mobile terminal and computer readable storage medium | |
| CN107682541B (en) | Audio control method for screen projection, mobile terminal and storage medium | |
| CN108012270B (en) | Information processing method, equipment and computer readable storage medium | |
| CN112464208B (en) | File access method, mobile terminal and computer readable storage medium | |
| US20160057593A1 (en) | Method for controlling call forwarding information and electronic device thereof | |
| CN105872124B (en) | Contact person synchronization device and method | |
| CN109711198B (en) | Application management method, mobile terminal and storage medium | |
| CN109104722B (en) | Terminal access method, device and computer readable storage medium | |
| CN108566476B (en) | Information processing method, terminal and computer readable storage medium | |
| CN108040330B (en) | WiFi directional transmission method, mobile terminal and readable 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: 20191202 Address after: A601-b610, No.15, Qianjin Second Road, Liutang community, Xixiang street, Bao'an District, Shenzhen City, Guangdong Province Applicant after: Shenzhen Mobile Power Technology Co.,Ltd. Address before: 518057 Guangdong Province, Shenzhen high tech Zone of Nanshan District City, No. 9018 North Central Avenue's innovation building A, 6-8 layer, 10-11 layer, B layer, C District 6-10 District 6 floor Applicant before: NUBIA TECHNOLOGY Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: Contact synchronization device and method Effective date of registration: 20231221 Granted publication date: 20200110 Pledgee: Shenzhen Rural Commercial Bank Co.,Ltd. Gongming Sub branch Pledgor: Shenzhen Mobile Power Technology Co.,Ltd. Registration number: Y2023980073387 |
|
| PE01 | Entry into force of the registration of the contract for pledge of patent right |