CN113645320B

CN113645320B - Incidence relation establishing method, data interaction method and device

Info

Publication number: CN113645320B
Application number: CN202010394443.9A
Authority: CN
Inventors: 叶军; 赵敏; 汪毅杰; 周亚洲; 翁淼青; 朱俊霖; 周星羽; 金若诗; 杨俊华; 彭扬威; 顾恩睿; 杨威; 朱鸿; 张世梁; 赵世婚; 王新; 杨震
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2020-05-11
Filing date: 2020-05-11
Publication date: 2022-12-20
Anticipated expiration: 2040-05-11
Also published as: CN113645320A

Abstract

The present specification provides an association relationship establishing method, a data interaction method and a device, where the establishing method may include: a first communication application server receives a cross-domain relation establishment application generated by a second communication application server; determining a first real user identifier corresponding to the first virtual user identifier according to a mapping relation between the virtual user identifier and a self-maintained real user identifier, and sending a cross-domain relation confirmation request to a first communication application client; after confirming that the first user carries out confirmation operation, establishing an association relation between the identification corresponding to the second user and the first real user identification; and returning an association relation synchronization notice to the second communication application server so that the second communication application server establishes an association relation between the identifier corresponding to the second user and the first virtual user identifier. By the technical scheme of the specification, cross-domain efficient establishment of association relation and cross-domain interaction of data, and information security and privacy protection of users in the domain can be realized.

Description

Incidence relation establishing method, data interaction method and device

Technical Field

The present disclosure relates to the field of network communication technologies, and in particular, to a method for establishing an association relationship, a method for data interaction, and an apparatus for data interaction.

Background

In order to meet the requirements of network communication, various communication applications are provided in the related technology, and association relations can be established among different users of the same communication application and data interaction can be realized. However, different communication applications are usually deployed in different domains, so that it is difficult to establish an association relationship between different users of different communication applications, and cross-domain data interaction cannot be realized.

Disclosure of Invention

In view of this, the present specification provides an association relationship establishing method, a data interaction method and a data interaction device.

In order to achieve the above purpose, the present specification provides the following technical solutions:

according to a first aspect of the present specification, a method for establishing an association relationship is provided, where the method includes:

a first communication application server receives a cross-domain relationship establishment application, wherein the cross-domain relationship establishment application is generated by a second communication application server in response to a request of a second communication application client, and comprises a first virtual user identifier and an identifier corresponding to a second user logged in the second communication application client;

the first communication application server side determines a first real user identifier corresponding to a first virtual user identifier according to a mapping relation between the virtual user identifier and a real user identifier contained in real user information maintained by the first communication application server side, and sends a cross-domain relation confirmation request to a first communication application client side logged in by a first user corresponding to the first real user identifier;

after determining that the first user performs a confirmation operation on the cross-domain relationship confirmation request, the first communication application server establishes an association relationship between the identifier corresponding to the second user and the first real user identifier;

and the first communication application server returns an association relation synchronization notice to the second communication application server so that the second communication application server establishes an association relation between the identifier corresponding to the second user and the first virtual user identifier.

According to a second aspect of the present specification, there is provided a method for establishing an association relationship, the method including:

a first communication application server receives a cross-domain relationship establishment request sent by a first communication application client, wherein the cross-domain relationship establishment request comprises a first real user identifier corresponding to a first user logged in the first communication application client and a second real user identifier corresponding to a second user;

the first communication application server side determines a first virtual user identifier corresponding to the first real user identifier according to a mapping relation between the virtual user identifier and a real user identifier contained in self-maintained real user information, and sends a cross-domain relation establishment application to a second communication application server side, wherein the cross-domain relation establishment application comprises the identifier corresponding to the first user and the second real user identifier, so that the second communication application function server side sends a corresponding cross-domain relation confirmation request to a second communication application client side logged in by the second user;

the first communication application server responds to the incidence relation synchronization notice returned by the second communication application server, and establishes an incidence relation between the identifier corresponding to the first user and the identifier of the second real user; and the incidence relation synchronous notification is created and sent by the second communication application server after determining that the second user carries out confirmation operation on the cross-domain relation confirmation request, and the incidence relation is established between the identifier corresponding to the first user and the second real user identifier.

According to a third aspect of the present specification, there is provided a data interaction method, the method comprising:

a first communication application server receives a cross-domain data interaction application sent by a second communication application server, wherein the cross-domain data interaction application comprises target data and a first virtual user identifier;

the first communication application server side determines a first real user identifier corresponding to the first virtual user identifier according to a mapping relation between the virtual user identifier and a real user identifier contained in self-maintained real user information;

and the first communication application server side sends the target data to a first communication application client side corresponding to the first real user identification.

According to a fourth aspect of the present specification, there is provided a data interaction method, the method comprising:

a first communication application server receives a data interaction request sent by a first communication application client, wherein the data interaction request comprises target data, a first real user identifier and a second real user identifier;

the first communication application server side determines a first virtual user identifier corresponding to the first real user identifier according to a mapping relation between the virtual user identifier and a real user identifier contained in self-maintained real user information, and generates a cross-domain data interaction application containing the target data, the first virtual user identifier and the second real user identifier;

and the first communication application server sends the cross-domain data interaction application to a second communication application server so that the second communication application server sends the target data to a second communication application client which is corresponding to the second real user identification and is logged in by a second user.

According to a fifth aspect of the present specification, there is provided a data interaction method, the method comprising:

a server of a first instant messaging application receives a cross-domain data interaction application sent by a server of a second instant messaging application, wherein the first instant messaging application is deployed in a first domain, and the second instant messaging application is deployed in a second domain different from the first domain;

the server side of the first instant messaging application determines interactive data contained in the cross-domain data interactive application and a target interactive user indicated by the cross-domain data interactive application;

and the server side of the first instant messaging application sends the interactive data to a client side corresponding to the target interactive user in the first instant messaging application.

According to a sixth aspect of the present specification, an apparatus for establishing an association relation is provided, the apparatus comprising:

the cross-domain relation establishment application comprises a first virtual user identifier and an identifier corresponding to a second user logged in the second communication application client side;

the association request sending unit is used for enabling the first communication application server to determine a first real user identifier corresponding to the first virtual user identifier according to the mapping relation between the virtual user identifier and a real user identifier contained in self-maintained real user information, and sending a cross-domain relation confirmation request to a first communication application client which is logged in by a first user corresponding to the first real user identifier;

a first relationship establishing unit, configured to establish, by the first communication application server, an association relationship between an identifier corresponding to the second user and the first real user identifier after determining that the first user performs a confirmation operation for the cross-domain relationship confirmation request;

and the first relation synchronization unit enables the first communication application server to return an association relation synchronization notice to the second communication application server, so that the second communication application server establishes an association relation between the identifier corresponding to the second user and the first virtual user identifier.

According to a seventh aspect of the present specification, there is provided an apparatus for establishing an association relationship, the apparatus including:

an association request receiving unit, configured to enable a first communication application server to receive a cross-domain relationship establishment request sent by a first communication application client, where the cross-domain relationship establishment request includes a first real user identifier corresponding to a first user logged in the first communication application client and a second real user identifier corresponding to a second user;

an association application sending unit, configured to enable the first communication application server to determine, according to a mapping relationship between a virtual user identifier and a real user identifier included in real user information maintained by the first communication application server, a first virtual user identifier corresponding to the first real user identifier, and send a cross-domain relationship establishment application to a second communication application server, where the cross-domain relationship establishment application includes an identifier corresponding to the first user and the second real user identifier, so that the second communication application function server sends a corresponding cross-domain relationship confirmation request to a second communication application client logged in by the second user;

a second relationship establishing unit, configured to enable the first communication application server to respond to an association relationship synchronization notification returned by the second communication application server, and establish an association relationship between an identifier corresponding to the first user and the second real user identifier; and the association relation synchronization notification is created and sent by the second communication application server after determining that the second user performs a confirmation operation on the cross-domain relation confirmation request, and establishing an association relation between the identifier corresponding to the first user and the second real user identifier.

According to an eighth aspect of the present specification, there is provided a data interaction apparatus, comprising:

the system comprises an interactive application receiving unit, a first communication application server and a second communication application server, wherein the interactive application receiving unit enables the first communication application server to receive a cross-domain data interactive application sent by the second communication application server, and the cross-domain data interactive application comprises target data and a first virtual user identifier;

the virtual identification determining unit is used for enabling the first communication application server to determine a first real user identification corresponding to the first virtual user identification according to the mapping relation between the virtual user identification and the real user identification contained in the self-maintained real user information;

and the target data sending unit enables the first communication application server to send the target data to a first communication application client corresponding to the first real user identifier.

According to a ninth aspect of the present specification, there is provided a data interaction apparatus, the apparatus comprising:

the interactive request receiving unit enables the first communication application server side to receive a data interactive request sent by the first communication application client side, wherein the data interactive request comprises target data, a first real user identifier and a second real user identifier;

the interactive application generating unit is used for enabling the first communication application server to determine a first virtual user identifier corresponding to the first real user identifier according to a mapping relation between the virtual user identifier and a real user identifier contained in self-maintained real user information, and generating a cross-domain data interactive application containing the target data, the first virtual user identifier and the second real user identifier;

and the interaction application sending unit enables the first communication application server to send the cross-domain data interaction application to a second communication application server so that the second communication application server sends the target data to a second communication application client which is corresponding to the second real user identification and is logged in by a second user.

According to a tenth aspect of the present specification, there is provided a data interaction apparatus, comprising:

an application receiving unit, which enables a server of a first instant messaging application to receive a cross-domain data interaction application sent by a server of a second instant messaging application, wherein the first instant messaging application is deployed in a first domain, and the second instant messaging application is deployed in a second domain different from the first domain;

a target determining unit, configured to enable a server of the first instant messaging application to determine interactive data included in the cross-domain data interaction application and a target interaction user indicated by the cross-domain data interaction application;

and the data sending unit enables the server side of the first instant messaging application to send the interactive data to the client side corresponding to the target interactive user in the first instant messaging application.

According to an eleventh aspect of the present specification, there is provided an electronic apparatus comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to implement the steps of the method according to any one of the aspects of the first aspect to the fifth aspect.

According to a twelfth aspect of the present description, there is provided a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method according to any one of the aspects of the first to fifth aspects.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the related art, the drawings used in the description of the embodiments or the related art will be briefly described below, and it is obvious for those skilled in the art to obtain other drawings without any creative effort.

Fig. 1 is a schematic diagram of an architecture of cross-domain communication according to an exemplary embodiment of the present disclosure.

Fig. 2 is a flowchart illustrating a method for establishing an association relationship according to an exemplary embodiment of the present disclosure.

Fig. 3 is a flowchart illustrating another association relationship establishing method according to an exemplary embodiment of the present disclosure.

FIG. 4 is a flow chart illustrating a method of data interaction in an exemplary embodiment of the present description.

FIG. 5 is a flow chart illustrating another method of data interaction in an exemplary embodiment of the present description.

FIG. 6 is a flow chart illustrating yet another method of data interaction in an exemplary embodiment of the present description.

Fig. 7 is an interaction flowchart of an association relationship establishing method according to an exemplary embodiment of the present specification.

Fig. 8-10 are schematic diagrams of a client-side presentation interface shown in an exemplary embodiment of the present specification.

Fig. 11 is an interaction flowchart of another association relationship establishing method shown in an exemplary embodiment of this specification.

FIG. 12 is an interaction flow diagram illustrating a data interaction method in an exemplary embodiment of the present specification.

FIG. 13 is an interaction flow diagram illustrating another method of data interaction, according to an exemplary embodiment of the present description.

Fig. 14 is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present disclosure.

Fig. 15 is a block diagram of an association relationship establishing apparatus according to an exemplary embodiment of the present specification.

Fig. 16 is a block diagram of another association relationship establishing apparatus according to an exemplary embodiment of the present specification.

Fig. 17 is a block diagram illustrating a data interaction device according to an exemplary embodiment of the present specification.

Fig. 18 is a block diagram of another data interaction device shown in an exemplary embodiment of the present specification.

Fig. 19 is a block diagram illustrating yet another data interaction device in an exemplary embodiment of the present specification.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.

The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first communication application may also be referred to as the second communication application, and similarly, the second communication application may also be referred to as the first communication application, and the like, without departing from the scope of the present description. The word "if," as used herein, may be interpreted as "at … …" or "at … …" or "in response to a determination," depending on the context.

Fig. 1 is a schematic diagram of a cross-domain communication architecture according to an exemplary embodiment of the present disclosure. AS shown in fig. 1, the system may include several user equipments (such AS handset A1, handset An, etc.) belonging to domain a and a server AS, and several user equipments (such AS handset B1, handset Bm, etc.) belonging to domain B and a server BS. From the perspective of application software, the user equipment is provided with a communication application client, and the server is provided with a communication application server.

The server AS and the server BS may be physical servers comprising an independent host, or the server AS and the server BS may be virtual servers carried by a cluster of hosts, or the server AS and the server BS may be cloud servers. During operation, the server AS and the server BS may respectively operate server-side programs of different communication applications to implement related service functions of each communication application, for example, when the server AS or the server BS operates a communication program in related technologies, the server AS or the server BS may be configured AS a server for implementing a communication function in related technologies; when the server AS and the server BS run the related communication program established by the association relationship described in this specification, the server AS and the server BS may be configured AS a server for implementing the communication function established by the association relationship described in this specification; when the server AS and the server BS run the related communication program for data interaction described in this specification, the server AS and the server BS may be configured AS a server for implementing the communication function for data interaction described in this specification.

Handsets A1-Bm are just one type of user equipment that the user may use. In fact, it is obvious that the user can also use electronic devices of the type such as: tablet devices, notebook computers, personal Digital Assistants (PDAs), wearable devices (such as smart glasses, smart watches, etc.), etc., which are not limited in this specification. During operation, the user equipment may operate a client-side program of the communication application to implement a related service function of the communication application, for example, when the electronic equipment operates a related communication program established by an association relationship, the electronic equipment may be configured as a client for implementing the association relationship establishment function.

And the network for interaction among the above devices may include various types of wired or wireless networks. In an embodiment, the Network may include a Public Switched Telephone Network (PSTN) and the internet, and may also include a near field wireless communication Network such as WIFI, bluetooth, and the like, which is not limited in this specification.

It can be seen that, in the implementation process of the technical solution of the present specification, intra-domain interaction between the client and the server corresponding to the same communication application and cross-domain interaction between the servers corresponding to different communication applications are involved. The technical solution of the present specification will be described below from the processing logic and the interaction process of each party, respectively.

Fig. 2 is a flowchart of an association relationship establishing method provided in an exemplary embodiment of the present specification. As shown in fig. 2, the method applied to the first communication application server may include the following steps:

step 202, the first communication application server receives a cross-domain relationship establishment application, the cross-domain relationship establishment application is generated by the second communication application server in response to a request of the second communication application client, and the cross-domain relationship establishment application comprises a first virtual user identifier and an identifier corresponding to a second user logged on the second communication application client.

In an embodiment, one of the first communication application corresponding to the first communication application server and the second communication application corresponding to the second communication application server is deployed in a public domain, and the other is deployed in a private domain, so as to establish an association relationship between a public domain user identifier and a private domain user identifier.

In an embodiment, the second communication application server may maintain second real user information corresponding to the second user, where the real user information may include a second real user identifier, and thus, as an exemplary embodiment, the identifier corresponding to the second user may include the second real user identifier, so that the first communication application server establishes an association relationship between the second real user identifier and the first real user identifier, thereby implementing a more direct association relationship. As another exemplary embodiment, the identifier corresponding to the second user may also include a second virtual user identifier having a mapping relationship with the second real user identifier, so that the first communication application server establishes an association relationship between the second virtual user identifier and the first real user identifier, thereby enabling the first user to acquire as little user information of the second user as possible, and ensuring privacy security of the second user corresponding to the user mapping relationship.

In an embodiment, the first communication application server may receive, before receiving the cross-domain relationship establishment application, a first user information acquisition request sent by the second communication application server, and then return, as a response to the request, to the second communication application server, first virtual user information and a standard verification identifier that include a first virtual user identifier, where the first virtual user information is displayed in a relationship application interface on the second communication application client, and the relationship application interface is used for triggering to generate the cross-domain relationship establishment application.

The standard verification identifier can be stored locally by a second communication application server so as to generate a cross-domain relationship establishment application containing the standard verification identifier; the standard verification identifier may also be forwarded to the second communication application client by the second communication application server, so that the client generates a cross-domain relationship establishment request including the standard verification identifier and sends the cross-domain relationship establishment request to the second communication application server. And the first communication application server compares the to-be-verified identification contained in the application with the standard verification identification after receiving the cross-domain relationship establishment application, and if the to-be-verified identification is matched with the standard verification identification, the cross-domain relationship establishment application is generated based on the standard verification identification sent to the second communication application server, namely the cross-domain relationship establishment application corresponds to the user information acquisition request. At this time, the first communication application server may match the identifier to be verified with the standard verification identifier as a precondition for the first communication application server to establish an association relationship between the second user identifier and the first virtual user information, thereby ensuring consistency and consistency between the first user information acquisition request and the cross-domain relationship establishment application, and avoiding cross-domain establishment of an association relationship between other user applications not applying for the first user information and the first user.

Step 204, the first communication application server determines a first real user identifier corresponding to the first virtual user identifier according to a mapping relationship between the virtual user identifier and a real user identifier contained in real user information maintained by the first communication application server, and sends a cross-domain relationship confirmation request to a first communication application client logged in by a first user corresponding to the first real user identifier.

In an embodiment, the virtual user identifier and the real user identifier are configured differently. Specifically, the content of the virtual user identifier may be more than that of the real user identifier. For example, the virtual user identifier may include a user identifier of a corresponding user, an organization identifier corresponding to an organization architecture to which the user belongs, and a domain identifier and/or domain information of a domain in which the user is located; the real user id may only include the user id of the user. Because the content of the virtual user identifier is more than that of the real user identifier, the user identifier maintained by any communication application server side is ensured to accurately correspond to users of other communication applications. The above-mentioned identification may include ID, name, etc., and this specification does not limit this.

Step 206, after determining that the first user performs a confirmation operation on the cross-domain relationship confirmation request, the first communication application server establishes an association relationship between the identifier corresponding to the second user and the first real user identifier.

In an embodiment, the first communication application server may generate first virtual user information corresponding to the first virtual user identifier based on first real user information corresponding to the first user, where the first virtual user information includes at least a part of content of the first real user information; the first virtual user information may then be synchronized to a second communication application server. The first communication application server generates first virtual user information only containing partial content of the first real user information and synchronizes to the second communication application server, so that the first virtual user information maintained by the second communication application server is partial information of the first user.

Further, the synchronization process of the first virtual user information may be performed before the association relationship is established, and the first virtual user information may include basic user information of the first user. The synchronization process of the first virtual user information may be performed after the association relationship is established, and the first virtual user information may include basic user information and extended user information of the first user. Further, the extended user information may include privacy information of the first user. Through two times of synchronization before and after the establishment of the association relationship, the first user virtual information stored by the second communication application server only comprises the basic information of the first user before the establishment of the association relationship, and the first user virtual information not only comprises the basic information of the first user but also comprises the extended user information after the establishment of the association relationship.

In an embodiment, the association relationship may include any one of: friend relationships, session relationships, special attention relationships.

And 208, the first communication application server returns an association relation synchronization notification to the second communication application server, so that the second communication application server establishes an association relation between the identifier corresponding to the second user and the first virtual user identifier.

In an embodiment, the first communication application server may add an application type mark to the address book contact information corresponding to the first user, so as to indicate whether the real user information corresponding to the corresponding address book contact information is maintained by the first communication application server, and indicate the first communication application client to perform differentiated display on the address book contact information corresponding to different application type marks. It can be understood that the address book contact corresponding to the first user with the labeled contact information is a contact in other communication applications (not the first communication application). By adding marks to the contact information, the first communication application client can distinguish and display the first communication application contact and other communication application contacts, so that the first user can conveniently know the communication application to which the contact belongs, the first user can conveniently communicate with the first user in a targeted manner, and the communication efficiency of the first user is improved.

In another embodiment, the first communication application server may further add an application type mark to the communication session in which the first user participates, to indicate whether the real user information corresponding to the participants of the corresponding communication session is maintained by the first communication application server, and indicate the first communication application client to perform differentiated display on the session window of the communication session corresponding to the different application type marks. It will be appreciated that the tagged first user may be involved in a session involving a user in another messaging application (not the first messaging application). By adding marks to the conversation, the first communication application client can distinguish and display different conversations participated by users in different communication applications, so that the first user can conveniently know whether users belonging to other communication applications except the first communication application exist in conversation participants, the first user can conveniently participate in the conversation in a targeted manner, and the first user can be prevented from making mistakes in the conversation process.

In fact, the type mark may be added to the contact person or the session in the address book at any time after the contact person is added or the session is established, and the adding time of the type mark is not limited in this specification.

Further, under the condition that the application type mark indicates that the real user information corresponding to the participants of the corresponding communication session is maintained by the first communication application server, the application type mark is used for indicating the first communication application client to display the session window of the corresponding communication session on a first-level interface of the session list; and under the condition that the application type mark indicates that the real user information corresponding to at least one participant of the corresponding communication session is not maintained by the first communication application server, the application type mark is used for indicating the first communication application client to display the session window of the corresponding communication session on a secondary interface of the session list. The mark is added to the conversation, the client is indicated to display the conversation list area in the primary interface and the secondary interface in a differentiated mode, conversation windows of users who have conversation of other communication applications which are not the first communication application in conversation participants are displayed on the secondary interface in a centralized mode, the conversation list is prevented from being complicated due to the fact that all the conversation windows are displayed in a non-differentiated mode, and then the communication efficiency of the first user is improved to a certain extent.

In this embodiment, the first communication application server maintains a real user identifier included in the real user information and a mapping relationship between the real user identifier and the virtual user identifier. On one hand, the first communication application server side can search the first real user identification corresponding to the first virtual user identification contained in the cross-domain relationship establishment application through the mapping relationship, so that the one-to-one correspondence between the virtual user identification and the real user identification is realized, and the accurate and efficient response to the cross-domain relationship establishment application is further realized. On the other hand, the second communication application server only needs to acquire the first virtual user identifier of the first user and does not need other user information of the first user to complete the establishment of the association relationship, so that the information safety and privacy protection of the first user are realized through the isolation effect of the virtual user identifier.

Fig. 3 is a flowchart of another association relationship establishing method provided in an exemplary embodiment of the present specification. As shown in fig. 3, the method is applied to the first communication application server, and may include the following steps:

step 302, a first communication application server receives a cross-domain relationship establishment request sent by a first communication application client, where the cross-domain relationship establishment request includes a first real user identifier corresponding to a first user logged in the first communication application client and a second real user identifier corresponding to a second user.

Step 304, the first communication application server determines a first virtual user identifier corresponding to the first real user identifier according to a mapping relationship between the virtual user identifier and a real user identifier contained in real user information maintained by the first communication application server, and sends a cross-domain relationship establishment application to a second communication application server, where the cross-domain relationship establishment application includes an identifier corresponding to the first user and the second real user identifier, so that the second communication application function server sends a corresponding cross-domain relationship confirmation request to a second communication application client logged in by the second user.

In an embodiment, the virtual user identifier and the real user identifier are configured differently. Specifically, the content contained in the virtual user identifier may be more than the content contained in the real user identifier. For example, the virtual user identifier may include a user identifier of a corresponding user, an organization identifier corresponding to an organization architecture to which the user belongs, and a domain identifier and/or domain information of a domain in which the user is located; the real user id may only include the user id of the user. Because the content of the virtual user identifier is more than that of the real user identifier, the user identifier maintained by any communication application server side is ensured to accurately correspond to users of other communication applications. The above-mentioned identification may include ID, name, etc., and this specification does not limit this.

In an embodiment, the first communication application server may maintain first real user information corresponding to the first user, where the real user information may include a first real user identifier, and thus, as an exemplary embodiment, the identifier corresponding to the first user may include the first real user identifier, so that the second communication application server establishes an association relationship between the first real user identifier and the second real user identifier, thereby implementing a more direct association relationship. As another exemplary embodiment, the identifier corresponding to the first user may also include a first virtual user identifier that has a mapping relationship with the first real user identifier, so that the second communication application server establishes an association relationship between the first virtual user identifier and the second real user identifier, so that the second user knows as little user information of the first user as possible, and privacy security of the first user corresponding to the user mapping relationship is ensured.

In an embodiment, the first communication application server may send a second user information obtaining request to the second communication application server before sending the cross-domain relationship establishment application, and then receive second virtual user information and a standard verification identifier, which are returned by the second communication application server in response to the request and include a second virtual user identifier corresponding to the second virtual user identifier, where the second virtual user information is displayed in a relationship application interface on the first communication application client, the relationship application interface is used for triggering to generate the cross-domain relationship establishment application, and the standard verification identifier is used by the second communication application server to verify whether the standard verification identifier matches a to-be-verified identifier included in the cross-domain relationship establishment application.

The second communication application server side can store the standard verification identifier locally so as to generate a cross-domain relation establishment application containing the standard verification identifier; the standard verification identifier may also be forwarded to a second communication application client, so that the client generates a cross-domain relationship establishment request including the standard verification identifier and sends the cross-domain relationship establishment request to the second communication application server. And the second communication application server compares the to-be-verified identification contained in the application with the standard verification identification after receiving the cross-domain relationship establishment application, and if the to-be-verified identification is matched with the standard verification identification, the cross-domain relationship establishment application is generated based on the standard verification identification sent to the second communication application server, namely the cross-domain relationship establishment application corresponds to the user information acquisition request. At this time, the second communication application server may match the standard verification identifier with the identifier to be verified as a precondition for the second communication application server to establish an association relationship between the identifier corresponding to the first user and the second real user identifier, thereby ensuring consistency and consistency between the second user information acquisition request and the cross-domain relationship establishment application, and avoiding cross-domain establishment of an association relationship between other user applications not applying for the second user information and the second user.

Step 306, the first communication application server side responds to the incidence relation synchronization notice returned by the second communication application server side, and establishes incidence relation between the identifier corresponding to the first user and the second real user identifier; and the association relation synchronization notification is created and sent by the second communication application server after determining that the second user performs a confirmation operation on the cross-domain relation confirmation request, and establishing an association relation between the identifier corresponding to the first user and the second real user identifier.

In an embodiment, the first communication application server receives second virtual user information corresponding to a second real user identifier and synchronized by a second communication application server; the second virtual user information is generated by the second communication application server side based on second real user information corresponding to the second user, and the second virtual user information comprises at least part of content of the second real user information. And the second communication application server generates second virtual user information only containing partial content in the second real user information and synchronizes the second virtual user information to the first communication application server, so that the second virtual user information maintained by the first communication application server is partial information of the second user.

Further, the synchronization process of the second virtual user information may be performed before the association relationship is established, and the second virtual user information may include the basic user information of the second user. The synchronization process of the second virtual user information may be performed after the association relationship is established, and the second virtual user information may include basic user information and extended user information of the second user. Further, the extended user information may include privacy information of the second user. Through two times of synchronization before and after the association relationship is established, the second user virtual information stored by the first communication application server only contains the basic information of the second user before the association relationship is established, and after the association relationship is established, the second user virtual information not only contains the basic information of the second user but also contains the extended user information.

Fig. 4 is a flowchart of a data interaction method provided in an exemplary embodiment of the present specification. As shown in fig. 4, the method is applied to the first communication application server, and may include the following steps:

step 402, a first communication application server receives a cross-domain data interaction application sent by a second communication application server, wherein the cross-domain data interaction application comprises target data and a first virtual user identifier.

In an embodiment, the cross-domain data interaction application is generated by the second communication application client, and the cross-domain data interaction application further includes an identifier corresponding to the second user logged on the second communication application client, at this time, the first communication application server may determine, according to the identifier corresponding to the second user, a data interaction permission of the second user for the first user corresponding to the first real user information; and then, under the condition that the second user has the data interaction authority aiming at the first user, the target data is sent to the first communication application client. It can be seen that, the first communication application server actually uses the data interaction permission that the second user has for the first user as a precondition for sending the target data to the first communication application client, that is, only when the first user has the data interaction permission for the second user, the first user can implement data interaction with the second user, thereby ensuring data transmission order among different users of different communication applications and avoiding occurrence of malicious data interaction events.

Further, the first communication application server may determine that the second user has the data interaction authority for the first user when the first communication application server maintains the association relationship established between the identifier corresponding to the second user and the first real user information. At the moment, cross-domain data interaction between different users with established association relation is allowed, and the pertinence of the cross-domain data interaction is ensured.

Further, as an exemplary embodiment, the association relationship between the second user identifier and the first real user information may be established based on the establishment method of the association relationship. Or, as another exemplary embodiment, in order to implement fast and efficient establishment of the association relationship and avoid repeated operations, the association relationship between the second user identifier and the first real user information may be established by the second communication application server and then migrated from the second communication application server to the first communication application server.

Step 404, the first communication application server determines a first real user identifier corresponding to the first virtual user identifier according to a mapping relationship between the virtual user identifier and a real user identifier contained in the real user information maintained by the first communication application server.

In an embodiment, the identifier corresponding to the second user may include a second real user identifier included in second real user information corresponding to the second user, which is maintained by the second communication application server, or a second virtual user identifier having a mapping relationship with the second real user identifier.

In an embodiment, the second communication application server may maintain second real user information corresponding to the second user, where the real user information may include a second real user identifier. As an exemplary embodiment, the identifier corresponding to the second user may include the identifier of the second real user; as another exemplary embodiment, the identifier corresponding to the second user may also include a second virtual user identifier having a mapping relationship with the second real user identifier, so that the first communication application server sends the target data to the first communication application client corresponding to the first real user identifier, so that the first user knows as little user information of the second user as possible, and privacy and security of the second user corresponding to the user mapping relationship are ensured.

Step 406, the first communication application server sends the target data to a first communication application client corresponding to the first real user identifier.

In an embodiment, in order to facilitate the second user to know the interaction result of the target data in time, after the target data is sent, the first communication application server may return the cross-domain data interaction result to the second communication application server, so that the second communication application client displays the cross-domain data interaction result to the second user.

In this embodiment, the first communication application server maintains a real user identifier included in the real user information and a mapping relationship between the real user identifier and the virtual user identifier. Therefore, on one hand, the first communication application server can search the first real user identifier corresponding to the first virtual user identifier included in the cross-domain data interaction application through the mapping relation, so that one-to-one correspondence between the virtual user identifier and the real user identifier is realized, and accurate and efficient response to the cross-domain relation establishment application is further realized. On the other hand, the second communication application server side can realize the data interaction only by acquiring the first virtual user identifier of the first user and without needing other user information of the first user, so that the information safety and privacy protection of the first user are realized through the isolation effect of the virtual user identifier.

Fig. 5 is a flowchart of another data interaction method provided in an exemplary embodiment of the present specification. As shown in fig. 5, the method is applied to the first communication application server, and may include the following steps:

step 502, a first communication application server receives a data interaction request sent by a first communication application client, where the data interaction request includes target data, a first real user identifier, and a second real user identifier.

In an embodiment, after receiving the data interaction request, the first communication application server may query whether an association relationship exists between the first real user identifier and the second real user identifier, and use the association relationship between the first real user identifier and the second real user identifier as a precondition for sending the cross-domain data interaction application to the second communication application server. At this time, only under the condition that the incidence relation between the first real user identifier and the second real user identifier exists, the first user can realize data interaction with the second user, the data transmission orderliness between different users of different communication applications is ensured, and the occurrence of malicious data interaction events is avoided.

In an embodiment, one of the first communication application corresponding to the first communication application server and the second communication application corresponding to the second communication application server is deployed in a public domain, and the other is deployed in a private domain, so as to implement data interaction between a public domain user and a private domain user.

Step 504, the first communication application server determines, according to a mapping relationship between a virtual user identifier and a real user identifier included in real user information maintained by the first communication application server, a first virtual user identifier corresponding to the first real user identifier, and generates a cross-domain data interaction application including the target data, the first virtual user identifier, and the second real user identifier.

Step 506, the first communication application server sends the cross-domain data interaction application to a second communication application server, so that the second communication application server sends the target data to a second communication application client, where a second user corresponding to the second real user identifier logs in, of the second communication application client.

In an embodiment, in order to facilitate the first user to know the interaction result of the target data in time, the first communication application server may receive the cross-domain data interaction result returned by the second communication application server; and then forwarding the cross-domain data interaction result to the first communication application client so that the first communication application client displays the cross-domain data interaction result to the first user.

In this embodiment, the first communication application server maintains a real user identifier included in the real user information and a mapping relationship between the real user identifier and the virtual user identifier. Therefore, on one hand, the first communication application server can search the first virtual user identifier corresponding to the first real user identifier included in the data interaction request through the mapping relation, so that one-to-one correspondence between the real user identifier and the virtual user identifier is realized, and the cross-domain data interaction application is further accurately and efficiently generated and sent. On the other hand, the first communication application server only needs to include the first virtual user identifier of the first user in the cross-domain data interaction application, so that the second communication application server only can acquire the first virtual user identifier of the first user and cannot acquire other user information of the first user, and information safety and privacy protection of the first user are achieved through the isolation effect of the virtual user identifier.

Fig. 6 is a flowchart of another data interaction method provided in an exemplary embodiment of the present specification. As shown in fig. 6, the method applied to the first communication application server may include the following steps:

step 602, a server of a first instant messaging application receives a cross-domain data interaction application sent by a server of a second instant messaging application, wherein the first instant messaging application is deployed in a first domain, and the second instant messaging application is deployed in a second domain different from the first domain.

Step 604, the server of the first instant messaging application determines the interactive data included in the cross-domain data interactive application and the target interactive user indicated by the cross-domain data interactive application.

Step 606, the server of the first instant messaging application sends the interaction data to the client corresponding to the target interaction user in the first instant messaging application.

In an embodiment, the cross-domain data interaction application may be established by the server of the second instant messaging application based on a data interaction request sent by the client of the second instant messaging application. The interactive data included in the cross-domain data interaction application may be included in the data interaction request and sent to a server of a second instant messaging application, or the client of the second instant messaging application may send the interactive data to the server of the second instant messaging application in association with the data interaction request, or the server of the second instant messaging application may actively obtain the interactive data from a storage location specified by the request after receiving the data interaction request, which is not limited in the present application. After the client of the second instant messaging application sends out the data interaction request, the server of the second instant messaging application establishes a corresponding cross-domain data interaction application based on the request, so that the cross-domain data interaction request of the initiator user of the data interaction request is effectively responded.

Under different application scenarios, the interaction data included in the cross-domain data interaction application is different. In an embodiment, corresponding to a cross-domain association relationship establishment scenario between different instant messaging applications, the interaction data is used by a client corresponding to a first instant messaging application to display a relationship establishment confirmation interface, and the target interaction user may implement a trigger operation for the interface, where the trigger operation is used to indicate whether to establish an association relationship between an initiator user and a target interaction user of the data interaction request. Therefore, the server of the first instant messaging application and/or the server of the second instant messaging application can establish an association relationship between the target interaction user and the target interaction user based on the trigger operation implemented by the target interaction user aiming at the relationship establishment confirmation interface.

Specifically, the server of the first instant messaging application may establish an association relationship between a real user identifier of an initiator user of the data interaction request and a real user identifier of the target interaction user, or may establish an association relationship between a virtual user identifier of the initiator user of the data interaction request and a real user identifier of the target interaction user. Correspondingly, the server of the second instant messaging application may establish an association between the real user identifier of the initiator user of the data interaction request and the real user identifier of the target interaction user, or may establish an association between the real user identifier of the initiator user of the data interaction request and the virtual user identifier of the target interaction user.

In another embodiment, the interaction data may be an instant messaging message sent by an initiator user of a data interaction request to a target interaction user, corresponding to a cross-domain instant messaging message interaction scenario among different instant messaging applications. At this time, the initiator user of the data interaction request corresponding to the first instant messaging application is a sender of the instant messaging message, and the target interaction user corresponding to the second instant messaging application is a receiver of the instant messaging message, so that the interaction of the cross-domain instant messaging message is realized between the initiator user and the target interaction user of the data interaction request through the above manner.

In the technical scheme of the present specification, any cross-domain association relationship establishment process can adopt the association relationship establishment scheme of the present specification, and belongs to the protection scope of the technical scheme of the present specification; for example, the established association may include: friend relationships, session relationships, special attention relationships, and the like. Taking the establishment of the friend relationship as an example, in a more specific scenario, the technical solution of the present specification may be applied to a friend adding process, for example, a first user scans a two-dimensional code of a business card of a second user through a first communication application client to add the second user as a friend, that is, a friend relationship is established between the first user and the second user.

For convenience of understanding, the following describes a technical solution of this specification with reference to an interaction flowchart of the association relationship establishing method shown in fig. 7 by taking a scenario of establishing the foregoing friend relationship under the network architecture shown in fig. 1 as an example. AS can be seen from fig. 1, the client A1 and the server AS corresponding to the communication application a belong to a domain a, and the client B1 and the server BS corresponding to the communication application B belong to a domain B.

In this embodiment, the server AS maintains the complete user information of the client A1 and the virtual user identifier of the client B1, and similarly, the server BS maintains the complete user information of the client B1 and the virtual user identifier of the client A1. The process of establishing the friend relationship may include the following steps:

in step 701, a client A1 sends a user information acquisition request to a server BS through a server AS.

In an embodiment, the client A1 may trigger sending the user information obtaining request by scanning the related information of the user B1. Specifically, the user A1 may invoke a scanning function of the client A1 by triggering a scanning control displayed in a contact list of the client A1, and then invoke an image acquisition component of the user equipment A1 to scan relevant information of the user B1, where the relevant information may be a business card of the user B1, an account two-dimensional code in an entity form, a two-dimensional code displayed in a display medium, and the like. The user A1 may also execute a preset trigger operation for the user equipment A1 itself to save or receive the related information of the user B1, to call the client A1 to scan, for example, call a two-dimensional code recognition function of the client A1 by long-pressing an account two-dimensional code picture of the user B1. After scanning the user information, the client A1 sends a user information acquisition request about the user B1 to the server BS through the server AS.

In another embodiment, the user A1 may trigger sending the user information acquisition request by inputting the user information of the user B1. Specifically, the user A1 may search the user B1 through a contact search interface in the client A1 in the form of a mobile phone number, a communication application account, and the like, where the search process is to send a user information acquisition request about the user B1 to the server BS through the server AS.

The user information acquisition request may include identification information of the serving BS, so AS to inform the serving AS to forward the user information acquisition request to the serving BS.

In step 702, the server BS generates the virtual user information of the user B1 logged in the client B1.

The server BS may search the user B1 corresponding to the request and generate the virtual user information of the user B1 based on the user identifier, the user number, and other information of the user B1 included in the user information acquisition request.

Specifically, the serving BS may provide partial user information from the maintained complete user information of the user B1 according to a preset rule to generate the virtual user information of the user B1. For example, the complete user information may include a user ID, a creation time, a nickname, a gender, an address, a signature, etc., and in this case, only the user ID may be extracted as the virtual user information of the user B1, or basic user information constituted by other extracted partial information may be used as the virtual user information, which is not limited in this specification.

In an embodiment, to implement validity verification of a subsequent friend addition request, the serving BS may further generate a standard verification identifier, for example, a random number generated according to a preset rule, for the user information acquisition request.

Step 703, the service end BS returns the virtual user information to the client A1 through the service end AS.

The server BS may return the virtual user identifier of the user B1 to the client A1 through the server AS, or may associate the virtual user identifier of the user B1 with the standard verification identifier through the server AS and return to the client A1.

In fact, before the user A1 applies for adding the user B1 as a friend, the service end A1 may not yet maintain the virtual user information of the user B1, so after receiving the virtual user information of the user B1 returned by the service end BS, the service end A1 may store the information locally and maintain the information, and directly return the virtual user information of the user B1 to the client Ai when the subsequent other users Ai apply for adding the user B1 as a friend, so as to reduce the user response time and the waiting time of the user Ai as much as possible.

Even more, the user information of the user B1 scanned by the client may include the corresponding virtual user information, and at this time, the steps 701 to 703 may not be executed.

In step 704, the client A1 displays the virtual user information in a friend adding interface of the user B1.

After receiving the virtual user identifier of the user B1, the client A1 may display the virtual user identifier in a friend addition interface for the user A1 to view. Specifically, the information content included in the virtual user identifier may be displayed according to a preset format. The friend adding interface may include a friend adding control, where the friend adding control is used to receive a trigger instruction corresponding to a preset trigger operation of the user A1 — when the user A1 performs the preset trigger operation for the friend adding control, it may be determined that the user A1 wants to add the user B1 as a friend.

In an embodiment, the server BS may return the virtual user information of the user B1 including the basic user information to the server AS before the friend relationship between the user A1 and the user B1 is established, and at this time, the client A1 may show the virtual user information of the user B1, with an effect shown in fig. 7 (a). Correspondingly, the service end BS may return the virtual user information of the user B1 including the basic user information and the extension information to the service end AS after the friend relationship between the user A1 and the user B1 is established, so AS to update the virtual user information of the user B1. The extended information may be the gender, the contact information, the unit name, the position, and the like of the user B1, and at this time, the client A1 may display the virtual user information of the user B1, with the effect shown in fig. 7 (B) in fig. 7.

The duration for the client A1 to display the friend adding interface is not limited in this specification, that is, after the client A1 displays the friend adding interface, the user A1 may execute the preset triggering operation on the friend adding control at any time.

Step 705, the client A1 sends a friend addition request to the server AS.

After the user A1 implements a preset triggering operation for the friend adding control, the client A1 generates a friend adding request for the user B1, and sends the request to the server AS. The friend addition request includes the real user identifier of the user A1 and the virtual user identifier of the user B1, and may further include the standard verification identifier obtained from the server BS.

Step 706, query the virtual user id of user A1.

The service side AS maintains the complete user information of the client side A1 and the mapping relation between the real user identification and the virtual user identification of the user A1. Therefore, the server AS may query the virtual user identifier of the user A1 based on the real user identifier of the user A1 included in the friend addition request.

If the virtual user id of the user A1 is found, the process goes to step 707 directly. Otherwise, if the virtual user identifier of the user A1 is not queried, it indicates that the mapping relationship between the real user identifier of the user A1 and the virtual user identifier has not been maintained in the server AS, at this time, the virtual user identifier of the user A1 may be directly generated according to the complete user information of the protected user A1, and then step 707 is performed.

In step 707, the server AS sends a friend addition application about the user B1 to the server BS.

The service side AS can generate a friend adding request of the user A1 for the user B1 based on the inquired virtual user information and send the request to the service side BS. The friend addition request may include the virtual user identifier of the user A1 and the virtual user identifier of the user B1, and may further include the standard verification identifier obtained from the server BS.

In step 708, the server BS verifies the friend add application about the user B1.

After receiving the friend addition application, the service terminal BS may perform validity verification on the application. Specifically, since the verification identifier included in the friend addition application is not necessarily a standard verification identifier, the verification identifier included in the friend addition application is a to-be-verified identifier with respect to the service BS. At this time, the service end BS may extract the to-be-verified identifier from the application, and then compare the to-be-verified identifier with the standard verification identifier generated by the service end BS in step 702: if the to-be-verified identifier matches the standard verification identifier, it indicates that the friend addition application is generated based on the user information acquisition request, and therefore it is determined that the application is legal, and step 709 is performed. Otherwise, if the to-be-verified identifier does not match the standard verification identifier, it indicates that the friend addition application is not generated (possibly tampered) based on the user information acquisition request, and therefore it is determined that the application is illegal, and a subsequent response process to the application is directly stopped. A friend addition failure message can also be returned to the client A1 through the server AS to inform the user A1 that friend addition fails.

In step 709, the server BS queries the real user id of the user B1.

The server BS itself maintains the complete user information of the client B1 and the mapping relationship between the real user identifier and the virtual user identifier of the user B1. Therefore, the server BS may query the real user id of the user B1 based on the virtual user id of the user B1 included in the friend addition request.

In step 710, the server BS sends a friend addition confirmation request to the client B1.

The server BS may send a friend addition confirmation request to the client B1 corresponding to the user B1 based on the queried real user identifier of the user B1. The request may include the virtual user identification of user A1.

In step 711, the client B1 receives a friend addition confirmation instruction of the user B1.

After receiving the friend addition confirmation request, the client B1 may display the virtual user identifier included in the request in a friend addition confirmation interface according to a preset format, so that the virtual user identifier is viewed by the user B1.

The friend addition confirmation interface may include a friend addition confirmation control, where the friend addition confirmation control is used to receive a trigger instruction corresponding to a preset trigger operation of the user B1, and when the user B1 performs the preset trigger operation on the friend addition confirmation control, it may be determined that the user B1 agrees that the addition user A1 is a friend.

The duration of the client B1 displaying the friend addition confirmation interface is not limited in this specification, that is, after the client B1 displays the friend addition confirmation interface, the user B1 may execute the preset trigger operation on the addition control at any time.

In an embodiment, if the client B1 has initiated a friend addition request for the user A1 before receiving the friend addition confirmation interface, that is, the client B1 has received a trigger instruction for the friend addition request interface corresponding to the user A1 displayed by the client B1, the client B1 may not display the friend addition confirmation interface related to the user A1, and directly proceed to step 713.

In step 712, the client B1 returns a buddy addition confirmation message to the server BS.

And after the user B1 executes a preset triggering operation for the friend addition confirmation interface, the client B1 returns a friend addition confirmation message to the service terminal BS.

In step 713, the server BS establishes a friend relationship between the virtual user id of the user A1 and the real user id of the user B1.

After receiving the friend addition confirmation message returned by the client B1, the server BS establishes a friend relationship between the virtual user identifier of the user A1 and the real user identifier of the user B1.

Specifically, if the global friend relationship table maintained by the client B1 records friend relationships of multiple users of the communication application B, a friend relationship table entry including the virtual user identifier of the user A1 and the real user identifier of the user B1 may be added to the global friend relationship table. If only the friend relationship of the user B is recorded in the personal friend relationship table for the user B1 maintained by the client B1, a friend relationship table entry containing the virtual user identifier of the user A1 is added in the personal friend relationship table.

In an embodiment, after the friend relationship is established, the service end BS may further return the virtual user information of the user B1, which includes the basic user information of the user B1 and the extended user information, to the service end AS, so that the service end AS updates the virtual user information of the user B1 based on the information. Similarly, the service end AS may also include the basic user information of the user A1 and the virtual user information of the user A1 of the extended user information to the service end BS, so that the service end BS updates the virtual user information of the user A1 based on the information.

In step 714, the service BS returns the buddy relationship synchronization notification to the service AS.

After the server BS establishes the friend relationship between the virtual user identifier of the user A1 and the real user identifier of the user B1, the server BS sends a friend relationship synchronization notification corresponding to the established friend relationship to the server AS, so that the server AS synchronously records the friend relationship between the user A1 and the user B1.

Step 715, the server AS establishes a friend relationship between the real user identifier of the user A1 and the virtual user identifier of the user B1.

After receiving the friend relationship synchronization notification sent by the service end BS, the service end AS establishes a friend relationship between the virtual user identifier of the user B1 and the real user identifier of the user A1.

Specifically, if the global friend relationship table maintained by the client A1 records friend relationships of multiple users of the communication application a, a friend relationship table entry including a virtual user identifier of the user B1 and a real user identifier of the user A1 may be added to the global friend relationship table. If only the friend relationship of the user a is recorded in the personal friend relationship table for the user A1 maintained by the client A1, a friend relationship table entry containing the virtual user identifier of the user B1 is added in the personal friend relationship table.

In step 714, the service AS returns the friend addition result to the client AS.

And the server AS returns a friend adding result to the client AS based on the established friend relationship so that the client A1 displays the friend adding result to the user A1 and correspondingly adjusts the display effect of the friend interface of the user B1 in the client A1, namely, the user information of the user B1 is displayed in the friend list of the user A.

In an embodiment, the client A1 may add an application type flag to the virtual user identifier of the user B1, so that the client A1 displays the user B1 in a friend interface of the user A1 in a differentiated manner. Similarly, the client B1 may add a type tag to the virtual user identifier of the user A1, so that the client B1 displays the user A1 in the friend interface of the user B1 in a differentiated manner.

Further, the friend relationship between the user A1 and other users (including the user B1) may be integrally migrated to the service side AS after being established by the service side BS corresponding to the communication application B. At this time, the migrated users may include users who have already established a friendship with the user A1, or may include users who have not established a friendship with the user A1. As shown in fig. 9, for a user who has not established a friend relationship, a friend relationship adding control (for example, an "adding" control corresponding to B1 in fig. 9) may be displayed so that the user A1 adds the other party as a friend; for the user who has established the friend relationship, the added reminder (e.g., "added" word corresponding to the small forest in fig. 9) may be displayed so that the user A1 knows the friend relationship of both parties.

In another embodiment, the client A1 may add an application type flag to the communication session in which the user B1 participates, so that the client A1 differentially displays the communication session in which the user B1 participates in the session display interface of the user A1. Similarly, the client B1 may add an application type flag to the communication session in which the user A1 participates, so that the client B1 differentially displays the communication session in which the user A1 participates in the session display interface of the user B1. Specific effects can be seen in fig. 10 (a) and 10 (b): in fig. 10 (a), in a session display interface (primary interface) of the client a corresponding to the communication application a, all cross-domain sessions between users of the non-communication application a and the user A1 are aggregated in a "non-a user message set" window, and after the user A1 can trigger the window, a secondary interface display effect turned in is as shown in fig. 10 (b). As can be seen, in the session presentation interface shown in fig. 10 (B), the session window of each session is added with application type flags "application B", "application C", "application D", and the like of the communication application to which the session participant (the other party than the user a) belongs. Furthermore, in the case that the cross-domain session is a group chat session (group chat S), an application type flag of the messaging application to which the group chat participant belongs may be displayed in the session window.

Thus, the process of establishing the friend relationship in the scenario that the service side AS maintains the virtual user identifier of the user B1 and the service side BS maintains the virtual user identifier of the user A1 is completed. The process of establishing a friend relationship in a scenario where the service side AS maintains the virtual user identifier of the user B1 but the service side BS does not maintain the virtual user identifier of the user A1 will be described below with reference to the interaction flowchart of the place where the association relationship is established shown in fig. 11.

It should be noted that, in this embodiment, the client A1 may also request the virtual user information of the user B1 from the server B1 through the server A1, but the process is not substantially different from the specific process of steps 701 to 704 shown in fig. 7, so that the embodiment starts the description by directly sending the friend addition request from the client A1 to the server AS. The process for establishing the friend relationship in the scenario may include the following steps:

in step 1111, the client A1 sends a friend addition request to the server AS.

After the user A1 implements a preset triggering operation for the friend adding control, the client A1 generates a friend adding request for the user B1 and sends the request to the server AS. The friend adding request includes the real user identifier of the user A1 and the real user identifier of the user B1.

Step 1102, query the virtual user id of user A1.

The server AS itself maintains the complete user information of the client A1 and the mapping relationship between the real user identifier and the virtual user identifier of the user A1. Therefore, the server AS may query the virtual user identifier of the user A1 based on the real user identifier of the user A1 included in the friend addition request.

In step 1103, the service end AS sends a friend addition application about the user B1 to the service end BS.

The service side AS can generate a friend adding request of the user A1 for the user B1 based on the inquired virtual user and send the request to the service side BS. The friend addition request may include the virtual user id of the user A1 and the real user id of the user B1.

In step 1104, the server BS sends a friend addition confirmation request to the client B1.

And the server BS directly sends a friend adding confirmation request to the client B1 corresponding to the user B1 according to the real user identification of the user B1 carried in the friend adding application.

In step 1105, the client B1 receives a friend addition confirmation instruction of the user B1.

In step 1106, the client B1 returns a friend addition confirmation message to the server BS.

In step 1107, the server BS establishes a friend relationship between the virtual user identifier of the user A1 and the real user identifier of the user B1.

In step 1108, the service BS returns a buddy relationship synchronization notification to the service AS.

Step 1109, the service end AS establishes a friend relationship between the real user identifier of the user A1 and the virtual user identifier of the user B1.

In step 1110, the server AS returns the friend addition result to the client AS.

There is no essential difference between the steps 1105-1110 and the steps 711-716 shown in fig. 7, and the detailed process can be recorded in the steps 711-716, which is not described herein again.

The following describes a technical solution of the present specification with reference to an interaction flowchart of the data interaction method shown in fig. 12, taking a scenario of performing a network chat under the network architecture shown in fig. 1 as an example. AS shown in fig. 1, the client A1 and the server AS corresponding to the communication application a belong to a domain a, and the client B1 and the server BS corresponding to the communication application B belong to a domain B.

In this embodiment, the server AS maintains the complete user information of the client A1 and the virtual user identifier of the client B1, and similarly, the server BS maintains the complete user information of the client B1 and the virtual user identifier of the client A1. The chat data transmission process in the network chat scenario may include the following steps:

in step 1111, the client A1 sends a chat request to the server AS.

First, the client A1 presents a chat interface for the user B1, where the chat interface includes a chat data input control, so that the user A1 can input chat data through the chat data input control.

In an embodiment, the chat interface may be displayed before the user A1 and the user B1 establish the friend relationship (the chat session at this time belongs to the temporary session), or may be displayed after the user A1 and the user B1 establish the friend relationship (the chat session at this time belongs to the friend session).

In an embodiment, the chat data may be text data, facial expression data, picture data, voice data, or file data. For the above-described temporary conversation and friend conversation, the type of chat data that allows interaction in the respective conversations may be preset. For example, only partial types of data such as text data, emoticon data, or picture data may be allowed to interact with the temporary session, and all types of data such as text data, emoticon data, picture data, voice data, or file data may be allowed to interact with the friend session.

In one embodiment, an application type flag may be preset for a participant of any session, and then a data type of chat data that allows interaction in the any session may be preset according to the application type flag. During the chat, the data sent by any participant of any session may be chat data of an allowed data type. Application type indicia for each participant may also be displayed in the session interface of any of the above-described sessions.

After the user A1 inputs the chat data allowed by the session through the chat data input control, the client A1 may send a chat request including the identifier corresponding to the chat data user A1 and the virtual user identifier of the user B2 to the server AS. The identifier corresponding to the user A1 may be a real user identifier of the user A1, which is maintained by the server A1 and is included in the real user information corresponding to the user A1, or may also be a virtual user identifier of the user A1, which has a mapping relationship with the real user identifier of the user A1, and the following description will take the identifier corresponding to the user A1 as the virtual user identifier of the user A1 as an example.

Step 1202, the server BS queries the friend relationship between the user A1 and the user B1.

The server BS may query whether the local friend relationship between the user A1 and the user B1 is maintained according to the virtual user identifier of the user A1.

If the friend relationship between the user A1 and the user B1 is maintained locally, it is indicated that the user B1 is a friend of the user A1, that is, the chat session to which the chat data belongs is a friend session. If the friend relationship between the user A1 and the user B1 is not inquired and maintained locally, the fact that the user B1 is a friend of the user A1 is indicated, namely the chat session to which the chat data belongs is a temporary session.

Then, it can be determined whether the chat data in the chat request is the data type of the interaction allowed by the chat session, and if the chat data is the data type of the interaction allowed by the chat session, step 1203 is performed; otherwise, if the chat data is of a data type that the chat session does not allow interaction, the chat request may be discarded, and a data type error warning may be returned to the client A1, so that the user A1 may know the error of the data type and timely replace the chat data of the allowed data type to participate in the chat session. In particular, the data type error warning may be a warning text, such as "unsupported data type! The word "or" data type does not support, please change "and the like, which is not limited in this specification.

In step 1203, the service AS queries the virtual user id of the user A1.

Step 1204, the service side AS sends a chat application to the service side BS.

The service side AS maintains the complete user information of the client side A1 and the mapping relation between the real user identification and the virtual user identification of the user A1. Therefore, the server AS may query the virtual user id of the user A1 based on the real user id of the user A1 included in the chat request.

Then, a chat application containing the virtual user identifier of the user A1, the virtual user identifier of the user B1 and the chat data may be created based on the queried virtual user identifier of the user A1, and the chat application may be sent to the server BS.

Step 1205, the server BS queries the real user id of the user B1.

The server BS itself maintains the complete user information of the client B1 and the mapping relationship between the real user identifier and the virtual user identifier of the user B1. Therefore, the server BS may query the real user id of the user B1 based on the virtual user id of the user B1 included in the chat application.

In step 1206, the server BS sends the chat data to the client B1.

Step 1207, client B1 presents the chat data.

And the server BS sends the chat data to the client B1 corresponding to the user B1 according to the real user identification of the user B1, and the chat data is displayed in a corresponding session interface by the client B1. Specifically, if the session to which the chat data belongs to a temporary session, the chat data is displayed in a temporary session interface; and if the session to which the chatting data belongs to the friend session, displaying the chatting data in a friend session interface so that the user B1 can check the chatting data.

In step 1208, the server BS returns the chat data transmission result to the server AS.

After the server BS sends the chat data to the client B1, a chat data sending result including the virtual user identifier of the user B1, the virtual user identifier of the user A1, and the sending result identifier may be returned to the server AS, so that the server AS obtains a result of whether the chat data is sent successfully or not.

If the chat data is successfully transmitted to the client B1 according to the step 1207, the transmission result identifier is a successful identifier indicating that the chat data is successfully transmitted. If the sending process of the chat data fails due to the reasons of the failure of the query of the real user identifier, the failure of the client B1 in receiving the data and the like, the sending result identifier is a failure identifier for indicating the failure of sending the chat data.

Step 1209, the service AS queries the real user id of the user A1.

The server AS itself maintains the complete user information of the client A1 and the mapping relationship between the real user identifier and the virtual user identifier of the user A1. Therefore, the service AS can query the real user id of the user A1 based on the virtual user id of the user A1 included in the chat data transmission result.

In step 1210, the server AS returns a transmission result identifier to the client A1.

In step 1211, the client A1 displays the chat data transmission result.

And the server AS sends the sending result identification to the client A1 based on the inquired real user identification of the user A1, and the client A1 receives the sending result identification and then correspondingly displays the chat data sending result according to the sending result identification. Specifically, under the condition that the sending result identifier is a successful identifier, a successful reminder, such as text reminder information of "received, unread" and the like, can be displayed in a first association area of the sent chatting data in the session interface; under the condition that the sending result identifier is the failure identifier, a failure prompt, such as a text prompt message of 'sending failure', 'please retry' and the like, a preset failure sign symbol or a failure sign expression and the like, can be displayed in a second associated area of the sent chatting data in the session interface; or the color of the display area where the chat data has been sent may be changed to a preset failure prompt color, or the shape of the display area may be changed to a preset failure prompt shape, etc., which are not described in detail.

Thus, the data transmission process in the scenario that the service side AS maintains the virtual user identifier of the user B1 and the service side BS maintains the virtual user identifier of the user A1 is completed. With reference to the interaction flowchart of the data interaction method shown in fig. 13, a data transmission process in a scenario where the service end AS maintains the virtual user identifier of the user B1 but the service end BS does not maintain the virtual user identifier of the user A1 will be described. The chat data transmission process in the scene can comprise the following steps:

in step 1301, the client A1 sends a chat request to the server AS.

First, the client A1 presents a chat interface for the user B1, where the chat interface includes a chat data input control, so that the user A1 can input chat data through the chat data input control. The specific process of the user A1 inputting the chat data through the above-mentioned control can be seen in step 1201.

After the user A1 inputs the chat data allowed by the session through the chat data input control, the client A1 may send a chat request containing the chat data, the identifier corresponding to the user A1, and the real user identifier of the user B1 to the server AS. The identifier corresponding to the user A1 may be a real user identifier of the user A1, which is maintained by the server A1 and is included in the real user information corresponding to the user A1, or may also be a virtual user identifier of the user A1, which has a mapping relationship with the real user identifier of the user A1, and the following description takes the identifier corresponding to the user A1 as the virtual user identifier of the user A1 as an example.

In step 1302, the server BS queries the friend relationship between the user A1 and the user B1.

The server BS may query whether the local friend relationship between the user A1 and the user B1 is maintained (i.e., between the virtual user id of the user A1 and the real user id of the user B1) according to the virtual user id of the user A1. Then, it is determined whether the type of the chat session and the data type of the chat data are the data types allowed by the chat session according to the query result, and the specific query and determination manner may refer to the description in step 1202, which is not described herein again.

Step 1303, the server AS queries the virtual user id of the user A1.

In step 1304, the service AS sends a chat application to the service BS.

The service side AS maintains the complete user information of the client side A1 and the mapping relation between the real user identification and the virtual user identification of the user A1. Therefore, the service AS can query the virtual user id of the user A1 based on the real user id of the user A1 included in the chat request.

Step 1305, the server BS sends the chat data to the client B1.

In step 1306, client B1 presents the chat data.

Step 1307, the service end BS returns the chat data transmission result to the service end AS.

After the server BS sends the chat data to the client B1, a chat data sending result including the real user identifier of the user B1, the virtual user identifier of the user A1, and the sending result identifier may be returned to the server AS, so that the server AS obtains a result of whether the chat data is sent successfully or not.

If the chat data is successfully sent to the client B1 according to the step 706, the sending result identifier is a successful identifier for indicating that the chat data is successfully sent. If the sending process of the chat data fails due to reasons such as the failure of querying the real user identifier and the failure of receiving the data by the client B1, the sending result identifier is a failure identifier for indicating the failure of sending the chat data.

In step 1308, the service AS queries the real user id of the user A1.

Step 1309, the service end AS returns the sending result identifier to the client A1.

In step 1310, the client A1 displays the chat data transmission result.

There is no essential difference between the above-mentioned steps 1308-1310 and the steps 1209-1212 shown in fig. 12, and the detailed process can be recorded in the above-mentioned steps 1209-1212, which is not described herein again.

Fig. 14 is a schematic structural diagram of an electronic device shown in an exemplary embodiment of the present specification. Referring to fig. 14, in the hardware level, the electronic device includes a processor 1401, an internal bus 1402, a network interface 1403, a memory 1404, and a nonvolatile memory 1405, but may include hardware required for other services. The processor 1401 reads a corresponding computer program from the nonvolatile memory 1405 into the memory 1404 and runs the computer program, thereby forming a device for establishing an association relationship on a logical level. Of course, besides the software implementation, the present specification does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may be hardware or logic devices.

Fig. 15 is a block diagram illustrating an association relationship establishing apparatus according to an exemplary embodiment of the present specification. Referring to fig. 15, in a software implementation, the means for establishing an association relationship may include:

an association application receiving unit 1501, configured to enable a first communication application server to receive a cross-domain relationship establishment application, where the cross-domain relationship establishment application is generated by a second communication application server in response to a request of a second communication application client, and the cross-domain relationship establishment application includes a first virtual user identifier and an identifier corresponding to a second user logged in the second communication application client;

an association request sending unit 1502, configured to enable the first communication application server to determine, according to a mapping relationship between a virtual user identifier and a real user identifier included in real user information maintained by the first communication application server, a first real user identifier corresponding to the first virtual user identifier, and send a cross-domain relationship confirmation request to a first communication application client logged in by a first user corresponding to the first real user identifier;

a first relationship establishing unit 1503, configured to establish, by the first communication application server, an association relationship between an identifier corresponding to the second user and the first real user identifier after it is determined that the first user performs a confirmation operation on the cross-domain relationship confirmation request;

the first relationship synchronization unit 1504 enables the first communication application server to return an association relationship synchronization notification to the second communication application server, so that the second communication application server establishes an association relationship between the identifier corresponding to the second user and the first virtual user identifier.

Optionally, the identifier corresponding to the second user includes a second real user identifier included in second real user information corresponding to the second user and maintained by the second communication application server, or a second virtual user identifier having a mapping relationship with the second real user identifier.

Optionally, the method further includes:

an information request responding unit 1505, configured to enable the first communication application server to return, to the second communication application server, first virtual user information and a standard verification identifier corresponding to the first virtual user identifier after receiving a first user information obtaining request sent by the second communication application server, where the first virtual user information is shown in a relationship application interface on the second communication application client, and the relationship application interface is used for triggering to generate the cross-domain relationship establishment application;

the identifier to be verified is matched with the standard verification identifier and is used as a precondition for the first communication application server to establish an association relationship between the second user identifier and the first virtual user information.

Optionally, the method further includes:

a virtual information generating unit 1506, configured to enable the first communication application server to generate first virtual user information corresponding to the first virtual user identifier based on first real user information corresponding to the first user, where the first virtual user information includes at least a part of content of the first real user information;

a virtual information synchronization unit 1507, for enabling the first communication application server to synchronize the first virtual user information with the second communication application server.

Alternatively to this, the first and second parts may,

before the association relationship is established, the first virtual user information synchronized from the first communication application server to the second communication application server contains basic user information;

after the association relationship is established, the first virtual user information synchronized by the first communication application server to the second communication application server includes the basic user information and the extended user information.

Optionally, the extended user information includes privacy information of the first user.

Optionally, the virtual user identifier and the real user identifier are configured in a different manner.

Optionally, the association relationship includes any one of: friend relationships, session relationships, special attention relationships.

Optionally, the method further includes:

the user mark adding unit 1508, enables the first communication application server to add an application type mark to the address book contact information corresponding to the first user, so as to indicate whether the real user information corresponding to the corresponding address book contact information is maintained by the first communication application server, and indicate the first communication application client to perform differentiated display on the address book contact information corresponding to different application type marks.

Optionally, the method further includes:

a session mark adding unit 1509, configured to enable the first communication application server to add an application type mark to the communication session in which the first user participates, so as to indicate whether the real user information corresponding to the participant of the corresponding communication session is maintained by the first communication application server, and indicate that the first communication application client performs differentiated display on the session window of the communication session corresponding to the different application type marks.

Alternatively to this, the first and second parts may,

under the condition that the application type mark indicates that the real user information corresponding to the participants of the corresponding communication session is maintained by the first communication application server, the application type mark is used for indicating the first communication application client to display the session window of the corresponding communication session on a primary interface of a session list;

and under the condition that the application type mark indicates that the real user information corresponding to at least one participant of the corresponding communication session is not maintained by the first communication application server, the application type mark is used for indicating the first communication application client to display the session window of the corresponding communication session on a secondary interface of a session list.

Optionally, one of the first communication application corresponding to the first communication application service end and the second communication application corresponding to the second communication application service end is deployed in a public domain, and the other is deployed in a private domain.

Fig. 16 is a block diagram illustrating another association relationship establishing apparatus according to an exemplary embodiment of the present specification. Referring to fig. 16, in a software implementation, the means for establishing an association relationship may include:

an association request receiving unit 1601, configured to enable a first communication application server to receive a cross-domain relationship establishment request sent by a first communication application client, where the cross-domain relationship establishment request includes a first real user identifier corresponding to a first user logged in the first communication application client and a second real user identifier corresponding to a second user;

an association application sending unit 1602, configured to enable the first communication application server to determine, according to a mapping relationship between a virtual user identifier and a real user identifier included in real user information maintained by the first communication application server, a first virtual user identifier corresponding to the first real user identifier, and send a cross-domain relationship establishment application to a second communication application server, where the cross-domain relationship establishment application includes an identifier corresponding to the first user and the second real user identifier, so that the second communication application function server sends a corresponding cross-domain relationship confirmation request to a second communication application client logged in by the second user;

a second relation establishing unit 1603, enabling the first communication application server to respond to the association relation synchronization notification returned by the second communication application server and establish an association relation between the identifier corresponding to the first user and the second real user identifier; and the association relation synchronization notification is created and sent by the second communication application server after determining that the second user performs a confirmation operation on the cross-domain relation confirmation request, and establishing an association relation between the identifier corresponding to the first user and the second real user identifier.

Optionally, the identifier corresponding to the first user includes:

and the first communication application server maintains a first real user identifier contained in first real user information corresponding to the first user, or a first virtual user identifier which has a mapping relation with the first real user identifier.

Optionally, the cross-domain relationship establishment application further includes an identifier to be verified, and the apparatus further includes:

an information request sending unit 1604, which enables the first communication application server to send a second user information obtaining request to the second communication application server;

an information forwarding unit 1605, which enables the first communication application server to forward the received second real user information and standard verification identifier returned by the second communication application server to the first communication application client, where the second real user information is displayed on a relationship application interface on the first communication application client, the relationship application interface is used for triggering to generate the cross-domain relationship establishment application, and the standard verification identifier is used by the second communication application server to verify whether the standard verification identifier matches the identifier to be verified included in the cross-domain relationship establishment application;

and the standard verification identifier matched with the identifier to be verified is used as a precondition for establishing an association relation between the identifier corresponding to the first user and the second real user identifier by the second communication application server side.

Optionally, the method further includes:

a virtual information receiving unit 1606, configured to enable the first communication application server to receive second virtual user information corresponding to the second real user identifier and synchronized with the second communication application server;

the second virtual user information is generated by the second communication application server based on second real user information corresponding to the second user, and the second virtual user information includes at least a part of content of the second real user information.

Alternatively to this, the first and second parts may,

before the association relationship is established, the second virtual user information synchronized by the second communication application server to the first communication application server contains basic user information;

after the association relationship is established, the second virtual user information synchronized by the second communication application server to the second communication application server includes the basic user information and the extended user information.

Optionally, the extended user information includes privacy information of the second user.

Optionally, the virtual user information and the real user information are configured in a different manner.

Optionally, one of the first communication application corresponding to the first communication application server and the second communication application corresponding to the second communication application server is deployed in a public domain, and the other is deployed in a private domain.

Fig. 17 is a block diagram illustrating a data interaction device according to an exemplary embodiment of the present specification. Referring to fig. 17, in a software implementation, the data interaction apparatus may include:

an interactive application receiving unit 1701, enabling a first communication application server to receive a cross-domain data interactive application sent by a second communication application server, wherein the cross-domain data interactive application comprises target data and a first virtual user identifier;

a virtual identifier determining unit 1702, configured to enable the first communication application server to determine, according to a mapping relationship between a virtual user identifier and a real user identifier included in real user information maintained by the first communication application server, a first real user identifier corresponding to the first virtual user identifier;

a target data sending unit 1703, configured to enable the first communication application server to send the target data to a first communication application client corresponding to the first real user identifier.

Optionally, the cross-domain data interaction application is generated by a second communication application client, the cross-domain data interaction application further includes an identifier corresponding to a second user logged on the second communication application client, and the apparatus further includes:

an interaction authority determining unit 1704, configured to enable the first communication application server to determine, according to the identifier corresponding to the second user, a data interaction authority of the second user for a first user corresponding to the first real user information;

the authorized data sending unit 1705 is configured to, when the second user has a data interaction authority for the first user, send the target data to the first communication application client by the first communication application server.

Optionally, the interaction authority determining unit 1704 is further configured to:

and under the condition that the first communication application server maintains the association relationship established between the identifier corresponding to the second user and the first real user information, the first communication application server judges that the second user has the data interaction authority aiming at the first user.

Alternatively to this, the first and second parts may,

the association between the second user identifier and the first real user information is established based on the method according to the first or second aspect of the invention; alternatively, the first and second electrodes may be,

and after the incidence relation between the second user identification and the first real user information is established by the second communication application server, migrating the second user identification and the first real user information from the second communication application server to the first communication application server.

Optionally, the method further includes:

an interaction result sending unit 1706, which enables the first communication application server to return a cross-domain data interaction result to the second communication application server, so that the second communication application client displays the cross-domain data interaction result to the second user.

FIG. 18 illustrates a block diagram of another data interaction device, shown in an exemplary embodiment of the present description. Referring to fig. 18, in a software implementation, the data interaction apparatus may include:

an interaction request receiving unit 1801, configured to enable a first communication application server to receive a data interaction request sent by a first communication application client, where the data interaction request includes target data, a first real user identifier, and a second real user identifier;

an interactive application generating unit 1802, configured to enable the first communication application server to determine, according to a mapping relationship between a virtual user identifier and a real user identifier included in real user information maintained by the first communication application server, a first virtual user identifier corresponding to the first real user identifier, and generate a cross-domain data interactive application including the target data, the first virtual user identifier, and the second real user identifier;

an interaction application sending unit 1803, configured to enable the first communication application server to send the cross-domain data interaction application to a second communication application server, so that the second communication application server sends the target data to a second communication application client, where a second user corresponding to the second real user identifier logs in, of the second user.

Optionally, the method further includes:

the association relationship query unit 1804 is configured to query, by the first communication application server, whether an association relationship between the first real user identifier and the second real user identifier exists after the data interaction request is received, and use the association relationship between the first real user identifier and the second real user identifier as a precondition for sending the cross-domain data interaction application to the second communication application server.

Optionally, the method further includes:

an interaction result receiving unit 1805, configured to enable the first communication application server to receive a cross-domain data interaction result returned by the second communication application server;

an interaction result forwarding unit 1806, configured to enable the first communication application server to forward the cross-domain data interaction result to the first communication application client, so that the first communication application client displays the cross-domain data interaction result to the first user.

FIG. 19 illustrates a block diagram of yet another data interaction device, in accordance with an exemplary embodiment of the present specification. Referring to fig. 19, in a software implementation, the data interaction apparatus may include:

an application receiving unit 1901, configured to enable a server of a first instant messaging application to receive a cross-domain data interaction application sent by a server of a second instant messaging application, where the first instant messaging application is deployed in a first domain, and the second instant messaging application is deployed in a second domain different from the first domain;

a target determining unit 1902, configured to enable a server of the first instant messaging application to determine interaction data included in the cross-domain data interaction application and a target interaction user indicated by the cross-domain data interaction application;

a data sending unit 1903, configured to enable the server of the first instant messaging application to send the interaction data to a client corresponding to the target interaction user in the first instant messaging application.

Optionally, the cross-domain data interaction application is established by the server of the second instant messaging application based on a data interaction request sent by the client of the second instant messaging application.

Optionally, the interactive data is used by the client corresponding to the first instant messaging application to display a relationship establishment confirmation interface, and the trigger operation of the target interaction user on the relationship establishment confirmation interface is used to indicate whether to establish an association relationship between the initiator user of the data interaction request and the target interaction user.

Optionally, the interactive data is an instant messaging message sent by an initiator user of the data interaction request to the target interaction user.

The implementation process of the functions and actions of each unit in the device is detailed in the implementation process of the corresponding step in the method, and is not described herein again.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

In a typical configuration, an electronic device includes one or more processors (CPUs), input/output interfaces, a network interface, and a memory.

The memory may include forms of volatile memory in a computer readable medium, random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

For example, the present specification proposes a computer-readable medium on which computer instructions are stored, which when executed by a processor implement the above-mentioned association establishment method.

For example, the present specification proposes another computer-readable medium having stored thereon computer instructions which, when executed by a processor, implement the above-described data interaction method.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

For the above-mentioned apparatus embodiments, since they basically correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.

The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.

Claims

1. A method for establishing an association relationship is characterized in that the method comprises the following steps:

the first communication application server side determines a first real user identifier corresponding to the first virtual user identifier according to a mapping relation between the virtual user identifier and a real user identifier contained in self-maintained real user information, and sends a cross-domain relation confirmation request to a first communication application client side which is logged in by a first user corresponding to the first real user identifier;

2. The method of claim 1, wherein the identification corresponding to the second user comprises:

and the second communication application server side maintains a second real user identifier contained in second real user information corresponding to the second user, or a second virtual user identifier which has a mapping relation with the second real user identifier.

3. The method according to claim 1, wherein the cross-domain relationship establishment application further includes an identifier to be verified, the method further comprising:

after receiving a first user information acquisition request sent by the second communication application server, the first communication application server returns first virtual user information and a standard verification identifier corresponding to the first virtual user identifier to the second communication application server, the first virtual user information is displayed on a relationship application interface on the second communication application client, and the relationship application interface is used for triggering to generate the cross-domain relationship establishment application;

the identifier to be verified is matched with the standard verification identifier and is used as a precondition for the first communication application server to establish an association relationship between the identifier corresponding to the second user and the first virtual user identifier.

4. The method of claim 1, further comprising:

the first communication application server generates first virtual user information corresponding to the first virtual user identifier based on first real user information corresponding to the first user, wherein the first virtual user information comprises at least part of content of the first real user information;

and the first communication application server side synchronizes the first virtual user information to the second communication application server side.

5. The method of claim 4,

6. The method of claim 5, wherein the extended user information comprises privacy information of the first user.

7. The method of claim 1, wherein the virtual user identifier is configured differently than the real user identifier.

8. The method of claim 1, wherein the association comprises any one of: friend relationships, session relationships, special attention relationships.

9. The method of claim 1, further comprising:

the first communication application server adds an application type mark to the address book contact information corresponding to the first user to indicate whether the real user information corresponding to the corresponding address book contact information is maintained by the first communication application server or not, and indicates the first communication application client to perform differentiated display on the address book contact information corresponding to different application type marks.

10. The method of claim 1, further comprising:

the first communication application server adds application type marks to the communication sessions participated by the first user to indicate whether the real user information corresponding to the participants of the corresponding communication sessions is maintained by the first communication application server or not, and indicates the first communication application client to perform differentiated display on the session windows of the communication sessions corresponding to different application type marks.

11. The method of claim 10,

12. The method according to claim 1, wherein one of the first communication application corresponding to the first communication application server and the second communication application corresponding to the second communication application server is deployed in a public domain, and the other one is deployed in a private domain.

13. A method for establishing an association relationship is characterized in that the method comprises the following steps:

the first communication application server side determines a first virtual user identifier corresponding to the first real user identifier according to a mapping relation between the virtual user identifier and a real user identifier contained in self-maintained real user information, and sends a cross-domain relation establishment application to a second communication application server side, wherein the cross-domain relation establishment application comprises the identifier corresponding to the first user and the second real user identifier, so that the second communication application server side sends a corresponding cross-domain relation confirmation request to a second communication application client side logged in by the second user;

the first communication application server responds to the incidence relation synchronization notice returned by the second communication application server, and establishes an incidence relation between the identifier corresponding to the first user and the identifier of the second real user; and the association relation synchronization notification is created and sent by the second communication application server after determining that the second user performs a confirmation operation on the cross-domain relation confirmation request, and establishing an association relation between the identifier corresponding to the first user and the second real user identifier.

14. The method of claim 13, wherein the identification corresponding to the first user comprises:

15. The method according to claim 13, wherein the cross-domain relationship establishment application further includes an identifier to be verified, further comprising:

the first communication application server side sends a second user information acquisition request to the second communication application server side;

the first communication application server forwards received second real user information and a standard verification identifier returned by the second communication application server to the first communication application client, the second real user information is displayed on a relationship application interface on the first communication application client, the relationship application interface is used for triggering to generate the cross-domain relationship establishment application, and the standard verification identifier is used by the second communication application server to verify whether the standard verification identifier is matched with the identifier to be verified contained in the cross-domain relationship establishment application;

16. The method of claim 13, further comprising:

the first communication application server receives second virtual user information which is synchronous with the second communication application server and corresponds to the second real user identification;

17. The method of claim 16,

18. The method of claim 17, wherein the extended user information comprises privacy information of the second user.

19. The method of claim 13, wherein the virtual user identifier is configured differently than the real user identifier.

20. The method of claim 13, wherein one of the first communication application corresponding to the first communication application server and the second communication application corresponding to the second communication application server is deployed in a public domain, and the other one is deployed in a private domain.

21. A method of data interaction, the method comprising:

22. The method of claim 21, wherein the cross-domain data interaction application is generated by a second communication application client, and further comprises an identifier corresponding to a second user logged on the second communication application client, the method further comprising:

the first communication application server side determines the data interaction authority of the second user aiming at the first user corresponding to the first real user identification according to the identification corresponding to the second user;

and under the condition that the second user has data interaction authority aiming at the first user, the first communication application server side sends the target data to the first communication application client side.

23. The method according to claim 22, wherein the determining, by the first communication application server, the data interaction permission of the second user for the first user corresponding to the first real user identifier according to the identifier corresponding to the second user includes:

and under the condition that the first communication application server maintains the association relationship established between the identifier corresponding to the second user and the first real user identifier, the first communication application server judges that the second user has the data interaction authority aiming at the first user.

24. The method of claim 23,

the association between the identity corresponding to the second user and the identity of the first real user is established based on the method according to any one of claims 1 to 20; alternatively, the first and second electrodes may be,

and after the association relationship between the identifier corresponding to the second user and the first real user identifier is established by the second communication application server, migrating the second user identifier from the second communication application server to the first communication application server.

25. The method according to claim 22, wherein the identifier corresponding to the second user comprises a second real user identifier included in second real user information corresponding to the second user and maintained by the second communication application server, or a second virtual user identifier having a mapping relationship with the second real user identifier.

26. The method of claim 21, further comprising:

and the first communication application server side returns a cross-domain data interaction result to the second communication application server side, so that the second communication application client side displays the cross-domain data interaction result to a second user.

27. A method of data interaction, the method comprising:

28. The method of claim 27, further comprising:

after receiving the data interaction request, the first communication application server side inquires whether an incidence relation between a first real user identification and a second real user identification exists or not, and the incidence relation between the first real user identification and the second real user identification exists is used as a precondition for sending the cross-domain data interaction application to the second communication application server side.

29. The method of claim 27, wherein one of the first communication application corresponding to the first communication application server and the second communication application corresponding to the second communication application server is deployed in a public domain, and the other one is deployed in a private domain.

30. The method of claim 27, further comprising:

the first communication application server receives a cross-domain data interaction result returned by the second communication application server;

and the first communication application server side forwards the cross-domain data interaction result to the first communication application client side so that the first communication application client side displays the cross-domain data interaction result to a first user.

31. A method of data interaction, the method comprising:

32. The method of claim 31, wherein the cross-domain data interaction application is established by the server of the second instant messaging application based on a data interaction request sent by the client of the second instant messaging application.

33. The method according to claim 32, wherein the interaction data is used by a client corresponding to the first instant messaging application to display a relationship establishment confirmation interface, and the triggering operation of the relationship establishment confirmation interface by the target interaction user is used to indicate whether an association relationship is established between an initiator user of the data interaction request and the target interaction user.

34. The method of claim 32, wherein the interaction data is an instant messaging message sent by an initiator user of the data interaction request to the target interaction user.

35. An apparatus for establishing association relationship, the apparatus comprising:

36. An apparatus for establishing association relationship, the apparatus comprising:

an association application sending unit, configured to enable the first communication application server to determine, according to a mapping relationship between a virtual user identifier and a real user identifier included in real user information maintained by the first communication application server, a first virtual user identifier corresponding to the first real user identifier, and send a cross-domain relationship establishment application to a second communication application server, where the cross-domain relationship establishment application includes an identifier corresponding to the first user and the second real user identifier, so that the second communication application server sends a corresponding cross-domain relationship confirmation request to a second communication application client that the second user logs in;

a second relation establishing unit, which enables the first communication application server to respond to the incidence relation synchronization notice returned by the second communication application server and establish the incidence relation between the identification corresponding to the first user and the identification of the second real user; and the association relation synchronization notification is created and sent by the second communication application server after determining that the second user performs a confirmation operation on the cross-domain relation confirmation request, and establishing an association relation between the identifier corresponding to the first user and the second real user identifier.

37. A data interaction apparatus, the apparatus comprising:

the interactive application receiving unit enables a first communication application server to receive a cross-domain data interactive application sent by a second communication application server, wherein the cross-domain data interactive application comprises target data and a first virtual user identifier;

the virtual identification determining unit enables the first communication application server to determine a first real user identification corresponding to the first virtual user identification according to a mapping relation between the virtual user identification and a real user identification contained in real user information maintained by the first communication application server;

38. A data interaction apparatus, the apparatus comprising:

and the interactive application sending unit enables the first communication application server to send the cross-domain data interactive application to a second communication application server so that the second communication application server sends the target data to a second communication application client which is corresponding to the second real user identification and is logged in by a second user.

39. A data interaction apparatus, the apparatus comprising:

a target determining unit, configured to enable a server of the first instant messaging application to determine interaction data included in the cross-domain data interaction application and a target interaction user indicated by the cross-domain data interaction application;

40. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to implement the method of any one of claims 1-34.

41. A computer-readable storage medium having stored thereon computer instructions, which when executed by a processor, perform the steps of the method of any one of claims 1-34.