CN110035004B

CN110035004B - User name card sharing method, friend adding method and related device

Info

Publication number: CN110035004B
Application number: CN201910319328.2A
Authority: CN
Inventors: 陈晓波; 叶波; 林莉; 李斌
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-04-19
Filing date: 2019-04-19
Publication date: 2021-03-02
Anticipated expiration: 2039-04-19
Also published as: CN110035004A

Abstract

The embodiment of the application discloses a user business card sharing method. The first user account shares the user name card with the target account, so that the user name card sharing function among heterogeneous systems is realized, a user among the heterogeneous systems can add friends through the shared user name card, direct network social contact of the user account among the heterogeneous systems is realized, the user can meet the network social contact requirement of cross-social contact software without downloading various social contact software, and the user experience is improved.

Description

User name card sharing method, friend adding method and related device

Technical Field

The application relates to the field of data processing, in particular to a user business card sharing method, a friend adding method and a related device.

Background

With the development of internet technology, more and more users perform social contact through a network, and social contact software is a carrier for supporting the social contact behavior, so that the users can perform network social contact through user accounts registered on the social contact software.

The social software circulating in the market at present is various in types, and different types of social software can be regarded as different heterogeneous systems.

However, the current social software does not provide a sharing function of the user account between heterogeneous systems, so that some users must install multiple social software to meet their social networking needs, and the operation burden of the users is increased.

Disclosure of Invention

In order to solve the technical problems, the application provides a user business card sharing method, a friend adding method and a related device, so that a user business card sharing function among heterogeneous systems is achieved, a user among the heterogeneous systems can add friends through shared user business cards, direct network social contact of user accounts among the heterogeneous systems is achieved, the user can meet network social contact requirements of cross-social contact software without downloading various social contact software, and user experience is improved.

The embodiment of the application discloses the following technical scheme:

in a first aspect, an embodiment of the present application discloses a method for sharing a user name card, where the method includes:

the first user account acquires a user name card of a shared user account; the shared user account belongs to a first heterogeneous system;

the first user account displays a target user selection interface, and acquires a target account through a selection operation triggered on the target user selection interface; the target account belongs to a second heterogeneous system;

and the first user account shares the user business card with the target account.

In a second aspect, an embodiment of the present application discloses a user business card sharing device, the device includes a first obtaining unit, a display unit, a second obtaining unit and a sharing unit:

the first obtaining unit is used for obtaining a user name card of a shared user account; the shared user belongs to a first heterogeneous system through an account;

the display unit is used for displaying a target user selection interface; the second obtaining unit is used for obtaining a target account through a selection operation triggered on the target user selection interface; the target account belongs to a second heterogeneous system;

the sharing unit is used for sharing the user business card with the target account.

In a third aspect, an embodiment of the present application discloses a method for adding a friend, including:

a target user account belonging to a second heterogeneous system acquires a user name card shared by a first user account, wherein the shared user account belongs to the first heterogeneous system;

the target user account initiates a friend adding request to the shared user account according to the user name card;

and the target user account acquires notification information sent from the first heterogeneous system, wherein the notification information is used for identifying that the friend adding request is pushed to the shared user account.

In a fourth aspect, an embodiment of the present application discloses a device for adding a friend, where the device includes a first obtaining unit, a sending unit, and a second obtaining unit:

the first obtaining unit is used for obtaining a user name card shared by a first user account, and the shared user account belongs to a first heterogeneous system;

the sending unit is used for initiating a friend adding request to the shared user account according to the user business card;

the second obtaining unit is configured to obtain notification information sent from the first heterogeneous system, where the notification information is used to identify that the friend adding request is pushed to the shared user account.

In a fifth aspect, an embodiment of the present application discloses an apparatus, which includes a processor and a memory:

the memory is used for storing program codes and transmitting the program codes to the processor;

the processor is configured to perform the method of any of the first or third aspects in accordance with instructions in the program code.

In a sixth aspect, an embodiment of the present application discloses a computer-readable storage medium for storing program code for executing the method of any one of the first aspect or the third aspect.

According to the technical scheme, if the first user account wishes to share the shared user account in the first heterogeneous system with the target account in the second heterogeneous system, the first user account can display a target user selection interface and obtain the target account through selection operation triggered on the target user selection interface, the first user account can share the user name card with the target account, so that a user name card sharing function among the heterogeneous systems is achieved, a user among the heterogeneous systems can add friends through the shared user name card, direct network social contact of the user accounts among the heterogeneous systems is achieved, the user can meet network social contact requirements of cross-social contact software without downloading various social contact software, and user experience is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.

Fig. 1 is an exemplary diagram of an application scenario of a user business card sharing method according to an embodiment of the present application;

fig. 2 is a flowchart of a user business card sharing method according to an embodiment of the present application;

FIG. 3a is an exemplary diagram of a user business card provided by an embodiment of the present application;

FIG. 3b is an exemplary diagram of a target user selection interface provided by an embodiment of the present application;

FIG. 4a is an exemplary diagram of a sharing relationship chain provided by an embodiment of the present application;

FIG. 4b is an exemplary diagram of a sharing relationship chain provided by an embodiment of the present application;

FIG. 5a is an exemplary diagram of a first identifier provided by an embodiment of the present application;

FIG. 5b is an exemplary diagram of a first identifier provided by an embodiment of the present application;

FIG. 6 is a diagram illustrating example information in business card information provided in an embodiment of the present application;

FIG. 7 is a diagram illustrating an effect of jumping from the social software 1 to the social software 2 according to an embodiment of the present application;

FIG. 8 is a diagram illustrating an effect of jumping from social software 1 to social software 2 according to an embodiment of the present application;

fig. 9 is an exemplary diagram of an application scenario of a method for adding a friend according to an embodiment of the present application;

fig. 10 is a flowchart of a method for adding a friend according to an embodiment of the present application;

fig. 11 is an effect diagram of a request for adding a friend initiated by a target user account according to an embodiment of the present application;

fig. 12 is a diagram illustrating an effect that a shared user account agrees to add a target user account as a friend according to an embodiment of the present application;

fig. 13 is an architecture diagram of communication between the social software 1 and the social software 2 through an interworking background according to an embodiment of the present application;

fig. 14 is a flowchart of a method for sharing a business card and adding a friend by a user according to an embodiment of the present application;

fig. 15a is a structural diagram of a user business card sharing apparatus according to an embodiment of the present application;

fig. 15b is a structural diagram of a user business card sharing device according to an embodiment of the present application;

fig. 16a is a structural diagram of a device for adding a friend according to an embodiment of the present application;

fig. 16b is a structural diagram of a device for adding a friend according to an embodiment of the present application;

FIG. 17 is a block diagram of an apparatus provided in an embodiment of the present application;

fig. 18 is a block diagram of a server according to an embodiment of the present application.

Detailed Description

Embodiments of the present application are described below with reference to the accompanying drawings.

Because the current social software does not provide a sharing function of the user account between the heterogeneous systems, some users can realize the network social requirements only by installing various social software, and the operation burden of the users is increased.

In order to solve the technical problem, an embodiment of the present application provides a user business card sharing method, which is mainly used for user business card sharing across systems. The method can be applied to terminal equipment, and the terminal equipment can be a Personal Computer (PC), an intelligent terminal, a Personal Digital Assistant (PDA), a tablet computer and the like.

The terminal equipment is provided with the social software belonging to different heterogeneous systems, and the social software belonging to different heterogeneous systems can be installed on the same terminal equipment or different terminal equipment. The social software may include enterprise WeChat, QQ, and the like, and the embodiments of the present application will be mainly described by taking as examples that the social software belonging to different heterogeneous systems is social software 1 and social software 2, respectively.

The user business card sharing method provided by the embodiment of the application can be applied to the application scene shown in fig. 1. In the scenario shown in fig. 1, a first user account wishes to share a shared user account in the first heterogeneous system 101 with a target account in the second heterogeneous system 102. The first heterogeneous system 101 and the first heterogeneous system 102 are different heterogeneous systems, that is, the social software to which the target account belongs is different from the social software to which the shared user account belongs. Common social software enterprises are heterogeneous systems with different WeChat, WeChat and QQ, and in the following embodiments, the first heterogeneous system 101 is the social software 1, and the second heterogeneous system 102 is the social software 2.

The first user account and the shared user account are both user accounts. The target account may be a user account or a group account.

In order to enable the first user account to share the shared user account with the target account, the first user account may display a target user selection interface, and the first user account may perform a selection operation on the target user selection interface. The first user account acquires the target account through a selection operation triggered on the target user selection interface, so that the user business card is shared with the target account. The user business card sharing function between the heterogeneous systems is achieved, so that the user between the heterogeneous systems can add friends through the shared user business cards, direct network social contact of the user account between the heterogeneous systems is achieved, the user can meet the network social contact requirement of cross-social contact software without downloading various social contact software, and user experience is improved.

Next, taking the first heterogeneous system as social software 1 and the second heterogeneous system as social software 2 as examples, the user business card sharing method provided by the embodiment of the present application will be described with reference to the drawings.

Referring to fig. 2, fig. 2 shows a signaling interaction diagram of a user business card sharing method, where the method includes:

s201, the first user account obtains a user business card of the shared user account.

The shared user account belongs to a first heterogeneous system (e.g., social software 1). In this embodiment, the first user account and the shared user account are in a friend relationship, or the first user account is the shared user account.

According to the difference of the relationship between the first user account and the shared user account, the manner of acquiring the user business card of the shared user account by the first user account may include multiple manners. If the first user account and the shared user account are in a friend relationship, in a possible implementation manner, a user corresponding to the first user account may find the shared user account through a friend list of the user, and the first user account may acquire a user name card of the shared user account by clicking a "name card" option in the shared user account.

If the first user account is a shared user account, in a possible implementation manner, the first user account may obtain a user business card in a personal information page (e.g., my in WeChat), so that the user business card of the first user account is shared in the second heterogeneous system.

Of course, besides the first user account and the second user account having the above relationship, so as to obtain the user business card, the first user account may also obtain the user business card of the shared user account shared or forwarded by other user accounts in the chat interface, for example, the first user account belongs to the first heterogeneous system, the user business card is shared in the user group where the first user account is located, and then the first user account may obtain the user business card of the shared user account in the user group including the first user account. For example, the first user account may share the user's business card with the target account by long-press selection. Referring to fig. 3a, the user business card may include profile information of the shared user account, for example, a user name (such as XXX in fig. 3 a), an avatar, description information (such as a company name), an identity, and the like corresponding to the shared user account.

It should be noted that, in some cases, the user business card further includes a target resource, and the target resource is used to increase the probability that the user business card is clicked in the target account.

The target resources can include a plurality of red packets, lucky dials and the like, for example, a certain amount, so that when the target account acquires the user name card, the target resources can be displayed to the target account, the target account is attracted to click the user name card, and the probability that the user name card is clicked in the target account is improved.

S202, the first user account displays a target user selection interface, and acquires the target account through a selection operation triggered on the target user selection interface.

Wherein the target account belongs to a second heterogeneous system (e.g., social software 2). Target user selection interface referring to fig. 3b, fig. 3b includes an option of "send user business card to social software 2", and the selection operation triggered by the first user account on the target user selection interface may be triggered by the first user account clicking on the option of "send user business card to social software 2".

It should be noted that the execution sequence of S201 and S202 is not limited in this embodiment.

And S203, the first user account shares the user business card with the target account.

It can be understood that the first user account may share the user business card with the target account according to the identity of the target account, so that the target account may add the shared user account as a friend through the user business card.

It should be noted that the user business card shared among the heterogeneous systems may exist in the form of two-dimensional code data, and since the two-dimensional code data may be shared at will and the two-dimensional code data does not limit which accounts can add the sharee as friends, it may cause that if the two-dimensional code corresponding to the user business card of the sharee is spread maliciously among different accounts, the possibility that the sharee is disturbed by an unfavorable adding request is greatly increased, and a poor sharing experience is caused to the sharee.

For example, a user account 1 in the heterogeneous system a wants to add a user account 2 (a shared person) in the heterogeneous system b, the user account 2 shares a two-dimensional code corresponding to a user business card of the user account 2 with the user account 1 through the user account 3, and the user account 2 and the user account 3 have a friend relationship. The user account 1 obtains the user name card of the user account 2 by scanning the two-dimensional code, and then the user name card is triggered to add the user account 2 as a friend. If the user account 1 can further push the two-dimensional code corresponding to the user business card of the user account 2 to the relationship chain where the two-dimensional code is located, each user account in the relationship chain can further push the two-dimensional code corresponding to the user business card of the user account 2 to other relationship chains, and so on. All the user accounts included in the relationship chain of the pushed two-dimensional code can initiate addition requests to the user account 2, and the addition requests disturb great troubles for the user account 2 and cause poor sharing experience for the user account 2.

In this case, in order to avoid annoyance of the shared user by an unsuspecting addition request, in a possible implementation manner, the user name card shared by the first user account is specifically name card information, the name card information includes a sharing relationship chain for sharing relationship information between accounts related to the user name card, the sharing relationship chain may embody that the first user account and the shared user account are a friend relationship, a relationship between the first user account and the target account, which user account the user name card belongs to (for example, belongs to the shared user account), and which account the user name card is shared by (for example, the first user account is shared with the target account).

The business card information acquired by the target account number comprises a first identifier determined according to the sharing relation chain. Because the first identifier is used for identifying that the target account has the authority of adding friends to the shared user account, the business card information shared to the target account can only be used for a specific user account, that is, only the user account identified by the target account or group members in a group identified by the target account can have the authority of adding friends to the shared user account. Therefore, after the target account adds friends to the shared user account, other accounts cannot use the business card information to add the shared user account as friends even if the business card information is spread to other accounts maliciously because other accounts do not have the authority limited by the first identifier. Therefore, the possibility that the shared person such as the shared user account is disturbed by an unfortunate adding request is basically avoided, and the sharing experience is improved. It should be noted that the first user account shares the user business card with the target account, may be the first user account directly shares the user business card with the target account, or the first user account forwards the user business card to the target account through another user account, and indirectly shares the user business card with the target account. If the first user account directly shares the user business card with the target account, the related account can comprise a user account (the first user account) sharing the user business card, a user account (a shared user account) to which the user business card belongs, and an account (the target account) to which the user business card is shared; if the first user account indirectly shares the user business card with the target account, the related accounts can include the user account sharing the user business card, the user account to which the user business card belongs, the user account transferring the user business card and the target account.

The sharing relationship chain not only comprises the accounts related to the user business card, but also comprises relationship information for identifying the relationship between the related accounts. The relationship between the related accounts may include a friend relationship, an account binding relationship, and the like, for example, the first user account and the shared user account are in a friend relationship, the first user account and a user account transferring the user name card are in an account binding relationship, and the first user account and the target account are in a friend relationship.

If the first user account directly shares the user business card with the target account, the sharing relationship chain is as shown in fig. 4 a. WW _ b represents the identity of the account of the shared user, i.e. the name card of the user belongs to the account b in the social software 1 identified by WW _ b; from _ openid: WW _ a represents the identifier of the first user account, to _ openid: WX _1 represents the identifier of the target account, account a and account b in the social software 1 are in a friend relationship, and account a in the social software 1 and account 1 in the social software 2 are in a friend relationship.

If the first user account indirectly shares the user business card with the target account, the sharing relationship chain is as shown in fig. 4 b. As shown in fig. 4b, taking account a in the social software 1 to share account b in the social software 1 with account 2 in the social software 2 through account 1 in the social software 2 as an example, WW _ openid represents an identifier of a shared user account, that is, the user business card belongs to account b in the social software 1 identified by WW _ b; from _ openid, WW _ a, WX _1 and WW _ a are in a binding relationship, account a and account b in social software 1 are in a friend relationship, and account a in social software 1 and account 1 in social software 2 are in a friend relationship.

The sharing relation chain can be used for generating the first identification according to the sharing chain when the user business card is shared by the target account, and the addition of the account of the shared user as a friend account is limited. The legality of the user account of the user name card can be checked according to the sharing chain, and the user name card is prevented from being spread maliciously by an illegal user account. In addition, when the target user account sends a request for adding friends to the shared user account, the legality of the target user account can be verified according to the sharing chain, and the phenomenon that an illegal user account disturbs the shared user account is avoided.

The business card information can be represented by CardInfo, the business card information acquired by the target account includes a first identifier determined according to the sharing relationship chain, and the first identifier is used for identifying that the target account has the authority of adding friends to the shared user account. The first identifier may be represented by a ticket, and the first identifier may be a plaintext, and in some cases, in order to avoid tampering the first identifier, the first identifier may be encrypted to obtain an encrypted ticket, and specifically, the encrypted ticket may be generated with the target account as a key.

Taking the shared user account as an account b in the social software 1 as an example, the first identifier may be shown in fig. 5a and 5 b. Fig. 5a shows that a first identifier corresponding to a shared user account is shared with a target account (for example, account 2 in social software 2), where from _ username: WX _2 represents an identifier of a user account that initiates a request for adding a friend, and to _ username: WW _ b represents which account is desired to be added as a friend, where the first identifier identifies that the target account WX _2 has a right to add a friend to the shared user account WW _ b. Fig. 5b shows that the first identifier corresponding to the shared user account is shared with the group corresponding to the target account, where from _ username, group openid, indicates the identifier of the group where the user account initiating the request for adding a friend is located, and to _ username, WW _ b, indicates which account is desired to be added as a friend, and the first identifier identifies that the group member in the target group account has the right to add a friend to the shared user account WW _ b.

It should be noted that, in one possible implementation, the business card information is obtained by: first, a first user account generates a sharing request for sharing a user business card to a target account, wherein the sharing request comprises a sharing relation chain. Then, the first user account acquires the business card information created according to the sharing request.

It should be noted that, in a possible implementation manner, a user corresponding to the first user account triggers a user business card function of sharing the shared user account, so as to trigger the first user account to generate the sharing request.

For example, the second heterogeneous system is the social software 2, after the first user account acquires the user business card of the shared user account, the user corresponding to the first user account triggers the first user account to generate the sharing request by clicking "send to the social software 2" in fig. 3a and "send the user business card to the social software 2" in fig. 3 b.

It should be noted that the manner of acquiring the business card information created according to the sharing request by the first user account may include many ways. One way for the first user account to obtain the business card information created according to the sharing request may be that the first user account obtains the business card information from the first user account according to the business card information created by the sharing request.

Another way for the first user account to obtain the business card information created according to the sharing request may be that the first user account sends the sharing request to an interworking system, and an interworking system (imuion) creates the business card information according to the obtained sharing request, so as to send the business card information to the first user account, where the interworking system has data processing logics of the first heterogeneous system and the second heterogeneous system, and the business card information created by the interworking system according to the sharing request conforms to the data processing logics of the first heterogeneous system and the second heterogeneous system. At this time, the first identification in the business card information may be added by the interworking system.

It can be understood that the information included in the business card information can be converted into a data format recognizable by both the first heterogeneous system and the second heterogeneous system through the interworking system, for example, the user identifier is converted into a universal openid, and the openid can be recognized by both the first heterogeneous system and the second heterogeneous system.

In some cases, the business card information may further include profile information of the shared user account. The data information included in the business card information may be as shown in fig. 6, where name represents a user name, headurl represents a head portrait, openid represents an identifier of a user account, and desc (corporate, etc.) identifier description information, such as a company name.

It should be noted that, because the heterogeneous system in which the first user account is located has a corresponding background, in a possible implementation manner, the first user account may send the sharing request to the interworking system through the background of the heterogeneous system in which the first user account is located. Taking the heterogeneous system where the first user account is located as the social software 1 as an example, the first user account may send the sharing request to the interworking system through the background of the social software 1.

According to the technical scheme, if a first user account wishes to share a shared user account in a first heterogeneous system with a target account in a second heterogeneous system, the first user account can display a target user selection interface and acquire the target account through selection operation triggered on the target user selection interface, the first user account can share business card information with the target account, the business card information comprises a sharing relation chain for sharing relation information between accounts related to a business card of a user, when the target account acquires the business card information, the business card information comprises a first identifier determined according to the sharing relation chain, and the first identifier is used for identifying that the target account has the right of adding friends to the shared user account. Due to the limitation of the first identifier, the business card information shared by the target account can only be used for a specific user account, for example, the target account adds friends to the shared user account, even if the business card information is spread to other accounts maliciously, other accounts cannot add the shared user account as a friend by using the business card information because other accounts do not have the limitation of the first identifier, so that the possibility that the shared user account, for example, the shared user account is disturbed by an unfavorable adding request is basically avoided, and the sharing experience is improved.

It should be noted that the method provided by the embodiment of the present application may include multiple user business card sharing scenarios, and five scenarios will be mainly introduced next.

The first scenario is that a first user account belongs to a first heterogeneous system, a target account is a target user account, an account binding relationship or a friend relationship exists between the target user account and the first user account, and the first user account directly shares a shared user account with the target user account. For example, an account a in the social software 1 shares an account b in the social software 1 with an account 1 in the social software 2, the account a in the social software 1 is a first user account, the account b in the social software 1 is a shared user account, and the account 1 in the social software 2 is a target account.

The second scenario is that a first user account belongs to the first heterogeneous system, the target account is a target user account, an account binding relationship is formed between a second user account belonging to the second heterogeneous system and the first user account, and the first user account shares the shared user account with the target user account through the second user account. For example, account a in social software 1 shares account b in social software 1 with account 2 in social software 2 through account 1 in social software 2. The account a in the social software 1 is a first user account, the account b in the social software 1 is a shared user account, the account 1 in the social software 2 is a second user account, and the account 2 in the social software 2 is a target account.

The third scenario is that the first user account belongs to a second heterogeneous system, the target account is a target user account, a friend relationship is formed between the target user account and the first user account, and the first user account directly shares the shared user account with the target user account. For example, account 1 in social software 2 shares account b in social software 1 to account 2 in social software 2. The account 1 in the social software 2 is a first user account, the account b in the social software 1 is a shared user account, and the account 2 in the social software 2 is a target account.

The fourth scenario is that the first user account belongs to a first heterogeneous system or a second heterogeneous system, the target account is a target group account, the first user account is a group member in a group corresponding to the target group account, and the first user account directly shares the shared account with the target group account corresponding to the group in which the first user account is located. For example, an account a in the social software 1 shares an account b in the social software 1 with a group of the social software 2 including the account a, where the account a in the social software 1 is a first user account, the account b in the social software 1 is a shared user account, and a group account corresponding to a group in the social software 2 including the account a is a target group account. Or the account 1 in the social software 2 shares the account b in the social software 1 with a group in the social software 2 including the account 1, where the account 1 in the social software 2 is a first user account, the account b in the social software 1 is a shared user account, and a group account corresponding to the group in the social software 2 including the account 1 is a target group account.

In a fifth scenario, the first user account belongs to the first heterogeneous system, the target account is a target group account, a second user account belonging to the second heterogeneous system and the first user account are in an account binding relationship, the second user account is a group member in a group corresponding to the target group account, and the first user account shares the shared user account with the target group account corresponding to the group in which the second user account is located through the second user account. For example, an account a in the social software 1 shares an account b in the social software 1 with a group where the account 1 is located through an account 1 in the social software 2, where the account a in the social software 1 is a first user account, the account b in the social software 1 is a shared user account, the account 1 in the social software 2 is a second user account, and a group account corresponding to the group where the account 1 is located is a target group account.

The first scene, the third scene and the fourth scene belong to a first user account and directly share a shared user account with a target account, so that the sharing relationship chain shows which user account the user name card belongs to, which user account the user name card is shared with, and also shows that the shared user account is in a friend relationship with the first user account, the first user account is in a friend relationship or an account binding relationship with a user account identified by the target account, or the first user account is a group member in a group identified by the target account. Under these scenarios, the first heterogeneous system to which the shared user account belongs and the second heterogeneous system to which the target account belongs may be installed on the same terminal device, or may be installed on different terminal devices. At this time, the first identifier in the business card information may be added by the first user account.

The second scenario and the fifth scenario belong to a situation that a first user account indirectly shares a user business card with a target account, namely the first user account shares a shared user account with the target account through a second user account, the first user account directly shares the user business card with the second user account, and the second user account forwards the user business card to the target account. Therefore, the sharing relationship chain represents the identifier of which user account the user name card belongs to, the user name card is shared by which user account to the target account, the account number used for forwarding the user name card to the target account is which account number, and the sharing relationship chain also represents the account number binding relationship between the shared user account and the first user account as a friend relationship, between the first user account and the second user account, and the like.

Under the scenes, because the second user account and the first user account are in an account binding relationship, when the first user account shares the user business card with the second user account, the first user account needs to jump to a second heterogeneous system from the first heterogeneous system, and the jump is performed among applications (such as social software), so that the first heterogeneous system to which the shared user account belongs and the second heterogeneous system to which the target account belongs need to be installed on the same terminal device.

It should be noted that, the first identifier in the business card information is different according to different sharing scenarios of the business card of the user, and the opportunity of generating the first identifier is different. In the first scenario, the third scenario and the fourth scenario, the sharing relationship chain represents which user account the user business card belongs to, and the user business card is shared to which account by which user account, that is, the shared user account, the first user account and the target account are represented, so that business card information shared by the first user account to the target account includes the first identifier.

In the second scenario and the fifth scenario, the business card information acquired by the first user account may not include the first identifier yet, but the first identifier is generated in the process that the first user account shares the business card information with the target account, so that the business card information acquired by the target account is ensured to include the first identifier. In this case, one possible implementation manner for the first user account to share the business card information with the target account is that the first user account shares the business card information with the second user account, so that the second user account obtains the first identifier according to a sharing relationship chain included in the business card information, and shares the business card information carrying the first identifier with the target user account or a target group account corresponding to a group where the first user account is located.

Under these scenarios, because the first heterogeneous system to which the shared user account belongs and the target account belong are installed on the same terminal device, one implementation manner for the first user account to share the business card information with the second user account may be that the first user account calls an interface of the second heterogeneous system through the first heterogeneous system, and forwards the business card information, which is encapsulated into a data format conforming to the interface, to the second user account. And jumping from the first heterogeneous system to the second heterogeneous system on the terminal equipment by calling an interface of the second heterogeneous system, so that the business card information is forwarded to the second user account.

The interface may be a Software Development Kit (SDK) interface, and the SDK interface provides data encapsulation and parsing capability to meet different data type delivery requirements (such as text, pictures, video, files, chat records, etc.). When a first user account in a first heterogeneous system wants to transmit certain data (such as business card information) to a second user account in a second heterogeneous system, the first user account encapsulates the data into a data format conforming to the interface, and transmits the data to the second user account in a form of binary data through openURL direct-carrying data or a mode of pasting board uipanel shared data. And the second user account reads data from the openURL or UIPasteboard, analyzes and converts the data into a text data type, and then distributes the text data type to a corresponding ApiHandler interface for subsequent processing.

In this embodiment, if the first user account belongs to the social software 1, the target account belongs to the social software 2, and the target account is the target user account, an effect graph obtained by jumping from the social software 1 to the social software 2 is shown as 701 in fig. 7, and an effect graph obtained by sharing the business card information with the target user account is shown as 702 in fig. 7; if the first user account belongs to the social software 1, the target account belongs to the social software 2, and the target account is a target group account, an effect diagram of jumping from the social software 1 to the social software 2 is shown as 801 in fig. 8, and an effect diagram of sharing business card information to the target group account is shown as 802 in fig. 8.

It should be noted that, in order to avoid that the business card information is acquired by an illegal user account, before the first user account sends the business card information to the second user account, whether the second user account and the first user account are in an account binding relationship may be verified through the second heterogeneous system, and if yes, the business card information is sent to the second user account.

Next, how the second user account obtains the first identifier according to the sharing relationship chain included in the business card information will be introduced.

After the second user account receives the business card information, a user corresponding to the second user account can select a target account, so that a first identifier is requested to be generated. The first identifier may be generated by the second user account according to the sharing relationship chain, or may be generated by sending the business card information to the second heterogeneous system background for application.

If the second user account sends the business card information to the second heterogeneous system background for applying to generate the first identifier, in order to avoid the business card information being intercepted by an illegal user, after the second user account sends the business card information to the second heterogeneous system background, the second heterogeneous system background can firstly check whether the second user account is in account binding relationship with the first user account, and if so, requests the IMUnion to generate the first identifier.

Taking the shared user account as an account WW _ b in the social software 1, the target account as an account WX _2 in the social software 2, and the second user account as an account WX _1 in the social software 2 as an example, after the business card information is shared with WX _1, the social software 2 side may analyze to obtain the business card information (cardlnfo), then, the user selection corresponding to WX _1 is forwarded to WX _2, and WX _1 may send the cardlnfo to a background application of the social software 2 to generate a first identifier that WX _2 has a right to add a friend to WW _ b. The background of the social software 2 will first check whether the bind _ openid of cardlnfo is the currently logged WX _1, and if not (if yes, WX _3), will generate a failed message to be inserted into the chat session between WX _1 and WX _ 3; if it is WX _1, the IMUnion background is requested to generate the first identity.

It should be noted that, in some cases, a second user account may have a need of desiring to add a shared user account as a friend, and in order to ensure that the shared user account may be added as a friend through name card information after the second user account acquires name card information, in some possible implementation manners, the name card information shared by the first user account to the target account may further include a second identifier determined according to the sharing relationship chain, where the second identifier is used to identify that the second user account has a right to add a friend to the shared user account.

The purpose of sharing the user business card of the shared account with the target account by the first user account is to enable the user account identified by the target account or a group member in a group identified by the target account to add the shared user account as a friend, and then, a method for adding a friend is introduced on the basis of the foregoing embodiment.

The method for adding the friend provided by the embodiment of the application can be applied to terminal equipment, and the terminal equipment can be a Personal Computer (PC), an intelligent terminal, a Personal Digital Assistant (PDA), a tablet computer and the like.

The method for adding friends provided by the embodiment of the application can be applied to the application scene shown in fig. 9. In the scenario shown in fig. 9, the target user account in the second heterogeneous system 102 wants to be a friend by adding the shared user account in the first heterogeneous system 101. The first heterogeneous system 101 and the first heterogeneous system 102 are different heterogeneous systems, that is, the social software to which the target user account belongs is different from the social software to which the shared user account belongs. In the following embodiments, the first heterogeneous system 101 is social software 1, and the second heterogeneous system 102 is social software 2.

The method comprises the steps that a target user account and a shared user account are both user accounts, in order to achieve the purpose that the target user account adds the shared user account as a friend, the target user account obtains a user name card shared by a first user account, a friend adding request is initiated to the shared user account according to the user name card, if the friend adding request can be pushed to the shared user account, the target user account obtains notification information sent by a first heterogeneous system, and the notification information is used for identifying that the friend adding request is pushed to the shared user account.

Next, a method for adding a friend provided in the embodiment of the present application will be described with reference to the drawings.

Referring to fig. 10, fig. 10 is a signaling interaction diagram illustrating a method of adding a buddy, the method comprising:

s1001, the target user account belonging to the second heterogeneous system obtains the user business card shared by the first user account.

The shared user account belongs to a first heterogeneous system.

S1002, the target user account initiates a friend adding request to the shared user account according to the user business card.

After the target user account acquires the user business card, the user business card may include the data information of the shared user account, and the target user account may directly view the data information.

If the target user account and the shared user account are not in a friend relationship, the target user account may initiate a request for adding a friend to the shared user account. An effect diagram of a target user account initiating a request for adding a friend through a user business card is shown in fig. 11, where a user corresponding to the target user account triggers the target user account to initiate a request for adding a friend by clicking a "add to address list" button in 1101 and a "send" button in 1102.

It should be noted that, in a possible implementation manner of S1002, the target user account initiates a request for adding a friend to the shared user account through the first heterogeneous system, where 1002 in fig. 10 is shown as the implementation manner.

And S1003, the first heterogeneous system sends notification information to the target user account.

The notification information is used for identifying that the friend adding request is pushed to the shared user account.

And after receiving the notification message, the target user account waits for the shared user account to agree to add the target user account as a friend. If the shared user account agrees to add the target user account as the friend, the shared user account sends an addition success message, the target user account obtains addition success information, the addition success information is used for identifying that the shared user account adds the target user account as the friend according to the friend adding request, and then the target user account adds the shared user account into a friend relationship list. As shown in fig. 12, an effect diagram that the shared user account agrees to add a target user account as a friend is shown, a user corresponding to the shared user account clicks a "pass verification" button in 1201, so as to trigger sending of an addition success message, a display interface after adding of a friend is completed is shown as 1202, and the shared user account and the target user account which are friends of each other can perform message intercommunication, such as message sending and voice call.

It should be noted that, because the user business card may be diffused among different account numbers, in order to avoid that the shared user is disturbed by an unsuspecting addition request, and improve the sharing experience, in a possible implementation manner, the user business card is specifically business card information, and the business card information includes a first identifier, and the first identifier is used for identifying that the target account number has an authority to add a friend to the shared user account number.

Correspondingly, the request for adding a friend further includes the first identifier, so that if the first heterogeneous system receives the request for adding a friend, the first heterogeneous system may verify the target user account through the first identifier, and if the target user account is determined to be the user account identified by the target account or a group member in a group identified by the target account, execute the step S1003.

It should be noted that, if the first identifier is an encrypted first identifier, the interworking system may decrypt the business card information through the first identifier, so that the first heterogeneous system verifies the target user account.

It should be noted that the business card information may be intercepted by an illegal user account in the sharing process, so as to tamper the business card information, for example, a target account identified in the real business card information is the account WX _2 in the social software 2, and if the business card information is intercepted by an illegal user account (for example, the account WX _3 in the social software 2), the account WX _3 in the social software 2 tamper the target account into the account WX _3 in the social software 2 in order to add a shared user account (for example, the account WW _ b in the social software 1) as a friend.

In this case, in order to avoid that an illegal user account can add a shared user account as a friend, in a possible implementation manner, the request for adding a friend further includes a name card identifier of the name card information, and the name card information further includes a sharing relation chain for sharing information about relationships between accounts related to user name cards of the shared user account, so that before S1003, the first heterogeneous system and the second heterogeneous system can verify whether the target user account is a legal user account according to the sharing relation chain, and if the target user account is verified to be a legal user account, the step of S1003 is executed. The first heterogeneous system and the second heterogeneous system are used for verifying that the sharing relation chain of the legal user account is determined according to the name card identification.

For example, the first heterogeneous system may verify whether the first user account and the shared user account are in a friend relationship; the first heterogeneous system or the second heterogeneous system can verify whether the first user account and the target user account are in a friend relationship or not according to the sharing relationship chain, or whether the first user account and the target user account are in the same group or not; the first heterogeneous system can verify whether the first user account and the second user account are in a binding relationship according to the sharing relationship chain; the second heterogeneous system may verify whether the target user account and the second user account are in a friend relationship according to the sharing relationship chain, or whether the second user account and the target user account are in the same group, and so on.

The method comprises the steps that a friend adding request initiated by a target user account to a shared user account comprises a first identifier, and the first identifier is used for identifying that the target account has the permission of adding friends to the shared user account. Due to the limitation of the first identifier, the business card information shared to the target account can only be used for a specific user account, for example, the target user account identified by the target account or a group member in a group identified by the target account adds friends to the shared user account, even if the business card information is spread to other accounts maliciously, the friend adding requests initiated by other accounts cannot be pushed to the shared user account because other accounts do not have the limit of the first identifier, so that the possibility that the shared user account, for example, the shared user account is disturbed by the unfavorable adding requests is basically avoided, and the sharing experience is improved.

Next, a method for sharing a business card and adding a friend of a user provided by the embodiment of the present application will be introduced in combination with an actual application scenario. In the application scenario, an account a in the social software 1 shares an account b in the social software 1 with an account 2 in the social software 2 through the account 1 in the social software 2. The account a in the social software 1 is a first user account, the account b in the social software 1 is a shared user account, the account 1 in the social software 2 is a second user account, the account 2 in the social software 2 is a target account, the first heterogeneous system is the social software 1, the second heterogeneous system is the social software 2, and the social software 1 and the social software 2 communicate with each other through an intercommunication background. The account a in the social software 1 finds the shared user account through the friend list, obtains the user name card of the shared user account by clicking the name card option in the shared user account, and triggers the first user account to generate the sharing request by clicking the name card sent to the social software 2 in fig. 3a and the name card sent to the social software 2 in fig. 3 b.

An architecture diagram for performing communication between the social software 1 and the social software 2 through an interworking background can be seen in fig. 13, which includes a background 1301 of the social software 1, an interworking system 1302, a background 1303 of the social software 2, a client 1304 of the social software 1, a data channel 1305, and a client 1306 of the social software 2, where an access layer of the social software 1 of the background 1301 and an access layer of the social software 2 of the background 1303 communicate through an access layer of the interworking system 1302. The background 1301 of the social software 1 is responsible for interaction logic and data processing with the client 1304 and the intercommunication system 1302 of the social software 1, and can manage accounts, group logic, notifications, messages, friend data and the like related to the client 1304 of the social software 1; the interworking system 1302 is responsible for logic processing and data storage of a plurality of heterogeneous systems, such as heterogeneous account management, message logic, group logic, and the like, and can implement other functions requiring torsion between heterogeneous systems by extending a logic module; the embodiment mainly introduces the central control capability of heterogeneous account management and message intercommunication; the backend 1303 of the social software 2 is responsible for interaction logic and data processing with the client 1306 and the interworking system 1302 of the social software 2, and can manage accounts, group logic, notifications, messages, friend details, and the like involved in the client 1306 of the social software 2.

The client 1304 of the social software 1 is responsible for logic processing and User Interface (UI) display such as external User business card Interface, card information, SDK call management of the social software 2, friend logic management, and the like, and in this embodiment, the external User business card Interface is mainly provided, so that the account a in the social software 1 can obtain the User business card of the account b in the social software 1 and perform subsequent operations on the User business card to obtain business card information, and the business card information can be transferred to the client 1306 of the social software 2 through the data channel 1305 by calling the SDK of the social software 2. The client 1306 of the social software 2 is responsible for business card information, SDK call processing, profile management (providing a profile interface), logical processing of adding friends and the like, and UI presentation (e.g., a session interface may be provided).

Referring to fig. 14, fig. 14 is a flow chart illustrating a user business card sharing and friend adding method, the method comprising:

s1401, the account a in the social software 1 obtains the user name card of the account b in the social software 1.

S1402, the account a in the social software 1 generates a sharing request for sharing the user business card with the account 2 in the social software 2.

And S1403, the account a in the social software 1 sends a sharing request to the intercommunication system.

And S1404, the intercommunication system creates business card information according to the sharing request.

S1405, the intercommunication system sends business card information to the background of the social software 1.

S1406, the background of the social software 1 sends business card information to the account a in the social software 1

S1407, skipping to the social software 2 through the SDK interface by the account a in the social software 1, and sending the business card information to the account 1 in the social software 2.

And S1408, the account 1 in the social software 2 analyzes the business card information, and selects to forward the business card information to the friend account 2 in the social software 2.

S1409, the account 1 in the social software 2 sends the encrypted ticket for generating the account 2 to the background of the social software 2.

S1410, the background of the social software 2 checks whether the account 1 in the social software 2 and the account a in the social software 1 are in an account binding relationship, and if yes, S1411 is executed.

S1411, the background of the social software 2 sends the encrypted ticket of the account 2 to the intercommunication background.

S1412, the intercommunication background generates an encrypted ticket corresponding to the first identifier.

S1413, the intercommunication background sends an encrypted ticket corresponding to the first identifier to the account 2 in the social software 2.

And S1414, generating a friend adding request by the account 2 in the social software 2.

S1415, the account 2 in the social software 2 sends a friend adding request to the background of the social software 2.

S1416, the background of the social software 2 checks whether the account 1 and the account 2 in the social software 2 are in a friend relationship, and if yes, the step S1417 is executed.

S1417, the background of the social software 2 sends a friend adding request to the intercommunication system.

S1418, the intercommunication system decrypts the encrypted ticket corresponding to the first identifier and sends the first identifier to the background of the social software 1.

S1419, the background of the social software 1 verifies the account 1 according to the first identifier, and verifies whether the account 1 is a valid user account according to the sharing relationship chain, and if the account 1 is a user account identified by the target account and is a valid user account, S1420 is executed.

Verifying whether the account 1 in the social software 2 is a legal user account includes verifying whether the account a and the account b in the social software 1 are in a friend relationship, and verifying whether the account a in the social software 1 and the account 1 in the social software 2 are in an account binding relationship.

S1420, the background of the social software 1 continues to send a friend adding request to the account b of the social software 1, and sends notification information to the account 2 in the social software 2.

It is understood that S1414-S1420 corresponds to the complete process of the target user account initiating a request for adding a friend to the shared user account according to the business card information in S1002.

S1421, the account 2 in the social software 2 waits for the addition success message of the account b in the social software 1.

S1422, the account b in the social software 1 agrees to the request of adding friends of the account 2 in the social software 2.

S1423, the account b in the social software 1 sends addition success information to the account 2 in the social software 2.

And S1424, adding the account b in the social software 1 into the friend relationship list by the account 2 in the social software 2.

Wherein, S1401-S1413 are user business card sharing processes, and S1414-S1424 are friend adding processes according to business card information.

Based on the corresponding embodiment of fig. 2, the present application provides a user business card sharing device, referring to fig. 15a, the device includes a first obtaining unit 1501, a display unit 1502, a second obtaining unit 1503, and a sharing unit 1504:

the first obtaining unit 1501 is configured to obtain a user business card of a shared user account; the shared user belongs to a first heterogeneous system through an account;

the display unit 1502 is configured to display a target user selection interface; the second obtaining unit 1503 is configured to obtain a target account through a selection operation triggered on the target user selection interface; the target account belongs to a second heterogeneous system;

the sharing unit 1504 is configured to share the user business card with the target account.

In a possible implementation manner, the user business card further includes a target resource, and the target resource is used to improve the probability that the user business card is clicked in the target account.

In a possible implementation manner, the user business card shared by the first user account is specifically business card information, the business card information includes a sharing relation chain for sharing relation information between accounts related to the user business card, the business card information acquired by the target account includes a first identifier determined according to the sharing relation chain, and the first identifier is used for identifying that the target account has a right to add friends to the shared user account.

In a possible implementation manner, the first user account and the shared user account are in a friend relationship, or the first user account is the shared user account.

In one possible implementation, the business card information is obtained by:

the first user account generates a sharing request for sharing the user business card to the target account; the sharing request comprises the sharing relationship chain; and the first user account acquires the business card information created according to the sharing request.

In a possible implementation manner, the first user account belongs to the first heterogeneous system, the target account is a target user account, an account binding relationship or a friend relationship exists between the target user account and the first user account, and the business card information shared by the first user account to the target account further includes the first identifier.

In a possible implementation manner, the first user account belongs to the first heterogeneous system, the target account is a target user account, and an account binding relationship is formed between a second user account belonging to the second heterogeneous system and the first user account; the sharing unit 1504 is specifically configured to:

the first user account shares the business card information with the second user account, so that the second user account obtains the first identifier according to the sharing relation chain, and shares the business card information carrying the first identifier with the target user account.

In a possible implementation manner, the sharing unit 1504 is specifically configured to:

and the first user account calls an interface of a second heterogeneous system through the first heterogeneous system, and forwards the business card information which is packaged into a data format conforming to the interface to the second user account.

In a possible implementation manner, the business card information shared by the first user account to the target account further includes a second identifier determined according to the sharing relationship chain, where the second identifier is used to identify that the second user account has a right to add a friend to the shared user account.

In a possible implementation manner, the first user account belongs to a second heterogeneous system, the target account is a target user account, a friend relationship is formed between the target user account and the first user account, and the first user account shares the business card information with the target account and further includes the first identifier.

In a possible implementation manner, the first user account belongs to a first heterogeneous system or a second heterogeneous system, the target account is a target group account, the first user account is a group member in a group corresponding to the target group account, and the business card information shared by the first user account to the target account further includes the first identifier.

In a possible implementation manner, the business card information includes a first identifier added by the first user account.

In a possible implementation manner, the first user account belongs to the first heterogeneous system, the target account is a target group account, a second user account belonging to the second heterogeneous system and the first user account are in an account binding relationship, and the second user account is a group member in a group corresponding to the target group account; the sharing unit 1504 is specifically configured to:

the first user account shares the business card information with the second user account, so that the second user account obtains the first identifier according to the sharing relation chain, and shares the business card information carrying the first identifier with the target group account.

In one possible implementation, referring to fig. 15b, the apparatus further comprises a sending unit 1505:

the sending unit 1505 is configured to send the sharing request to an interworking system; the interworking system has data processing logic for the first heterogeneous system and the second heterogeneous system;

the second obtaining unit 1503 is further configured to:

and obtaining business card information which is created by the intercommunication system according to the sharing request and accords with the data processing logic of the first heterogeneous system and the second heterogeneous system.

Based on the embodiment corresponding to fig. 10, the present application provides an add buddy device, referring to fig. 16a, the device includes a first obtaining unit 1601, a sending unit 1602, and a second obtaining unit 1603:

the first obtaining unit 1601 is configured to obtain a user business card shared by a first user account, where the shared user account belongs to a first heterogeneous system;

the sending unit 1602, configured to initiate a request for adding a friend to the shared user account according to the user business card;

the second obtaining unit 1603 is configured to obtain notification information sent from the first heterogeneous system, where the notification information is used to identify that the request for adding a friend is pushed to the shared user account.

In a possible implementation manner, the user business card is specifically business card information, the business card information includes a first identifier, and the first identifier is used for identifying that a target account has a right to add a friend to the shared user account;

the friend adding request also comprises the first identification;

the second obtaining unit 1603 is further configured to, if the target user account is determined to be the user account identified by the target account through the first identifier, or is a group member in a group identified by the target account, perform a step of obtaining, by the target user account, notification information sent from the first heterogeneous system.

In a possible implementation manner, the request for adding a friend further includes a name card identifier of the name card information, the name card information further includes a sharing relationship chain for sharing relationship information between accounts related to a user name card of a shared user account, and the second obtaining unit 1603 is specifically configured to:

if the target user account is verified as a valid user account by the first heterogeneous system and the second heterogeneous system according to the sharing relationship chain, the second obtaining unit 1603 performs a step of obtaining notification information from the second heterogeneous system; and the first heterogeneous system and the second heterogeneous system are used for verifying that the sharing relation chain of a legal user account is determined according to the name card identifier.

In one possible implementation, referring to fig. 16b, the apparatus further includes a third obtaining unit 1604 and an adding unit 1605:

the third obtaining unit 1604, configured to obtain information on successful addition, where the information on successful addition is used to identify that the shared user account is a friend to which the target user account is added according to the request for adding a friend;

the adding unit 1605 is configured to add the shared user account to a friend relationship list.

The embodiment of the present application further provides an apparatus, and the apparatus provided in the embodiment of the present application is described below with reference to the accompanying drawings. Referring to fig. 17, an apparatus 1700 is provided in this embodiment of the present application, where the apparatus 1700 may also be a terminal apparatus, and the terminal apparatus may be any intelligent terminal including a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), a Point of Sales (POS), a vehicle-mounted computer, and the terminal apparatus is a mobile phone for example:

fig. 17 is a block diagram illustrating a partial structure of a mobile phone related to a terminal device provided in an embodiment of the present application. Referring to fig. 17, the handset includes: radio Frequency (RF) circuit 1710, memory 1720, input unit 1730, display unit 1740, sensor 1750, audio circuit 1760, wireless fidelity (WiFi) module 1770, processor 1780, and power supply 1790. Those skilled in the art will appreciate that the handset configuration shown in fig. 17 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

The following describes each component of the mobile phone in detail with reference to fig. 17:

the RF circuit 1710 can be used for receiving and transmitting signals during information transmission and reception or during a call, and in particular, for processing the received downlink information of the base station in the processor 1780; in addition, the data for designing uplink is transmitted to the base station. In general, the RF circuitry 1710 includes, but is not limited to, an antenna, at least one Amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the RF circuitry 1710 may also communicate with networks and other devices via wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Message Service (SMS), and the like.

The memory 1720 can be used for storing software programs and modules, and the processor 1780 executes various functional applications and data processing of the mobile phone by operating the software programs and modules stored in the memory 1720. The memory 1720 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function (such as a sound playing function, an image playing function, and the like), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 1720 may include high-speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The input unit 1730 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the cellular phone. Specifically, the input unit 1730 may include a touch panel 1731 and other input devices 1732. The touch panel 1731, also referred to as a touch screen, may collect touch operations of a user (e.g., operations of the user on the touch panel 1731 or near the touch panel 1731 by using any suitable object or accessory such as a finger or a stylus), and drive a corresponding connection device according to a preset program. Alternatively, the touch panel 1731 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, and sends the touch point coordinates to the processor 1780, and can receive and execute commands sent from the processor 1780. In addition, the touch panel 1731 may be implemented by various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The input unit 1730 may include other input devices 1732 in addition to the touch panel 1731. In particular, other input devices 1732 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

The display unit 1740 may be used to display information input by or provided to the user and various menus of the mobile phone. The Display unit 1740 may include a Display panel 1741, and optionally, the Display panel 1741 may be configured in a form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, the touch panel 1731 may cover the display panel 1741, and when the touch panel 1731 detects a touch operation on or near the touch panel 1731, the touch panel is transmitted to the processor 1780 to determine the type of the touch event, and then the processor 1780 provides a corresponding visual output on the display panel 1741 according to the type of the touch event. Although in fig. 17, the touch panel 1731 and the display panel 1741 are implemented as two separate components to implement the input and output functions of the mobile phone, in some embodiments, the touch panel 1731 and the display panel 1741 may be integrated to implement the input and output functions of the mobile phone.

The handset may also include at least one sensor 1750, such as light sensors, motion sensors, and other sensors. Specifically, the light sensor may include an ambient light sensor that adjusts the brightness of the display panel 1741 according to the brightness of ambient light, and a proximity sensor that turns off the display panel 1741 and/or the backlight when the mobile phone is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.

Audio circuitry 1760, speaker 1761, and microphone 1762 may provide an audio interface between the user and the handset. The audio circuit 1760 may transmit the electrical signal converted from the received audio data to the speaker 1761, and the electrical signal is converted into a sound signal by the speaker 1761 and output; on the other hand, the microphone 1762 converts the collected sound signals into electrical signals, which are received by the audio circuit 1760 and converted into audio data, which are then processed by the audio data output processor 1780 and sent to, for example, another cell phone via the RF circuit 1710, or output to the memory 1720 for further processing.

WiFi belongs to short-distance wireless transmission technology, and the mobile phone can help a user to send and receive e-mails, browse webpages, access streaming media and the like through the WiFi module 1770, and provides wireless broadband Internet access for the user. Although fig. 17 shows the WiFi module 1770, it is understood that it does not belong to the essential constitution of the handset, and can be omitted entirely as needed within the scope not changing the essence of the invention.

The processor 1780 is the control center of the handset, connects various parts of the entire handset using various interfaces and lines, and performs various functions of the handset and processes data by running or executing software programs and/or modules stored in the memory 1720 and calling data stored in the memory 1720, thereby monitoring the entire handset. Optionally, processor 1780 may include one or more processing units; preferably, the processor 1780 may integrate an application processor, which primarily handles operating systems, user interfaces, application programs, etc., and a modem processor, which primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 1780.

The handset also includes a power supply 1790 (e.g., a battery) to power the various components, which may preferably be logically connected to the processor 1780 via a power management system, to manage charging, discharging, and power consumption via the power management system.

Although not shown, the mobile phone may further include a camera, a bluetooth module, etc., which are not described herein.

In this embodiment, the processor 1780 included in the terminal device further has the following functions:

Or the like, or, alternatively,

Referring to fig. 18, fig. 18 is a block diagram of a server 1800 according to an embodiment of the present invention, where the server 1800 may have a large difference due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 1822 (e.g., one or more processors) and a memory 1832, and one or more storage media 1830 (e.g., one or more mass storage devices) for storing applications 1842 or data 1844. The memory 1832 and the storage medium 1830 may be, among other things, transient storage or persistent storage. The program stored on the storage medium 1830 may include one or more modules (not shown), each of which may include a series of instruction operations on a server. Still further, a central processor 1822 may be provided in communication with the storage medium 1830 to execute a series of instruction operations in the storage medium 1830 on the server 1800.

The server 1800 may also include one or more power supplies 1826, one or more wired or wireless network interfaces 1850, one or more input-output interfaces 1858, and/or one or more operating systems 1841, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and so forth.

The steps performed by the server in the above embodiment may be based on the server structure shown in fig. 18.

The embodiment of the present application further provides a computer-readable storage medium for storing a program code, where the program code is used to execute any one implementation manner of the method described in the foregoing embodiments.

The terms "first," "second," "third," "fourth," and the like in the description of the application and the above-described figures, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" for describing an association relationship of associated objects, indicating that there may be three relationships, e.g., "a and/or B" may indicate: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A method for sharing a business card of a user is characterized by comprising the following steps:

the first user account shares the user name card with the target account;

the user business card shared by the first user account is specifically business card information, the business card information comprises a sharing relation chain for sharing relation information between accounts related to the user business card, the business card information acquired by the target account comprises a first identifier determined according to the sharing relation chain, and the first identifier is used for identifying that the target account has the authority of adding friends to the shared user account, so that requests of adding friends to the shared user account, initiated by other accounts without the authority of adding friends to the shared user account, cannot be pushed to the shared user account.

2. The method of claim 1, wherein the user business card further comprises a target resource, and the target resource is used for increasing the probability that the user business card is clicked in the target account.

3. The method of any one of claims 1-2, wherein the first user account is in a friend relationship with the shared user account, or wherein the first user account is the shared user account.

4. The method of claim 1, wherein the business card information is obtained by:

the first user account generates a sharing request for sharing the user business card to the target account; the sharing request comprises the sharing relationship chain;

and the first user account acquires the business card information created according to the sharing request.

5. The method according to claim 1, wherein the first user account belongs to the first heterogeneous system, the target account is a target user account, an account binding relationship or a friend relationship exists between the target user account and the first user account, and the first user account shares business card information with the target account, wherein the business card information further includes the first identifier.

6. The method according to claim 1, wherein the first user account belongs to the first heterogeneous system, the target account is a target user account, and an account binding relationship exists between a second user account belonging to the second heterogeneous system and the first user account; the first user account shares the business card information with the target account, and the method comprises the following steps:

7. The method of claim 6, wherein the first user account shares the business card information with the second user account, including:

8. The method of claim 6, wherein the sharing of the business card information by the first user account to the target account further comprises determining a second identifier according to the sharing relationship chain, wherein the second identifier is used for identifying that the second user account has a right to add a friend to the shared user account.

9. The method according to claim 1, wherein the first user account belongs to a second heterogeneous system, the target account is a target user account, a friend relationship exists between the target user account and the first user account, and the first user account shares business card information with the target account, wherein the business card information further includes the first identifier.

10. The method according to claim 1, wherein the first user account belongs to a first heterogeneous system or a second heterogeneous system, the target account is a target group account, the first user account is a group member in a group corresponding to the target group account, and the business card information shared by the first user account to the target account further includes the first identifier.

11. The method according to any one of claims 5, 9 and 10, wherein the first identification added by the first user account is included in the business card information.

12. The method according to claim 1, wherein the first user account belongs to the first heterogeneous system, the target account is a target group account, a second user account belonging to the second heterogeneous system and the first user account are in an account binding relationship, and the second user account is a group member in a group corresponding to the target group account; the first user account shares the business card information with the target account, and the method comprises the following steps:

13. The method of claim 4, further comprising:

the first user account sends the sharing request to an intercommunication system; the interworking system has data processing logic for the first heterogeneous system and the second heterogeneous system;

the first user account acquiring the business card information created according to the sharing request, including:

and the first user account acquires business card information which is created by the intercommunication system according to the sharing request and accords with the data processing logic of the first heterogeneous system and the second heterogeneous system.

14. The utility model provides a user's business card sharing device which characterized in that, the device includes first acquisition unit, display element, second acquisition unit and sharing unit:

the first obtaining unit is used for obtaining a user name card of a shared user account by a first user account; the shared user account belongs to a first heterogeneous system;

the display unit is used for displaying a target user selection interface by the first user account;

the second obtaining unit is used for obtaining a target account by the first user account through a selection operation triggered on the target user selection interface; the target account belongs to a second heterogeneous system;

the sharing unit is used for the first user account to share the user business card with the target account;

15. A method for adding friends, the method comprising:

a target user account belonging to a second heterogeneous system acquires a user name card shared by a first user account, and the shared user account belongs to the first heterogeneous system;

the target user account acquires notification information sent from the first heterogeneous system, wherein the notification information is used for identifying that the friend adding request is pushed to the shared user account;

the business card sharing method comprises the steps that a user business card shared by a first user account is specifically business card information, the business card information comprises a sharing relation chain for sharing relation information among accounts related to the user business card, the business card information acquired by a target account comprises a first identifier determined according to the sharing relation chain, the first identifier is used for identifying that the target account has the authority of adding friends to the shared user account, and therefore if the target user account does not have the authority of adding friends to the shared user account, a friend adding request cannot be pushed to the shared user account.

16. The method of claim 15 wherein the add buddy request further comprises the first identification;

before the target user account acquires notification information sent from the first heterogeneous system, the method further includes:

and if the target user account is determined to be the user account identified by the target account through the first identifier, or is a group member in a group identified by the target account, executing a step of acquiring notification information sent from the first heterogeneous system by the target user account.

17. The method according to claim 16, wherein the request for adding a friend further includes a name card identifier of the name card information, the name card information further includes a sharing relationship chain for sharing relationship information between accounts related to user name cards of shared user accounts, and before the target user account acquires notification information, the method further includes:

if the target user account is verified to be a legal user account by the first heterogeneous system and the second heterogeneous system according to the sharing relation chain, executing a step of acquiring notification information from the second heterogeneous system by the target user account; and the first heterogeneous system and the second heterogeneous system are used for verifying that the sharing relation chain of a legal user account is determined according to the name card identifier.

18. The method according to claim 16 or 17, further comprising:

the target user account acquires adding success information, wherein the adding success information is used for identifying that the shared user account adds the target user account as a friend according to the friend adding request;

and the target user account adds the shared user account into a friend relationship list.

19. A friend adding device is characterized by comprising a first obtaining unit, a sending unit and a second obtaining unit:

the second obtaining unit is configured to obtain notification information sent from the first heterogeneous system, where the notification information is used to identify that the friend adding request is pushed to the shared user account;

the business card sharing method comprises the steps that a user business card shared by a first user account is specifically business card information, the business card information comprises a sharing relation chain for sharing relation information among accounts related to the user business card, a target account acquires the business card information and comprises a first identifier determined according to the sharing relation chain, the target account belongs to a second heterogeneous system, the first identifier is used for identifying that the target account has the authority for adding friends to the shared user account, and therefore if the target user account does not have the authority for adding friends to the shared user account, a friend adding request cannot be pushed to the shared user account.

20. A user business card sharing device, comprising a processor and a memory:

the processor is configured to perform the method of any of claims 1-13 according to instructions in the program code.

21. An add buddy device, comprising a processor and a memory:

the processor is configured to perform the method of any of claims 15-18 according to instructions in the program code.

22. A computer-readable storage medium, characterized in that the computer-readable storage medium is configured to store a program code for performing the method of any of claims 1-13 or 15-18.