CN110035004A - A kind of user's business card sharing method, good friend's adding method and relevant apparatus - Google Patents

Abstract

An embodiment of the present application discloses a method for sharing user business cards. 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 displays a target user selection interface , and obtain the target account through the selection operation triggered on the target user selection interface. The first user account shares the user card with the target account, thereby realizing the user card sharing function between heterogeneous systems, so that users between heterogeneous systems can add friends through the shared user card, and realize the direct connection of user accounts between heterogeneous systems. For social networking, users do not need to download a variety of social software to meet the needs of social networking across social software, which improves user experience.

Description

A user card sharing method, friend adding method and related device

technical field

The present application relates to the field of data processing, and in particular, to a method for sharing business cards of users, a method for adding friends, and related devices.

Background technique

With the development of Internet technology, more and more users socialize through the Internet, and social software is a carrier that supports the above-mentioned social behavior, and users can socialize online through user accounts registered on the social software.

There are various types of social software currently circulating in the market, and different types of social software can be regarded as different heterogeneous systems.

However, the current social software does not provide the sharing function of user accounts between heterogeneous systems, so that some users must install various social software to realize their own social network requirements, which increases the user's operational burden.

SUMMARY OF THE INVENTION

In order to solve the above technical problems, the present application provides a method for sharing user business cards, a method for adding friends, and related devices, so as to realize the function of sharing user business cards between heterogeneous systems, so that users between heterogeneous systems can share user business cards through the shared user business card. Add friends to realize direct network socialization of user accounts between heterogeneous systems. Users do not need to download a variety of social software to meet the needs of network socialization across social software, which improves user experience.

The embodiments of the present application disclose the following technical solutions:

In a first aspect, an embodiment of the present application discloses a method for sharing a business card of a user, and the method includes:

The first user account obtains the user card of the shared user account; the shared user account belongs to the first heterogeneous system;

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

The first user account shares the user card with the target account.

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

The first obtaining unit is configured to obtain the user card of the shared user account; the shared user belongs to the first heterogeneous system through the account;

the display unit is configured to display a target user selection interface; the second acquisition unit is configured to acquire a target account through a selection operation triggered on the target user selection interface; the target account belongs to the second heterogeneous system ;

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

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

The target user account belonging to the second heterogeneous system obtains the user card shared by the first user account, and the shared user account belongs to the first heterogeneous system;

The target user account initiates a friend addition request to the shared user account according to the user card;

The target user account acquires notification information sent from the first heterogeneous system, where the notification information is used to identify that the friend addition request is pushed to the shared user account.

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

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

the sending unit, configured to initiate a friend addition request to the shared user account according to the user card;

The second acquiring unit is configured to acquire 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 fifth aspect, an embodiment of the present application discloses a device, and the device includes a processor and a memory:

the memory is used to store program code and transmit the program code to the processor;

The processor is configured to execute the method of any one of the first aspect or the third aspect according to the instructions in the program code.

In a sixth aspect, an embodiment of the present application discloses a computer-readable storage medium, where the computer-readable storage medium is used to store program codes, and the program codes are used to execute any one of the first aspect or the third aspect. Methods.

It can be seen from the above technical solutions that 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 the target user selection interface, and pass The selection operation triggered on the target user selection interface obtains the target account, and the first user account can share the user card with the target account, thereby realizing the user card sharing function between heterogeneous systems. Friends can be added through the shared user business card to realize direct network socialization of user accounts between heterogeneous systems. Users do not need to download a variety of social software to meet the needs of network social networking across social software, improving user experience.

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the accompanying drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only These are some embodiments of the present application, and for those of ordinary skill in the art, other drawings can also be obtained from these drawings without any creative effort.

1 is an example diagram of an application scenario of a method for sharing business cards of users provided by an embodiment of the present application;

2 is a flowchart of a method for sharing business cards of users according to an embodiment of the present application;

3a is an example diagram of a user card provided by an embodiment of the present application;

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

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

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

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

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

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

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

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

FIG. 9 is an example diagram of an application scenario of a method for adding friends provided by an embodiment of the present application;

10 is a flowchart of a method for adding a friend provided by an embodiment of the present application;

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

FIG. 12 is an effect diagram of a shared user account agreeing to add a target user account as a friend provided by an embodiment of the present application;

13 is an architectural diagram of communication between the social software 1 and the social software 2 provided by the embodiment of the present application through the interworking background;

14 is a flowchart of a method for sharing and adding friends of user business cards provided by an embodiment of the present application;

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

15b is a structural diagram of a user card sharing device provided by an embodiment of the application;

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

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

17 is a structural diagram of a device provided by an embodiment of the application;

FIG. 18 is a structural diagram of a server provided by an embodiment of the present application.

Detailed ways

The embodiments of the present application will be described below with reference to the accompanying drawings.

Since the current social software does not provide the sharing function of user accounts between heterogeneous systems, some users must install various social software to realize their own social network requirements, which increases the user's operational burden.

In order to solve the above technical problems, the embodiments of the present application provide a method for sharing user business cards, which is mainly used for sharing business cards between users across systems. The method may be applied to a terminal device, and the terminal device may be a personal computer (personal computer, PC for short), an intelligent terminal, a personal digital assistant (PDA for short), a tablet computer, and the like.

Wherein, social software belonging to different heterogeneous systems is installed on the terminal device, and the social software belonging to different heterogeneous systems may be installed on the same terminal device or may be installed on different terminal devices. The social software may include enterprise WeChat, WeChat, QQ, etc. The embodiments of this application will mainly introduce social software 1 and social software 2 as examples of social software belonging to different heterogeneous systems, respectively.

The user card sharing method provided in the embodiment of the present application can be applied to the application scenario shown in FIG. 1 . In the scenario shown in FIG. 1 , the first user account wishes to share the shared user account in the first heterogeneous system 101 with the 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 companies WeChat, WeChat, and QQ are different heterogeneous systems. In the subsequent embodiments, the first heterogeneous system 101 is social software 1, and the second heterogeneous system 102 is social software 2 as an example. introduce.

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

In order to realize that the first user account shares 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 obtains the target account through a selection operation triggered on the target user selection interface, thereby sharing the user card with the target account. The user card sharing function between heterogeneous systems is realized, so that users between heterogeneous systems can add friends through the shared user card, and realize direct network socialization of user accounts between heterogeneous systems. Users do not need to download a variety of social software. Satisfy the needs of social networking across social software and improve user experience.

Next, the first heterogeneous system is social software 1 and the second heterogeneous system is social software 2 as examples, and the user name card sharing method provided by the embodiments of the present application will be introduced with reference to the accompanying drawings.

Referring to FIG. 2, FIG. 2 shows a signaling interaction diagram of a method for sharing business cards of users, the method includes:

S201. The first user account obtains the user card of the shared user account.

The shared user account belongs to the first heterogeneous system (eg, 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.

Depending on the relationship between the first user account and the shared user account, the first user account may acquire the user card of the shared user account in various ways. If the first user account and the shared user account are in a friend relationship, in a possible implementation manner, the user corresponding to the first user account can find the shared user account through its friend list, and click on the shared user account in the shared user account. The "Business Card" option enables the first user account to obtain the user card of the shared user account.

If the first user account is the user account to be shared, in a possible implementation manner, the first user account can obtain the user card on the personal information page (for example, me in WeChat), so as to share its own user card with the first user card. Two heterogeneous systems.

Of course, in addition to the above relationship between the first user account and the second user account, thereby obtaining the user card, the first user account can also obtain the user card of the shared user account shared or forwarded by other user accounts in the chat interface, For example, if the first user account belongs to the first heterogeneous system, and the user card is shared in the user group where the first user account belongs, the first user account can obtain the shared user in the user group including the first user account. User card for the account. For example, the first user account can share the user card with the target account by long-pressing to select. The user card can be shown in Figure 3a, and the user card may include the profile information of the user account being shared, for example, the user name corresponding to the user account being shared (such as XXX in Figure 3a), avatar, description information (such as company name), identification, etc.

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

Target resources can include many, such as a certain amount of red envelopes, lucky wheel, etc., so that when the target account obtains the user card, it can display the target resource to the target account, attract the target account to click on the user card, and increase the user card in the user card. The probability of being clicked on the target account.

S202: 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.

Wherein, the target account belongs to the second heterogeneous system (eg, social software 2). The target user selection interface is shown in Figure 3b. Figure 3b includes the option of "send user card to social software 2". The selection operation triggered by the first user account on the target user selection interface can be that the first user account clicks "Send User Business card to social software 2" is triggered by this option.

It should be noted that this embodiment does not limit the execution order of S201 and S202.

S203. The first user account shares the user card with the target account.

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

It can be seen from the above technical solutions that 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 the target user selection interface, and pass The selection operation triggered on the target user selection interface obtains the target account, and the first user account can share the user card with the target account, thereby realizing the user card sharing function between heterogeneous systems. Friends can be added through the shared user business card to realize direct network socialization of user accounts between heterogeneous systems. Users do not need to download a variety of social software to meet the needs of network social networking across social software, improving user experience.

It should be noted that user business cards shared between heterogeneous systems can exist in the form of QR codes, because the data in the form of QR codes can be freely shared, and the data in the form of QR codes does not restrict which accounts You can add the shared person as a friend, which may lead to the malicious spread of the QR code corresponding to the user card of the shared person among different accounts, and the possibility of the shared person being harassed by malicious add requests is greatly increased. Created a poor sharing experience.

For example, user account 1 in heterogeneous system a wants to add user account 2 (the shareee) in heterogeneous system b, and user account 2 shares the two-dimensional corresponding to the user card of user account 2 to user account 1 through user account 3 code, user account 2 has a friend relationship with user account 3. User account 1 obtains the user card of user account 2 by scanning the two-dimensional code, and then triggers the user card to add user account 2 as a friend. If user account 1 can further push the QR code corresponding to the user card of user account 2 to the relationship chain where it is located, each user account in the relationship chain can further push the QR code corresponding to the user card of user account 2 Pushed to other relationship chains, and so on. All user accounts included in the relationship chain of the pushed QR code can initiate an add request to user account 2. The harassment of these add requests has brought great trouble to user account 2 and caused a poor sharing experience to user account 2. .

In this case, in order to prevent the sharer from being harassed by malicious addition requests, in a possible implementation manner, the user card shared by the first user account is specifically business card information, and the business card information includes sharing the user card information. The sharing relationship chain of the relationship information between the accounts involved in the business card. The sharing relationship chain can reflect the relationship between the first user account and the shared user account as a friend relationship, the relationship between the first user account and the target account, and which user account the user card belongs to. (for example, belonging to the shared user account), which user account the user card is shared with which account (for example, the first user account is shared with the target account).

The business card information obtained by the target account includes the first identifier determined according to the sharing relationship chain. Since the first identifier is used to identify that the target account has the right to add 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 the user account identified by the target account. Only group members in the group can have the permission to add friends to the shared user account. In this way, after the target account adds friends to the shared user account, since other accounts do not have the authority restricted by the first identifier, even if the business card information is maliciously spread to other accounts, other accounts cannot use the business card information to add the shared user. The account is a friend. Thus, the possibility of being harassed by a malicious add request for a shared user account, such as a shared user account, is basically eliminated, and the sharing experience is improved. It should be noted that when the first user account shares the user card with the target account, the first user account may directly share the user card with the target account, or the first user account may forward the user card to the target account through other user accounts, indirectly. Share the user card with the target account. If the first user account directly shares the user card with the target account, the involved accounts may include the user account that shares the user card (the first user account), the user account to which the user card belongs (the shared user account), and the user account to which the user card is shared. Account sharing (target account); if the first user account indirectly shares the user card with the target account, the involved accounts may include the user account that shares the user card, the user account to which the user card belongs, the user account that transfers the user card, and the target account .

The sharing relationship chain includes not only the accounts involved in the user card, but also relationship information identifying the relationship between the involved accounts. The relationship between the involved accounts may include friend relationship, account binding relationship, etc. For example, the first user account and the shared user account are a friend relationship, the first user account and the user account that transfers the user card are account binding relationships, The first user account and the target account are friends, and the like.

If the first user account directly shares the user card with the target account, the sharing relationship chain is shown in Figure 4a. Figure 4a takes account a in social software 1 sharing account b in social software 1 to account 1 in social software 2 as an example, card_openid:WW_b represents the identifier of the shared user account, that is, the user card belongs to the one identified by WW_b Account b in social software 1; from_openid:WW_a represents the identity of the first user account, to_openid: WX_1 represents the identity of the target account, account a and account b in social software 1 are friends, and account a in social software 1 and Account 1 in social software 2 is a friend relationship.

If the first user account indirectly shares the user card with the target account, the sharing relationship chain is as shown in Figure 4b. As shown in Figure 4b, taking account a in social software 1 sharing account b in social software 1 to account 2 in social software 2 through account 1 in social software 2 as an example, card_openid:WW_b represents the identifier of the shared user account, That is, the user card belongs to the account b in the social software 1 identified by WW_b; from_openid:WW_a indicates the identification of the first user account, bind_openid:WX_1 indicates the identification of the second user account, and the second user account identified by WX_1 is the same as that identified by WW_a. The first user account is a binding relationship, the account a and the account b in the social software 1 are in a friend relationship, and the account a in the social software 1 and the account 1 in the social software 2 are in a friend relationship.

By sharing the relationship chain, it is convenient to generate the first identifier according to the sharing chain when sharing the user's business card with the target account, and to limit the account of adding the shared user account as a friend. The validity of the user account of the transfer user's business card can also be verified according to the sharing chain, so as to avoid malicious proliferation of the user's business card by illegal user accounts. In addition, when the target user account sends a friend request to the shared user account, the legitimacy of the target user account can be verified according to the sharing chain, so as to prevent illegal user accounts from harassing the shared user account.

Business card information can be represented by CardInfo, and the business card information obtained by the target account includes a first identifier determined according to the sharing relationship chain, and the first identifier is used to identify that the target account has access to the shared user. Permission to add friends to the account. The first identifier can be represented by a ticket, and the first identifier can be in plain text. In some cases, in order to prevent the first identifier from being tampered with, the first identifier can be encrypted to obtain an encrypted ticket. Specifically, an encrypted ticket can be generated by using the target account as the key. .

Taking the account of the user to be shared as an account b in the social software 1 as an example, the first identifier may be shown in FIG. 5a and FIG. 5b. Fig. 5a shows that the first identifier corresponding to the shared user account is shared with the target account (for example, the account 2 in the social software 2), wherein from_username:WX_2 represents the identifier of the user account that initiated the request to add a friend, and to_username:WW_b represents which one you want to add The account is a friend, and the first identifier identifies that the target account WX_2 has the right to add friends to the shared user account WW_b. Fig. 5b shows that the first identification corresponding to the shared user account is shared with the group corresponding to the target account, wherein from_username:group openid indicates the identification of the group where the user account that initiates the adding friend request, to_username:WW_b indicates which account you want to add as a friend, The first identifier identifies that a group member in the target group account has the right to add friends to the shared user account WW_b.

It should be noted that, in a possible implementation manner, the business card information is obtained in the following manner: First, the first user account generates a sharing request for sharing the user business card with the target account, and the sharing request includes the sharing relationship chain. Then, the first user account obtains the business card information created according to the sharing request.

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

For example, the second heterogeneous system is social software 2. After the first user account obtains the user card of the shared user account, the user corresponding to the first user account clicks "send to social software 2" in Fig. 3a and Fig. 3b "Send user business card to social software 2" triggers the first user account to generate the sharing request.

It should be noted that, the first user account may acquire the business card information created according to the sharing request in many ways. One way for the first user account to obtain the business card information created according to the sharing request may be: the business card information created by the first user account according to the sharing request, so that the first user account obtains the business card information from the first user account itself .

Another way for the first user account to acquire the business card information created according to the sharing request may be that the first user account sends the sharing request to the interworking system, and the interworking system (IMUnion) creates the business card information according to the acquired sharing request, thereby converting the The business card information is sent to the first user account, the interworking system has the data processing logic 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 first heterogeneous system. Data processing logic for a heterogeneous system and a second heterogeneous system. At this time, the first identifier 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 the first heterogeneous system and the second heterogeneous system through the interworking system, for example, the user ID can be converted into a general openid, the first heterogeneous system Both the system and the second heterogeneous system recognize the openid.

In some cases, the business card information may also include profile information of the shared user account. The data information included in the business card information can be referred to as shown in FIG. 6 , name represents the user name, headurl represents the avatar, openid represents the identifier of the user account, and desc (corpname, etc) represents the description information, such as the company name.

It should be noted that, since the heterogeneous system where 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 where it is located. . Taking the social software 1 as an example of the heterogeneous system where the first user account is located, the first user account can send the sharing request to the interworking system through the background of the social software 1 thereof.

It can be seen from the above technical solutions that 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 the target user selection interface, and pass The selection operation triggered on the target user selection interface obtains the target account, and the first user account can share the business card information with the target account. When the account obtains the business card information, the business card information includes a first identifier determined according to the sharing relationship chain, where the first identifier is used to identify that the target account has the authority to add friends to the shared user account. Due to the limitation of the first identification, the business card information shared to 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 maliciously spread to other accounts, other accounts will be Without the authority restricted by the first identification, other accounts cannot use the business card information to add the shared user account as a friend, thus basically eliminating the possibility of the shared user being harassed by malicious addition requests, such as the shared user account. Improved sharing experience.

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

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

The second scenario is that the first user account belongs to the first heterogeneous system, the target account is the target user account, and the second user account belonging to the second heterogeneous system and the first user account are accounts A binding relationship, the first user account shares the shared user account to 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. Wherein, the account a in the social software 1 is the first user account, the account b in the social software 1 is the shared user account, the account 1 in the social software 2 is the second user account, and the account 2 in the social software 2 is the target account.

The third scenario is that the first user account belongs to the second heterogeneous system, the target account is the target user account, the target user account and the first user account are in a friend relationship, and the first user account directly converts the The shared user account is shared 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 the first user account, the account b in the social software 1 is the shared user account, and the account 2 in the social software 2 is the target account.

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

The fifth scenario is that the first user account belongs to the first heterogeneous system, the target account is a target group account, and there is a relationship between the second user account belonging to the second heterogeneous system and the first user account is an account binding relationship, and the second user account is a group member in the group corresponding to the target group account, and the first user account will be shared with the shared user account through the second user account to the group corresponding to the second user account target group account. For example, account a in social software 1 shares account b in social software 1 to the group where account 1 is located through account 1 in social software 2, where account a in social software 1 is the first user account, and the social software Account b in 1 is the shared user account, account 1 in social software 2 is the second user account, and the group account corresponding to the group where account 1 belongs is the target group account.

Among them, the first scenario, the third scenario and the fourth scenario belong to the first user account, and the shared user account is directly shared with the target account. Therefore, the sharing relationship chain reflects which user account the user card belongs to, and the user card Which user account is shared to which account also reflects that the shared user account and the first user account are friends, and the user account identified by the first user account and the target account is a friend relationship or account binding relationship, or the first user account. Group members in the group identified by the target account. In 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 and fifth scenarios belong to the first user account indirectly sharing the user card with the target account, that is, the first user account will share the user account to be shared with the target account through the second user account, and the first user account will share the user card with the target account. It is directly shared to the second user account, and then forwarded to the target account by the second user account. Therefore, the sharing relationship chain reflects the identification of which user account the user card belongs to, which user account the user card is shared with to the target account, which account is the bound account used to forward the user card to the target account, and also reflects the shared user account. A friend relationship with the first user account, an account binding relationship between the first user account and the second user account, and the like.

In these scenarios, since the second user account and the first user account are account-bound, when the first user account shares the user card with the second user account, it needs to jump from the first heterogeneous system to the second heterogeneous system system, jumping is performed between applications (such as social software), therefore, 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 generation time of the first identifier in the business card information may be different according to different scenarios of user card sharing. In the first scenario, the third scenario and the fourth scenario, the sharing relationship chain reflects which user account the user card belongs to, and which user account the user card is shared to which account, that is, it reflects the shared user account, the first A user account and a target account, therefore, the business card information shared by the first user account with the target account includes the first identifier.

In the second scenario and the fifth scenario, the business card information obtained by the first user account may not yet include the first identifier, but the first user account generated during the process of sharing the business card information with the target account by the first user account. identification, so as to ensure that the business card information obtained by the target account includes the first identification. In this case, a 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 can share the business card information according to the information included in the business card information. The sharing relationship chain obtains the first identifier, and shares the business card information carrying the first identifier to the target user account or the target group account corresponding to the group where the first user account belongs.

In these scenarios, since the first heterogeneous system to which the user account to be shared belongs and the target account to which the target account belongs are installed on the same terminal device, an implementation manner for the first user account to share business card information with the second user account may be: The first user account invokes the interface of the second heterogeneous system through the first heterogeneous system, and forwards the business card information encapsulated in a data format conforming to the interface to the second user account. By invoking the interface of the second heterogeneous system, jumping from the first heterogeneous system on the terminal device to the second heterogeneous system is realized, thereby completing the forwarding of business card information to the second user account.

The interface may be a software development kit (Software Development Kit, SDK for short) interface, and the SDK interface provides data encapsulation and parsing capabilities to meet the needs of transmitting different data types (such as text, pictures, videos, files, chat history, etc.). When the first user account in the first heterogeneous system wants to transfer certain data (such as business card information) to the second user account in the second heterogeneous system, the first user account will encapsulate the data into a format that conforms to the interface. The data format, in the form of binary data, is passed to the second user account in the form of directly carrying data through openURL or sharing data with the pasteboard UIPasteboard. The second user account reads data from openURL or UIPasteboard, parses and converts it into a text data type, and distributes it to the corresponding ApiHandler interface for subsequent processing.

In this embodiment, if the first user account belongs to social software 1, the target account belongs to social software 2, and the target account is the target user account, the effect diagram of jumping from social software 1 to social software 2 is shown in 701 in FIG. 7 . As shown, the effect diagram of business card information sharing to the target user account is shown in 702 in 7; if the first user account belongs to social software 1, the target account belongs to social software 2, and the target account is the target group account, then from social software 1 The effect diagram of jumping to the social software 2 is shown in 801 in FIG. 8 , and the effect diagram of the business card information sharing to the target group account is shown in 802 in 8 .

It should be noted that, in order to prevent the business card information from being acquired by an illegal user account, before the first user account sends the business card information to the second user account, the second heterogeneous system can verify whether there is a relationship between the second user account and the first user account. Account binding relationship, if yes, send the business card information to the second user account.

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

After the second user account receives the business card information, the user corresponding to the second user account can select the target account, thereby requesting to generate the first identifier. The first identifier may be generated by the second user account itself according to the sharing relationship chain, or may be sent to the background of the second heterogeneous system to apply for generating the first identifier.

If the second user account sends the business card information to the background of the second heterogeneous system to apply for generating the first identifier, in order to prevent the business card information from being intercepted by illegal users, after the second user account sends the business card information to the background of the second heterogeneous system, the second The background of the heterogeneous system may first check whether the second user account is in an account binding relationship with the first user account, and if so, request IMUnion to generate the first identifier.

Taking the shared user account as the account WW_b in the social software 1, the target account as the account WX_2 in the social software 2, and the second user account as the account WX_1 in the social software 2 as an example, when the business card information is shared to WX_1, the social The software 2 side will parse and obtain the business card information (CardInfo), and then, the user corresponding to WX_1 chooses to forward it to WX_2, and WX_1 will send the CardInfo to the background application of social software 2 to generate the first identifier that WX_2 has the permission to add friends to WW_b. The background of social software 2 will first check whether the bind_openid of CardInfo is the WX_1 currently logged in, if not (if it is WX_3), it will generate a failure message and insert it into the chat session between WX_1 and WX_3; if it is WX_1, request the IMUnion background A first identification is generated.

It should be noted that, in some cases, the second user account may have the need to add the shared user account as a friend. In order to ensure that the second user account can add the shared user account through the business card information after obtaining the business card information. friend, in some possible implementations, the business card information shared by the first user account with the target account may further include a second identifier determined according to the sharing relationship chain, where the second identifier is used to identify the first The second user account has the right to add friends to the shared user account.

The purpose of the first user account sharing the user card of the shared account with the target account is to enable the user account identified by the target account, or the group members in the group identified by the target account to add the shared user account as a friend. Next, in the aforementioned The method for adding friends is introduced on the basis of the embodiment.

The method for adding friends provided by the embodiments of the present application may be applied to a terminal device, and the terminal device may be a personal computer (PC for short), an intelligent terminal, a personal digital assistant (PDA for short), a tablet computer, or the like.

Wherein, social software belonging to different heterogeneous systems is installed on the terminal device, and the social software belonging to different heterogeneous systems may be installed on the same terminal device or may be installed on different terminal devices. The social software may include enterprise WeChat, WeChat, QQ, etc. The embodiments of this application will mainly introduce social software 1 and social software 2 as examples of social software belonging to different heterogeneous systems, respectively.

The method for adding friends provided by the embodiments of the present application can be applied to the application scenario shown in FIG. 9 . In the scenario shown in FIG. 9 , the target user account in the second heterogeneous system 102 wishes 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 subsequent embodiments, the first heterogeneous system 101 is social software 1 and the second heterogeneous system 102 is social software 2 as an example for introduction.

The target user account and the shared user account are both user accounts. In order to add the shared user account to the target user account as a friend, the target user account obtains the user card shared by the first user account, and initiates a notification to the shared user account according to the user card. Add a friend request. If the friend request can be pushed to the shared user account, the target user account obtains notification information sent from the first heterogeneous system, and the notification information is used to identify that the friend addition request is pushed to the shared user. account.

Next, the method for adding friends provided by the embodiments of the present application will be introduced with reference to the accompanying drawings.

Referring to FIG. 10, FIG. 10 shows a signaling interaction diagram of a method for adding friends, the method includes:

S1001. The target user account belonging to the second heterogeneous system acquires the user business card shared by the first user account.

Wherein, the shared user account belongs to the first heterogeneous system.

S1002. The target user account initiates a friend addition request to the shared user account according to the user card.

After the target user account obtains the user card, the user card may include the profile information of the shared user account, and the target user account may directly view the profile information.

If the target user account and the shared user account are not in a friend relationship, the target user account may initiate an add friend request to the shared user account. The effect diagram of the target user account initiating the request to add friends through the user card is shown in Figure 11. The user corresponding to the target user account triggers the target user account to initiate adding friends by clicking the "Add to Address Book" button in 1101 and the "Send" button in 1102. ask.

It should be noted that, a possible implementation manner of S1002 is that the target user account initiates a friend addition request to the shared user account through the first heterogeneous system, and 1002 in FIG. 10 shows this implementation manner.

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

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

After the target user account receives the notification message, it 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 a friend, the shared user account sends an addition success message, and the target user account obtains the addition success information, which is used to identify the shared user account according to the friend addition request. The target user account is added as a friend, and then the target user account adds the shared user account to a friend relationship list. Among them, the effect diagram of the shared user account agreeing to add the target user account as a friend is shown in Figure 12. The user corresponding to the shared user account clicks the "Pass Verification" button in 1201, thereby triggering the sending of a successful addition message, and completing the process of adding friends. The display interface is shown in 1202. The shared user account and the target user account that are friends with each other can communicate with each other through messages, such as sending messages and making voice calls.

It should be noted that, since the user card may be spread among different accounts, in order to avoid the sharer being harassed by malicious add requests and improve the sharing experience, in a possible implementation, the user card is specifically the business card information. The business card information includes a first identifier, and the first identifier is used to identify that the target account has the authority to add friends to the shared user account.

Correspondingly, the request for adding a friend also includes the first identifier, so that if the first heterogeneous system receives the request for adding a friend, the first heterogeneous system can verify the target user account through the first identifier, and if the target user account is determined For the user account identified by the target account, or a group member in the group identified by the target account, the step of S1003 is performed.

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

It should be noted that the business card information may be intercepted by an illegal user account during the sharing process, thereby tampering with the business card information. For example, the target account identified in the real business card information is the account WX_2 in social software 2. The account (such as the account WX_3 in the social software 2) is intercepted, and the account WX_3 in the social software 2 can add the shared user account (such as the account WW_b in the social software 1) as a friend, and the target account number is tampered with in the social software 2. Account WX_3.

In this case, in order to prevent illegal user accounts from being able to add the shared user account as a friend, in a possible implementation manner, the request for adding a friend further includes a business card identifier of the business card information, and the business card information further includes Share the shared relationship chain of the relationship information between the accounts involved in the user card of the shared user account, so that before S1003, the first heterogeneous system and the second heterogeneous system can check whether the target user account is a legitimate user account according to the shared relationship chain. Verification is performed, and if the verification target user account is a legitimate user account, the step of S1003 is performed. Wherein, the sharing relationship chain used by the first heterogeneous system and the second heterogeneous system to verify the legal user account is determined according to the identification of the business card.

For example, the first heterogeneous system can 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 the same relationship according to the sharing relationship chain. Friendship, or whether the first user account and the target user account are in the same group; the first heterogeneous system can verify whether the first user account and the second user account are bound according to the sharing relationship chain; the second heterogeneous system It can be verified according to the sharing relationship chain whether the target user account and the second user account are in a friend relationship, or whether the second user account and the target user account are in the same group, and so on.

Since the adding friend request initiated by the target user account to the shared user account includes the first identifier, the first identifier is used to identify that the target account has the right to add friends to the shared user account. Due to the limitation of the first identification, the business card information shared to the target account can only be used for a specific user account, such as the target user account identified by the target account or the group members in the group identified by the target account to add friends to the shared user account , even if the business card information is maliciously spread to other accounts, because other accounts do not have the authority restricted by the first identifier, the friend request initiated by other accounts will not be pushed to the shared user account, thus basically preventing the shared user such as The possibility of being harassed by malicious add requests to the shared user account improves the sharing experience.

Next, the method for sharing business cards and adding friends provided by the embodiments of the present application will be introduced in combination with actual application scenarios. In this application scenario, 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 . Wherein, the account a in the social software 1 is the first user account, the account b in the social software 1 is the shared user account, the account 1 in the social software 2 is the second user account, and the account 2 in the social software 2 is the target Account, the first heterogeneous system is social software 1, the second heterogeneous system is social software 2, and the social social software 1 and the social software 2 communicate through an interworking background. The account a in the social software 1 finds the shared user account through its friend list, obtains the user card of the shared user account by clicking the "Business Card" option in the shared user account, and then clicks "Send to social media" in Figure 3a. Software 2" and "send user card to social software 2" in FIG. 3b trigger the first user account to generate the sharing request.

Figure 13 shows the architecture diagram of the communication between social software 1 and social software 2 through the interworking backend, including the backend 1301 of social software 1, the interworking system 1302, the backend 1303 of social software 2, and the client 1304 of social software 1 , the data channel 1305 and the client 1306 of the social software 2, wherein the access layer of the social software 1 of the background 1301 communicates with the access layer of the social software 2 of the background 1303 through the access layer of the interworking system 1302. The background 1301 of the social software 1 is responsible for the interaction logic and data processing with the client 1304 of the social software 1 and the interworking system 1302, and can manage the accounts, group logic, notifications, messages, Friends information, etc.; the interworking system 1302 is responsible for the logic processing and data storage of multiple heterogeneous systems, such as heterogeneous account management, message logic, group logic, etc., and other needs can be reversed between heterogeneous systems by extending logic modules. This embodiment focuses on the central capability of heterogeneous account management and message intercommunication; the background 1303 of the social software 2 is responsible for the interaction logic and data processing with the client 1306 of the social software 2 and the intercommunication system 1302, and can manage social Accounts, group logic, notifications, messages, friend profiles, etc. involved in the client 1306 of Software 2.

The client 1304 of the social software 1 is responsible for logic processing such as business card interface, card information, SDK call management of the social software 2, friend logic management, and user interface (User Interface, UI for short) display. In this embodiment, it mainly provides external users Business card interface, so that account a in social software 1 can obtain the user card of account b in social software 1, and perform subsequent operations on it to obtain business card information. The business card information is transmitted to the client 1306 of the social software 2 . The client 1306 of the social software 2 is responsible for business card information, SDK calling processing, data management (providing a data interface), adding friends and other logic processing and UI display (for example, a conversation interface can be provided).

Referring to Fig. 14, Fig. 14 shows a flowchart of a method for sharing and adding friends of a user's business card, the method includes:

S1401 , the account a in the social software 1 obtains the user 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 card with the account 2 in the social software 2 .

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

S1404, the interworking 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 the business card information to the account a in the social software 1

S1407 , the account a in the social software 1 jumps to the social software 2 through the SDK interface, and sends the business card information to the account 1 in the social software 2 .

S1408 , the account 1 in the social software 2 parses to obtain the business card information, and selects and forwards it to the friend account 2 in the social software 2 .

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

S1410. The background of the social software 2 verifies 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 so, execute S1411.

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

S1412. The interworking 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.

S1414, the account 2 in the social software 2 generates a request for adding a friend.

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

S1416 , the background of the social software 2 verifies whether the account 1 and the account 2 in the social software 2 are friends, and if so, execute S1417 .

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

S1418 , the interworking 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 legal user account according to the sharing relationship chain. If the account 1 is the user account identified by the target account and is a legal user account, perform S1420.

Verifying whether account 1 in social software 2 is a legitimate user account includes verifying whether account a and account b in social software 1 are friends, and verifying whether account a in social software 1 and account 1 in social software 2 are accounts. binding relationship.

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

It can be understood that S1414-S1420 are equivalent to the complete process in S1002 in which the target user account initiates a request for adding a friend to the shared user account according to the business card information.

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

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

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

S1424, the account 2 in the social software 2 adds the account b in the social software 1 to the friend relationship list.

Among them, S1401-S1413 are the user card sharing process, and S1414-S1424 are the process of adding friends according to the business card information.

Based on the embodiment corresponding to FIG. 2 , the present application provides a user card sharing device. Referring to FIG. 15 a , 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 the user card of the shared user account; the shared user belongs to the first heterogeneous system through the account;

The display unit 1502 is used to display the target user selection interface; the second acquisition unit 1503 is used to obtain the target account through a selection operation triggered on the target user selection interface; the target account belongs to the second system;

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

In a possible implementation manner, the user card further includes a target resource, and the target resource is used to increase the probability that the user 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, and the business card information includes a sharing relationship chain of relationship information between accounts involved in sharing the user business card, and the target The business card information obtained by the account includes a first identifier determined according to the sharing relationship chain, where the first identifier is used to identify that the target account has the authority 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 a possible implementation manner, the business card information is obtained in the following manner:

The first user account generates a sharing request for sharing the user business card with the target account; the sharing request includes the sharing relationship chain; the first user account obtains the business card created according to the sharing request information.

In a possible implementation manner, the first user account belongs to the first heterogeneous system, the target account is a target user account, and there is account binding between the target user account and the first user account relationship or friend relationship, the business card information shared by the first user account with the target account also 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 the second user account belonging to the second heterogeneous system is the same as the second user account. A user account is an account binding relationship; the sharing unit 1504 is specifically used for:

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 relationship chain, and will carry all the information of the first identifier. The business card information is shared to the target user account.

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

The first user account calls the interface of the second heterogeneous system through the first heterogeneous system, and forwards the business card information encapsulated in 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 with the target account further includes a second identifier determined according to the sharing relationship chain, where the second identifier is used to identify the second identifier The user account has the right to add friends 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, and the target user account and the first user account are in a friend relationship, and the The business card information shared by the first user account with the target account 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, and the first user account is the target group account For the group members in the corresponding group, the business card information shared by the first user account with the target account also 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, and the second user account belonging to the second heterogeneous system is associated with the first heterogeneous system. A user account is an account binding relationship, and the second user account is a group member in the group corresponding to the target group account; the sharing unit 1504 is specifically used for:

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 relationship chain, and will carry all the information of the first identifier. The business card information is shared to the target group account.

In a possible implementation, referring to FIG. 15b, the apparatus further includes a sending unit 1505:

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

The second obtaining unit 1503 is further configured to:

Obtain business card information that is created by the interworking system according to the sharing request and conforms to 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 apparatus for adding friends. Referring to FIG. 16 a , the apparatus 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 card shared by a first user account, where the shared user account belongs to the first heterogeneous system;

The sending unit 1602 is configured to initiate an add friend request to the shared user account according to the user 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, and the business card information includes a first identifier, and the first identifier is used to identify that the target account has the right to add friends to the shared user account;

The adding friend request further includes the first identifier;

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

In a possible implementation manner, the adding friend request further includes a business card identifier of the business card information, and the business card information further includes a sharing relationship chain of the relationship information between the accounts involved in sharing the business card of the user account of the shared user. The second obtaining unit 1603 is specifically used for:

If the target user account is verified as a legitimate user account by the first heterogeneous system and the second heterogeneous system according to the sharing relationship chain, the second obtaining unit 1603 executes obtaining a notification from the second heterogeneous system The information step; the sharing relationship chain used by the first heterogeneous system and the second heterogeneous system to verify the legal user account is determined according to the business card identifier.

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

The third obtaining unit 1604 is configured to obtain addition success information, where the addition success information is used to identify that the shared user account has added the target user account as a friend according to the friend addition request;

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 a device, and the device provided by the embodiment of the present application will be introduced below with reference to the accompanying drawings. Referring to FIG. 17 , an embodiment of the present application provides a device 1700. The device 1700 may also be a terminal device, and the terminal device may include a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), Any intelligent terminal such as Point of Sales (POS), on-board computer, etc., taking the terminal device as a mobile phone as an example:

FIG. 17 is a block diagram showing a partial structure of a mobile phone related to a terminal device provided by an embodiment of the present application. Referring to FIG. 17 , the mobile phone includes: a radio frequency (Radio Frequency, RF for short) circuit 1710, a memory 1720, an input unit 1730, a display unit 1740, a sensor 1750, an audio circuit 1760, a wireless fidelity (WiFi for short) module 1770, a processing The device 1780, the power supply 1790 and other components. Those skilled in the art can understand that the structure of the mobile phone shown in FIG. 17 does not constitute a limitation on the mobile phone, and may include more or less components than shown, or combine some components, or arrange different components.

The following is a detailed introduction to each component of the mobile phone with reference to Figure 17:

The RF circuit 1710 can be used for receiving and sending signals during the process of sending and receiving information or talking. In particular, after receiving the downlink information of the base station, it is processed by the processor 1780; in addition, it sends the designed uplink data to the base station. Generally, the RF circuit 1710 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (Low Noise Amplifier, LNA for short), a duplexer, and the like. In addition, RF circuitry 1710 may also communicate with networks and other devices via wireless communications. The above-mentioned wireless communication can use any communication standard or protocol, including but not limited to Global System of Mobile communication (GSM for short), General Packet Radio Service (GPRS for short), Code Division Multiple Access (Code Division Multiple Access) Division Multiple Access (CDMA for short), Wideband Code Division Multiple Access (WCDMA for short), Long Term Evolution (LTE for short), E-mail, Short Messaging Service (Short Messaging Service, SMS for short), etc. .

The memory 1720 can be used to store software programs and modules, and the processor 1780 executes various functional applications and data processing of the mobile phone by running the software programs and modules stored in the memory 1720 . The memory 1720 may mainly include a stored program area and a stored data area, wherein the stored program area may store an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; Data created by the use of the mobile phone (such as audio data, phone book, etc.), etc. Additionally, 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 can be used to receive inputted numerical or character information, and generate key signal input related to user setting and function control of the mobile phone. Specifically, the input unit 1730 may include a touch panel 1731 and other input devices 1732 . The touch panel 1731, also known as a touch screen, can collect user touch operations on or near it (such as the user's finger, stylus, etc., any suitable object or accessory on or near the touch panel 1731). operation), and drive the corresponding connection device according to the preset program. Optionally, the touch panel 1731 may include two parts, a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it to the touch controller. To the processor 1780, and can receive the command sent by the processor 1780 and execute it. In addition, the touch panel 1731 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 1731 , the input unit 1730 may further include other input devices 1732 . Specifically, other input devices 1732 may include, but are not limited to, one or more of physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, joysticks, and the like.

The display unit 1740 may be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 1740 may include a display panel 1741 . Optionally, the display panel 1741 may be configured in the form of a liquid crystal display (LCD for short), an organic light-emitting diode (OLED for short). Further, the touch panel 1731 can cover the display panel 1741. When the touch panel 1731 detects a touch operation on or near it, it transmits it to the processor 1780 to determine the type of the touch event, and then the processor 1780 determines the type of the touch event according to the touch event. Type provides corresponding visual output on display panel 1741. Although in FIG. 17, the touch panel 1731 and the display panel 1741 are used as two independent components to realize the input and input functions of the mobile phone, in some embodiments, the touch panel 1731 and the display panel 1741 can be integrated to form Realize the input and output functions of the mobile phone.

The cell phone 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 and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 1741 according to the brightness of the ambient light, and the proximity sensor may turn off the display panel 1741 and/or when the mobile phone is moved to the ear. or backlight. As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (usually three axes), and can detect the magnitude and direction of gravity when it is stationary. games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors such as gyroscope, barometer, hygrometer, thermometer, infrared sensor, etc. Repeat.

The audio circuit 1760, the speaker 1761, and the microphone 1762 can provide an audio interface between the user and the mobile phone. The audio circuit 1760 can transmit the received audio data converted electrical signal to the speaker 1761, and the speaker 1761 converts it into a sound signal for output; on the other hand, the microphone 1762 converts the collected sound signal into an electrical signal, which is converted by the audio circuit 1760 After receiving, it is converted into audio data, and then the audio data is output to the processor 1780 for processing, and then sent to, for example, another mobile phone through the RF circuit 1710, or the audio data is output to the memory 1720 for further processing.

WiFi is a short-distance wireless transmission technology. The mobile phone can help users to send and receive emails, browse web pages and access streaming media through the WiFi module 1770. It provides users with wireless broadband Internet access. Although FIG. 17 shows the WiFi module 1770, it can be understood that it is not a necessary component of the mobile phone, and can be completely omitted as required within the scope of not changing the essence of the invention.

The processor 1780 is the control center of the mobile phone, using various interfaces and lines to connect various parts of the entire mobile phone, by running or executing the software programs and/or modules stored in the memory 1720, and calling the data stored in the memory 1720. Various functions of the mobile phone and processing data, so as to monitor the mobile phone as a whole. Optionally, the processor 1780 may include one or more processing units; preferably, the processor 1780 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, etc. , the modem processor mainly deals with wireless communication. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 1780.

The mobile phone also includes a power supply 1790 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 1780 through a power management system, so as to manage charging, discharging, and power consumption management functions through the power management system.

Although not shown, the mobile phone may also include a camera, a Bluetooth module, and the like, which will not be repeated here.

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

The first user account obtains the user card of the shared user account; the shared user account belongs to the first heterogeneous system;

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

The first user account shares the user card with the target account.

or,

The target user account belonging to the second heterogeneous system obtains the user card shared by the first user account, and the shared user account belongs to the first heterogeneous system;

The target user account initiates a friend addition request to the shared user account according to the user card;

The target user account acquires notification information sent from the first heterogeneous system, where the notification information is used to identify that the friend addition request is pushed to the shared user account.

An embodiment of the present application also provides a server. Please refer to FIG. 18 . FIG. 18 is a structural diagram of a server 1800 provided by an embodiment of the present application. The server 1800 may vary greatly due to different configurations or performance, and may include a or one or more Central Processing Units (CPU) 1822 (eg, one or more processors) and memory 1832, and one or more storage media 1830 (eg, one or more storage media 1844) storing application programs 1842 or data 1844 mass storage devices). Among them, the memory 1832 and the storage medium 1830 may be short-term storage or persistent storage. The program stored in the storage medium 1830 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the server. Furthermore, the central processing unit 1822 may be configured to communicate with the storage medium 1830 to execute a series of instruction operations in the storage medium 1830 on the server 1800 .

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

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

Embodiments of the present application further provide a computer-readable storage medium for storing program codes, where the program codes are used to execute any one of the implementation manners of the methods described in the foregoing embodiments.

The terms "first", "second", "third", "fourth", etc. (if any) in the description of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It is to be understood that the data so used may be interchanged under appropriate circumstances such that the embodiments of the application described herein can, for example, be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having" and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those expressly listed Rather, those steps or units may include other steps or units not expressly listed or inherent to these processes, methods, products or devices.

It should be understood that, in this application, "at least one (item)" refers to one or more, and "a plurality" refers to two or more. "And/or" is used to describe the relationship between related objects, indicating that there can be three kinds of relationships, for example, "A and/or B" can mean: only A, only B, and both A and B exist , where A and B can be singular or plural. The character "/" generally indicates that the related objects are an "or" relationship. "At least one item(s) below" or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (a) of a, b or c, can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c" ", where a, b, c can be single or multiple.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated unit, if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM for short), Random Access Memory (RAM for short), magnetic disk or CD, etc. that can store program codes medium.

As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand: The technical solutions described in the embodiments are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions in the embodiments of the present application.

Claims (22)

1. a user card sharing method, is characterized in that, described method comprises: The first user account obtains the user card of the shared user account; the shared user account belongs to the first heterogeneous system; The first user account displays a target user selection interface, and obtains a target account through a selection operation triggered on the target user selection interface; the target account belongs to the second heterogeneous system; The first user account shares the user card with the target account. 2 . The method according to claim 1 , wherein the user card further includes target resources, and the target resources are used to increase the probability that the user card is clicked in the target account. 3 . 3 . The method according to claim 1 , wherein the user business card shared by the first user account is specifically business card information, and the business card information includes sharing of relationship information between accounts involved in sharing the user business card. 4 . A relationship chain, the business card information obtained by the target account includes a first identifier determined according to the sharing relationship chain, and the first identifier is used to identify that the target account has the ability to add friends to the shared user account. permissions. 4. The method according to any one of claims 1-3, wherein the first user account and the shared user account are in a friend relationship, or the first user account is the shared user account user account. 5. The method according to claim 3, wherein the business card information is obtained in the following manner: The first user account generates a sharing request for sharing the user card with the target account; the sharing request includes the sharing relationship chain; The first user account acquires business card information created according to the sharing request. 6. The method according to claim 3, wherein the first user account belongs to the first heterogeneous system, the target account is a target user account, and the target user account and the first user Accounts have an account binding relationship or a friend relationship, and the business card information shared by the first user account with the target account also includes the first identifier. 7 . The method according to claim 3 , wherein the first user account belongs to the first heterogeneous system, the target account is a target user account, and the second user account belongs to the second heterogeneous system. 8 . There is an account binding relationship between the user account and the first user account; the first user account shares business card information with the target account, including: 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 relationship chain, and will carry all the information of the first identifier. The business card information is shared to the target user account. 8. The method according to claim 7, wherein the first user account shares the business card information with the second user account, comprising: The first user account calls the interface of the second heterogeneous system through the first heterogeneous system, and forwards the business card information encapsulated in a data format conforming to the interface to the second user account. 9. The method according to claim 7, wherein the business card information shared by the first user account with the target account further comprises a second identification determined according to the sharing relationship chain, and the second identification is It is identified that the second user account has the right to add friends to the shared user account. 10. The method according to claim 3, wherein the first user account belongs to a second heterogeneous system, the target account is a target user account, and the target user account is between the target user account and the first user account. For a friend relationship, the business card information shared by the first user account with the target account further includes the first identifier. 11. The method according to claim 3, wherein the first user account belongs to a first heterogeneous system or a second heterogeneous system, the target account is a target group account, and the first user account is a group member in the group corresponding to the target group account, and the business card information shared by the first user account with the target account further includes the first identifier. 12 . The method according to claim 6 , wherein the business card information includes a first identifier added by the first user account. 13 . 13. The method according to claim 3, wherein the first user account belongs to the first heterogeneous system, the target account is a target group account, and the second user account belongs to the second heterogeneous system. There is an account binding relationship between the user account and the first user account, and the second user account is a group member in the group corresponding to the target group account; the first user account shares business cards with the target account information, including: 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 relationship chain, and will carry all the information of the first identifier. The business card information is shared to the target group account. 14. The method of claim 5, wherein the method further comprises: The first user account sends the sharing request to the interworking system; the interworking system has the data processing logic of the first heterogeneous system and the second heterogeneous system; The first user account obtains business card information created according to the sharing request, including: The first user account acquires business card information that is created by the interworking system according to the sharing request and conforms to the data processing logic of the first heterogeneous system and the second heterogeneous system. 15. A user card sharing device, characterized in that the device comprises a first acquiring unit, a display unit, a second acquiring unit and a sharing unit: The first obtaining unit is configured to obtain the user card of the shared user account; the shared user account belongs to the first heterogeneous system; the display unit, used for displaying a target user selection interface; the second obtaining unit, configured to obtain a target account through a selection operation triggered on the target user selection interface; the target account belongs to the second heterogeneous system; The sharing unit is configured to share the user card with the target account. 16. A method for adding friends, characterized in that the method comprises: The target user account belonging to the second heterogeneous system obtains the user card shared by the first user account, and the shared user account belongs to the first heterogeneous system; The target user account initiates a friend addition request to the shared user account according to the user card; The target user account acquires notification information sent from the first heterogeneous system, where the notification information is used to identify that the friend addition request is pushed to the shared user account. 17 . The method according to claim 16 , wherein the user business card is specifically business card information, and the business card information includes a first identifier, and the first identifier is used to identify that the target account has access to the shared user. 18 . Permission to add friends to the account; The adding friend request further includes the first identifier; Before the target user account acquires the notification information sent from the first heterogeneous system, the method further includes: If the target user account is determined by the first identifier to be the user account identified by the target account, or is a group member in the group identified by the target account, execute the target user account acquisition from the first Steps for notification messages from heterogeneous systems. 18 . The method according to claim 17 , wherein the request for adding a friend further comprises a business card identification of the business card information, and the business card information further includes relationship information between accounts involved in sharing the user business card of the shared user account. 19 . before the target user account obtains the notification information, the method further includes: If the target user account is verified as a legitimate user account by the first heterogeneous system and the second heterogeneous system according to the sharing relationship chain, execute the process of obtaining notification information from the second heterogeneous system by the target user account. Step: The sharing relationship chain used by the first heterogeneous system and the second heterogeneous system to verify the legal user account is determined according to the business card identifier. 19. The method according to claim 17 or 18, wherein the method further comprises: The target user account obtains addition success information, and the addition success information is used to identify that the shared user account has added the target user account as a friend according to the friend addition request; The target user account adds the shared user account to a friend relationship list. 20. A device for adding friends, characterized in that the device comprises a first acquiring unit, a sending unit and a second acquiring unit: The first obtaining unit is configured to obtain the user business card shared by the first user account, where the shared user account belongs to the first heterogeneous system; the sending unit, configured to initiate a friend addition request to the shared user account according to the user card; The second acquiring unit is configured to acquire 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. 21. A device, characterized in that the device comprises a processor and a memory: the memory is used to store program code and transmit the program code to the processor; The processor is configured to execute the method of any one of claims 1-14 or 16-19 according to instructions in the program code. 22. A computer-readable storage medium, wherein the computer-readable storage medium is used to store program codes, and the program codes are used to execute the method according to any one of claims 1-14 or 16-19 .