WO2015106710A1 - Contact information processing method, apparatus, and system - Google Patents

Contact information processing method, apparatus, and system Download PDF

Info

Publication number
WO2015106710A1
WO2015106710A1 PCT/CN2015/070843 CN2015070843W WO2015106710A1 WO 2015106710 A1 WO2015106710 A1 WO 2015106710A1 CN 2015070843 W CN2015070843 W CN 2015070843W WO 2015106710 A1 WO2015106710 A1 WO 2015106710A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
cards
contact
contact information
merging
Prior art date
Application number
PCT/CN2015/070843
Other languages
French (fr)
Inventor
Weibing LIN
Original Assignee
Tencent Technology (Shenzhen) Company Limited
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Tencent Technology (Shenzhen) Company Limited filed Critical Tencent Technology (Shenzhen) Company Limited
Publication of WO2015106710A1 publication Critical patent/WO2015106710A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/42—Mailbox-related aspects, e.g. synchronisation of mailboxes

Definitions

  • the present disclosure relates to the field of mobile Internet technologies, and in particular, to a contact information processing method, apparatus, and system.
  • a function of synchronizing contact information is set in a mobile terminal or a PC terminal, and contact information in different mobile terminals can be backed up to a server end, which ensures security of the contact information, and can implement sharing of the contact information.
  • merging processing needs to be performed at the server end for duplicate contacts, so as to reduce waste of storage space of the server end.
  • the two backed-up contact cards are detected for merging.
  • remark information of a same contact in different terminals may not be completely the same; as a result, duplicate contacts exist when contact information is merged.
  • contact cards A, B, C, D, and E all belong to a same contact, where all contact information of the contact card A is the same as that of the contact card B, the contact card A and the contact card C have different names, the contact card A and the contact card D have different email addresses, and the contact card A and the contact card E have different mobile numbers.
  • the existing merging solution it can only be detected that the contact card A and the contact card B are duplicate, and need to be merged.
  • the contact card A and the contact card C have different names, the contact card A and the contact card D have different email addresses, and the contact card A and the contact card E have different mobile numbers, duplicate contacts cannot be detected, and consequently merging processing is not performed. Therefore, accuracy of merging duplicate contacts is reduced, and storage space of the server end is wasted.
  • Embodiments of the present invention provide a contact information processing method, apparatus, and system, which aim to improve accuracy of merging duplicate contacts, and save storage space.
  • An embodiment of the present invention provides a contact information processing method, applied to a server having one or more processors and a memory for storing program modules to be executed by the one or more processors, including:
  • An embodiment of the present invention further provides a contact information processing apparatus, including:
  • a receiving module configured to receive a request, initiated by a user client, for merging cards of duplicate contacts
  • a pulling module configured to pull data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, each of the user contact cards including contact information;
  • a comparison module configured to compare the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result
  • a processing module configured to process the user contact cards according to the comparison result by using a preset policy.
  • An embodiment of the present invention further provides a contact information processing system, including: a user client and a server, where:
  • the user client is configured to initiate, to the server, a request for merging cards of duplicate contacts;
  • the server includes the apparatus described above.
  • the contact information processing method, apparatus, and system provided in the embodiments of the present invention, when a request, initiated by a user client, for merging cards of duplicate contacts is received, data of user contact cards corresponding to the user client is pulled according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information; the user contact cards are compared with each other based on the data of the user contact cards, to obtain a comparison result; and the user contact cards are processed according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, and storage space of a server, a terminal, or the like is saved.
  • FIG. 1 is an architectural diagram of a hardware environment involved in an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a first embodiment of a contact information processing method according to the present disclosure
  • FIG. 3 is a schematic flowchart of comparing user contact cards based on data of the user contact cards, and processing the user contact cards according to a comparison result by using a preset policy according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a second embodiment of a contact information processing method according to the present disclosure
  • FIG. 5 is a schematic flowchart of a third embodiment of a contact information processing method according to the present disclosure.
  • FIG. 6 is a schematic diagram of functional modules in a first embodiment of a contact information processing apparatus according to the present disclosure
  • FIG. 7 is a schematic diagram of functional modules in a second embodiment of a contact information processing apparatus according to the present disclosure.
  • FIG. 8 is a schematic diagram of functional modules in a third embodiment of a contact information processing apparatus according to the present disclosure.
  • FIG. 9 is a schematic structural diagram of a preferred embodiment of a contact information processing system according to the present disclosure.
  • FIG. 1 is an architectural diagram of a hardware environment involved in a method of an embodiment of the present invention.
  • the hardware running environment involved in the method of this embodiment of the present invention includes a user client, and a server or a local terminal (for example, a PC or a mobile terminal such as a mobile phone) .
  • a server 20 is used as an example in this embodiment, and the user client may be a terminal having a function of triggering merging of duplicate contacts, such as a PC terminal 10 or a mobile terminal 30, where the client and the server 20 may communicate through a wireless network or a wired network.
  • An application is installed in the client 10, which provides a user operation interface for a user to click an option of merging duplicate contacts.
  • the client requests, according to a user operation instruction, the server 20 to merge duplicate contacts; and when receiving a request, initiated by the user client, for merging cards of duplicate contacts, the server 20 pulls data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information; compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result; and processes the user contact cards according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, and storage space of a server end is saved.
  • a name which is globally unique, where mobile numbers of persons are not duplicate
  • an email address which is globally unique, where email addresses of persons are not duplicate
  • two contact cards are duplicate as long as one same field occurs in the contact cards.
  • a contact card is generalized into one in a standard vcard form; then, comparison is performed according to a comparison algorithm, where a comparison result is set to three cases as follows: identical, similar (where major fields are the same, and a major field may refer to a name, a mobile number, a home number, an office number, or the like) , and not identical; and then, corresponding processing is performed according to different comparison results.
  • a contact information processing method is provided in the following embodiments.
  • a first embodiment of the present invention provides a contact information processing method, including:
  • Step S101 Receive a request, initiated by a user client, for merging cards of duplicate contacts.
  • the method of this embodiment may be executed by a server, or a local terminal, for example, a local computer or a mobile terminal such as a mobile phone; and a server is used as an example in this embodiment, where the server has one or more processors and a memory for storing program modules to be executed by the one or more processors.
  • the user client may be a terminal having a function of triggering merging of duplicate contacts, such as a PC terminal or a mobile terminal, where an option on which a user performs a click operation to merge duplicate contacts is provided in an interface of the terminal. For example, a user may click, at an entry of a mobile phone end or a PC web end, an option for merging duplicate contacts; and the client requests, according to a user operation instruction, the server to merge cards of duplicate contacts.
  • the request for merging cards of duplicate contacts may carry ID information of a user, and the like, and the request may be sent to the server end in an http manner.
  • a contact card records, in one or more fields, contact information of the user, for example, the name, a mobile number, a home number, an office number, and the like of a contact.
  • Step S102 Pull data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information.
  • the server pulls, from a background, the data of the user contact cards corresponding to the user.
  • Step S103 Compare the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result, and process the user contact cards according to the comparison result by using a preset policy.
  • the server After obtaining the data of the user contact cards by pulling, the server analyzes the data of the user contact cards, and compares the user contact cards to find whether the user contact cards have same data, so as to perform corresponding deletion or merging processing or perform no processing according to a comparison result.
  • a name which is globally unique, where mobile numbers of persons are not duplicate
  • an email address which is globally unique, where email addresses of persons are not duplicate
  • two contact cards are duplicate as long as one same field occurs in the contact cards.
  • the contact cards are compared according to a comparison algorithm, where a comparison result is set to three cases as follows: contact information is identical, contact information is similar, and contact information is not identical; and then, corresponding processing is performed according to different comparison results.
  • the condition that contact information is identical refers to that all contact information in user contact cards is the same. That all contact information is the same may include a case in which all the contact information in the user contact cards is completely the same, and may also include a case in which all the contact information in the user contact cards is essentially the same. Determining that contact information is essentially the same may be set according to an actual situation, or contact information may be regarded the same according to a certain algorithm. For example, in user contact cards, a same phone number may have a local area code, and may also not have a local area code. For another example, for a Chinese phone number, one with the national code 86 added in the front and one without the national code 86 are essentially same phone numbers. For still another example, whether contact information has a profile picture or not does not affect determining whether it belongs to a same contact, and it may also be regarded that contact information is essentially a same piece of contact information.
  • the condition that contact information is similar refers to that contact information in one or more fields set in user contact cards is the same.
  • major fields are the same, and a major field may refer to a name, a mobile number, a home number, an office number, or the like.
  • the condition that contact information is not identical refers to that all contact information in user contact cards is different, or contact information in major fields in user contact cards is different.
  • a specific processing process may be set as follows:
  • comparison result is identical, automated processing is performed on a group of contact cards whose comparison result is identical, that is, one user contact card in the contact card group is retained, and another same user contact card in the user contact card group is deleted. The user may not be prompted with this operation, and a processing result is subject to a time at which a contact card is backed up to the server most recently. If the comparison result is similar (where major fields are the same, and a major field may refer to, for example, a name, a mobile number, a home number, an office number, or the like. ) , the user is prompted with a group of contact cards whose comparison result is similar, so that the user manually performs merging as needed.
  • Content prompted to the user may include: the contact card group that meets the condition that contact information is similar, where information in each field of each contact card is displayed; and the user is prompted whether to perform merging processing on two or more contact cards in the contact card group.
  • Merging processing on the contact card group that meets the condition that contact information is similar may refer to combining information in each field in two or more contact cards to form a new contact card; and may also be selecting, by the user, one contact card in the contact card group as current information of a contact, and deleting another contact card in the contact card group that meets the condition that contact information is similar.
  • the user may determine, according to an actual situation, whether to perform corresponding merging processing on user contact cards that meet the condition that contact information is similar. If merging processing is needed, the user may manually select and merge fields or perform corresponding deletion processing on the client.
  • the server performs, according to an operation result of the user client, corresponding merging processing on the user contact card group that meets the condition that contact information is similar.
  • the comparison result may not be displayed to the user, that is, no processing may be performed; or corresponding execution result information is fed back to the user client, for example, information indicating that a merging operation is completed, or cards of duplicate contacts that need to be merged do not exist is fed back.
  • a server end when receiving a request, initiated by a user client, for merging cards of duplicate contacts, pulls data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information; compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result; and performs corresponding processing on the user contact cards according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, and storage space of the server end is saved.
  • the foregoing step S103 may include:
  • Step S1031 Compare the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result; and when the comparison result meets a set condition that contact information is identical, perform step S1032; when the comparison result meets a set condition that contact information is similar, perform step S1033; and when the comparison result meets a set condition that contact information is not identical, perform step S1035.
  • Step S1032 For a user contact card group that meets the condition that contact information is identical, retain one user contact card in the user contact card group, and delete another user contact card in the user contact card group.
  • Step S1033 Return, to the user client, a user contact card group that meets the condition that contact information is similar, so that the user client determines whether to perform merging processing on user contact cards that meet the condition that contact information is similar.
  • Step S1034 When the user requests performing merging processing on the user contact cards that meet the condition that contact information is similar, the server performs corresponding merging processing on the user contact card group that meets the condition that contact information is similar.
  • Step S1035 Perform no processing, or feed back corresponding execution result information to the user client.
  • the server first compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result, and determines whether the user contact cards meet the condition that contact information is identical.
  • a user contact card group that meets the condition that contact information is similar is returned to the user client.
  • the user may determine, according to an actual situation, whether to perform merging processing on user contact cards that meet the condition that contact information is similar. If merging processing is needed, the user may manually select and merge fields or perform corresponding deletion processing on the client.
  • the server performs, according to an operation result of the user client, corresponding merging processing on the user contact card group that meets the condition that contact information is similar.
  • same user contact cards are merged, and similar contact cards are grouped for a user to select and merge fields, so that cards of duplicate contacts of a user at a server end caused by various reasons are merged more intelligently, which solves the problem of cards of duplicate contacts of the user. Therefore, accuracy of merging duplicate contacts is improved, storage space of the server end is saved, and desirable experience is provided for the user.
  • a second embodiment of the present invention provides a contact information processing method. Based on the first embodiment shown in FIG. 2, after the foregoing step S102 of pulling data of user contact cards, the method further includes:
  • Step S104 Perform generalization processing on the data of the user contact cards.
  • a difference between this embodiment and the foregoing first embodiment lies in that in this embodiment, after obtaining the data of the user contact cards by pulling, the server further needs to perform generalization processing on the data of the user contact cards, so that comparability of the contact cards is improved, and the server conveniently compares different user contact cards.
  • Performing generalization processing on the data of the user contact cards may be: orchestrating fields in a user contact card according to a certain rule, for example, the user contact cards in Table 1 may be all orchestrated in a sequence of fields in a user contact card: a number, a name, a mobile number, and an email address.
  • the server conveniently compares different fields, and the server compares different user contact cards more efficiently.
  • a third embodiment of the present invention provides a contact information processing method. Based on the second embodiment shown in FIG. 4, after the foregoing step S101 of receiving, by a server, a request, initiated by a user client, for merging cards of duplicate contacts, the method further includes:
  • Step S105 Verify legality of the request for merging cards of duplicate contacts; and after the verification succeeds, perform step S102; and otherwise, perform step S106.
  • Step S106 Prompt the user client with information indicating a verification failure.
  • a difference between this embodiment and the second embodiment shown in FIG. 4 lies in that in this embodiment, after the server receives the request, initiated by the user client, for merging cards of duplicate contacts, the server further needs to verify legality of the identity of the user to improve security of an operation of merging contact cards.
  • the server verifies legality of the request for merging cards of duplicate contacts, for example, a user ID carried in the user request is matched; and if the matching succeeds, the verification succeeds, which indicates that the user identity is legal; and if the matching fails, the verification does not succeed, which indicates that the user identity is illegal.
  • the server pulls the data of the user contact cards according to the request for merging cards of duplicate contacts; compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result; and performs merging processing on the user contact cards according to the comparison result by using a preset policy.
  • the user client is prompted with the information indicating a verification failure.
  • a server end verifies legality of the request for merging cards of duplicate contacts; after the verification succeeds, pulls data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information; performs generalization processing on the data of the user contact cards; compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result; and performs corresponding processing on the user contact cards according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, storage space of the server end is saved, and security and efficiency of an operation of merging contact cards are improved.
  • a first embodiment of the present invention provides a contact information processing apparatus, including: a receiving module 201, a pulling module 202, a comparison module 203, and a processing module 204, where
  • the receiving module 201 is configured to receive a request, initiated by a user client, for merging cards of duplicate contacts;
  • the pulling module 202 is configured to pull data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information;
  • the comparison module 203 is configured to compare the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result
  • the processing module 204 is configured to process the user contact cards according to the comparison result by using a preset policy.
  • the apparatus of this embodiment may be disposed in a server, and may also be disposed in a local terminal, for example, a local computer or a mobile terminal such as a mobile phone; and a server is used as an example in this embodiment, where the server has one or more processors and a memory for storing program modules to be executed by the one or more processors, and the program modules include instructions for executing the foregoing method.
  • the user client may be a terminal having a function of triggering merging of duplicate contacts, such as a PC terminal or a mobile terminal, where an option on which a user performs a click operation to merge duplicate contacts is provided in an interface of the terminal. For example, a user may click, at an entry of a mobile phone end or a PC web end, an option for merging duplicate contacts; and the client requests, according to a user operation instruction, the server to merge cards of duplicate contacts.
  • the request for merging cards of duplicate contacts may carry ID information of a user, and the like, and the request may be sent to the server end in an http manner.
  • a contact card records, in one or more fields, contact information of the user, for example, the name, a mobile number, a home number, an office number, and the like of a contact.
  • the server pulls, from a background, the data of the user contact cards corresponding to the user.
  • the server After obtaining the data of the user contact cards by pulling, the server analyzes the data of the user contact cards, and compares the user contact cards to find whether the user contact cards have same data, so as to perform corresponding deletion or merging processing or perform no processing according to a comparison result.
  • a name which is globally unique, where mobile numbers of persons are not duplicate
  • an email address which is globally unique, where email addresses of persons are not duplicate
  • two contact cards are duplicate as long as one same field occurs in the contact cards.
  • the contact cards are compared according to a comparison algorithm, where a comparison result is set to three cases as follows: contact information is identical, contact information is similar, and contact information is not identical; and then, corresponding processing is performed according to different comparison results.
  • the condition that contact information is identical refers to that all contact information in user contact cards is the same. That all contact information is the same may include a case in which all the contact information in the user contact cards is completely the same, and may also include a case in which all the contact information in the user contact cards is essentially the same. Determining that contact information is essentially the same may be set according to an actual situation, or contact information may be regarded the same according to a certain algorithm. For example, in user contact cards, a same phone number may have a local area code, and may also not have a local area code. For another example, for a Chinese phone number, one with the national code 86 added in the front and one without the national code 86 are essentially same phone numbers. For still another example, whether contact information has a profile picture or not does not affect determining whether it belongs to a same contact, and it may also be regarded that contact information is essentially a same piece of contact information.
  • the condition that contact information is similar refers to that contact information in one or more fields set in user contact cards is the same.
  • major fields are the same, and a major field may refer to a name, a mobile number, a home number, an office number, or the like.
  • the condition that contact information is completely not identical refers to that all contact information in user contact cards is different, or contact information in major fields in user contact cards is different.
  • a specific processing process may be set as follows:
  • the comparison result is similar (where major fields are the same, and a major field may refer to, for example, a name, a mobile number, a home number, an office number, or the like. )
  • the user is prompted with a group of contact cards whose comparison result is similar, so that the user manually performs merging as needed.
  • Content prompted to the user may include: the contact card group that meets the condition that contact information is similar, where information in each field of each contact card is displayed; and the user is prompted whether to perform merging processing on two or more contact cards in the contact card group.
  • Merging processing on the contact card group that meets the condition that contact information is similar may refer to combining information in each field in two or more contact cards to form a new contact card; and may also be selecting, by the user, one contact card in the contact card group as current information of a contact, and deleting another contact card in the contact card group that meets the condition that contact information is similar.
  • the user may determine, according to an actual situation, whether to perform corresponding merging processing on user contact cards that meet the condition that contact information is similar. If merging processing is needed, the user may manually select and merge fields or perform corresponding deletion processing on the client.
  • the server performs, according to an operation result of the user client, corresponding merging processing on the user contact card group that meets the condition that contact information is similar.
  • the comparison result may not be displayed to the user, that is, no processing may be performed; or corresponding execution result information is fed back to the user client, for example, information indicating that a merging operation is completed, or cards of duplicate contacts that need to be merged do not exist is fed back.
  • a server end when receiving a request, initiated by a user client, for merging cards of duplicate contacts, pulls data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information; compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result; and performs corresponding processing on the user contact cards according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, and storage space of the server end is saved.
  • the processing module 204 is further configured to: when the comparison result meets a set condition that contact information is identical, perform corresponding processing on a user contact card group that meets the condition that contact information is identical, for example, retain one user contact card in the contact card group, and delete another user contact card in the user contact card group.
  • the processing module 204 is further configured to: when the comparison result meets a set condition that contact information is similar, return, to the user client, a user contact card group that meets the condition that contact information is similar, so that the user client determines whether to perform merging processing on user contact cards that meet the condition that contact information is similar; and when the user requests performing merging processing on the user contact cards that meet the condition that contact information is similar, perform corresponding merging processing on the user contact card group that meets the condition that contact information is similar.
  • the processing module 204 is further configured to: when the comparison result meets a set condition that contact information is not identical, perform no processing, or feed back corresponding execution result information to the user client.
  • same user contact cards are merged, and similar contact cards are grouped for a user to select and merge fields, so that cards of duplicate contacts of a user at a server end caused by various reasons are merged more intelligently, which solves the problem of cards of duplicate contacts of the user. Therefore, accuracy of merging duplicate contacts is improved, storage space of the server end is saved, and desirable experience is provided for the user.
  • a second embodiment of the present invention provides a contact information processing apparatus, based on the first embodiment shown in FIG. 6, further including:
  • a generalization processing module 205 configured to perform generalization processing on the data of the user contact cards.
  • a difference between this embodiment and the foregoing first embodiment lies in that in this embodiment, after obtaining the data of the user contact cards by pulling, the server further needs to perform generalization processing on the data of the user contact cards, so that comparability of the contact cards is improved, and the server conveniently compares different user contact cards.
  • Performing generalization processing on the data of the user contact cards may be: orchestrating fields in a user contact card according to a certain rule, for example, the user contact cards in Table 1 may be all orchestrated in a sequence of fields in a user contact card: a number, a name, a mobile number, and an email address.
  • the server conveniently compares different fields, and the server compares different user contact cards more efficiently.
  • a third embodiment of the present invention provides a contact information processing apparatus, based on the second embodiment shown in FIG. 7, further including:
  • a verification module 206 configured to verify legality of the request for merging cards of duplicate contacts, so that after the verification succeeds, the pulling module pulls the data of the user contact cards according to the request for merging cards of duplicate contacts.
  • a difference between this embodiment and the second embodiment shown in FIG. 7 lies in that in this embodiment, after the server receives the request, initiated by the user client, for merging cards of duplicate contacts, the server further needs to verify legality of the identity of the user to improve security of an operation of merging contact cards.
  • the server verifies legality of the request for merging cards of duplicate contacts, for example, a user ID carried in the user request is matched; and if the matching succeeds, the verification succeeds, which indicates that the user identity is legal; and if the matching fails, the verification does not succeed, which indicates that the user identity is illegal.
  • the server pulls the data of the user contact cards according to the request for merging cards of duplicate contacts; compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result; and performs merging processing on the user contact cards according to the comparison result by using a preset policy.
  • the user client is prompted with the information indicating a verification failure.
  • a server end verifies legality of the request for merging cards of duplicate contacts; after the verification succeeds, pulls data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information; performs generalization processing on the data of the user contact cards; compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result; and performs merging processing on the user contact cards according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, storage space of the server end is saved, and security and efficiency of an operation of merging contact cards are improved.
  • a preferred embodiment of the present invention provides a contact information processing system, including: a user client 301 and a server 302, where:
  • the user client 301 is configured to initiate, to the server 302, a request for merging cards of duplicate contacts;
  • the server 302 may include the apparatus described in the foregoing embodiments.
  • the user client 301 is further configured to: when a comparison result meets a set condition that contact information is similar, receive a user contact card group that is returned by the server 302 and meets the condition that contact information is similar; determine whether to perform merging processing on user contact cards that meet the condition that contact information is similar; and if yes, request the server 302 to perform merging processing on the user contact cards that meet the condition that contact information is similar.
  • the user client 301 may be a terminal having a function of triggering merging of duplicate contacts, such as a PC terminal or a mobile terminal, where an option on which a user performs a click operation to merge duplicate contacts is provided in an interface of the terminal. For example, a user may click, at an entry of a mobile phone end or a PC web end, an option for merging duplicate contacts; and the client requests, according to a user operation instruction, the server 302 to merge cards of duplicate contacts.
  • the request for merging cards of duplicate contacts may carry ID information of a user, and the like, and the request may be sent to the server 302 in an http manner.
  • a contact card records, in one or more fields, contact information of the user, for example, the name, a mobile number, a home number, an office number, and the like of a contact.
  • the server 302 pulls, from a background, data of user contact cards corresponding to the user.
  • the server 302 After obtaining the data of the user contact cards by pulling, the server 302 analyzes the data of the user contact cards, and compares the user contact cards to find whether the user contact cards have same data, so as to perform corresponding merging processing or perform no processing according to a comparison result.
  • a name which is globally unique, where mobile numbers of persons are not duplicate
  • an email address which is globally unique, where email addresses of persons are not duplicate
  • two contact cards are duplicate as long as one same field occurs in the contact cards.
  • the contact cards are compared according to a comparison algorithm, where a comparison result is set to three cases as follows: contact information is completely identical, contact information is similar, and contact information is not identical; and then, corresponding processing is performed according to different comparison results.
  • the condition that contact information is identical refers to that all contact information in user contact cards is the same. That all contact information is the same may include a case in which all the contact information in the user contact cards is completely the same, and may also include a case in which all the contact information in the user contact cards is essentially the same. Determining that contact information is essentially the same may be set according to an actual situation, or contact information may be regarded the same according to a certain algorithm. For example, in user contact cards, a same phone number may have a local area code, and may also not have a local area code. For another example, for a Chinese phone number, one with the national code 86 added in the front and one without the national code 86 are essentially same phone numbers. For still another example, whether contact information has a profile picture or not does not affect determining whether it belongs to a same contact, and it may also be regarded that contact information is essentially a same piece of contact information.
  • the condition that contact information is similar refers to that contact information in one or more fields set in user contact cards is the same.
  • major fields are the same, and a major field may refer to a name, a mobile number, a home number, an office number, or the like.
  • the condition that contact information is not identical refers to that all contact information in user contact cards is different, or contact information in major fields in user contact cards is different.
  • a specific processing process may be set as follows:
  • the comparison result is similar (where major fields are the same, and a major field may refer to, for example, a name, a mobile number, a home number, an office number, or the like. )
  • the user is prompted with a group of contact cards whose comparison result is similar, so that the user manually performs merging as needed.
  • Content prompted to the user may include: the contact card group that meets the condition that contact information is similar, where information in each field of each contact card is displayed; and the user is prompted whether to perform merging processing on two or more contact cards in the contact card group.
  • Merging processing on the contact card group that meets the condition that contact information is similar may refer to combining information in each field in two or more contact cards to form a new contact card; and may also be selecting, by the user, one contact card in the contact card group as current information of a contact, and deleting another contact card in the contact card group that meets the condition that contact information is similar.
  • the user may determine, according to an actual situation, whether to perform corresponding merging processing on user contact cards that meet the condition that contact information is similar. If merging processing is needed, the user may manually select and merge fields or perform corresponding deletion processing on the client.
  • the server performs, according to an operation result of the user client, corresponding merging processing on the user contact card group that meets the condition that contact information is similar.
  • the comparison result may not be displayed to the user, that is, no processing may be performed; or corresponding execution result information is fed back to the user client 301, for example, information indicating that a merging operation is completed, or cards of duplicate contacts that need to be merged do not exist is fed back.
  • a server 302 when receiving a request, initiated by a user client 301, for merging cards of duplicate contacts, pulls data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information; compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result; and performs corresponding processing on the user contact cards according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, and storage space of the server 302 is saved.
  • completely same user contact cards are merged, and similar contact cards are grouped for a user to select and merge fields, so that cards of duplicate contacts of a user at a server end 302 caused by various reasons are merged more intelligently, which solves the problem of cards of duplicate contacts of the user, and provides desirable experience for the user.
  • the server 302 further needs to perform generalization processing on the data of the user contact cards, so that comparability of the contact cards is improved, and the server 302 conveniently compares different user contact cards.
  • Performing generalization processing on the data of the user contact cards may be: orchestrating fields in a user contact card according to a certain rule, for example, the user contact cards in Table 1 may be all orchestrated in a sequence of fields in a user contact card: a number, a name, a mobile number, and an email address.
  • the server 302 conveniently compares different fields, and the server 302 compares different user contact cards more efficiently.
  • the server 302 After the server 302 receives the request, initiated by the user client 301, for merging cards of duplicate contacts, the server 302 further needs to verify legality of the identity of the user to improve security of an operation of merging contact cards.
  • the server 302 verifies legality of the request for merging cards of duplicate contacts, for example, a user ID carried in the user request is matched; and if the matching succeeds, the verification succeeds, which indicates that the user identity is legal; and if the matching fails, the verification does not succeed, which indicates that the user identity is illegal.
  • the server 302 pulls the data of the user contact cards according to the request for merging cards of duplicate contacts; compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result; and performs merging processing on the user contact cards according to the comparison result by using a preset policy.
  • the user client 301 is prompted with the information indicating a verification failure.
  • a server 302 verifies legality of the request for merging cards of duplicate contacts; after the verification succeeds, pulls data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information; performs generalization processing on the data of the user contact cards; compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result; and performs corresponding processing on the user contact cards according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, storage space of the server 302 is saved, and security and efficiency of an operation of merging contact cards are improved.
  • the terms “include” , “comprise” , or any variation thereof are intended to cover a non-exclusive inclusion. Therefore, in the context of a process, method, object, or device that includes a series of elements, the process, method, object, or device not only includes such elements, but also includes other elements not specified expressly, or may include inherent elements of the process, method, object, or device. Unless otherwise specified, an element limited by “include a/an. . . " does not exclude other same elements existing in the process, the method, the object, or the device that includes the element.
  • the method of the foregoing embodiments may be implemented by software plus a necessary universal hardware platform, and certainly may also be implemented by hardware, but in many cases, the former implementation manner is preferred.
  • the technical solutions of the present disclosure essentially or the part contributing to the prior art may be implemented in a form of a software product.
  • the computer software product is stored in a storage medium (for example, a ROM/RAM, a magnetic disk, or an optical disc) and includes several instructions for instructing a terminal device (which may be a mobile phone, a computer, a server, a network device, or the like) to perform the methods described in the embodiments of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The present disclosure relates to contact information processing method, apparatus, and system. The method includes: receiving a request, initiated by a user client, for merging cards of duplicate contacts; pulling data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information; comparing the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result; and processing the user contact cards according to the comparison result by using a preset policy. The present disclosure improves accuracy of merging duplicate contacts, and saves storage space.

Description

CONTACT INFORMATION PROCESSING METHOD, APPARATUS, AND SYSTEM
FIELD OF THE DISCLOSURE
The present disclosure relates to the field of mobile Internet technologies, and in particular, to a contact information processing method, apparatus, and system.
BACKGROUND OF THE DISCLOSURE
Currently, a function of synchronizing contact information is set in a mobile terminal or a PC terminal, and contact information in different mobile terminals can be backed up to a server end, which ensures security of the contact information, and can implement sharing of the contact information.
During synchronization of the contact information, merging processing needs to be performed at the server end for duplicate contacts, so as to reduce waste of storage space of the server end. However, in an existing solution for synchronizing contacts, during backup of the contact information of the different mobile terminals to the server end, only when two backed-up contact cards include completely the same contact information, the two backed-up contact cards are detected for merging. However, a possible case is that remark information of a same contact in different terminals may not be completely the same； as a result, duplicate contacts exist when contact information is merged.
As shown in FIG. 1, contact cards A, B, C, D, and E all belong to a same contact, where all contact information of the contact card A is the same as that of the contact card B, the contact card A and the contact card C have different names, the contact card A and the contact card D have different email addresses, and the contact card A and the contact card E have different mobile numbers. If the existing merging solution is used, it can only be detected that the contact card A and the contact card B are duplicate, and need to be merged. However, because the contact card A and the contact card C have different names, the contact card A and the contact card D have different email addresses, and the contact card A and the contact card E have different mobile numbers, duplicate contacts cannot be detected, and consequently merging processing is not performed. Therefore, accuracy of merging duplicate contacts is reduced, and storage space of the server end is wasted.
Contact card Name Mobile number Email address
A Xiaoming 12345678901 1234@qq. com
B Xiaoming 12345678901 1234@qq. com
C Xiaobai 12345678901 1234@qq. com
D Xiaoming 12345678901 123@qq. com
E Xiaoming 12345678902 1234@qq. com
Table 1 Information of contact cards
SUMMARY
Embodiments of the present invention provide a contact information processing method, apparatus, and system, which aim to improve accuracy of merging duplicate contacts, and save storage space.
An embodiment of the present invention provides a contact information processing method, applied to a server having one or more processors and a memory for storing program modules to be executed by the one or more processors, including:
receiving a request, initiated by a user client, for merging cards of duplicate contacts；
pulling data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, each of the user contact cards including contact information；
comparing the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and
processing the user contact cards according to the comparison result by using a preset policy.
An embodiment of the present invention further provides a contact information processing apparatus, including:
a receiving module, configured to receive a request, initiated by a user client, for merging cards of duplicate contacts；
a pulling module, configured to pull data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, each of the user contact cards including contact information；
a comparison module, configured to compare the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and
a processing module, configured to process the user contact cards according to the comparison result by using a preset policy.
An embodiment of the present invention further provides a contact information processing system, including: a user client and a server, where:
the user client is configured to initiate, to the server, a request for merging cards of duplicate contacts； and
the server includes the apparatus described above.
In the contact information processing method, apparatus, and system provided in the embodiments of the present invention, when a request, initiated by a user client, for merging cards of duplicate contacts is received, data of user contact cards corresponding to the user client is pulled according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information； the user contact cards are compared with each other based on the data of the user contact cards, to obtain a comparison result； and the user contact cards are processed according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, and storage space of a server, a terminal, or the like is saved.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is an architectural diagram of a hardware environment involved in an embodiment of the present invention；
FIG. 2 is a schematic flowchart of a first embodiment of a contact information processing method according to the present disclosure；
FIG. 3 is a schematic flowchart of comparing user contact cards based on data of the user contact cards, and processing the user contact cards according to a comparison result by using a preset policy according to an embodiment of the present invention；
FIG. 4 is a schematic flowchart of a second embodiment of a contact information processing method according to the present disclosure；
FIG. 5 is a schematic flowchart of a third embodiment of a contact information processing method according to the present disclosure；
FIG. 6 is a schematic diagram of functional modules in a first embodiment of a contact information processing apparatus according to the present disclosure；
FIG. 7 is a schematic diagram of functional modules in a second embodiment of a contact information processing apparatus according to the present disclosure；
FIG. 8 is a schematic diagram of functional modules in a third embodiment of a contact information processing apparatus according to the present disclosure； and
FIG. 9 is a schematic structural diagram of a preferred embodiment of a contact information processing system according to the present disclosure.
To make the technical solutions of the present disclosure more comprehensible, a detailed description is further provided below with reference to the accompanying drawings.
DESCRIPTION OF EMBODIMENTS
It should be understood that, the specific embodiments described herein are merely used to explain the present disclosure, but not intended to limit the present disclosure.
As shown in FIG. 1, FIG. 1 is an architectural diagram of a hardware environment involved in a method of an embodiment of the present invention. The hardware running environment involved in the method of this embodiment of the present invention includes a user client, and a server or a local terminal (for example, a PC or a mobile terminal such as a mobile phone) . A server 20 is used as an example in this embodiment, and the user client may be a terminal having a function of triggering merging of duplicate contacts, such as a PC terminal 10 or a mobile terminal 30, where the client and the server 20 may communicate through a wireless network or a wired network. An application is installed in the client 10, which provides a user operation interface for a user to click an option of merging duplicate contacts. The client requests, according to a user operation instruction, the server 20 to merge duplicate contacts； and when receiving a request, initiated by the user client, for merging cards of duplicate contacts, the server 20 pulls data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information； compares the user contact cards with each other based on the data of the user contact cards, to obtain a  comparison result； and processes the user contact cards according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, and storage space of a server end is saved.
Because a name, a mobile number (which is globally unique, where mobile numbers of persons are not duplicate) , an email address (which is globally unique, where email addresses of persons are not duplicate) , and the like are unique to some extent, it basically can be determined that two contact cards are duplicate as long as one same field occurs in the contact cards. Based on these considerations, in the solutions in the embodiments of the present invention, a contact card is generalized into one in a standard vcard form； then, comparison is performed according to a comparison algorithm, where a comparison result is set to three cases as follows: identical, similar (where major fields are the same, and a major field may refer to a name, a mobile number, a home number, an office number, or the like) , and not identical； and then, corresponding processing is performed according to different comparison results.
Specifically, based on the foregoing hardware architecture shown in FIG. 1, a contact information processing method is provided in the following embodiments.
As shown in FIG. 2, a first embodiment of the present invention provides a contact information processing method, including:
Step S101: Receive a request, initiated by a user client, for merging cards of duplicate contacts.
The method of this embodiment may be executed by a server, or a local terminal, for example, a local computer or a mobile terminal such as a mobile phone； and a server is used as an example in this embodiment, where the server has one or more processors and a memory for storing program modules to be executed by the one or more processors.
The user client may be a terminal having a function of triggering merging of duplicate contacts, such as a PC terminal or a mobile terminal, where an option on which a user performs a click operation to merge duplicate contacts is provided in an interface of the terminal. For example, a user may click, at an entry of a mobile phone end or a PC web end, an option for merging duplicate contacts； and the client requests, according to a user operation instruction, the server to merge cards of duplicate contacts.
The request for merging cards of duplicate contacts may carry ID information of a user, and the like, and the request may be sent to the server end in an http manner.
A contact card records, in one or more fields, contact information of the user, for example, the name, a mobile number, a home number, an office number, and the like of a contact.
Step S102: Pull data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information.
After receiving the request, initiated by the client, for merging cards of duplicate contacts, the server pulls, from a background, the data of the user contact cards corresponding to the user.
Step S103: Compare the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result, and process the user contact cards according to the comparison result by using a preset policy.
After obtaining the data of the user contact cards by pulling, the server analyzes the data of the user contact cards, and compares the user contact cards to find whether the user contact cards have same data, so as to perform corresponding deletion or merging processing or perform no processing according to a comparison result.
In this embodiment, the following is considered: Because a name, a mobile number (which is globally unique, where mobile numbers of persons are not duplicate) , an email address (which is globally unique, where email addresses of persons are not duplicate) , and the like are unique to some extent, it basically can be determined that two contact cards are duplicate as long as one same field occurs in the contact cards.
Therefore, based on the foregoing considerations, in this embodiment, the contact cards are compared according to a comparison algorithm, where a comparison result is set to three cases as follows: contact information is identical, contact information is similar, and contact information is not identical； and then, corresponding processing is performed according to different comparison results.
The condition that contact information is identical refers to that all contact information in user contact cards is the same. That all contact information is the same may include a case in which all the contact information in the user contact cards is completely the same, and may also include a case in which all the contact information in the user contact cards is essentially the same. Determining that contact information is essentially the same may be set according to an actual situation, or contact information may be regarded the same according to a certain algorithm. For example, in user contact cards, a same phone number may have a local area code, and may also  not have a local area code. For another example, for a Chinese phone number, one with the national code 86 added in the front and one without the national code 86 are essentially same phone numbers. For still another example, whether contact information has a profile picture or not does not affect determining whether it belongs to a same contact, and it may also be regarded that contact information is essentially a same piece of contact information.
The condition that contact information is similar refers to that contact information in one or more fields set in user contact cards is the same. For example, major fields are the same, and a major field may refer to a name, a mobile number, a home number, an office number, or the like.
The condition that contact information is not identical refers to that all contact information in user contact cards is different, or contact information in major fields in user contact cards is different.
A specific processing process may be set as follows:
If the comparison result is identical, automated processing is performed on a group of contact cards whose comparison result is identical, that is, one user contact card in the contact card group is retained, and another same user contact card in the user contact card group is deleted. The user may not be prompted with this operation, and a processing result is subject to a time at which a contact card is backed up to the server most recently. If the comparison result is similar (where major fields are the same, and a major field may refer to, for example, a name, a mobile number, a home number, an office number, or the like. ) , the user is prompted with a group of contact cards whose comparison result is similar, so that the user manually performs merging as needed.
Content prompted to the user may include: the contact card group that meets the condition that contact information is similar, where information in each field of each contact card is displayed； and the user is prompted whether to perform merging processing on two or more contact cards in the contact card group.
Merging processing on the contact card group that meets the condition that contact information is similar may refer to combining information in each field in two or more contact cards to form a new contact card； and may also be selecting, by the user, one contact card in the contact card group as current information of a contact, and deleting another contact card in the contact card group that meets the condition that contact information is similar.
The user may determine, according to an actual situation, whether to perform corresponding merging processing on user contact cards that meet the condition that contact  information is similar. If merging processing is needed, the user may manually select and merge fields or perform corresponding deletion processing on the client. The server performs, according to an operation result of the user client, corresponding merging processing on the user contact card group that meets the condition that contact information is similar.
If the comparison result is not identical, the comparison result may not be displayed to the user, that is, no processing may be performed； or corresponding execution result information is fed back to the user client, for example, information indicating that a merging operation is completed, or cards of duplicate contacts that need to be merged do not exist is fed back.
In this embodiment, by using the foregoing solution, when receiving a request, initiated by a user client, for merging cards of duplicate contacts, a server end pulls data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information； compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and performs corresponding processing on the user contact cards according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, and storage space of the server end is saved.
To be more specific, as shown in FIG. 3, the foregoing step S103 may include:
Step S1031: Compare the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and when the comparison result meets a set condition that contact information is identical, perform step S1032； when the comparison result meets a set condition that contact information is similar, perform step S1033； and when the comparison result meets a set condition that contact information is not identical, perform step S1035.
Step S1032: For a user contact card group that meets the condition that contact information is identical, retain one user contact card in the user contact card group, and delete another user contact card in the user contact card group.
Step S1033: Return, to the user client, a user contact card group that meets the condition that contact information is similar, so that the user client determines whether to perform merging processing on user contact cards that meet the condition that contact information is similar.
Step S1034: When the user requests performing merging processing on the user contact cards that meet the condition that contact information is similar, the server performs  corresponding merging processing on the user contact card group that meets the condition that contact information is similar.
Step S1035: Perform no processing, or feed back corresponding execution result information to the user client.
Specifically, as an implementation manner, the server first compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result, and determines whether the user contact cards meet the condition that contact information is identical.
When the comparison result meets the set condition that contact information is identical, corresponding processing is performed on a user contact card group that meets the condition that contact information is identical, for example, one user contact card in the contact card group is retained, and another same user contact card in the user contact card group is deleted.
For user contact cards that do not meet the condition that contact information is identical, it is determined whether the user contact cards meet the condition that contact information is similar.
When the comparison result meets the set condition that contact information is similar, a user contact card group that meets the condition that contact information is similar is returned to the user client.
The user may determine, according to an actual situation, whether to perform merging processing on user contact cards that meet the condition that contact information is similar. If merging processing is needed, the user may manually select and merge fields or perform corresponding deletion processing on the client. The server performs, according to an operation result of the user client, corresponding merging processing on the user contact card group that meets the condition that contact information is similar.
For user contact cards that do not meet the condition that contact information is identical, if a result of comparison of the user contact cards meets the set condition that contact information is not identical, no processing may be performed； or corresponding execution result information is fed back to the user client.
Therefore, by using the foregoing solution, same user contact cards are merged, and similar contact cards are grouped for a user to select and merge fields, so that cards of duplicate contacts of a user at a server end caused by various reasons are merged more intelligently, which solves the problem of cards of duplicate contacts of the user. Therefore, accuracy of merging  duplicate contacts is improved, storage space of the server end is saved, and desirable experience is provided for the user.
As shown in FIG. 4, a second embodiment of the present invention provides a contact information processing method. Based on the first embodiment shown in FIG. 2, after the foregoing step S102 of pulling data of user contact cards, the method further includes:
Step S104: Perform generalization processing on the data of the user contact cards.
A difference between this embodiment and the foregoing first embodiment lies in that in this embodiment, after obtaining the data of the user contact cards by pulling, the server further needs to perform generalization processing on the data of the user contact cards, so that comparability of the contact cards is improved, and the server conveniently compares different user contact cards.
Performing generalization processing on the data of the user contact cards may be: orchestrating fields in a user contact card according to a certain rule, for example, the user contact cards in Table 1 may be all orchestrated in a sequence of fields in a user contact card: a number, a name, a mobile number, and an email address. In this way, the server conveniently compares different fields, and the server compares different user contact cards more efficiently.
As shown in FIG. 5, a third embodiment of the present invention provides a contact information processing method. Based on the second embodiment shown in FIG. 4, after the foregoing step S101 of receiving, by a server, a request, initiated by a user client, for merging cards of duplicate contacts, the method further includes:
Step S105: Verify legality of the request for merging cards of duplicate contacts； and after the verification succeeds, perform step S102； and otherwise, perform step S106.
Step S106: Prompt the user client with information indicating a verification failure.
A difference between this embodiment and the second embodiment shown in FIG. 4 lies in that in this embodiment, after the server receives the request, initiated by the user client, for merging cards of duplicate contacts, the server further needs to verify legality of the identity of the user to improve security of an operation of merging contact cards.
Specifically, after receiving the request, initiated by the user client, for merging cards of duplicate contacts, the server verifies legality of the request for merging cards of duplicate contacts, for example, a user ID carried in the user request is matched； and if the matching succeeds,  the verification succeeds, which indicates that the user identity is legal； and if the matching fails, the verification does not succeed, which indicates that the user identity is illegal.
After the verification succeeds, the server pulls the data of the user contact cards according to the request for merging cards of duplicate contacts； compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and performs merging processing on the user contact cards according to the comparison result by using a preset policy.
When the verification does not succeed, the user client is prompted with the information indicating a verification failure.
In this embodiment, by using the foregoing solution, when receiving a request, initiated by a user client, for merging cards of duplicate contacts, a server end verifies legality of the request for merging cards of duplicate contacts； after the verification succeeds, pulls data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information； performs generalization processing on the data of the user contact cards； compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and performs corresponding processing on the user contact cards according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, storage space of the server end is saved, and security and efficiency of an operation of merging contact cards are improved.
As shown in FIG. 6, a first embodiment of the present invention provides a contact information processing apparatus, including: a receiving module 201, a pulling module 202, a comparison module 203, and a processing module 204, where
the receiving module 201 is configured to receive a request, initiated by a user client, for merging cards of duplicate contacts；
the pulling module 202 is configured to pull data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information；
the comparison module 203 is configured to compare the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and
the processing module 204 is configured to process the user contact cards according to the comparison result by using a preset policy.
The apparatus of this embodiment may be disposed in a server, and may also be disposed in a local terminal, for example, a local computer or a mobile terminal such as a mobile phone； and a server is used as an example in this embodiment, where the server has one or more processors and a memory for storing program modules to be executed by the one or more processors, and the program modules include instructions for executing the foregoing method.
The user client may be a terminal having a function of triggering merging of duplicate contacts, such as a PC terminal or a mobile terminal, where an option on which a user performs a click operation to merge duplicate contacts is provided in an interface of the terminal. For example, a user may click, at an entry of a mobile phone end or a PC web end, an option for merging duplicate contacts； and the client requests, according to a user operation instruction, the server to merge cards of duplicate contacts.
The request for merging cards of duplicate contacts may carry ID information of a user, and the like, and the request may be sent to the server end in an http manner.
A contact card records, in one or more fields, contact information of the user, for example, the name, a mobile number, a home number, an office number, and the like of a contact.
After receiving the request, initiated by the client, for merging cards of duplicate contacts, the server pulls, from a background, the data of the user contact cards corresponding to the user.
After obtaining the data of the user contact cards by pulling, the server analyzes the data of the user contact cards, and compares the user contact cards to find whether the user contact cards have same data, so as to perform corresponding deletion or merging processing or perform no processing according to a comparison result.
In this embodiment, the following is considered: Because a name, a mobile number (which is globally unique, where mobile numbers of persons are not duplicate) , an email address (which is globally unique, where email addresses of persons are not duplicate) , and the like are unique to some extent, it basically can be determined that two contact cards are duplicate as long as one same field occurs in the contact cards.
Therefore, based on the foregoing considerations, in this embodiment, the contact cards are compared according to a comparison algorithm, where a comparison result is set to three  cases as follows: contact information is identical, contact information is similar, and contact information is not identical； and then, corresponding processing is performed according to different comparison results.
The condition that contact information is identical refers to that all contact information in user contact cards is the same. That all contact information is the same may include a case in which all the contact information in the user contact cards is completely the same, and may also include a case in which all the contact information in the user contact cards is essentially the same. Determining that contact information is essentially the same may be set according to an actual situation, or contact information may be regarded the same according to a certain algorithm. For example, in user contact cards, a same phone number may have a local area code, and may also not have a local area code. For another example, for a Chinese phone number, one with the national code 86 added in the front and one without the national code 86 are essentially same phone numbers. For still another example, whether contact information has a profile picture or not does not affect determining whether it belongs to a same contact, and it may also be regarded that contact information is essentially a same piece of contact information.
The condition that contact information is similar refers to that contact information in one or more fields set in user contact cards is the same. For example, major fields are the same, and a major field may refer to a name, a mobile number, a home number, an office number, or the like.
The condition that contact information is completely not identical refers to that all contact information in user contact cards is different, or contact information in major fields in user contact cards is different.
A specific processing process may be set as follows:
If the comparison result is identical, automated processing is performed on a group of contact cards whose comparison result is identical, that is, one user contact card in the contact card group is retained, and another same user contact card in the user contact card group is deleted. The user may not be prompted with this operation, and a processing result is subject to a time at which a contact card is backed up to the server most recently.
If the comparison result is similar (where major fields are the same, and a major field may refer to, for example, a name, a mobile number, a home number, an office number, or the like. ) , the user is prompted with a group of contact cards whose comparison result is similar, so that the user manually performs merging as needed.
Content prompted to the user may include: the contact card group that meets the condition that contact information is similar, where information in each field of each contact card is displayed； and the user is prompted whether to perform merging processing on two or more contact cards in the contact card group.
Merging processing on the contact card group that meets the condition that contact information is similar may refer to combining information in each field in two or more contact cards to form a new contact card； and may also be selecting, by the user, one contact card in the contact card group as current information of a contact, and deleting another contact card in the contact card group that meets the condition that contact information is similar.
The user may determine, according to an actual situation, whether to perform corresponding merging processing on user contact cards that meet the condition that contact information is similar. If merging processing is needed, the user may manually select and merge fields or perform corresponding deletion processing on the client. The server performs, according to an operation result of the user client, corresponding merging processing on the user contact card group that meets the condition that contact information is similar.
If the comparison result is not identical, the comparison result may not be displayed to the user, that is, no processing may be performed； or corresponding execution result information is fed back to the user client, for example, information indicating that a merging operation is completed, or cards of duplicate contacts that need to be merged do not exist is fed back.
In this embodiment, by using the foregoing solution, when receiving a request, initiated by a user client, for merging cards of duplicate contacts, a server end pulls data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information； compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and performs corresponding processing on the user contact cards according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, and storage space of the server end is saved.
To be more specific, the processing module 204 is further configured to: when the comparison result meets a set condition that contact information is identical, perform corresponding processing on a user contact card group that meets the condition that contact information is identical, for example, retain one user contact card in the contact card group, and delete another user contact card in the user contact card group.
The processing module 204 is further configured to: when the comparison result meets a set condition that contact information is similar, return, to the user client, a user contact card group that meets the condition that contact information is similar, so that the user client determines whether to perform merging processing on user contact cards that meet the condition that contact information is similar； and when the user requests performing merging processing on the user contact cards that meet the condition that contact information is similar, perform corresponding merging processing on the user contact card group that meets the condition that contact information is similar.
The processing module 204 is further configured to: when the comparison result meets a set condition that contact information is not identical, perform no processing, or feed back corresponding execution result information to the user client.
Therefore, by using the foregoing solution, same user contact cards are merged, and similar contact cards are grouped for a user to select and merge fields, so that cards of duplicate contacts of a user at a server end caused by various reasons are merged more intelligently, which solves the problem of cards of duplicate contacts of the user. Therefore, accuracy of merging duplicate contacts is improved, storage space of the server end is saved, and desirable experience is provided for the user.
As shown in FIG. 7, a second embodiment of the present invention provides a contact information processing apparatus, based on the first embodiment shown in FIG. 6, further including:
a generalization processing module 205, configured to perform generalization processing on the data of the user contact cards.
A difference between this embodiment and the foregoing first embodiment lies in that in this embodiment, after obtaining the data of the user contact cards by pulling, the server further needs to perform generalization processing on the data of the user contact cards, so that comparability of the contact cards is improved, and the server conveniently compares different user contact cards.
Performing generalization processing on the data of the user contact cards may be: orchestrating fields in a user contact card according to a certain rule, for example, the user contact cards in Table 1 may be all orchestrated in a sequence of fields in a user contact card: a number, a name, a mobile number, and an email address. In this way, the server conveniently compares different fields, and the server compares different user contact cards more efficiently.
As shown in FIG. 8, a third embodiment of the present invention provides a contact information processing apparatus, based on the second embodiment shown in FIG. 7, further including:
a verification module 206, configured to verify legality of the request for merging cards of duplicate contacts, so that after the verification succeeds, the pulling module pulls the data of the user contact cards according to the request for merging cards of duplicate contacts.
A difference between this embodiment and the second embodiment shown in FIG. 7 lies in that in this embodiment, after the server receives the request, initiated by the user client, for merging cards of duplicate contacts, the server further needs to verify legality of the identity of the user to improve security of an operation of merging contact cards.
Specifically, after receiving the request, initiated by the user client, for merging cards of duplicate contacts, the server verifies legality of the request for merging cards of duplicate contacts, for example, a user ID carried in the user request is matched； and if the matching succeeds, the verification succeeds, which indicates that the user identity is legal； and if the matching fails, the verification does not succeed, which indicates that the user identity is illegal.
After the verification succeeds, the server pulls the data of the user contact cards according to the request for merging cards of duplicate contacts； compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and performs merging processing on the user contact cards according to the comparison result by using a preset policy.
When the verification does not succeed, the user client is prompted with the information indicating a verification failure.
In this embodiment, by using the foregoing solution, when receiving a request, initiated by a user client, for merging cards of duplicate contacts, a server end verifies legality of the request for merging cards of duplicate contacts； after the verification succeeds, pulls data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information； performs generalization processing on the data of the user contact cards； compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and performs merging processing on the user contact cards according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, storage space of the server end is saved, and security and efficiency of an operation of merging contact cards are improved.
As shown in FIG. 9, a preferred embodiment of the present invention provides a contact information processing system, including: a user client 301 and a server 302, where:
the user client 301 is configured to initiate, to the server 302, a request for merging cards of duplicate contacts； and
the server 302 may include the apparatus described in the foregoing embodiments.
Preferably, the user client 301 is further configured to: when a comparison result meets a set condition that contact information is similar, receive a user contact card group that is returned by the server 302 and meets the condition that contact information is similar； determine whether to perform merging processing on user contact cards that meet the condition that contact information is similar； and if yes, request the server 302 to perform merging processing on the user contact cards that meet the condition that contact information is similar.
Specifically, reference may be made to FIG. 1, and in this embodiment, the user client 301 may be a terminal having a function of triggering merging of duplicate contacts, such as a PC terminal or a mobile terminal, where an option on which a user performs a click operation to merge duplicate contacts is provided in an interface of the terminal. For example, a user may click, at an entry of a mobile phone end or a PC web end, an option for merging duplicate contacts； and the client requests, according to a user operation instruction, the server 302 to merge cards of duplicate contacts.
The request for merging cards of duplicate contacts may carry ID information of a user, and the like, and the request may be sent to the server 302 in an http manner.
A contact card records, in one or more fields, contact information of the user, for example, the name, a mobile number, a home number, an office number, and the like of a contact.
After receiving the request, initiated by the client, for merging cards of duplicate contacts, the server 302 pulls, from a background, data of user contact cards corresponding to the user.
After obtaining the data of the user contact cards by pulling, the server 302 analyzes the data of the user contact cards, and compares the user contact cards to find whether the user contact cards have same data, so as to perform corresponding merging processing or perform no processing according to a comparison result.
In this embodiment, the following is considered: Because a name, a mobile number (which is globally unique, where mobile numbers of persons are not duplicate) , an email address  (which is globally unique, where email addresses of persons are not duplicate) , and the like are unique to some extent, it basically can be determined that two contact cards are duplicate as long as one same field occurs in the contact cards.
Therefore, based on the foregoing considerations, in this embodiment, the contact cards are compared according to a comparison algorithm, where a comparison result is set to three cases as follows: contact information is completely identical, contact information is similar, and contact information is not identical； and then, corresponding processing is performed according to different comparison results.
The condition that contact information is identical refers to that all contact information in user contact cards is the same. That all contact information is the same may include a case in which all the contact information in the user contact cards is completely the same, and may also include a case in which all the contact information in the user contact cards is essentially the same. Determining that contact information is essentially the same may be set according to an actual situation, or contact information may be regarded the same according to a certain algorithm. For example, in user contact cards, a same phone number may have a local area code, and may also not have a local area code. For another example, for a Chinese phone number, one with the national code 86 added in the front and one without the national code 86 are essentially same phone numbers. For still another example, whether contact information has a profile picture or not does not affect determining whether it belongs to a same contact, and it may also be regarded that contact information is essentially a same piece of contact information.
The condition that contact information is similar refers to that contact information in one or more fields set in user contact cards is the same. For example, major fields are the same, and a major field may refer to a name, a mobile number, a home number, an office number, or the like.
The condition that contact information is not identical refers to that all contact information in user contact cards is different, or contact information in major fields in user contact cards is different.
A specific processing process may be set as follows:
If the comparison result is identical, automated processing is performed on a group of contact cards whose comparison result is identical, that is, one user contact card in the contact card group is retained, and another same user contact card in the user contact card group is deleted. The user may not be prompted with this operation, and a processing result is subject to a time at which a contact card is backed up to the server most recently.
If the comparison result is similar (where major fields are the same, and a major field may refer to, for example, a name, a mobile number, a home number, an office number, or the like. ) , the user is prompted with a group of contact cards whose comparison result is similar, so that the user manually performs merging as needed.
Content prompted to the user may include: the contact card group that meets the condition that contact information is similar, where information in each field of each contact card is displayed； and the user is prompted whether to perform merging processing on two or more contact cards in the contact card group.
Merging processing on the contact card group that meets the condition that contact information is similar may refer to combining information in each field in two or more contact cards to form a new contact card； and may also be selecting, by the user, one contact card in the contact card group as current information of a contact, and deleting another contact card in the contact card group that meets the condition that contact information is similar.
The user may determine, according to an actual situation, whether to perform corresponding merging processing on user contact cards that meet the condition that contact information is similar. If merging processing is needed, the user may manually select and merge fields or perform corresponding deletion processing on the client. The server performs, according to an operation result of the user client, corresponding merging processing on the user contact card group that meets the condition that contact information is similar.
If the comparison result is not identical, the comparison result may not be displayed to the user, that is, no processing may be performed； or corresponding execution result information is fed back to the user client 301, for example, information indicating that a merging operation is completed, or cards of duplicate contacts that need to be merged do not exist is fed back.
In this embodiment, by using the foregoing solution, when receiving a request, initiated by a user client 301, for merging cards of duplicate contacts, a server 302 pulls data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information； compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and performs corresponding processing on the user contact cards according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, and storage space of the server 302 is saved.
In addition, in this embodiment, completely same user contact cards are merged, and similar contact cards are grouped for a user to select and merge fields, so that cards of duplicate contacts of a user at a server end 302 caused by various reasons are merged more intelligently, which solves the problem of cards of duplicate contacts of the user, and provides desirable experience for the user.
Further, after obtaining the data of the user contact cards by pulling, the server 302 further needs to perform generalization processing on the data of the user contact cards, so that comparability of the contact cards is improved, and the server 302 conveniently compares different user contact cards.
Performing generalization processing on the data of the user contact cards may be: orchestrating fields in a user contact card according to a certain rule, for example, the user contact cards in Table 1 may be all orchestrated in a sequence of fields in a user contact card: a number, a name, a mobile number, and an email address. In this way, the server 302 conveniently compares different fields, and the server 302 compares different user contact cards more efficiently.
Further, after the server 302 receives the request, initiated by the user client 301, for merging cards of duplicate contacts, the server 302 further needs to verify legality of the identity of the user to improve security of an operation of merging contact cards.
Specifically, after receiving the request, initiated by the user client 301, for merging cards of duplicate contacts, the server 302 verifies legality of the request for merging cards of duplicate contacts, for example, a user ID carried in the user request is matched； and if the matching succeeds, the verification succeeds, which indicates that the user identity is legal； and if the matching fails, the verification does not succeed, which indicates that the user identity is illegal.
After the verification succeeds, the server 302 pulls the data of the user contact cards according to the request for merging cards of duplicate contacts； compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and performs merging processing on the user contact cards according to the comparison result by using a preset policy.
When the verification does not succeed, the user client 301 is prompted with the information indicating a verification failure.
Therefore, by using the foregoing solution, when receiving a request, initiated by a user client 301, for merging cards of duplicate contacts, a server 302 verifies legality of the request for merging cards of duplicate contacts； after the verification succeeds, pulls data of user contact  cards corresponding to the user client according to the request for merging cards of duplicate contacts, where each of the user contact cards includes contact information； performs generalization processing on the data of the user contact cards； compares the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and performs corresponding processing on the user contact cards according to the comparison result by using a preset policy. Therefore, accuracy of merging duplicate contacts is improved, storage space of the server 302 is saved, and security and efficiency of an operation of merging contact cards are improved.
In should be further noted that in this specification, the terms "include" , "comprise" , or any variation thereof are intended to cover a non-exclusive inclusion. Therefore, in the context of a process, method, object, or device that includes a series of elements, the process, method, object, or device not only includes such elements, but also includes other elements not specified expressly, or may include inherent elements of the process, method, object, or device. Unless otherwise specified, an element limited by "include a/an. . . " does not exclude other same elements existing in the process, the method, the object, or the device that includes the element.
The foregoing sequence numbers of the embodiments of the present invention are merely for the purpose of description, and do not indicate preferences of the embodiments.
Through the foregoing description of the embodiments, it is clear to a person skilled in the art that the method of the foregoing embodiments may be implemented by software plus a necessary universal hardware platform, and certainly may also be implemented by hardware, but in many cases, the former implementation manner is preferred. Based on such an understanding, the technical solutions of the present disclosure essentially or the part contributing to the prior art may be implemented in a form of a software product. The computer software product is stored in a storage medium (for example, a ROM/RAM, a magnetic disk, or an optical disc) and includes several instructions for instructing a terminal device (which may be a mobile phone, a computer, a server, a network device, or the like) to perform the methods described in the embodiments of the present invention.
The foregoing descriptions are merely preferred embodiments of the present invention, and are not intended to limit the patent scope of the present disclosure. Any equivalent modification made to the structure or processes based on the content of this specification and the accompanying drawings for direct or indirect use in other related technical fields shall be also encompassed in the patent protection scope of the present disclosure.

Claims (17)

  1. A contact information processing method, applied to a server having one or more processors and a memory for storing program modules to be executed by the one or more processors, comprising:
    receiving a request, initiated by a user client, for merging cards of duplicate contacts；
    pulling data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, each of the user contact cards comprising contact information；
    comparing the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and
    processing the user contact cards according to the comparison result by using a preset policy.
  2. The method according to claim 1, after the step of pulling data of user contact cards, further comprising:
    performing generalization processing on the data of the user contact cards, wherein the generalization processing is orchestrating fields in a user contact card according to a certain rule.
  3. The method according to claim 1 or 2, wherein the step of processing the user contact cards according to the comparison result by using a preset policy comprises:
    when the comparison result meets a set condition that contact information is identical, for a user contact card group that meets the condition that contact information is identical, retaining one user contact card in the user contact card group, and deleting another user contact card in the user contact card group.
  4. The method according to claim 1 or 2, after the step of processing the user contact cards according to the comparison result by using a preset policy, comprising:
    when the comparison result meets a set condition that contact information is similar, returning, to the user client, a user contact card group that meets the condition that contact information is similar, so that the user client determines whether to perform merging processing on user contact cards that meet the condition that contact information is similar； and
    when the user requests performing merging processing on the user contact cards that meet the condition that contact information is similar, performing corresponding merging processing on the user contact card group that meets the condition that contact information is similar.
  5. The method according to claim 1 or 2, after the step of processing the user contact cards according to the comparison result by using a preset policy, further comprising:
    when the comparison result meets a set condition that contact information is not identical, feeding back corresponding execution result information to the user client.
  6. The method according to claim 3, wherein the condition that contact information is identical refers to that all contact information in user contact cards is identical.
  7. The method according to claim 4, wherein the condition that contact information is similar refers to that contact information in one or more fields set in user contact cards is the same.
  8. The method according to claim 5, wherein the condition that contact information is not identical refers to that contact information in all fields set in user contact cards is different.
  9. The method according to claim 1 or 2, after the step of receiving a request, initiated by a user client, for merging cards of duplicate contacts, further comprising:
    verifying legality of the request for merging cards of duplicate contacts； and after the verification succeeds, performing the step of pulling data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts.
  10. A contact information processing apparatus, applied to a server in communication with a user client for contact information processing and comprising:
    one or more processors； and
    a memory storing one or more program modules to be executed by the one or more processors, the program modules comprising instructions for executing the method according to any one of claims 1 to 9；
    the apparatus comprising:
    a receiving module, configured to receive a request, initiated by a user client, for merging cards of duplicate contacts；
    a pulling module, configured to pull data of user contact cards corresponding to the user client according to the request for merging cards of duplicate contacts, each of the user contact cards comprising contact information；
    a comparison module, configured to compare the user contact cards with each other based on the data of the user contact cards, to obtain a comparison result； and
    a processing module, configured to process the user contact cards according to the comparison  result by using a preset policy.
  11. The apparatus according to claim 10, further comprising:
    a generalization processing module, configured to perform generalization processing on the data of the user contact cards, wherein the generalization processing is orchestrating fields in a user contact card according to a certain rule.
  12. The apparatus according to claim 10 or 11, wherein
    the processing module is further configured to: when the comparison result meets a set condition that contact information is identical, for a user contact card group that meets the condition that contact information is identical, retain one user contact card in the user contact card group, and delete another user contact card in the user contact card group.
  13. The apparatus according to claim 10 or 11, wherein
    the processing module is further configured to: when the comparison result meets a set condition that contact information is similar, return, to the user client, a user contact card group that meets the condition that contact information is similar, so that the user client determines whether to perform merging processing on user contact cards that meet the condition that contact information is similar； and when the user requests performing merging processing on the user contact cards that meet the condition that contact information is similar, perform corresponding merging processing on the user contact card group that meets the condition that contact information is similar.
  14. The apparatus according to claim 10 or 11, wherein
    the processing module is further configured to: when the comparison result meets a set condition that contact information is not identical, feed back corresponding execution result information to the user client.
  15. The apparatus according to claim 12, further comprising:
    a verification module, configured to verify legality of the request for merging cards of duplicate contacts, so that after the verification succeeds, the pulling module pulls the data of the user contact cards according to the request for merging cards of duplicate contacts.
  16. A contact information processing system, comprising: a user client and a server, the user client being configured to initiate, to the server, a request for merging cards of duplicate contacts； and
    the server comprising the apparatus according to any one of claims 10 to 15.
  17. The system according to claim 16, wherein
    the user client is further configured to: when a comparison result meets a set condition that contact information is similar, receive a user contact card group that is returned by the server and meets the condition that contact information is similar； determine whether to perform merging processing on user contact cards that meet the condition that contact information is similar； and if yes, request the server to perform merging processing on the user contact cards that meet the condition that contact information is similar.
PCT/CN2015/070843 2014-01-17 2015-01-16 Contact information processing method, apparatus, and system WO2015106710A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410023836.3A CN104796312B (en) 2014-01-17 2014-01-17 Contact person information processing method, apparatus and system
CN201410023836.3 2014-01-17

Publications (1)

Publication Number Publication Date
WO2015106710A1 true WO2015106710A1 (en) 2015-07-23

Family

ID=53542422

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/070843 WO2015106710A1 (en) 2014-01-17 2015-01-16 Contact information processing method, apparatus, and system

Country Status (2)

Country Link
CN (1) CN104796312B (en)
WO (1) WO2015106710A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108897728A (en) * 2018-06-27 2018-11-27 平安科技（深圳）有限公司 Short message splicing processing method, device, computer equipment and storage medium
CN112073174A (en) * 2020-07-28 2020-12-11 广州骏伯网络科技有限公司 Communication account decryption method, device, equipment, storage medium and information interaction system

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105260344B (en) * 2015-09-08 2018-06-01 北京乐动卓越科技有限公司 Address list accurately merges the method and system of duplicate removal
CN107302617A (en) * 2017-05-17 2017-10-27 深圳市金立通信设备有限公司 A kind of data managing method and terminal
CN110505141B (en) * 2018-05-17 2022-10-28 腾讯科技（深圳）有限公司 Instant messaging message processing method and device, readable medium and electronic equipment
CN109309750A (en) * 2018-09-19 2019-02-05 珠海格力电器股份有限公司 Contact merging method and device, storage medium and mobile terminal

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068156A (en) * 2006-12-20 2007-11-07 腾讯科技（深圳）有限公司 Conflict processing method and conflict processing server when data synchronization
US20110307455A1 (en) * 2010-06-10 2011-12-15 Microsoft Corporation Contact information merger and duplicate resolution
CN102624682A (en) * 2011-06-30 2012-08-01 北京小米科技有限责任公司 Method for managing client data

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN201167394Y (en) * 2008-03-11 2008-12-17 宇龙计算机通信科技(深圳)有限公司 Mobile terminal equipment
CN102333299A (en) * 2011-05-30 2012-01-25 上海合合信息科技发展有限公司 Method for providing information of contact
CN103248635A (en) * 2012-02-03 2013-08-14 腾讯科技（深圳）有限公司 Contact processing method, terminal and server
CN103200293A (en) * 2013-03-05 2013-07-10 上海斐讯数据通信技术有限公司 Method of automatically combining tautonomy contacts in process of guiding contacts into contact list
CN103442135B (en) * 2013-08-19 2015-06-17 惠州Tcl移动通信有限公司 Processing method for merging contact items and eliminating duplication and touch control terminal

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101068156A (en) * 2006-12-20 2007-11-07 腾讯科技（深圳）有限公司 Conflict processing method and conflict processing server when data synchronization
US20110307455A1 (en) * 2010-06-10 2011-12-15 Microsoft Corporation Contact information merger and duplicate resolution
CN102624682A (en) * 2011-06-30 2012-08-01 北京小米科技有限责任公司 Method for managing client data

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108897728A (en) * 2018-06-27 2018-11-27 平安科技（深圳）有限公司 Short message splicing processing method, device, computer equipment and storage medium
CN112073174A (en) * 2020-07-28 2020-12-11 广州骏伯网络科技有限公司 Communication account decryption method, device, equipment, storage medium and information interaction system
CN112073174B (en) * 2020-07-28 2023-06-27 广州骏伯网络科技有限公司 Communication account decryption method, device, equipment, storage medium and information interaction system

Also Published As

Publication number Publication date
CN104796312A (en) 2015-07-22
CN104796312B (en) 2017-12-26

Similar Documents

Publication Publication Date Title
WO2015106710A1 (en) Contact information processing method, apparatus, and system
US9870268B2 (en) Virtual computing instance migration
US20200089718A1 (en) Inferred user identity in content distribution
CN109614238B (en) Target object identification method, device and system and readable storage medium
WO2019075842A1 (en) Task allocation method and apparatus, storage medium and computer device
US20160232374A1 (en) Permission control method and apparatus
US9355250B2 (en) Method and system for rapidly scanning files
CN106095513B (en) Application self-identification safe starting method and system
US20190220439A1 (en) Software Discovery with Variable Scan Frequency
EP2715565A2 (en) Dynamic rule reordering for message classification
US20150249665A1 (en) Method and system for extracting characteristic information
CN109472540B (en) Service processing method and device
CN105260639A (en) Face recognition system data update method and device
CN110737891A (en) host intrusion detection method and device
US10033737B2 (en) System and method for cross-cloud identity matching
CN106250181A (en) The performance optimization method of a kind of (SuSE) Linux OS and framework
CN109783440B (en) Data storage method, data retrieval method, data storage device, medium and electronic equipment
US9514501B2 (en) Systems and methods for multimedia-processing
CN113434069A (en) Menu configuration method, device, equipment and storage medium
CN110597682B (en) Application deployment method and device, computer equipment and storage medium
CN107704557B (en) Processing method and device for operating mutually exclusive data, computer equipment and storage medium
WO2015081834A1 (en) Method and apparatus for distinguishing software types
CN109582680A (en) Method for processing business, electronic device and readable storage medium storing program for executing based on new product development
CN107644043B (en) Internet bank quick navigation setting method and system
CN104239145B (en) A kind of data consistency control method and device based on case mechanism

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15736895

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 19.12.16)

122 Ep: pct application non-entry in european phase

Ref document number: 15736895

Country of ref document: EP

Kind code of ref document: A1