CN112819480B

CN112819480B - Data processing method, device and storage medium

Info

Publication number: CN112819480B
Application number: CN201911043828.4A
Authority: CN
Inventors: 王春晖; 叶波; 林莉; 李斌; 朱标亦
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-10-30
Filing date: 2019-10-30
Publication date: 2023-06-09
Anticipated expiration: 2039-10-30
Also published as: CN112819480A

Abstract

The embodiment of the application discloses a data processing method, a device and a storage medium, wherein the method comprises the following steps: acquiring a batch inheritance request sent by a management terminal aiming at a second user associated with a first user; determining a target to-be-allocated user with a two-way association relation with a first user from to-be-allocated users, and generating configuration text information associated with a second user according to an initial binding relation between the target to-be-allocated user and the second user; according to the first account information of the first user, sending configuration text information to a target user terminal corresponding to a target user to be allocated, so that the target user terminal generates a friend adding request aiming at the second account information based on the configuration text information; and checking the checking key information according to the friend adding request, and establishing a bidirectional association relation between the target user to be allocated and the second user when the checking is successful. By adopting the embodiment of the application, the processing efficiency of the service data can be improved, and the loss of the service data is prevented.

Description

Data processing method, device and storage medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a data processing method, apparatus, and storage medium.

Background

At present, when the enterprise staff contacts with the clients, most enterprise staff contacts with the clients through the same instant messaging application (such as WeChat). For example, in the instant messaging application, the enterprise employee a may add account information of a plurality of clients using personal account information (e.g., account information a), so as to contact a plurality of successfully added clients; enterprise employee B may also add account information for multiple clients using personal account information (e.g., account information B) in the instant messaging application, thereby enabling contact with multiple successfully added clients. In other words, each enterprise employee communicates with the client according to the personal account information, if the enterprise employee B needs to contact with the client of the enterprise employee a, the enterprise employees need to be added manually one by one according to the account information a, so that the efficiency of processing the business data is reduced.

Because the friends added by the personal account number of each enterprise employee belong to the personal privacy of the enterprise employee, other employees cannot directly acquire the client information of the enterprise employee. For example, when enterprise employee a leaves a job or has a long vacation, it is difficult for other employees (e.g., enterprise employee B) who take over for the enterprise employee a to directly acquire the customer with the enterprise employee a, which in turn results in a high probability of losing the customer of the enterprise employee a.

Content of the application

The embodiment of the application provides a data processing method, a data processing device and a storage medium, which can improve the processing efficiency of service data and prevent the loss of the service data.

An aspect of an embodiment of the present application provides a data processing method, where the method is applied to a first server corresponding to a first application, and includes:

acquiring a batch inheritance request sent by a management terminal aiming at a second user associated with a first user; the batch inheritance request is determined by the management terminal after service allocation is carried out on users to be allocated which are associated with the first user; the user to be allocated is a user in a second application different from the first application;

determining a target to-be-allocated user with a two-way association relation with the first user from the to-be-allocated users, and generating configuration text information associated with the second user according to an initial binding relation between the target to-be-allocated user and the second user; the configuration text information comprises second account information of the second user and verification key information for verification;

according to the first account information of the first user, the configuration text information is sent to a target user terminal corresponding to the target user to be distributed, so that the target user terminal generates a friend adding request aiming at the second account information based on the configuration text information;

And verifying the verification key information according to the friend adding request, and establishing a bidirectional association relation between the target user to be allocated and the second user when the verification is successful.

The obtaining the batch inheritance request sent by the management terminal aiming at the second user related to the first user comprises the following steps:

receiving a list acquisition request sent by a management terminal aiming at a configuration page of a first application, and returning a user list to be allocated to the management terminal based on the list acquisition request so that the management terminal outputs the user list to be allocated on a first display interface; the list of users to be allocated comprises the first user and M users to be allocated associated with the first user; m is a positive integer;

acquiring N users to be distributed, which are determined by the management terminal from the M users to be distributed; the N is a positive integer less than or equal to the M;

acquiring initial binding relations between second users associated with the first user and the N users to be distributed respectively; the second user is determined by the management terminal in response to a triggering operation triggered by a second display interface;

And acquiring a batch inheritance request which is sent by the management terminal based on the initial binding relation and is associated with the second user.

The receiving, by the management terminal, a list acquisition request sent by aiming at a configuration page of a first application, and returning, to the management terminal, a user list to be allocated based on the list acquisition request, including:

acquiring a list acquisition request sent by a management terminal aiming at a configuration page of the first application; the list acquisition request is determined by the management terminal in response to a triggering operation triggered by a configuration interface for the configuration page;

acquiring a list of users to be allocated associated with a first user in the first application according to the list acquisition request;

and returning M users to be allocated, which are associated with the first user, in the list of the users to be allocated to the management terminal so that the management terminal outputs the first user and the M users to be allocated on a first display interface.

The obtaining initial binding relations between the second user associated with the first user and the N users to be distributed respectively includes:

receiving an address book acquisition request sent by the management terminal based on the first user; the address book acquisition request is determined by the management terminal in response to a triggering operation for triggering an allocation button in the first display interface;

Acquiring user information of the first user carried in the address book acquisition request, searching a group to which the first user belongs according to the user information, and sending an address book corresponding to the group to the management terminal so that the management terminal outputs the address book on a second display interface;

acquiring a second user determined by the management terminal aiming at the address book on the second display interface;

and acquiring initial binding relations between the N users to be distributed and the second user, which are established by the management terminal.

Wherein the method further comprises:

splitting each inheritance request in the batch inheritance requests, and adding each split inheritance request to a task queue respectively;

generating adding response information corresponding to each inheritance request when each inheritance request is added to the task queue;

and returning the adding response information to the management terminal so that the management terminal sets the service state corresponding to each inheritance request to be a state to be confirmed based on the adding response information.

The method comprises the steps of determining a target to-be-allocated user with a bidirectional association relation with a first user from the to-be-allocated users, and generating configuration text information associated with the second user according to an initial binding relation between the target to-be-allocated user and the second user, wherein the configuration text information comprises the following steps of;

Acquiring a first relation record table corresponding to a user to be allocated, which is associated with the first user, searching first verification key information in the first relation record table, and determining the user to be allocated in a list column where the first verification key information is located as a target user to be allocated; the first verification key information is used for representing the bidirectional association relationship between the first user and the user to be allocated;

acquiring a second relation record table associated with the first user, searching second check key information in the second relation record table, and acquiring a second user in a list column where the second check key information is located; the second check key information is used for representing a group association relationship between the first user and the second user;

taking the two-way association relationship and the group association relationship as verification key information;

and generating configuration text information associated with the second user according to the initial binding relation between the target user to be distributed and the second user, the second account information of the second user and the verification key information.

The step of verifying the verification key information according to the friend adding request, and establishing a bidirectional association relationship between the target user to be allocated and the second user when the verification is successful, comprises the following steps:

Checking the bidirectional association relation in the check key information based on the friend adding request, and checking the group association relation;

when the verification is successful, the friend adding request is sent to the second account information;

and establishing a bidirectional association relation between the target user to be allocated and the second user.

The sending the configuration text information to a target user terminal corresponding to the target user to be allocated according to the first account information of the first user, so that the target user terminal generates a friend adding request for the second account information based on the configuration text information, including:

according to the first account information of the first user, the configuration text information is sent to a second server, so that the second server forwards the configuration text information to a target user terminal corresponding to a target user to be distributed;

receiving a friend adding request forwarded by a second server when a request initiator is determined to be the target user to be distributed; the friend adding request is generated by the target user terminal based on the second account information in the configuration text information.

In one aspect, another data processing method is provided, where the method is applied to a user terminal corresponding to a second application, and includes:

receiving configuration text information sent by a first server corresponding to a first application according to first account information of a first user; the configuration text information comprises second account information of a second user and verification key information for verification;

responding to triggering operation of a conversation interface where the configuration text information is located, and displaying a friend adding interface independent of the conversation interface; the friend adding interface comprises the second account information;

responding to a friend adding operation aiming at the friend adding interface, and sending a friend adding request to the second account information; the friend adding request is used for indicating the first server to establish a bidirectional association relationship between the target user to be allocated and the second user when the first server successfully verifies the verification key information, wherein the user to be allocated is a user in the second application different from the first application.

In one aspect, the present application provides a data processing apparatus, where the method is applied to a first server corresponding to a first application, and includes:

The acquisition module is used for acquiring a batch inheritance request sent by the management terminal aiming at a second user associated with the first user; the batch inheritance request is determined by the management terminal after service allocation is carried out on users to be allocated which are associated with the first user; the user to be allocated is a user in a second application different from the first application;

the first generation module is used for determining a target user to be distributed, which has a two-way association relation with the first user, from the users to be distributed, and generating configuration text information associated with the second user according to an initial binding relation between the target user to be distributed and the second user; the configuration text information comprises second account information of the second user and verification key information for verification;

the sending module is used for sending the configuration text information to a target user terminal corresponding to the target user to be distributed according to the first account information of the first user, so that the target user terminal generates a friend adding request aiming at the second account information based on the configuration text information;

and the establishing module is used for verifying the verification key information according to the friend adding request, and establishing a bidirectional association relation between the target user to be allocated and the second user when the verification is successful.

Wherein, the acquisition module includes:

the list returning unit is used for receiving a list acquisition request sent by the management terminal aiming at a configuration page of the first application, and returning a user list to be allocated to the management terminal based on the list acquisition request so that the management terminal outputs the user list to be allocated on a first display interface; the list of users to be allocated comprises the first user and M users to be allocated associated with the first user; m is a positive integer;

the first acquisition unit is used for acquiring N users to be allocated determined by the management terminal from the M users to be allocated; the N is a positive integer less than or equal to the M;

the second acquisition unit is used for acquiring initial binding relations between the N users to be distributed and second users associated with the first user respectively; the second user is determined by the management terminal in response to a triggering operation triggered by a second display interface;

and the third acquisition unit is used for acquiring a batch inheritance request which is sent by the management terminal based on the initial binding relation and is associated with the second user.

Wherein the list return unit includes:

A first obtaining subunit, configured to obtain a list obtaining request sent by a management terminal for a configuration page of the first application; the list acquisition request is determined by the management terminal in response to a triggering operation triggered by a configuration interface for the configuration page;

a second obtaining subunit, configured to obtain a to-be-allocated user list associated with a first user in the first application according to the list obtaining request;

and the returning subunit is used for returning M users to be distributed, which are associated with the first user, in the list of the users to be distributed to the management terminal so that the management terminal outputs the first user and the M users to be distributed on a first display interface.

Wherein the second acquisition unit includes:

the receiving subunit is used for receiving an address book acquisition request sent by the management terminal based on the first user; the address book acquisition request is determined by the management terminal in response to a triggering operation for triggering an allocation button in the first display interface;

the searching subunit is used for acquiring the user information of the first user carried in the address book acquisition request, searching a group to which the first user belongs according to the user information, and sending an address book corresponding to the group to the management terminal so that the management terminal outputs the address book on a second display interface;

The third acquisition subunit is used for acquiring a second user determined by the management terminal aiming at the address book on the second display interface;

and the fourth acquisition subunit is used for acquiring the initial binding relation between the N users to be distributed and the second user, which is established by the management terminal.

Wherein the apparatus further comprises:

the splitting module is used for splitting each inheritance request in the batch inheritance requests, and each split inheritance request is respectively added to a task queue;

the second generation module is used for generating the adding response information corresponding to each inheritance request when each inheritance request is added to the task queue;

and the return module is used for returning the adding response information to the management terminal so that the management terminal sets the service state corresponding to each inheritance request to be a state to be confirmed based on the adding response information.

Wherein the first generation module comprises:

a fourth obtaining unit, configured to obtain a first relationship record table corresponding to a user to be allocated associated with the first user, find first verification key information in the first relationship record table, and determine the user to be allocated in a list column where the first verification key information is located as a target user to be allocated; the first verification key information is used for representing the bidirectional association relationship between the first user and the user to be allocated;

A fifth obtaining unit, configured to obtain a second relationship record table associated with the first user, find second calibration key information in the second relationship record table, and obtain a second user in a list field where the second calibration key information is located; the second check key information is used for representing a group association relationship between the first user and the second user;

the determining unit is used for taking the two-way association relationship and the group association relationship as verification key information;

the generation unit is used for generating configuration text information associated with the second user according to the initial binding relation between the target user to be distributed and the second user, the second account information of the second user and the verification key information.

Wherein, the establishment module includes:

the verification unit is used for verifying the bidirectional association relation in the verification key information based on the friend adding request and verifying the group association relation;

the first sending unit is used for sending the friend adding request to the second account information when the verification is successful;

the establishing unit is used for establishing a bidirectional association relation between the target user to be allocated and the second user.

Wherein, the sending module includes:

the second sending unit is used for sending the configuration text information to a second server according to the first account information of the first user so that the second server forwards the configuration text information to a target user terminal corresponding to a target user to be distributed;

the receiving unit is used for receiving a friend adding request forwarded by the second server when the request initiator is determined to be the target user to be distributed; the friend adding request is generated by the target user terminal based on the second account information in the configuration text information.

In one aspect, the present application provides a computer device comprising: a processor, a memory, a network interface;

the processor is connected with the memory and the network interface, wherein the network interface is used for providing a data communication function, the memory is used for storing a computer program, and the processor is used for calling the computer program to execute the method in the aspect in the embodiment of the application.

An aspect of the present application provides a computer readable storage medium storing a computer program comprising program instructions which, when executed by a processor, perform the method of the above aspect of the embodiments of the present application.

In one aspect, another data processing apparatus is provided in an embodiment of the present application, where the apparatus is applied to a user terminal corresponding to a second application, and includes:

the receiving module is used for receiving configuration text information sent by the first server corresponding to the first application according to the first account information of the first user; the configuration text information comprises second account information of a second user and verification key information for verification;

the display module is used for responding to the triggering operation of the conversation interface where the configuration text information is located and displaying a friend adding interface independent of the conversation page; the friend adding interface comprises the second account information;

the request sending module is used for responding to the friend adding operation aiming at the friend adding interface and sending a friend adding request to the second account information; the friend adding request is used for indicating the first server to establish a bidirectional association relationship between the target user to be allocated and the second user when the first server successfully verifies the verification key information, wherein the user to be allocated is a user in the second application different from the first application.

In the embodiment of the application, a first server corresponding to a first application can acquire a batch inheritance request sent by a management terminal for a second user associated with the first user; the batch inheritance request is determined by the management terminal after service allocation is carried out on users to be allocated which are associated with the first user; the user to be allocated is a user in a second application different from the first application; at this time, the first server may determine a target to-be-allocated user having a bi-directional association relationship with the first user from the to-be-allocated users, and generate configuration text information associated with the second user according to an initial binding relationship between the target to-be-allocated user and the second user; the configuration text information comprises second account information of the second user and verification key information for verification; further, the first server may send the configuration text information to a target user terminal corresponding to the target user to be allocated according to the first account information of the first user, so that the target user terminal generates a friend adding request for the second account information based on the configuration text information; and verifying the verification key information according to the friend adding request, and establishing a bidirectional association relation between the target user to be allocated and the second user when the verification is successful. Therefore, in the embodiment of the application, the first server corresponding to the first application may acquire the batch inheritance request sent by the management terminal for the second user associated with the first user, and further, the first server may allocate the to-be-allocated user associated with the first user in the second application to the second user in batches based on the batch inheritance request, so that the second user inherits the to-be-allocated user in batches, thereby improving the processing efficiency of the service data. In addition, the embodiment of the application assigns the user to be assigned associated with the first user to the second user, so that the loss of service data can be prevented.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic structural diagram of a network architecture according to an embodiment of the present application;

fig. 2 is a schematic view of a scenario for data interaction according to an embodiment of the present application;

FIG. 3 is a schematic flow chart of a data processing method according to an embodiment of the present application;

fig. 4 is a schematic view of a scenario for selecting a user to be allocated according to an embodiment of the present application;

FIG. 5 is a schematic view of a first display interface according to an embodiment of the present disclosure;

FIG. 6 is a schematic diagram of a second display interface according to an embodiment of the present disclosure;

fig. 7a is a schematic diagram of checking association according to an embodiment of the present application;

fig. 7b is a schematic diagram of a session interface between a second user and a target user to be allocated according to an embodiment of the present application;

FIG. 8 is a flowchart of another data processing method according to an embodiment of the present disclosure;

FIG. 9 is a schematic view of a scenario for splitting a batch inheritance request provided in an embodiment of the present application;

FIG. 10 is a schematic diagram of a data processing apparatus according to an embodiment of the present application;

FIG. 11 is a schematic diagram of a computer device provided in an embodiment of the present application;

FIG. 12 is a schematic diagram of another data processing apparatus provided herein;

FIG. 13 is a schematic diagram of another computer device provided in an embodiment of the present application;

FIG. 14 is a schematic diagram of a data processing system according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

Fig. 1 is a schematic structural diagram of a network architecture according to an embodiment of the present application. As shown in fig. 1, the network architecture may include a first server 1000, a second server 2000, and a management terminal 3000, a first user terminal cluster and a second user terminal cluster. The first user terminal cluster may include a plurality of user terminals, and as shown in fig. 1, may include a user terminal 4000a, a user terminal 4000b, user terminals 4000c, …, and a user terminal 4000n. The second user terminal cluster may include a plurality of user terminals, as shown in fig. 1, and may specifically include a user terminal 5000a, a user terminal 5000b, user terminals 5000c, …, and a user terminal 5000n.

As shown in fig. 1, the management terminal 3000 may be in network connection with the first server 1000, so that the management terminal 3000 may perform data interaction with the first server 1000 through the network connection. In addition, the user terminals 4000a, 4000b, 4000c, …, 4000n may respectively make network connections with the second server 2000 so that each user terminal may interact with the second server 2000 through the network connections. The user terminals 5000a, 5000b, 5000c, …, 5000n may be respectively network connected to the first server 1000, so that each user terminal may interact with the second server 1000 via the network connection.

As shown in fig. 1, each of the management terminal 3000 and the second user terminal cluster may be integrally installed with a first application. The first application may be an instant messaging application, where the first application may be an office-type application (e.g., an enterprise WeChat application). When the first application is run on each user terminal in the management terminal 3000 and the second user terminal cluster, data interaction may be performed with the first server 1000 shown in fig. 1 described above. Furthermore, each user terminal in the first cluster of user terminals may be integrally installed with a second application. Wherein the second application may be another instant messaging application (e.g., a WeChat application) that is different from the first application. When the second application is running on each user terminal, data interaction can be performed between the second application and the second server 2000 shown in fig. 1. The user in the first application can conduct data interaction with the user in the second application through voice short messages, videos, pictures, words and the like. It will be appreciated that all users in the first application belong to the same group and that a user may be present in multiple groups.

For easy understanding, each of the management terminal 3000 and the second user terminal in the second user terminal cluster in the embodiment of the present application may include: smart terminals with instant messaging functions such as smart phones, tablet computers, desktop computers and the like. Wherein each user terminal of the management terminal 3000 and the second user terminal cluster may integrate the first application described above. It may be appreciated that the embodiment of the present application may select one user terminal from the plurality of user terminals of the first user terminal cluster shown in fig. 1 as the target user terminal. The target user terminal may include: smart terminals with instant messaging functions such as smart phones, tablet computers, desktop computers and the like. For example, in the embodiment of the present application, the user terminal 4000a shown in fig. 1 may be used as a target user terminal, and the target user terminal may integrate the second application. At this time, each user terminal in the management terminal 3000 and the second user terminal cluster may implement data interaction with the first server 1000 through the service data platform corresponding to the first application, where the first server 1000 may implement data interaction with the second server 2000, and the second server 2000 may implement data interaction with the target user terminal.

For example, when accessing the first application (e.g., an enterprise WeChat application), an administrator corresponding to the management terminal 3000 may perform a triggering operation for a sub-application (e.g., a customer contact application) of the business data platform in the first application. The sub-application may be used for data interaction with the second application (e.g., a WeChat application). At this point, the manager may enter the sub-application and perform a triggering operation on a configuration interface in the sub-application (e.g., a customer that distributes off-office members). In this embodiment of the present application, the current display interface (for example, the page where the configuration interface is located) of the sub-application may be referred to as a configuration page.

Further, the management terminal 3000 may send a service request to the first server 1000 in response to a triggering operation triggered by the manager for the configuration interface of the configuration page. In this embodiment, the service request for obtaining the list request to be allocated may be referred to as a list obtaining request. The first server 1000 may acquire a list of users to be allocated associated with a first user (for example, user a) in the first application based on the list acquisition request, and further, may return M users to be allocated in the list of users to the management terminal 3000, so that the management terminal outputs the first user and M users to be allocated associated with the first user on a display interface. In this embodiment of the present application, the display interface displaying the to-be-allocated user list may be referred to as a first display interface. The user to be allocated is a user in a second application different from the first application; and M is a positive integer.

In this embodiment of the present application, the user having a user to be allocated may be collectively referred to as a first user, and it may be understood that the first user may be one or more users in the first application, and the first user may include any one of the following users: the system can be taken as an off-duty employee of an enterprise, an employee of a holiday of the enterprise, an employee who is away from a post, and the like, and is not exemplified here.

It should be understood that the management terminal 3000 may determine N users to be allocated from M users to be allocated in response to a triggering operation triggered by the manager for the first display interface. Wherein N is a positive integer less than or equal to M. At this time, the management terminal 3000 may transmit a service request to the first server 1000 by responding to a trigger operation triggered by the manager for an allocation button (e.g., allocated to other members) in the first display interface. In this embodiment of the present application, the service request for obtaining the address book of the group to which the first user belongs may be referred to as an address book obtaining request.

Further, the first server 1000 may acquire the user information of the first user carried in the address book acquisition request, search the group of the first user according to the user information, and send the address book corresponding to the group to the management terminal 3000, so that the management terminal 3000 outputs the address book on the display interface. In this embodiment of the present application, the display interface for displaying the address book of the group to which the first user belongs may be referred to as a second display interface.

It is to be understood that the group may be a small group (for example, a sales group) to which the first user belongs, a department group (for example, a sales group) to which the first user belongs, an enterprise group (for example, an a enterprise group) to which the first user belongs, or the like, which is not illustrated here.

It should be appreciated that the administrator corresponding to the administrative terminal 3000 may determine the user associated with the first user (e.g., user B) from the address book on the second display interface. At this time, the embodiment of the present application may refer to this user B as the second user. At this time, the management terminal 3000 may establish the initial binding relationship between the N users to be allocated and the second user. In other words, the manager may assign the N users to be assigned to the user B (second user) determined from the address book of the group to which the user a (first user) belongs.

Further, the first server 1000 may acquire a service request associated with the user B, which the management terminal 3000 transmits based on the initial binding relationship. The service request for distributing the user to be distributed associated with the first user may be referred to as a batch inheritance request in the embodiment of the application. At this time, the first server 1000 may determine a user to be allocated having a bi-directional association relationship (i.e., bi-directional friend relationship) with the first user from among the users to be allocated, which is referred to as a target user to be allocated (e.g., user C). It is understood that the first server 1000 may generate the configuration text information associated with the user B according to the initial binding relationship between the user C and the user B. For example, the configuration text information may be "user A has left his job, his colleague user B has taken over his job, you can contact user B". The configuration text information may include account information (second account information) of the user B and verification key information for performing verification, where the verification key information may be used to verify a bidirectional association relationship between the user a (first user) and the user C (target user to be allocated) and a group association relationship between the user a and the user B.

It should be understood that, according to the account information (first account information) of the user a, the first server 1000 may send the configuration text information to the second server 2000 shown in fig. 1, where the second server 2000 forwards the configuration text information to the target user terminal (i.e., the user terminal 4000 a) corresponding to the user C, so that the user terminal 4000a outputs the configuration text information on the chat display interface between the user C and the user a. The chat display interface may be referred to as a session interface.

Further, the user terminal 4000a may respond to a trigger operation of the user C for an operability area trigger in the configuration text information within a validity period (e.g., 7 days) of the configuration text information. At this time, the user terminal 4000a may display a display interface independent of the session interface. In this embodiment of the present application, the display interface for displaying the second account information may be referred to as a friend adding interface. It may be appreciated that the user terminal 4000a may generate a service request in response to the friend adding operation of the user C for the friend adding interface. The service request for adding the second user may be referred to as a friend adding request in the embodiment of the present application. At this time, the user terminal 4000a may transmit the friend addition request to the second server 2000. The second server 2000 may forward the friend addition request to the first server 1000 upon determining that the request originator of the friend addition request is user C.

It should be understood that, based on the friend addition request, the first server 1000 may verify the two-way association relationship and the group association relationship in the above-mentioned verification key information, respectively. When the verification is successful, the first server 1000 may send the friend adding request to account information of the user B, so as to establish a bidirectional association relationship between the user C (target user to be allocated) and the user B (second user).

Further, please refer to fig. 2, which is a schematic diagram of a scenario for data interaction according to an embodiment of the present application. As shown in fig. 2, the management terminal may be the management terminal 3000 in fig. 1, the first server may be the first server 1000 in fig. 1, the second server may be the second server 2000 in fig. 1, and the target user terminal may be the user terminal 4000a in fig. 1.

The first display interface 100a of the management terminal shown in fig. 2 may include a first user and a plurality of users to be allocated associated with each first user. For example, the first display interface 100a may include a first user (user 10a and user 10 b), a user to be assigned (user 20a, user 20b, user 30a, user 30b, and user 30 c), and an assignment button as shown in fig. 2. Among them, the users to be allocated associated with the user 10a (employee a) may be the user 20a (customer a) and the user 20B (customer B), and the users to be allocated associated with the user 10B (employee B) may be the user 30a (customer C), the user 30B (customer D), and the user 30C (customer E). At this time, the list of users to be allocated displayed on the first display interface 100a may be acquired by the first server upon receiving the management terminal transmission list acquisition request.

It may be understood that, a manager corresponding to the management terminal may perform a triggering operation (for example, a touch operation such as clicking, long pressing, etc.) with respect to a configuration interface (for example, a client that allocates an off-office member) of a configuration page of a first application (enterprise WeChat application), and the management terminal may respond to a list acquisition request sent by the triggering operation to the first server. Further, the first server may obtain a list of users to be allocated associated with the first user in the first application according to the list obtaining request. It should be appreciated that the first server may return the plurality of users to be allocated associated with the first user in the list of users to be allocated to the management terminal, so that the management terminal outputs the first user and the plurality of users to be allocated on the first display interface 100 a.

It will be appreciated that, as shown in fig. 2, for convenience of explanation, only two first users, namely employee a and employee B, are taken as examples in the embodiment of the present application. Wherein there are two users to be assigned associated with employee a, customer a and customer B. There are three users to be assigned associated with employee B, customer C, customer D, and customer E.

The manager may perform a triggering operation in the to-be-allocated user list in the first display interface 100a, and obtain N to-be-allocated users from M to-be-allocated users in the to-be-allocated user list, where N is a positive integer less than or equal to M. The manager can determine a user to be allocated associated with the first user within a preset allocation threshold range of the first user of the management terminal. For example, the allocation threshold may be preset to 50, and the manager may determine the users to be allocated associated with 50 first users. When the manager performs trigger operation on the 51 st first user, the management terminal may pop up a reminder message to remind the manager that the number of the first users determined by the manager exceeds the allocation threshold. For example, the alert message may be "only 50 off-staff people can be selected at most at a time".

For example, as shown in fig. 2, the embodiment of the present application may determine two users, namely, the client a and the client B, as users to be allocated, and it may be understood that the first user associated with the two users to be allocated is employee a. Further, the manager may perform a trigger operation with respect to an allocation button (e.g., allocated to other member (1)) in the first display interface 100 a. Wherein the allocation button may display a record of the number of first users. At this time, the management terminal may send an address book acquisition request associated with employee a to the first server in response to the trigger operation.

It should be understood that, as shown in fig. 2, the first server may acquire the user information of the first user (employee a) carried in the address book acquisition request, find a group to which the first user belongs, and send an address book corresponding to the group to the management terminal, so that the management terminal outputs the address book on the second display interface 200 a. As shown in fig. 2, the second display interface 200a may include address books of the group to which the employee a belongs, that is, the user 40a (employee C), the user 40b (employee D), and the user 40C (employee E). It is to be understood that the group may be a small group (e.g., sales group) to which employee a belongs, a department group (e.g., sales group) to which employee a belongs, an enterprise group (a enterprise group) to which employee a belongs, or the like, which is not limited herein.

Further, the management terminal may determine the second user (employee D) from the address book of the group to which employee a belongs in response to the triggering operation of the manager with respect to the second display interface 200 a. In other words, the manager may perform a triggering operation on the user 40b with respect to the address book of the second display interface 200a, so that the management terminal may pop up a window 2000a to the manager in response to the triggering operation. For example, "determine to assign the customer to employee D". The manager may determine that the second user is employee D by triggering the confirm button of the window 2000a. The method and the device can be used for more accurately reassigning the users to be assigned to the appropriate second users (staff D) by looking at the group to which the first users (staff A) belong.

It should be appreciated that as shown in fig. 2, the management terminal may establish an initial binding relationship between the two users to be allocated and the second user (employee D) and send a batch inheritance request associated with employee D to the first server. At this time, the first server may determine, from the two users to be allocated, a user having a bi-directional association relationship with the first user (employee a) as a target user to be allocated (for example, client a). Further, based on the initial binding relationship between client A and employee D, the first server may generate configuration text information associated with employee D. The configuration text information includes account information (second account information) of the employee D and verification key information for verification.

Further, the second server may receive the configuration text information associated with employee D sent by the first server and forward the configuration text information to the target user terminal associated with the target user to be assigned (client a). At this time, the target user terminal corresponding to the client a may output the configuration text information on the session interface 300 a. The session interface 300a may display a chat log of client a with employee a, among other things. At this time, the client a may perform a triggering operation for the operability area in the configuration text information within the validity period (for example, 7 days) of the configuration text information, so that the target user terminal may display the friend adding interface 400a independent of the session interface 300 a. The friend adding interface 400a includes account information (second account information) of the employee D.

It should be appreciated that the client a may perform a friend adding operation with respect to a friend adding button (e.g., contact with him) in the friend adding interface 400a, generate a friend adding request, and send the friend adding request to the second server. At this time, the second server checks the friend adding request, and when the second server determines that the request initiator of the friend adding request is the client a, the second server forwards the friend adding request to the first server.

It should be understood that, based on the friend adding request, the first server may verify the two-way association relationship and the group association relationship in the above-mentioned verification key information respectively. When the first server checks successfully, the friend adding request can be sent to the account information of the staff D, so that a bidirectional association relationship between the client A and the staff D is established.

The specific implementation manner of the first server to distribute the users to be distributed associated with the first user to the second user associated with the first user in batches may be referred to in the embodiments corresponding to fig. 3 to fig. 9 below.

Further, please refer to fig. 3, which is a flowchart illustrating a data processing method according to an embodiment of the present application. The method can be applied to a first server corresponding to the first application. As shown in fig. 3, the method includes:

s101, acquiring a batch inheritance request sent by a management terminal aiming at a second user associated with a first user.

Specifically, the management terminal may send a batch inheritance request to a first server corresponding to the first application in response to a triggering operation of the manager for a second user associated with the first user. Wherein the batch inheritance request is determined by the management terminal after service allocation is carried out on users to be allocated associated with the first user; the user to be allocated is a user in a second application different from the first application.

It should be understood that the management terminal in the embodiment of the present application may be the management terminal in the embodiment corresponding to fig. 2, and the management terminal may be the management terminal 3000 in the embodiment corresponding to fig. 1. In addition, the first server corresponding to the first application in the embodiment of the present application may be the first server in the embodiment corresponding to fig. 2, and the first server may be the first server 1000 in the embodiment corresponding to fig. 1.

It will be appreciated that the management terminal integrating the first application (e.g., enterprise WeChat application) may respond to a triggering operation performed by a manager for a configuration interface (e.g., a client that distributes off-office members) in a configuration page of the first application, at which time a list retrieval request may be sent to the first server. The triggering operation may include a touch operation such as clicking or long pressing, or may include a non-touch operation such as voice or gesture, which will not be limited herein.

It should be appreciated that the first server may obtain a list of users to be allocated associated with a first user (e.g., user a) in the first application based on the list obtaining request. The first user may be one or more users in the first application, and the first user may be an off-duty employee of the enterprise, an employee of the enterprise who is on holiday, an employee who is on the shift, or the like, which is not illustrated here.

Further, the first server may return the M users to be allocated in the list of users to be allocated to the management terminal, so that the management terminal outputs the first user and the M users to be allocated associated with the first user on the first display interface. Wherein M is a positive integer; the user to be allocated is a user in a second application (e.g., a WeChat application) different from the first application.

It should be understood that the management terminal may determine N users to be allocated from M users to be allocated in response to a triggering operation triggered by the manager for the first display interface. Wherein N is a positive integer less than or equal to M. The method and the device can select a plurality of users to be distributed, which are associated with the first user, so that the cost of the manager for distributing the single users to be distributed is saved, the time is saved, and the processing efficiency of the business data is improved.

For ease of understanding, further, please refer to fig. 4, which is a schematic view of a scenario for selecting a user to be allocated according to an embodiment of the present application. The management terminal may display a plurality of first users and a plurality of users to be allocated associated with each first user. In the embodiment of the present application, only two first users are taken as examples, which are used for explaining the selection manner of the users to be allocated. The management terminal may be the management terminal 3000 shown in fig. 1.

As shown in fig. 4, a list of users to be allocated and an allocation button may be displayed on the first display interface 100a of the management terminal. Wherein the list of users to be allocated may comprise two first users, namely user 10a and user 10b, and the users to be allocated associated with the first users. Among them, it can be understood that, in the first display interface 100a of the management terminal, the users to be allocated associated with the user 10a (employee a) can be the user 20a (i.e., the client a) and the user 20B (i.e., the client B). The users to be assigned associated with user 10B (i.e., employee B) may be user 30a (i.e., customer C), user 30B (i.e., customer D), and user 30C (i.e., customer E). In addition, the first display interface 100a further includes an allocation button, that is, "allocate to other members". It will be appreciated that the allocation button may display the number of first users determined by the manager through a trigger operation.

It should be appreciated that when the manager determines the user to be allocated through a trigger operation in the first display interface 100a, the allocation button on the first display interface 100a may display the number of first users associated with the user to be allocated, which is currently determined by the manager. It is understood that the manager may determine the user to be allocated associated with the first user within a preset allocation threshold of the first user of the management terminal. For example, the allocation threshold may be preset to 50, and the manager may determine the users to be allocated associated with 50 first users. When the manager performs trigger operation on the 51 st first user, the management terminal may pop up a reminder message to remind the manager that the number of the first users determined by the manager exceeds the allocation threshold. For example, the alert message may be "only 50 off-staff people can be selected at most at a time".

Further, the manager may determine the number of users to be allocated in the list of users to be allocated. In the first display interface 100b shown in fig. 4, the manager may perform a trigger operation for the user to be allocated in the list of users to be allocated, and determine the user to be allocated in the form of a single person selection. For example, the manager may perform a trigger operation for the user 20B in the to-be-allocated user list, so that a to-be-allocated user, that is, the client B, may be determined. The allocation button in the first display interface 100b may display the number of the first user, that is, "allocate to other members (1)".

Optionally, in the first display interface 100c shown in fig. 4, the manager may further perform a triggering operation on the first user in the to-be-allocated user list, so as to determine the to-be-allocated user in a form of one-time multi-user selection. For example, the manager may perform a trigger operation for user 10B (i.e., employee B) in the list of users to be assigned, so that three users to be assigned associated with employee B, namely customer C, customer D, and customer E, may be determined. It should be noted, among other things, that after a one-time multi-person selection is made for user 10a, the single person selections for customer C, customer D and customer E are disabled. The allocation button in the first display interface 100c may display the number of the first user, that is, "allocate to other members (1)".

In addition, in the first display interface 100d shown in fig. 4, the manager may perform a one-time multi-person selection for the first user in the to-be-allocated user list, and then perform a single-person selection for to-be-allocated users associated with other first users in the to-be-allocated user list. For example, the manager may perform a trigger operation for the user 10B (i.e., the client B) in the to-be-allocated user list, thereby determining three to-be-allocated users, i.e., the client C, the client D, and the client E. The manager may then perform a triggering operation again for the user to be allocated (e.g., user 20B) associated with user 10a, respectively, to determine the user to be allocated, client B. In other words, the manager may determine four users to be allocated in the list of users to be allocated. The allocation button in the first display interface 100d may display the number of the first user, that is, "allocate to other members (2)". In addition, the manager may perform single-person selection on the first user in the to-be-allocated user list, and perform one-time multi-person selection on to-be-allocated users associated with other first users in the to-be-allocated user list, which is not limited herein.

Further, please refer to fig. 5, which is a schematic diagram of a first display interface according to an embodiment of the present application. The management terminal can be an intelligent terminal with an instant messaging function, such as a tablet personal computer, a desktop computer and the like. As shown in fig. 5, a list of users to be allocated and an allocation button may be displayed on the first display interface 100e of the smart terminal.

It may be understood that, when receiving the list acquisition request sent by the management terminal for the configuration page, the first server may return the list of users to be allocated shown in fig. 5 to the management terminal. The to-be-allocated user list may display a plurality of to-be-allocated users, and in this embodiment, only 5 to-be-allocated users are taken as an example. In the first display interface 100E of the management terminal, all users to be allocated associated with the first user, namely, user 20a (i.e., client a), user 20B (i.e., client B), user 30a (i.e., client C), user 30B (i.e., client D), and user 30C (i.e., client E), may be displayed.

It will be appreciated that the manager may perform a triggering operation for the original adder, and pop up the window 1000a of the selected original adder independent of the first display interface 100 e. The window 1000a may display a plurality of first users, such as user 10a (i.e., employee A) and user 10B (employee B). Among other things, it is understood that user 10a is a first user associated with user 20a (i.e., client a) and user 20B (i.e., client B), and user 10B is a first user associated with user 30a (i.e., client C), user 30B (i.e., client D), and user 30C (i.e., client E).

For example, the manager may perform a triggering operation for the user 10b in the window 1000 a. When the manager activates the confirm button in the window 1000a, the list of users to be allocated of the first display interface 100E of the management terminal may display users to be allocated, that is, the client C, the client D, and the client E, associated with the employee B. At this time, the manager may perform multiple triggering operations for the three users to be allocated, to determine the users to be allocated.

Optionally, the manager may perform a plurality of triggering operations in displaying all users to be allocated associated with the first user, to determine the users to be allocated. For example, the manager may trigger the user 20a to determine that the client a is the user to be allocated. The manager may then trigger the user 30a to determine that the customer C is the user to be allocated.

It should be understood that, for convenience of explanation, as shown in the corresponding embodiment of fig. 2, this embodiment of the present application is only exemplified by one first user (user 10 a) to explain that the management terminal sends a batch inheritance request to the first server. It will be appreciated that, by determining the users to be allocated as described above, the manager can determine two users to be allocated, user 20a (client a) and user 20B (client B), associated with user 10a (employee a). Further, the manager may perform a trigger operation on the allocation button (i.e., allocated to other members) in the first display interface 100a shown in fig. 4 described above or the allocation button (i.e., allocated to other members) in the first display interface 100e shown in fig. 5 described above. At this time, the management terminal may send an address book acquisition request to the first server in response to the trigger operation.

Further, the first server may acquire the user information of the first user (employee a) carried in the address book acquiring request, find a group to which the first user belongs, and send an address book corresponding to the group to the management terminal, so that the management terminal outputs the address book on the second display interface 200 a.

For ease of understanding, please refer to fig. 6, which is a schematic diagram of a second display interface according to an embodiment of the present application. The management terminal may be the management terminal 3000 shown in fig. 1 described above. The second display interface 200a of the management terminal may display an address book of the group associated with the first user. In this embodiment, only three users in the address book are taken as examples, so as to describe the determining process of the second user.

As shown in fig. 6, the second display interface may include address books of the group to which employee a belongs, that is, user 40a (employee C), user 40b (employee D), and user 40C (employee E). It will be appreciated that the administrator may perform a triggering operation for the user 40b of the second display interface 200 a. At this time, the management terminal may pop up a window 2000a independent of the second display interface 200a to the manager in response to the triggering operation. For example, the window 2000a may display a confirmation message, "determine to assign the customer to employee D? ". The manager may determine that the second user is employee D by triggering the confirm button of the window 2000a. Among other things, the embodiments of the present application may determine the second user from the group to which the first user (employee a) belongs, so as to more accurately reassign the user to be assigned associated with the first user to the second user (other employee, for example, employee D) who is suitably in succession to the first user. Further, the management terminal may establish initial binding relationships between the client a and the client B and the employee D, respectively, and send a batch inheritance request associated with the employee D to the first server.

S102, determining a target to-be-allocated user with a two-way association relation with the first user from the to-be-allocated users, and generating configuration text information associated with the second user according to an initial binding relation between the target to-be-allocated user and the second user.

The configuration text information comprises second account information of the second user and verification key information for verification.

Specifically, the first server may obtain a first relationship record table corresponding to a user to be allocated associated with the first user, and find first verification key information in the first relationship record table. At this time, the first server may determine the user to be allocated in the list column where the first verification key information is located as the target user to be allocated. Further, the first server may obtain a second relationship record table associated with the first user, and look up second check-up key information in the second relationship record table. At this time, the first server may acquire the second user in the list field where the second check-up key information is located. It should be understood that the first server may use the bi-directional association relationship and the group association relationship as verification key information. Further, the first server may generate configuration text information associated with the second user according to the initial binding relationship between the target user to be allocated and the second user, the second account information of the second user, and the verification key information. The first verification key information is used for representing the bidirectional association relationship between the first user and the user to be distributed; the second check-up key information is used for representing a group association relationship between the first user and the second user.

It should be understood that, after performing step S101 described above, the management terminal may establish an initial binding relationship between the client a and the client B and the employee D, and send a batch inheritance request associated with the employee D (second user) to the first server. Where customer a and customer B are users to be assigned associated with employee a (first user).

It should be appreciated that the first server may obtain a first relationship record table corresponding to the user to be assigned associated with employee a. For easy understanding, please refer to table 1, which is a bidirectional association record table provided in the embodiment of the present application.

TABLE 1

User in second application associated with employee A	Association relation
		Customer A	Two-way association relation (first check key information)
Customer B	One-way association relation

It can be understood that, as shown in table 1, the association relationship between the client a and the employee a is a bidirectional association relationship, and the association relationship between the client B and the employee a is a unidirectional association relationship. In the embodiment of the application, the bidirectional friend relationship between the client a and the employee a may be referred to as a bidirectional association relationship, and the unidirectional friend relationship between the client B and the employee a may be referred to as a unidirectional association relationship. The first verification key information can be used for representing the bidirectional association relation between the employee A and the user to be distributed.

It may be appreciated that the first server may obtain the first relationship record table shown in table 1, and may search the first relationship record table for the first verification key information. When the first server finds the first verification key information, the user to be allocated (i.e., client a) in the list column where the first verification key information is located may be determined as the target user to be allocated.

Further, the first server may obtain a second relationship record table associated with employee A. For ease of understanding, please refer to table 2, which is a group association table provided in the embodiment of the present application.

TABLE 2

User in first application associated with employee A	Association relation
		Staff C	Group association relation (second check key information)
Staff D	Group association relation (second check key information)
		Staff E	Non-group association relationship

It can be understood that, as shown in the above table 2, the association relationship between the employee C and the employee a is a group association relationship, the association relationship between the employee D and the employee a is a group association relationship, and the association relationship between the employee E and the employee a is a non-group association relationship. In this embodiment of the present application, the association relationship of the employee C and the employee a belonging to the same group may be referred to as a group association relationship, and the association relationship of the employee E and the employee a belonging to different groups may be referred to as a non-group association relationship. The second check-up key information may be used to characterize a group association between employee a and the second user.

It will be appreciated that the first server may obtain a second record relationship table as shown in table 2 above, and may look up the second check-up key information in the second record relationship table. As shown in table 2, the first server may find that there are two users (i.e., employee C and employee D) in the list field where the second check-up key information is located. It will be appreciated that both users may inherit as the second user the target to-be-assigned user associated with employee a.

It should be understood that the first server may use the above-mentioned two-way association relationship and the group association relationship as the verification key information. Further, since the second user determined by the manager from the address book of the group to which the employee a belongs is the employee D, the first server may generate the configuration text information associated with the employee D according to the initial binding relationship between the client a (the target user to be allocated) and the employee D (the second user), the account information (the second account information) of the employee D, and the verification key information.

And S103, according to the first account information of the first user, sending the configuration text information to a target user terminal corresponding to the target user to be distributed, so that the target user terminal generates a friend adding request aiming at the second account information based on the configuration text information.

Specifically, the first server may send the configuration text information to a second server corresponding to a second application (WeChat) according to the first account information of the first user. And at this time, the second server forwards the configuration text information to a target user terminal corresponding to the target user to be allocated, so that the configuration text information is displayed on a session interface of the target user terminal. The session interface may be a session interface between the first user and the target user to be allocated. Further, the target user to be allocated can execute triggering operation for the session interface. At this time, the target user terminal may respond to the triggering operation to display a friend adding interface independent of the session interface. Further, the target to-be-allocated user can execute friend adding operation on the friend adding interface. At this time, the management terminal may respond to the friend adding operation and send a friend adding request to the second server. And when the second server determines that the request initiator is the target user to be allocated, adding the request to the friend forwarded by the first server.

It should be understood that the second server corresponding to the second application in the embodiment of the present application may be the second server in the embodiment corresponding to fig. 2, and the second server may be the second server 2000 in the embodiment corresponding to fig. 1. In addition, the target ue in the embodiment of the present application may be the target ue in the embodiment corresponding to fig. 2, and the target ue may be the ue 3000a in the embodiment corresponding to fig. 1.

It should be understood that, after performing the step S102, the first server may generate the configuration text information associated with the employee D according to the initial binding relationship between the client a (target user to be allocated) and the employee D (second user), the account information of the employee D (second account information), and the verification key information.

Further, the first server may send the configuration text information to the second server according to the account information (first account information) of the employee a. At this time, the second server may forward the configuration text information to the target user terminal corresponding to the client a. As shown in fig. 2, on the session interface 300a between the client a and the employee a of the target user terminal, the configuration text information forwarded by the second server may be displayed. For example, the configuration text information may be "employee A has left his colleague employee D has taken over his work, you can contact employee D".

It should be appreciated that the client a may trigger for an operability area in the configuration text information within a validity period (e.g., 7 days) of the configuration text information, so that the target user terminal may display a buddy addition interface 400a independent of the session interface 300 a. The friend adding interface 400a may include account information of the employee D. At this time, the client a may perform a friend adding operation with respect to a friend adding button (e.g., contact with him) in the friend adding interface 400a. The target user terminal may respond to the friend adding operation, generate a friend adding request associated with the employee D, and send the friend adding request to the second server. Further, the second server checks the friend adding request, and when the second server determines that the request initiator of the friend adding request is the client A, the second server forwards the friend adding request to the first server.

It can be understood that if the client a fails to perform a triggering operation on the configuration text information within the validity period of the configuration text information, the configuration text information is disabled. In other words, the first server does not receive the friend adding request sent by the target user terminal within seven days when sending the configuration text information to the target user terminal corresponding to the client a. At this time, the first server may re-add the client a to the first display interface 100a of the management terminal so that the client a is re-displayed in the to-be-allocated user list.

S104, checking the checking key information according to the friend adding request, and establishing a bidirectional association relation between the target user to be allocated and the second user when the checking is successful.

Specifically, the first server may verify the bidirectional association relationship in the verification key information based on the friend addition request, and verify the group association relationship. And the first server can send the friend adding request to the second account information when the verification is successful. Further, the first server may establish a bi-directional association relationship between the target user to be allocated and the second user.

For easy understanding, further, please refer to fig. 7a, which is a schematic diagram for checking association relationships according to an embodiment of the present application. The client a, the employee a, and the employee D in the embodiment of the present application may be the target to-be-allocated user, the first user, and the second user determined in the foregoing correspondence of the embodiment of fig. 2. That is, as shown in the embodiment corresponding to fig. 2, the first server may receive a friend adding request sent by the target user terminal corresponding to the client a to the account information (second account information) of the employee D.

Further, as shown in fig. 7a, when the first server obtains the friend adding request, the bidirectional association relationship and the group association relationship in the verification key information may be verified respectively. That is, the first server needs to check the two-phase association relationship (two-way friend relationship) between employee a and client a, and the group association relationship (same group) between employee a and employee D. When the verification is successful, the first server can send the friend adding request to the account information of the staff D, so that a bidirectional association relationship between the client A and the staff D is established. In the embodiment of the application, the first server checks the two-way association relationship and the group association relationship again for the friend adding request, so that the situation of adding the two-way friends through illegal means can be avoided.

For ease of understanding, further, please refer to fig. 7b, which is a schematic diagram of a session interface between the second user and the target user to be allocated according to an embodiment of the present application. The target ue may be the target ue corresponding to fig. 2. The session interface 500a may be a session interface between employee D and customer a.

It can be understood that, after the client a and the employee D are successfully added by the friend adding request, a greeting message preset in advance by the employee D may be displayed on the session interface 500a of the target user terminal corresponding to the client a. The greeting message may be a greeting message that is actively sent to the friend by the employee D each time the friend is successfully added. For example, "you good, i am employee D, very happy to serve you.

As shown in fig. 7b, the session interface 500a of the target user terminal may also display a prompt text message. For example, the prompt text message may be "opposite party takes over employee A and you to see a chat log with employee A". It will be appreciated that the client a may trigger an operation for an operability area in the prompt text information of the session interface 500 a. At this time, the target user terminal may send a service request to the second server in response to the trigger operation. Wherein the service request may be referred to as a chat log acquisition request. Further, the second server may return a chat log between the client a and the employee a to the target user terminal based on the chat log acquisition request.

Further, please refer to fig. 8, which is a flowchart illustrating another data processing method according to an embodiment of the present application. The method relates to a management terminal, a first server, a second server and a target user terminal in a customer service system. As shown in fig. 8, the method may include:

s201, the management terminal sends a batch inheritance request to the first server for a second user associated with the first user.

The specific implementation manner of step S201 may be referred to the description of step S101 in the embodiment corresponding to fig. 3, and will not be repeated here.

S202, the first server performs splitting processing on each inheritance request in the batch inheritance requests, and each split inheritance request is respectively added to a task queue.

S203, when the first server adds each inheritance request to the task queue, the first server generates the adding response information corresponding to each inheritance request.

And S204, the first server returns the adding response information to the management terminal so that the management terminal sets the service state corresponding to each inheritance request to be a state to be confirmed based on the adding response information.

The specific implementation of the steps S202 to S204 may be described in the following corresponding example of fig. 9.

For ease of understanding, further, please refer to fig. 9, which is a schematic view of a scenario for splitting a batch inheritance request according to an embodiment of the present application. As shown in fig. 9, the management terminal may be the management terminal 3000 shown in fig. 2 and the first server may be the first server 1000 shown in fig. 2.

It should be understood that the management terminal may transmit a batch inheritance request to the first server as shown in fig. 9. Wherein the bulk inheritance request may be a bulk inheritance request as in the embodiment corresponding to fig. 2 described above. I.e. the management terminal may send to the first server the users to be allocated, i.e. user 20a (client a) and user 20B (client B) associated with the first user (user 10a, i.e. employee a) determined in the list of users to be allocated, in response to the triggering operation performed for the list of users to be allocated. Further, the first server may obtain a bulk inheritance request sent by the management terminal for the second user (user 40b, employee D) associated with the first user.

It will be appreciated that the first server may take the form of a synchronous return asynchronous process for the bulk inheritance request, as shown in fig. 9. In other words, the first server may split the bulk inheritance request into an inheritance request a associated with client a and an inheritance request B associated with client B. Further, the first server may add the split inheritance request a and the inheritance request B to a task queue, respectively, and process each inheritance request in the task queue in turn. Among other things, the manner in which the first server splits bulk inheritance requests and processes each inheritance request in the task queue in turn may be referred to herein as an asynchronous processing manner. When the inheritance request a and the inheritance request B are successfully added to the task queue, the addition response information corresponding to each inheritance request can be generated. Further, the first server may return each generated added response information to the management terminal together, so that the management terminal changes the service state corresponding to each inheritance request based on each added response information. In this embodiment of the present application, a mode that the first server returns the added response information corresponding to each inheritance request together may be referred to as a synchronous return mode. Therefore, the embodiment of the application adopts a synchronous return asynchronous processing mode for the batch inheritance request, and can effectively avoid the phenomenon that the management terminal waits for overtime.

Wherein it should be appreciated that the first server may generate an add response message associated with the inherited request a after the inherited request a is successfully added to the task queue. When the inheritance request B is successfully added to the task queue, the first server may generate an add response message associated with the inheritance request B. At this time, the first server may return the two added response messages to the management terminal together, so that the management terminal may set the service states corresponding to the inheritance request a and the inheritance request B to be the to-be-confirmed states (i.e., to be confirmed by the client).

In addition, it may be understood that, when the first server processes each inheritance request added to the task queue in sequence, if the management terminal receives a friend adding request sent by a target user terminal corresponding to a target user to be allocated in each inheritance request, the service state corresponding to the inheritance request may be set to a confirmed state (i.e. confirmed).

It can be understood that, when the first server processes the inheritance request a in the task queue, the first relationship record table shown in the above table 1 may be obtained, and since the key information between the client a and the employee a is a bi-directional association relationship (bi-directional friend relationship), that is, the first server may determine the client a as the target user to be allocated. The first server can send configuration text information to a target user terminal corresponding to the client A through account information of the staff A. Further, the client a may send a friend adding request associated with the employee D to the management terminal based on the configuration text information. When the management terminal receives the friend addition request, the service state of the inheritance request a may be set to a confirmed state (i.e., confirmed).

Further, when the first server processes the inheritance request B in the task queue, the first relationship record table shown in the above table 1 may be obtained, because the key information between the client B and the employee a is a unidirectional association relationship (unidirectional friend relationship). Therefore, the first server cannot send the configuration text information associated with the employee D to the client B through the account information (first account information) of the employee a in the case of the one-way friend relationship. At this time, the first server may return the client B to the management terminal within a certain period (for example, 1 day), so that the manager informs the employee D to send a friend adding request to the client B according to the account information of the employee D.

Optionally, the first server cannot send configuration text information associated with the employee D to the client B through account information (first account information) of the employee a in the case of the unidirectional friend relationship. At this time, the first server may also return the client B to the management terminal, so that the client B is displayed on the to-be-allocated user list in the first display interface, and the manager may also select the client B again as the to-be-allocated user to be allocated to the second user. If a preset selection threshold is reached (for example, three times), the management terminal may send the account information of the client B to a second user (for example, employee D), so that employee D sends a friend adding request to the client B according to the account information of employee D.

S205, a first server determines a target user to be distributed, which has a two-way association relation with the first user, from the users to be distributed, and generates configuration text information associated with the second user according to an initial binding relation between the target user to be distributed and the second user.

S206, the first server sends the configuration text information to a second server according to the first account information of the first user.

Specifically, the first server may send the configuration text information to a second server corresponding to a second application (WeChat application) according to the first account information of the first user.

S207, the second server forwards the configuration text information to the target user terminal.

And S208, the target user terminal responds to the triggering operation of the conversation interface where the configuration text information is located, and a friend adding interface independent of the conversation interface is displayed.

Specifically, the target user to be allocated can execute triggering operation for the session interface where the configuration text information is located. The session interface may be a session interface between the first user and the target user to be allocated. At this time, the target user terminal may respond to the triggering operation to display a friend adding interface independent of the session interface.

S209, the target user terminal responds to the friend adding operation aiming at the friend adding interface and sends a friend adding request to the second server.

Specifically, the target to-be-allocated user may perform a friend adding operation on the friend adding interface. At this time, the management terminal may respond to the friend adding operation and send a friend adding request to the second server.

And S210, the second server forwards a friend adding request to the first server when determining that the request initiator is the target user to be allocated.

S211, the first server checks the check key information according to the friend adding request, and when the check is successful, a bidirectional association relation between the target user to be allocated and the second user is established.

The specific implementation manner of step S205 to step S211 may refer to the description of step S102 to step S104 in the embodiment corresponding to fig. 3, and will not be repeated here.

Further, please refer to fig. 10, which is a schematic diagram illustrating a structure of a data processing apparatus according to an embodiment of the present application. The data processing apparatus 1 may be applied to a first server corresponding to a first application, and the server may be the first server 1000 in the embodiment corresponding to fig. 2. The data processing apparatus 1 may include: the system comprises an acquisition module 10, a first generation module 20, a transmission module 30, a building module 40, a splitting module 50, a second generation module 60 and a return module 70.

The acquiring module 10 is configured to acquire a batch inheritance request sent by a management terminal for a second user associated with a first user; the batch inheritance request is determined by the management terminal after service allocation is carried out on users to be allocated which are associated with the first user; the user to be allocated is a user in a second application different from the first application;

wherein, the acquisition module 10 comprises: a list return unit 101, a first acquisition unit 102, a second acquisition unit 103, and a third acquisition unit 104.

The list returning unit 101 is configured to receive a list acquisition request sent by a management terminal for a configuration page of a first application, and return a to-be-allocated user list to the management terminal based on the list acquisition request, so that the management terminal outputs the to-be-allocated user list on a first display interface; the list of users to be allocated comprises the first user and M users to be allocated associated with the first user; m is a positive integer;

Wherein the list return unit 101 includes: a first acquisition subunit 1011, a second acquisition subunit 1012, and a return subunit 1013.

The first obtaining subunit 1011 is configured to obtain a list obtaining request sent by the management terminal for the configuration page of the first application; the list acquisition request is determined by the management terminal in response to a triggering operation triggered by a configuration interface for the configuration page;

the second obtaining subunit 1012 is configured to obtain, according to the list obtaining request, a list of users to be allocated associated with a first user in the first application;

the returning subunit 1013 is configured to return M users to be allocated, which are associated with the first user, in the list of users to be allocated to the management terminal, so that the management terminal outputs the first user and the M users to be allocated on a first display interface.

The specific implementation manner of the first acquiring subunit 1011, the second acquiring subunit 1012 and the returning subunit 1013 may be referred to the description of the first display interface of the management terminal in the embodiment corresponding to fig. 3, and will not be further described herein.

The first obtaining unit 102 is configured to obtain N to-be-allocated users determined by the management terminal from the M to-be-allocated users; the N is a positive integer less than or equal to the M;

the second obtaining unit 103 is configured to obtain initial binding relationships between the N users to be allocated and second users associated with the first user, respectively; the second user is determined by the management terminal in response to a triggering operation triggered by a second display interface;

wherein the second obtaining unit 103 includes: a receiving subunit 1031, a finding subunit 1032, a third acquiring subunit 1033, and a fourth acquiring subunit 1034.

The receiving subunit 1031 is configured to receive an address book acquisition request sent by the management terminal based on the first user; the address book acquisition request is determined by the management terminal in response to a triggering operation for triggering an allocation button in the first display interface;

the searching subunit 1032 is configured to obtain the user information of the first user carried in the address book obtaining request, search, according to the user information, a group to which the first user belongs, and send an address book corresponding to the group to the management terminal, so that the management terminal outputs the address book on a second display interface;

The third obtaining subunit 1033 is configured to obtain a second user determined by the management terminal for the address book on the second display interface;

the fourth obtaining subunit 1034 is configured to obtain an initial binding relationship between the N users to be allocated and the second user, which is established by the management terminal.

The specific implementation manner of the receiving subunit 1031, the searching subunit 1032, the third obtaining subunit 1033 and the fourth obtaining subunit 1034 may refer to the description of the obtaining the initial binding relationship in the embodiment corresponding to fig. 3, and will not be further described herein.

The third obtaining unit 104 is configured to obtain a batch inheritance request associated with the second user, where the batch inheritance request is sent by the management terminal based on the initial binding relationship.

The specific implementation manner of the list returning unit 101, the first acquiring unit 102, the second acquiring unit 103, and the third acquiring unit 104 may refer to the description of step S101 in the embodiment corresponding to fig. 3, and will not be further described herein.

The first generating module 20 is configured to determine, from the users to be allocated, a target user to be allocated that has a bi-directional association relationship with the first user, and generate configuration text information associated with the second user according to an initial binding relationship between the target user to be allocated and the second user; the configuration text information comprises second account information of the second user and verification key information for verification;

Wherein the first generating module 20 includes: a fourth acquisition unit 201, a fifth acquisition unit 202, a determination unit 203, and a generation unit 204.

The fourth obtaining unit 201 is configured to obtain a first relationship record table corresponding to a user to be allocated associated with the first user, search first verification key information in the first relationship record table, and determine the user to be allocated in a list column where the first verification key information is located as a target user to be allocated; the first verification key information is used for representing the bidirectional association relationship between the first user and the user to be allocated;

the fifth obtaining unit 202 is configured to obtain a second relationship record table associated with the first user, search for second calibration key information in the second relationship record table, and obtain a second user in a list field where the second calibration key information is located; the second check key information is used for representing a group association relationship between the first user and the second user;

the determining unit 203 is configured to use the two-way association relationship and the group association relationship as verification key information;

the generating unit 204 is configured to generate, according to the initial binding relationship between the target user to be allocated and the second user, the second account information of the second user, and the verification key information, configuration text information associated with the second user.

The specific implementation manner of the fourth obtaining unit 201, the fifth obtaining unit 202, the determining unit 203 and the generating unit 204 may refer to the description of step S102 in the embodiment corresponding to fig. 3, and the description thereof will not be repeated here.

The sending module 30 is configured to send the configuration text information to a target user terminal corresponding to the target user to be allocated according to the first account information of the first user, so that the target user terminal generates a friend adding request for the second account information based on the configuration text information;

wherein, the sending module 30 includes: a second transmitting unit 301 and a receiving unit 302.

The second sending unit 301 is configured to send the configuration text information to a second server according to the first account information of the first user, so that the second server forwards the configuration text information to a target user terminal corresponding to a target user to be allocated;

the receiving unit 302 is configured to receive a friend adding request forwarded by a second server when determining that a request initiator is the target user to be allocated; the friend adding request is generated by the target user terminal based on the second account information in the configuration text information.

The specific implementation manner of the second transmitting unit 301 and the receiving unit 302 may refer to the description of step S103 in the embodiment corresponding to fig. 3, and the detailed description will not be repeated here.

The establishing module 40 is configured to verify the verification key information according to the friend adding request, and establish a bidirectional association relationship between the target to-be-allocated user and the second user when the verification is successful.

Wherein, the establishing module 40 includes: a verification unit 401, a first sending unit 402 and a setup unit 403.

The verification unit 401 is configured to verify the bidirectional association relationship in the verification key information based on the friend addition request, and verify the group association relationship;

the first sending unit 402 is configured to send the friend adding request to the second account information when the verification is successful;

the establishing unit 403 is configured to establish a bidirectional association relationship between the target user to be allocated and the second user.

The specific implementation manner of the verification unit 401, the first sending unit 402, and the establishing unit 403 may refer to the description of step S104 in the embodiment corresponding to fig. 3, and the description will not be repeated here.

Wherein the apparatus further comprises:

the splitting module 50 is configured to split each inheritance request in the batch of inheritance requests, and add each split inheritance request to a task queue respectively;

the second generating module 60 is configured to generate addition response information corresponding to each inheritance request when each inheritance request is added to the task queue;

the returning module 70 is configured to return the addition response information to the management terminal, so that the management terminal sets a service state corresponding to each inheritance request to a to-be-confirmed state based on the addition response information.

The specific implementation manners of the obtaining module 10, the first generating module 20, the sending module 30, the establishing module 40, the splitting module 50, the second generating module 60 and the returning module 70 may be referred to the description of steps S201 to S211 in the embodiment corresponding to fig. 8, and the detailed description will not be repeated here. In addition, the description of the beneficial effects of the same method is omitted.

Further, please refer to fig. 11, which is a schematic diagram of a computer device according to an embodiment of the present application. As shown in fig. 11, the computer device 1000 may be the first server 1000 in the corresponding embodiment of fig. 2, and the computer device 1000 may include: at least one processor 1001, such as a CPU, at least one network interface 1004, a user interface 1003, a memory 1005, at least one communication bus 1002. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display (Display), a Keyboard (Keyboard), and the network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), among others. The memory 1005 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 1005 may also optionally be at least one storage device located remotely from the aforementioned processor 1001. As shown in fig. 11, an operating system, a network communication module, a user interface module, and a device control application program may be included in the memory 1005, which is one type of computer storage medium.

In the computer device 1000 shown in fig. 11, the network interface 1004 is mainly used for network communication with the management terminal and the second server; while user interface 1003 is primarily used as an interface for providing input to a user; and the processor 1001 may be used to invoke a device control application stored in the memory 1005 to implement:

It should be understood that the computer device 1000 described in the embodiment of the present application may perform the description of the data processing method in the embodiment corresponding to fig. 3 and fig. 8, and may also perform the description of the data processing apparatus 1 in the embodiment corresponding to fig. 10, which is not repeated herein. In addition, the description of the beneficial effects of the same method is omitted.

Furthermore, it should be noted here that: the embodiments of the present application further provide a computer readable storage medium, where the computer readable storage medium stores a computer program executed by the aforementioned data processing apparatus 1, where the computer program includes program instructions, when executed by the processor, can perform the description of the data processing method in the embodiment corresponding to fig. 3 or fig. 8, and therefore, a description will not be repeated herein. In addition, the description of the beneficial effects of the same method is omitted. For technical details not disclosed in the embodiments of the computer-readable storage medium according to the present application, please refer to the description of the method embodiments of the present application.

Further, please refer to fig. 12, which is a schematic diagram illustrating another data processing apparatus provided in the present application. The data processing device may be applied to a user terminal corresponding to the second application, where the user terminal may be the target user terminal in the embodiment corresponding to fig. 2, and the data processing device 2 may include: a receiving module 100, a display module 200 and a request transmitting module 300.

The receiving module 100 is configured to receive configuration text information sent by a first server corresponding to a first application according to first account information of a first user; the configuration text information comprises second account information of a second user and verification key information for verification;

the display module 200 is configured to respond to a triggering operation for a session interface where the configuration text information is located, and display a friend adding interface independent of the session page; the friend adding interface comprises the second account information;

the request sending module 300 is configured to respond to a friend adding operation for the friend adding interface, and send a friend adding request to the second account information; the friend adding request is used for indicating the first server to establish a bidirectional association relationship between the target user to be allocated and the second user when the first server successfully verifies the verification key information, wherein the user to be allocated is a user in the second application different from the first application.

The specific implementation manners of the receiving module 100, the display module 200 and the request sending module 300 may be referred to the description of the target ue in the embodiments corresponding to fig. 3 and fig. 8, and will not be further described herein. In addition, the description of the beneficial effects of the same method is omitted.

Further, please refer to fig. 13, which is a schematic diagram of another computer device according to an embodiment of the present application. As shown in fig. 13, the computer device 4000 may be the target user terminal in the corresponding embodiment of fig. 2, and the computer device 4000 may include: at least one processor 4001, e.g. a CPU, at least one network interface 4004, a user interface 4003, a memory 4005, at least one communication bus 4002. Wherein the communication bus 4002 is used to enable connection communications between these components. The user interface 4003 may comprise a Display (Display), a Keyboard (Keyboard), and the network interface 4004 may optionally comprise a standard wired interface, a wireless interface (e.g., WI-FI interface), among others. The memory 4005 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one magnetic disk memory. The memory 4005 may also optionally be at least one storage device located remotely from the aforementioned processor 4001. As shown in fig. 13, an operating system, a network communication module, a user interface module, and a device control application program may be included in the memory 4005 as one type of computer storage medium.

In the computer device 4000 shown in fig. 13, the network interface 4004 is mainly used for network communication with a second server; while the user interface 4003 is primarily an interface for providing input to a user; and the processor 4001 may be used to invoke the device control application stored in the memory 4005 to implement:

It should be understood that the computer device 4000 described in the embodiments of the present application may perform the description of the data processing method in the embodiment corresponding to fig. 3 and 8, and may also perform the description of the data processing apparatus 2 in the embodiment corresponding to fig. 12, which is not repeated herein. In addition, the description of the beneficial effects of the same method is omitted.

Furthermore, it should be noted here that: the embodiments of the present application further provide a computer readable storage medium, where the computer readable storage medium stores a computer program executed by the aforementioned data processing apparatus 2, where the computer program includes program instructions, when executed by the processor, can perform the description of the data processing method in the embodiment corresponding to fig. 3 or fig. 8, and therefore, a description will not be repeated herein. In addition, the description of the beneficial effects of the same method is omitted. For technical details not disclosed in the embodiments of the computer-readable storage medium according to the present application, please refer to the description of the method embodiments of the present application.

Further, please refer to fig. 14, which is a schematic diagram illustrating a structure of a data processing system according to an embodiment of the present application. The data processing system 3 may comprise data processing means 1a and data processing means 2a. The data processing apparatus 1a may be the data processing apparatus 1 in the embodiment corresponding to fig. 10, and it is understood that the data processing apparatus 1a may be integrated with the first server 1000 in the embodiment corresponding to fig. 2, and therefore, a detailed description thereof will be omitted herein. The data processing device 2a may be the data processing device 2 in the embodiment corresponding to fig. 12, and it is understood that the data processing device 2a may be integrated with the target user terminal in the embodiment corresponding to fig. 2, and therefore, a detailed description thereof will be omitted herein. In addition, the description of the beneficial effects of the same method is omitted. For technical details not disclosed in the embodiments of the data processing system according to the present application, please refer to the description of the method embodiments of the present application.

Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), or the like.

The foregoing disclosure is only illustrative of the preferred embodiments of the present application and is not intended to limit the scope of the claims herein, as the equivalent of the claims herein shall be construed to fall within the scope of the claims herein.

Claims

1. A method of data processing, the method being applied to a first server corresponding to a first application, the method comprising:

determining a target to-be-allocated user with a two-way association relation with the first user from the to-be-allocated users, and generating configuration text information associated with the second user according to an initial binding relation between the target to-be-allocated user and the second user; the configuration text information comprises second account information of the second user and verification key information for verification; the verification key information comprises the bidirectional association relation and the group association relation; the bidirectional association relationship is used for indicating that the target to-be-allocated user and the first user have a bidirectional friend relationship; the group association relationship is used for indicating users belonging to the same group with the first user;

and respectively checking the bidirectional association relation and the group association relation in the checking key information according to the friend adding request, and establishing the bidirectional association relation between the target user to be allocated and the second user when the checking is successful.

2. The method of claim 1, wherein the acquiring the bulk inheritance request sent by the management terminal for the second user associated with the first user comprises:

3. The method according to claim 2, wherein receiving a list acquisition request sent by a management terminal for a configuration page of a first application, and returning a list of users to be allocated to the management terminal based on the list acquisition request, includes:

4. The method of claim 2, wherein the obtaining initial binding relationships between the second users associated with the first user and the N users to be allocated, respectively, comprises:

5. The method according to claim 1, wherein the method further comprises:

6. The method of claim 1, wherein the determining a target to-be-allocated user having a bi-directional association with the first user from the to-be-allocated users, generating configuration text information associated with the second user according to an initial binding relationship between the target to-be-allocated user and the second user, comprises;

7. The method of claim 6, wherein the verifying the verification key information according to the friend adding request, and establishing the bidirectional association relationship between the target to-be-allocated user and the second user when the verification is successful, comprises:

8. The method according to claim 1, wherein the sending the configuration text information to the target user terminal corresponding to the target user to be allocated according to the first account information of the first user, so that the target user terminal generates a friend adding request for the second account information based on the configuration text information, includes:

9. A data processing method, which is applied to a user terminal corresponding to a second application, and is characterized by comprising:

receiving configuration text information sent by a first server corresponding to a first application according to first account information of a first user; the configuration text information comprises second account information of a second user and verification key information for verification; the configuration text information is generated according to an initial binding relationship between a target user to be allocated and the second user; the target user to be allocated is a user which has a bidirectional association relation with the first user and is determined from the user to be allocated when the first server acquires a batch inheritance request sent by the management terminal aiming at the second user; the batch inheritance request is determined by the management terminal after service allocation is carried out on users to be allocated which are associated with the first user; the verification key information comprises the bidirectional association relation and the group association relation; the bidirectional association relationship is used for indicating that the target to-be-allocated user and the first user have a bidirectional friend relationship; the group association relationship is used for indicating users belonging to the same group with the first user;

responding to a friend adding operation aiming at the friend adding interface, and sending a friend adding request to the second account information; the friend adding request is used for indicating the first server to establish the bidirectional association relationship between the target user to be allocated and the second user when the bidirectional association relationship and the group association relationship in the verification key information are successfully verified, wherein the user to be allocated is a user in the second application different from the first application.

10. A data processing apparatus, the apparatus being applied to a first server corresponding to a first application, comprising:

The generation module is used for determining a target user to be distributed, which has a bidirectional association relation with the first user, from the users to be distributed, and generating configuration text information associated with the second user according to an initial binding relation between the target user to be distributed and the second user; the configuration text information comprises second account information of the second user and verification key information for verification; the verification key information comprises the bidirectional association relation and the group association relation; the bidirectional association relationship is used for indicating that the target to-be-allocated user and the first user have a bidirectional friend relationship; the group association relationship is used for indicating users belonging to the same group with the first user;

the establishing module is used for respectively verifying the bidirectional association relation and the group association relation in the verification key information according to the friend adding request, and establishing the bidirectional association relation between the target user to be allocated and the second user when the verification is successful.

11. A data processing apparatus, the apparatus being applied to a user terminal corresponding to a second application, comprising:

the receiving module is used for receiving configuration text information sent by the first server corresponding to the first application according to the first account information of the first user; the configuration text information comprises second account information of a second user and verification key information for verification; the configuration text information is generated according to an initial binding relationship between a target user to be allocated and the second user; the target user to be allocated is a user which has a bidirectional association relation with the first user and is determined from the user to be allocated when the first server acquires a batch inheritance request sent by the management terminal aiming at the second user; the batch inheritance request is determined by the management terminal after service allocation is carried out on users to be allocated which are associated with the first user; the verification key information comprises the bidirectional association relation and the group association relation; the bidirectional association relationship is used for indicating that the target to-be-allocated user and the first user have a bidirectional friend relationship; the group association relationship is used for indicating users belonging to the same group with the first user;

the request sending module is used for responding to the friend adding operation aiming at the friend adding interface and sending a friend adding request to the second account information; the friend adding request is used for indicating the first server to establish the bidirectional association relationship between the target user to be allocated and the second user when the bidirectional association relationship and the group association relationship in the verification key information are successfully verified, wherein the user to be allocated is a user in the second application different from the first application.

12. A computer device, comprising: a processor, a memory, and a network interface;

the processor is connected to a memory for providing data communication functions, a network interface for storing program code, and for invoking the program code to perform the method of any of claims 1-9.

13. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program comprising program instructions which, when executed by a processor, perform the method of any of claims 1-9.