WO2017206696A1 - 联系方式处理方法及装置、存储介质 - Google Patents

联系方式处理方法及装置、存储介质 Download PDF

Info

Publication number
WO2017206696A1
WO2017206696A1 PCT/CN2017/084032 CN2017084032W WO2017206696A1 WO 2017206696 A1 WO2017206696 A1 WO 2017206696A1 CN 2017084032 W CN2017084032 W CN 2017084032W WO 2017206696 A1 WO2017206696 A1 WO 2017206696A1
Authority
WO
WIPO (PCT)
Prior art keywords
contact
user
address book
mode
contact mode
Prior art date
Application number
PCT/CN2017/084032
Other languages
English (en)
French (fr)
Inventor
林立
邓雨星
林�也
Original Assignee
腾讯科技（深圳）有限公司
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 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Publication of WO2017206696A1 publication Critical patent/WO2017206696A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42136—Administration or customisation of services
    • H04M3/42144—Administration or customisation of services by service provider
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/951—Indexing; Web crawling techniques

Definitions

  • the present invention relates to communications technologies, and in particular, to a contact processing method and apparatus, and a storage medium.
  • multiple contact methods may be stored for the same user.
  • the mobile phone number as an example, one or more of the plurality of mobile phone numbers for the same user in the address book may be currently in a down state, or have been The operator recycles the owner, so there is a failure number (such as downtime or change of owner).
  • a failure number such as downtime or change of owner.
  • the embodiment of the present invention is to provide a contact processing method and device, and a storage medium, which can accurately identify a failure contact manner in an address book, thereby improving communication efficiency.
  • an embodiment of the present invention provides a contact processing method, including:
  • the characteristics of each contact method that meets the predetermined condition are analyzed, and the contact mode matching the preset feature is selected as the failure contact mode.
  • an embodiment of the present invention provides a contact processing apparatus, including:
  • the search module is configured to search for any two address books in multiple address books to obtain a user with an associated relationship
  • a building block configured to construct a relationship chain formed by users having an associated relationship
  • a determining module configured to search for a common user of the address book corresponding to each user in the relationship chain, compare the contact manners of the shared users, and obtain a contact manner that the comparison result meets a predetermined condition
  • the screening module is configured to analyze the characteristics of each of the contact modes that meet the predetermined condition, and select a contact mode that matches the preset feature as a failed contact mode.
  • an embodiment of the present invention provides a contact processing apparatus, including:
  • a memory configured to store an executable program
  • the processing method of the contact method provided by the embodiment of the present invention is implemented when the processor is configured to execute the executable program stored in the memory.
  • an embodiment of the present invention provides a storage medium, where an executable program is stored, and when the executable program is executed by a processor, the contact processing method provided by the embodiment of the present invention is implemented.
  • the shared user is a potential user holding the invalid contact method.
  • the relationship chain of the user with the associated relationship can be constructed through the address book, and the search is realized by the address book of each user in the relationship chain. The technical effect of efficiently locating potential users holding invalid contact methods.
  • the characteristics of the characteristics of the failure contact method are screened, and the technical effect of accurate positioning of the failure contact mode is realized.
  • the sequential processing method is beneficial to a large number of communication. Record batch identification of invalid contact methods.
  • FIG. 1 is a schematic diagram of an optional application scenario of a method for processing a contact method according to an embodiment of the present disclosure
  • FIG. 2 is a schematic structural diagram of an optional hardware of a contact processing device according to an embodiment of the present invention.
  • FIG. 3 is an optional schematic flowchart of a method for processing a contact method according to an embodiment of the present disclosure
  • FIG. 4 is an optional schematic diagram of a method for processing a contact method according to FIG. 1 according to an embodiment of the present invention
  • FIG. 5 is another schematic flowchart of a method for processing a contact method according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of a comparison before and after an invalid contact mode in an address book according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a comparison before and after information of the usage frequency of the identifier in the address book according to the embodiment of the present invention.
  • FIG. 8a is a schematic diagram of an optional implementation of clearing the invalid number function switch according to an embodiment of the present invention.
  • FIG. 8b is another schematic implementation diagram of clearing the invalid number function switch according to an embodiment of the present invention.
  • FIG. 8c is an optional schematic diagram of a contact corresponding to multiple phone numbers in an embodiment of the present invention.
  • FIG. 8 is a schematic implementation diagram of identifying a function switch of a failed number according to an embodiment of the present invention.
  • FIG. 8e is a schematic diagram of an optional interface for cleaning up a failed number according to an embodiment of the present invention.
  • FIG. 9a is a schematic flowchart of determining an invalid phone number in an embodiment of the present invention.
  • FIG. 9b is an optional schematic diagram of a contact degree in an embodiment of the present invention.
  • 9c is a schematic diagram of an optional data flow direction for determining a failed telephone number according to an embodiment of the present invention.
  • FIG. 10 is another schematic structural diagram of a contact processing device according to an embodiment of the present invention.
  • the terms "including”, “comprising”, or any other variations thereof are intended to encompass non-exclusive inclusions, such that a method or apparatus comprising a plurality of elements includes not only the Elements, but also other elements not explicitly listed, or elements that are inherent to the implementation of the method or device.
  • an element defined by the phrase “comprising a " does not exclude the presence of additional related elements (such as steps in the method or means in the device) in the method or device including the element.
  • the contact processing method provided by the embodiment of the present invention includes a series of steps, but the contact processing method provided by the embodiment of the present invention is not limited to the described steps, and the contact processing device provided by the embodiment of the present invention is similarly provided.
  • a series of modules are included, but the contact processing device provided by the embodiment of the present invention is not limited to including the explicitly described module, and may further include a module/unit that needs to be set to acquire relevant information or process based on the contact method.
  • first”, “second”, “third” and the like are merely different objects, and do not represent a specific ordering for an object.
  • a “/" second/"third” may be interchanged in a particular order or order, where permitted. It will be understood that the objects of the "first” / "second” / “third” distinction may be interchanged where appropriate to enable embodiments of the invention described herein to be capable of other than those illustrated or described herein. Implemented sequentially.
  • Contact information which can establish communication information with users through information technology, such as phone number, email address, social network account number, etc.
  • the terminal can be a device such as a smart phone, a tablet computer, a desktop computer, a notebook computer, a wearable device (such as a smart watch) capable of supporting wired or wireless communication or supporting various applications or social software for communication.
  • a wearable device such as a smart watch
  • the embodiment of the invention describes a contact processing method and device, and a storage medium, which is used for identifying a failed contact manner in multiple contact manners of the same contact in the address book, for example, identifying a failure from multiple phone numbers of the same user.
  • the number identifies a failed e-mail address from a plurality of e-mail addresses of the same user.
  • the contact number is a telephone number as an example, but the embodiment of the present invention does not exclude other types of contact information.
  • FIG. 1 An example of an application scenario in which the contact processing device is configured on the network side is as shown in FIG. 1 .
  • an optional application scenario of the contact processing method in the embodiment of the present invention is related to the following entities: a terminal 11 supporting the address book, and a contact
  • the server 12 and the network 13 are processed in a manner.
  • the terminal 11 and the contact processing server 12 perform data interaction through the network 13, and the terminal 11 may be multiple.
  • the communication is found.
  • the related art does not support the user to know which of the three numbers is a valid number, and the user can only try to dial or contact one by one. In this process, multiple attempts to dial will consume too much time and effort of the user, and reduce the use of the address book. Efficiency, reducing user communication efficiency.
  • FIG. 1 is only one possible architecture example of the technical solution described in the embodiment of the present invention.
  • Other application scenarios may include a terminal not involved in FIG. 1 or installed on the terminal. Communication applications or social software, etc. Techniques described in the embodiments of the present invention The solution can be applied to the above scenarios to solve the problem that it is difficult to determine the failure contact method in the related art.
  • FIG. 1 the contact processing device is set as an example on the network side server. It can be understood that the contact processing device can be set in various terminals according to actual implementation requirements.
  • FIG. 2 is an optional hardware structure diagram of the contact processing device 20 according to the embodiment of the present invention.
  • the contact processing device 20 shown in FIG. 2 includes: at least one processor 21, a memory 22, and at least one communication interface 24. And user interface 23.
  • the various components in the contact processing device 20 are coupled together by a bus system 25. It will be appreciated that the bus system 25 is used to implement connection communication between these components.
  • the bus system 25 includes, in addition to the data bus, a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 25 in FIG.
  • the user interface 23 may include a display, a keyboard, a mouse, a trackball, a click wheel, a button, a button, a touch panel, or a touch screen.
  • memory 22 can be either volatile memory or non-volatile memory, as well as both volatile and non-volatile memory.
  • the memory 22 described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.
  • the memory 22 in the embodiment of the present invention is used to store various types of data to support the operation of the contact processing device 20.
  • Examples of such data include any computer program for operating on the contact processing device 20, such as an operating system 221 and an application 222; address book data, and the like.
  • the operating system 221 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, for implementing various basic services and processing hardware-based tasks.
  • the application 222 can include various applications, and the program for implementing the contact processing method of the embodiment of the present invention can be included in the application 222.
  • Processor 21 may be an integrated circuit chip with signal processing capabilities. In reality In the present process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 21 or an instruction in the form of software.
  • the processor 21 described above may be a general purpose processor, a digital signal processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or the like.
  • DSP digital signal processor
  • the processor 21 can implement or perform the various methods, steps, and logic blocks disclosed in the embodiments of the present invention.
  • a general purpose processor can be a microprocessor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiment of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a storage medium located in the memory 22, and the processor 21 reads the information in the memory 22, in conjunction with its hardware, to perform the steps of the aforementioned contact processing method.
  • the contact processing device 20 may be configured by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), and Complex Programmable Logic Devices.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal processors
  • PLDs Programmable Logic Devices
  • Complex Programmable Logic Devices CPLD, Complex Programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • controller controller
  • microcontroller MCU, Micro Controller Unit
  • microprocessor Microprocessor
  • Other electronic component implementations are used to perform the aforementioned method of contact processing.
  • the embodiment of the invention provides a contact processing method, which can be used to identify a contact contact manner of a contact in an address book, such as an invalidation number.
  • the contact processing method described in the embodiment of the present invention includes the following steps:
  • Step 101 Obtain an address book of the user, and the address book includes a contact information of the contact of the user.
  • the contact processing device is configured as a network side server, and the contact processing server obtains an address book of the corresponding terminal user from multiple terminals, for example, a terminal that enables/uses the address book synchronization function.
  • the address book can be stored on the network side, such as a cloud server.
  • the contact processing server can obtain this from the network side after obtaining the authorization of each user.
  • the user's address book; optionally, the user's authorization can be implemented as follows: the user sets whether to allow the contact processing server to obtain the user's address book in the address book synchronization function, and if yes, instructs the contact processing server to obtain the user's authorization.
  • the contact processing server may be the same device as the network side, or may be a different device; here, a user's address book may include the name and contact information of the user's contact;
  • the contact information of the contact includes: a phone number, an email address, a communication address, and a user identity certificate of a social application (such as WeChat, QQ).
  • the contact processing device is set in the terminal as an example, and the terminal acquires the address records of the plurality of users from the plurality of terminals.
  • an address book of a user who has opened/used the address book sharing function can synchronize the address book to the trusted terminal periodically or irregularly.
  • the trusted terminal refers to a terminal that mutually opens data/information access rights through pre-authentication. .
  • Step 102 Search for an address book of any two users, obtain a user who is a contact in the address book of any two users, and construct at least one relationship chain based on the association relationship of the users who are the contacts.
  • the users who are contacts are the users with the associated relationship determined based on the address book, and the contacts of the two users who are the contacts respectively include the contact information of the other party.
  • searching for an address book of any two users to obtain a feasible implementation manner of a user who is a contact is determined according to the first user's address book and the second user's address book. For example, whether the first user has a relationship with the second user is as follows:
  • Step 1021 Acquire a contact mode of the first user and a contact mode of the second user respectively; where the first user and the second user are any two different users of the multiple users;
  • Step 1022 Search for a contact information of the second user in the address book of the first user.
  • Step 1023 Find the contact information of the first user in the address book of the second user.
  • the determination is One user and the second user are each other's contacts.
  • a feasible implementation manner of constructing at least one relationship chain based on users who are contacts as each other includes: using any one of the users as contacts as a node, and any user The other users who are contacts each other are cascaded nodes, and the relationship chain is constructed based on the cascaded nodes; if the first user and the second user are determined as contacts, the first user is the node and the second user is the cascade. Nodes, based on cascaded nodes, build a relational chain.
  • traversing to find any two of the above-mentioned multiple users assuming that the contact processing server has acquired a total of three different users, such as the address records of user A, user B, and user C, the following operations are required: 1) Find the address records of user A and user B, determine whether user A and user B are contacts of each other; 2) find the address records of user A and user C, and determine whether user A and user C are contacts of each other; 3) Find the address book of user B and user C, determine whether user B and user C are contacts of each other; 4) construct at least one relationship chain based on the users who are contacts as determined by steps 1) to 3) above; Any two users in A, B, and C are contacts of each other, and users A, B, and C form a triangular relationship chain, and each user corresponds to one end of the triangle.
  • Step 103 Determine the same contact based on the address book of each user in the relationship chain, compare the contact manners of the same contact in different address books (ie, the address book of each user in the relationship chain), and obtain a comparison result that is consistent with the reservation. Contact information for conditions.
  • the same contact is a user shared by at least two address books, and thus may also be referred to as a shared user, and the same contact may be compared by a user identifier (such as a user name, a serial number, etc.). Or the user's contact method is determined in a comparison manner, that is, for two address books, if the same user identifier is included, or the same contact information is included, it is determined to include the same contact.
  • a user identifier such as a user name, a serial number, etc.
  • a feasible implementation manner of the foregoing step 103 includes: searching for the name and contact manner of each contact in each user's address book in the relationship chain, and searching whether the address of each user in the relationship chain has the same name.
  • the target contact if not, the process ends; if yes, the contact information corresponding to the target contact in the address book of each user in the relationship chain is compared, and if the contact manner is different, in the address book of each user in the relationship chain, Determine the contact information corresponding to the target contact as the contact method that meets the predetermined conditions.
  • another feasible implementation manner of the foregoing step 103 includes: searching for a name and a contact manner of each contact in each user's address book in the relationship chain, and searching whether the address records of each user in the relationship chain have the same The target contact of the contact method, if not, the process ends; if yes, the name corresponding to the target contact in the address book of each user in the relationship chain, if the name is different, in the address book corresponding to each user of the relationship chain , determine the contact information of the target contact, as a contact method that meets the predetermined conditions.
  • contact list 1 and address book 2 if there is contact 1 (such as a certain phone number), then the contact user 1 corresponds to the corresponding user in address book 1, and corresponds to address book 2 User, if it is a different user, set to user A and user B, then all contact information of user A in address book 1 (except contact 1, address book 1 may also include other contact information corresponding to user A) And all the contact information in the address book 2 meet the predetermined conditions, which is a potential failure contact method; at the same time, all the contact information of the user B in the address book 1, And all contact information in Address Book 2 (except Contact 2, Address Book 2 may also include other contact information for User B). Compliance with the predetermined conditions is a potential invalid contact method.
  • Step 104 Analyze the characteristics of the contact modes that meet the predetermined conditions based on the communication data of the contact information that meets the predetermined condition, and select the contact mode that matches the preset feature as the invalid contact mode.
  • a new attribute may be added to the corresponding contact mode in the associated address book: the invalid contact mode; or, for the contact that is not identified as the invalid contact mode.
  • the attribute of the effective contact method is added as one of the basis for the user to judge whether to use, modify or delete the contact method.
  • the filtered contact information is stored in the contact processing server, for example, the filtered invalid contact information is written into a record table dedicated to storing the user's invalid contact information, or stored.
  • the database used to store the address book is synchronized to the terminal by means of active delivery or passive request.
  • the characteristics of the contact manners that meet the predetermined conditions are analyzed, and the contact mode matching the preset features is selected as the implementation manner of the invalid contact mode, and Includes any one or combination of the following:
  • the information verification contact method for example, including verification based on SMS login, user application registration, etc.
  • the contact method is not used for a long time, it is a failed contact method.
  • the possibility of using the contact method with higher frequency is higher.
  • the communication data of each contact method that meets the predetermined condition is parsed, and the usage time of each contact method that meets the predetermined condition is used for the information verification mode (for example, , the time of the last communication, determining whether the time difference between the usage time and the current time is greater than the first time threshold, and if so, determining The corresponding contact mode is the invalid contact mode; otherwise, the corresponding contact mode is determined as a valid contact mode; here, the first time threshold may be set by the user/contact processing server based on historical data, actual demand, and the like.
  • the scene device that the same phone number is recycled by the operator not only needs to determine the invalid contact mode, but also needs to determine which user the invalid contact mode corresponds to. Invalid contact method.
  • the first contact mode is set, and the user who has the first contact mode in the address book of each user in the relationship chain is set as the first user, and the analysis represents the first
  • the communication data used for information verification is used to obtain the usage time of the first contact mode used by the first contact for the information verification mode, and whether the time difference between the use time and the current time is greater than the first time threshold, where the first time threshold is
  • the user/contact processing server may be configured based on historical data, actual requirements, etc., if yes, determining that the first contact mode is the invalid contact mode of the first contact; otherwise, determining that the first contact mode is the first contact Effective contact method.
  • connection mode is related to various applications used by the user (such as payment application and social use). It is a high-frequency use scenario of contact mode. When the contact mode does not have any application binding, it is the possibility of invalid contact. There is a high probability that the contact is bound to the application.
  • the associated application data may include a contact mode and an application binding; the associated contact mode of the application, for example, the contact mode is bound to the verification number, the application registration by the contact method, the contact mode is bound to the application account, and the like.
  • the second contact mode is set, and the user who has the first contact mode in the address book of each user in the relationship chain is set as the second user, and the second contact mode is set.
  • determining whether the second contact mode is used as the associated contact mode of the application used by the second contact, and if not, determining that the second contact mode is the invalid contact of the second contact The method; if yes, determining that the second contact is a valid contact of the second contact.
  • the communication time may be, for example, the latest communication time (such as the time when the short message was sent or received, the time of making a phone call or a mail), etc.; here, the second time threshold may be processed by the user/contact server based on historical data and actual demand. Wait for setting.
  • the contact processing server not only needs to determine the invalid contact mode, but also needs to determine that the invalid contact mode corresponds to Which contact.
  • the third contact mode is set, and the user having the third contact mode in the address book of each user in the relationship chain is set as the third user, and the third contact is analyzed.
  • the method corresponds to the communication data of the communication record of the third contact, and obtains the communication time of the third contact mode; determines whether the time difference between the communication time of the third contact mode and the current time is greater than a second time threshold, and if yes, determines the third contact mode. Invalidation for the third contact Contact method; otherwise, the third contact method is determined as the effective contact method of the third contact.
  • the foregoing determining manner may be used alternatively or in combination. For example, by analyzing the communication data of the contact mode, it is determined whether at least two of the following conditions are met: the time difference between the used time and the current time is greater than the first time threshold; The associated contact mode of the application; whether the time difference between the communication time and the current time is greater than the second time threshold.
  • the contact processing server may send the invalid contact mode in the user's address book to the terminal in the user's address book when the condition of the failed contact mode is met. Identify the invalid contact method; of course, for the terminal to identify the invalid contact method, the terminal can also identify the invalid contact mode in the address book.
  • the implementation manner of the failure contact delivery condition may include any one or combination of the following:
  • the terminal When the terminal receives the user-triggered invalidation number cleaning operation for the address book, the terminal sends a request for managing the user's address book to the contact processing server; the contact processing server responds to the terminal's address book for managing the user. The request sends the invalid contact information in the user's address book to the terminal.
  • the terminal When the terminal receives the user-triggered invalid number identification operation for the specified contact in the address book, the terminal sends a request for managing the contact in the user's address book to the contact processing server, where the request carries the name of the designated contact Or the contact information to be identified; the contact processing server sends a failure contact manner of the designated contact in the user's address book to the terminal in response to the request sent by the terminal for managing the user's address book.
  • the event-triggered active delivery for example, the contact processing server detects that the absolute number or relative number of invalid contact modes in the user's address book exceeds a preset number threshold.
  • a feasible way to contact the server to determine the invalid contact method in the user's address book includes: the contact processing server matches the contact manners of each contact in the user's address book with the selected invalid contact manner, and obtains the invalid contact manner in the user's address book; optionally, the contact The mode processing server saves the invalid contact information in the determined user's address book.
  • the terminal processes the invalid contact mode in the user's address book sent by the server according to the contact mode, and identifies the invalid contact mode in the user's address book; for the user to operate the invalid contact mode identified in the user's address book, for example, the user will
  • the invalid contact information identified in the address book is deleted in whole or in part, or the user cancels the identification of some or all of the contact information identified in the address book as the invalid contact method.
  • the user knows that one or more of the contact information is identified as the invalid contact method.
  • the contact method is actually an effective contact method.
  • the contact processing server After the user operates the invalid contact information identified in the user's address book, the contact processing server updates the address book of the user stored synchronously in the network side in response to the user's operation for the invalid contact mode identified in the user's address book. Invalid contact method; optionally, when the user identifies the contact information of the contact information that is identified as the invalid contact mode in the user's address book, the contact processing server deletes the contact information of the cancelled identification from the invalid contact information selected above. .
  • FIG. 4 An optional process based on the architecture implementation method shown in FIG. 4 includes:
  • Step 201 When the terminal user of the terminal 11 wants to make a call or send a message to the Li**, the terminal user queries the address book of the terminal 11, and finds that three phone numbers are stored under the address of the address book, respectively, and the phone number is respectively 1. Phone number 2 and phone number 3. At this time, the terminal user faces multiple phone numbers corresponding to the contact person Lee, and does not know which phone number should be used.
  • Step 202 The terminal 11 detects that the terminal user is querying the address book and stays in the contact person Lee. ** Corresponding information page, and the terminal 11 finds that the contact li ** corresponds to a plurality of telephone numbers, and then sends a request for managing the address book of the terminal user of the terminal 11 to the contact processing server 12, and the request carries Contact the name of Li**, or carry multiple phone numbers corresponding to Li**.
  • Step 203 The contact processing server 12 searches for the invalid phone number of the contact person Lee from the invalid contact information of the terminal user's address book of the terminal 11 according to the name of the contact person Lee; or, the contact method
  • the processing server 12 matches the plurality of phone numbers corresponding to the Li** in the address book of the terminal user with the selected invalid contact information to determine the invalid phone number of the Lee.
  • the expired telephone number of Li** is telephone number 1 and telephone number 3.
  • Step 204 The contact processing server 12 transmits the expired telephone number (telephone number 1 and telephone number 3) of the Li** to the terminal 11.
  • Step 205 The terminal 11 processes the expired telephone number (telephone number 1 and telephone number 3) of the Li** sent by the server 12 according to the contact information, and sets the telephone number 1 corresponding to Li** in the address book of the terminal user of the terminal 11 and The telephone number 3 is respectively identified as "failed", thereby identifying the expired telephone number (telephone number 1 and telephone number 3) of Li**.
  • the end user can directly select the phone number 2 that is not identified as invalid to call or send a message to Li**, thereby preventing the user from attempting to dial or contact one by one for multiple numbers including the expired phone number.
  • the automatic identification of the invalid number in the address book overcomes the shortcomings of the related technology, which consumes user time and effort, reduces the use efficiency of the address book, and reduces the communication efficiency of the user.
  • the contact manners that meet the predetermined conditions are filtered out, and according to The feature of the contact method that meets the predetermined condition filters out the invalid contact mode that matches the preset feature, that is, by analyzing the contact information of the contact person of the address book of the plurality of terminal users, and identifying the invalid contact mode from all the contact modes, the user Direct use Communication with other contact methods (ie, effective contact methods) other than the failed contact mode prevents the end users in the related art from trying to communicate one by one for multiple contact modes including the failed contact mode, thereby saving the user's time. And the energy, as such, the embodiment of the present invention can automatically identify the invalid number in the address book, improve the use efficiency of the address book, and improve the communication efficiency of the user.
  • the embodiment of the present invention provides an example for explaining a processing scheme when the terminal receives an operation instruction triggered by the terminal user to clear the invalid contact mode in the address book.
  • the method for processing the contact method described in the embodiment of the present invention may be implemented by the terminal and the contact processing server, and the method includes the following steps:
  • Step 301 The terminal detects an operation of the terminal user for the address book.
  • Step 302 When the terminal detects an operation instruction triggered by the terminal user to clear the invalid contact mode in the address book, the terminal sends a message for obtaining the contact contact mode of each contact in the address book to the contact processing server; the message includes The identity of the end user, the contact information, or the contact details of all contacts in the address book.
  • Step 303 The contact processing server responds to the message sent by the terminal user for obtaining the contact information of each contact in the address book, and obtains the invalid contact manner of the plurality of terminal users determined in advance by querying the pre-generated database, and Matching the contact information of each contact in the address book of the terminal user with the invalid contact manner of multiple terminal users determined in advance, and obtaining the invalid contact manner of each contact in the address book of the terminal user, or by querying
  • the pre-generated database obtains a predetermined invalid contact manner of each contact in the address book of the end user.
  • Step 304 The contact processing server sends the obtained invalid contact manner of each contact in the address book of the terminal user to the terminal.
  • Step 305 The terminal processes the contact contact mode of each contact in the address book fed back by the server according to the contact mode, and identifies the corresponding contact mode in the address book as the invalid contact mode, as shown in FIG. 6
  • the contact contact mode of each contact in the illustrated address book is a schematic diagram of the comparison before and after the identification, for the terminal user to operate for the contact mode identified as the invalid contact mode in the address book, for example, The end user deletes all or part of the invalid contact information identified in the address book, or the terminal user cancels the identifier of some or all of the contact information identified in the address book as the invalid contact mode, for example, the user is determined to be identified as the invalid contact method.
  • One or more of the contact methods is actually an effective contact.
  • the terminal when the terminal user needs to clean up the invalid contact information of the address book, the terminal requests the terminal contact server to obtain the invalid contact information of each contact in the address book and identifies it in the address book, which is equivalent to each contact.
  • the method adds a new attribute: the invalid contact method, or the effective contact method (such as the contact information in the address book that is not identified as the invalid contact method), as one of the basis for the user to determine whether to use, modify or delete the contact method, saving the user Time and effort to improve the accuracy and efficiency of end users organizing contacts.
  • the embodiment of the present invention provides a technical solution for the requirement that the user wants to identify the usage frequency information of different contact modes of each contact in the address book, and specifically includes:
  • the contact method processes the message that the server actively or responds to the usage frequency information of the different contact manners of each contact sent by the terminal, and determines the communication of the terminal user based on the communication log data of each contact in the address book of the terminal user.
  • the frequency of use of communication by each contact in the contact is used; here, the frequency of use may include information such as common and infrequent use;
  • the contact processing server sends to the terminal the usage frequency information of different contact modes of each contact in the terminal user's address book.
  • the terminal identifies the usage frequency information of different contact modes of each contact in the address book of the terminal user; here, it is equivalent to adding new attributes for each contact mode: common or not commonly used, as the user judges whether to use or not One of the basis for modifying or deleting the contact information; it should be noted that the embodiment of the present invention is based on the foregoing embodiment, and the contact manner in the embodiment of the present invention
  • the usage frequency information (commonly used, not commonly used) refers to the frequency of contact (contact, phone, SMS, and related applications) used by contacts.
  • the contact information that is not marked as invalid (or marked as valid) may be The identification is commonly used, and may also be identified as not commonly used; see the contact information of each contact in the address book shown in FIG. 7 (executed by telephone number) is marked with a comparison diagram before and after using the frequency information, and at the same time view FIG. 6 and 7 can find:
  • the operation of the terminal user for the usage frequency information of different contact modes of each contact identified in the address book for example, deleting the contact information identified as infrequently used in the address book, or identifying the address book as an infrequent one. Or "unusual" identification of multiple contacts is cancelled.
  • the user knows that one or more contact methods identified as “unusual” are actually true and effective and commonly used contact methods; here, the end user can also be The contact information marked as “unusual” is cleared as the invalid contact method.
  • the end user can clean up the invalid contact information in the address book based on the usage frequency information of different contact methods of each contact identified in the address book.
  • the contact processing server updates the different contact manners of each contact in the address book of the terminal user that is synchronously stored in the network side in response to the operation of the end user's usage frequency information for different contact modes of each contact identified in the address book; For example, update the ID of the corresponding contact or delete the corresponding contact.
  • Embodiments of the present invention continue to implement the contact processing in combination with the example of the contact processing. The process is described.
  • the user can detect whether there is a invalid number in the address book of the terminal in the physical examination of the address book doctor, and prompt the user to organize; or
  • the user can also enter from the address book collation module to sort out the invalid number; or,
  • the terminal displays a button corresponding to the contact number (corresponding to multiple) corresponding to the plurality of phone numbers in the address book, and adds a button or an operation entry indicating the invalidation number for the user to select, see FIG. 8d, or the terminal detects the user from the page.
  • the user terminal is actively prompted to identify the invalid number in the plurality of phone numbers corresponding to the contact, and the recognition result is presented to the user.
  • the judgment tag (recognition result) is presented to the user. Referring to FIG. 8e, the user can independently select whether to process the numbers.
  • the calculation of the invalid phone number is divided into the offline calculation part and the online service part in the background. Due to the large amount of data processed, offline calculation can be performed on a distributed computing platform such as Hadoop platform, and then the result of offline calculation is imported into the storage. When the online service processes the user request, the storage is queried, and the part with the calculation result is returned to the user; see the invalid phone number calculation process shown in FIG. 9a.
  • the background of the address book will synchronize the user's contact data in the form of a log.
  • the data is stored in an encrypted manner on the distributed computing platform.
  • the current user is the center, and the contact in the user's address book can be established as the user's 1 degree contact if the user's and the contact's address book store the other party's number. For all 1 degree contacts, the contacts in their address book are taken out in turn, and then the 1 degree contact is established. At this time, the center user has a 2 degree user relationship circle, and the information data is imported in the form of user->phone number.
  • the degree of the contact is specifically: if two users mutually share the mobile phone number, then the two users are said to be 1 degree contact each other, and if there is a common 1 degree contact between the two users, then this is called Two users are 2 degree contacts to each other, and so on. Referring to FIG. 9b, users A and B and C are 1 degree contacts respectively, users A and D are 2 degree contacts, and users A and E are 3 degree contacts.
  • the offline part establishes the calculation of the user relationship circle.
  • the offline part uses the Hadoop platform to establish the contact pulse table on the Hadoop platform, that is, the relationship between users.
  • the user relationship circle can be established in the global data to establish a user relationship circle.
  • the conditions are similar to the previous one: people who have numbers (mutual contacts) can establish a relationship with the user relationship, and use this method to establish a contact list.
  • the user's number may be invalidated: in one case, the user is in a circle of friends, the name of the user is stored in a number of friends' contacts, and a different number is stored; another case It is the same number, which corresponds to different names in the two address books (that is, the user of the number changes), and the user corresponding to the two names in the address book may also have multiple numbers. In both cases, the associated number will be considered a potential expiration number. Of course, in order to avoid accidentally deleting the number that has not expired, some recovery mechanism will be used to prevent the user from deleting the number by mistake, and to support the recovery of the erroneously deleted number.
  • Identification of potential invalidation numbers There are several ways to identify whether a number has been used recently: for example, traffic SMS verification for various applications, recent instructions for using traffic correction are in use; or, if the mobile number has a binding application The number that is bound is largely in use; or, whether the number has a recent record of the call, and the call record is in use. Often the above troubleshooting steps can be used to find out if the corresponding number has been used recently, and if it is not used for a long time, it is regarded as the invalid number.
  • Time definition of the invalid number For example, the number that has not been used for 3 consecutive months is regarded as the invalid number, and the invalid label is put on the user's reference. It also shows the time the user has not used since the last time they were used. If the judgment condition is insufficient and the data is lacking, the invalid label will not be displayed if it cannot be judged.
  • the online platform After the offline platform calculates the invalid number, it will be imported into the online platform.
  • the online service can be used to quickly query and return the result of the invalid number in the address book to the user.
  • the data flow of the whole process is shown in Figure 9c.
  • User data (user's address book) is submitted to the distributed computing platform in the form of ciphertext data (guaranteed data security) to identify the invalid number, the invalid number is stored in the invalid number database, and the user is provided with the invalid number inquiry service.
  • ciphertext data guaranteed data security
  • the problem that the identification of a contact in the mobile phone address book has multiple numbers including the expired number is solved for the user, and the operation of the user to find the required number in the address book to dial or send the information is improved.
  • Efficiency avoiding the multiple attempts of dialing in this process, resulting in waste of time and effort; based on the embodiment of the present invention, it is possible to automatically identify a real and effective telephone number among multiple numbers of contacts for the user, and improve the communication of the user. s efficiency.
  • a scheme of using a relationship chain to find a user's failed telephone number is proposed. From the relationship chain, multiple numbers of contacts are found, and the invalid number is identified from these numbers. Integrate the user's communication data, and form a relationship chain from the relationship between the user and the contact, and The user in the tether calculates the time when the contact-related data is used synchronously to determine whether the number is used recently, or the unused time, and finds the expired number from the contact that has not been used for a long time, and displays Give the user a reference for the user to delete the invalid contact number.
  • the embodiment of the present invention describes a contact processing apparatus.
  • the contact processing apparatus shown in FIG. 10 includes:
  • the searching module 401 searches for any two address books in a plurality of address books to obtain a user with an associated relationship.
  • the building module 402 is configured to construct a relationship chain formed by users having an association relationship
  • the determining module 403 is configured to search for a shared user of the address book corresponding to each user in the relationship chain, compare the contact manners of the shared users, and obtain a contact manner that the comparison result meets the predetermined condition;
  • the screening module 404 is configured to analyze the characteristics of each contact mode that meets the predetermined condition, and select a contact mode that matches the preset feature as a failed contact mode.
  • the searching module 401 is configured to: search for a contact mode of the second user in the address book of the first user, and search for a contact mode of the first user in the address book of the second user; When both are found, it is determined that the first user and the second user have an association relationship.
  • the building module is specifically configured as:
  • a relationship chain is constructed based on the cascaded nodes by using any one of the users having the associated relationship as a node and other users having an associated relationship with any of the users as a cascade node.
  • the determining module 403 is specifically configured to: in the address book corresponding to each user in the relationship chain, search for users with the same contact mode, and compare the identifiers of users having the same contact mode; At the same time, it is determined that the same contact method is the contact method that meets the predetermined conditions.
  • the determining module 403 is specifically configured to: in the address book corresponding to each user in the relationship chain, search for users with the same contact mode, and the comparison has the same contact party. The identity of the user; when not the same, the same contact is determined to be the contact condition that meets the predetermined conditions.
  • the screening module 404 is specifically configured to parse the communication data indicating the first contact mode for information verification, and obtain the usage time that the first contact mode is used for information verification; when determining the usage time and current When the time difference of the time is greater than the first time threshold, the first contact mode is determined as the contact mode of the first user; wherein the first contact mode is any contact mode that meets the predetermined condition, and the first user has the first contact mode, And the user in the address book of the relationship chain.
  • the screening module 404 is specifically configured to: parse the communication data indicating that the second contact mode is used to associate the application;
  • the second contact mode is the contact contact mode of the second user; wherein the second contact mode is any contact mode that meets the predetermined condition, and the second user has The second contact, and the user in the address book of the relationship chain.
  • the screening module 404 is specifically configured to: parse the communication data indicating the third contact mode for communication, and obtain the communication time of the third contact mode; when determining the communication time of the third contact mode and the current When the time difference of the time is greater than the second time threshold, determining that the third contact mode is the third user's invalid contact mode; wherein the third contact mode is any contact mode that meets the predetermined condition, and the third user has the third contact mode, And the user in the address book of the relationship chain.
  • the determining module is further configured to:
  • the determining module is further configured to:
  • the embodiment of the present invention describes a contact processing apparatus.
  • the contact processing apparatus shown in FIG. 10 includes:
  • the searching module 401 searches for any two address books in a plurality of address books to obtain a user with an associated relationship.
  • the building module 402 is configured to construct a relationship chain formed by users having an association relationship
  • the determining module 403 is configured to search for a shared user of the address book corresponding to each user in the relationship chain, compare the contact manners of the shared users, and obtain a contact manner that the comparison result meets the predetermined condition;
  • the screening module 404 is configured to analyze the characteristics of each contact mode that meets the predetermined condition, and select a contact mode that matches the preset feature as a failed contact mode.
  • the searching module 401 is configured to: search for a contact mode of the second user in the address book of the first user, and search for a contact mode of the first user in the address book of the second user; When both are found, it is determined that the first user and the second user have an association relationship.
  • the module 402 is configured as follows:
  • a relationship chain is constructed based on the cascaded nodes by using any one of the users having the associated relationship as a node and other users having an associated relationship with any of the users as a cascade node.
  • the determining module 403 is specifically configured to: in the address book corresponding to each user in the relationship chain, search for users with the same contact mode, and compare the identifiers of users having the same contact mode; At the same time, it is determined that the same contact method is the contact method that meets the predetermined conditions.
  • the determining module 403 is specifically configured to: in the address book corresponding to each user in the relationship chain, search for users with the same contact mode, and compare the identifiers of users having the same contact mode; At the same time, determine the same contact method as the contact party that meets the predetermined conditions. formula.
  • the screening module 404 is specifically configured to parse the communication data indicating the first contact mode for information verification, and obtain the usage time that the first contact mode is used for information verification; when determining the usage time and current When the time difference of the time is greater than the first time threshold, the first contact mode is determined as the contact mode of the first user; wherein the first contact mode is any contact mode that meets the predetermined condition, and the first user has the first contact mode, And the user in the address book of the relationship chain.
  • the filtering module 404 is specifically configured to: parse the communication data indicating that the second contact mode is used to associate the application;
  • the second contact mode is the contact contact mode of the second user; wherein the second contact mode is any contact mode that meets the predetermined condition, and the second user has The second contact, and the user in the address book of the relationship chain.
  • the screening module 404 is specifically configured to: parse the communication data indicating the third contact mode for communication, and obtain the communication time of the third contact mode; when determining the communication time of the third contact mode and the current When the time difference of the time is greater than the second time threshold, determining that the third contact mode is the third user's invalid contact mode; wherein the third contact mode is any contact mode that meets the predetermined condition, and the third user has the third contact mode, And the user in the address book of the relationship chain.
  • the determining module 403 is further configured to:
  • Analyze communication data indicating communication records of different contact modes obtain the frequency of communication by each user in the address book using different contact methods, and identify in the address book; update the address book according to the update operation for the identifier in the address book Contact information for each user.
  • the determining module is further configured to: identify the invalid contact mode in the address book; and update the address book according to the operation of the invalid contact mode identified in the address book Contact information for each user.
  • the embodiment of the invention describes a computer readable medium, which may be a ROM (for example, a read only memory, a FLASH memory, a transfer device, etc.), a magnetic storage medium (for example, a magnetic tape, a disk drive, etc.), an optical storage medium (for example, a CD).
  • ROM read only memory
  • FLASH memory FLASH memory
  • magnetic storage medium for example, a magnetic tape, a disk drive, etc.
  • an optical storage medium for example, a CD.
  • computer-readable medium storing computer-executable instructions that, when executed, cause at least one processor to perform a contact processing method, For example, the contact processing method shown in FIG.
  • the sequential processing method is beneficial to a large number of communication. Record the batch contact identification invalid contact method; identify the invalid contact method in the address book;

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Signal Processing (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明公开一种联系方式处理方法及装置、存储介质；方法包括：在多个通信录中查找任意两个通讯录，得到具有关联关系的用户；构建具有关联关系的用户构成的关系链；查找所述关系链中各用户对应的通讯录的共有用户，对所述共有用户的联系方式进行比对，得到比对结果符合预定条件的联系方式；分析出各所述符合预定条件的联系方式的特征，并筛选出匹配预设特征的联系方式为失效联系方式。

Description

联系方式处理方法及装置、存储介质
相关申请的交叉引用
本申请基于申请号为201610377964.7、申请日为2016年5月31日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的内容在此引入本申请作为参考。
技术领域
本发明涉及通信技术，尤其涉及一种联系方式处理方法及装置、存储介质。
背景技术
随着通信技术特别是移动通信技术的发展，很多用户都使用过或正在使用多个联系方式，如手机号码、社交网络账号和电子邮箱等等，但就手机号码而言，相当用户也拥有两个或多个。
因而在通讯录中，针对同一个用户可能会存储有多个联系方式，以手机号码为例，通信录中针对同一用户的多个手机号码中一个或多个可能目前处于停机状态、或者已经被运营商回收易主，因而存在着失效号码(如停机或易主)，当需要打电话或发消息时，无法从该用户的多个号码中准确分辨出哪个或哪些号码是有效的，只能逐个尝试联系，如此，会耗费用户的时间和精力，降低通信效率。
发明内容
有鉴于此，本发明实施例期望提供一种联系方式处理方法及装置、存储介质，能够精确识别出通讯录中的失效联系方式，进而提高通信效率。
为达到上述目的，本发明实施例的技术方案是这样实现的：
第一方面，本发明实施例提供一种联系方式处理方法，包括：
在多个通信录中查找任意两个通讯录，得到具有关联关系的用户；
构建具有关联关系的用户构成的关系链；
查找所述关系链中各用户对应的通讯录的共有用户，对所述共有用户的联系方式进行比对，得到比对结果符合预定条件的联系方式；
分析出各所述符合预定条件的联系方式的特征，并筛选出匹配预设特征的联系方式为失效联系方式。
第二方面，本发明实施例提供一种联系方式处理装置，包括：
查找模块，配置为在多个通信录中查找任意两个通讯录，得到具有关联关系的用户；
构建模块，配置为构建具有关联关系的用户构成的关系链；
确定模块，配置为查找所述关系链中各用户对应的通讯录的共有用户，对所述共有用户的联系方式进行比对，得到比对结果符合预定条件的联系方式；
筛选模块，配置为分析出各所述符合预定条件的联系方式的特征，并筛选出匹配预设特征的联系方式为失效联系方式。
第三方面，本发明实施例提供一种联系方式处理装置，包括：
存储器，配置为存储可执行程序；
处理器，配置为通过执行所述存储器中存储的可执行程序时，实现本发明实施例提供的联系方式处理方法。
第四方面，本发明实施例提供一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现本发明实施例提供的联系方式处理方法。
本发明实施例具有以下技术效果：
1)将共有用户作为持有失效联系方式的潜在用户，对于共有用户而言，可以通过通讯录构建具有关联关系的用户的关系链，并通过对关系链中各用户的通讯录中查找实现，能够实现高效定位持有失效联系方式的潜在用户的技术效果。
2)通过查找共有用户的联系方式中符合预设条件的方式，能够迅速定位共有用户的联系方式中潜在的失效联系方式，能够实现高效定位潜在失效联系方式的技术效果。
3)对于潜在的失效联系方式，从失效联系方式所具有的特征的维度进行筛选，实现了对于失效联系方式精确定位的技术效果。
4)按照定位持有失效联系方式的潜在用户、从潜在用户的联系方式中定位潜在失效联系方式、并从潜在失效联系方式中定位失效联系方式的顺序，顺序化的处理方式有利于对大量通讯录进行批量化识别失效联系方式。
附图说明
图1为本发明实施例中联系方式处理方法的一个可选的应用场景示意图；
图2为本发明实施例中联系方式处理装置的一个可选的硬件结构示意图；
图3为本发明实施例中联系方式处理方法的一个可选的流程示意图；
图4为本发明实施例中基于图1实施联系方式处理方法的一个可选的示意图；
图5为本发明实施例中联系方式处理方法的另一个可选的流程示意图；
图6为本发明实施例中通讯录中标识失效联系方式前后的对照示意图；
图7为本发明实施例中通讯录中标识使用频繁程度信息前后的对照示意图；
图8a为本发明实施例中清理失效号码功能开关的一个可选的实现示意 图；
图8b为本发明实施例中清理失效号码功能开关的另一个可选实现示意图；
图8c为本发明实施例中一个联系人对应多个电话号码的一个可选示意图；
图8d为本发明实施例中识别失效号码功能开关的一个可选的实现示意图；
图8e为本发明实施例中清理失效号码的一个可选的界面示意图；
图9a为本发明实施例中确定失效电话号码的一个可选的流程示意图；
图9b为本发明实施例中联系人度数的一个可选的示意图；
图9c为本发明实施例中确定失效电话号码的一个可选的数据流向示意图；
图10为本发明实施例中联系方式处理装置的另一个可选的结构示意图。
具体实施方式
以下结合附图及实施例，对本发明进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。另外，以下所提供的实施例是用于实施本发明的部分实施例，而非提供实施本发明的全部实施例，在本领域技术人员不付出创造性劳动的前提下，对以下实施例的技术方案进行重组所得的实施例、以及基于对发明所实施的其他实施例均属于本发明的保护范围。
需要说明的是，在本发明实施例中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的方法或者装置不仅包括所明确记载的要素，而且还包括没有明确列出的其他要素，或者是还包括为实施方法或者装置所固有的要素。在没有更多限制的情况 下，由语句“包括一个……”限定的要素，并不排除在包括该要素的方法或者装置中还存在另外的相关要素(例如方法中的步骤或者装置中的单元)。例如，本发明实施例提供的联系方式处理方法包含了一系列的步骤，但是本发明实施例提供的联系方式处理方法不限于所记载的步骤，同样地，本发明实施例提供的联系方式处理装置包括了一系列模块，但是本发明实施例提供的联系方式处理装置不限于包括所明确记载模块，还可以包括为获取相关信息、或基于联系方式处理时所需要设置的模块/单元。
需要说明的是，本发明实施例所涉及的术语“第一”/“第二”/“第三”等仅仅是是区别类似的对象，不代表针对对象的特定排序，可以理解地，“第一”/“第二”/“第三”在允许的情况下可以互换特定的顺序或先后次序。应该理解“第一”/“第二”/“第三”区分的对象在适当情况下可以互换，以使这里描述的本发明的实施例能够以除了在这里图示或描述的那些以外的顺序实施。
对本发明实施例进行进一步详细说明之前，对本发明实施例中涉及的名词和术语进行说明，本发明实施例中涉及的名词和术语适用于如下的解释。
1)联系方式，能够通过信息技术与用户建立通信的信息，如电话号码、电子邮箱、社交网络账号等。
2)失效联系方式，与用户对应，即用户曾经使用，但是由于各种原因(如合约到期、违反服务使用条款等)主动或被动放弃使用的联系方式，使用该联系方式无法触达该用户，失效联系方式可能不再使用或被其他用户继续使用。
3)通讯录，存储于用户终端(如智能手机、笔记本电脑)的各种客户端(如拨号客户端、电子邮件客户端、社交客户端)中的、用于触达其他用户的联系方式的集合；通讯录使用用户标识(如名称、序列号)和通信 标识的数据结构记录。
4)终端，可以为智能手机、平板电脑、台式电脑、笔记本电脑、穿戴式设备(如智能手表)等能够支持有线或无线通信或支持各种用于通信的应用或社交软件的设备。
5)联系人，即任一用户的通讯录中记录的具有联系方式的用户，可以理解，本文中联系人与用户可以互换使用，不做具体区分。
本发明实施例记载联系方式处理方法及装置、存储介质，用于识别出通讯录中同一联系人的多个联系方式中的失效联系方式，例如，从同一用户的多个电话号码中识别出失效号码，从同一用户的多个电子邮箱中识别出失效电子邮箱，下文中为便于说明以联系方式为电话号码为例，但是本发明实施例并不排除其他类型的联系方式。
以联系方式处理装置设置在网络侧的服务器为例，参见图1示出的本发明实施例中联系方式处理方法的一个可选的应用场景示意图，涉及以下实体：支持通讯录的终端11、联系方式处理服务器12及网络13。
终端11与联系方式处理服务器12通过网络13进行数据交互，终端11可以为多个；当用户要给联系人李**打电话或发消息时，用户查询终端11的通讯录时，发现在通讯录中存储有对应于李**的三个电话号码，分别为电话号码1、电话号码2及电话号码3，但是，这3个号码中可能有失效号码(如停机或易主)，然而，相关技术中并不支持用户获知这3个号码中哪个是有效号码，用户只能逐个尝试拨打或联系，此过程中拨号的多次尝试将耗费用户过多的时间和精力，降低通讯录的使用效率，降低用户的通信效率。
需要说明的是，图1中示出的应用场景仅是本发明实施例记载的技术方案的一个可能的架构示例，其他应用场景可以包括图1未涉及的终端、或安装于终端上的用于通信的应用或社交软件等。本发明实施例记载的技 术方案可以应用于上述场景中，以解决相关技术存在的难以确定失效联系方式的问题。
图1中以联系方式处理装置设置在网络侧服务器为例进行说明，可以理解，联系方式处理装置可以根据实际实施需求设置各种终端中，就联系方式处理装置的硬件架构来说，参见图2，图2是本发明实施例提供的联系方式处理装置20的一个可选的硬件结构示意图，图2所示的联系方式处理装置20包括：至少一个处理器21、存储器22、至少一个通信接口24和用户接口23。联系方式处理装置20中的各个组件通过总线系统25耦合在一起。可理解，总线系统25用于实现这些组件之间的连接通信。总线系统25除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图2中将各种总线都标为总线系统25。
其中，用户接口23可以包括显示器、键盘、鼠标、轨迹球、点击轮、按键、按钮、触感板或者触摸屏等。
可以理解，存储器22可以是易失性存储器或非易失性存储器，也可包括易失性和非易失性存储器两者。本发明实施例描述的存储器22旨在包括但不限于这些和任意其它适合类型的存储器。
本发明实施例中的存储器22用于存储各种类型的数据以支持联系方式处理装置20的操作。这些数据的示例包括：用于在联系方式处理装置20上操作的任何计算机程序，如操作系统221和应用程序222；通讯录数据等。其中，操作系统221包含各种系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务。应用程序222可以包含各种应用程序，实现本发明实施例联系方式处理方法的程序可以包含在应用程序222中。
上述本发明实施例揭示的方法可以应用于处理器21中，或者由处理器21实现。处理器21可能是一种集成电路芯片，具有信号的处理能力。在实 现过程中，上述方法的各步骤可以通过处理器21中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器21可以是通用处理器、数字信号处理器(DSP，Digital Signal Processor)，或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。处理器21可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本发明实施例所公开的方法的步骤，可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于存储介质中，该存储介质位于存储器22，处理器21读取存储器22中的信息，结合其硬件完成前述联系方式处理方法的步骤。
在示例性实施例中，联系方式处理装置20可以被一个或多个应用专用集成电路(ASIC，Application Specific Integrated Circuit)、DSP、可编程逻辑器件(PLD，Programmable Logic Device)、复杂可编程逻辑器件(CPLD，Complex Programmable Logic Device)、现场可编程门阵列(FPGA，Field-Programmable Gate Array)、通用处理器、控制器、微控制器(MCU，Micro Controller Unit)、微处理器(Microprocessor)、或其他电子元件实现，用于执行前述的联系方式处理方法。
本发明实施例提供一种联系方式处理方法，可以用于识别出通讯录中联系人的失效联系方式如失效号码。参见图3，本发明实施例记载的联系方式处理方法包括以下步骤：
步骤101、获取用户的通讯录，通讯录包括用户的联系人的联系方式。
在本发明可实施例中，以联系方式处理装置设置在网络侧服务器为例，联系方式处理服务器从多个终端获取相应终端用户的通讯录，例如，开启/使用了通讯录同步功能的终端的通讯录可以被存储到网络侧，如云端服务器，联系方式处理服务器在获得各个用户的授权后，可以从网络侧获取这 些用户的通讯录；可选的，用户的授权的实现方式可以为：用户在通讯录同步功能中设置是否允许联系方式处理服务器获取用户的通讯录，若是则指示联系方式处理服务器获得用户的授权；反之未获授权；需要说明的是，联系方式处理服务器可以与网络侧为同一设备，也可以为不同的设备；这里，一个用户的通讯录可以包括该用户的联系人的名称和联系方式；其中，联系人的联系方式包括：电话号码、电子邮箱、通信地址和社交应用(例如微信、QQ)的用户身份凭证。
在本发明可选实施例中，以联系方式处理装置设置在终端为例，终端从多个终端获取多个用户的通讯录。例如，开启/使用了通讯录共享功能的用户的通讯录，可以定期或不定期地将通讯录同步到信任终端中，信任终端是指，通过预鉴权，互相开放数据/信息访问权限的终端。
步骤102、查找任意两个用户的通讯录，得到任意两个用户的通讯录中互为联系人的用户，基于互为联系人的用户的关联关系构建至少一个关系链。
这里，互为联系人的用户是基于通讯录而确定的具有关联关系的用户，互为联系人的两个用户的通讯录中分别包括对方用户的联系方式。
在本发明可选实施例中，查找任意两个用户的通讯录得到互为联系人的用户的一种可行的实现方式，以根据第一用户的通讯录、以及第二用户的通讯录，判断第一用户与第二用户是否具有关联关系为例：
步骤1021，分别获取第一用户的联系方式及第二用户的联系方式；这里，第一用户与第二用户为多个用户中的任意两个不同的用户；
步骤1022，在第一用户的通讯录中查找第二用户的联系方式；
步骤1023，在第二用户的通讯录中查找第一用户的联系方式。
即通过查找第一用户的通讯录以判定第一用户的通讯录是否包括第二用户的联系方式，及通过查找第二用户的通讯录以判定第二用户的通讯录 是否包括第一用户的联系方式，若确定均查找到时，即确定第一用户的通讯录包括第二用户的联系方式、且第二用户的通讯录包括第一用户的联系方式时，判定第一用户和第二用户互为联系人。
在本发明可选实施例中，基于互为联系人的用户构建至少一个关系链的一种可行的实现方式包括：以互为联系人的用户中的任一用户为节点、以与任一用户互为联系人的其它用户为级联节点，基于级联的节点构建关系链；假设第一用户和第二用户被判定为联系人，则以第一用户为节点、以第二用户为级联节点，基于级联的节点构建关系链。
举例来说，遍历查找上述多个用户中的任意两个用户，假设联系方式处理服务器总共获取了3个不同的用户，如用户A、用户B及用户C的通讯录，则需要执行以下操作：1)查找用户A、用户B的通讯录，判定用户A和用户B是否互为联系人；2)查找用户A、用户C的通讯录，判定用户A和用户C是否互为联系人；3)查找用户B、用户C的通讯录，判定用户B和用户C是否互为联系人；4)基于上述步骤1)至3)所确定的互为联系人的用户构建至少一个关系链；假设，用户A、B、C中任意两个用户均互为联系人，则用户A、B、C形成三角形的关系链，每个用户对应三角形的一个端点。
步骤103、基于关系链中各用户的通讯录确定相同联系人，对相同联系人在不同通讯录(即关系链中各用户的通讯录)中的联系方式进行比对，得到比对结果符合预定条件的联系方式。
在本发明可选实施例中，相同联系人是至少两个通讯录中所共有的用户，因此也可以称为共有用户，相同联系人可以通过比对用户标识(如用户名称、序列号等)或用户的联系方式进行比对的方式确定，即，对于两个通讯录，如果包括相同的用户标识，或包括相同的联系方式，则确定包括相同联系人。
例如，上述步骤103的一种可行的实现方式包括：查找关系链中各用户的通讯录中的各个联系人的名称和联系方式，查找关系链中各用户的通讯录中是否存在具有相同名称的目标联系人，若否，则流程结束；若是，则比对关系链中各用户的通讯录中目标联系人对应的联系方式，若联系方式不同，则在关系链中各用户的通讯录中，确定目标联系人对应的联系方式，作为符合预定条件的联系方式。
继续举例来说，对于用户A的通讯录1和用户B的通讯录2，如果均包括名称为“C”的用户，则继续比对用户C在通讯录1中的联系方式、以及在通讯录2中的联系方式，如果是不同的联系方式，设为联系方式1和联系方式2，则用户C在通讯录1中的全部联系方式(除了联系方式1，通讯录1中还可能包括其他的对应用户C的联系方式)、以及在通讯录2中的联系方式(除了联系方式2，通讯录2中还可能包括对应用户C的其他的联系方式)符合预定条件，是潜在的失效联系方式。
再例如，上述步骤103的另一种可行的实现方式包括：查找关系链中各用户的通讯录中的各个联系人的名称和联系方式，查找关系链中各用户的通讯录中是否存在具有相同联系方式的目标联系人，若否，则流程结束；若是，则比对关系链中各用户的通讯录中目标联系人对应的名称，若名称不同，则在关系链各用户对应的通讯录中，确定目标联系人的联系方式，作为符合预定条件的联系方式。
继续举例来说，对于通讯录1和通讯录2，如果均存在联系方式1(如某一电话号码)，则比对联系方式1在通讯录1中对应的用户，以及在通讯录2中对应的用户，如果是不同的用户，设为用户A和用户B，则用户A在通讯录1中的全部联系方式(除了联系方式1，通讯录1中还可能包括对应用户A的其他联系方式)、以及在通讯录2中的全部联系方式符合预定条件，是潜在的失效联系方式；同时，用户B在通讯录1中的全部联系方式、 以及在通讯录2中的全部联系方式(除了联系方式2，通讯录2中还可能包括对应用户B的其他联系方式)符合预定条件，是潜在的失效联系方式。
步骤104、基于符合预定条件的联系方式的通信数据，分析出各符合预定条件的联系方式的特征，筛选出匹配预设特征的联系方式为失效联系方式。
在本发明可选实施例中，对于筛选出的失效联系方式，可以在所属的通讯录中为相应的联系方式增加了新属性：失效联系方式；或者，对于未被识别为失效联系方式的联系方式，增加有效联系方式的属性，以此作为用户判断是否使用、修改或删除联系方式的依据之一。
例如，联系方式处理服务器识别出失效联系方式后，将筛选出的失效联系方式存储在联系方式处理服务器，例如将筛选出的失效联系方式写入专用于存储用户失效联系方式的记录表、或者存入用于存储通讯录的数据库，采用主动下发或被动请求的方式同步给终端。
在本发明可选实施例中，基于符合预定条件的联系方式的通信数据，分析出各符合预定条件的联系方式的特征，筛选出匹配预设特征的联系方式为失效联系方式的实现方式，可以包括以下方式的任意一种或组合：
方式1)
鉴于信息验证联系方式(例如，包括基于验证短信登录、用户应用注册等方式)是联系方式(特别是电话号码)的高频使用场景，当联系方式在长时间没有使用时，其为失效联系方式的可能性较高频使用的联系方式的可能性要高。
具体来说，基于表示联系方式用于信息验证方式的通信数据进行判断，解析各符合预定条件的联系方式的通信数据，确定各符合预定条件的联系方式被用于信息验证方式的使用时间(例如，最近一次用于通信的时间)，判断使用时间与当前时间的时间差是否大于第一时间阈值，若是，则判定 相应的联系方式为失效联系方式；否则，判定相应的联系方式为有效联系方式；这里，第一时间阈值可以由用户/联系人处理服务器基于历史数据、实际需求等进行设定。
此外，针对同一联系方式对应于至少两个联系人的情况，例如，同一电话号码被运营商回收易主的场景器不仅需要确定失效联系方式，还需要确定该失效联系方式对应于至哪一个用户的失效联系方式。
具体来说，对于任一符合预定条件的联系方式，设为第一联系方式，以及关系链中各用户的通讯录中具有该第一联系方式的用户，设为第一用户，解析表示第一联系方式用于信息验证的通信数据，得到第一联系方式被第一联系人用于信息验证方式的使用时间，判断使用时间与当前时间的时间差是否大于第一时间阈值，这里，第一时间阈值可以由用户/联系方式处理服务器基于历史数据、实际需求等进行设定，若是，则判定第一联系方式为第一联系人的失效联系方式；否则，判定第一联系方式为第一联系人的有效联系方式。
方式2)
联系方式与用户使用的各种应用(如支付应用、社交用于)绑定是联系方式的一个高频使用的场景，当联系方式没有任何应用绑定时，其为失效联系方式的可能性，较联系方式绑定有应用的可能性高。
解析各符合预定条件的联系方式的关联应用的通信数据，判断各符合预定条件的联系方式是否用作应用的关联联系方式，若否，则判定相应的联系方式为失效联系方式；若是，则判定相应的联系方式为有效联系方式。这里，关联应用数据可以包括联系方式与应用进行绑定；应用的关联联系方式，例如为联系方式被绑定为验证号码、以联系方式进行应用注册、将联系方式与应用的账号绑定等。
此外，针对同一联系方式对应于至少两个联系人的情况，例如，同一 电话号码被运营商回收易主的场景，不仅需要确定失效联系方式，还需要确定该失效联系方式对应于哪一个联系人。
具体来说，对于任一符合预定条件的联系方式，设为第二联系方式，以及关系链中各用户的通讯录中具有该第一联系方式的用户，设为第二用户，第二联系方式对应第二联系人的关联应用的通信数据，判断第二联系方式是否被用作第二联系人所使用应用的关联联系方式，若否，则判定第二联系方式为第二联系人的失效联系方式；若是，则判定第二联系方式为第二联系人的有效联系方式。
方式3)
鉴于联系方式的基础用途是用于用户的通信，当某一联系方式长时间未被用于通信时，其为失效联系方式的可能性增大。
解析第三联系方式的通信数据，判断确定各符合预定条件的联系方式的通信时间，判断通信时间与当前时间的时间差是否大于第二时间阈值，若是，则判定相应的联系方式为失效联系方式；否则，判定相应的联系方式为有效联系方式。举例来说，通信时间例如可以为最近一次的通信时刻(如最近一次收发短信、打电话或邮件的时刻)等；这里，第二时间阈值可以由用户/联系人处理服务器基于历史数据、实际需求等进行设定。
此外，针对同一联系方式对应于至少两个联系人的情况，例如，同一电话号码被运营商回收易主的场景，联系人处理服务器不仅需要确定失效联系方式，还需要确定该失效联系方式对应于哪一个联系人。
具体来说，对于任一符合预定条件的联系方式，设为第三联系方式，以及关系链中各用户的通讯录中具有该第三联系方式的用户，设为第三用户，解析第三联系方式对应第三联系人的通信记录的通信数据，得到第三联系方式的通信时间；判断第三联系方式的通信时间与当前时间的时间差是否大于第二时间阈值，若是，则判定第三联系方式为第三联系人的失效 联系方式；否则，判定第三联系方式为第三联系人的有效联系方式。
可以理解，上述的判断方式可以择一或者结合使用，例如，通过解析联系方式的通信数据，判断是否满足以下条件中的至少两个：使用时间与当前时间的时间差大于第一时间阈值；被用作应用的关联联系方式；通信时间与当前时间的时间差是否大于第二时间阈值。
另外，对于联系方式处理服务器识别失效联系方式的情况，在满足失效联系方式下发条件时，联系方式处理服务器可以向终端发送用户的通讯录中的失效联系方式，供终端在用户的通讯录中标识失效联系方式；当然，对于终端识别失效联系方式的情况，终端也可以在通讯录中标识失效联系方式。
示例性地，失效联系方式下发条件的实现方式可以包括以下任意一种或组合：
1)终端接收到用户触发的针对通讯录的失效号码清理操作时，向联系方式处理服务器发送用于管理用户的通讯录的请求；联系方式处理服务器响应于终端发送的用于管理用户的通讯录的请求，将用户的通讯录中的失效联系方式发送给终端。
2)终端接收到用户触发的针对通讯录中指定联系人的失效号码识别操作时，向联系方式处理服务器发送用于管理用户的通讯录中联系人的请求，该请求中携带指定联系人的名称或待识别联系方式；联系方式处理服务器响应于终端发送的用于管理用户的通讯录的请求，将用户的通讯录中的指定联系人的失效联系方式发送给终端。
3)周期性下发。
4)事件触发的主动下发，例如联系方式处理服务器检测到用户的通讯录中的失效联系方式的绝对数量或相对数量超过预设的数量门限。
联系方式处理服务器确定用户的通讯录中的失效联系方式的一种可行 的实现方式包括：联系方式处理服务器将用户的通讯录中各个联系人的联系方式，分别与上述筛选出的失效联系方式进行匹配，得到用户的通讯录中的失效联系方式；可选的，联系方式处理服务器将确定的用户的通讯录中的失效联系方式进行保存。
终端根据联系方式处理服务器发送的用户的通讯录中的失效联系方式，在用户的通讯录中标识失效联系方式；以供用户针对用户的通讯录中标识的失效联系方式进行操作，例如，用户将通讯录中标识的失效联系方式全部或部分删除，或者，用户将通讯录中标识为失效联系方式的部分或全部联系方式的标识取消，例如，用户确知被标识为失效联系方式的一个或多个联系方式其实是有效的联系方式。
用户针对用户的通讯录中标识的失效联系方式进行了操作之后，联系方式处理服务器响应于用户针对用户的通讯录中标识的失效联系方式的操作，更新网络侧中同步存储的用户的通讯录中失效联系方式；可选的，在用户将用户的通讯录中标识为失效联系方式的联系方式的标识取消时，联系方式处理服务器将从上述筛选出的失效联系方式中删除被取消标识的联系方式。
下面结合图1示出的应用场景，对本发明实施例记载的联系方式处理方法进行示例说明：参见图4示出的本发明实施例中基于图1所示的架构实施联系方式处理的一个可选的示意图，图4示出的联系方式处理方法包括：
步骤201、当终端11的终端用户想给李**打电话或发消息时，终端用户查询终端11的通讯录，发现在通讯录李**名下存储有3个电话号码，分别为电话号码1、电话号码2及电话号码3，此时，终端用户面对联系人李**对应的多个电话号码，不知道应该使用哪个电话号码。
步骤202、终端11检测到终端用户正在查询通讯录并停留在联系人李 **对应的信息页面，且终端11发现联系人李**对应有多个电话号码时，则向联系方式处理服务器12发送用于管理终端11的终端用户的通讯录的请求，该请求中携带联系人李**的名称，或者携带联系人李**对应的多个电话号码。
步骤203、联系方式处理服务器12根据联系人李**的名称，从预先确定的终端11的终端用户的通讯录的失效联系方式中查找到联系人李**的失效电话号码；或者，联系方式处理服务器12将终端用户的通讯录中李**对应的多个电话号码，与筛选出的失效联系方式进行匹配，确定李**的失效电话号码。这里，假设李**的失效电话号码为电话号码1及电话号码3。
步骤204、联系方式处理服务器12将李**的失效电话号码(电话号码1及电话号码3)发送至终端11。
步骤205、终端11根据联系方式处理服务器12发送的李**的失效电话号码(电话号码1及电话号码3)，在终端11的终端用户的通讯录中将李**对应的电话号码1及电话号码3分别标识为“失效”，从而识别出李**的失效电话号码(电话号码1及电话号码3)。
这样一来，终端用户可以直接选择没有被标识为失效的电话号码2给李**打电话或发消息，从而在避免用户对包括失效电话号码在内的多个号码逐个尝试拨打或联系的情况下，自动识别出通讯录中的失效号码，克服相关技术存在的耗费用户时间和精力，降低通讯录的使用效率，降低用户的通信效率的缺陷。
本发明实施例中，通过对基于互为联系人的终端用户构建的关系链中各终端用户的通讯录中的相同联系人的联系方式进行比对，筛选出符合预定条件的联系方式，并根据符合预定条件的联系方式的特征筛选出匹配预设特征的失效联系方式，即通过对多个终端用户的通讯录的联系人的联系方式进行分析，从所有联系方式中识别出失效联系方式，用户直接使用除 了失效联系方式之外的其他联系方式(即有效联系方式)进行通信，避免了相关技术中终端用户需要对包括失效联系方式在内的多个联系方式逐个尝试进行通信，从而节省了用户的时间和精力，如此，本发明实施例能够自动识别出通讯录中的失效号码，提高通讯录的使用效率，提高用户的通信效率。
本发明实施例针对终端接收到终端用户触发的清理通讯录中失效联系方式的操作指示时的处理方案进行示例说明。
参见图5，本发明实施例记载的联系方式处理方法可以由终端与联系方式处理服务器配合实施，方法包括以下步骤：
步骤301、终端检测终端用户针对通讯录的操作。
步骤302、终端检测到终端用户触发的针对通讯录中失效联系方式进行清理的操作指示时，向联系方式处理服务器发送用于获取通讯录中各联系人的失效联系方式的消息；该消息中包括终端用户的标识、联系方式或通讯录中所有的联系人的联系方式。
步骤303、联系方式处理服务器响应于终端用户发送的用于获取通讯录中各联系人的失效联系方式的消息，通过查询预先生成的数据库得到预先筛选确定的多个终端用户的失效联系方式，及将该终端用户的通讯录中各联系人的联系方式分别与预先筛选确定的多个终端用户的失效联系方式进行匹配，得到该终端用户的通讯录中各联系人的失效联系方式，或者通过查询预先生成的数据库得到预先确定的该终端用户的通讯录中各联系人的失效联系方式。
步骤304、联系方式处理服务器将得到的该终端用户的通讯录中各联系人的失效联系方式发送给该终端。
步骤305、终端根据联系方式处理服务器反馈的通讯录中各联系人的失效联系方式，将通讯录中相应的联系方式标识为失效联系方式，参见图6 示出的通讯录中各联系人的失效联系方式(图6中以电话号码举例)被标识前后的对照示意图，以供终端用户针对通讯录中被标识为失效联系方式的联系方式操作，例如，终端用户将通讯录中标识的失效联系方式全部或部分删除，或者，终端用户将通讯录中标识为失效联系方式的部分或全部联系方式的标识取消，例如，用户确知被标识为失效联系方式的一个或多个联系方式其实是有效的联系方式。
本发明实施例中，终端用户需要对通讯录的失效联系方式进行清理时，终端从终端服务器请求得到通讯录中各联系人的失效联系方式并在通讯录中标识出来，相当于为每个联系方式增加了新属性：失效联系方式、或有效联系方式(如通讯录中未标识为失效联系方式的联系方式)，以此作为用户判断是否使用、修改或删除联系方式的依据之一，节省用户的时间和精力，提高终端用户整理通讯录的准确性和效率。
本发明实施例针对用户希望在通讯录中标识出各联系人的不同联系方式的使用频繁程度信息的需求，提出解决的技术方案，具体包括：
联系方式处理服务器主动、或响应于终端发送的用于请求各联系人的不同联系方式的使用频繁程度信息的消息，基于终端用户的通讯录中各联系人的通信日志数据，确定终端用户的通讯录中各联系人使用不同的联系方式进行通信的使用频繁程度；这里，使用频繁程度可以包括常用、不常用等信息；
联系方式处理服务器向终端发送终端用户的通讯录中各联系人的不同联系方式的使用频繁程度信息。
终端在终端用户的通讯录中标识出各联系人的不同联系方式的使用频繁程度信息；这里，相当于为每个联系方式增加了新属性：常用、或不常用，以此作为用户判断是否使用、修改或删除联系方式的依据之一；需要说明的是，本发明实施例基于上述实施例，本发明实施例中的联系方式的 使用频繁程度信息(常用、不常用)，是指联系人使用联系方式进行通信(电话、短信、关联应用)的使用频繁程度；未被标注为失效(或被标注为有效)的联系方式可能被识别为常用，也可能被识别为不常用；参见图7示出的通讯录中各联系人的联系方式(以电话号码举例)被标注使用频繁程度信息前后的对照示意图，同时查看图6与图7就可以发现：
1)在图6中李**的电话号码2、钱**的电话号码7均未被标注为失效，以及，在图7中李**的电话号码2、钱**的电话号码7均被标注为常用；也就是说，李**的电话号码2、钱**的电话号码7均为有效且常用的电话号码；
2)在图6中张**的电话号码4、电话号码5均未被标注为失效，以及，在图7中张**的电话号码4被标注为常用，但是，张**的电话号码5被标注为不常用；也就是说，张**的电话号码4为有效且常用的电话号码，张**的电话号码5为有效但不常用的电话号码。
终端用户针对通讯录中标识的各联系人的不同联系方式的使用频繁程度信息的操作，例如，将通讯录中标识为不常用的联系方式删除，或者，将通讯录中标识为不常用的一个或多个联系方式的“不常用”标识取消，例如，用户确知被标识为“不常用”的一个或多个联系方式其实是真实有效且常用的联系方式；这里，终端用户也可以将被标注为“不常用”的联系方式作为失效联系方式进行清除，例如，终端用户可以基于通讯录中标识的各联系人的不同联系方式的使用频繁程度信息，清理通讯录中的失效联系方式。
联系方式处理服务器响应于终端用户针对通讯录中标识的各联系人的不同联系方式的使用频繁程度信息的操作，更新网络侧中同步存储的终端用户的通讯录中各联系人的不同联系方式；例如，更新相应联系方式的标识，或者将相应联系方式删除。
本发明实施例结合联系方式处理的实例，继续对联系方式处理的实现 过程进行说明。
1、通讯录客户端处理过程
a)操作界面
参见图8a，用户可在通讯录医生体检中检测出终端的通讯录中是否有失效号码，并提示用户进行整理；或者，
参见图8b，用户也可自行从通讯录整理模块进入，整理失效号码；或者，
参见图8c，用户从通讯录中查找联系人的电话号码时，面对联系人对应的多个电话号码，不知道应该使用哪一个？终端在显示有通信录中对应有多个电话号码的联系人(对应多个)的页面，增加指示标识失效号码的按钮或操作入口供用户选择，参见图8d，或者，终端在检测到用户从通讯录中查找对应有多个电话号码的联系人的信息时，主动提示用户终端正在识别联系人对应的多个电话号码中的失效号码，并将识别结果呈献给用户。
b)功能
根据云端服务器(如上述的联系方式处理服务器)分析后，将判断标签(识别结果)呈现给用户参见图8e，用户可自主选择是否对这些号码进行处理。
2、通讯录客户端的后台处理过程
失效电话号码的计算在后台分为离线计算部分和在线服务部分，由于处理的数据量很大，因此可以在分布式计算平台如Hadoop平台上进行离线计算，然后将离线计算的结果导入到存储中，在线服务处理用户请求的时候查询存储，有计算结果的部分返回给用户；参见图9a示出的失效电话号码计算流程。
首先需要将活跃用户的数据导入到分布式计算平台中。当用户使用通讯录同步功能，通讯录的后台会将该用户的联系人数据以日志的形式同步 到分布式计算平台(由于同步的数据涉及隐私，数据在分布式计算平台上的都以加密的方式存储)。
1)建立用户关系圈(即关系链)：
以当前用户为中心，将用户的通讯录中的联系人，如果用户和联系人的通讯录中存着对方的号码，那么可以将联系人建立为用户的1度联系人。对于所有1度联系人，依次取出他们通讯录当中的联系人，再建立1度联系人，此时，中心用户就有2度的用户关系圈，这些信息数据以用户->电话号码的形式导入到分布式计算平台。这里，联系人的度数具体为：如果两个用户互存了手机号码，那么称这两个用户互为1度联系人，如果两个用户之间都存在共同的1度联系人，那么称这两个用户互为2度联系人，以此类推。参见图9b，用户A与B和C分别是1度联系人，用户A与D是2度联系人，用户A与E是3度联系人。
离线部分建立用户关系圈的计算，离线部分使用Hadoop平台，在Hadoop平台建立联系人脉表即用户之间的关联关系，利用Hadoop的计算能力，可以在全局数据中建立用户关系圈，建立用户关系圈的条件与上一步相似：相互存有号码(互为联系人)的人可以建立用户关系圈关系，以此方法建立人脉表备用。
2)筛选出潜在的失效号码：
认为用户的号码可能是失效的有两种情况：一种情况是这个用户在朋友圈中，该用户的名字被多个朋友的通讯录中存有号码，并且存有不同号码；另一种情况是同一个号码，在2个通讯录中对应不同的名字(也就是号码的用户变化)，而通讯录中对应这2个名字的用户可能还对应有多个号码。这两种情况，相关的号码将被视为潜在的失效号码。当然为了避免将未失效的号码误删除的情况，但将使用一些恢复机制防止用户错删了号码，支持恢复误删除的号码。
潜在的失效号码的鉴定：使用多种方式来鉴定一个号码是否在最近被使用：例如，各种应用的流量短信验证，最近有使用流量校正的说明正在使用；或者，手机号码是否有绑定应用，有绑定的号码很大程度上正在使用；或者，该号码是否最近有通话的记录，有通话记录的正在使用。经常上述几个排查步骤，可以查出对应的号码是否最近使用过，如果很长时间未使用，则视为失效号码。
3)失效号码的时间界定：例如，将连续3个月内未使用过的号码视为失效号码，打上失效的标签，供用户参考。同时显示出用户离最近一次使用后未使用的时间。若因判断条件不足、数据缺乏，无法判断的则不显示失效标签。
4)结果导出&业务查询
离线平台计算失效号码之后，将导入到在线平台，使用在线服务的形式可以快速查询，将通讯录中是否存在失效号码的结果返回给用户；整个流程的数据流向如图9c所示。
用户数据(用户的通讯录)以密文数据(保证数据安全)的形式提交到分布式计算平台进行识别失效号码，失效号码在失效号码数据库存储，并向用户提供失效号码的查询服务。
上述示例中，通过大数据后台分析，为用户解决了识别手机通讯录中一个联系人有多个号码包含已失效号码的问题，提升了用户在通讯录中找到需要的号码拨打或发送信息的操作效率，规避了此过程中拨号的多次尝试导致时间和精力的浪费；基于本发明实施例，能实现自动为用户识别出联系人多个号码中真实有效且常用的电话号码，提升用户进行通信的效率。
上述示例中，提出使用关系链来寻找用户的失效电话号码的方案，从关系链中，找出联系人的多个号码，从这些号码中识别出失效号码。综合用户的通信数据，可以从用户与联系人之间的关系形成关系链，并针对关 系链中的用户，计算联系人相关数据被同步使用的时间，来判断号码是否在近期被使用，或者未使用的时长，从长时间未同步使用的联系人中寻找到已经失效的号码，展示给用户，以供用户参考是否删除失效的联系人号码。
本发明实施例记载一种联系方式处理装置，参见图10，图10示出的联系方式处理装置包括：
查找模块401，在多个通信录中查找任意两个通讯录，得到具有关联关系的用户
构建模块402，配置为构建具有关联关系的用户构成的关系链；
确定模块403，配置为查找关系链中各用户对应的通讯录的共有用户，对共有用户的联系方式进行比对，得到比对结果符合预定条件的联系方式；
筛选模块404，配置为分析出各符合预定条件的联系方式的特征，并筛选出匹配预设特征的联系方式为失效联系方式。
在本发明可选实施例中，查找模块401，具体配置为：在第一用户的通讯录中查找第二用户的联系方式，并在第二用户的通讯录中查找第一用户的联系方式；当均查找到时，确定第一用户和第二用户具有关联关系。
在本发明可选实施例中，构建模块，具体配置为：
以具有关联关系的用户中的任一用户为节点、以与任一用户具有关联关系的其它用户为级联节点，基于级联的节点构建关系链。
在本发明可选实施例中，确定模块403，具体配置为：在关系链中各用户对应的通讯录中，查找具有相同联系方式的用户，比对具有相同联系方式的用户的标识；当不同时，确定相同联系方式为符合预定条件的联系方式。
在本发明可选实施例中，确定模块403，具体配置为：在关系链中各用户对应的通讯录中，查找具有相同联系方式的用户，比对具有相同联系方 式的用户的标识；当不同时，确定相同联系方式为符合预定条件的联系方式。
在本发明可选实施例中，筛选模块404，具体配置为解析表示第一联系方式用于信息验证的通信数据，得到第一联系方式被用于信息验证的使用时间；当确定使用时间与当前时间的时间差大于第一时间阈值时，判定第一联系方式为第一用户的失效联系方式；其中，第一联系方式为任一符合预定条件的联系方式，第一用户为具有第一联系方式、且位于关系链的通讯录中的用户。
在上述实施例的基础上，筛选模块404，具体配置为：解析表示第二联系方式用于关联应用的通信数据；
当确定第二联系方式未作为应用的关联联系方式时，判定第二联系方式为第二用户的失效联系方式；其中，第二联系方式为任一符合预定条件的联系方式，第二用户为具有第二联系方式、且位于关系链的通讯录中的用户。
在本发明可选实施例中，筛选模块404，具体配置为：解析表示第三联系方式用于通信的通信数据，得到第三联系方式的通信时间；当确定第三联系方式的通信时间与当前时间的时间差大于第二时间阈值时，判定第三联系方式为第三用户的失效联系方式；其中，第三联系方式为任一符合预定条件的联系方式，第三用户为具有第三联系方式、且位于关系链的通讯录中的用户。
在本发明可选实施例中，确定模块，还配置为：
解析表示不同联系方式的通信记录的通信数据，得到通讯录中各用户使用不同的联系方式进行通信的频繁程度，并在通讯录中进行标识；
根据针对通讯录中标识的更新操作，更新通讯录中各用户的联系方式。
在本发明可选实施例中，确定模块，还配置为：
在通讯录中标识失效联系方式；
根据针对通讯录中标识的失效联系方式的操作，更新通讯录中各用户的联系方式。
本发明实施例记载一种联系方式处理装置，参见图10，图10示出的联系方式处理装置包括：
查找模块401，在多个通信录中查找任意两个通讯录，得到具有关联关系的用户
构建模块402，配置为构建具有关联关系的用户构成的关系链；
确定模块403，配置为查找关系链中各用户对应的通讯录的共有用户，对共有用户的联系方式进行比对，得到比对结果符合预定条件的联系方式；
筛选模块404，配置为分析出各符合预定条件的联系方式的特征，并筛选出匹配预设特征的联系方式为失效联系方式。
在本发明可选实施例中，查找模块401，具体配置为：在第一用户的通讯录中查找第二用户的联系方式，并在第二用户的通讯录中查找第一用户的联系方式；当均查找到时，确定第一用户和第二用户具有关联关系。
在本发明可选实施例中，构建模块402，具体配置为：
以具有关联关系的用户中的任一用户为节点、以与任一用户具有关联关系的其它用户为级联节点，基于级联的节点构建关系链。
在本发明可选实施例中，确定模块403，具体配置为：在关系链中各用户对应的通讯录中，查找具有相同联系方式的用户，比对具有相同联系方式的用户的标识；当不同时，确定相同联系方式为符合预定条件的联系方式。
在本发明可选实施例中，确定模块403，具体配置为：在关系链中各用户对应的通讯录中，查找具有相同联系方式的用户，比对具有相同联系方式的用户的标识；当不同时，确定相同联系方式为符合预定条件的联系方 式。
在本发明可选实施例中，筛选模块404，具体配置为解析表示第一联系方式用于信息验证的通信数据，得到第一联系方式被用于信息验证的使用时间；当确定使用时间与当前时间的时间差大于第一时间阈值时，判定第一联系方式为第一用户的失效联系方式；其中，第一联系方式为任一符合预定条件的联系方式，第一用户为具有第一联系方式、且位于关系链的通讯录中的用户。
在本发明可选实施例中，筛选模块404，具体配置为：解析表示第二联系方式用于关联应用的通信数据；
当确定第二联系方式未作为应用的关联联系方式时，判定第二联系方式为第二用户的失效联系方式；其中，第二联系方式为任一符合预定条件的联系方式，第二用户为具有第二联系方式、且位于关系链的通讯录中的用户。
在本发明可选实施例中，筛选模块404，具体配置为：解析表示第三联系方式用于通信的通信数据，得到第三联系方式的通信时间；当确定第三联系方式的通信时间与当前时间的时间差大于第二时间阈值时，判定第三联系方式为第三用户的失效联系方式；其中，第三联系方式为任一符合预定条件的联系方式，第三用户为具有第三联系方式、且位于关系链的通讯录中的用户。
在本发明可选实施例中，确定模块403，还配置为：
解析表示不同联系方式的通信记录的通信数据，得到通讯录中各用户使用不同的联系方式进行通信的频繁程度，并在通讯录中进行标识；根据针对通讯录中标识的更新操作，更新通讯录中各用户的联系方式。
在本发明可选实施例中，确定模块，还配置为：在通讯录中标识失效联系方式；根据针对通讯录中标识的失效联系方式的操作，更新通讯录中 各用户的联系方式。
本发明实施例记载一种计算机可读介质，可以为ROM(例如，只读存储器、FLASH存储器、转移装置等)、磁存储介质(例如，磁带、磁盘驱动器等)、光学存储介质(例如，CD-ROM、DVD-ROM、纸卡、纸带等)以及其他熟知类型的程序存储器；计算机可读介质中存储有计算机可执行指令，当执行指令时，引起至少一个处理器执行联系方式处理方法，例如图3示出的联系方式处理方法。
综上所述，本发明实施例具有以下技术效果：
1)按照定位持有失效联系方式的潜在用户、从潜在用户的联系方式中定位潜在失效联系方式、并从潜在失效联系方式中定位失效联系方式的顺序，顺序化的处理方式有利于对大量通讯录进行批量化识别失效联系方式；在通讯录中标识失效联系方式；
2)通过使用时间、信息验证以及应用关联的中的至少一个特征，从潜在的失效联系方式中精确识别失效联系方式；
3)支持用户对通讯录中的失效联系方式进行清理以更新通讯录。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (22)

  1. 一种联系方式处理方法，包括：
    在多个通信录中查找任意两个通讯录，得到具有关联关系的用户；
    构建具有关联关系的用户构成的关系链；
    查找所述关系链中各用户对应的通讯录的共有用户，对所述共有用户的联系方式进行比对，得到比对结果符合预定条件的联系方式；
    分析出各所述符合预定条件的联系方式的特征，并筛选出匹配预设特征的联系方式为失效联系方式。
  2. 根据权利要求1所述的方法，所述在多个通信录中查找任意两个通讯录，得到具有关联关系的用户，包括：
    在第一用户的通讯录中查找第二用户的联系方式，并在所述第二用户的通讯录中查找所述第一用户的联系方式；
    当均查找到时，确定所述第一用户和所述第二用户具有关联关系。
  3. 根据权利要求1所述的方法，其中，所述构建具有关联关系的用户构成的关系链，包括：
    以具有关联关系的用户中的任一用户为节点、以与所述任一用户具有关联关系的其它用户为级联节点，基于级联的所述节点构建所述关系链。
  4. 根据权利要求1所述的方法，其中，所述查找所述关系链中各用户对应的通讯录的共有用户，对所述共有用户的联系方式进行比对，得到比对结果符合预定条件的联系方式，包括：
    在所述关系链中各用户的通讯录中，查找具有相同标识的目标用户，比对所述目标用户的联系方式；
    当不同时，确定所述目标用户在所述关系链各用户的通讯录中对应的联系方式，作为所述符合预定条件的联系方式。
  5. 根据权利要求1所述的方法，其中，所述查找所述关系链中各用户 对应的通讯录的共有用户，对所述共有用户的联系方式进行比对，得到比对结果符合预定条件的联系方式，包括：
    在所述关系链中各用户对应的通讯录中，查找具有相同联系方式的目标用户，比对所述目标用户的标识；
    当不同时，确定所述目标用户在所述关系链中各用户对应的通讯录中对应的联系方式，作为所述符合预定条件的联系方式。
  6. 根据权利要求1所述的方法，其中，所述分析出各所述符合预定条件的联系方式的特征，并筛选出匹配预设特征的联系方式为失效联系方式，包括：
    解析表示第一联系方式用于信息验证的通信数据，得到所述第一联系方式被用于信息验证的使用时间；
    当确定所述使用时间与当前时间的时间差大于第一时间阈值时，判定所述第一联系方式为第一用户的失效联系方式；
    其中，所述第一联系方式为任一所述符合预定条件的联系方式，所述第一用户为具有所述第一联系方式、且位于所述关系链的通讯录中的用户。
  7. 根据权利要求要求1所述的方法，其中，所述分析出各所述符合预定条件的联系方式的特征，并筛选出匹配预设特征的联系方式为失效联系方式，包括：
    解析表示第二联系方式用于关联应用的通信数据；
    当确定所述第二联系方式未作为应用的关联联系方式时，判定所述第二联系方式为第二用户的失效联系方式；
    其中，所述第二联系方式为任一所述符合预定条件的联系方式，所述第二用户为具有所述第二联系方式、且位于所述关系链的通讯录中的用户。
  8. 根据权利要求要求1所述的方法，其中，所述分析出各所述符合预定条件的联系方式的特征，并筛选出匹配预设特征的联系方式为失效联系 方式，包括：
    解析表示第三联系方式的通信时间的通信数据，得到所述第三联系方式的通信时间；
    当确定所述第三联系方式的通信时间与当前时间的时间差大于第二时间阈值时，判定所述第三联系方式为第三用户的失效联系方式；
    其中，所述第三联系方式为任一所述符合预定条件的联系方式，所述第三用户为具有所述第三联系方式、且位于所述关系链的通讯录中的用户。
  9. 根据权利要求要求1所述的方法，其中，还包括：
    解析表示不同联系方式的通信记录的通信数据，得到所述通讯录中各用户使用不同的联系方式进行通信的频繁程度，并在所述通讯录中进行标识；
    根据针对所述通讯录中标识的更新操作，更新所述通讯录中各用户的联系方式。
  10. 根据权利要求要求1所述的方法，其中，还包括：
    在所述通讯录中标识所述失效联系方式；
    根据针对所述通讯录中标识的失效联系方式的操作，更新所述通讯录中各用户的联系方式。
  11. 一种联系方式处理装置，包括：
    查找模块，配置为在多个通信录中查找任意两个通讯录，得到具有关联关系的用户；
    构建模块，配置为构建具有关联关系的用户构成的关系链；
    确定模块，配置为查找所述关系链中各用户对应的通讯录的共有用户，对所述共有用户的联系方式进行比对，得到比对结果符合预定条件的联系方式；
    筛选模块，配置为分析出各所述符合预定条件的联系方式的特征，并 筛选出匹配预设特征的联系方式为失效联系方式。
  12. 根据权利要求11所述的装置，其中，
    所述查找模块，具体配置为：
    在第一用户的通讯录中查找第二用户的联系方式，并在所述第二用户的通讯录中查找所述第一用户的联系方式；
    当均查找到时，确定所述第一用户和所述第二用户具有关联关系。
  13. 根据权利要求11所述的装置，其中，
    所述构建模块，具体配置为：
    以具有关联关系的用户中的任一用户为节点、以与所述任一用户具有关联关系的其它用户为级联节点，基于级联的所述节点构建所述关系链。
  14. 根据权利要求11所述的装置，其中，
    所述确定模块，具体配置为：
    在所述关系链中各用户的通讯录中，查找具有相同标识的用户，比对所述具有相同标识的用户的联系方式；
    当不同时，确定所述目标用户在所述关系链各用户的通讯录中对应的联系方式，作为所述符合预定条件的联系方式。
  15. 根据权利要求11所述的装置，其中，
    所述确定模块，具体配置为：
    在所述关系链中各用户对应的通讯录中，查找具有相同联系方式的目标用户，比对所述目标用户的标识；
    当不同时，确定所述目标用户在所述关系链中各用户对应的通讯录中对应的联系方式，作为所述符合预定条件的联系方式。
  16. 根据权利要求11所述的装置，其中，
    所述筛选模块，具体配置为：
    解析表示第一联系方式用于信息验证的通信数据，得到所述第一联系 方式被用于信息验证的使用时间；
    当确定所述使用时间与当前时间的时间差大于第一时间阈值时，判定所述第一联系方式为第一用户的失效联系方式；
    其中，所述第一联系方式为任一所述符合预定条件的联系方式，所述第一用户为具有所述第一联系方式、且位于所述关系链的通讯录中的用户。
  17. 根据权利要求要求11所述的装置，其中，
    所述筛选模块，具体配置为：
    解析表示第二联系方式用于关联应用的通信数据；
    当确定所述第二联系方式未作为应用的关联联系方式时，判定所述第二联系方式为第二用户的失效联系方式；
    其中，所述第二联系方式为任一所述符合预定条件的联系方式，所述第二用户为具有所述第二联系方式、且位于所述关系链的通讯录中的用户。
  18. 根据权利要求要求11所述的装置，其中，
    所述筛选模块，具体配置为：
    解析表示第三联系方式的通信时间的通信数据，得到所述第三联系方式的通信时间；
    当确定所述第三联系方式的通信时间与当前时间的时间差大于第二时间阈值时，判定所述第三联系方式为第三用户的失效联系方式；
    其中，所述第三联系方式为任一所述符合预定条件的联系方式，所述第三用户为具有所述第三联系方式、且位于所述关系链的通讯录中的用户。
  19. 根据权利要求要求11所述的装置，其中，：
    所述确定模块，还配置为：
    解析表示不同联系方式的通信记录的通信数据，得到所述通讯录中各用户使用不同的联系方式进行通信的频繁程度，并在所述通讯录中进行标识；
    根据针对所述通讯录中标识的更新操作，更新所述通讯录中各用户的联系方式。
  20. 根据权利要求要求11所述的装置，其中，
    所述确定模块，还配置为：
    在所述通讯录中标识所述失效联系方式；
    根据针对所述通讯录中标识的失效联系方式的操作，更新所述通讯录中各用户的联系方式。
  21. 一种联系方式处理装置，包括：
    存储器，配置为存储可执行程序；
    处理器，配置为通过执行所述存储器中存储的可执行程序时，实现权利要求1至10任一项所述的联系方式处理方法。
  22. 一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现权利要求1至10任一项所述的联系方式处理方法。
PCT/CN2017/084032 2016-05-31 2017-05-11 联系方式处理方法及装置、存储介质 WO2017206696A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610377964.7 2016-05-31
CN201610377964.7A CN106095814B (zh) 2016-05-31 2016-05-31 联系人处理方法及服务器

Publications (1)

Publication Number Publication Date
WO2017206696A1 true WO2017206696A1 (zh) 2017-12-07

Family

ID=57230603

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/084032 WO2017206696A1 (zh) 2016-05-31 2017-05-11 联系方式处理方法及装置、存储介质

Country Status (2)

Country Link
CN (1) CN106095814B (zh)
WO (1) WO2017206696A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110417926A (zh) * 2018-04-28 2019-11-05 冯泽 联系建立方法、系统和计算机可读存储介质
CN113885954A (zh) * 2021-09-26 2022-01-04 湖南于一科技有限公司 检测微信通讯录中僵尸粉的方法、装置、设备及存储介质

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106095814B (zh) * 2016-05-31 2019-09-20 腾讯科技（深圳）有限公司 联系人处理方法及服务器
CN106682223B (zh) * 2017-01-04 2020-03-10 上海智臻智能网络科技股份有限公司 数据有效性检测方法及装置、智能交互方法及装置
CN106713676B (zh) * 2017-01-23 2019-08-06 北京安云世纪科技有限公司 通信号码识别控制方法、装置及通信终端
CN106850926B (zh) * 2017-02-21 2019-03-05 维沃移动通信有限公司 一种失效联系人处理方法、服务器及移动终端
CN107295118A (zh) * 2017-06-28 2017-10-24 西安万像电子科技有限公司 联系人查找方法和装置
CN110166637B (zh) * 2018-02-12 2021-07-23 深圳市六度人和科技有限公司 一种空号识别方法及装置
CN110198286A (zh) * 2018-02-24 2019-09-03 阿里巴巴集团控股有限公司 一种数据处理方法及计算设备
CN110851453B (zh) * 2018-08-01 2022-09-20 国网辽宁招标有限公司 一种项目通讯录动态的生成方法
CN111310538B (zh) * 2019-11-18 2020-11-17 万金芬 基于大数据服务器的内容管理系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102882953A (zh) * 2012-09-18 2013-01-16 李建成 通讯号码的同步方法和系统
CN103095884A (zh) * 2013-01-17 2013-05-08 东莞宇龙通信科技有限公司 一种联系人号码的处理方法及系统
CN104023108A (zh) * 2014-06-18 2014-09-03 中国联合网络通信集团有限公司 清除终端失效联系人的方法和装置
CN105141648A (zh) * 2014-06-09 2015-12-09 西安中兴新软件有限责任公司 一种通讯录更新方法和终端
CN106095814A (zh) * 2016-05-31 2016-11-09 腾讯科技（深圳）有限公司 联系人处理方法及服务器

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103781035A (zh) * 2014-01-10 2014-05-07 宇龙计算机通信科技(深圳)有限公司 一种基于移动终端的通讯联系处理方法及系统
CN104410694B (zh) * 2014-11-28 2017-11-28 东莞中国科学院云计算产业技术创新与育成中心 一种基于数据挖掘的云端通信录联系方式自主更新方法
CN104394258B (zh) * 2014-12-01 2018-05-01 广州三星通信技术研究有限公司 对通讯对象的联系方式变化进行处理的方法和装置
CN105357357A (zh) * 2015-10-14 2016-02-24 北京乐动卓越科技有限公司 电话号码管理方法和云端服务器

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102882953A (zh) * 2012-09-18 2013-01-16 李建成 通讯号码的同步方法和系统
CN103095884A (zh) * 2013-01-17 2013-05-08 东莞宇龙通信科技有限公司 一种联系人号码的处理方法及系统
CN105141648A (zh) * 2014-06-09 2015-12-09 西安中兴新软件有限责任公司 一种通讯录更新方法和终端
CN104023108A (zh) * 2014-06-18 2014-09-03 中国联合网络通信集团有限公司 清除终端失效联系人的方法和装置
CN106095814A (zh) * 2016-05-31 2016-11-09 腾讯科技（深圳）有限公司 联系人处理方法及服务器

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110417926A (zh) * 2018-04-28 2019-11-05 冯泽 联系建立方法、系统和计算机可读存储介质
CN113885954A (zh) * 2021-09-26 2022-01-04 湖南于一科技有限公司 检测微信通讯录中僵尸粉的方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN106095814A (zh) 2016-11-09
CN106095814B (zh) 2019-09-20

Similar Documents

Publication Publication Date Title
WO2017206696A1 (zh) 联系方式处理方法及装置、存储介质
TWI647583B (zh) Prompt method and prompting device for login account
US9743251B2 (en) Adding location names using private frequent location data
WO2018119587A1 (zh) 数据处理方法、装置、系统及信息采集设备
WO2015144058A1 (en) Account binding processing method, apparatus and system
US10536456B2 (en) Method and system for identifying user information in social network
US20200021963A1 (en) Communication Identifier Binding Processing Method and Terminal
US20150121491A1 (en) System and method of authenticating user account login request messages
CA2711279C (en) Social community generated answer system with collaboration constraints
EP3961448A1 (en) Method and system for detecting an infrastructure of malware or a cybercriminal
CN102968501A (zh) 一种通用的全文搜索方法
US11869014B2 (en) Physical proximity graphing
US11010484B2 (en) System and method to provide document management on a public document system
WO2021208461A1 (zh) 共享柜的物品更换方法、服务器及共享柜
US20130117768A1 (en) Web service api for unified contact store
WO2018219007A1 (zh) 数据查询系统中用户登录方法、电子设备及存储介质
CN111478894B (zh) 一种外部用户授权方法、装置、设备及可读存储介质
WO2016169438A1 (zh) 获取用户账号的方法和装置
JP2014235656A (ja) プログラム及び情報共有支援システム
US10033737B2 (en) System and method for cross-cloud identity matching
EP3089404A1 (en) Server and user group management method
WO2015062266A1 (en) System and method of authenticating user account login request messages
CN108540471B (zh) 移动应用网络流量聚类方法、计算机可读存储介质和终端
US20220327242A1 (en) Data management method and apparatus
CN116451210A (zh) 权限回收方法、装置、设备及存储介质

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 17805641

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17805641

Country of ref document: EP

Kind code of ref document: A1