WO2012155480A1

WO2012155480A1 - Method and device for searching contact information

Info

Publication number: WO2012155480A1
Application number: PCT/CN2011/082621
Authority: WO
Inventors: 陈军; 卢艳
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-08-17
Filing date: 2011-11-22
Publication date: 2012-11-22
Also published as: CN102957778B; CN102957778A

Abstract

Provided is a method and device for searching contact information, said method comprising: a sender client sends a request message to the clients of users in a contact list, wherein the request message carries a user identity of a target user and requests for the contact information of the target user; after receiving the request message, the receiver client checks, according to the user identity, whether there exists the target user in its own contact list. If not, said receiver client sends the request message to the clients of users in its own contact list and requests for the contact information of the target user. The present invention can search and obtain the contact information of the target user via contacts when the user can not directly obtain the contact information of the target user.

Description

Method and device for searching contact information

Technical field

The present invention relates to the field of communications technologies, and in particular, to a method and apparatus for searching for contact information.

Background technique

The theory of six divisions points out that there is no more than six people between each person and any stranger. That is to say, at most six people can know any stranger, and thus can build a huge social The internet.

In practice, in the current service based on the address book of the communication terminal, the user A can only obtain the contact information in the terminal address book, and cannot obtain the contact information other than the terminal address book. For example, the user A wants to obtain the terminal address book. The contact information of the user C other than the user C, even if the user C is a contact of the user B in the address book of the user A, the user A cannot obtain the contact information of the user C, and the contact information of the user C cannot be obtained through the user B. , can not extend User A's social network, reducing the user experience.

Summary of the invention

The technical problem to be solved by the present invention is to provide a method and device for searching for contact information, which can obtain contact information of a target user through an existing contact.

In order to solve the above technical problem, a method for searching for contact information of the present invention includes: a sender client sending a request message to a client of a user in the contact list, where the request message carries a user identifier of the target user, Requesting to obtain contact information of the target user;

After receiving the request message, the receiving client queries whether the target user exists in the contact list according to the user identifier, and if not, sends the user to the client of the user list in the contact list. The request message requests to obtain the contact information of the target user.

Preferably, the method further comprises:

If the recipient client queries the target user in its own contact list, the contact information of the target user is used as a return result, or the contact information or user identifier of the user is used. As a result of the return, and send the returned result.

Preferably, the receiver client includes an intermediate level receiver client and a last level receiver client;

After the last-level receiver client queries the target user, the return result is sent to the receiver client of the upper level;

After receiving the returned result, the intermediate-level receiver client sends the returned result to the receiver client or the sender client of the upper level.

Preferably, the method further comprises:

When the received result of the received client includes the contact information or the user identifier of the lower-level client, the intermediate-level receiver client adds its own contact information or user identifier to the returned result, and sends the returned result to the previous one. The recipient client of the level or the sender client enables the recipient client to obtain a path for obtaining contact information of the target user.

Preferably, the method further comprises:

When the sender client sends the request message to the client of the user in the contact list, the client also starts a counter for the client of the user in the contact list and counts the initial value;

When the receiving client does not query the target user in its own contact list, the counter is counted once, and when the count value reaches a deep threshold, the user is not sent to the client of the user in the contact list. Request message.

Preferably, when the count value does not reach the depth threshold, the receiver client sends the request message to the client of the user in the contact list of the user, and the client of the user in the contact list of the user The counter is started, and the count value of the local counter is assigned as the initial value of the count to the client of the user in the contact list of the user.

Preferably, the contact list is a locally stored contact list and/or a contact list stored on a web server.

An apparatus for searching for contact information, comprising: a sending unit, wherein:

The sending unit is configured to: send a request message to the client of the user in the contact list, where the request message carries the user identifier of the target user, and requests to obtain the contact information of the target user. Preferably, the method further includes a receiving unit and a query unit, wherein:

The receiving unit is configured to: receive a request message sent by a superior client;

The querying unit is configured to: after the receiving unit receives the request message, query, in the contact list, whether the target user exists in the contact list according to the user identifier, if not, send the sending unit to a lower level The client sends the request message.

Preferably, the querying unit is further configured to: when the target user is queried in the contact list, use the contact information of the target user as a return result, or use the contact information or the user identifier of the user as a return result, and The sending unit is called to send the returned result.

Preferably, the receiving unit is further configured to: receive a return result of the subordinate client, and add the contact information or the user identifier of the subordinate client when the return result includes the contact information or the user identifier of the subordinate client, The return result is sent by the sending unit to the client of the upper level.

Preferably, a counter control unit is further included, wherein:

The counter control unit is configured to: when the sending unit sends the request message to a client of the user in the contact list, start a counter for the client of the user in the contact list and assign an initial value; When the unit does not query the target user in the contact list, the counter counts the counter once, and when the count value reaches the depth threshold, the sending unit terminates sending the request message to the client of the user in the contact list.

In summary, in the embodiment of the present invention, when the user cannot directly obtain the contact information of the target user, the contact information of the target user may be searched and acquired through the contact. BRIEF abstract

1 is a flow chart of a method of searching for contact information of the present invention;

2 is a flow chart of an embodiment of acquiring other contact information of a target user according to the present invention;

3 is a flow chart of an embodiment of searching and sharing target user contact information of the present invention; and FIG. 4 is an architectural diagram of an apparatus for searching for contact information of the present invention. Preferred embodiment of the invention

Hereinafter, the present embodiment will be described in detail with reference to the drawings in conjunction with the embodiments. It should be noted that FIG. 1 is a method for searching for contact information in this embodiment, including:

Step 101: The sender client sends a request message to the client of the user in the contact list, where the request message carries the user identifier of the target user, and requests to obtain the contact information of the target user. For example, the user A needs to obtain the target user X. Contact information, contact information includes: phone number, email address and network ID (such as QQ number), etc., and user X is not in user A's contact list or buddy list, then user A can pass user A's contact The user in the list searches for user X. User A's client sends a request message to the user's client in its contact list to request the contact information of the target user X.

The contact list may be a contact stored locally by the client A of the user A, or may be a contact stored by the user A on the network. For example, the phone number of the contact is usually stored locally on the client, and the buddy list is communicated in time. Friends of social networks and common contact information of Email are often stored in the web server.

Assuming that user A's local and/or contact list in the network has users B, C, and D, the client of user A sends a request message to the clients of users B, C, and D, respectively, requesting to obtain the contact of user X. The user identifier of the user X is carried in the request message. The user identifier may be the user's name, nickname, and network user name. The user's geographic information (such as attribution information) may also be added to more accurately locate the target user.

The sender client can send a request message to the client of the user in the contact list at the same time or in batches according to its processing capability and network environment.

Step 102: The receiver client queries the contact list according to the user identifier of the target user to find whether the target user exists. If the target user exists, the contact information of the target user is returned to the sender client; otherwise, the receiver client continues to contact the contact. The client of the user in the list sends a request message, requests the contact information of the target user, and receives the returned result of the client of the user in the contact list, and returns the returned result to the sender client.

The receiver client includes an intermediate receiver client and a final receiver client; After the party client queries the target user, the return result is sent to the receiver client of the upper level; after receiving the return result, the intermediate client receives the return result and sends the return result to the receiver client of the upper level. Or the sender client.

The clients of the receivers B, C, and D respectively query whether there is a user X in the contact list in the local and/or network, and if yes, return the contact information of the user X, and end; otherwise, the receivers B, C, and D The client continues to send a request message to the client of the user in the local and/or contact list in the network, requests the contact information of the target user X, and receives the return result of the client of the user in the contact list, The result is returned and returned to User A's client.

In order to improve search efficiency, according to the six-degree segmentation theory, the depth of the search can be limited, such as searching for 3-6 levels. At this time, when the sender client sends the request message of the search target user to the receiver client, the receiver client starts a counter and counts the initial value, and when the receiver client sends the search request message to the next level, The counter is incremented by 1, and the count value is assigned as the initial value of the count to the receiver client of the next stage. When the count value of the counter reaches the limit value, the search is not performed to the next level.

In order to protect the privacy, the receiving client may not return the contact information of the searched target user directly to the sender client, and may return the contact information or the user identifier of the recipient client itself, and return the contact information or user identifier of the user. On the basis of this, it is also possible to return the user ID of the target user at the same time. In the scenario of multi-level search, the receiver client of the intermediate level adds its own contact information or user identifier to the return result of the client at the next level, so that the sender client can know the path of the contact information of the target user. It is convenient for the sender client to share the contact information of the target user in other ways through the obtained path.

Example 1

In this embodiment, after user A logs in to the social network, the friend X is offline, but user A wants to contact friend X in time, and user A does not know any other contact information of X.

2 is a flow chart of user A contacting user X in this embodiment. As shown in FIG. 2, the method includes the following steps:

Step 201: When the user A cannot contact the user X, the client of the user A sends a request message to the client of the online friend (referred to as the recipient client in the following step), requesting the contact information of the user X; Step 202: The receiving client queries whether there is another contact mode of the target user in the contact list, and if yes, returns the contact information of the target user to the sending client; otherwise, the receiving client continues to the contact list. The client of the user sends a request message, obtains the contact information of the target user, and receives the returned result of the user of the user in the contact list, returns the result and returns the sender client, repeats the step until the target user is searched. Or reach the limit of search depth.

Example 2:

In the fused address book service, after the user A searches for the user X on the server, the user A fails to apply for the contact information of the user X to the server. In this case, the user A can obtain the contact information of the user X by using the method of the embodiment. .

FIG. 3 is a flowchart of the embodiment. In this embodiment, the process of user A subscribing to user X mainly includes the following steps:

Step 301: The user A initiates a request for subscribing to the target user X to the server through the client. Step 302: When the subscription is unsuccessful, the client of the user A sends the client to the user in the contact list (hereinafter referred to as the recipient in the following step) Sending a request message, the request message is used to request the contact information of the search target user X; Step 303, the receiver client queries whether there is a target user in the contact list, and if there is a target user, returns the user's own information to the sender client. Contact information or user identification; otherwise, the recipient client continues to send a request message for searching the target user contact information to the client of the user in the contact list, and receives the return result of the user of the user in the contact list, Returning the result, adding its own contact information or user ID, and returning the returned result to the sender client; if the target user is searched, user A initiates a contact sharing request by returning the path in the result, requesting to share the contact information of the target user X. .

For example, user A's contacts have users B and C, user C subscribes to user D (ie, user D is the contact of user C), and user D subscribes to user X. User B cannot find user X, user C finds user D, and user D finds user X. Then user A's client initiates a contact sharing request to user D's client to request shared user X. Contact information of the user D; or the client of the user A obtains the contact information of the user D through the client sharing of the user C, and then The client sharing of user D obtains the contact information of user X.

4 is an apparatus for searching for contact information in the embodiment, including: a sending unit, a receiving unit, a query unit, and a counter control unit, where:

The sending unit is configured to send a request message to the client of the user in the contact list, and carry the user identifier of the target user in the request message, requesting to obtain the contact information of the target user.

a receiving unit, configured to receive a request message sent by a superior client;

The query unit is configured to: after the receiving unit receives the request message, query the contact list according to the user identifier to check whether there is a target user, if not, call the sending unit to send a request message to the lower-level client; query in the contact list When the target user is reached, the contact information of the target user is used as a return result, or the contact information or the user identifier of the user is used as a return result, and the sending unit is called to send the returned result.

The receiving unit is further configured to receive a return result of the lower-level client, and when the return result includes the contact information or the user identifier of the lower-level client, add the contact information or the user identifier to the returned result, and send the returned result to the upper unit through the sending unit. Level 1 client.

a counter control unit, configured to: when the sending unit sends the request message to the client of the user in the contact list, start a counter for the user of the user in the contact list and count the initial value; the query unit does not query in the contact list When the target user is reached, the counter is counted once, and when the count value reaches the deep threshold, the sending unit is terminated to send a request message to the client of the user in the contact list.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

In the embodiment of the present invention, when the user cannot directly obtain the contact information of the target user, the contact information of the target user may be searched for and obtained by the contact person.

Claims

Claim

1. A method for searching for contact information, including:

The sender client sends a request message to the client of the user in the contact list, where the request message carries the user identifier of the target user, and requests to obtain the contact information of the target user;

2. The method according to claim 1, further comprising:

If the receiving client queries the target user in its own contact list, the contact information of the target user is used as a return result, or the contact information or the user identifier of the user is used as a return result, and the sending Return the result.

3. The method of claim 2, wherein

The receiver client includes an intermediate-level receiver client and a last-party receiver client; after the last-party receiver client queries the target user, the return result is sent to the upper-level receiver. Party client

4. The method of claim 3, further comprising:

5. The method of claim 3, further comprising:

When the sender client sends the request message to the client of the user in the contact list, the sender client starts a counter and assigns an initial value to the client of the user in the contact list; When the receiving client does not query the target user in its own contact list, the counter is counted once, and when the count value reaches a deep threshold, the user is not sent to the client of the user in the contact list. Request message.

6. The method of claim 5, wherein

When the count value does not reach the depth threshold, the receiver client sends the request message to the client of the user in the contact list of the user, and starts a counter for the client of the user in the contact list of the user. The count value of the local counter is assigned as the initial value of the count to the client of the user in its own contact list.

7. The method of claim 1, wherein the contact list is a locally stored list of contacts and/or a list of contacts stored on a web server.

8. A device for searching for contact information, comprising: a sending unit, wherein:

The sending unit is configured to: send a request message to the client of the user in the contact list, where the request message carries the user identifier of the target user, and requests to obtain the contact information of the target user.

The device of claim 8, further comprising a receiving unit and a querying unit, wherein: the receiving unit is configured to: receive a request message sent by the upper client;

10. The apparatus according to claim 9, wherein

The query unit is further configured to: when the target user is queried in the contact list, use the contact information of the target user as a return result, or use the contact information or the user identifier of the user as a return result, and invoke the The sending unit transmits the returned result.

11. The apparatus according to claim 10, wherein

The receiving unit is further configured to: receive a return result of the subordinate client, and add the contact information or the user identifier of the subordinate client when the returned result includes the self in the return result The contact information or the user identifier is sent by the sending unit to the client of the upper level.

12. The apparatus according to claim 10, further comprising a counter control unit, wherein: the counter control unit is configured to: when the sending unit sends the request message to a client of a user in a contact list, And starting a counter for the user of the user in the contact list and counting the initial value; when the query unit does not query the target user in the contact list, counting the counter once, when the count value reaches the depth threshold, Terminating the sending unit to send the request message to the client of the user in the contact list.